This appendix provides instructions for creating the Endeca application that supports Commerce Reference Store using scripts instead of CIM. If Oracle ATG Web Commerce and Oracle Endeca Commerce are installed on different servers, you must create and provision the Endeca application using the scripts described below. After creating the Endeca application, return to the Assembling and Deploying Your ATG Applications section earlier in this guide to finish configuring your environment.
To create the Endeca application:
On the machine where Oracle Endeca Commerce is installed, create the directory where the Endeca application will reside, for example,
/usr/local/endeca/AppsorC:\Endeca\Apps.Copy the
<ATG11dir>/CommerceReferenceStore/Store/Storefront/deploydirectory to a temporary location on the machine where Oracle Endeca Commerce is installed.On the machine where Oracle Endeca Commerce is installed, open a UNIX shell or command prompt and browse to the ToolsAndFrameworks
/deployment_template/bindirectory, for example,/usr/local/endeca/ToolsAndFrameworks/11.0.0/deployment_template/binorC:\Endeca\ToolsAndFrameworks\11.0.0\deployment_template\bin.Execute the
deployscript. For example, on UNIX, enter:./deploy.sh --appCRS-temporary-directory/deploy/deploy.xmlOn Windows, enter:
deploy.bat --appCRS-temporary-directory\deploy\deploy.xmlAfter the note about the Platform Services version, press Enter to continue with the install.
Enter the following information for the script prompts:
Enter
Yto install a base deployment.Enter
CRSfor the name of the application.Enter the full path to the
Appsdirectory, for example:/usr/local/endeca/AppsorC:\Endeca\Apps.Enter the EAC port (default is 8888).
Note: The EAC port is used for all Endeca applications that have been deployed, so if you deploy more than one application, continue to use the same port number for all of them.
Enter the CAS install directory using UNIX-style forward slashes, even if on Windows. For example, /
usr/local/endeca/CAS/orC:/Endeca/CAS/11.0.0.Enter the CAS version number (default is
11.0.0).Enter the CAS hostname (default is
localhost).Enter the CAS port (default is 8500).
Enter the language code (default is
en).Enter the fully-qualified Workbench hostname.
Production application server host name. This is the host where the ATGProduction server will be running. [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. This is the host where the ATG preview server will be running. [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
ATGPublishingserver 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).
Oracle Endeca Workbench port number [8006]
Live Dgraph port (default is 15000).
Authoring Dgraph port (default is 15002)
LogServer port (default is 15010)
Path for the Oracle Wallet
jps-config.xmlfile, for example,/usr/local/endeca/ToolsAndFrameworks/11.0.0/server/workspace/credential_store/jps-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.
You see a message that says “Application successfully deployed” when the deployment is finished.
In a UNIX shell or command prompt, change directories to the Endeca applications directory, for example,
/usr/local/endeca/AppsorC:\endeca\Apps. TheCRSapplication directory is added as child of the/Appsdirectory.
Commerce Reference Store only requires one Endeca application, so at this point you can move onto provisioning the application, described below. Other environments may require additional Endeca applications (see the ATG-Endeca Integration Guide for guidance). If so, you should create additional Endeca applications for any other ATG server instances which you intend to index against, for example, Staging and Publishing servers. Be sure to enter unique ports for Live Dgraph, Authoring Dgraph, and LogServer for each additional application.
To provision the Endeca application:
In a UNIX shell or command prompt, change directories to your Endeca application’s
/controldirectory, for example,/usr/local/endeca/Apps/CRS/controlorC:\Endeca\Apps\CRS\control.Execute the
initialize_services.shscript. For example, on UNIX, enter:./initialize_services.shOn Windows, enter:
initialize_services.batReturn to the Assembling and Deploying Your ATG Applications section earlier in this guide to finish configuring your environment. (Note: If your environment has multiple Endeca applications, repeat these steps for any other Endeca applications you created.)
