Configuring Your Oracle Commerce Platform Server Instances and Creating the EAC Applications

In this section, you configure the publishing, staging, and production Oracle Commerce Platform server instances.

For the staging and production server instances, you will also 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:

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

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.

Note: 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 applications. If the Oracle Commerce Platform and Oracle Commerce Guided Search with Experience Manager are installed on different machines, you must create the EAC applications via a script. Follow the instructions in this section carefully to create the Oracle Commerce server instances only. Then see Appendix A: Creating EAC Applications via Script for detailed instructions on creating the EAC applications. After creating the EAC applications, continue with the Assembling and Deploying Your Oracle Commerce Applications in this guide.

To create the EAC application deployment directory:

  1. In a new UNIX shell or command prompt, create the directory where the EAC applications will be deployed, for example, /usr/local/endeca/Apps or C:\Endeca\Apps.

To configure the publishing server instance:

  1. In the CIM MAIN MENU, select [3] Server Instance Configuration.

  2. In the SERVER INSTANCE TYPE SELECTION menu, select [P] Publishing Server - 0 Instances Configured.

  3. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [P] Publishing Server General Configuration - REQUIRED.

  4. Enter the following information for your publishing server instance. In some cases, you can accept the defaults; however, if the default ports conflict for your environment, you will have to supply alternatives. Also, a number of the prompts reference the EAC applications, their MDEX instances, hosts, and ports. Oracle recommends that both the Publishing and Staging server instances reference the CSAStaging<locale> EAC applications. The values recommended below correspond to the values you will set when you create the CSAStaging<locale> EAC applications later in this guide.

    Prompt [default]

    Recommended Value/Default

    Production Lock Server host name

    The host name of the ATGProduction server.

    Production Lock Server port

    9012

    CAS host name

    The host name of the server where CAS is running.

    CAS port

    8500

    EAC host name

    The host name of the Workbench server where the EAC applications are running.

    EAC port

    8888

    EAC base application name

    CSAStaging

    Fully-qualified Workbench host name, including domain

    The host name of the server where the Workbench is running, including the domain.

    Workbench port

    8006

    Mapping between the EAC application key and the MDEX host:port that is used when that key is passed in the request

    The value for this prompt should reference the authoring MDEX instances for the CSAStagingen, CSAStaginges, and CSAStagingde EAC applications. To create the mapping using the ports recommended in this guide, use the following, replacing localhost as necessary:
    en=localhost:18002,es=localhost:19002,de=localhost:20002

    Default MDEX host name

    The host name of the server where the CSAStagingen authoring MDEX will be running.

    Default MDEX port number

    18002, which is the HTTP port for the CSAStagingen authoring MDEX.

    Path for 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.

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

    UNIX:
    /usr/local/endeca/Apps/application_export_archive

    Windows:
    C:/Endeca/Apps/application_export_archive

    Local Preview hostname

    The host name of the server where Business Control Center Preview will run. In this guide, you are instructed to use the Publishing server to host Business Control Center Preview, therefore this value should be the host name of your ATGPublishing server instance (note that the Publishing server is also referrred to as the Content Administration server).

    Local Preview host port

    The HTTP port of the ATGPublishing server.

    Weblogic:
    7103

    Jboss:
    8180

    Application configuration archive path for the default EAC application

    The application configuration archive path is the location where EAC application content promoted using the file-based method is stored. For this prompt, enter the path for the CSAStagingen EAC application.

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

    UNIX: /usr/local/endeca/Apps/application_export_archive/CSAStagingen

    Windows:
    C:/Endeca/Apps/application_export_archive/CSAStagingen

  5. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [I] Instance Management – REQUIRED.

  6. In the INSTANCE MANAGEMENT menu, select [A] Add Server Instance.

  7. In the Select Type of Server Instance To Create menu, select [1] Publishing with a Server Lock Manager: Minimum 1 Required.

  8. In the NAME FOR NEW SERVER INSTANCE menu, enter ATGPublishing for the Server Instance Name.

  9. (WebLogic Only) Perform these steps for WebLogic environments only:

    • In the WEBLOGIC ONLINE PORT BINDING menu, select [C] Choose Custom Port Binding.

    • In the CHOOSE CUSTOM WEBLOGIC ONLINE PORT BINDING menu, select [2] ports-01: http port is 7103.

  10. (JBoss Only) Perform these steps for JBoss environments only:

    • In the JBOSS PORT BINDING menu, select [C] Choose Custom Port Binding.

    • In the CHOOSE CUSTOM JBOSS PORT BINDING menu, select [2] ports-01: http port is 8180.

  11. Enter the following ports. The defaults CIM provides for each application server are listed in the table below. You can leave the defaults as is unless they cause port conflicts on your machine.

    Port Type

    WebLogic Default

    JBoss Default

    HTTP Port

    7103

    8180

    HTTPS Port

    7104

    8543

    Site HTTP Port

    7103

    8180

    RMI Port

    8861

    8861

    DRP Port

    8851

    8851

    File Deployment Port

    8811

    8811

    File Synchronization Deploy Server Port

    8816

    8816

    Lock Server Port

    9010

    9010

  12. In the INSTANCE MANAGEMENT menu, select [D] Done.

  13. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [O] Configure Another Server Instance Type.

