Middleware Install and Configure

Edit online

This section describes and defines the processes and procedures that will be used to manage catalog requests to install and configure middleware.

Authorization

The creation and approval of a Middleware Install and Configure catalog request is complex and is therefore described as part of authorization process. These steps may be combined and in some organizations they are. Typically in smaller organizations some of the steps clearly will not be as detailed or be subjected to detailed reviews. However, in most large enterprises, checks and balances are in place to ensure the continuous business operations and these enterprises will have the steps that are described here. The tasks of the approvers will include verification of funding for the request. Multiple approvers may be required in some organizations. Notifications are sent to the service requisition user indicating the disposition of the approval request with reason codes.

Standard Authorization process to be used for any authorization and approval activities.

Fulfillment

This procedure begins when the project manager receives a signed service order that involves the installation of new IBM CUSTOMER servers. The procedure ends when all activities related to a Middleware Install and Configure catalog request are completed and the catalog request is closed.

The roles responsible for managing the request are the Project Manager, and the Server Build Coordinator, DBA, MQ Administrator and Websphere administrator roles (as required).

The following tasks are performed as part of the fulfillment process:
  1. 1. SB – Validate Database Requirements are met
    1. Validate memory requirements
    2. Create Required DB administration IDs
    3. Create any required DB client IDs
    4. Validate Disk Space requirements
    5. Create required filesystems directories or virtual disks with proper ACLs
    6. Validate OS level Requirements
    7. Validate SAN allocation requirements
    8. Validate TSM backup requirements
    9. Validate Network Connectivity
    10. Validate that required Firewall ports are open
  2. DBA – Perform Database Installation and Configuration
    1. Create Database instances and tables as per Database Design and Requirements Document
    2. Test DB client connectivity
  3. SB – Validate MQ Requirements are met (if required)
    1. Validate memory requirements
    2. Create Required MQ administration IDs
    3. Create any required MQ client IDs
    4. Validate Disk Space requirements
    5. Create required file systems directories or virtual disks with proper ACLs
    6. Validate OS level Requirements
    7. Validate SAN allocation requirements
    8. Validate TSM backup requirements
    9. Validate Network Connectivity
    10. Validate that required Firewall ports are open
  4. MQAdmin – Perform MQ Installation and Configuration (if required)
    1. Install MQ Application
    2. Create MQ Queues and Channels as per MQ Design and Requirements Document
    3. Test MQ client connectivity
  5. SB – Validate WAS Requirements are met (if required)
    1. Validate memory requirements
    2. Create Required WAS administration IDs
    3. Validate Disk Space requirements
    4. Create required filesystems directories or virtual disks with proper ACLs
    5. Validate OS level Requirements
    6. Validate SAN allocation requirements
    7. Validate TSM backup requirements
    8. Validate Network Connectivity
    9. Validate that required Firewall ports are open
  6. WASAdmin – Perform WAS Installation and Configuration (if required)
    1. Install and Configure WAS Application
    2. Test WAS connectivity
  7. SB – IBM Server Lockdown
    1. IBM Security Scan completed
  8. SB – Customer Server Lockdown
    1. Customer Server lockdown completed

Resource assignment

Direct assignment by analysts to specialist or the team queue. Resource assignment is described as part of the fulfillment activities as the assignments are made.

Role assignment

Note that roles are meant as logical groupings of tasks. They are not meant to match any particular organizational structure. Several roles may be performed by the same individual. A role may be split up among several individuals.

Table 1. Role assignment for Middleware Install and Configure
Role Responsibilities related to Server/Network Build Requests
Project Manager (Requester) Coordinates the front end of the server build request process and performs service request validation and closure activities.
Server Build Coordinator (Fulfiller Approver) Monitors all activities related to the server build service request from receipt of signed Service Order (SO) to closure of service request (SR).
SR Coordinator (Fulfiller) Receives service requests (SRs) from the server build service request queue, analyzes requests, assigns requests to appropriate queues, assigns SLA targets, assigns SR numbers, opens SR activities for assigned service providers.
Server Build Team (Fulfiller) Receives service request and performs all activities related to installing and configuring the server, coordinates with other functional areas that may be providing services for the request, makes updates to the configuration management and asset management systems, and performs lockdown activities and turnover activities.
Hardware Planning (Fulfiller) Receives hardware asset, creates/updates Inventory tool, installs and configures server hardware and cabling.
Capacity Planning (Fulfiller) Validates solution and makes updates to the form prior to the creation of the server build service request
SAN Engineer (Fulfiller) Participates in SAN planning activities, provides SAN implementation scripts, and performs SAN installation activities in coordination with the hardware planning team.
Tivoli Storage Management The TSM team is involved in planning activities, and provides a TSM option file for the servers during the fulfillment process.
Network Services (Fulfiller) IBM CUSTOMER NS network services provisions network switches and routers. IBM NS coordinates with facilities team to ensure physical connectivity is provided as specified.
Facilities Team (Fulfiller) The IBM CUSTOMER facilities team coordinates with IBM NS and SAN teams to provide physical connectivity and power for servers included in the service request.
Steady State Team (Fulfiller) The steady state team accepts the responsibility for managing the servers once they have been completely installed and configured by the other fulfillment teams.
DBA Team (Fulfiller) The DBA team is involved in database planning, installation, configuration, and testing activities.
MQAdmin (Fulfiller) The MQ Administration team is involved in MQ planning, installation, configuration, and testing activities.
Note: Alternative content fulfillment options and job plans exist which will direct requests to the Change Process Manager.