The SearchSQLQLRepository and SearchSQLRepositoryEventServer components are used by the subscriber table needed for GSA distributed cache invalidation.
These components are located in the DAF.Search.Base module, in the /atg/search/service component directory. By default, these components point to the local, default JDBC connection and the related services. If your environment has both production and internal-facing ATG instances, you must change these components on the internally-facing machines to point to the _production versions of the target components.
Note: Oracle ATG Web Knowledge Manager sets these components to point to their _production equivalents automatically, and you do not need to configure them further.
Component | Default Setting | Production Setting |
|---|---|---|
|
|
|
The |
|
|
Note: There should only be one SQLRepositoryEventServer per data source. It’s important that /atg/dynamo/server/SQLRepositoryEventServer_production on the asset management server and /atg/dynamo/server/SQLRepositoryEventServer on the production server are connected to the same database account.
If you want to use something other than the production server as the target, clone the _production components and configure them to point to components on your alternative server. Most installations should not require this.
