Suppose you want to set up a site consisting of an Administration Server, three servers that serve pages, one server that runs the ATG lock manager, and one server that runs the process editor server. Here’s an example of how you might do this:

  1. Start up WebLogic Server using the startWebLogic script. This starts up the WebLogic Administration Server (default name myserver, default port 7001).

  2. In the WebLogic Console, create servers named pageServer1, pageServer2, and pageServer3. Assign each server port number 7700. Assign a unique IP address to each server (i.e., an IP address used by no other server in the domain).

  3. Create a cluster named pageCluster. Put pageServer1, pageServer2, and pageServer3 into this cluster.

  4. Create servers named procedit and lockmgr. Assign each server the port number 7800. Assign each server a unique IP address.

  5. Create a cluster named serviceCluster. Put procedit and lockmgr into this cluster.

  6. Assign the two clusters different multicast addresses.

  7. Using either the Dynamo Administration UI or the makeDynamoServer script, create ATG servers named pageServer1, pageServer2, pageServer3, procedit, and lockmgr. (You do not need to give the ATG servers the same names as the WebLogic servers, but it is a good idea do so.)

  8. Configure the ATG lockmgr server to run the ATG ServerLockManager. (See Enabling the Repository Cache Lock Managers for more information.)

  9. Configure the ATG Scenario Manager to run the process editor server on the ATG procedit server. (See the ATG Personalization Programming Guide for more information.)

  10. Set up ATG session backup, as discussed in Enabling Session Backup.

  11. Assemble your application, deploy it on each server in both clusters, and configure each instance to use the ATG server corresponding to the WebLogic server the instance is running on. (This process is discussed in Assembling for a WebLogic Cluster.)

  12. Undeploy any applications that are deployed on the Administration Server.

  13. Configure your HTTP server to serve pages from each server in pageCluster (but not any of the other servers).

  14. Shut down the Administration Server and then restart it. This will ensure that all of the changes you made will take effect.

  15. Start up the managed servers you created, using the startManagedWebLogic script. The syntax of this script is:

    startManagedWebLogic WebLogicServeradminURL

    where WebLogicServer is the name of the WebLogic server, and adminURL is the URL of the WebLogic Administration Server. Let’s assume that the hostname for the Administration Server is myMachine. To start up the WebLogic pageServer1, the command would be:

    startManagedWebLogic pageServer1 http://myMachine/7001

loading table of contents...