ATG data source components are wrappers that provide the connection information that applications use to connect to the repositories that represent your databases. The database tables used by Search fall by default into two schemas:
management (also called publishing), which contains some versioned data used by Search
production, which contains most of the Search data
Though your DBA may configure your database differently, ATG documentation assumes the default arrangement.
Note: The startSQLRepository script, which is used to import initial data into ATG application databases, uses a FakeXADataSource, while JBoss uses a JNDIReference JTDataSource. To work around this, you define a FakeXADataSource in home/localconfig/atg/dynamo/service/jdbc (which startSQLRepository uses) and the JNDIReference in home/servers/server_name/localconfig/atg/dynamo/service/jdbc (which JBoss uses). The JNDI name must match the JBoss name for the management schema. In order for JBoss to use the server, you must specify that server when you issue the startDynamoOnJBOSS command.
Note: All servers that share a data source need to use a common server lock manager.
You do not need to do any Search-specific datasource configuration for the management schema. For the production schema, you need to configure the following datasource for all of your ATG servers:
/atg/search/service/SearchJTDatasource
Configure the componentPath property of the SearchJTDataSource component on each of your ATG servers (asset management, production, staging).
/atg/search/service/SearchJTDatasource
componentPath=/atg/dynamo/service/jdbc/JTDataSource_Production_Core
Each of these SearchJTDataSource components must ultimately point to the same (production) database schema, but each might refer to a different datasource in the componentPath property, depending on how your data sources are configured and named.
By default the SearchJTDataSource component on the asset management server 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 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.
