TIBCO BusinessWorks log4j File

The standard log4j logging service is available for components of TIBCO BusinessWorks. The log4j is the logging infrastructure developed by the Apache group, and is separate from the standard TIBCO logging infrastructure. For more information, please see http://logging.apache.org/log4j/docs/index.html

Custom java code (BusinessWorks JavaCode or JavaMethod activity) can send log message to the TIBCO BusinessWorks log file by using the log4j logger "bw.logger" that is specified in log4j property file and its located at (BW_HOME\5.x\lib\log4j.properties).

For example, TIBCO BusinessWorks JavaCode activity may use the following code to log warning message to the BusinessWorks log file:

org.apache.log4j.Logger logger = org.apache.log4j.Logger.getLogger("bw.logger"); logger.warn("This is a warning message from BW JavaCode activity");

If you use your own logger class, you can configure the TIBCO BusinessWorks log4j properties file to include your logger. This involves adding log4j.logger and log4j.appender properties to the properties file.

Do not move this file from its current location (BW//lib), as this is where BW expects to find this file. If you would like to use a different file in a different location please see the BW documentation.

Read more...

Graphical user interface utility for EMS- GEMS 3.2 & Software

Gems is a graphical user interface utility for TIBCO Enterprise Message Service (EMS). It can be used by JMS developers as a general purpose test debugging tool and by administrative support staff as a management and monitorig tool.

Gems provides the following main features:

• Server Monitoring- Server state and main statistics are automtically updated, warning and error limits may be configured. Server generated events are also captured.
• Server Management- Including, general server configuration, JMS destinations, JNDI factories, users/groups, permissions, bridges, routes etc.
• JMS support- Messages may be sent/received, queues may be browsed and message contents inspected. Selectors and filters may be specified.
• JMS Message Monitoring- Messages may be monitored (snooped) as they pass trough the server. Request and reply messages can be correlated to provide service response times.
• JMS Message Management- Eg; purging messages, copy messages from a queue to another queue on a different server.
• Charting- Server statistics may be charted in real time, data may be saved to CSV files for export to other tools such as Excel.
• Logging- Server statistics may be logged automatically when warning or error limits are breached.
• Security- SSL connectivity, view only mode.

To get GEMS software click Here.

Read more...