Sun N1 Service Provisioning System User's Guide for BEA WebLogic 9 Plug-in 1.0

Creating the WebLogic Infrastructure

Use the WebLogic 9 Common Tasks page as a starting point to create and manage WebLogic servers and clusters.

Creating WebLogic 9 Domains and Administration Servers

How to Create a WebLogic 9 Domain and Administration Server

You need to create a domain and Administration Server before you can set up Managed Servers to host your applications. A domain is a set of WebLogic servers that is managed by an Administration Server. All information about the domain is contained in a configuration file that is stored on the Administration Server.

When you create a new domain by installing the AdminServer component, you also perform the following tasks.

Configure the domain.
Create the Admin Server virtual host. This task is performed when the plan is run.

You can use this procedure to create a new domain or you can use this procedure to register an existing domain within the provisioning system by selecting the markOnly option.

Note –

In this document, two similar terms are used: AdminServer and Administration Server. The prepackaged Sun N1 Service Provisioning System WebLogic 9 component is called the AdminServer component. AdminServer represents the provisioning system component and Administration Server represents the installed application running in the WebLogic 9 environment.

Before You Begin

To create a WebLogic 9 domain, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.

Steps

Verify that your WebLogic session variables, WL_DEFAULT_USER and WL_DEFAULT_PASSWORD, are set.

WebLogic session variables must be seven characters long. The WL_DEFAULT_PASSWORD variable must contain a number.

For more information about session variables, see Chapter 5, Session Variables, in Sun N1 Service Provisioning System 5.2 Plan and Component Developer’s Guide.

In the Common Tasks section in the browser interface, click WebLogic 9.

Click the Domain Management: Create link.

The plan's Details page displays.

Click Run.

The Run page displays.

