How Do I: Deploy a Workshop Application to a Cluster?
This topic provides step by step instructions for configuring a domain for a cluster of WebLogic Servers and for deploying a Workshop application to that cluster. These instructions applies only to Windows installations of Workshop. For information about cluster hardware configuration see Setting up WebLogic Clusters in the WebLogic 7.0 documentation.
The five basic tasks in setting up and deploying to a cluster are:
1. Select Start-->BEA WebLogic Platform 7.0-->Configuration Wizard
2. In the Select a Template
dialog, select WebLogic Workshop.
Under Name, type the name you wish to give to your domain. Click Next.
3. In the Choose a Sever Type dialog, select Admin Server with Clustered Managed Server(s). Click Next.
4. In the Choose Domain Location dialog,
enter the location of the domain on the local machine.
5. In the Configure Clustered Severs dialog,
click Add to enter information
about each managed server you wish to included in your cluster. For each
managed server, enter:
Name
The Name must consist of alphanumeric characters with no spaces.
Listen
Address
For the Listen Address field see DNS Names or IP Addresses
in the WebLogic Server 7.0 documentation.
Listen
Port and SSL Listen Port
Any port numbers between 1 and 65535 are valid.
Repeat step 5 for each managed server you wish to add to the cluster.
6. In the Configure Cluster dialog, enter
Cluster Name
This gives the name of the cluster as a whole.
Cluster Multicast
Address
Allowable values are in the range 224.0.0.0 - 239.255.255.255
Cluster Multicast
Port
Any pumber between 1 and 65535 is valid.
Cluster Address
The Cluster Address defaults to the address:port combinations for each
server instance in the cluster.
Name
The Name must consist of alphanumeric characters with no spaces.
Server
Listen Address
For the Listen Address field see DNS Names or IP Addresses
in the WebLogic Server 7.0 documentation. The listen address you enter
here should be the same as was entered in step 5 above.
Server
Listen Port and SSL Listen Port
Any port number between 1 and 65535 are valid. The ports you enter
here should be the same as you entered in step 5 above.
This task must be repeated for each managed server that you specified in step 5 above.
12. Select Start-->BEA WebLogic Platform 7.0-->Configuration Wizard
13. Under Select a template, select WebLogic Workshop. Under Name, enter the domain name you entered when configuring the administration server.
14. In the Choose Server Type dialog, select Managed Server (with owning Admin Server configuration)
15. In the Choose Domain Location dialog, enter the location of the domain on the local machine.
16. In the Configure Administrative Server Connection dialog, enter:
Admin
Server Name or IP
See DNS Names or IP Addresses in the WebLogic
Server 7.0 documentation.
Admin
Server Listen Port
Any port number between 1 and 65535 are valid. The
ports you enter here should be the same as you entered in step 5 above.
Admin
Server SSL Listen Port
Any port number between 1 and 65535 are valid. The
ports you enter here should be the same as you entered in step 5 above.
Managed
Server Name
Enter the DNS name of the managed server.
17. In the Configure Standalone/Administration Server dialog, enter:
Name
The Name must consist of alphanumeric characters with no spaces.
Server
Listen Address
For the Listen Address field see DNS Names or IP Addresses
in the WebLogic Server 7.0 documentation. The
listen address you enter here should be the same as was entered in step
5 above.
Server
Listen Port and SSL Listen Port
Any port number between 1 and 65535 are valid. The
ports you enter here should be the same as you entered in step 5 above.
18. In the Create Administrative User dialog, enter a username and password. The username and password are required to start the server instances in the cluster. The username, such as "system" must belong to a role that is permitted to start server instances. For information about allowable usernames see the Protecting System Administration Operations in BEA WebLogic Server Administration Guide.
19. In the Create Start Menu Entry For Server dialog, choose whether you want to place a link to the administration server on the Start Menu.
20. In the Configuration Summary dialog, click Create. It is recommended that you cut and paste the configuration summary to a text editor for future reference.
21. In the Configuration Wizard Complete dialog, select End Configuration Wizard, and click Done.If you are using a software proxy server, you must build and configure the proxy application that will service requests from clients. For information about software proxy server see Configure Proxy Plug-Ins in the WebLogic Server 7.0 documentation.
To start a cluster, you must first start the administration server and then each of the managed servers. Do not start the managed servers until the administration server has been started.
To start the administration server:
22. Open a command shell, and cd to the domain directory that you created in step 4 above.
23. Enter the following command:
startWebLogic
production nodebug.
To start a managed server:
24. Open a command shell, and cd to the domain directory you created in step 4 above.
25. Enter the command
startManagedWeblogic [managed server DNS name or IP address] [URL of the administration server:port]
For example,
startManagedWeblogic
managedServer1 http://adminServer:7133
Repeat steps 24 and 25 for each managed server in the cluster.
Before you deploy a Workshop application to a server cluster, you must first generate an EAR file for the application. For instructions on generating an EAR file, see How To Generate an EAR for a Web Service Application.
When you make an EAR using jwsCompile, make sure to specify the -http-port, -https-port and -hostname parameters. The -http-port and -https-port should give the ports that clients will use to call the proxy server. The -hostname parameter should specify the proxy server's DNS name. Once you have generated an EAR, you must deploy it to the servers in your cluster. To deploy an EAR file to a cluster, you can either use the command line tool weblogic.Deployer or the WebLogic Server console. To learn more about using weblogic.Deployer to deploy an EAR file to cluster, see weblogic.Deployer Utility and weblogic.Deployer in the WebLogic Server 7.0 documentation. To learn more about using the WebLogic Server console to deploy an EAR file see WebLogic Administrative Console.
How Do I: Deploy WebLogic Workshop Web Services to a Production Server?