In this section, you use CIM to create the EAC application that supports Commerce Reference Store. Note that this section assumes that you are installing the Oracle Commerce Platform and Oracle Commerce Guided Search with Experience Manager on the same machine. In this case, CIM can be used to create the EAC application.
If the Oracle Commerce Platform and Oracle Commerce Guided Search with Experience Manager are installed on different machines, you must create the EAC application via a script. Note that Guided Search with Experience Manager does not support the AIX operating system; therefore, if you are installing the Oracle Commerce Platform on AIX, you must install Guided Search with Experience Manager on a separate Linux, Windows, or Solaris machine and use a script to create the EAC application. See Appendix A: Creating the EAC Application via Scripts for detailed instructions. After creating the EAC application, continue with the Assembling and Deploying Your Oracle Commerce Applications in this guide.
To create the EAC application:
In a new UNIX shell or command prompt, create the directory where the EAC 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 EAC Application – OPTIONAL.
Select [A] EAC App Configuration without Experience Manager Preview.
Enter the following information. Defaults are provided in brackets.
CRS EAC App Name [CRS]
CRS EAC 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, for example,
/usr/local/endeca/CAS/11.2.0orC:/Endeca/CAS/11.2.0IMPORTANT: Use forward slashes for this path, even if on Windows.
CAS Version [11.2.0]
Language Code [en]
Fully-qualified Workbench Hostname, Including Domain [localhost]
Workbench Port Number [8006]
Production application server host name [localhost]. This is the host name of the server that hosts the Oracle Commerce application. Enter the
ATGProductionserver host name.Production application server HTTP port number. If you used the ports suggested in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere.
Host name of the user segment server. This is the server that will respond to Workbench requests for Busines Control Center user segment data. Oracle recommends using the Content Adminstration server (also called the Publishing server in this guide) for this purpose. Enter the host name of the
ATGPublishingserver. [localhost]HTTP port of the user segment server. If you used the ports suggested in this guide, these values are 7103 for WebLogic, 8180 for JBoss and Tomcat, and 9181 for WebSphere.
Path for the Oracle Wallet
jps-config.xmlfile, for example,/usr/local/endeca/ToolsAndFrameworks/11.2.0/server/workspace/credential_store/jps-config.xmlorC:/Endeca/ToolsAndFrameworks/11.2.0/server/workspace/credential_store/jps-config.xmlIMPORTANT: Use forward slashes for this path, even if on Windows.
Application configuration archive path. This is the path for the live ZIP files created by the EAC application during application export, for example,
/usr/local/endeca/Apps/application_export_archiveorC:/Endeca/Apps/application_export_archive. The EAC application will have a sub-directory in the location provided here, where its ZIP files reside.IMPORTANT: Use forward slashes for this path, even if on Windows.
If you have a split install, where Oracle Commerce Guided Search with Experience Manager and the Oracle Commerce Platform are installed on different machines, you must specify the shared directory you created in the Creating a Shared Archive Directory section, for example,
/usr/local/application_export_archiveorC:/application_export_archive.Authoring application configuration archive path. This is the path for the authoring ZIP files created by the EAC application during application export, for example,
/usr/local/endeca/Apps/application_export_archiveorC:/Endeca/Apps/application_export_archive. The EAC application will have a sub-directory in the location provided here, where its ZIP files reside.IMPORTANT: Use forward slashes for this path, even if on Windows.
If you have a split install, where Oracle Commerce Guided Search with Experience Manager and the Oracle Commerce Platform are installed on different machines, you must specify the shared directory you created in the Creating a Shared Archive Directory section, for example,
/usr/local/application_export_archiveorC:/application_export_archive.Path to the ToolsAndFrameworks directory, for example,
/usr/local/endeca/ToolsAndFrameworks/11.2.0orC:\Endeca\ToolsAndFrameworks\11.2.0Path to the MDEX directory including the version number, for example,
/usr/local/endeca/MDEX/6.5.1orC:\Endeca\MDEX\6.5.2Path to the Platform Services directory including the version number, for example,
/usr/local/endeca/PlatformServices/11.2.0orC:\Endeca\PlatformServices\11.2.0
Select [D] Deploy to deploy the EAC application.
In the INITIALIZE CRS EAC 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 Oracle Commerce Applications.