In the Plan Parameters area, select the variable settings for the AdminServer component that you plan to deploy.
- If the variable settings have been established for this component, select the appropriate settings from the menu.
- If the settings are not available from the menu, click Select From List.
  
  The Select Variable Settings From List window displays.
  - To create a new set of variable settings, select Create Set.
    
    The following list provides commonly updated variables for the AdminServer component.
    
    Note –
    For those variables that specify port values, the ports that you specify must be free if the value of the weblogicUser variable is not root.
    
    domainName
    
    Required. The WebLogic domain name.
    
    adminListenPort
    
    Required. The default TCP port (between 1024 and 65534) on which the Administration Server will listen for non-SSL communication. The default value is 7001.
    
    adminSslListenPort
    
    The default TCP port (between 1024 and 65534) on which the Administration Server will listen for SSL communication. The default value is 7002.
    
    administrationPort
    
    The default TCP port (between 1 and 65534) that the Administration Server will use for all connections. By setting this variable, all other ports are disabled. The default for this value is 9002.
    
    enableAdministrationPort
    
    Enable the Domain wide administration port you specified in the administrationPort variable. Set this value to true to enable the Administration Server to listen for communication on the port you specified in the administrationPort variable.
    
    If you set this value to true, set the secureConnect value to true. All communications traffic will use this port.
    
    The default value is false.
    
    adminPort
    
    Required. The default port for JMX calls and the Managed Servers to use. This value must be either :[adminListenPort], :[adminSslListenPort], or :[administrationPort]. The default value is :[adminSslListenPort].
    
    Note –
    If you set this variable to :[adminSslListenPort], set the secureConnect variable to true. If you set this variable to :[administrationPort], set both the secureConnect and enableAdministrationPort variables to true.
    
    Before the domain is created, a check is performed to verify that the ports are available. .
    
    secureConnect
    
    Optional. True specifies that the port specified for the adminPort variable will use SSL for connections. Set this value to true if you are using the adminSslListenPort or administrationPort variables.
    
    production
    
    Required. This variable determines whether the managed server is run in production mode. The default value of production is false. This variable can be set to true or false.
    
    Variables that are updated less often include configuration variables such as the following:
    
    adminManagedServer
    
    Required. The name of the managed server that hosts the domain administration console. The default value is AdminServer. If performing a markOnly install, set the variable to the server name used during the WebLogic install.
    
    adminHost
    
    Required. The hostname or IP address that managed servers use to connect to the Admin Server. The default value is the hostname of the Remote Agent on which the Admin Server resides.
    
    Note –
    Due to SSL host name verifications, you might need to change this value to the node name of the machine if you are using the secureConnect.
    
    targetRefName
    
    Required. This variable becomes the name of the domain's virtual host. The substitution variable is based on the values for the host name and for the domain name. This variable follows the format :[target:sys.hostName]_weblogic_admin_ :[domainName]. For example, sqa-420_weblogic_admin_wls.
    
    configJAR
    
    Specifies the domain template JAR to use to configure the domain. Use the default value provided. The default value is :[wlHomeDir]:[/]common:[/]templates:[/]domains:[/]wls.jar.
    
    The Select Variable Settings From List window displays.
    1. In the text field at the top of the table, type the name of the new variable settings set.
    2. To change the WebLogic Domain name, select the domainName row and type the new domain name.
    3. Specify the port number that you want to use in the appropriate variable field.
      
      Specify the port value in the adminListenPort, adminSslListenPort, or administrationPort field.
    4. Select the adminPort row and type the appropriate variable substitution value for the variable you set in the previous step.
      
      Set this value to either :[adminListenPort], :[adminSslListenPort], or :[administrationPort].
    5. To specify that secure HTTP be used to connect to the Administration Server, select the secureConnect row and type True in the text field.
      
      Set this value if the adminPort variable is set to either :[adminSslListenPort] or :[administrationPort].
    6. To change the path to where WebLogic is installed, select the beaHome row and type the correct path.
      
      Note –
      The value for the installPath variable is treated as a relative path to the default Remote Agent directory, unless you specify an absolute path, such as /opt. For example, for a Solaris Remote Agent, if you set the installPath variable to opt and deploy the file to an Agent with a default home directory of /opt/SUNWn1sps/agent, the file is deployed to /opt/SUNWn1sps/agent/opt/.
    7. If necessary, modify the value of the remaining predefined variables.
      
      The targetRefName is pre-defined for you, although you can modify it 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]
  - If you want to use another component's variable settings, click Import Set From Component.
    
    The Import Variable Settings window displays.
    1. If necessary, navigate to the Folder that contains the component with the variable settings you want to import.
    2. Select the component version.
      
      Note –
      Variable settings can vary between component versions. Ensure that the current components and the component from which you want to import variable settings share common variables. If the component from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable settings are not imported.
    3. Click Import Variable Settings.
      
      The variables settings are imported, and are displayed in the table.
    4. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.
  - If you want to use component variable settings that are stored in a file, follow these steps.
    1. In the Import Sets from File text field, enter the path to the variable settings file that you want to use.
      
      To browse through the file system to find the appropriate file, click the Browse button.
    2. Click Import.
      
      The variables settings are imported, and are displayed in the table.
      
      Note –
      If the file from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable set is not imported.
    3. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.

Select the target host.

Target the virtual host that was created when you installed the WebLogic software. See How to Install the WebLogic Software procedure.

Note –
The target host must be a member of the com.sun.weblogic9#InstallHS host set.

If you are capturing an existing WebLogic domain within the provisioning system, select the markOnly option.

Ensure that all the variable values you specify for this component match the configuration of the installed WebLogic domain.

Click Run Plan (Includes Preflight).

Creating Managed Servers

You can run multiple Managed Servers in each domain to host your applications. WebLogic Managed Servers are installed and represented in the provisioning system by Server components. Throughout this book, Server refers to the provisioning system component, while Managed Server refers to the installed instance of the Managed Server running in the WebLogic 9 environment.

You can also enable your Managed Servers to use the WebLogic Node Manager process to remotely manage your systems. To enable your Managed Servers to use Node Manager, you must create a WebLogic machine on the Managed Server.

