WebSphere

Create database resources

You can use the createMessageLoggerResource.jacl script to create database resources for the Message Logger mediation primitive.

Context

When you install and configure WebSphere Process Server, or WebSphere Enterprise Service Bus, you can create database resources that are suitable for the Message Logger mediation primitive.

After you have installed your runtime product, you can use the createMessageLoggerResource.jacl script to create database resources for the Message Logger primitive. The createMessageLoggerResource.jacl script is in the bin directory, under the product installation directory.

You might use the createMessageLoggerResource.jacl script under the following circumstances:
  • If you were migrating from a previous version of the runtime product, and did not want to use the Common database for the Message Logger primitive.
  • If you wanted multiple schema qualifiers, on z/OS® or i5/OS. You could then compartmentalize Message Logger data in the Common database. For example, you could use one schema for test data and another schema for production data.

Requirements

The createMessageLoggerResource.jacl script is run using the wsadmin scripting client. Wsadmin is a non-graphical scripting client that lets you perform administrative tasks from a script. At run time, the wsadmin scripting client is in the bin directory, under the product installation directory.

Purpose

The createMessageLoggerResource.jacl script can be used to create:
  • A database.
  • A database table.
  • A JDBC data source.
  • A schema qualifier.

The following examples show a few of the script flags: many of the flags are optional and have default values. For more information on the optional flags, and their default values, refer to the createMessageLoggerResource.jacl script.

Example: create a database

On Windows, the following example creates a database called EsbLogMedDB, of type DERBY_EMBEDDED. The example also creates a table called MSGLOG under a schema qualifier of ESBLOG:
Draft comment:
After wsadmin.bat you can use -conntype none, but what about -profileName ??
wsadmin.bat -f createMessageLoggerResource.jacl -createDb

Example: create a table in a database

On Windows, the following example creates a table called MSGLOG under a schema qualifier of ESBLOG. The table is created in database EsbLogMedDB, which is of type DERBY_EMBEDDED:
Draft comment:
After wsadmin.bat you can use -conntype none, but what about -profileName ??
wsadmin.bat -f createMessageLoggerResource.jacl -createTable

Example: create a data source for a database

On Windows, the following example creates a data source at jdbc/mediation/messageLog, scoped at the cell level:
Draft comment:
After wsadmin.bat you can use -conntype none, but what about -profileName ??
wsadmin.bat -f createMessageLoggerResource.jacl -createDataSource -scopeLevel cell

Example: create a database schema name

The -createSchemaVariable flag creates a schema variable as a WebSphere environment variable. On Windows, the following example creates a WebSphere environment variable at the default scope level, with a value of esblogtest. The WebSphere environment variable created is always called ESB_MESSAGE_LOGGER_QUALIFIER:
Draft comment:
After wsadmin.bat you can use -conntype none, but what about -profileName ??
wsadmin.bat -f createMessageLoggerResource.jacl -createSchemaVariable -dbSchemaName esblogtest

reference Reference topic

Terms of use | Feedback


Timestamp icon Last updated: 20 June 2010 00:39:57 BST (DRAFT)


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.wbit.help.medprim620.doc/ref/rwesb_MessageLoggerJacl.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).
iDoc on