This section provides step by step instructions for using CIM to configure your ATG Search installation.
CIM greatly reduces the chance for configuration errors. It configures datasource components, calculates which database scripts to run in what location and what order, determines which data imports are required, configures lock managers, and creates the required server types for the selection of products have you have installed.
For general instructions on using CIM, see the ATG Installation and Configuration Guide. CIM dynamically generates menus based on which configuration steps you have performed and which products you have installed.
Note that you will need connection information for your database (usernames, passwords, driver location, etc.) before performing the database configuration steps.
Start CIM.
From the Main Menu, select Product Selection.
From the Product Selection menu, choose Search and any other products you want to configure. Only products you have installed can be selected.
From the Commerce Addons menu, select any additional features to configure, such as dedicated lock servers or staging servers.
Additional steps not related to Search may follow, depending on your selected addons.
Specify which server should include the optional QueryConsole tool, if you plan to use it. See the Sample Application section of the ATG Search Query Guide for information.
Select Index by Product or Index by SKU. See the ATG Search Administration Guide.
Additional steps not related to Search may follow, depending on your selected addons.
From the Main Menu, select Datasource Configuration. CIM guides you through the process of configuring the datasources needed to communicate with the schemas required by your product combination. Follow the prompts to configure your datasources.
Select database type
Enter the use name for the database connection.
Enter the password for the database connection.
Enter the hostname of the machine on which the database is installed.
Enter the port number used to connect to the database.
Enter the database name.
CIM automatically creates the database URL. Check it for errors before proceeding.
Enter the path to your database driver.
CIM automatically assigns a JNDI name to the datasource. You can accept the default or provide your own JNDI name.
From the Configure Datasource menu, select Test Connection to ensure that your datasource is correctly configured.
From the Configure Datasource menu, select Create Schema.
From the Configure Datasource menu, select Import Initial Data.
From the Main Menu, select Server Instance Configuration. CIM automatically determines which server types are required. Perform the steps required under general configuration.
For a publishing server, specify the hostname for the Search instance, and the RMI port it will use to connect to either the staging server or production server.
Note: Server instance types represent publishing, asset management, etc. server types. Server instances represent individual servers of that type.
For each server instance type, configure at least one server instance. For many installations, you only need one instance of each type.
Perform any non-CIM configuration tasks as specified by the relevant roadmap.
Use CIM to assemble and deploy your applications. From the Main Menu, select Application Assembly and Deployment. CIM walks you through creating EAR files based on your server instances and deploying them to the application server.
Note that CIM does not configure the following:
Standalone search engines.
Any components for a staging environment to be used with Search.
Your ATG Content Administration topology. See the Setting Up an Asset Management Server chapter of the ATG Content Administration Programming Guide.
Your
IndexingOutputConfigcomponent. 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.
Additional search environments. CIM automatically adds a
/atg/commerce/search/catalog/QueryRequest.propertiesfile with the following configuration:targetName=StagingHowever, in order to use the target, you must manually add the appropriate search environments.
