The client version of the ATG Control Center or any other ATG client application is launched against the set of Oracle ATG Web Commerce modules in a development-mode EAR file running on a remote server.

The client launcher displays a dialog box that prompts for the hostname, port, username, and password. The hostname and port are used to resolve an RMI service on the server, which in turn provides the client with HTTP URLs for remote downloading of module and system resources. The username and password are used for basic HTTP authentication of the download.

The client then:

When this procedure completes successfully, the client-side module root is in effect a mirror of the server-side module root, but a selective one, covering only resources that were marked for downloading in the manifest. The client application is then launched within a custom class loader, using the same set of modules as on the server, but employing the ATG-Client-Class-Path and ATG-Client-Main-Class manifest attributes instead of ATG-Class-Path and Main-Class.