Installation Guide for Oracle Billing Insight > Configuring Oracle WebLogic >
Starting the Oracle WebLogic Cluster
If you are configuring the Self-Service application on an Oracle WebLogic cluster, then you must start the cluster after deployment. This task is a step in Process of Configuring the Self-Service Application on an Oracle WebLogic Cluster. To start the Oracle WebLogic cluster
- On the computer where the Admin server is located, start the admin server:
$selfservice_domain/bin/startWeblogic.sh
- On each computer, start the node manager:
$WL_HOME/server/bin/startNodeManager.sh
- Start each of the managed servers that is on the same computer as the Admin server:
$WL_HOME/common/bin/startManagedWeblogic.sh BillingInsightMS1 http://10.240.12.163:7001
where:
- BillingInsightMS1 is the name you gave the managed server.
- 10.240.12.163 is the IP address of the computer where the Admin server is located.
- 7001 is the port number of the Admin server.
- Start the proxy server. In this command, EBillingProxy is the name you gave the Proxy server:
$WL_HOME/common/bin/startManagedWebLogic.sh BillingInsightProxy http:// 10.240.12.163:7001
where:
- BillingInsightProxy is the name you gave the Proxy server.
- 10.240.12.163 is the IP address of the computer where the Admin server is located.
- 7001 is the port number of the Admin server.
- On each of the other computers in the cluster, follow these steps:
- Start the node manager:
$WL_HOME/server/bin/startNodeManager.sh
- Start each managed server, using the following command:
$weblogic_home /common/bin/startManagedWeblogic.sh BillingInsightMS2 http:// 10.240.12.163:7001
where:
- BillingInsightMS2 is the name you gave the managed server.
- 10.240.12.163 is the IP address of the computer where the Admin server is located.
- 7001 is the port number of the Admin server.
Stopping the Oracle WebLogic Cluster
Follow these instructions if you want to stop the Oracle WebLogic cluster where the Self-Service application is implemented. To stop the Oracle WebLogic cluster
|