Configuring a WebSphere Application Server Version 5.1 Environment

Plug-In Conventions

The provisioning system enables you to provision and manage applications.

Plans and Component Procedures

The WebSphere 5.1 plug-in provides both plans and component procedures as tools for you to perform tasks. By using plans, you link directly to the functionality you desire. Using component procedures, you have a greater number of tasks that you can perform. Any task that you can perform using a plan included with the WebSphere Plug-In, you can perform by using a component procedure.

Task Names

The WebSphere 5.1 plug-in organizes tasks in four categories: application tasks, infrastructure tasks, configuration tasks, and advanced tasks. These four task categories follow the same convention for describing the task that you must perform.

Global Prerequisite

All tasks within the provisioning system require that you have specific permissions. To perform tasks with the WebSphere 5.1 plug-in, 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.

For more information about permissions, see Chapter 3, Controlling Access Using Permissions, in N1 Grid Service Provisioning System 5.0 System Administration Guide.

For information about how to update your group membership, see How to Change a User’s Group Membership in N1 Grid Service Provisioning System 5.0 System Administration Guide.

Process Overview

Creating a WebSphere 5.1 environment within the provisioning system is similar to the process of creating the environment without the provisioning system.

1. Import the WebSphere 5.1 plug-in.

   See Adding the WebSphere Plug-In to the N1 Grid Service Provisioning System.

2. Configure the provisioning system's Master Server.

   See How to Configure the Master Server for the WebSphere Plug-in.

3. Set the WebSphere 5.1 session variables: WS_DEFAULT_USER and WS_DEFAULT_PASSWORD.

   These variables are used during standalone application server installation, deployment manager installation, and node federation.

   See Chapter 5, Session Variables, in N1 Grid Service Provisioning System 5.0 Plan and Component Developer’s Guide.

4. Prepare all hosts.

   The WebSphere 5.1 plug-in contains new system services that must be pushed out to all hosts in the provisioning system. See Preparing a Physical Host in N1 Grid Service Provisioning System 5.0 System Administration Guide.

5. Create a standalone WebSphere application server.

   See How to Install a Standalone WebSphere Application Server.

6. Create additional application server instances.

   See How to Create an Application Server Instance.

7. (Optional) Create the deployment manager.

   See How to Install a Deployment Manager.

8. If necessary, add each WebSphere application server to the deployment manager.

   See How to Add Nodes to the Deployment Manager.

9. (Optional) Create a cluster and add cluster members to the cluster.

   See How to Create a WebSphere Cluster and How to Add Cluster Members.

10. If necessary, configure the application's connection to the database.

    1. Configure the JDBC Provider.

       See How to Create a JDBC Provider Component.

    2. Configure the data source.

       See How to Create a Data Source Component.

11. Configure the Java Virtual Machine (JVM) component.

    See How to Configure the JVM Component.

12. Capture the application files.

13. Deploy applications to target application servers or clusters.

    An application can target either an application server or a cluster.

    See Installing an Enterprise Application.