In this section, you configure publishing and production ATG server instances. If your configuration does not include ATG Search, skip the steps marked (Search Only) below.
To configure your ATG server instances:
In the CIM MAIN MENU menu, select [2] Server Instance Configuration.
In the SERVER INSTANCE TYPE SELECTION menu, select [A] ATG Commerce Store Publishing - 0 Instances Configured.
In the SERVER INSTANCE TYPE CONFIGURATION menu, select [A] ATG Commerce Store Publishing General Configuration – REQUIRED.
Enter the following information (defaults are provided in brackets):
Production Lock Server host name
Production Lock Server port [9012]
(Search Only) Remote Production Search Instance host name
(Search Only) Remote Production Search Instance RMI port (default is 8860)
In the SERVER INSTANCE TYPE CONFIGURATION menu, select [I] Instance Management – REQUIRED.
In the INSTANCE MANAGEMENT menu, select [A] Add Server Instance.
In the Select Type of Server Instance To Create menu, select [1] ATG Commerce Store Publishing with Lock Server : Minimum 1 Required.
In the NAME FOR NEW SERVER INSTANCE menu, enter
ATGPublishing
for the Server Name Instance.(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.
Enter the following ports. The defaults CIM provides for each application server are listed in the table below. Defaults that must be changed are marked with an asterisk and a recommended port value is provided in parentheses. You can leave the other defaults as is unless they cause port conflicts on your machine.
Port Type
JBoss Default
WebLogic Default
WebSphere Default
HTTP Port
8180
7001* (7003)
9080* (9081)
HTTPS Port
8543
7002
9443* (9444)
RMI Port
8861
8860* (8861)
8860* (8861)
DRP Port
8851
8850* (8851)
8850* (8851)
File Deployment Port
8811
8810* (8811)
8810* (8811)
File Synchronization Deploy Server Port
8816
8815
8815
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 ATG Installation and Configuration Guide for detailed instructions.
In the INSTANCE MANAGEMENT menu, select [D] Done.
In the SERVER INSTANCE TYPE CONFIGURATION menu, select [O] Configure Another Server Instance Type.
In the SERVER INSTANCE TYPE SELECTION menu, select [C] ATG Commerce Store Production - 0 Instances Configured.
In the SERVER INSTANCE TYPE CONFIGURATION menu, select [A] ATG Commerce Store Production General Configuration – REQUIRED.
In the SERVER INSTANCE TYPE CONFIGURATION menu, select [I] Instance Management – REQUIRED.
In the INSTANCE MANAGEMENT menu, select [A] Add Server Instance.
In the Select Type of Server Instance To Create menu, select [1] ATG Commerce Store Production with Server Lock Manager.
In the NAME FOR NEW SERVER INSTANCE menu, enter
ATGProduction
for the Server Instance Name.(JBoss Only) In the JBOSS PORT BINDING menu, select [U] Use Default Port Binding.
Enter the following ports. The defaults CIM provides for each application server are listed in the table below. Defaults that must be changed are marked with an asterisk and a recommended port value is provided in parentheses. You can leave the other defaults as is unless they cause port conflicts on your machine.
Port Type
JBoss Default
WebLogic Default
WebSphere Default
HTTP Port
8080
7001* (7004)
9080* (9082)
HTTPS Port
8443
7002* (7005)
9443* (9445)
RMI Port
8860
8860
8860
DRP Port
8850
8850
8850
File Deployment Port
8810
8810
8810
Lock Server Port
9012
9012
9012
In the INSTANCE MANAGEMENT menu, select [D] Done.
In the SERVER INSTANCE TYPE CONFIGURATION menu, select [O] Configure Another Server Instance Type.
In the SERVER INSTANCE TYPE SELECTION menu, select [D] Done.
Continue with the section Assemble and Deploy Your ATG Applications.