One of them is the possibility to store persistent messages in a database. In previous versions, the only possibility was to use file based storage. In case you wanted to use fault tolerant groups of servers, this caused some difficulties as having both the messages and the shared state information in files required them to be in a shared storage device, either via hardware  (SCSI and SAN, NAS or NAS with NFS) or software (Cluster Server or Clustered File System). These solutions are expensive and hard to maintain while using a database eases the configuration and leaves the hard work on the DBMS. You can even combine file and database based storage depending on the queue or topic.

Database storage is based in Hibernate, so any database server supported by Hibernate could be used to store the data. To use it, first we will need to enable it, setting the following parameters in the tibemsd.conf file:

• dbstore_classpath: pointing to the hibernate and DB driver jar files.
• dbstore_driver_name: specifies the jdbc driver.
• dbstore_driver_dialect: specifies the hibernate driver dialect.
• jre_library: associated JVM libraries.

Second, we will have to create the stores in the stores.conf file, for example:

[TSLstore] dbstore_driver_url=jdbc:mysql:thin:localhost:3306:TSLDB dbstore_driver_username=anonymous dbstore_driver_password=anonymous

Third, link the destinations with the appropriate store, either in the topics.confand queues.conf files or using the command line administration tool with thesetprop command, e.g.

setprop topic my.topic store=dbstore

Finally, we will need to export the EMS database tables using the EMS Schema export tool provided with EMS:

java -jar <EMS_home>/bin/tibemsd_util.jar -tibemsdconf <route_to_tibemds.conf>/tibemsd.conf -createall -export

To view the data logged by the mediation Log task that is in a mediation flow, you must configure a logger.You can configure the logger/appender in one of two ways:

●Use the TIBCOActiveMatrix Administrator-see Configuring the Logger/Appender Using the TIBCO ActiveMatrix Administrator
●Use the bootStrap.xml file-see Configuring the Logger/Appender Using the bootStrap.xml File

IMHO, using the first method (via the admin is easier)

Configuring the Logger/Appender Using the TIBCO ActiveMatrix Administrator

You can configure a logger/appender for a service unit of an ActiveMatrix service assembly using the TIBCO ActiveMatrix Administrator. When a logger is configured for a service unit, all data logged by the service unit for a specified log role will be written to the same appender. The logged data will include data from the Log mediation task, as well as the data from the other loggers in the service unit. To configure the logger/appender using the ActiveMatrix Administrator Follow these general steps to configure the logger at a mediation service unit level:

1.Start the web-based TIBCO ActiveMatrix Administrator.
2.Select the Deploy to an Environment perspective.
3.From the Service Assemblies table, select a service assembly.
4.On the General Settings tab, select the Logging Configurations option.
5.On the Logging Configurations tab, click the Service Unit Logging button.
6.Choose the Mediation service unit and provide the required logging configuration details.

Here you can choose the your appender (console, file – also specify file name, jms) and the log level that you want to set. If you choose the file appender and specify a file name as “abc.log”, the log file will be created in the logs folder of the node.

If you do all this and still don't see the logs, just restart the SA.

For training on TIBCO mail us at [email protected]

TIBCO ActiveMatrix Service Bus is a lightweight enterprise service bus that helps organizations bridge the mediation gap in their SOA infrastructure. It reduces complexity and increases flexibility and reuse by replacing hard-coded service dependencies with configuration, and can be used to quickly on board services from a third-party environment or a TIBCO-based infrastructure.

• - Reduces complexity by enabling quick and easy onboarding of a large number of services with TIBCO’s unique                  AutoMediate feature.
• - Lowers cost by providing an SOA infrastructure that fits into any heterogeneous environment.
• - Saves time and reduces complexity with role-based, easy-to-use, lifecycle management.
• - Simplifies management and prevents security breaches with built-in governance.
• - Increases flexibility and service reuse by replacing hard-coded service dependencies and protocols with dynamic configuration and deployment.

An underlying grid-based architecture makes it possible to scale up (by adding multiple instances of ActiveMatrix Service Bus to the same JVM) and out (by adding multiple instances of ActiveMatrix Service Bus across JVMs, or on different machines) dynamically at runtime and on commodity hardware. The mediation layer can scale to meet high availability and fault tolerance requirements. With ActiveMatrix Service Bus, policy enforcement is built in. Rather than having a separate component (proxy agent) bolted on top of the mediation layer, baked-in policy enforcement ensures fewer moving parts to manage, resulting in fewer security loopholes.

For training on TIBCO mail us at [email protected]