If you will use SQL JMS, create the appropriate tables in that database. These tables are created by the script that creates the DAS schema:

<ATG10dir>/DAS/sql/install/{db-type}/das_ddl.sql

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

<ATG10dir>/DAS/sql/install/{db-type}/drop_das_ddl.sql

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 Oracle ATG Web Commerce 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 Oracle ATG Web Commerce 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 Oracle ATG Web Commerce installation uses a DB2 database system, add the following settings to the properties of /atg/dynamo/messaging/SqlJmsProvider:

parameterizedSelect=false
useSetBinaryStream=false