Creating and Managing WebLogic Servers and Clusters
Use the WebLogic common tasks page to create and manage WebLogic server and clusters in the provisioning software. You can perform several specific tasks:
To Create a WebLogic
Admin Server for 7.0
Steps
-
From the Common Tasks section in the browser interface, click WebLogic.
-
On the WebLogic Common Tasks page, click Manage 7.0 Admin Servers.
-
On the Components Details page for the 7.0 Admin Server component, click the Run action next to default:install.
-
To set variables for this Admin Server, click Select from List in the Plan Parameters section of the window.
-
To create a new set of variables that have different values from the default values, click Create Set.
The Select Variable Setting From List window appears.
-
In the text field at the top of the table, enter the name of the new variable settings set.
-
To specify the name of the WebLogic Admin Server, click the box next to adminHost and type the name into the field.
-
To change the port number for the WebLogic Admin Server from the default value of 7001, click the box next to adminPort and type the new number into the field.
-
To specify that secure HTTP be used to connect to the WebLogic Admin Server, click the box next to secureConnect and type True into the field.
-
To change the path to where WebLogic is installed, click the box next to wlHomeDir and type the path into the field.
-
To change the WebLogic domain name, click the box next to domainName and type the domain name into the field.
The remaining variables are pre-defined for you, although you can modify them if necessary.
-
The targetRefName is created based on the values for the host name and for the domain name. This variable follows the format :[target:sys.hostName]_admin_:[domainName]
-
The installPath is created based on the value for the domain name. This variable follows the format admin_:[domainName]
-
The webLogicJARPath is created based on the value for the WebLogic home directory. This variable follows the format :[wlHomeDir]:[/]weblogic700:[/]server:[/]lib:[/]weblogic.jar
-
The domainRoot is user_projects
-
-
After updating the component variable values, click Save.
The new variable settings display in the table.
-
Click Select.
-
-
To use variable settings for another component, click Import Set.
The Import Variable Settings window displays.
-
-
Select the target host.
-
Click Run Plan (includes preflight).
To Create a WebLogic
Admin Server for 6.1
Steps
-
From the Common Tasks section in the browser interface, click WebLogic.
-
On the WebLogic Common Tasks page, click Manage 6.1 Admin Servers.
-
On the Components Details page for the 6.1 Admin Server component, click the Run action next to default:install.
-
To set variables for this Admin Server, click Select from List in the Plan Parameters section of the window.
-
To create a new set of variables that have different values from the default values, click Create Set.
The Select Variable Setting From List window appears.
-
In the text field at the top of the table, enter the name of the new variable settings set.
-
To specify the name of the WebLogic Admin Server, click the box next to adminHost and type the name into the field.
-
To change the port number for the WebLogic Admin Server from the default value of 7001, click the box next to adminPort and type the new number into the field.
-
To specify that secure HTTP be used to connect to the WebLogic Admin Server, click the box next to secureConnect and type True into the field.
-
To change the path to where WebLogic is installed, click the box next to wlHomeDir and type the path into the field.
-
To change the WebLogic domain name, click the box next to domainName and type the domain name into the field.
The remaining variables are pre-defined for you, although you can modify them if necessary.
-
The targetRefName is created based on the values for the host name and for the domain name. This variable follows the format :[target:sys.hostName]_admin_:[domainName]
-
The installPath is created based on the value for the domain name. This variable follows the format admin_:[domainName]
-
The webLogicJARPath is created based on the value for the WebLogic home directory. This variable follows the format :[wlHomeDir]:[/]lib:[/]weblogic.jar
-
-
After updating the component variable values, click Save.
The new variable settings display in the table.
-
Click Select.
-
-
To use variable settings for another component, click Import Set.
The Import Variable Settings window displays.
-
-
Select the target host.
-
Click Run Plan (includes preflight).
To Create a WebLogic
Cluster
A WebLogic server cluster consists of multiple WebLogic server instances running simultaneously and working together to provide increased scalability and reliability. A cluster appears to clients to be a single WebLogic server instance. The server instances that constitute a cluster can run on the same machine, or can be located on different machines. Each server instance in a cluster must run the same version of WebLogic server.
Note –
In the N1 Grid Service Provisioning System environment, you must create a cluster, then create the managed servers that are in that cluster. While creating the managed server, one of the optional arguments in the variable list is the cluster host name. When installing a managed server, this cluster host name is used to create a dependency on it. If you create the managed servers before the cluster, there will be no cluster host and therefore the dependency creation will fail.
Steps
-
From the Common Tasks section in the browser interface, click WebLogic.
-
On the WebLogic Common Tasks page, click Manage Clusters.
-
On the Components Details page for the WebLogic cluster component, click the Run action next to default:install.
-
To set variables for this cluster, click Select from List in the Plan Parameters section of the window.
-
To create a new set of variables that have different values from the default values, click Create Set.
The Select Variable Setting From List window appears.
-
In the text field at the top of the table, enter the name of the new variable settings set.
-
To specify the name of the cluster, click the box next to targetName and type the cluster name into the field.
-
After updating the component variable values, click Save.
The new variable settings display in the table.
-
Click Select.
-
-
To use variable settings for another component, click Import Set.
The Import Variable Settings window displays.
-
-
Select the target WebLogic Admin server on which to define the cluster.
-
Click Run Plan (includes preflight).
-
Create server instances to be part of the cluster, as described in
To Manage WebLogic
Server Instances
For each actual WebLogic admin server, you can run multiple server instances. This task explains how to create, start, and stop WebLogic server instances.
Note –
Do not manage your WebLogic applications outside of the N1 Grid Service Provisioning System. If you use the provisioning software, you must manage your WebLogic applications exclusively with the provisioning software.
Steps
-
From the Common Tasks section in the browser interface, click WebLogic.
-
On the WebLogic Common Tasks page, click Manage Server Instances.
-
To create a managed server instance, click the Run action next to Default: Install in the Components Procedures list.
-
To choose a set of variables that apply to this managed server, click Select from List in the Plan Parameters section of the window.
-
To create a new set of variables that have different values from the default values, click Create Set.
The Select Variable Setting From List window appears.
-
In the text field at the top of the table, enter the name of the new variable settings set.
-
To specify the name of the WebLogic Admin Server on which this managed service instance will run, click the box next to adminServerHostName and type the name into the field. This must be an existing WebLogic Admin Server name.
-
To provide a name for the managed server instance, click the box next to targetName and type the name into the field.
This name will be used in the targetRefName to create the actual name for the managed server instance.
-
To provide a full name for the managed server instance, click the box next to targetRefName and type the name into the field.
By default, the targetRefName is created based on the host name, followed by the type of the host (such as “server”), followed by the targetName you provided in the previous step.
-
To provide a path to where to install the managed server instance, click the box next to installPath and provide a complete path name.
By default, the installPath is generated based on the type of the host, followed by the domain name of either the adminServerHostName or some other targetable component, followed by the targetName.
-
If this managed server is part of a cluster, provide the clusterHostName.
Note –The managed server depends on the existence of this cluster. If the cluster does not yet exist, you must create it and then return to create the managed server instance.
-
Provide a complete path to the WebLogic startup script.
If an appropriate script does not exist, you cannot start the WebLogic server instance. You might need to modify the default WebLogic startup script. Specifically, make sure that you provide values for the following variables:
-
SERVER_NAME=server_name — The name of the WebLogic admin server; for example, managed2
-
ADMIN_URL=URL_for_server — The URL to the WebLogic server; for example, http://myplace.domain.me.com:7001/
-
WLS_USER=${1} — The username to be used for the WebLogic server. The ${1} nomenclature sets the WebLogic username to the first argument that you provide when you call the script. This usage bypasses the username prompt during server startup.
-
WLS_PW=${2} — The password for the WebLogic username. The ${2} nomenclature sets the WebLogic password to the password that you provide as the second argument when you call the script. This usage bypasses the password prompt during server startup.
Note –When you make these changes to the startup script, make sure that you delete any old information in the script that would override the values that you defined. Also, be sure to set the script to run in the background, and to redirect the input and output streams for the script.
-
-
After updating the component variable values, click Save.
The new variable settings display in the table.
-
Click Select.
You are returned to the Components Details page for the managed server instance.
-
-
To use variable settings for another component, click Import Set.
The Import Variable Settings window displays.
-
If necessary, navigate to the Folder that contains the component with the variable settings to import.
-
Select the component version.
Note –Variable settings can vary between component versions.
-
Click Import Variable Settings.
The imported variable settings display in the table.
-
Click Select.
You are returned to the Components Details page for the managed server instance.
-
-
-
On the Components Details page for the managed server instance, select the target host on which to run this managed server instance.
-
Click Run Plan (includes preflight).
-
-
To start a WebLogic managed server instance, click the Run action next to Start in the Component Procedures list on the Components Details page for the managed server instance.
-
To stop a WebLogic managed server instance, click the Run action next to Stop in the Component Procedures list on the Components Details page for the managed server instance.
- © 2010, Oracle Corporation and/or its affiliates