How to Create a WebLogic Managed Server

You can use this procedure to create a new Managed Server or you can use this procedure to register an existing Managed Server within the provisioning system by selecting the markOnly option.

Before You Begin

Before you can create a WebLogic Managed Server, the following criteria must be met.

A domain to contain the Managed Server must exist.

For more information, see How to Create a WebLogic 9 Domain and Administration Server.
The domain's AdminServer must be running.

To manually start an AdminServer, run the startAdminServer component procedure from the AdminServer component Details page.
The WebLogic software must be installed on the host on which you plan to install a Managed Server.

See How to Install the WebLogic Software.
You must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
(Optional) If you want to remotely manage your Managed Server with a Node Manager, you must create a WebLogic machine. You must then enrol the WebLogic machine in a domain, and start the Node Manager.

See How to Create WebLogic Machines.

Steps

In the Common Tasks section in the browser interface, click WebLogic 9.

Click the Application Server Management: Create link.

The plan's Details page displays.

Click Run.

The Run page displays.

In the Plan Parameters area, select the variable settings for the ManagedServer component that you plan to deploy.

The Server component represents the Managed Server instance within the WebLogic 9 environment.
- If the variable settings have been established for this component, select the appropriate settings from the menu.
- If the settings are not available from the menu, click Select From List.
  
  The Select Variable Settings From List window displays.
  - To create a new set of variable settings, select Create Set.
    
    The following list provides commonly updated variables for the ManagedServer component.
    
    variable set name
    
    Required. A name for the new variable set you create
    
    adminServerHostName
    
    Required. Name of the AdminServer virtual host that hosts the new Managed Server. This value will be in the format remoteAgentName_weblogic_admin_domainName.
    
    You can find the virtual host on the Hosts page. The virtual host will be of type com.sun.weblogic9#AdminServerHS.
    
    targetName
    
    Required. The new Managed Server's name. This name is used in the targetRefName variable to create the Managed Server virtual host.
    
    startupScriptName
    
    Required. The name of the Managed Server's startup script.
    
    serverPort
    
    Required. The default value for this variable is 7010. If this port is not available, the plan fails with a warning.
    
    serverSslPort
    
    Required. The default value for this variable is 7020.If this port is not available, the plan fails with a warning.
    
    listenAddress
    
    Required. The IP address the Managed Server uses to listen.
    
    useNodeManager
    
    Required. Specifies whether to use a WebLogic machine to remotely manage a Managed server (true/false). The default value is false. If you are using a WebLogic machine to remotely manage your managed server, set this value to true.
    
    adminPortOverRide
    
    Specifies the TCP port that this server will use for communications with the Administration Server.
    
    If the Managed Server is running on the same system as the Administration Server, change the default value for this variable to avoid a conflict with the port that the Administration Server is using for the administration port.
    
    If you change the value for this variable, this port will be used for all connections, overriding the value as specified by the administrationPort variable for the Administration Server. The default value is 9002.
    
    webLogicUser
    
    Required. The UNIX user to run the WebLogic installation. This user must exist on the host to be installed and must have write permission on the beaHome directory. The default value for this variable is taken from the WebLogic software installation component.
    
    production
    
    Required. This variable determines whether the managed server is run in production mode. The default value of production is false. This variable can be set to true or false.
    
    serverRoot
    
    Required. The directory used for the Managed Server.
    
    If you are using a WebLogic machine to manage your Managed Server, set this value to :[wlHomeDir]:[/]common:[/]nodemanager:[/]:[domainName]:[/]servers:[/]:[targetName] to point to the Node Manager server root directory.
  - If you want to use another component's variable settings, click Import Set From Component.
    
    The Import Variable Settings window displays.
    1. If necessary, navigate to the Folder that contains the component with the variable settings you want to import.
    2. Select the component version.
      
      Note –
      Variable settings can vary between component versions. Ensure that the current components and the component from which you want to import variable settings share common variables. If the component from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable settings are not imported.
    3. Click Import Variable Settings.
      
      The variables settings are imported, and are displayed in the table.
    4. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.
  - If you want to use component variable settings that are stored in a file, follow these steps.
    1. In the Import Sets from File text field, enter the path to the variable settings file that you want to use.
      
      To browse through the file system to find the appropriate file, click the Browse button.
    2. Click Import.
      
      The variables settings are imported, and are displayed in the table.
      
      Note –
      If the file from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable set is not imported.
    3. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.

