The Configuration and Installation Manager (CIM) helps to simplify 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 an installation running quickly and easily.
CIM handles the following configuration steps:
Creates database tables and imports initial data as described in this chapter, including those for the reporting data ware house.
Creates data sources according to the database connection information you supply (as described in the ATG Installation and Configuration Guide), including those needed for the reporting data warehouse.
Creates and configures Oracle ATG Web Commerce servers, including a lock manager (as described in the ATG Installation and Configuration Guide and the ATG Platform Programming Guide) and a data warehouse loader server.
Assembles your application EAR files for each Oracle ATG Web Commerce server (as described in the ATG Platform Programming Guide).
Deploys EAR files to your application server.
See the CIM help and the ATG Installation and Configuration Guide for additional information on CIM.
To configure Commerce using CIM, do the following:
Install your application server.
Install your Oracle ATG Web Commerce applications, using the appropriate installers for each.
Create your databases and set up accounts (note that you do not need to do this if you are configuring the included MySQL demo database).
To start CIM, go to
<ATG10dir>/home/bin
and type:cim
Note: Type H at any prompt for additional information as you proceed through the configuration steps. Note also that CIM menus change dynamically depending on which products you have installed and which selections you have previously made in your configuration.
Select the products you want to configure.
Select add-ons. Add-ons are applications that support other applications, but which are unlikely to be used on their own.
Select any demo applications you want to install.
Select whether you want to configure a switching or a non-switching datasource. See Creating Tables for a Switching Schema for more information on switching.
Select your application server.
Configure your database. This involves the following steps:
Configure datasources for each database. A datasource is a configuration file that contains the connection information for your database. CIM automatically calculates which databases are required to support your installation. (For example, if you are not using switching, you probably only need to configure Publishing and Production Core datasources; if you are using switching, you must also configure your two switching datasources.)
For the MySQL demo database, use the following values:
User name: (see table that follows for user names)
Password: (see table that follows for passwords)
Host: localhost
Port: 3306
Database Name: (see table that follows for database names)
Database URL: (automatically generated)
JNDI Name: (use the CIM-generated name)
Driver Path: <ATGdir>/MySQL/mysql-connector-java-5.1.15-bin.jar
Database Name
Account User Name
Password
production_core
prod
Welcome1
publishing
pub
Welcome1
switchingA
switchA
Welcome1
switchingB
switchB
Welcome1
agent
agent
Welcome1
datawarehouse
dw
Welcome1
Create schemas. CIM automatically runs the scripts that create your database schemas and imports any initial data required. Before you can import data into the MySQL demo database, you may be prompted to create passwords for user accounts.
Configure your server instances. See the ATG Installation and Configuration Guide for information on server instances. CIM automatically calculates the minimum number of server instances required to run your installed products. For most Commerce installations, you need at least a publishing server and a production server.
Assemble and deploy your application EAR files to your application server.
Note that CIM does not configure the following:
Your ATG Content Administration topography. See the ATG Content Administration Programming Guide.
Your Oracle ATG Web Commerce Search
IndexingOutputConfig
component. See the ATG Search Installation and Configuration Guide. CIM does handle some Search configuration options, such as whether you plan to index by product or by SKU, but you will most likely have to do additional configuration.