Configuring Your Oracle Commerce Platform Server Instances

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

To configure your Oracle Commerce Platform server instances:

  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 most cases, you can accept the defaults, which are provided in brackets below. The exception is the EAC base application name. Change this setting from ATG to CRS.

  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. (WebSphere Only) Perform these steps for WebSphere environments only:

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

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

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

    WebSphere Default

    HTTP Port

    7103

    8180

    9181

    HTTPS Port

    7104

    8543

    9544

    Site HTTP Port

    7103

    8180

    9181

    RMI Port

    8861

    8861

    8861

    DRP Port

    8851

    8851

    8851

    File Deployment Port

    8811

    8811

    8811

    File Synchronization Deploy Server Port

    8816

    8816

    8816

    Lock Server Port

    9010

    9010

    9010

    Note: By default the Sun T1000 and T2000 systems run a server that uses port 9010. ATG’s lock management components also use this port. If you are using lock management on one of these systems, you must either disable the Sun server or use a different lock server port while configuring your server instance. See the Sun T1000 and T2000 Requirements in the Platform Installation and Configuration Guide for detailed instructions.

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

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

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

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

  17. Enter the following information for your production server instance. Note that the defaults have been updated based on the information you provided for the publishing server so, for most settings, you should be able to accept the default values.

    • CAS host name [localhost]

    • CAS port [8500]

    • EAC host name [localhost]

    • EAC port [8888]

    • EAC base application name. Accept the CRS default.

    • Fully-qualified Workbench host name, including domain

    • Workbench port [8006]

    • Default MDEX host name [localhost]

    • Default MDEX port number [15000]

    • Application configuration archive path. This is the location where content promoted using the file-based method is stored, for example, /usr/local/endeca/Apps/CRS/data/workbench/application_export_archive/CRS or C:/Endeca/Apps/CRS/data/workbench/application_export_archive/CRS. IMPORTANT: 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 a CRS directory in the shared directory you created in the Creating a Shared Archive Directory section, for example, /usr/local/application_export_archive/CRS or C:\application_export_archive/CRS.

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

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

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

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

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

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

    WebSphere Default

    HTTP Port

    7003

    8080

    9081

    HTTPS Port

    7004

    8443

    9444

    Site HTTP Port

    7003

    8080

    9081

    RMI Port

    8860

    8860

    8860

    DRP Port

    8850

    8850

    8850

    File Deployment Port

    8810

    8810

    8810

    Lock Server Port

    9012

    9012

    9012

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

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

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

  27. Continue with the section Creating the EAC Application.

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