Dynamo comes with a SOLID database preconfigured for evaluation purposes. This database already has the necessary tables created for use with SQL JMS. But if SQL JMS is going to be used on another database, the appropriate tables need to be created in that database. These tables are created by the script that creates the DAF schema:

<ATG9dir>/DAF/sql/install/{db-type}/daf_ddl.sql

This script should be run on the appropriate database to initialize the DAF schema, including the SQL JMS tables. To drop the tables in the DAF schema, use the script:

<ATG9dir>/DAF/sql/install/{db-type}/drop_daf_ddl.sql

To view the SQL JMS database schema, see the DAF Entity Relationship Diagram.

By default, the SQL JMS system uses the JTDataSource component (located in Nucleus at /atg/dynamo/service/jdbc/JTDataSource) to obtain its JDBC connections. This means that SQL JMS uses the same database as other Dynamo application components. If SQL JMS is to be used with a different database, a DataSource component must be configured for that database, and the SQL JMS system must be configured to use this new data source. The SQL JMS system is controlled by the Nucleus component at /atg/dynamo/messaging/SqlJmsProvider; you can set the dataSource property of this component to specify a different data source, like this:

dataSource=/atg/dynamo/service/jdbc/MyDataSource

Configuring the SQLJmsProvider for Informix

If your Dynamo installation uses an Informix database system, add the following setting to the properties of /atg/dynamo/messaging/SqlJmsProvider:

parameterizedSelect=false

Configuring the SQLJmsProvider for DB2

If your Dynamo installation uses a DB2 database system, add the following settings to the properties of /atg/dynamo/messaging/SqlJmsProvider:

parameterizedSelect=false
useSetBinaryStream=false

 
loading table of contents...