test

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

Creating WebLogic 9 Domains and Administration Servers

ProcedureHow 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.

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

  1. 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.

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

  3. Click the Domain Management: Create link.

    The plan's Details page displays.

  4. Click Run.

    The Run page displays.

  5. 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.

  6. 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.

  7. 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.

  8. Click Run Plan (Includes Preflight).