Appendix A: Creating EAC Applications via Script

This appendix provides instructions for creating the EAC applications that supports Commerce Store Accelerator using scripts instead of CIM. If the Oracle Commerce Platform and Oracle Commerce Guided Search with Experience Manager are installed on different servers, you must create and provision the EAC applications using the scripts described below. After creating the EAC applications, return to the Assembling and Deploying Your Oracle Commerce Applications section earlier in this guide to finish configuring your environment.

For the staging and production server instances, you must create the EAC applications that support them. Each server has three supporting EAC applications, one each for English, Spanish, and German. For the production server, you will create three EAC applications with these names:

  • CSAen

  • CSAes

  • CSAde

For the staging server, you will create three EAC applications with these names:

  • CSAStagingen

  • CSAStaginges

  • CSAStagingde

The EAC applications that support the staging server are configured to use Experience Manager Preview, while the EAC applications that support the production server do not.

To create the EAC applications:

  1. On the machine where Oracle Commerce Guided Search with Experience Manager is installed, create the directory where the EAC application will reside, for example, /usr/local/endeca/Apps or C:\Endeca\Apps.

  2. If you have not already done so, copy the <ATG11dir>/CommerceAccelerator/Applications/B2CStore/src/main/deploy directory to a temporary location on the machine where Oracle Commerce Guided Search with Experience Manager is installed. This directory has three sub-directories, one each for CSAen, CSAes, and CSAde, and each directory contains a deploy.xml file. You use the same deploy.xml for both the CSA<language> and CSAStaging<language> EAC applications. For example, you use the CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAen/deploy.xml for both the CSAen and CSAStagingen applications.

  3. On the machine where Oracle Commerce Guided Search with Experience Manager is installed, open a UNIX shell or command prompt and browse to the ToolsAndFrameworks /deployment_template/bin directory, for example, /usr/local/endeca/ToolsAndFrameworks/11.2.0/deployment_template/bin or C:\Endeca\ToolsAndFrameworks\11.2.0\deployment_template\bin.

  4. Execute the deploy script for the CSAen EAC application. For example, on UNIX, enter:

    ./deploy.sh --app CSA-temporary-directory/deploy/CSAen/deploy.xml

    On Windows, enter:

    deploy.bat --app CSA-temporary-directory\deploy\CSAen\deploy.xml

  5. After the note about the Platform Services version, press Enter to continue with the deployment.

  6. Type N to install a base deployment.

  7. Enter the following information for the CSAen EAC application using the values supplied in the table below. Be careful to enter the CSAen values for this EAC application’s configuration.

    Prompt

    Value

    CSA EAC application name

    CSAen: CSAen

    CSAes: CSAes

    CSAde: CSAde

    CSAStagingen: CSAStagingen

    CSAStaginges: CSAStaginges

    CSAStaginde: CSAStagingde

    CSA EAC application deployment path

    The location where the CSA EAC Applications will be deployed, for example:

    UNIX:
    /usr/local/endeca/Apps

    Windows:
    C:\Endeca\Apps

    EAC port number

    8888

    Workbench port number

    8006

    Live Dgraph port number

    You must specify a unique live Dgraph port number for each EAC application.

    CSAen: 15000

    CSAes: 16000

    CSAde: 17000

    CSAStagingen: 18000

    CSAStaginges: 19000

    CSAStagingde: 20000

    Authoring Dgraph port number

    You must specify a unique authoring Dgraph port number for each EAC application.

    CSAen: 15002

    CSAes: 16002

    CSAde: 17002

    CSAStagingen: 18002

    CSAStaginges: 19002

    CSAStagingde: 20002

    Log Server port number

    You must specify a unique log server port number for each EAC application.

    CSAen: 15010

    CSAes: 16010

    CSAde: 17010

    CSAStagingen: 18010

    CSAStaginges: 19010

    CSAStagingde: 20010

    CAS path

    The path to the CAS installation, including the version number.

    IMPORTANT: Use forward slashes for this path, even on Windows, for example:

    UNIX:
    /usr/local/endeca/CAS/11.2.0

    Windows:
    C:/Endeca/CAS/11.2.0

    CAS port number

    8500

    Server name for the Oracle Commerce application

    The name of the server where the CSA application is hosted.

    CSAen, CSAes, CSAde Because you are defining the production EAC applications, enter the host name of the ATGProduction server.

    CSAStagingen, CSAStaginges, CSAStagingde Because you are defining the staging EAC applications, enter the host name of the ATGStaging server.

    HTTP port for the Oracle Commerce application

    CSAen, CSAes, CSAde: The HTTP port of the ATGProduction server. For example, 7003 on WebLogic or 8080 on Jboss.

    CSAStagingen, CSAStaginges, CSAStagingde: The HTTP port of the ATGStaging server. For example, 7203 on WebLogic or 8280 on Jboss.

    Server name for the Experience Manager preview application

    CSAen, CSAes, CSAde The production EAC applications do not use Experience Manager preview, so you can provide a dummy value for this prompt.

    CSAStagingen, CSAStaginges, CSAStagingde: The server name of the ATGStaging server.

    HTTP port for the Experience Manager preview application

    CSAen, CSAes, CSAde The production EAC applications do not use Experience Manager preview, so you can provide a dummy value for this prompt.

    CSAStagingen, CSAStaginges, CSAStagingde: The HTTP port of the ATGStaging server. For example, 7203 on WebLogic or 8280 on Jboss.

    Context root for the Experience Manager preview application

    CSAen, CSAes, CSAde The production EAC applications do not use Experience Manager preview, so you can provide a dummy value for this prompt.

    CSAStagingen, CSAStaginges, CSAStagingde: csa

    User segment server host name

    Oracle recommends using the ATGPublishing server as the user segment server. Therefore, this value should be the host name of the ATGPublishing server.

    User segment server HTTP port number

    The HTTP port of the ATGPublishing server. For example, 7103 on Weblogic or 8180 on Jboss.

    Oracle Wallet jps-config.xml file path

    The location of the Oracle Wallet file that stores secure credentials.

    IMPORTANT: Use forward slashes for this path, even on Windows, for example:

    UNIX:
    /usr/local/endeca/ToolsAndFrameworks/11.2.0/server/workspace/credential_store/jps-config.xml

    Windows:
    C:/Endeca/ToolsAndFrameworks/11.2.0/server/workspace/credential_store/jps-config.xml

    Application configuration archives export directory

    The path for the live ZIP files created by the EAC applications during application export. Oracle recommends that all of the EAC applications place their ZIP files into the same export directory. Each EAC application will have a sub-directory in the location provided here, where its ZIP files will reside. Because this is a split install, you must specify the path of the shared directory you created in the Creating a Shared Archive Directory section.

    IMPORTANT: Use forward slashes for this path, even on Windows, for example:

    UNIX:
    /usr/local/application_export_archive

    Windows:
    C:/application_export_archive

    Authoring application configuration archives export directory

    The path for the authoring ZIP files created by the EAC applications during application export. Oracle recommends that all of the EAC applications place their ZIP files into the same export directory. Each EAC application will have a sub-directory in the location provided here, where its ZIP files will reside. Because this is a split install, you must specify the path of the shared directory you created in the Creating a Shared Archive Directory section.

    IMPORTANT: Use forward slashes for this path, even on Windows, for example:

    UNIX:
    /usr/local/application_export_archive

    Windows:
    C:/application_export_archive

    You see a message that says “Application successfully deployed” when the deployment is finished.

  8. In a UNIX shell or command prompt, change directories to the EAC applications directory, for example, /usr/local/endeca/Apps or C:\endeca\Apps. Note that the CSAen application directory is added as child of the /Apps directory.

  9. Repeat these steps to create EAC applications for CSAes, CSAde, CSAStagingen, CSAStaginges, and CSAStagingde. Remember that, because the EAC applications are intended to be identical on the production and staging servers, the same deployment templates are used to create the staging EAC applications and the production EAC applications. In other words, use:

    • /deploy/CSAen/deploy.xml for the CSAStagingen application

    • /deploy/CSAes/deploy.xml for the CSAStaginges application

    • /deploy/CSAde/deploy.xml for the CSAStagingde application

To provision the EAC applications:

  1. In a UNIX shell or command prompt, change directories to your EAC application’s /control directory, for example, /usr/local/endeca/Apps/EAC-application-name/control or C:\Endeca\Apps\EAC-application-name\control.

  2. Execute the initialize_services.sh script. For example, on UNIX, enter:

    ./initialize_services.sh

    On Windows, enter:

    initialize_services.bat

  3. Repeat these steps for all of your EAC applications.

  4. Return to the Assembling and Deploying Your Oracle Commerce Applications section earlier in this guide to finish configuring your environment.

Copyright © 1997, 2016 Oracle and/or its affiliates. All rights reserved. Legal Notices