Message Broker Error Log
Contents |
RSS Feed - WebSphere MQ
Rabbitmq Broker Log File
Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » WebSphere Message Broker Support » Message Broker logging Message Broker logging « View previous topic :: View next topic » Author Message rmah Posted: Wed Jan 28, 2009 5:10 pm Post subject: Message Broker logging CenturionJoined: 04 May 2007Posts: 142 Hi, I notice that Message Broker logs to /var/log/messages. This file is usually only readable by root. Is there any way to change or customize where https://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/au16700_.htm message broker logs? thanks! _________________MQ 6.0.2.3 Broker 6.0.0.7 for Linux Back to top Ric-Tic Posted: Wed Jan 28, 2009 7:15 pm Post subject: Re: Message Broker logging ApprenticeJoined: 18 Nov 2003Posts: 38Location: Zurich, Switzerland rmah wrote: Hi, I notice that Message Broker logs to /var/log/messages. This file is usually only readable by root. Is there any way to change or customize where message broker logs? thanks! http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/an04230_.htm Back to top smdavies99 Posted: Thu Jan http://mqseries.net/phpBB/viewtopic.php?t=47440&sid=3f1bfe27ddbd393e2f2bdcbdd09a293d 29, 2009 3:14 am Post subject: Jedi CouncilJoined: 10 Feb 2003Posts: 5826Location: Somewhere over the Rainbow this side of Never-never land. Having /var/log/message readable by 'non root' users or (typically) 'oper' group uses may be against the security policies (or the local sysadmin's fiefdom)for your organisation. Ok, it shouldn't matter on Dev systems but I have come accross companies that refuse event to let non root users see the contents even on Dev boxes. This is a clear argument for having proper exception handling built into every flow from day 1. With the advent of file output nodes in the V6.1 base product, you can write exceptions to file in places /var/tmp which (unless the security people are complete sadists and many of us have met these people from tile to time ) should be readable by everyone. If you can't read them from there, you will have to request the creation of a directory somewhere (with appropriate group read/write privs) that will allow you to do read the output._________________WMQ User since 1999 MQSI/WBI/WMB/'Thingy' User since 2002 Linux user since 1995 Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Monhas the following sections: Working with Log Files Logging Security Exceptions Problems and Common Solutions Working with Log Files The Oracle Message https://docs.oracle.com/cd/A87860_01/doc/ois.817/a65435/logging.htm Broker stores status and error messages in Oracle Message Broker log files. A log file includes information that is helpful for diagnosing problems and for tracking http://peoplesoft.wikidot.com/integration-broker-logging the operation of the Oracle Message Broker. Log files allow Oracle Message Broker administration and support personnel to diagnose problems with the system. By default, the log message broker file is named omblog with the appended values as shown below, or the name is specified using the string defined in the Java property oracle.oas.mercury.logName. omblog-hostname-time where: hostname is the name of the system where the Oracle Message Broker is running. time is the value of the current time, in milliseconds, when the omblog message broker logs file is created. Logging Directory When running in remote mode, the Oracle Message Broker creates log files in the directory $OMB_HOME/logs if $OMB_HOME is defined and $OMB_HOME/logs is writable (on Windows NT systems, the directory is %OMB_HOME%\logs if %OMB_HOME% is defined and %OMB_HOME%\logs is writable). Otherwise, log files are created in the current directory. When running in local mode, the Oracle Message Broker creates the log file in one of the following two directories: The current directory The directory that is specified using the Java property oracle.oas.mercury.logDirectory. The directory specified with the oracle.oas.mercury.logDirectory property must be writable. When running in Local Mode, the Oracle Message Broker appends information to the log file, if the specified log file already exists. It does not overwrite existing logging information. The Oracle Message Broker administrator is responsible for deleting unused log files. DMS Metric Log Files Use the MsgBroker command with the -stats option to save the collected Dynamic Monitoring Service me
Contributing to the Wiki Forums Forum Recent posts Hints, Tips and Gotchas Ask for Help General Discussion Employment Opportunities Seen a new PeopleSoft implementation? Report it now – asterlan.com Top Articles Application Engine Auditing User Profiles Batch Scheduling Campus Solutions Tables CI Development FAQ Component Interfaces CI Based Web Services Consuming a Web Service Copying Rowsets Data Archive Manager Debugging and Tracing Definition Security Designing Pages Email Message Catalog Integration Broker Managing Indexes Migrate Project PeopleTools Security Process Scheduler Report Manager Skilling up for Fusion System Process Requests Testing Web Services Text Editors Tracing App Designer XML (BI) Publisher Resources Great Free Software PS Chrome Helper Extension Oracle PeopleBooks PeopleSoft Resources PeopleSoft Web Search Useful Web Sites Links mcAMDOIS - CAPI Grey Sparling's Blog PSST0101 The PeopleSoft DBA PeopleSoft Tipster PeopleSoft Corner Jim's PeopleSoft Journal PeopleSoft Tutorial Blogging about Oracle Applications PeopleSoft Learnings PeopleSoft Career PeopleSoft SQR PeopleTools Blog PeopleSoft Support Tips Extra Hot Working Scripts PeopleSoft / Oracle Tips ERP Wizard PSFT_PP Cedar Hills Group Remote DBA Integration Broker Logging Integration Broker logging can be very useful for troubleshooting messaging issues. This article goes through how to enable and view integration broker logs. Integration Broker Gateway Properties Integration broker logging settings are configured under: PeopleTools > Integration Broker > Configuration > Gateways. Open your local Gateway (usually called LOCAL) and click on the Gateway Setup Properties. Login to the gateway properties using the default user ID and password (they are provided on the page). You may need to ask your system administrator for the appropriate credentials if the default values do not work. Once you login, click on the Advanced Properties Page link. This will open the integrationGateway.properties file and allow you to edit it. Logging Settings Scroll through the integrationGateway.properties file until you find the logging section. The following line is what sets the logging level (2 is the default): ig.log.level=2 The logging levels are: Level Value -100 Suppress any logging -1 Language Exception 1 Standard Gateway Exception 2 Errors and Warnings 3 Important information, errors and wa