When you add a new environment type to your installation, you must create content adapter components for it. To do this, duplicate the following three component pairs on the asset management server (where Search Administration runs):

You can find components by searching in the Component Browser of the Dynamo Server Admin (see the ATG Installation and Configuration Guide for information on Dynamo Server Admin).

Place the copies in your asset management server’s localconfig directory, and give them names that reflect the new environment type. In this example, the components have _test appended to the name. When you create the copy, make sure that your new component is complete and includes the class and scope information.

Then configure the componentPath property of each standard component to point to the remote version of each component. For example, configure the new CatalogRankConfigAdapter_test to point to the new RemoteCatalogRankConfigAdapter_test:

componentPath=RemoteCatalogRankConfigAdapter_test

The remote components each include a number of properties; for this purpose, the important ones are remotePath, remoteHost, and *path. Configure these properties to point to the component running on the production server (which in this case is a test environment you are adding). In RemoteCatalogRankConfigAdapter_test, configure these properties:

# /atg/commerce/search/config/RemoteCatalogRankConfigAdapter_test.properties

...
remoteHost=testhost.company.com
remotePort=8860
# path to the customization data adapter on the remote test host
remoteCustomizationDataAdapterNucleusPath=\
  /atg/commerce/search/config/CatalogRankConfigAdapter_test

The path in this case is the path on the remote machine (in the component name, Remote indicates that the component points to a remote component; in the property name, remote indicates the pointer to that remote component).