Electronic Journal external definitions

The Electronic Journal service has the following data externalized in the services definition file:
Table 1. JDBCJournal tag
Tag attribute Tag description
id Name of the JDBCJournal attribute.
schema Schema name. If the schema is created in the DBMS, the schema name must match the DBMS specifications (for instance, in DB2®, the name must be 8 characters or fewer and uppercase).
dataSourceName The DataSource object name to be used by all requests to get a connection. This should be specified when working with the connection pooling provided by WebSphere® Application Server or with any other JDBC implementation of the connection pooling. This name requires a context part and a logical name part, since it will be used to do a lookup in the naming context. A typical string might look something like "jdbc/sample," where the context is "jdbc" and the logical name is "sample." This information can be supplied by the WebSphere administrator, and it identifies the DataSource object placed in the naming service.
createSchema A boolean value. If set to true (the default value), the service understands there is a schema in the database that keeps the journal tables. If you set this attribute to false, the service understands there is no schema created in the database for keeping the journal tables. You must set this attribute to false if the DBMS being used does not support schemas (such as DB2 UDB for OS/390®).
isRecIdFromTable Determines whether multiple journal instances defined in the context can use the same set of journal tables. The attribute's value can be true or false (default). It’s recommend to enable this in cluster journal environment.
Table 2. column tag
Tag attribute Tag description
id Journal table column name used for mapping.
dataName Operation context DataField name (or the key that keeps the data field value) used for mapping.