Select the target host or target host set.

The Managed Server resides on the Remote Agent that you target.

Target the virtual host that was created when you installed the WebLogic software. See How to Install the WebLogic Software procedure.

Note –
The target host must be a member of the com.sun.weblogic9#InstallHS host set.

If you are modelling an existing WebLogic Managed Server within the provisioning system, select the markOnly option.

Ensure that the variables you specified for the component match the values for the existing managed server.

Click Run Plan (Includes Preflight).

Creating WebLogic Clusters

You might need to create a cluster for the following reasons:

To increase application availability with the server's failover capabilities
To increase throughput by scaling applications across multiple servers

A cluster appears to clients as a single WebLogic Managed Server instance. The server instances that constitute a cluster can run on the same machine, or can be located on different machines. Each cluster member in a cluster must run the same version of WebLogic.

How to Create a WebLogic Cluster

You can use this procedure to create a new cluster or you can use this procedure to register an existing cluster within the provisioning system by selecting the markOnly option.

Before You Begin

Before you create a WebLogic cluster, you must create a WebLogic domain, and an Administration Server.

To create a WebLogic cluster, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.

Steps

In the Common Tasks section in the browser interface, click WebLogic 9.

Click the Cluster Management: Create link.

The plan's Details page displays.

Click Run.

The Run page displays.

In the Plan Parameters area, select the variable settings for the Cluster component that you plan to deploy.
- If the variable settings have been established for this component, select the appropriate settings from the menu.
- If the settings are not available from the menu, click Select From List.
  
  The Select Variable Settings From List window displays.
  - To create a new set of variable settings, select Create Set.
    
    The following list provides commonly updated variables for the ManagedServer component.
    
    variable set name
    
    Required. A name for the new variable set you create
    
    targetName
    
    Required. The name of the new cluster.
    
    clusterAddress
    
    Optional. This variable can be a DNS host name that maps to multiple IP addresses or a comma-separated list of single address host names or IP addresses. No value is necessary for this variable.
    
    multicastAddress
    
    This variable provides the address that cluster members can use to communicate with each other.
    
    multicastPort
    
    This variable provides the port number that cluster members can use to communicate with each other.
    
    The Select Variable Settings From List window displays.
    1. In the text field at the top of the table, type the name of the new variable settings set.
    2. To change the name of the new cluster, select the targetName row and type the new name.
    3. To specify the address for the cluster instance, select the clusterAddress row and type the address.
      
      This variable can be a DNS host name that maps to multiple IP addresses or a comma-separated list of single address host names or IP addresses. No value is necessary for this variable.
    4. To change the cluster's multicast port, select the multicastAddress row and type the new address.
      
      This variable provides the address that cluster members can use to communicate with each other. The default value is 237.0.0.1.
    5. To change the cluster's multicast address, select the multicastPort row and type the new port number.
      
      This variable provides the aport number that cluster members can use to communicate with each other. The default value is 7001.
    6. If necessary, modify the value of the remaining predefined variables.
      - The installPath is created based on the value for the AdminServer virtual host name, the domain name, and the cluster name.
      - 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]
    7. Click Save.
      
      The new variable settings display in the table.
    8. Click Select.
  - If you want to use another component's variable settings, click Import Set From Component.
    
    The Import Variable Settings window displays.
    1. If necessary, navigate to the Folder that contains the component with the variable settings you want to import.
    2. Select the component version.
      
      Note –
      Variable settings can vary between component versions. Ensure that the current components and the component from which you want to import variable settings share common variables. If the component from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable settings are not imported.
    3. Click Import Variable Settings.
      
      The variables settings are imported, and are displayed in the table.
    4. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.
  - If you want to use component variable settings that are stored in a file, follow these steps.
    1. In the Import Sets from File text field, enter the path to the variable settings file that you want to use.
      
      To browse through the file system to find the appropriate file, click the Browse button.
    2. Click Import.
      
      The variables settings are imported, and are displayed in the table.
      
      Note –
      If the file from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable set is not imported.
    3. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.

