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...

TIBCO ActiveMatrix Service Grid- Key Features

• Provides a unified design-time and runtime service framework. Eliminates the need for technology-dependent “wrapper code” for services enablement.
• Enables companies to dynamically deploy services across machines or co-locate them within an OS process, move services to different machines, and add distributed load balancing and fault tolerance.
• The distribution and number of service instances in the grid can be scaled dynamically based on the real-time load and service level agreement using TIBCO ActiveMatrix® Service Performance Manager.
• Embeds TIBCO ActiveMatrix® Service Bus – a lightweight enterprise service bus that helps organizations bridge the mediation gap within their SOA infrastructure, reducing complexity and increasing flexibility.
• Provides a common Eclipse-based environment for service development, assembly, composition, and testing, and a common web-based console for monitoring and management. It reduces operational cost with built-in governance.

Read more...

TIBCO ActiveMatrix Service Grid- Overview

TIBCO ActiveMatrix® Service Grid simplifies heterogeneous SOA by enabling IT organizations to turn their business logic into services and graphically assemble, deploy, host, manage, and monitor these services together as composite applications on a unified runtime foundation.

• Allows developers to focus on the business logic by replacing 20 to 40 percent of the technical code in a service with centralized configuration.
• Reduces architectural complexity by providing a grid- and standards-based, technology-neutral platform with service containers for .NET/C#/VB/WCF, C++, Java, Ruby, and other service technologies.
• Leverages open standards like SCA, with an Eclipse-based environment for service development, composition and assembly, and OSGi-based runtime.
• Provides built-in governance support, allowing you to add governance without impacting existing work.

Read more...