You can start the ACC in several ways, depending on whether you’re starting it locally in relation to your Nucleus-based application, or on a separate client.

Note: If you are using a UNIX variant, the shell from which you start the ACC must support X11 forwarding. Depending on your client, you may need to install X11 packages, or use Xming or equivalent tools.

Note: Due to a Java bug, if you are running Java 6, you cannot run the ACC in the same virtual machine as an IBM WebSphere application server. You can run the ACC in a dedicated VM, or install the following IBM iFix:

http://ww-01.ibm.com/support/docview.wss?uid=swg24027328

To connect to a Nucleus-based application from a client machine, you must use the client version of the ACC (see Installing the ATG Control Center on a Client Machine). Note that for a Nucleus-based application to accept connections from the ACC, all of the following must be true:

These settings are all part of the default configuration created by the Oracle Commerce Platform installer, so you generally do not need to configure them.

In addition, to enable the client version of the ACC to connect to an application, the application must include the DafEar.Admin module. This module is not included by default, so you must explicitly specify it when you assemble the application. See Including the Dynamo Server Admin in the Platform Programming Guide for more information.

JBoss In order to connect to your running Oracle Commerce Platform application from any remote location (that is, not using localhost), you must start your JBoss server using the –b option. For example:

standalone.bat --server-config=ATGProduction.xml -b 0.0.0.0

See your JBoss documentation for information on this and other settings.