Select the target host.

Because you can only install a cluster on an Administrative Server, the target host is the AdminServer virtual host.

If you are capturing an existing WebLogic cluster within the provisioning system, select the markOnly option.

Click Run Plan (Includes Preflight).

How to Create Cluster Members

Cluster nodes are Managed Servers assigned to a cluster. You will want to create cluster members to make your applications highly available and scalable.

When a Managed Server joins the cluster, the applications that are currently targeted to the Managed Server continue to target that server, the application deployment state is preserved. The plan that creates the cluster members automatically stops the Managed Server to add it to the cluster. After the Managed Server is added, the plan restarts the Managed Server.

You can use this procedure to create a new cluster member or you can use this procedure to register an existing cluster member within the provisioning system by selecting the markOnly option.

Before You Begin

Before you can create cluster members, the following requirements must be met.

Managed Servers that you plan to convert to cluster members must exist.

For more information, see How to Create a WebLogic Managed Server.
The cluster that you plan to add nodes to must exist.

For more information, see How to Create a WebLogic Cluster.

To create a cluster member, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.

Steps

In the Common Tasks section in the browser interface, click WebLogic 9.

Click the Cluster Member Management: Join link.

The plan's Details page displays.

Click Run.

The plan's Run page displays.

Choose the Managed Server that you want to add to the cluster.
- Select the Target Host by typing the Managed Server's name or selecting it from a list.
- Select the Target Host Set from the menu.

Verify that the plan variable WebLogic Cluster Name contains the correct cluster name.

To specify how long the provisioning system waits before verifying that the server was restarted, type the number of seconds in the Seconds to Wait Before Failing Verify Step field.

If you are capturing an existing WebLogic cluster member within the provisioning system, select the markOnly option.

Click Run Plan (Includes Preflight).

Creating WebLogic Machines

You can set up a WebLogic machine to use the Node Manager process to remotely manage your Managed Servers. To use the Node Manager process to control your Managed Server, you must install the WebLogic machine component, and then enroll the Machine in a domain.

Choose the appropriate procedure to create a WebLogic machine.

To install the Machine component on a Managed Server, see How to Create WebLogic Machines.
To incorporate an existing WebLogic machine in your N1 SPS environment, see How to Capture an Existing WebLogic Machines in Your N1 SPS Environment.

How to Create WebLogic Machines

This procedure describes how to install the WebLogic machine component and start the Node Manager process.

To incorporate an existing WebLogic machine in your N1 SPS environment, see How to Capture an Existing WebLogic Machines in Your N1 SPS Environment.

Steps

In the Common Tasks section in the browser interface, click WebLogic 9.

Click the WebLogic Machine Installation: Install link.

The plan's Details page displays.

Click Run.

The Run page displays.

In the Plan Parameters area, select the variable settings for the Machine component that you plan to deploy.

