Archive

Posts Tagged ‘websphere’

configure syslog to redirect WebSphere Message Broker (mq) messages to file

April 29th, 2011 No comments

On Linux® and UNIX® systems, all WebSphere® Message Broker messages (other than those generated by the command line utilities) are sent to the syslog, so it is useful to redirect user messages to a separate file.

Start of changeOn UNIX, syslog entries are restricted in length and messages that are sent to the syslog are truncated by the new line character. To record a large amount of data in a log on UNIX, set the Destination property on the Trace node to File or User Trace instead of Local Error Log.End of change

Before you create a broker on Linux or UNIX systems, configure the syslog daemon to redirect user messages to a file called user.log:

Log on as root.
Enter the following commands to create a file called user.log.
On UNIX systems, enter the command:

touch /var/adm/user.log
chown root:mqbrkrs /var/adm/user.log
chmod 640 /var/adm/user.log

On Linux, enter the command:

touch /var/log/user.log
chown root:mqbrkrs /var/log/user.log
chmod 640 /var/log/user.log

Add the following line to the /etc/syslog.conf file Start of change(on later versions of SUSE Linux, this is /etc/syslog-ng.conf)End of change to redirect debug level messages to the file user.log:
On UNIX systems, enter the command:

user.info /var/adm/user.log

On Linux, enter the command:

user.info /var/log/user.log

You can use user.* - instead of user.info in the preceding examples.
* means that information, notice, warning, and debug messages are caught
- means that syslog does not synchronize the file after writing to it.
You might experience a performance gain, but you can lose some data if the computer fails immediately after it has written to the file.
Start of changeAdd a line to ensure that messages at the required level from the user facility are recorded. If you specify a level of info, all operational messages are recorded; these messages provide important information about the operation of the broker, and can be useful in diagnosing problems.End of change
Restart the syslog daemon.
On AIX®, enter the command:

refresh -s syslogd

On HP-UX and Solaris, enter the command:

kill -HUP 'cat /etc/syslog.pid'

On Linux, enter the command:

/etc/init.d/syslogd restart

or

/etc/rc.d/init.d/syslogd restart

for systems where rc.d is not a soft link
For other syslog options, see the documentation for your operating system.

About other websphere message broker documents, please refer to http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp

Categories: IT Architecture, Linux, Systems Tags: , ,