ATG’s Configuration and Installation Manager (CIM) helps to simplify ATG product configuration by walking you through the required steps. This ensures that all necessary steps are completed and are done in the correct order. You can use CIM to get a working installation running quickly and easily, but keep in mind that you will most likely end up doing further configuration on your installation as your project evolves.
CIM handles the following configuration steps:
Creates data sources according to the database connection information you supply, including those needed for the ACI data warehouse.
Creates database tables and imports initial data, including those for the ACI data ware house.
Creates and configures ATG servers, including a lock manager and a data warehouse loader server.
Assembles your application EAR files for each ATG server.
Deploys EAR files to your application server.
See Appendix C, Search CIM Details for a full listing of the database scripts and configuration files CIM uses. See the CIM help and the ATG Installation and Configuration Guide for additional information on CIM.
To configure Search using CIM, do the following:
Install your application server.
Install your applications.
To start CIM, go to
<ATG9dir>/home/binand type:cimSelect the products you want to configure.
Select add-ons, including Search.
Continue through CIM according to the prompts. Type H at any prompt for additional information.
Note that CIM does not configure the following:
Standalone Search engines
Any components for a staging environment to be used with Search, including:
Your Content Administration topography. See the Setting Up an Asset Management Server chapter of the ATG Content Administration Programming Guide.
Your Commerce store and
IndexingOutputConfigcomponent. See the ATG Commerce Search Guide. CIM does handle some configuration options, such as whether you plan to index by product or by SKU, but you will most likely have to do additional configuration.Automatic startup for the
ProductCatalogOutputConfigcomponents on either production or staging servers. You must manually configure these components to start automatically.Configuration for deployment-triggered indexing (see Synchronizing Versioned Repository Deployment and Indexing). You must manually configure these components.
Your Search project, indexing rules, and customizations. See the ATG Search Administration Guide.