The Machine component represents the Machine instance within the WebLogic 9 environment.
- If the variable settings have been established for this component, select the appropriate settings from the menu.
- If the settings are not available from the menu, click Select From List.
  
  The Select Variable Settings From List window displays.
  - To create a new set of variable settings, select Create Set.
    
    The following list provides commonly updated variables for the Machine component.
    
    variable set name
    
    Required. A name for the new variable set you create
    
    machineName
    
    Required. Specifies the name for the Node Manager machine in the domain. The default value is the host name of the target host.
    
    nodeManagerPort
    
    Required. Specifies the port that the Node Manager uses to listen for communication. The default value is 5556.
    
    nodeManagerListenAddress
    
    Required. Specifies the IP address the Node Manager uses to listen. The default value is the IP address of the Remote Agent.
    
    unixPlatform
    
    Required. Specifies the type of machine to create (true,false). The default value is true.
    
    weblogicUser
    
    Required. The UNIX user to run the Node Manager. This user must exist on the host to be installed and must have write permission on the beaHome directory. The default value is the value for the weblogicUser variable that is set for the installall component.
    
    wlHomeDir
    
    Required. Specifies the location of the WebLogic software installation. Do not change this variable.
    
    installPath
    
    Required. Specifies the unique install path for the machine. Do not change this variable.
  - If you want to use another component's variable settings, click Import Set From Component.
    
    The Import Variable Settings window displays.
    1. If necessary, navigate to the Folder that contains the component with the variable settings you want to import.
    2. Select the component version.
      
      Note –
      Variable settings can vary between component versions. Ensure that the current components and the component from which you want to import variable settings share common variables. If the component from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable settings are not imported.
    3. Click Import Variable Settings.
      
      The variables settings are imported, and are displayed in the table.
    4. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.
  - If you want to use component variable settings that are stored in a file, follow these steps.
    1. In the Import Sets from File text field, enter the path to the variable settings file that you want to use.
      
      To browse through the file system to find the appropriate file, click the Browse button.
    2. Click Import.
      
      The variables settings are imported, and are displayed in the table.
      
      Note –
      If the file from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable set is not imported.
    3. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.

Select the target host or target host set.

The WebLogic machine resides on the Remote Agent that you target.

Note –
The target host must be a member of the com.sun.weblogic#InstallHS host set.

Target the virtual host that was created when you installed the WebLogic software. See How to Install the WebLogic Software procedure.

If you want to start the Node Manager after the installation, verify that the Start Node Manager checkbox is checked.

(Optional) If you want to pass any Java arguments to the WebLogic Server Scripting Tool (WLST) during the installation, type the arguments in the Java Arguments Used for weblogic.WLST field.

You might need to use WLST if the Administration Server port uses SSL and requires demo certificates.

For information on how to perform administrative tasks and configuration changes using the WLST, see BEA's WebLogic Server Using the WebLogic Server Scripting Tool document

Click Run Plan (Includes Preflight).

The provisioning software creates the WebLogic machine.

Verify that the WebLogic machine was created.
1. In the Common Tasks section of the browser interface, click WebLogic 9.
2. Click the WebLogic Machine Installation: View Installations link.
  
  The Component Details Where Installed page displays. The WebLogic machine you created appears in the Hosts Where Installed table with the extension -machine.

Next Steps

You must enroll your WebLogic machine in a WebLogic domain. For instructions, see How to Enroll WebLogic Machines in a Domain.

To use the WebLogic machine to manage your Managed Servers, you must instruct your Managed Servers to use Node Manager. See How to Create a WebLogic Managed Server.

How to Capture an Existing WebLogic Machines in Your N1 SPS Environment

This procedure describes how to incorporate an existing WebLogic machinein the provisioning system.

To create a new WebLogic machine, see How to Create WebLogic Machines.

Steps

In the Application Deployments section in the browser interface, click Components.

The Components page is displayed.

If necessary, click the Change Folder link to navigate to the com/sun/weblogic9 folder.

In the Components column, click Machine.

The Components Details page is displayed.

In the Component Procedures table, click the Run link in the install: markOnly row.

The Plans Details Run page is displayed.

In the Plan Parameters area, select the variable settings for the Machine component that you plan to deploy.