To configure the production server instance:

  1. In the SERVER INSTANCE TYPE SELECTION menu, select [S] Production Server - 0 Instances Configured.

  2. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [P] Commerce Production Server General Configuration - REQUIRED.

  3. Enter the following information for your production server instance. In some cases, you can accept the defaults; however, if the default ports conflict for your environment, you will have to supply alternatives. Also, a number of the prompts reference the EAC applications, their MDEX instances, hosts, and ports. Oracle recommends that the Production server instance references the CSA<locale> EAC applications. The values recommended below correspond to the values you will set when you create the CSA<locale> EAC applications later in this guide.

    Prompt [default]

    Recommended Value/Default

    CAS host name

    The host name of the server where CAS is running.

    CAS port

    8500

    EAC host name

    The host name of the Workbench server where the EAC appliations are running.

    EAC port

    8888

    EAC base application name

    CSA

    Fully-qualified Workbench host name, including domain

    The host name of the server where the Workbench is running, including the domain.

    Workbench port

    8006

    Mapping between the EAC application key and the MDEX host:port that is used when that key is passed in the request

    The value for this prompt should reference the live MDEX instances for the CSAen, CSAes, and CSAde EAC applications. To create the mapping using the ports recommended in this guide, use the following, replacing localhost as necessary:
    en=localhost:15000,es=localhost:16000,de=localhost:17000

    Default MDEX host name

    The host name of the server where the CSAen live MDEX will be running.

    Default MDEX port number

    15000, which is the HTTP port for the CSAen live MDEX.

    Path for 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.

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

    UNIX:
    /usr/local/endeca/Apps/application_export_archive

    Windows:
    C:/Endeca/Apps/application_export_archive

    Application configuration archive path for the default EAC application

    The application configuration archive path is the location where EAC application content promoted using the file-based method is stored. For this prompt, enter the path for the CSAen EAC application.

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

    UNIX: /usr/local/endeca/Apps/application_export_archive/CSAen

    Windows:
    C:/Endeca/Apps/application_export_archive/CSAen

  4. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [I] Instance Management – REQUIRED.

  5. In the INSTANCE MANAGEMENT menu, select [A] Add Server Instance.

  6. In the Select Type of Server Instance To Create menu, select [1] Production with a Server Lock Manager: Minimum 1 Required.

  7. In the NAME FOR NEW SERVER INSTANCE menu, enter ATGProduction for the Server Instance Name.

  8. In the <Application_Server> ONLINE PORT BINDING menu, select [U] Use Default Port Binding.

  9. Enter the following ports. The defaults CIM provides for each application server are listed in the table below. You can leave the defaults as is unless they cause port conflicts on your machine.

    Port Type

    WebLogic Default

    JBoss Default

    HTTP Port

    7003

    8080

    HTTPS Port

    7004

    8443

    Site HTTP Port

    7003

    8080

    RMI Port

    8860

    8860

    DRP Port

    8850

    8850

    File Deployment Port

    8810

    8810

    Lock Server Port

    9012

    9012

  10. In the INSTANCE MANAGEMENT menu, select [D] Done.

