The database

XBM store information concerning JCLs execution in a relational database. All data types used by XBM are SQL ANSI standard, and access to the RDBMS is made trough JDBC, so each ANSI DB supporting JDBC can be used.

More sessions of XBM may access the same database, that means that all the information concerning the job execution of several XBM instances in the network can be tracked in one single database.

Furthermore, even if you have more than one XBM instance, you only need to define users once, and simply assign the desired one to the required instance, with the necessary authorization level.

A sample scenario:

The machine PROD serves the production for the applications A01 and A02. The machine DEV serves both development and test environments.

On PROD machine two instances of XBM run to serve application A01 and A02. On DEV machine two XBM instances run to serve the development environment and the test environment. All these instance may access the same database and store their information on a single destination.

The XBM users are define only once: someone is assigned only to one instance (i.e. A01 operators); someone is assigned to multiple instances (i.e. developers are assigned to both development and test instances); other ones are assigned to all instances (i.e. administrators are assigned to all instances).

Pluggable reports

Data stored in database can be extracted and printed using the features offered by the RDBMS or using the pluggable report mechanism provided by XBM remote console.

Pluggable reports are Java objects which are subclasses of abstract class com.hite.xbmReport.

For more information concerning writing pluggable reports please refer to Plugins chapter.