The Machine component represents the Machine instance within the WebLogic 9 environment.
- If the variable settings have been established for this component, select the appropriate settings from the menu.
- If the settings are not available from the menu, click Select From List.
  
  The Select Variable Settings From List window displays.
  - To create a new set of variable settings, select Create Set.
    
    The following list provides commonly updated variables for the Machine component.
    
    variable set name
    
    Required. A name for the new variable set you create
    
    machineName
    
    Required. Specifies the name for the Node Manager machine in the domain. The default value is the host name of the target host.
    
    nodeManagerPort
    
    Required. Specifies the port that the Node Manager uses to listen for communication. The default value is 5556.
    
    nodeManagerListenAddress
    
    Required. Specifies the IP address the Node Manager uses to listen.
    
    unixPlatform
    
    Required. Specifies the type of machine to create (true,false). The default value is true.
    
    weblogicUser
    
    Required. The UNIX user to run the Node Manager. This user must exist on the host to be installed and must have write permission on the beaHome directory.
    
    wlHomeDir
    
    Required. Specifies the location of the WebLogic software installation.
    
    installPath
    
    Required. Specifies the unique install path for the machine.
  - If you want to use another component's variable settings, click Import Set From Component.
    
    The Import Variable Settings window displays.
    1. If necessary, navigate to the Folder that contains the component with the variable settings you want to import.
    2. Select the component version.
      
      Note –
      Variable settings can vary between component versions. Ensure that the current components and the component from which you want to import variable settings share common variables. If the component from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable settings are not imported.
    3. Click Import Variable Settings.
      
      The variables settings are imported, and are displayed in the table.
    4. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.
  - If you want to use component variable settings that are stored in a file, follow these steps.
    1. In the Import Sets from File text field, enter the path to the variable settings file that you want to use.
      
      To browse through the file system to find the appropriate file, click the Browse button.
    2. Click Import.
      
      The variables settings are imported, and are displayed in the table.
      
      Note –
      If the file from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable set is not imported.
    3. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.

Select the target host or target host set.

The WebLogic machine resides on the Remote Agent that you target.

Note –
The target host must be a member of the com.sun.weblogic#InstallHS host set.

Target the virtual host that was created when you installed the WebLogic software. See How to Install the WebLogic Software procedure.

Click Run Plan (Includes Preflight).

The provisioning software creates the WebLogic machine.

Verify that the WebLogic machine was created.
1. In the Common Tasks section of the browser interface, click WebLogic 9.
2. Click the WebLogic Machine Installation: View Installations link.
  
  The Component Details Where Installed page displays. The WebLogic machine you created appears in the Hosts Where Installed table with the extension -machine.

Next Steps

You must enroll your WebLogic machine in a WebLogic domain. For instructions, see How to Enroll WebLogic Machines in a Domain.

To use the WebLogic machine to manage your Managed Servers, you must instruct your Managed Servers to use Node Manager. See How to Create a WebLogic Managed Server.

How to Enroll WebLogic Machines in a Domain

After you create a WebLogic machine, you must enroll the machine in a WebLogic domain. This procedure describes how to enroll a WebLogic machine in a domain.

Before You Begin

You must create a WebLogic domain before you enroll a WebLogic machine. For more information, see How to Create a WebLogic 9 Domain and Administration Server.

Steps

In the Common Tasks section of the browser interface, click WebLogic 9.

Click the WebLogic Machine Installation: Enroll link.

The Plans Details Run page displays.

Select the WebLogic machine that you want to enroll from the Current Installations list.

Click the Run Selected Installations link.

The Plans Details Run page refreshes to include plan parameters and options.

In the Logical Host for Domain Admin Server field, type the logical host name for the Administration Server.

In the Java Arguments Used for weblogic.WLST field, type any appropriate options to use with the WebLogic Scripting Tool (WLST).

If your Administration Server is using SSL, specify the following options to use the demo SSL certificates. Specify these arguments on one line, separated by a space.
-Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust

Specify any additional options or limits as appropriate for your environment.

Click Run Plan (includes preflight).