Note: Skip the next procedure if you need to create your EAC applications via script. Instead, in the SERVER INSTANCE TYPE CONFIGURATION menu, select [O] Configure Another Server Instance Type and continue with the instructions for creating the staging server instance.

To create the production server instance’s EAC applications:

  1. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [D] Deploy CSA EAC Application - OPTIONAL.

  2. In the EAC APPLICATION DEPLOYMENT TYPE menu, select [A] EAC Application Configuration without Experience Manager Preview.

  3. 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

    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

    Dgraph port number

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

    CSAen: 15000

    CSAes: 16000

    CSAde: 17000

    Authoring Dgraph port number

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

    CSAen: 15002

    CSAes: 16002

    CSAde: 17002

    Log Server port number

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

    CSAen: 15010

    CSAes: 16010

    CSAde: 17010

    CAS port number

    8500

    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

    Workbench port number

    8006

    Server name for the Oracle Commerce application

    The name of the server where the CSA application is hosted. Because you are defining the production EAC applications, enter the host name of the ATGProduction server.

    HTTP port for the Oracle Commerce application

    The HTTP port of the ATGProduction server.

    Weblogic:
    7003

    Jboss:
    8080

    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.

    Weblogic:
    7103

    Jboss:
    8180

    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.

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

    UNIX:
    /usr/local/endeca/Apps/application_export_archive

    Windows:
    C:/Endeca/Apps/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.

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

    UNIX:
    /usr/local/endeca/Apps/application_export_archive

    Windows:
    C:/Endeca/Apps/application_export_archive

    deploy.xml file path

    The location of the deployment template for each EAC application. Note that the deployment templates are language and EAC-application specific.

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

    CSAen:

    /usr/local/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAen/deploy.xml

    OR

    C:/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAen/deploy.xml

    CSAes: / /usr/local/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAes/deploy.xml

    OR

    C:/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAes/deploy.xml

    CSAde:

    /usr/local/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAde/deploy.xml

    OR

    C:/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAde/deploy.xml

    ToolsAndFrameworks directory

    The location of the ToolsAndFrameworks directory, including the version number. For example:

    UNIX:
    /usr/local/endeca/ToolsAndFrameworks/11.2.0

    Windows:
    C:\Endeca\ToolsAndFrameworks\11.2.0

    MDEX directory

    The location of the MDEX directory, including the version number. For example:

    UNIX:
    /usr/local/endeca/MDEX/6.5.2

    Windows:
    C:\Endeca\MDEX\6.5.2

    Platform Services directory

    The location of the PlatformServices directory, including the version number. For example:

    UNIX:
    /usr/local/endeca/PlatformServices/11.2.0

    Windows:
    C:\Endeca\PlatformServices\11.2.0

  4. Select [D] Deploy to deploy the English EAC application.

  5. In the INITIALIZE CSA EAC APP menu, choose [I] Initialize. After the initializing is done, you are returned to the SERVER INSTANCE TYPE CONFIGURATION menu.

    Note: The initialize command as executed by CIM does not use the --force option. For this reason, if you have already initialized an EAC application through CIM but need to make changes to it, you can use CIM to configure the application again but you must use the initialize_services command described in Appendix A: Creating EAC Applications via Script along with the --force option to do the initialization.

  6. Repeat steps 1 to 5 two more times to create the CSAes and CSAde EAC applications for the production server instance. Most of the prompts are the same for the all three EAC applications and the table marks values that are language-specific. Be sure to use the Spanish values for the Spanish EAC application and the German values for the German EAC application.

  7. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [O] Configure Another Server Instance Type. Continue with the next section to configure the staging server instance.

