Set up your localconfig and server configuration files under <ATG11dir>/home/servers and <ATG11dir>/home/localconfig to configure the default and server specific behaviors of your Nucleus-based application. These files are included in your EAR when it is generated.
Using either the Configuration and Installation Manager (CIM) or the
makeDynamoServerscript, create one Oracle Commerce Platform server configuration for each application server.Configure the Oracle Commerce Platform lock manager server to run the
ServerLockManager. (See Enabling the Repository Cache Lock Managers earlier in this chapter for more information.)Configure the Scenario Manager to run the workflow and process editor servers. There should be exactly one instance of your Oracle Commerce Platform application running each of these components, and all other instances should be aware of them. (See the Personalization Programming Guide for more information.)
Note: The JNDI lookup for your data source must be prefixed with java:comp/env/. For example, if your data source has a JNDI name ATGDB, the JNDIName property of the JTDataSource should be java:/comp/env/ATGDB. Set your transaction manager to use your application server’s implementation. See the Creating Data Sources section for additional JNDI naming constraints.
