In this section, you use CIM to create the Endeca application that supports Commerce Reference Store. Note that this section assumes that you are installing Oracle ATG Web Commerce and Oracle Endeca Commerce on the same machine. In this case, CIM can be used to create the Endeca application.
If Oracle ATG Web Commerce and Oracle Endeca Commerce are installed on different machines, you must create the Endeca application via a script. Note that Oracle Endeca Commerce does not support the AIX operating system; therefore, if you are installing Oracle ATG Commerce on AIX, you must install Oracle Endeca Commerce on a separate Linux, Windows, or Solaris machine and use a script to create the Endeca application. See Appendix A: Creating the Endeca Application via Scripts for detailed instructions. After creating the Endeca application, continue with the Assembling and Deploying Your ATG Applications in this guide.
To create the Endeca application:
In a new UNIX shell or command prompt, create the directory where the Endeca applications are deployed, for example,
/usr/local/endeca/AppsorC:\Endeca\Apps.In the CIM MAIN MENU, select [3] Server Instance Configuration.
In the SERVER INSTANCE TYPE SELECTION menu, select [S] Production Server - 1 Instance Configured – DONE.
In the SERVER INSTANCE TYPE CONFIGURATION menu, select [D] Deploy CRS Endeca Application – OPTIONAL.
Select [E] Endeca App Configuration with Experience Manager Preview.
Enter the following information. Defaults are provided in brackets:
CRS Endeca App Name [CRS]
CRS Endeca App Deployment Path, for example,
/usr/local/endeca/AppsorC:\Endeca\AppsEAC Port Number [8888]
Dgraph Port Number [15000]
Authoring Dgraph Port Number [15002]
Log Server Port Number [15010]
CAS Hostname [localhost]
CAS Port Number [8500]
CAS Path including the version number. Enter the CAS Path using UNIX-style forward slashes, even if on Windows, for example,
/usr/local/endeca/CAS/11.0.0orC:/Endeca/CAS/11.0.0.CAS Version [11.0.0]
Language Code [en]
Fully-qualified Workbench Hostname, Including Domain [localhost]
Workbench Port Number [8006]
Production application server host name [localhost]
Production application server HTTP port number. Typical values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9080 for WebSphere.
Preview host name [localhost]
Preview port number. Typical values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9080 for WebSphere.
Context root of the preview application [crs]
Host name of the ATG user segment server. This is the server that will respond to Experience Manager requests for Busines Control Center user segment data. Oracle recommends using the Content Adminstration server (also called the Publishing server in this guide). [localhost]
HTTP port of the ATG user segment server.
IMPORTANT: If you are following the instructions in this guide, these values are 7103 for WebLogic, 8180 for JBoss and Tomcat, and 9181 for WebSphere (note that these values do not match the values provided in the CIM prompt).
Path for the Oracle Wallet
jsp-config.xmlfile, for example,/usr/local/endeca/ToolsAndFrameworks/11.0.0/server/workspace/credential_store/jsp-config.xmlorC:\Endeca\ToolsAndFrameworks\11.0.0\server\workspace\credential_store\jps-config.xmlDirectory where the application configuration archives are exported to. Commerce Reference Store does not use this Endeca feature, so you do not need to provide a value for it.
Path to the Endeca ToolsAndFrameworks directory, for example,
/usr/local/endeca/ToolsAndFrameworks/11.0.0orC:\Endeca\ToolsAndFrameworks\11.0.0Path to the Endeca MDEX directory including the version number, for example,
/usr/local/endeca/MDEX/6.5.0orC:\Endeca\MDEX\6.5.0Path to the Endeca Platform Services directory including the version number, for example,
/usr/local/endeca/PlatformServices/11.0.0orC:\Endeca\PlatformServices\11.0.0
Select [D] Deploy to deploy the Endeca application.
In the INITIALIZE CRS ENDECA APP menu, choose [I] Initialize. After the initializing is done, you are returned to the SERVER INSTANCE TYPE CONFIGURATION menu.
In the SERVER INSTANCE TYPE CONFIGURATION menu, choose [O] Configure Another Server Instance Type.
In the SERVER INSTANCE TYPE SELECTION menu, choose [D] Done.
Continue with the section Assembling and Deploying Your ATG Applications.