To configure the staging server instance:

  1. In the SERVER INSTANCE TYPE SELECTION menu, select [T] Staging Server - 0 Instances Configured.

  2. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [S] Staging Server General Configuration - REQUIRED.

  3. Enter the following information for your staging server instance. In some cases, you can accept the defaults, however, if the default ports conflict for your environment, you will have to supply alternatives. Also, a number of the prompts reference the EAC applications, their MDEX instances, hosts, and ports. Oracle recommends that both the Publishing and Staging server instances reference the CSAStaging<locale> EAC applications. The values recommended below correspond to the values you will set when you create the CSAStaging<locale> EAC applications later in this guide.

    Prompt [default]

    Recommended Value/Default

    Production Lock Server host name

    The host name of the ATGProduction server.

    Production Lock Server port

    9012

    CAS host name

    The host name of the server where CAS is running.

    CAS port

    8500

    EAC host name

    The host name of the Workbench server where the EAC appliations are running. [localhost]

    EAC port

    8888

    EAC base application name

    CSAStaging

    Fully-qualified Workbench host name, including domain

    The host name of the server where the Workbench is running, including the domain.

    Workbench port

    8006

    Mapping between the EAC application key and the MDEX host:port that is used when that key is passed in the request

    The value for this prompt should reference the authoring MDEX instances for the CSAStagingen, CSAStaginges, and CSAStagingde EAC applications. To create the mapping using the ports recommended in this guide, use the following, replacing localhost as necessary:
    en=localhost:18002,es=localhost:19002,de=localhost:20002

    Default MDEX host name

    The host name of the server where the CSAStagingen authoring MDEX will be running.

    Default MDEX port number

    18002, which is the HTTP port for the CSAStagingen authoring MDEX.

    Path for 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.

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

    UNIX:
    /usr/local/endeca/Apps/application_export_archive

    Windows:
    C:/Endeca/Apps/application_export_archive

    Application configuration archive path for the default EAC application

    The application configuration archive path is the location where EAC application content promoted using the file-based method is stored. For this prompt, enter the path for the CSAStagingen EAC application.

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

    UNIX:
    /usr/local/endeca/Apps/application_export_archive/CSAStagingen

    Windows:
    C:/Endeca/Apps/application_export_archive/CSAStagingen

  4. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [I] Instance Management – REQUIRED.

  5. In the INSTANCE MANAGEMENT menu, select [A] Add Server Instance.

  6. In the NAME FOR NEW SERVER INSTANCE menu, enter ATGStaging for the service instance name.

  7. (WebLogic Only) Perform these steps for WebLogic environments only:

    • In the WEBLOGIC ONLINE PORT BINDING menu, select [C] Choose Custom Port Binding.

    • In the CHOOSE CUSTOM WEBLOGIC ONLINE PORT BINDING menu, select [3] ports-02: http port is 7203.

  8. (JBoss Only) Perform these steps for JBoss environments only:

    • In the JBOSS PORT BINDING menu, select [C] Choose Custom Port Binding.

    • In the CHOOSE CUSTOM JBOSS PORT BINDING menu, select [3] ports-02: http port is 8280.

  9. Enter the following ports. The defaults CIM provides for each application server are listed in the table below. You can leave the defaults as is unless they cause port conflicts on your machine.

    Port Type

    WebLogic Default

    JBoss Default

    HTTP Port

    7203

    8280

    HTTPS Port

    7204

    8643

    Site HTTP Port

    7203

    8280

    RMI Port

    8862

    8862

    DRP Port

    8852

    8852

    File Deployment Port

    8812

    8812

  10. In the INSTANCE MANAGEMENT menu, select [D] Done.

Note: Skip the next procedure if you need to create your EAC applications via script. Instead, select [O] Configure Another Server Instance Type, then select [D] Done to return to the CIM MAIN MENU. Next, go create the EAC applications as described in Appendix A: Creating EAC Applications via Script. After you have created the EAC applications, go to the Assembling and Deploying Your Oracle Commerce Applications to finish the configuration work in CIM.

