Creating the Endeca EAC Application via Scripts - Deployment Template

How to create the Endeca EAC application?

1. On the machine where Oracle Commerce Guided Search with Experience Manager is installed, create the directory where the EAC application will reside
   Example: /opt/app/endeca/apps 
   
   
2. Copy the <ATG11dir>/CommerceReferenceStore/Store/Storefront/deploy directory to a temporary location on the machine where Oracle Commerce Guided Search with Experience Manager is installed.
   Example: /opt/app/ATGtemp
   
   
3. Execute the deploy script. 
   Example:
   /opt/app/endeca/ToolsAndFrameworks/11.1.0/deployment_template/bin >./deploy.sh --app /opt/app/ATGtemp/deploy/deploy.xml
   
   
4. Press Enter to continue with the install
5. Enter the following information for the script prompts:
   • Enter N to install a base deployment.
     
     
   • Enter CRS for the name of the application.
     
     
   • Enter the full path to the Apps directory, 
     Example: /opt/app/endeca/apps 
   • Enter the EAC port (default is 8888)
     
     
   • Workbench port number [8006]
     
     
   • Dgraph1 (Live Dgraph) port (default is 15000)
     
     
   • Authoring Dgraph port (default is 15002)
     
     
   • LogServer port (default is 15010)
     
     
   • Enter the CAS install directory using UNIX-style forward slashes, even if on Windows. 
     Example:/opt/app/endeca/CAS/11.1.0
     
     
   • Enter the CAS version number (default is 11.1.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 (localhost)
     
     
   • Production application server host name. This is the host where the ATGProduction server will be running. [localhost]
     
     
   • Production application server HTTP port number. 
     IMPORTANT: If you are following the instructions in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere.
     
     
   • Preview host name [localhost]
     
     
   • Preview port number.
     
     
     If you are following the instructions in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere.
     
     
   • Context root of the preview application [crs]
     
     
   • Host name of the user segment server. This is the server that will respond to Experience Manager requests for Business Control Center user segment data. Oracle recommends using the Content Adminstration server (also called the ATGPublishing server in this guide). [localhost]
     
     
   • HTTP port of the user segment server.  
     IMPORTANT: If you are following the instructions in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere. 
     
     
   • Path for the Oracle Wallet jps-config.xml file
     Example:  /opt/app/endeca/ToolsAndFrameworks/11.1.0/server/workspace/credential_store/jps-config.xml
   • Application configuration archive path. This is the location where content promoted using the file-based method is stored,
     Example, /opt/app/endeca/apps/CRS/data/workbench/application_export_archive 
   You see a message that says “Application successfully deployed” when the deployment is finished. 
   
   
6. Change directories to the EAC applications directory, 
   Example: /opt/app/endeca/apps 
   The CRS application directory is added as child of the /apps directory.

How to provision the EAC application?

1. In a UNIX shell, change directories to your EAC application’s /control directory,
   Example: /opt/app/endeca/apps/CRS/control
   

2. Execute the initialize_services.sh script.
   ./initialize_services.sh