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.

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 in the Installing the ATG Platform chapter for more information). Note that for a Nucleus-based application to accept connections from the ACC, all of the following must be true:

  • The application includes the DAS-UI module.

  • The rmiEnabled property of the /atg/dynamo/Configuration component is set to true.

  • The adminPort property of the /atg/dynamo/Configuration component is set to the listen port of your application server (for example, the JBoss default is 8080).

These settings are all part of the default configuration created by the ATG 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 Administration UI in the ATG Programming Guide for more information.

JBoss Note: In order to connect to your running ATG application from any remote location (that is, not using localhost), you must start your JBoss server using the –b option. For example, on Windows use the following command:

run.bat -b

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

loading table of contents...