Using the CLI to Work With WebLogic

When you work with WebLogic through the provisioning system, you can use two command lines: the N1 Grid Service Provisioning System command line and the WebLogic command line.

Using the N1 Grid Service Provisioning System Command-Line Interface

By default, the provisioning system's command-line interface is located in the following directory: /opt/SUNWn1sps/N1_Grid_Service_Provisioning_system_5.0/cli/bin/cr_cli

BEA WebLogic 8 plug-in objects are located in the /com/sun/weblogic8 folder.

You can interact with plug-in components and plans much like any other custom component or plan. However, if you want to make changes to the components or plans, you need to save the component or plan to a new folder and make your changes there. For more information about using the provisioning system's command-line interface, see Chapter 1, Using the Command-Line Interface, in N1 Grid Service Provisioning System 5.0 Command-Line Interface Reference Manual

Using the WebLogic Command-Line Interface

The WebLogic command line is accessible through the WebLogic 8 Common Task page. For more information about the WebLogic 8 command-line interface, see the WebLogic Server Command Reference on BEA's web site.

How to Use the WebLogic Command-Line Interface Through the N1 Grid Service Provisioning System

You can run WebLogic commands on any Administration Server or Managed Server.

Steps

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

2. Select whether you plan to run the command on an Administration Server or a Managed Server.

   • If you plan to run commands on an Administration Server, click Domain Management: Start.

   • If you plan to run commands on a Managed Server, click Application Server Management: Start.

   The component Details page displays

3. Select the Run-cli component procedure and click Run.

   The plan's Run page displays.

4. Select the AdminServer virtual host or Managed Server virtual host on which to run the CLI and click Run Selected Installations.

5. Type the needed information in the plan variable fields.

   Many of the plan variables do not require information and can be left blank. The following list describes the optional variables.

   The SSL arguments for the command

   This variable can be safely ignored if you do not connect to the server using SSL.

   The name of the user who must have appropriate permission to view or modify the target of the command

   This is the user name variable. The user name and password variables are mutually exclusive with the user-configuration file and key file variables. Supply either the user name and password or the user-configuration file and key file locations.

   The password that is associated with the username

   This is the password variable. The user name and password variables are mutually exclusive with the user-configuration file and key file variables. Supply either the user name and password or the user-configuration file and key file locations.

   The name and location of a user-configuration file, which contains an encrypted username and password

   This is the user-configuration file variable. The user name and password variables are mutually exclusive with the user-configuration file and key file variables. Supply either the user name and password or the user-configuration file and key file locations.

   The name and location of the key file

   This is the key file variable. The user name and password variables are mutually exclusive with the user-configuration file and key file variables. Supply either the user name and password or the user-configuration file and key file locations.

6. Click Run Plan (Includes Preflight).

Example 4–1 Using the Command-Line Interface

This example uses the WebLogic FORCESHUTDOWN command to illustrate input for each Run-cli plan variable.

Using the WebLogic Server Scripting Tool Within the N1 Grid Service Provisioning System

You can use the WebLogic Server Scripting Tool (WLST) from the provisioning system's browser interface. 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.

How to Create a WebLogic Script Component

You must first create the WebLogic script component, then install it.

Steps

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

2. Click the Command Line Interface: Create link.

   The component's Edit page displays.

3. Type the name of the new WebLogic Script component.

4. (Optional) Type the components label and description.

5. Select a host that has a copy of the WebLogic script file on its file system.

6. Navigate through the host's file system and select the file.

7. Click Check In Selected Item.

   The component's Check In page displays.

8. Select a folder on which you have edit permissions.

9. Click Continue to Check In.

How to Install a WebLogic Script Component

Before You Begin

Before you can install a WebLogic script component, one must exist within the provisioning system. See How to Create a WebLogic Script Component.

Steps

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

2. Click the Command Line Interface: View All link.

   The Components page displays.

3. In the row of the WLScript component that you plan to install, click Details.

   The component's Details page displays.

4. In the Component Procedures table, select the Default: Install procedure and click Run.

   The plan's Run page displays.

5. Select the target host.

   You target the AdminServer virtual host.

   ---

   Note –

   You do not need to modify the component variables for license installation.

   ---

6. (Optional) Type the name of the WebLogic user who installed the software in the RunAs field.

   This user represented by the webLogicUser variable used in the software installation plan.

7. Click Run Plan (Includes Preflight).