To create the staging server instance’s EAC applications:

  1. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [D] Deploy CSA EAC Application.

  2. In the EAC APPLICATION DEPLOYMENT TYPE menu, select [E] EAC Application Configuration with Experience Manager Preview.

  3. Enter the following information for the CSAStagingen EAC application.

    Prompt

    Value

    CSA EAC application name

    CSAStagingen: CSAStagingen

    CSAStaginges: CSAStaginges

    CSAStagingde: 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

    Dgraph port number

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

    CSAStagingen: 18000

    CSAStaginges: 19000

    CSAStagingde: 20000

    Authoring Dgraph port number

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

    CSAStagingen: 18002

    CSAStaginges: 19002

    CSAStagingde: 20002

    Log Server port number

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

    CSAStagingen: 18010

    CSAStaginges: 19010

    CSAStagingde: 20010

    CAS port number

    8500

    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

    Workbench port number

    8006

    Server name for the Oracle Commerce application

    The name of the server where the CSA application is hosted. Because you are defining the staging EAC applications, enter the host name of the ATGStaging server.

    HTTP port for the Oracle Commerce application

    The HTTP port of the ATGStaging server.

    Weblogic:
    7203

    Jboss:
    8280

    Host for the Experience Manager preview application

    The name of the server that is hosting the application that Endeca Preview should reference for preview content. Enter the name of the ATGStaging server for this prompt.

    HTTP port for the Experience Manager preview application

    The HTTP port of the ATGStaging server.

    Weblogic:
    7203

    Jboss:
    8280

    Context root for the Endeca preview application

    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. [localhost]

    User segment server HTTP port number

    The HTTP port of the ATGPublishing server.

    Weblogic:
    7103

    Jboss:
    8180

    Oracle Wallet jps-config.xml file path

    The location of the Oracle Wallet file that stores secure credentials, 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.

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

    UNIX:
    /usr/local/endeca/Apps/application_export_archive

    Windows:
    C:/Endeca/Apps/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.

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

    UNIX:
    /usr/local/endeca/Apps/application_export_archive

    Windows:
    C:/Endeca/Apps/application_export_archive

    deploy.xml file path

    The location of the deployment template for each EAC application. 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. Note that the deployment templates are language and EAC-application specific.

    IMPORTANT: Use forward style slashes, even on Windows, for example:

    CSAStagingen:

    /usr/local/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAen/deploy.xml

    OR

    C:/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAen/deploy.xml

    CSAStaginges:

    /usr/local/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAes/deploy.xml

    OR

    C:/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAes/deploy.xml

    CSAStagingde:

    /usr/local/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAde/deploy.xml

    OR

    C:/ATG/ATG11.2/CommerceAccelerator/Applications/B2CStore/src/main/deploy/CSAde/deploy.xml

    ToolsAndFrameworks directory

    The location of the ToolsAndFrameworks directory, including the version number. For example:

    UNIX:
    /usr/local/endeca/ToolsAndFrameworks/11.2.0

    Windows:
    C:\Endeca\ToolsAndFrameworks\11.2.0

    MDEX directory

    The location of the MDEX directory, including the version number. For example:

    UNIX:
    /usr/local/endeca/MDEX/6.5.2

    Windows:
    C:\Endeca\MDEX\6.5.2

    Platform Services directory

    The location of the PlatformServices directory, including the version number. For example:

    UNIX:
    /usr/local/endeca/PlatformServices/11.2.0

    Windows:
    C:\Endeca\PlatformServices\11.2.0

  4. Select [D] Deploy to deploy the English EAC application.

  5. In the INITIALIZE CSA EAC APP menu, choose [I] Initialize. After the initializing is done, you are returned to the SERVER INSTANCE TYPE CONFIGURATION menu.

  6. Repeat steps 1 to 5 two more times to create the Spanish and German EAC applications for the staging server instance. Most of the prompts are the same for the all three EAC applications and the table marks values that are language-specific. Be sure to use the Spanish values for the Spanish EAC application and the German values for the German EAC application.

  7. In the SERVER INSTANCE TYPE CONFIGURATION menu, select [O] Configure Another Server Instance Type.

  8. In the SERVER INSTANCE TYPE SELECTION menu, select [D] Done.

  9. Continue with the section Assembling and Deploying Your Oracle Commerce Applications.

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