ATG data source components are wrappers that provide the connection information that applications use to connect to the repositories that represent your databases. You can configure datasources very easily through CIM. If you must configure a datasource manually, see the information in this section.

You must configure the componentPath property of the /atg/search/service/SearchJTDataSource component on each of your servers:

componentPath=/atg/dynamo/service/jdbc/Your_Production_DataSource
_Component

By default the SearchJTDataSource component is configured to point to JTDataSource_Production, which is typically a switching data source. You must change this configuration to use a non-switching datasource (such as JTDataSource_Production_core) that points to the production database. (If you are using switching, you can configure the componentPath to point to either datasource that makes up your switch configuration, but do not use the switching datasource itself.)

Note: The startSQLRepository script, which is used to import initial data into Oracle ATG Web Commerce application databases, uses a FakeXADataSource, while JBoss uses a JNDIReference JTDataSource. To work around this, you define a FakeXADataSource in <ATG10dir>/home/localconfig/atg/dynamo/service/jdbc (which startSQLRepository uses) and the JNDIReference in <ATG10dir>/home/servers/server_name/localconfig/atg/dynamo/service/jdbc (which JBoss uses). The JNDI name must match the JBoss name for the management schema.

Note: All servers that share a data source need to use a common server lock manager.