TSAM User Guide

Tivoli Service Automation Manager
Version 7.2.2
User's Guide
SC34-2656-00
Tivoli Service Automation Manager

Version 7.2.2
User's Guide
SC34-2656-00
Note Before using this information and the product it supports, read the information in Notices on page 73.
Edition notice This edition applies to IBM Tivoli Service Automation Manager Version 7 Release 2 Modification Level 2 (program number 5724W78), available as a licensed program product, and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC34-2610-04 and any previous editions. Order publications through your IBM representative or the IBM branch office serving your area. Publications are not stocked at the addresses given below. Address comments on this publication to: IBM Deutschland Research and Development GmbH IBM Systems and Technology Group Systems Software Development Dept. 2705, Bldg. 71032-16 Schoenaicher Str. 220 71032 Boeblingen Germany FAX (Germany): 07031 16 4240 FAX (other countries): (+49) 7031 16 4240 Make sure to include the following in your comment or note: v Title and order number of this book v Page number or topic related to your comment When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright IBM Corporation 2008, 2011. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v Preface . . . . . . . . . . . . . . vii
Who should read this information. . . . . . . vii What's new in this release . . . . . . . . . vii Useful links . . . . . . . . . . . . . . viii Support information . . . . . . . . . . . viii Getting technical training . . . . . . . . . ix Searching knowledge bases . . . . . . . . ix Searching the Internet . . . . . . . . . ix Using IBM Support Assistant . . . . . . ix Finding product fixes . . . . . . . . . ix Getting email notification of product fixes . . x Contacting IBM Software Support . . . . . . x Setting up a software maintenance contract . . x Determine the business impact . . . . . . xi Describe the problem and gather background information . . . . . . . . . . . . xi Submit the problem to IBM Software Support xii Additional software installation on the provisioned servers . . . . . . . . . . . . . . . Managing POWER LPAR provisioning with VMControl . . . . . . . . . . . . . Image management. . . . . . . . . . . Workload Deployer overview . . . . . . . . 21 . 22 . 22 . 23
Chapter 2. Using the Self-Service Virtual Server Management offerings. . 25

Submitting requests in the self-service user interface Approvals and notifications . . . . . . . . . Email notifications . . . . . . . . . . . Approving requests. . . . . . . . . . . Creating a project and adding virtual servers . . . Creating a project from a saved server image . . . Canceling a project . . . . . . . . . . . . Creating projects with a Workload Deployer pattern Canceling Workload Deployer pattern projects. . . Modifying project . . . . . . . . . . . . Adding virtual servers to an existing project . . Adding a server from a saved image . . . . . Modifying reservation dates . . . . . . . . Removing a virtual server . . . . . . . . Modifying server . . . . . . . . . . . . Modifying server resources . . . . . . . . Windows disk size modification after changing password . . . . . . . . . . Resetting a server password . . . . . . . . Starting a server . . . . . . . . . . . . Stopping a server . . . . . . . . . . . Restarting a server . . . . . . . . . . . Installing software on server. . . . . . . . Backing up and restoring server images . . . . . Creating server image . . . . . . . . . . Restoring a server from image . . . . . . . Removing saved images . . . . . . . . . Managing Image Library . . . . . . . . . . Registering VMware images . . . . . . . . Registering POWER LPAR images . . . . . . Registering Xen images . . . . . . . . . Registering KVM images . . . . . . . . . Registering z/VM image . . . . . . . . . Registering POWER LPAR images via IBM Systems Director VMControl . . . . . . . Unregistering an image in the Image Library . . Registering a VMControl image . . . . . . Registering a new image for a migrated resource pool . . . . . . . . . . . . . . . . Modifications to the registered images . . . Generated network segments . . . . . . Managing customers . . . . . . . . . . . Creating customers . . . . . . . . . . . Removing customers . . . . . . . . . . Managing users . . . . . . . . . . . . . Creating users . . . . . . . . . . . . 25 26 27 28 29 31 32 33 34 34 34 36 37 37 38 38 40 40 41 41 41 41 42 43 44 44 45 45 46 47 48 48 49 50 50 51 51 52 52 53 54 54 54
Chapter 1. Tivoli Service Automation Manager overview . . . . . . . . . . 1

Product components . . . . . . . . . . . . 2 Tivoli Service Automation Manager Installation Launchpad . . . . . . . . . . . . . . 2 Self-Service Virtual Server Management . . . . 2 User interfaces. . . . . . . . . . . . . 3 Applications in the administrative user interface . 3 Service Definitions application . . . . . . 4 Service Deployment Instances application . . 4 Resource Allocation applications . . . . . . 4 Monitoring Definition applications for WebSphere Cluster service . . . . . . . . 4 Situation Analysis application . . . . . . 5 Cloud Server Pool Administration application 5 Cloud Storage Pool Administration application 5 Cloud Network Administration application . . 5 Cloud Customer Administration application . . 6 Service Topology application . . . . . . . 7 Service Update Package application. . . . . 7 Service Topology Node applications . . . . 7 IT Topology Work Orders application . . . . 8 Auxiliary applications . . . . . . . . . 9 WebSphere Cluster Service. . . . . . . . . 9 Service topology node attributes . . . . . 13 Performance monitoring support for the WebSphere Cluster service . . . . . . . 15 Service structure . . . . . . . . . . . . . 17 Service provider support . . . . . . . . . . 18 Reporting function . . . . . . . . . . . . 19 Tivoli Service Automation Manager report types and content . . . . . . . . . . . . . 19 Tivoli Usage and Accounting Manager reporting function . . . . . . . . . . . . . . 20
Copyright IBM Corp. 2008, 2011
iii
Modifying user information . . . . . User modification conditions . . . Removing a user . . . . . . . . Creating new teams . . . . . . . Modifying team information. . . . . Removing a team . . . . . . . . Viewing requests . . . . . . . . . Viewing the details of a submitted request . Viewing and managing requests for approval Viewing projects . . . . . . . . . . Viewing and managing servers . . . . . Viewing Workload Deployer project details .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
56 57 57 58 58 59 59 60 61 61 62 62
Appendix. Accessibility features. . . . 71 Notices . . . . . . . . . . . . . . 73 Glossary . . . . . . . . . . . . . . 75

A. C. E. H. J . M P. R. S. T. V. W X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 75 75 75 75 75 76 76 76 76 77 77 77
Chapter 3. Using the WebSphere Cluster service . . . . . . . . . . . 65

Customizing the WebSphere Cluster service definition . . . . . . . . . . . . . . . Instantiating the WebSphere Cluster Service . . . Executing management plans for the WebSphere Cluster service . . . . . . . . . . . . . Adding server . . . . . . . . . . . . Removing server . . . . . . . . . . . Stopping WebSphere Deployment Manager . . . Deleting script logs from WebSphere Cluster servers 65 65 67 67 68 69 70
Trademarks and Service Marks . . . . 79 Index . . . . . . . . . . . . . . . 81
iv
Tivoli Service Automation Manager V7.2.2 User's Guide
Tables
1. 2. 3. 4. 5. Documentation links for Tivoli Service Automation Manager component products . . viii Uniqueness scopes for topology node attributes . . . . . . . . . . . . . 14 Uniqueness specifications for attribute names 14 Uniqueness resolution rule . . . . . . . 15 Summary of Tivoli Service Automation Manager Reports and Content . . . . . . 19 6. 7. 8. 9. Access to requests depending on the group . . . . . . . . . . Restrictions for the resources values Restrictions for the resources values OS Family and Version values . . security . . . . . . . . . . . . . . . . 26 29 35 46
vi
Preface
This publication documents how to use the online user interfaces of Tivoli Service Automation Manager.
Who should read this information

This information is intended for users of the online interfaces provided by Tivoli Service Automation Manager.
What's new in this release

This section provides a summary of new product features and enhancements to existing functions. Extensions Guide The new guide available for Tivoli Service Automation Manager version 7.2.2 documents how to build new or extend existing solutions in the areas of cloud computing or IT service management using the product. Service provider support The service provider feature introduced with Tivoli Service Automation Manager 7.2.2 allows for creating clouds that can be used by multiple customers. Resources can be used more efficiently and customers are able to support multiple internal organizations. The Cloud Customer Administration application allows you to configure new customers and manage their resources. New security model The service provider feature introduces a customer object, and new security levels. Moreover, instead of user roles, users can be assigned to multiple security groups. Support for additional storage on System p virtual machines Tivoli Service Automation Manager 7.2.2 offers a flexible and extensible way to assign additional storage resources to your System p virtual machines. The new Cloud Storage Pool Administration application enables you to easily manage your cloud storage pools. Reliability, availability, and serviceability (RAS) To support troubleshooting when using Tivoli Service Automation Manager, seven RAS functions are introduced in version 7.2.2, including three new types of BIRT reports, and documentation on best practices. New application for managing your cloud server pools The Cloud Server Pool Administration application enables you to create cloud server pools in two ways. You can either use the application to import the
vii
customized DCM items, or you can create a cloud server pool using the interface of the application. You can also use it to perform a variety of operations on the cloud server pools. Network changes You can define the network metadata of an image, for example how many and what kind of network interfaces the image requires. You can also use the extensible network model. The new Cloud Network Administration application enables you to manage network templates, network segments, subnetworks, virtual switch templates, and network configuration instances.
Useful links
Tivoli Service Automation Manager is a component product. Use the following topic to find more information about the related products and the requirements that must be met for them.
Table 1. Documentation links for Tivoli Service Automation Manager component products Product name IBM Tivoli Provisioning Manager, version 7.2.0.2
Documentation URL http://publib.boulder.ibm.com/infocenter/ tivihelp/v45r1/index.jsp?topic= %2Fcom.ibm.tivoli.tpm.doc%2Fwelcome %2Fic-homepage.html
IBM Tivoli Service Request Manager, version http://publib.boulder.ibm.com/infocenter/ 7.2.0.1 tivihelp/v32r1/index.jsp?topic= %2Fcom.ibm.srm.doc%2Fsrm_welcome.htm Maximo Base Services http://publib.boulder.ibm.com/infocenter/ tivihelp/v3r1/index.jsp?topic= %2Fcom.ibm.mam.doc_7.1 %2Fmam_welcome.htm http://publib.boulder.ibm.com/infocenter/ tivihelp/v2r1/index.jsp?topic= %2Fcom.ibm.IBMDS.doc%2Fwelcome.htm http://publib.boulder.ibm.com/infocenter/ db2luw/v9r5/topic/com.ibm.db2.luw.doc/ welcome.html http://publib.boulder.ibm.com/infocenter/ wasinfo/v6r1/topic/ com.ibm.websphere.base.doc/info/aes/ae/ welcome_base61.html
IBM Tivoli Directory Server, version 6.3
DB2, version 9.5
IBM WebSphere Application Server Network Deployment, version 6.1
Support information
You can find support information for IBM products from a variety of sources. v Getting technical training on page ix v Searching knowledge bases on page ix v Contacting IBM Software Support on page x
viii
Getting technical training

Information about Tivoli technical training courses is available online. Go to http://www.ibm.com/software/tivoli/education/.
Searching knowledge bases

If you have a problem with Tivoli Service Automation Manager, search through one of the many available knowledge bases. You can begin with the IT Service Management Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/index.jsp.
Searching the Internet

If you cannot find an answer to your question in the IT Service Management information center, search the Internet for the latest, most complete information to help you resolve your problem. To search multiple Internet resources, go to the IBM Tivoli Support website. From there, you can search a number of resources, including: v IBM technotes v IBM downloads v IBM Redbooks If you still cannot find a solution to the problem, you can search forums and newsgroups on the Internet for the latest information to help you resolve it.
Using IBM Support Assistant

At no additional cost, you can install on any workstation the IBM Support Assistant, a stand-alone application. You can then enhance the application by installing product-specific plug-in modules for the IBM products that you use. The IBM Support Assistant helps you gather support information when you need to open a problem management record (PMR), which you can then use to track the problem. The product-specific plug-in modules provide you with the following resources: v Support links v Education links v Ability to submit problem management reports For more information, see the IBM Support Assistant Web site at http://www-01.ibm.com/software/support/isa/.
Finding product fixes

A product fix might be available from the IBM Software Support website.
About this task

Check the website to determine which fixes are available for your product.
Procedure
1. Find the Tivoli Service Automation Manager product at http://www.ibm.com/ software/tivoli/products/. 2. Click the Support Pages link for the product.
Preface
ix
3. Click Fixes for a list of fixes for your product. 4. Click the name of a fix to read the description and download the fix.
Getting email notification of product fixes

You can get notifications about fixes and other news about IBM products.
Procedure
1. From the support page for any IBM product, click My support in the upper-right corner of the page. 2. Optional: If you have not registered, click Register in the upper-right corner of the support page to set up your user ID and password. 3. Sign in to My support. 4. On the My support page, click Edit profiles in the left navigation pane, and scroll to Select Mail Preferences. Select a product family and check the appropriate boxes for the type of information you want. 5. Click Submit. 6. For email notification for other products, repeat steps 4 and 5.
Contacting IBM Software Support

You can contact IBM Software Support if you have an active IBM software maintenance contract and if you are authorized to submit problems to IBM.
About this task

Before you contact IBM Software Support, follow these steps:
Procedure
1. Set up a software maintenance contract. 2. Determine the business impact of your problem. 3. Describe your problem and gather background information.
What to do next
Then see Submit the problem to IBM Software Support on page xii for information on contacting IBM Software Support.
Setting up a software maintenance contract

To be able to submit a problem to IBM, you need to have a software maintenance contract. The type of contract that you need depends on the type of product you have.
Procedure
v For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as IBM DB2 and IBM WebSphere products that run on Microsoft Windows or UNIX operating systems), enroll in IBM Passport Advantage: Enrolling online: Go to the Passport Advantage Web page at http://www.ibm.com/software/lotus/passportadvantage/, click How to enroll, and follow the instructions.
Enrolling by Telephone: For the telephone number for your country, go to the IBM Software Support Handbook webpage at http:// www14.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html and click Contacts. v For IBM eServer software products, you can purchase a software maintenance agreement by working directly with an IBM marketing representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical support advantage webpage at http://www.ibm.com/servers/eserver/techsupport.html.
What to do next
If you are not sure which type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. For a list of support telephone numbers for your location, go to the Software Support Handbook page at http://www14.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html.
Determine the business impact

When you report a problem to IBM, you are asked to supply a severity level. In order to provide this information, understand and assess the business impact of the problem you are reporting.
Severity 1 Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Significant business impact: The program is usable but is severely limited. Some business impact: The program is usable with less significant features (not critical to operations) unavailable. Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented.
Severity 2 Severity 3 Severity 4
Describe the problem and gather background information

When explaining a problem to IBM, it is helpful to be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: v What software versions were you running when the problem occurred? v Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. v Can the problem be recreated? If so, what steps led to the failure? v Have any changes been made to the system? For example, hardware, operating system, networking software, and so on. v Are you currently using a workaround for this problem? If so, be prepared to explain it when you report the problem.
Preface
xi
Submit the problem to IBM Software Support

You can submit the problem to IBM Software Support online or by telephone. Online Go to the IBM Software Support Web site at http://www.ibm.com/ software/support/probsub.html. Enter your information into the appropriate problem submission tool. By Telephone For the telephone number to call in your country, go to the contacts page of the IBM Software Support Handbook at http:// www14.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html. If the problem that you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. If a workaround is possible, IBM Software Support provides one for you to implement until the APAR is resolved and a fix is delivered.
xii
Chapter 1. Tivoli Service Automation Manager overview

Tivoli Service Automation Manager assists in the automated provisioning, management, and deprovisioning of cloud resources, comprised of hardware servers, networks, operating systems, middleware, and application-level software. Several virtualization environments (hypervisors) are supported in the process of individual virtual server provisioning.
Tivoli Service Automation Manager also provides management support for services consisting of a specific set of middleware, in combination with AIX, and Linux (System x and System z). IBM provides many automation and best-practice service definition templates, including specialized job plans or workflows. Tivoli Service Automation Manager makes use of the entire spectrum of Tivoli process automation engine tools. Tivoli Service Automation Manager helps you define and automate services that are lifecycle oriented, for example, a service to establish and administer an IT server network for a limited period of time, to satisfy increased demand for processing capacity or to serve as a test environment. Predefined service definitions determine the overall framework for the services. The actual service instances are requested using these service definitions. The Self-Service Virtual Server Management environment, is used by the cloud users to request provisioning and manage the virtual environments. Tivoli Service Automation Manager uses IBM Service Management and the Tivoli process automation engine as an integration platform. IBM Service Management is an approach designed to automate and simplify the management of business services. It concentrates on four areas: v v v v Technology integration and standards Improved collaboration among IT people spread across organizational silos Best-practices based process modules for automated process execution Sharing of business-critical IT information to improve decision making
Tivoli Service Automation Manager offers the following standard service environments and definitions: Self-Service Virtual Server Management environment In this service environment, which is a collection of service offerings, users request the provisioning of projects comprising virtual servers. The service environment has an intuitive self-service user interface with Web 2.0 technology for enhanced interactive feedback. An administrator function is also provided. WebSphere Cluster Service This optional, separately priced service provisions and manages a WebSphere cluster.
Product components
This section provides the overview the components of Tivoli Service Automation Manager.
Tivoli Service Automation Manager Installation Launchpad

The Tivoli Service Automation Manager Installation Launchpad guides the user through the installation process. For details, see "Installing Tivoli Service Automation Manager" in the Installation and Administration Guide.
Self-Service Virtual Server Management

Tivoli Service Automation Manager provides support for user-initiated provisioning and management of virtual servers on System x, System p, or System z. The product also supports the IBM CloudBurst and IBM Workload Deployer products, which are based on System x hardware. The self-service environment is supported by the self-service user interface. The Self-Service Virtual Server Management functional addresses a long-standing need for efficient management of self-service deployment of virtual servers and associated software. Using a set of simple, point-and-click tools, the user can select a software stack and have the software automatically installed or uninstalled in a virtual host that is automatically provisioned. These tools integrate with Tivoli Service Request Manager to provide a self-service portal for reserving, provisioning, recycling, and modifying virtual servers, and working with server images, in the following platform environments, which are a part of a virtualized non-production lab (VNPL): v VMware on System x (also used in the IBM CloudBurst and IBM Workload Deployer products) v Xen on System x v v v v KVM on System x LPARs on Power Systems z/VM guests on System z WebSphere CloudBurst Appliance
This function ensures the integrity of fulfillment operations that involve a wide range of resource actions: v Creating virtual servers as part of a new deployment project or adding virtual servers to an existing project, with optional scheduling for implementation at some future time v For each virtual server created, installing a software image that includes an operating system and other applications that are associated with the image. v Installing additional software on the provisioned virtual machines v Deleting a virtual server when it is no longer needed, freeing up resources for other servers v Saving virtual server images and restoring the servers to their previous state v Saving and restoring images of servers within the project. v Deleting individual servers. v Canceling a project and deleting all of the associated virtual servers. v Starting, stopping, and restarting virtual servers.
v Resetting the administrator password on a virtual server. v Adding, removing, and modifying users and user teams. You use these capabilities to achieve incremental value by adopting a self-service virtual server provisioning process, growing and adapting the process at your own pace, and adding task automation to further reduce labor costs around defined provisioning needs. Before users in the data center can create and provision virtual servers, administrators perform a set of setup tasks, including configuring the integration, setting up the virtualization environments managed by the various hypervisors, and running a Tivoli Provisioning Manager discovery to find servers and images across the data center. After this initial setup has been completed, the administrator associates the virtual server offerings with Tivoli Provisioning Manager virtual server templates. The Image Library is used as the source for software images to be used in provisioning the virtual servers.
User interfaces
Tivoli Service Automation Manager provides two options for user interaction: a self-service user interface and an administrative user interface. The administrative user interface is the standard interface within the Tivoli process automation engine framework (formerly known as Maximo). It is intended primarily for service and system administrators who perform the installation, upgrade, configuration and administration tasks. The self-service user interface is tailored to users of self-service offerings and administrators. It is based on the Web 2.0 standard, which enables for the context-sensitive and real-time display updating based on the current entry or selection made by the user. The result is a faster access to the necessary information without having to go through a sequence of clicks, dialogs, and panels. Related tasks: Submitting requests in the self-service user interface on page 25 Log on to the self-service user interface, where you can access the offerings and request provisioning.
Applications in the administrative user interface

Many of the components of Tivoli Service Automation Manager are implemented in the form of applications within the administrative user interface. This section describes the available applications and their functions.
Chapter 1. Product overview
Service Definitions application

You use the Service Definitions application to create or modify a service definition and to instantiate services based on that definition. You can also customize the service definition delivered with Tivoli Service Automation Manager to suit your requirements more precisely. For services that are instantiated (that is, represented with actual hardware) based on an approved service definition, the Service Definitions application triggers the instantiation workflow. Self-Service Virtual Server Management, however, employs an interactive process for instantiation that is carried out using the Service Request Manager.
Service Deployment Instances application

You use the Service Deployment Instances application to manage existing deployments (physical implementations) of a service.
Resource Allocation applications

You use Resource Allocation applications allow you to document and review requirements and allocate configuration items (CIs). Resources are allocated to fulfill document requirements or allocate configuration items. There are two purposes for allocating resources. v Document requirements Users can insert requirement items to specify the requirements the CI has to fulfill. These items are classified using the standard Tivoli process automation engine classification mechanism, which means that the user can reuse predefined forms. v Allocate configuration items (CIs) Once the requirements are set and approved, a CI has to be allocated that matches those requirements. The user can review and change the set requirements. Using this information, they can select a CI that matches. Automated filtering helps the user find the appropriate CI. The Resource Allocation applications include: v Resource Allocation Record v Resource Allocation for Service Deployment Instance
Monitoring Definition applications for WebSphere Cluster service

If you need to modify the service definition delivered with Tivoli Service Automation Manager to match your requirements for performance monitoring, you can change the monitoring definition using the set of Monitoring Definition applications. Note: This section pertains only to performance monitoring within the scope of the Tivoli Service Automation Manager WebSphere Cluster service. It does not describe displaying resource usage data collected by Tivoli Monitoring agents that are installed on servers provisioned using the Self-Service Virtual Server Management component. Performance monitoring is supported in combination with IBM Tivoli Monitoring on distributed platforms (Linux on System x, System p, and System z, and AIX). The Monitoring Definition applications refer to the monitoring environment being used with respect to any given service definition and service deployment instance.
IBM Tivoli Monitoring must be installed separately. It is no longer offered as an installation option for Tivoli Service Automation Manager. Alternatively, a separately installed Tivoli Monitoring environment can be used. For details on setting up IBM Tivoli Monitoring, see the documentation for this product http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=/ com.ibm.itm.doc/toc.xml). There are three monitoring related applications: v Monitoring Definition v Monitoring Definition Instantiation v Monitoring Definition Instances The handling of performance-related situations detected by the monitoring agents in a deployed landscape is provided by the Situation Analysis application.
Situation Analysis application

You use the Situation Analysis application to review the context of the service deployment instance in which a performance-related event occurred, including the topology of the service instance, the CIs involved, and the monitoring definitions. For an overview of the situation analysis function, see Performance monitoring support for the WebSphere Cluster service on page 15. Note: This information pertains only to performance monitoring within the scope of the Tivoli Service Automation Manager WebSphere Cluster service. It is not related to displaying resource usage data collected by Tivoli Monitoring agents that are installed on servers provisioned using the Self-Service Virtual Server Management component.
Cloud Server Pool Administration application

Use this application to define and configure cloud server pools after the installation of Tivoli Service Automation Manager. This application helps you define and configure a cloud server pool for each back end on which you want to provision servers.
Cloud Storage Pool Administration application

Use this application to create and configure cloud storage pools. Cloud storage pools are a flexible solution to add additional storage to your provisioned servers. They are a collection of storage resources for additional disks that can be assigned to a newly created image if you need more storage space than just the boot disk.
Cloud Network Administration application

This application is used to perform cloud configurations and to manage them in a production environment. The Cloud Network Administration application is one of the applications that are used during the Tivoli Service Automation Manager configuration process. Use it after performing the configuration of the backend resources and of the storage pool. The network configurations handled by this application include: v Importing network Data Center Model (DCM) objects and parameters that describe subnetworks and virtual switches
v Importing network templates that contain predefined network configuration parameters After performing these initial configurations and setting up a production environment, Tivoli Service Automation Manager configurations change over time. The Cloud Network Administration application helps you manage these changes by handling the following tasks: v Importing a new revision of a network template v Changing the status of a network template v Deleting a network template v Listing network templates v Showing details of a network template
Cloud Customer Administration application

The Cloud Customer Administration application provides the administrator with an overview of the allocated resources of a specific customer. The application is organized into multiple tabs. These tabs show the resources, requests, and reservations of the selected customer. The main purpose of the Cloud Customer Administration application is to maintain customers individually. The administrator can also perform configuration tasks for individual customers and access other applications that serve this purpose. Tasks that are available within the Cloud Customer Administration application include: v Viewing customer-specific information (users, teams, submitted requests, projects, saved images, reserved resources, and quotas) v Creating and removing customer templates and customers v Assigning resources to customers and returning resources v Adding, deleting, activating, and deactivating quotas and limits The application supports three types of customers: Cloud Template (type=CT) This type is used as a template for new customers. The cloud template is created and modified in the administrative user interface. Then it becomes available in the self-service interface as part of the Create Customer request. A template customer is not operational, which means that no user can belong to a customer of type CT. Cloud Customer (type=CC) This customer type can be created in the self-service user interface and then configured or modified in the administrative user interface. If customer templates are configured, you can use them to create new customers of type CC. A cloud customer is operational. Users assigned to it can request and use resources. One user can be assigned to one customer only, and that user can never be migrated between customers. When a user is assigned to a customer, that user can access and request resources that are assigned to that customer. Service Provider (type=SP) A predefined global customer that is delivered with Tivoli Service Automation Manager 7.2.2, with a default name PMRDPCUST. If no other customers are defined, all users belong to this default customer. New customers of type SP cannot be created.
The application is useful if the customer reports a problem with the cloud. The administrative user can view and find the resources related to that customer. For example, if the customer reports that a service request on a project failed, the administrator can easily navigate to the list of all service requests and projects related to this customer. From this application, the administrator can navigate to the service request application to get further details about the specific service request. For specific information about the features of each tab that is available in this application, click the ? Help button within the application.
Service Topology application

The Service Topology application is the main application for viewing and editing service topology templates and instances. If you need to modify the service definition delivered with Tivoli Service Automation Manager to exactly match your requirements, you can change the service topology using this application. The Service Topology application operates mainly on the topology and topology node data model objects. You use it to view and edit the following: v Name and description of a topology v Nodes of a topology v Basic relationships between nodes (parent-child relationships) v Monitoring agent assignments for nodes v Resource allocation records for nodes
Service Update Package application

You use this application to manage existing Service Update Packages and deploy them on one or more Service Definitions or Service Deployment Instances.
Service Topology Node applications

You use these applications to work with topology node objects. These applications provide more sophisticated and detailed ways for browsing and editing topology node objects than available with the Service Topology application. The applications in this category include: v Service Topology Node v Service Topology Node Operation v Node Attribute Uniqueness Violations v Co-Location Editor v Topology Customization In addition to the node viewing capabilities provided by the Service Topology application, it is possible to change relationships between nodes. For one topology node, you can display all related nodes (direct parent or child, or otherwise related nodes) in a list. A child node can be selected and set as the main object for the application in order to inspect the child node. In this way, you can walk through and inspect complete hierarchies of topology nodes. This application also allows you to define custom relationships (in contrast to standard parent-child relationships) between nodes. Use this when relationships between nodes have to be defined that cannot be modeled using standard parent-child relationships.
IT Topology Work Orders application

The IT Topology Work Orders application displays the status of an IT topology work order. This application can be accessed either in the Work Orders tab of the Service Deployment Instances application or when the error handling workflow creates an assignment due to an error during processing. An IT topology work order is used as a frame of reference during management plan processing. It contains the state of the work order and references to the input and output definitions for work order operation. When the management plan is being executed, there is one work order that contains the state of the overall management plan. This work order is referred to as the top IT topology work order. When any operation from a management plan starts, another IT topology work order, the operation work order, is created for the operation and its state. Workflows that run within the context of an operation focus on the corresponding operation work order. Many Tivoli Service Automation Manager operations use a common main workflow for tasks. This workflow is called the error handling workflow. This workflow calls the operation-specific implementation workflow. If the workflow returns an error by ending via the negative-action connection line, the error handling workflow provides an assignment to the operator entitled 'A Workflow Failed'. The operation work order is opened in the IT Topology Work Orders application. The problem is described in the Messages tab of the application. The operator can then route the workflow assignment and take one of the following actions: v Continue by ignoring the failed workflow and processing the remaining steps. This option can be useful if the failed task was already completed manually by the operator or if it can be omitted. Tivoli Service Automation Manager continues processing by starting the next operation. v Continue by re-executing the failed workflow. This option may be useful if errors occur due to temporary problems (such as a temporary network outage). Tivoli Service Automation Manager restarts the same operation with the current input values. v Continue by ignoring the failed workflow and canceling all remaining steps. This option can be used if continuing the management plan is no longer practical. Note: Tivoli Service Automation Manager does not perform a cleanup in this case. Canceling means that all remaining job plans and tasks are still executed, but each job task is considered completed when it is encountered, meaning that the corresponding workflow is skipped. If an initial management plan is canceled by the operator, the service deployment instance state is set to 'Canceled'. The user has to manually clean up all the changes that occurred up to this assignment. This includes topology changes, such as in the case of a WebSphere Add Server workflow. It also includes changes made to the managed environment or Tivoli Provisioning Manager. You can also use the IT Topology Work Orders application to suspend and resume work orders and send notifications to users about issues related to the current management plan.
Auxiliary applications
Several auxiliary applications support special-purpose editing or process control functions: v Service Automation Manager v Management Plan Input Parameters v Management Plan Target Selection v Service Topology Customization Editor
WebSphere Cluster Service

The WebSphere Cluster Service allows you to provision the IBM WebSphere Application Server Network Deployment V6.1 product and manage its life cycle. This section is relevant only if you have purchased and installed the Tivoli Service Automation Manager for WebSphere Application Server chargeable component. See "Installing Tivoli Service Automation Manager for WebSphere Application Server" in the Installation and Administration Guide for instructions on installing this service. It can be installed either directly after the main Tivoli Service Automation Manager installation or at a later time. The WebSphere Cluster Service provisions a WebSphere cluster consisting of the following elements: v WebSphere Cell v WebSphere Network Deployment (ND) Manager v WebSphere Network Deployment managed node v WebSphere Application Server instance v WebSphere Cluster v HTTP Server node This service comprises the following components: v WebSphere Cluster Service definition, comprising best-practice WebSphere topology templates and management plans v Updated automation package (.tcdriver file), which enables Tivoli Provisioning Manager to provision WebSphere server instances together with Tivoli Service Automation Manager. Also included are sample XML files to configure Tivoli Provisioning Manager to use the WebSphere Cluster service v Scripts that perform changes in the WebSphere Application Server when they are executed from Tivoli Service Automation Manager using the Script Adapter The management plans include internal plans for creating a WebSphere cell or adding a managed node to an existing cell. Plans for basic management tasks in the life cycle of the service, such as starting and stopping individual components, are also provided. The WebSphere Cluster Service integrates very tightly into basic Tivoli Service Automation Manager concepts and applications, utilizing the existing Service Definitions and Service Topologies applications and processes such as Approval. The following WebSphere components are part of each service deployment instance. These components are modeled as individual topology nodes: v Each instance contains and manages a single WebSphere cluster. v The management instance for a cell, the Deployment Manager, can be provisioned and is used heavily. v There is at least one managed node that can be provisioned and managed.
v Each managed node contains a single application server instance, which is also called a cluster member. v Provisioning and management of an IBM HTTP server instance are also supported.
WebSphere topology
In the following sections, the types of topology nodes used in the WebSphere cluster service are listed. Each of these node types is defined by a Service Request Manager classification that declares the attributes. Operations for topology nodes are summarized for each type of node as applicable. WebSphere Cell A WebSphere ND Deployment Manager node that manages the cell and all of its components, one or more WebSphere ND managed nodes hosting application server instances, and a number of IBM HTTP Server nodes representing the Web tier of the environment. Furthermore, a cell can define multiple WebSphere clusters that group similar application server instances. Deployment Manager A special type of WebSphere node for controlling a WebSphere cell and all of its components. WebSphere components are configured within a cell is done using the Deployment Manager node. The following operations are supported: v Installing WebSphere ND on a server and creating a Deployment Manager profile (and thus a Deployment Manager node). This implicitly defines a WebSphere cell that is managed by the new Deployment Manager v Defining a new WebSphere cluster within a cell. The cluster is initially created without members v Creating a new cluster member (application server instance) for an existing cluster on an existing WebSphere managed node v Start the deployment manager. The deployment manager has to be started for most other operations to succeed. This is done during initial provisioning. v Stopping the deployment manager v Starting a complete cluster, that is all members within a cluster v Stopping a complete cluster, that is all members within a cluster v Starting a managed node and all cluster members that are managed by this node v Stopping a managed node and all cluster members that are managed by this node. This might be required if the server this node runs on needs maintenance v Starting the application server instance v Stopping the application server instance v Generating the plug-in configuration for the web servers configured for a cell and propagate it to the web server. The web server must then route web traffic based on the new configuration, for example handling load for newly deployed applications or routing to newly created cluster members
10
v If you use Tivoli Monitoring in conjunction with Tivoli Service Automation Manager, install a Tivoli Monitoring agent on the server this instance runs on v If you use Tivoli Monitoring in conjunction with Tivoli Service Automation Manager, uninstall a Tivoli Monitoring agent from the server this instance runs on v Enabling administrative security on this managed node. You can set a user name and password for the administrative console of the deployment manager, for example v Incorporating a managed node in the cell that is managed by this Deployment Manager. In this way, the Deployment Manager can introduce changes to the given node v Removing the given managed node from this cell v Copying the HTTP Server configuration script that was created by the HTTP Server installation to the Deployment Manager, so that it can be invoked to make the HTTP Server known to the Deployment Manager v Uninstalling WebSphere from a server Managed Node <n> A managed node within a WebSphere cell. The node is managed/controlled by the cell Deployment Manager and does not have its own management interface (such as an administration console). Managed nodes host application server instances for deploying J2EE applications. The following operations are supported: v Installing WebSphere ND on a server and creating a managed node profile (and thus a WebSphere managed node). v Installing a Tivoli Monitoring agent on the server this instance runs on. This is only applicable if you use Tivoli Monitoring in conjunction with Tivoli Service Automation Manager. v Uninstalling a Tivoli Monitoring agent from the server this instance runs on. This is only applicable if you use Tivoli Monitoring in conjunction with Tivoli Service Automation Manager. WebSphere Application Server instance A WebSphere Application Server instance is an implementation of the WebSphere Application Server. It is a container for hosting J2EE applications and corresponds to one instance of a Java Virtual Machine on the respective node. Application server instances can be hosted on managed or stand-alone WebSphere nodes; they cannot be hosted by Deployment Manager nodes, that is, they cannot be defined within Deployment Manager profiles. WebSphere Cluster A WebSphere cluster is a logical grouping defined within a WebSphere cell for managing similar application server instances, that is, those of equal configuration. The typical reasons for clustering are load balancing and high availability. IBM HTTP Server node An IBM HTTP Server is the web server product of the WebSphere family. In a clustered environment, instances of HTTP Server form the web or front-end tier of a J2EE application-hosting landscape and distribute HTTP traffic among members of a cluster of WebSphere Application Servers. Supported operations are as follows: v Installing and configuring IBM HTTP Server on a server.
11
v Starting this HTTP Server instance. v Install a Tivoli Monitoring agent on the server this instance runs on. This is only applicable if you use Tivoli Monitoring in conjunction with Tivoli Service Automation Manager. v Uninstall a Tivoli Monitoring agent on the server this instance runs on. This is only applicable if you use Tivoli Monitoring in conjunction with Tivoli Service Automation Manager. DBMS server A database management server. This is used in the optional Tivoli Monitoring integration, such that events reported by this database server can be correlated to a service deployment instance. Database instance A database instance managed by a DBMS server. This is used in the optional Tivoli Monitoring integration, such that events detected by this database can be correlated to a service deployment instance.
Management plans
The following processes can be performed on a deployed instance of the WebSphere Cluster Service: Add Server Adds a WebSphere managed node to a cell and creates a member that is added to an existing cluster Remove Server Removes an existing member from a cluster and deprovisions its associated WebSphere managed node from a cell Start WebSphere Deployment Manager Starts the Deployment Manager for this service deployment instance Stop WebSphere Deployment Manager Stops the Deployment Manager for this service deployment instance Start WebSphere Node Starts a complete WebSphere managed node, including all application server instances hosted by the node Stop WebSphere Node Stops a complete WebSphere managed node, including all application server instances hosted by the node Start WebSphere Cluster Member Starts a specific application server instance on a managed node Stop WebSphere Cluster Member Stops a specific application server instance on a managed node Start WebSphere Cluster Starts a complete WebSphere cluster, that is, all of the members of the cluster Stop WebSphere Cluster Stops a complete WebSphere cluster, that is, all of the members of the cluster
12
Service topology node attributes

The service topology is the set of individual hardware and software components that constitute the defined or instantiated service. Each element of the topology is referred to as a node. The following section describes a topology using the WebSphere Cluster Service as a sample framework. In the WebSphere Cluster Service, the main logical component of the environment to be managed is a WebSphere Cell. Consequently, the top node in the hierarchy is a WebSphere Cell node. A WebSphere Cell contains an IBM HTTP Server, a Deployment Manager, and one or more managed nodes. A cell can also define multiple clusters. All of these nodes are direct children of the WebSphere Cell node. A WAS ND managed node hosts WebSphere Application Server Instances. Thus, the managed node has a child designated as "AppSrv Instance". All nodes that require hardware resources for deployment have associated resource allocation templates that define what the resource must look like. To support the configuration of more than one topology node on a physical server, nodes that are eligible for co-location can be assigned to a co-location group. That group is then assigned to the physical resource. Nodes not assigned to a group are classified as stand-alone nodes. Nodes in a co-location group can later be selectively deleted from the group, or an entire group can be dissolved, in each case the affected nodes are returned to stand-alone status. The WebSphere Cell contains one or more managed nodes. Each node has three special attributes: v Minimum cardinality v Maximum cardinality v Maximum cardinality unlimited These attributes are used to define how often a node can occur in an instance of the topology. Other attributes indicate whether the node participates in performance monitoring and whether it needs a hardware resource to run, for example. Since selected nodes in a service topology can occur multiple times, a mechanism is required to ensure that the attributes that describe these nodes are unique across the topology or even across all services. Node attributes must allow for the definition of a uniqueness scope in order to prevent conflicts with attributes of other nodes in a topology. For example, all nodes within a topology should have a unique name. WebSphere Application Server nodes that are deployed on the same host must also have unique, non-conflicting port number assignments. A simple resolution of conflicts is provided through placeholders in character-string-type attributes that are replaced with numbers that are automatically incremented at instantiation time. These numbers are replaced and incremented on a per-topology basis. A more sophisticated and granular handling of attributes (both string and numeric) is necessary, for example, for port number assignments. In general, automated resolution of conflicts is done based on numeric variable substitution according to user-defined rules (see below). With numeric attributes, the entire attribute is subject to substitution. With string attributes, placeholders for such numeric variables are placed in the string. It is possible to insert multiple placeholders into one string, and each of these is replaced. If placeholders in one string are identical,
13
the same value is inserted for each occurrence in a string. The complete identifier of such a placeholder variable comprises the fully qualified name (including node classification ID) of the attribute (see also Attribute Name Handling below) and the name of the placeholder variable. For numeric attributes, the fully-qualified name of the attribute itself identifies the replacement variable. Uniqueness scope: A uniqueness_scope parameter can be set for all specification attributes that defines which type of uniqueness is to be enforced for that parameter of a node within a topology. The following uniqueness scopes can be set:
Table 2. Uniqueness scopes for topology node attributes Uniqueness scope None Global Service Definition Topology Meaning Uniqueness not enforced (default scope) Uniqueness is enforced across all topology nodes known to the system Uniqueness is enforced across all topologies of service deployment instances derived from one service definition Uniqueness is enforced within the topology. The value of that attribute of a node must be unique within the entire topology, meaning that no other node in the same topology can have the same value for that attribute Uniqueness is enforced on a per-host basis. Nodes deployed on the same host must not define the value for an attribute Uniqueness is enforced in a user-defined group; once defined, a group can be referenced by attributes of all nodes, and uniqueness is enforced in the scope of the selected group
Host Group
Attribute name handling: The user can define how the name of an attribute is treated with respect to uniqueness, that is how the uniqueness is enforced between the attributes of one node and the attributes of other nodes. The following types of attributes handling can be set:
Table 3. Uniqueness specifications for attribute names Attribute name uniqueness Exact Wildcard Meaning Only values of identically named attributes are considered for uniqueness handling (default) An expression containing wildcard characters (%) can be specified to define a range of attributes that are considered for uniqueness handling. Not only can the Wildcard specification can be used not only for selecting a wider range of actual attribute names, it can also be used to select attributes from multiple classifications. For example, if attributes PORT_ONE and PORT_TWO are to be correlated during uniqueness handling (to prevent port assignment conflicts), the wildcard expression PORT_% could be used
14
Table 3. Uniqueness specifications for attribute names (continued) Attribute name uniqueness Alias group Meaning Arbitrarily named attributes can be assigned to user-defined alias groups. All attributes that belong to the same alias group are then considered for uniqueness handling. This allows for correlating attributes, for example, of different node classifications, that would be correlatable by name. For example, an attribute of a WebSphere node named SOAP_PORT (a TCP/IP port) and an attribute BOOTSTRAP_ADDRESS (also a TCP/IP port) of an Application Server instance could be assigned to an alias group NETWORK_PORTS with host scope in order to keep allocated TCP/IP ports unique on a host.
Uniqueness resolution rules: Within the user-defined uniqueness scope of an attribute, variables are substituted according to a set of rules that define how substitution values are calculated. Resolution is always performed on the basis of a numeric calculation. There is currently one rule defined:
Table 4. Uniqueness resolution rule Uniqueness resolution rule Increment Meaning Increments the substitution variable by a user-defined step value (default 1) starting at a certain base value (default 1). A unique value is calculated by obtaining the highest value for an existing attribute and incrementing it to assign the value to the new attribute. The value of a numeric attribute defines the base value and overrides any such value specified in the rule.
Numeric placeholders in character strings are treated the same way as numeric attributes except that the base value is always the one defined in the rule. Identically named placeholders within one string are assigned the same value. For text-only attributes without placeholders, the uniqueness requirements can be defined, but no automatic uniqueness resolution is performed. Tivoli Service Automation Manager detects violations of the uniqueness rules for attributes and displays the affected parts of the topology in the Node Attribute Uniqueness Violations panel.
Performance monitoring support for the WebSphere Cluster service

You can also use the Tivoli Service Automation Manager to install performance monitoring software (agents) on the servers it provisions. This software detects situations that cause degraded performance. Tivoli Service Automation Manager reacts to such situations by presenting the user with options to analyze and resolve the problems based on procedures that have been accepted as recommended practices. Note: This section applies only to the Tivoli Service Automation Manager WebSphere Cluster service. It does not apply to the Tivoli Monitoring based resource usage collection functions offered with the Self-Service Virtual Server Provisioning component.
15
Each Tivoli Service Automation Manager service definition can have an associated monitoring definition. These definitions provide the framework for implementing the monitoring agents and controlling which types of events it will react to. If you need to modify the service definition delivered with Tivoli Service Automation Manager to suit your requirements for performance monitoring, you can change it using the set of Monitoring Definition applications. Performance monitoring is supported in combination with IBM Tivoli Monitoring on distributed platforms (Linux on System x, System p, and System z, and AIX). The Monitoring Definition applications refer to the monitoring environment being used with respect to any given service definition and service deployment instance. IBM Tivoli Monitoring must be installed separately. It is no longer offered as an installation option for Tivoli Service Automation Manager. For details on setting up IBM Tivoli Monitoring, see the documentation for this product (http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/ index.jsp?toc=/com.ibm.itm.doc/toc.xml). The Situation Analysis application handles the situations detected by the monitoring agents in a deployed landscape. When a monitoring agent detects a situation, it triggers the execution of a workflow within Tivoli Service Automation Manager. The Situation Analysis application, which is part of this workflow, is called and assigned to the user with the role corresponding to the domain that applies to the agent and situation. For example, if the scenario is part of the domain AIX or DB2, the application execution within the workflow is assigned to the respective AIX administrator or DB2 administrator role. A customer can also add a new domain by enhancing the situation analysis workflow, adding new roles and adding new values to the domain. An assignment to analyze the event appears in the inbox of the corresponding user within the Start Center panel of the Tivoli process automation engine user interface. When the user clicks on this assignment, the application to analyze the event opens. The following categories of information are shown: v Information about the situation, including: The system on which the situation occurred The domain the situation is related to (WAS, DB2, AIX, LINUX) The name of the situation v One or more service deployment instances that are candidates for the situation indicated. You can then browse the entire context of the instance within which the situation occurred, including the topology, the CIs involved, and the monitoring definitions. Deployment instances are only shown when the affected system belongs to that instance and the situation was defined for one of the agent types deployed on the system for that instance. Each instance includes a link to the Service Deployment Instances application so that you can browse all information and details related to that instance. v when a service deployment instance is selected, the recommended practices (also called good practices) for the situation in the context of this instance. You use analysis practices to analyze a situation and management practices to resolve a situation. These practices can refer to actions in the Select Action menu
16
to launch another management tool (such as the TEP console) in order to analyze or resolve a situation. Analysis practices are displayed as plain text. A management practice can be either a management action described in text form and intended to be executed manually by the user, or a Tivoli Service Automation Manager management plan that can be executed automatically by the system. The list of practices is sorted by the probability that the practice will resolve the event. The number of times the practice was chosen to resolve an event of this type is used as the sorting criterion. That is, the practice chosen most often and considered the best approach by an administrator (by clicking on the Feedback Good Practice button) is displayed as the first element in the list. Depending on the analysis of the event, you can choose among the following actions to resolve the problem: v Close the event if it is only informational and no action is required. v Go to the Incident application. v Start a management action from the set of management practices to resolve the event.
Service structure
Services offered by Tivoli Service Automation Manager are organized as follows: Service definition Basic set of rules for creating a specific IT landscape. Tivoli Service Automation Manager delivers preconfigured service definitions that can be used as templates for customizing the definition to meet your specific needs. Service deployment instance Actual IT landscape described by the service definition. Service topology A set of hardware servers and software representing the IT landscape. Monitoring definition A framework for activating monitoring software to detect possible performance problems in a deployed landscape. Management plan Predefined modification of the provisioned landscape. Job plan A tool that implements management plans in terms of software. Workflows Preconfigured sequence of steps that perform a specific function. For example, there are workflows to instantiate (deploy) a service, make management changes once the instance has been deployed, and perform error handling. Work order A tool that provides the framework for executing management plans. Resources Actual hardware and software that can be used in constructing the landscape.
17
Service provider support

The new service provider feature introduced with Tivoli Service Automation Manager 7.2.2 allows for creating clouds that can be used by multiple customers. Two types of resources are available within a cloud: single customer objects that are assigned to customers individually, and multi-customer objects that can be shared among customers. The underlying idea of the solution is data segregation, which is used to associate resources with one or more customers. Resources can be used more efficiently and customers are able to support multiple internal organizations. A customer level is introduced in the self-service user interface. Each customer is associated with a specific group of teams and users. Users are always assigned to one customer only. They can be assigned to multiple teams, but all of these teams must belong to the same customer. Users can view only the information and resources that are related to their associated customer. Customers and their resources are managed in the administrative user interface, with the Cloud Customer Administration application. The application is organized into tabs. The tabs support the following actions: v Viewing the list of customers, their teams and users, requests, resources, reservations, quotas, and limits v Creating customer templates and modifying existing customers v Assigning and returning customer resources v Setting quotas and limits on customer resources In Tivoli Service Automation Manager 7.2.2, there is a clear distinction between objects that are assigned to only one customer and resources that can be shared by many or even all customers within a cloud. The Tivoli Process Automation engine service provider functionality segregates the data for this purpose. Multi-customer resources are associated manually. Association tasks related to those resources are performed in the Cloud Customer Administration application. Single customer resources are assigned automatically to the customer for which the requesting user is working. For example, if a person who is assigned to a specific customer submits a request for a new team, the fulfillment flow associates the team with the customer automatically. Resources that can be shared by customers are: v Cloud server pools v Cloud network templates v Cloud storage pools v Master images v Software products Resources that can be assigned only to individual customers are: v Teams v Users v Service deployment instances, also called projects v Saved server images The multi-customer support in Tivoli Service Automation Manager 7.2.2 introduces new tasks related to the data segregation system. This system must ensure that users see only the data assigned to them.
18
Three new roles are introduced in the self-service user interface: cloud customer administrator, approver, and security administrator. Some significant changes were also made to the authorities of the existing user roles. The main reason for the overall reorganization is the introduction of the cloud customer level. Cloud customer administrator role is strictly connected with the cloud customer level. Users in this role have authorities similar to the authorities of a cloud administrator, but they are dedicated to individual customers. They have no authority to create or remove users and register or unregister software images. Another role that is strictly connected with the cloud customer level is the approver role. Approvers can check the status of projects, and see the service requests associated with their customers. They are also authorized to approve those service requests. Cloud administrators and cloud customer administrators can also approve requests. Security administrator can create, manage and delete users. User roles are called security groups in version 7.2.2, and a user can be a member of multiple security groups. In Tivoli Service Automation Manager 7.2.2, you can add new customized security groups. For example, you can define a separate security group that is authorized to use VMware specific offerings. You can also reuse the existing roles and group management from LDAP. These procedures are described in details in the Tivoli Service Automation Manager Extended Solution Guide. Related information For more information about creating and removing customers in the self-service user interface, see Managing customers in the Tivoli Service Automation Manager User's Guide. For more information about the features of the Cloud Customer Administration application, see Cloud Customer Administration application on page 6.
Reporting function
Reports show information related to service definitions and deployments.
Tivoli Service Automation Manager report types and content

The following types of reports are available with Tivoli Service Automation Manager. The type of information shown in each report differs depending on the service.
Table 5. Summary of Tivoli Service Automation Manager Reports and Content
Tivoli Service Automation Manager Application Service Definitions
Report Type
Report Name
Selection Parameters
Content List of all service definitions and instances.
All Service Definitions AllSD <service> .rptdesign Service Definition Summary SDSummary <service> .rptdesign Status Owner From Date To Date
Service Definitions
Basic service definition information and list of service definitions and deployments.
19
Table 5. Summary of Tivoli Service Automation Manager Reports and Content (continued)
Tivoli Service Automation Manager Application Service Definitions
Report Type Service Definition Details
Report Name SDDetail <service> .rptdesign
Selection Parameters Service Name
Content Service-dependent content with identifying information, status, topology, monitoring and resource assignments, and service definition history
Service Deployment Instances
Service Deployment Summary
SISummary <service> .rptdesign
Service-dependent graphics Status and lists showing CPU and Owner Service Definition Name memory levels, servers by owner, servers by platform From Date architecture, monitoring agents To Date by type, and instances Service Name Service-dependent content including graphics showing CPU, memory, servers by architecture, monitoring agents, and service history Information concerning components of the service instance that are located on the same physical server Service-dependent graphics showing CPU, memory, servers (over time and for all deployments)
Service Deployment Details
SIDetail <service> .rptdesign
Co-Located Nodes
coLocation <service> .rptdesign SISummaryHistory <service> .rptdesign
Host Name
Service Deployment History Summary
From Date To Date
To see the complete list of reports available in your environment: 1. Log in to the administrative interface. 2. Click Go To > Administration > Reporting > Report Administration. 3. In the Application field, type PMZHB and press Enter. The list of all available reports is displayed. For details on generating reports, see "Working with reports" in the Installation and Administration Guide. For post-installation setup tasks required to activate the Reporting function, see "Configuring the Reporting function" in the Installation and Administration Guide.
Tivoli Usage and Accounting Manager reporting function

As an option, Tivoli Service Automation Manager can use the Tivoli Usage and Accounting Manager metering function. Tivoli Usage and Accounting Manager helps you improve IT cost management. You use it to analyze your costs and track, allocate, and invoice based on actual resource use by department, user, and many other criteria. Tivoli Service Automation Manager instantiates and manages service instances. It is able to track creation, modification, and deletion of a service instance itself, as well as the capacity assigned to it. This information can be periodically extracted and transformed into a so-called CSR (Common Server Resource) file, which can then be retrieved by Tivoli Usage and Accounting Manager to generate reports. Tivoli Usage and Accounting Manager helps measure service usage data. In the Tivoli Service Automation Manager context, this data is the amount of resources (CPUs and memory) allocated or assigned to servers provisioned by the Self-Service Virtual Server Provisioning component over time. Servers belong to
20
projects and projects belong to the service. Each deployment has a user. The user can own deployments coming from different services, request new deployments, or request changes to the existing deployments. For accounting purposes, organizational information must be defined for each user, that is, at the minimum, a department identification must be assigned to each user identification. For each project, you can distinguish between the requester of the project and the organization being charged with the project. You can define organizational information for a project by adding an (optional) project account code for the team that is using the project. Reports can then be generated based on the team and its users. It is also important that no two deployment instances are created with the same name, because this will result in inaccurate usage and accounting data. Before you can start using this function, you need to configure both Tivoli Service Automation Manager and Tivoli Usage and Accounting Manager. For more information, see Integrating Tivoli Usage and Accounting Manager in the Tivoli Service Automation Manager Installation and Administration Guide. To find out how to employ the collected data in the form of reports, see Working with the usage and accounting reports in the Tivoli Service Automation Manager Installation and Administration Guide.
Additional software installation on the provisioned servers

With Tivoli Service Automation Manager, you can install one or more software modules when you create a virtual machine, or you can install them on virtual machines that were already provisioned. You can use one of the product components, Tivoli Provisioning Manager, to define software installation templates and then install that software on the virtual servers. After the software product definitions are created in the administrative interface, the self-service interface users can install the software modules on virtual machines. Before you install any software modules on a provisioned machine, create software product definitions using the administrative user interface. See Tivoli Service Automation Manager Installation and Administration Guide for more information on creating software product definitions. In the self-service interface, you can install software modules by submitting three types of requests: Create Project with server type You can select software to be installed on the servers that are to be provisioned in a project. All servers have the same software installed. Add server type You can select software to be installed on a new server that is added to a project. Install Additional Software on a Server You can install software modules on a server that is already provisioned. You can select multiple software items and install them in a specified order. You can also specify additional configuration parameters for the software items to be installed.
21
Related tasks: Installing software on server on page 41 If the administrator added any software module templates and configured them in the administrative interface, you can install additional software items on an existing virtual server.
Managing POWER LPAR provisioning with VMControl

This topic provides reference information about managing POWER LPAR virtual servers using IBM Systems Director VMControl. VMControl quick reference VMControl is a plug-in of IBM Systems Director. Tivoli Service Automation Manager supports IBM Systems Director VMControl 2.3.0.2 Enterprise Edition. VMControl is an alternative way to provide POWER LPAR virtualization and image management functions. For more information about VMControl, see the section on VMControl 2.3.0.2 in the IBM Systems Director Information Center: http://publib.boulder.ibm.com/ infocenter/director/v6r2x/topic/com.ibm.director.vim.helps.doc/ fsd0_vim_c_vmc_230.html. Setting up the environment Before a Tivoli Service Automation Manager administrator can manage POWER LPAR computers using VMControl, the environment needs to be configured. For more information on the procedure, see Configuring Cloud Pools in the Tivoli Service Automation Manager Installation and Administration Guide. Managing provisioning All self-service requests, apart from modifying disk size and saving/restoring virtual servers, are available for POWER LPAR provisioning via VMControl. Recovering form errors For troubleshooting when using VMControl, see Recovering from errors when using IBM Systems Director VMControl in the Tivoli Service Automation Manager Installation and Administration Guide.
Image management
Software and server images can be maintained in the Tivoli Provisioning Manager Image Library for selection at provisioning time. New Server image templates can be created and imported to the library. Once the images are in the library, they must be registered so that they can be used to provision new virtual servers. A snapshot-like image of an entire provisioned server can also be saved and restored in the current project, so that the server can be initialized at the state represented by the image. The Tivoli Service Automation Manager User's Guide describes the image-related tasks that are available to administrators and users working with the self-service user interface.
22
For other administrative tasks, see "Managing server images" in the Installation and Administration Guide.
Workload Deployer overview

IBM Workload Deployer is an optional, separately paid appliance that can be integrated with Tivoli Service Automation Manager. Note: The only supported version of IBM Workload Deployer is 3.0. Workload Deployer offers a comprehensive set of patterns and capabilities that focus on addressing WebSphere workloads. It enables creating, deploying, monitoring, and managing service construction and delivery within Tivoli Service Automation Manager. The appliance is based on special virtual images, such as the WebSphere Application Sever Hypervisor Edition, and allows creating patterns that represent the target application environment. These patterns include the infrastructure nodes of the application and the necessary configuration for the environment. By using Workload Deployer, you can deploy them into your private cloud. In this way, the appliance provides management and monitoring capabilities that give you necessary controls over your running application environments.
The integration with Tivoli Service Automation Manager

The functions of Workload Deployer and Tivoli Service Automation Manager are complementary in nature.Workload Deployer allows users to create, deploy, and manage customized environments based on the WebSphere application and located in a private cloud. Tivoli Service Automation Manager provides the tools to perform the standardization and the automation in the cloud environment, thereby enabling rapid provisioning for a wide breadth of workloads. The integration provides: v the service delivery and management capability of Tivoli Service Automation Manager v the Workload Deployer patterns and capabilities v a unified interface from which users can deploy and manage their cloud-based environments Tivoli Service Automation Manager enables creating and deploying application environments based on any kind of software. Workload Deployer offers capabilities for application environments based on IBM software, thereby simplifying installation, configuration, integration, and orchestration scripting procedures for those workloads. The integration of the two applications can be made according to different scenarios. Depending on what services you want to deliver via the cloud, the most common scenarios are when: v When there is a need for unified management of private clouds that include WebSphere. v When you need to add request workflow capabilities to Workload Deployer. After the integration, Tivoli Service Automation Manager becomes the primary management device for your private cloud. The capabilities of both the products remain the same. Tivoli Service Automation Manager enables the provisioning and management of a wide array of cloud-based services including operating systems, application platforms, and end-user applications. The integration of Workload Deployer enhances the time to value for delivering WebSphere environments regardless of what other services you deliver through Tivoli Service Automation
23
Manager. Moreover, integrating the products allows you to unify management of your cloud services using the self-service user interface. Workload Deployer delivers its patterns, namely rapid provisioning, consistent configurations, and inherent product knowledge for WebSphere workloads without the need to switch between multiple service management portals.
24
Chapter 2. Using the Self-Service Virtual Server Management offerings

Tivoli Service Automation Manager provides robust functionality for selecting and provisioning standard software packages on virtual servers of various type. A simple, easy-to-use set of applications enable data center personnel to achieve rapid time-to-value for virtual server provisioning from these platforms. The configuration that is provided for these applications supports fully automated provisioning with a standardized set of deployment activities.
Submitting requests in the self-service user interface

Log on to the self-service user interface, where you can access the offerings and request provisioning.
Before you begin

v Use one of the supported browsers: Microsoft Internet Explorer 8 Mozilla Firefox 3.5 or 3.6 v Install Microsoft Silverlight when using Internet Explorer. v Enable native XMLHTTP support when using Internet Explorer. In the browser toolbar, click Tools > Internet Options > Advanced and select the Enable native XMLHTTP support check box. v Enable JavaScript, CSS, SSL, and cookies. v Set your browser resolution to a minimum of 1024x768.
Procedure
1. In a supported browser, access the URL: https://<hostname>:9443/SimpleSRM where hostname is the Internet name of the management server. 2. Log in with the credentials that you have been assigned. Default administrative credentials: User Name: PMRDPCAUSR Password: maxadmin 3. Select Request a new service > Virtual Server Management to get access to all offerings, or select Frequent requests. This option lists 4 most frequent offerings, based on the last 30 requests submitted by the user.
What to do next
You can access the requests from the hierarchical graphical menu. Depending on the security group that you are assigned to, a different set of requests will be available in the menu:
25
Table 6. Access to requests depending on the security group

Cloud Administrator Create project Create project from saved image Add server Add server from saved image Modify reservation Cancel project Modify server resources Reset server password Start, stop, or restart server Install software Remove server Create server image Restore server from image Remove saved images Register image Unregister image Create user Modify user Remove user Create team Modify team Remove team Create customer Remove customer Approve and reject requests View requests View projects View servers v v v v Cloud Manager Team Administrator v v v v Team User Cloud Customer Administrator v v v v Approver Security Administrator -
v v v v v v v v v v v v v v v v v v v v v v v v
v v v v
v v v v v v v v v v v v v v v
v v v
v v v v v v v v v v v v v v v v v v v v
v v v v
v v v -
Related concepts: User interfaces on page 3 Tivoli Service Automation Manager provides two options for user interaction: a self-service user interface and an administrative user interface.
Approvals and notifications

The product is shipped with a set of built-in approval workflows and notifications that are invoked after self-service provisioning requests are created. Approvals By default, all self-service requests are automatically approved. Administrators can enable the approval process for server-related requests. Three groups of users are then allowed to approve the requests: v Cloud administrators
26
v Cloud customer administrators v Cloud approvers v Cloud managers If a request for a customer is sent for approval, all approvers associated with the customer are notified, and any of them can approve the request. The following requests cannot be sent for approval: v Install Software v Manage Users requests v Manage Teams requests v Manage Image Library requests Tip: To enable the approval process, see Enabling or disabling automatic approval of requests in the Tivoli Service Automation Manager Installation and Administration Guide. Notifications Email notifications are sent out whenever one of the project-related request is submitted: v Create/Cancel Project v Save/Restore Image v Start/Stop/Modify/Add/Remove Server The same notification is sent to three groups of users: v Requester v Project owner (the user that requested project creation) v Team that owns the project (on CC list) You can customize the built-in approval workflows and notifications to meet the needs of your organization.
Email notifications
You can stay informed about your requests without being logged on to Tivoli Service Automation Manger through automatic email notifications. The system administrator can configure what notifications you want to receive. Email notifications can be sent when: v Service Request approval is rejected, required, or approved. v Project is created, canceled, pending removal due to an expired reservation or a reservation time is modified. v Server is started, stopped, added, modified, removed, pending removal due to an expired reservation or an operation has been performed. v Virtual server image is created, saved, restored, or deleted. v WebSphere CloudBurst pattern is created, pending removal or canceled. Project change notifications are sent to three groups of users: v Requester v Project owner v Project team (CC list)
27
By default, the requester and all customer team members receive a notification regarding submitted requests. Cloud administrators must be registered as a team members to receive notifications. Note: Ensure that the team users have email addresses that can be relayed by your mail server, else email cannot be sent.
Example
Dear John Smith Your Service Request 00048 "Project Request" has been approved and QUEUED for processing. Do not reply to this message as it was automatically generated. Regards, Your Service Automation Team
Approving requests
When the approval process is enabled, a group of users with approval privileges can approve or decline the requests that the users submit. They can also reassign the requests for other users approval. Tip: To enable the approval process, see Enabling or disabling automatic approval of requests in the Tivoli Service Automation Manager Installation and Administration Guide. The following users are able to approve and decline requests: v Cloud administrators v Cloud customer administrators v Cloud approvers v Cloud managers If a request for a customer is sent for approval, all approvers associated with the customer are notified, and any of them can approve the request.
Procedure
1. From the Home panel on the My Approvals pod, select Manage Approvals... A list of requests that have been assigned for your approval is displayed. 2. Select a request that you want to approve and click one of the options: v Approve v Reject v Reassign Note: Use the Reassign option if you want to assign the request to another user. This functionality must be enabled as described in Enabling or disabling delegation of approval requests in the Tivoli Service Automation Manager Installation and Administration Guide. Otherwise the option is not available.
28
Creating a project and adding virtual servers

Use the wizard to create a virtual server project with one or more virtual servers. Each server receives an automatically assigned host name.
Before you begin

This task can only be performed by team and cloud administrators. Note: If projects are being created by multiple users, or multiple projects are being scheduled by the same user, the resources are not updated for projects that are in the queued or new status. This may allow a user to create projects for which there are not enough resources.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Create Project with server type. The Create Project wizard opens. 2. In the Project Details panel: a. Enter a project name. b. Select the team that should have access to the project. c. Optional: Type a description for the project. d. Set the start date and time, and duration. Important: The time of provisioning is based on the time and timezone set on your local machine when the request is submitted. Ensure that your time is set correctly. e. Click Next. 3. In the Requested Image tab: a. Select resource group used to reserve resources. b. Select the operating system image to be deployed. Only registered images are available. To learn how to register an image, see Managing Image Library on page 45. c. Select the number of servers to be provisioned in the project. d. Click Next. 4. In the Server Details tab, use the slider buttons to adjust the settings of the requested resources as required. Restriction: The following values are restricted for certain platforms:
Table 7. Restrictions for the resources values VMware Memory Swap Memory Virtual CPU Disk a multiple of 4 MB POWER LPAR a multiple of 128 MB
a multiple of 1 GB - decimal values are not allowed 1, 2 or 4 For POWER LPAR servers provisioned via IBM Systems Director VMControl disk space value is static and cannot be modified.
Click Next.
29
5. In the Additional Disks tab: Note: This feature is available for POWER LPAR servers only. a. Review the available storage resources. If no resources are available, verify that they have been configured correctly in the administrative user interface b. Specify the Mount point, Volume group name, and Volume name. c. Select the disk size to be assigned to each requested server. If you cannot select the disk size, the required resources are not available. d. Select the file system to be used. e. Click Add New to add another disk, and repeat the steps to fill in the details. f. Click Next. 6. In the Additional Software tab, select additional software modules to install on the requested servers: a. Use the arrows to select additional software to be installed on the provisioned servers. Then, use the vertical arrows to set the order in which the items are to be installed. If the software item requirements can be fulfilled, its name will appear in the Selected Software box. Otherwise an error message will be displayed. Note: Software installation feature is independent of hypervisor at the backend. If a server fulfills the requirements of the selected software module then that software module is listed as installable on it. b. To specify any additional parameters for each software item, select an item and click Configure Software. Fill in the fields as required. Default values for the parameters are displayed in the input fields and are editable if they can be modified. Input for encrypted parameters is displayed as passwords. Hidden parameters are not displayed on the user interface. If no items are available in the Available Software box, verify that they have been configured correctly in the administrative interface. For more information, see Tivoli Service Automation Manager Installation and Administration Guide. 7. In the Network Configuration tab, select a network segment for each network interface. 8. Define any required settings in the Other Settings tab: a. For VMware, POWER LPAR and KVM projects, select the following options, if required: Save an image of each server when the project reaches its end date and is being decommissioned Select this checkbox to configure the project to automatically save a new image of each virtual server in this project at the time the project is canceled. Keep saved images after the project has been decommissioned Select this checkbox to configure the project so that the existing server images are not removed along with the serves at the time the project is canceled. b. Select Monitoring Agent to be Installed, if required. This agent performs scans to identify server resource utilization (memory, CPU and disk space). The usage values can then be viewed in the Manage Servers panel. This field is only available if configured. c. Click Next.
30
9. In the Summary tab, review the settings for your project. Click Finish to submit the request.
Results
A service request is created to complete the virtual server project that you have defined or to reserve the hardware for deployment on the indicated start date. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. Immediate fulfillment: After any required approvals are received, host names for the virtual servers are automatically assigned from a pool of host names that is maintained by your administrator. You receive an e-mail notification when the new project is completed. Scheduled fulfillment: You will receive an indication of whether the request has been approved or rejected. If the request is approved, it becomes a reservation for the indicated hardware capacity and network parameters on the start date. If the request is not approved, the reason may be that the requested hardware capacity or network parameters are not available for the indicated time frame. Note: The virtual machine disk size value may differ from the one requested. For Tivoli Service Automation Manager, 1GB = 230 bytes, 1MB = 210 bytes. On a Linux operating system these values will differ, as 1GB = 109 bytes.
Creating a project from a saved server image

You can create a new project and use the saved server images to provision a server in that project. This functionality is only available for VMware, POWER LPAR and KVM.
About this task

The parameters of the server to be provisioned are defined by the image. The server configuration will be identical to the one from which the image was taken. If you want to restore a server with a monitoring agent installed on it, the administrator needs to enable agent installation in some of the request panels first. For more information see Enabling the monitoring agent installation on restored images in the Tivoli Service Automation Manager Installation and Administration Guide.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Create Project from Saved Image. 2. 3. 4. 5. Enter a Project Name. Select the team that should have access to the project. Optional: Type a description for the project. Set the start date and time, and duration.
Important: The time of provisioning is based on the time and timezone set on your local machine when the request is submitted. Ensure that your time is set correctly. 6. Select resource group used to reserve resources.
31
7. Select the image to be deployed. The list that is displayed shows all available images for the servers that are not currently provisioned. 8. For VMware, POWER LPAR and KVM projects, select the following options if required: Save an image of each server when the project reaches its end date and is being decommissioned Select this checkbox to configure the project to automatically save a new image of each virtual server in this project at the time the project is canceled. Keep saved images after the project has been decommissioned Select this checkbox to configure the project so that the existing server images are not removed along with the serves at the time the project is canceled. 9. Click OK to submit the request.
What to do next
To add more servers to a project using other saved images, use the Add Server from Saved Image request.
Canceling a project
You can cancel a virtual server project, also when it is scheduled for a future date. When you cancel a project, all of the servers that have been provisioned within that project are deprovisioned. The host names that were automatically assigned to these servers are freed up for use by other virtual servers that are created in the data center. Any image saved for a server that participated in the project is deleted.
Before you begin

Only cloud and team administrators can perform this task.
About this task

To cancel a virtual server project:
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Cancel Project. 2. From the Project Name list, select a name of the project that you want to cancel. Project details, and a list of servers in the project are displayed. 3. For VMware, POWER LPAR and KVM projects, the list of all images saved for the project is displayed. Select the following options if required: Save an image of each server when the project reaches its end date and is being decommissioned Select this checkbox to configure the project to automatically save a new image of each virtual server in this project at the time the project is canceled. Keep saved images after the project has been decommissioned Select this checkbox to configure the project so that the existing server images are not removed along with the serves at the time the project is canceled.
32
4. Click OK to submit the request.
Results
A service request is created to cancel the project. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. After any required approvals are received, the project is canceled, and you receive an e-mail notification.
Creating projects with a Workload Deployer pattern

Learn how to create and save a cloud project using a Workload Deployer pattern. This task can be performed after integrating Tivoli Service Automation Manager with IBM Workload Deployer.
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Create a Project with a Workload Deployer Pattern. 2. Type a name for the project and, optionally, project description. 3. From the Team Access list, select a team for which you want to grant access to the project. 4. Set the start and end dates. You can set Indefinite for the end date, which allows the virtual system to run until an administrator manually removes it. 5. Select a Workload Deployer pattern from the list and modify its settings if necessary. 6. Select a WebSphere CloudBurst cloud group to which the pattern is to be deployed. 7. Specify the parameters for Administrative agents and Standalone server to create or change relationships between the virtual image parts that define the topology. 8. Click OK to submit the request.
Results
A service request is created to complete the virtual server project that you have defined or to reserve the hardware for project on the indicated start date. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. Immediate fulfillment: After any required approvals are received, host names for the virtual servers are automatically assigned from a pool of host names that is maintained by your administrator. You receive an e-mail notification when the new deployment is completed. Scheduled fulfillment: You will receive an indication of whether the request has been approved or rejected. If it has been approved, the request becomes a reservation for the indicated hardware capacity and network parameters on the start date. If the request is not approved, the reason may be that the requested hardware capacity or network parameters are not available for the indicated time frame. Subsequently, Workload Deployer determines what machines in the cloud are the hosts for each part in the pattern. At the end of the successful deployment, the newly created virtual system is listed in the Manage Projects window of Tivoli
33
Service Automation Manager.
Canceling Workload Deployer pattern projects

You can cancel a project saved with Workload Deployer pattern, also if it is scheduled for a future date. When you cancel a project, all of the servers that have been provisioned within that project are deprovisioned. The host names that were automatically assigned to these servers are freed up for use by other virtual servers that are created in the data center. Any image saved for a server that participated in the project is deleted.
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Cancel Workload Deployer Project. 2. Display the values for the Project Name list and select the project that you are canceling. 3. Click OK to submit the request.
Results
A service request is created to cancel the project. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. After any required approvals are received, the project is canceled, and you receive an e-mail notification.
Modifying project
Use these tasks to learn how to add new servers to a project or modify the reservation date.
Adding virtual servers to an existing project

When, for example, the scope of a project increases substantially, you can add one or more virtual servers to an existing project. Select an active project and add one or more new servers, specifying the number of CPUs, the memory, and the software to be deployed for each. The new servers receive automatically assigned host names.
Before you begin

This task can only be performed by team and cloud administrators.
About this task

To add servers to a project:
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Modify Project. 2. Click Add server type, depending on what type of server you want to add to the project. 3. Select the project from the list, and click Next. 4. In the Requested Image tab:
34
a. Select resource group used to reserve resources. b. Select the operating system image to be deployed. Only registered images are available. To learn how to register an image, see Managing Image Library on page 45. c. Select the number of servers to be provisioned in the project. d. Click Next. 5. In the Server Details tab, use the slider buttons to adjust the settings of the requested resources as required. Restriction: The following values are restricted for certain platforms:
Table 8. Restrictions for the resources values VMware Memory Swap Memory Virtual CPU Disk a multiple of 4 MB POWER LPAR a multiple of 128 MB
a multiple of 1 GB - decimal values are not allowed 1, 2 or 4 For POWER LPAR servers provisioned via IBM Systems Director VMControl disk space value is static and cannot be modified.
Click Next. 6. In the Additional Disks tab: Note: This feature is available for POWER LPAR servers only. a. Review the available storage resources. If no resources are available, verify that they have been configured correctly in the administrative user interface b. Specify the Mount point, Volume group name, and Volume name. c. Select the disk size to be assigned to each requested server. If you cannot select the disk size, the required resources are not available. d. Select the file system to be used. e. Click Add New to add another disk, and repeat the steps to fill in the details. f. Click Next. 7. In the Additional Software tab, select additional software modules to install on the requested servers: a. Use the arrows to select additional software to be installed on the provisioned servers. Then, use the vertical arrows to set the order in which the items are to be installed. If the software item requirements can be fulfilled, its name will appear in the Selected Software box. Otherwise an error message will be displayed. Note: Software installation feature is independent of hypervisor at the backend. If a server fulfills the requirements of the selected software module then that software module is listed as installable on it. b. To specify any additional parameters for each software item, select an item and click Configure Software. Fill in the fields as required.
35
Default values for the parameters are displayed in the input fields and are editable if they can be modified. Input for encrypted parameters is displayed as passwords. Hidden parameters are not displayed on the user interface. If no items are available in the Available Software box, verify that they have been configured correctly in the administrative interface. For more information, see Tivoli Service Automation Manager Installation and Administration Guide. 8. In the Network Configuration tab, select a network segment for each network interface. 9. In the Summary tab, review the settings for your project. Click Finish to submit the request.
Results
A service request is created to add the new servers to the specified project. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. Immediate fulfillment: After any required approvals are received, host names for the virtual servers are automatically assigned from a pool of host names that is maintained by your administrator. You receive an email notification when the new project is completed. Scheduled fulfillment: You will receive an indication of whether the request has been approved or rejected. If approved, the request becomes a reservation for the indicated hardware capacity on the start date. If the request is not approved, the reason may be that the requested hardware capacity is not available for the indicated time frame. Note: The virtual machine disk size value may differ from the one requested. For Tivoli Service Automation Manager, 1GB = 230 bytes, 1MB = 210 bytes. On a Linux operating system these values will differ, as 1GB = 109 bytes.
Adding a server from a saved image

You can create a server using one of the saved images and add this server to a project. This functionality is only available for VMware, POWER LPAR and KVM.
About this task

The parameters of the server to be provisioned are defined by the image. The server configuration will be identical to the one from which the image was taken. If you want to restore a server with a monitoring agent installed on it, the administrator needs to enable agent installation in some of the request panels first. For more information see Enabling the monitoring agent installation on restored images in the Tivoli Service Automation Manager Installation and Administration Guide.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Modify Project > Add Server from Saved Image. 2. Select the project from the list. Project details display. 3. In the Requested Image section, select the resource group used to reserve resources.
36
4. Select an image to be deployed. The list that is displayed shows all available images for the servers that are not currently provisioned. 5. Click OK to submit the request.
Modifying reservation dates

You can modify the start date of the scheduled project with a future start date, and the end date of all projects.
Before you begin

This task can only be performed by team and cloud administrators.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Modify Project > Modify Reservation. 2. From the Project Name list, select a project that you want to modify. Project details display. 3. Set the new start date and time, and duration. Important: The time of provisioning is based on the time and timezone set on your local machine when the request is submitted. Ensure that your time is set correctly. 4. Click OK to submit the request. Remember: When the reservation time is changed for a project and when quotas and limits exist for the respective customer and pool, then these limits are checked when you try to modify the reservation time. It is only possible to modify the reservation time within the previously specified limits.
Results
A service request is created to modify the dates as specified. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. After any required approvals are received, the dates of the reservation are changed (if possible) and you receive an e-mail notification.
Removing a virtual server

You can delete a virtual server from a project when the server is no longer needed. You can also delete the reservation for a server that is scheduled for provisioning on a future date. When you delete a server, the host name that was automatically assigned to that server is freed up for use by another virtual server that is created in the data center. Important: v You cannot remove the last server in the project. Instead, the whole project can be canceled. v You cannot remove the first server in a project with future reservation date. Instead, the whole project can be canceled.
Procedure
1. From the Home panel, select Request a New Service > Virtual Server Management > Modify Project > Remove Server 2. From the Project Name list, select a project.
37
3. From the list of servers that displays, select a server to remove. 4. For VMware, POWER LPAR and KVM projects, the list of all images saved for the project is displayed. Select the following options if required: Save a new image of this server before it is removed Select this check box to save a new image of the server to be removed. Keep existing saved images of this server after it has been removed Select this check box to keep any existing images of the server to be removed. Otherwise, when you remove a virtual server, any images saved for this server will also be deleted. 5. Click OK to submit the request.
Results
A new service request is created to delete the specified server and, optionally, its images. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. After any required approvals are received, the server is deleted, and you receive an email notification.
Modifying server
Use these tasks to learn how to modify the state of a server, its resources, or reset password for a server.
Modifying server resources

You can modify the number of CPUs, the amount of memory, or increase the disk space to be allocated to any supported virtual server that is currently provisioned. Requests for server capacity modification might be submitted when a project requires more capacity than was originally assigned. Similarly, the requests might arise when less capacity is needed. Note: v This request is not supported for System z and Xen hypervisors. v You can modify only one server per request.
About this task

Important: After you modify resources for VMWare and KVM servers, these servers are restarted, and any running services are interrupted. POWER LPAR servers are not restarted. To modify the capacity of an existing virtual server:
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Modify Server > Modify Server Resources. 2. Select the project from the list. Project details display. 3. From the table with available servers, select a server to modify its resources. Only one server can be modified in one request.
38
4. In the Resources section, use the sliders to adjust the settings of CPU, memory, and disk space as required. You can click Check resources to verify that the requested resources are available. Restriction: The following values are restricted for certain platforms: Memory v VMware: must be a multiple of 4 MB v POWER LPAR: must be a multiple of 128 MB v Swap memory can only be modified for all Linux platforms on VMware and KVM. It is not working for AIX and Windows platforms on VMware or on POWER LPAR. CPU v VMware: The value for Virtual CPU must be 1, 2 or 4. v KVM: Physical CPU cannot be modified. Disk size v Disk size modification is supported on the following operating systems: VMware: Red Hat Enterprise Linux 5.3, 5.4 SUSE Linux Enterprise Server 10.2, 11 with resize2fs tool version 1.39 or higher. Windows 2008 KVM: Red Hat Enterprise Linux 5.4 POWER LPAR: AIX version 6.1 Technology Level 4 or higher v For POWER LPAR servers provisioned via IBM Systems Director VMControl this functionality is not available. v Disk size cannot be modified if a POWER LPAR server was provisioned using Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) that is configured to use storage from MPIO mapped SAN disks. No additional disk can be mapped to extend the current one, and no already mapped MPIO SAN disk can be unmapped from the LPAR. v On Power, the disk extension is added to the VIO server by this service request. The extension on System p LPAR is visible only after manually triggering the command chvg -g rootvg. v Disk size can only be increased, not decreased. v When resizing disk on Windows, ensure that the password was not modified manually. For more information about Windows disk modifications if the password was modified manually, see Windows disk size modification after changing password on page 40. 5. Click OK to submit the request.
Results
A service request is created to change the virtual server capacity as specified. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. If you are using the built-in, default approval workflow, requests that you submit on your own behalf are automatically approved.
39
After any required approvals are received, the capacity is changed, and you receive an email notification. Note: The virtual machine disk size value may differ from the one requested. For Tivoli Service Automation Manager, 1GB = 230 bytes, 1MB = 210 bytes. On a Linux operating system these values will differ, as 1GB = 109 bytes.
Windows disk size modification after changing password

There are some restrictions on modifying disk size on Windows after the password was changed manually. To successfully process a disk modification request for Windows, the password must be set by Tivoli Service Automation Manager. If the password was changed manually, you can use a Reset Server Password request to change the password again so that it is synchronized with Tivoli Service Automation Manager. Any disk modification request that is submitted after the Windows password was changed manually is failed. Even though the request fails, the disk size is in fact modified in VMware. Both VMware and Tivoli Service Automation Manager show the new disk size. The disk space resulting from the resize operation is available as unallocated disk space in Windows, but the file system is not enlarged. Important: Do not use the unallocated space to create a second partition within Windows, as this might cause problems for future requests. There are two ways to enlarge the file system: v Windows administrator can resize the file system manually. v You can perform the following procedure in Tivoli Service Automation Manager: 1. Reset the password using the Reset Server Password request in the self-service user interface. 2. Further increase the disk size of the server in the Modify Server resources request. As a result, the file system is increased to the new disk size.
Resetting a server password

You can reset a server password and have it e-mailed to members of teams that have access to the project.
Before you begin

Ensure that you have the required privileges to submit this request.
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Modify Server > Reset server password. The Reset Server Password window displays. 2. Select a project. The list of servers associated with the project displays. 3. Select a server to reset the password for and click OK.
40
Results
The password is reset and the members of teams that have access to the project get an e-mail notification with new password.
Starting a server
You can start a server in a project.
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Modify Server > Start Server. The Start Server window displays. 2. Select a project from the list. The list of servers associated with the project displays. Note: If the monitoring agent was not selected to be installed when the server was created, the list of servers will include all servers regardless of their state. 3. Select a server to start and click OK.
Stopping a server
You can stop a server in a project.
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Modify Server > Stop Server. The Stop Server window opens. 2. Select a project from the list. The list of servers associated with the project displays. Note: If the monitoring agent was not selected to be installed when the server was created, the list of servers will include all servers regardless of their state. 3. Select a server to stop and click OK.
Restarting a server
You can restart a server in a project.
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Modify Server > Restart server. The Restart Server window opens. 2. Select a project from the list. The list of servers associated with the project displays. 3. Select a server to restart and click OK.
Installing software on server

If the administrator added any software module templates and configured them in the administrative interface, you can install additional software items on an existing virtual server.
Before you begin

Ensure that the software product definition for the item that you want to install has been configured by the Tivoli Service Automation Manager administrator. For more information, see Tivoli Service Automation Manager Installation and Administration Guide.
41
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Modify Server > Install Software 2. Select the project from the list. Project details display. 3. From the table with available servers, select a server to install additional software on. 4. Install additional software on the servers: a. Use the arrows to select additional software to be installed on the provisioned servers. Use the vertical arrows to set the order in which the items are to be installed. If the software item requirements can be fulfilled, its name will appear in the Selected Software box. Otherwise an error message will be displayed. Note: Software installation feature is independent of hypervisor at the backend. If a server fulfills the requirements of the selected software module then that software module is listed as installable on it. b. To specify any additional parameters for each software item, select an item and click Configure Software. Fill in the fields as required. Default values for the parameters are displayed in the input fields and are editable if they can be modified. Input for encrypted parameters is displayed as passwords. Hidden parameters are not displayed on the user interface. Note: If no items are available in the Available Software box, verify that they have been configured correctly in the administrative interface. 5. Click OK to submit the request. Related concepts: Additional software installation on the provisioned servers on page 21 With Tivoli Service Automation Manager, you can install one or more software modules when you create a virtual machine, or you can install them on virtual machines that were already provisioned.
Backing up and restoring server images

Use these tasks to learn how to create and remove a snapshot-like server images, and restore the servers using these images. Note: v This functionality is not supported for Xen , z/VM, and POWER LPAR via IBM Systems Director VMControl. v All images saved by a user in the self-service user interface are owned by this user. Only this user can ever restore the saved image. Each user can view only the images that he or she created, and does not have access to the images of other users. If an image is automatically saved at the end date of a project, the user who created the project becomes the owner of the saved image. Therefore, automatically saved images can be restored only by the creator of the project. v If you want to restore a server with a monitoring agent installed on it, the administrator needs to enable agent installation in some of the request panels first. For more information see Enabling the monitoring agent installation on restored images in the Tivoli Service Automation Manager Installation and Administration Guide.
42
Creating server image

You can save multiple images of a provisioned server in its current state. You can then use the images in a subsequent request to restore a server, create a project with a server image, or add a server to a project based on the image.
About this task

Note: v This functionality is not supported for Xen , z/VM, and POWER LPAR via IBM Systems Director VMControl. v All images saved by a user in the self-service user interface are owned by this user. Only this user can ever restore the saved image. Each user can view only the images that he or she created, and does not have access to the images of other users. If an image is automatically saved at the end date of a project, the user who created the project becomes the owner of the saved image. Therefore, automatically saved images can be restored only by the creator of the project. v If you want to restore a server with a monitoring agent installed on it, the administrator needs to enable agent installation in some of the request panels first. For more information see Enabling the monitoring agent installation on restored images in the Tivoli Service Automation Manager Installation and Administration Guide. Important: When creating a server image, make sure that you have enough free space on the data store.Tivoli Service Automation Manager does not check whether there is enough space available. If there is not enough space available, an inbox assignment is created in the administrative user interface and the situation must be resolved manually, as described in Configuring cloud pools in the Installation and Administration Guide.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Backup and Restore Server Image > Create Server Image. 2. In the corresponding fields, type virtual server image name and description. 3. Select the name of the project in which the server is provisioned. Project details display. 4. From the list that displays, select a server that you want to create an image of. A list of all images available for this server is displayed. 5. Click OK to submit the request.
Results
A service request is created to save an image of the server that you selected. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. After the required approvals are received, you will receive an email notification when the image is saved.
43
Restoring a server from image

You can restore a virtual server back to its previous state using an image that you saved before.
About this task

v You can only view, and use the images that you created. You cannot restore the images created by other users. v When you restore a server from an image, the image must have the same properties (CPU, memory and disk) as that of the current virtual machine. Otherwise, it cannot be restored and an error message is displayed.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Backup and Restore Server Image > Restore Server From Image. 2. From the Project Name list, select a project for which you want to restore a server. 3. Select a server that you want to restore. 4. From the list that displays, select the image that is to be used for restoring the server. Note: The list is limited to available images for servers that are currently provisioned. 5. Click OK to submit the request.
Results
A service request is created to restore the server from the selected image. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. After the required approvals are processed, you will receive an email notification when the image has been restored.
Removing saved images

You can remove previously saved server images from the inventory.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Backup and Restore Server Image > Remove Saved Images. 2. From the list that displays, select the image that is to be removed. The list displays only the images that you created. Images that were created by other users are not displayed. 3. Click OK to submit the request.
Results
A service request is created to remove the image from the inventory. Any notifications that are defined for this operation are sent out, and any approvals that are part of the work order are requested. After the required approvals are received, you will receive an e-mail notification when the image has been deleted.
44
Managing Image Library

Tivoli Provisioning Manager Image Library is the source for software images to be used in provisioning the virtual servers. Once the image templates discovery has been performed in Tivoli Provisioning Manager by the system administrator, the images need to be registered in the Image Library, so that they can be used for provisioning. Use these tasks to learn how to register or unregister server images. For more information about discovering images, see the corresponding sections in the Tivoli Service Automation Manager Installation and Administration Guide.
Registering VMware images

Use this task to learn how to register a VMware image in the Image Library.
Before you begin

v This task can only be performed by cloud administrator. Ensure that you have the required privileges. v Make sure the Tivoli Service Automation Manager administrator has run the image discovery in Tivoli Provisioning Manager.
About this task

To register a VMware image:
Procedure
1. In the Home panel, select Request a new service > Virtual Server Management > Manage Image Library > Register VMware Image. 2. Specify the name of the image, and, optionally, provide its description. 3. Select the Resource Pool from the list. 4. Select Discovered Image from the list. The list contains only the unregistered images. 5. In the Network Configuration section: a. Select the network type. Four predefined types are available: v Management v Customer v Backup-Restore v Storage b. Select Use this interface for host name resolution if the network interface is to be used for host name resolution. c. Optional: In the Network Usage section, select a set of usage values applicable to a particular interface. d. To add more network interfaces, click Add Network Interface, and specify the settings. In the Resources section, specify the Minimum and Recommended values for virtual CPUs, physical CPUs, memory, and disk space. Specify the details of the operating system of the image according to Table 9 on page 46. Depending on the operating system, specify the Administrator Password or Root Password that match the password set on the image from which the virtual machines will be created. If you are registering a Windows image, enter the Product Key.
6. 7. 8.
9.
45

Table 9. OS Family and Version values Family Installed (operating system of the software stack) Red Hat Enterprise Linux Linux CentOS SUSE Linux Enterprise Server Windows XP Windows 2003 Windows Windows Server 2008 Windows Server 2008 R2 Windows 7 Version 5.3 or 5.4 5.3 or 5.4 10.2 or 11 Not required 2003 2008 2008 7
Registering POWER LPAR images

Use this task to learn how to register a POWER LPAR image in the Image Library.
Before you begin

About this task

To register an image:
Procedure
1. Select Home > Request a new service > Virtual Server Management > Manage Image Library > Register POWER LPAR Image. 2. Specify the name of the image, and, optionally, provide its description. 3. Select the Resource Pool from the list. 4. Select Discovered Image from the list. The list contains only the unregistered images. 5. In the Network Configuration section: a. Select the network type. Four predefined types are available: v Management v Customer v Backup-Restore v Storage b. Select Use this interface for host name resolution if the network interface is to be used for host name resolution. c. Optional: In the Network Usage section, select a set of usage values applicable to a particular interface. d. To add more network interfaces, click Add Network Interface, and specify the settings.
46
6. In the Resources section, specify the Minimum and Recommended values for virtual CPUs, physical CPUs, memory, and disk space. 7. Enter the Root Password for the image. 8. Click OK to submit the request.
Registering Xen images

Use this task to learn how to register a Xen image in the Image Library.
Before you begin

About this task

To register a Xen image:
Procedure
1. From the Home panel, select Request a new service > Virtual Server Management > Manage Image Library > Register Xen Image. 2. Specify the name of the image, and, optionally, provide its description. 3. Select the Resource Pool from the list. 4. Select Discovered Image from the list. The list contains only the unregistered images. 5. In the Network Configuration section: a. Select the network type. Four predefined types are available: v Management v Customer v Backup-Restore v Storage b. Select Use this interface for host name resolution if the network interface is to be used for host name resolution. c. Optional: In the Network Usage section, select a set of usage values applicable to a particular interface. d. To add more network interfaces, click Add Network Interface, and specify the settings. 6. In the Resources section, specify the Minimum and Recommended values for virtual CPUs, physical CPUs, memory, and disk space. 7. Enter the File Name of the Image. 8. Click OK to submit the request.
47
Registering KVM images

Use this task to learn how to register a KVM image in the Image Library.
Before you begin

About this task

To register a KVM image:
Procedure
1. From the Home panel, select Request a new service > Virtual Server Management > Manage Image Library > Register KVM Image. 2. Specify the name of the image, and, optionally, provide its description. 3. Select the Resource Pool from the list. 4. Select Discovered Image from the list. The list contains only the unregistered images. 5. In the Network Configuration section: a. Select the network type. Four predefined types are available: v Management v Customer v Backup-Restore v Storage b. Select Use this interface for host name resolution if the network interface is to be used for host name resolution. c. Optional: In the Network Usage section, select a set of usage values applicable to a particular interface. d. To add more network interfaces, click Add Network Interface, and specify the settings. 6. In the Resources section, specify the Minimum and Recommended values for virtual CPUs, physical CPUs, memory, and disk space. 7. Click OK to submit the request.
Registering z/VM image

Use this task to learn how to register a z/VM image in the Image Library.
Before you begin

Procedure
1. From the Home panel, select Request a new service > Virtual Server Management > Manage Image Library > Register z/VM Image. 2. Specify the name of the image, and, optionally, provide its description.
48
3. Select the Resource Pool from the list. 4. Select Discovered Image from the list. The list contains only the unregistered images. 5. In the Network Configuration section: a. Select the network type. Four predefined types are available: v Management v Customer v Backup-Restore v Storage b. Select Use this interface for host name resolution if the network interface is to be used for host name resolution. c. Optional: In the Network Usage section, select a set of usage values applicable to a particular interface. d. To add more network interfaces, click Add Network Interface, and specify the settings. 6. In the Resources section, specify the Minimum and Recommended values for virtual CPUs, physical CPUs, memory, and disk space. 7. Click OK to submit the request.
Registering POWER LPAR images via IBM Systems Director VMControl

Use this task to learn how to register a POWER LPAR image in the Image Library using VMControl.
Before you begin

About this task

To register an image:
Procedure
1. Select Home > Request a new service > Virtual Server Management > Manage Image Library > Register VM Image via IBM Systems Director VMControl. 2. Specify the name of the image, and, optionally, provide its description. 3. Select the Resource Pool from the list. 4. Select Discovered Image from the list. The list contains only the unregistered images. 5. In the Resources section, specify the Minimum and Recommended values for virtual CPUs, physical CPUs, memory, and disk space. 6. Optional: Enter the root user password for the image. You can leave this field empty. 7. Click OK to submit the request.
49
Unregistering an image in the Image Library

You can unregister an image in the Tivoli Provisioning Manager Image Library, so that it will no longer be available in "Create project" or "Add server" tasks.
Before you begin

This task can only be performed by a cloud administrator. Ensure that you have required privileges.
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Manage Image Library > Unregister Image 2. Select a Resource Pool from the list. 3. Select the image that you want to unregister. 4. Click OK to submit the request.
Registering a VMControl image

This task describes the procedure necessary to deploy a project based on VMControl.
About this task

Starting with Tivoli Service Automation Manager 7.2.2, the network requirements are placed on the deployable images. For the VMControl configuration, you must annotate the network requirements in the discovered VMControl image.This step is accomplished by using the Register VM Image via IBM Systems Director VMControl offering. Prior to the registering, ensure that the following prerequisites are met: v A resource pool for VMControl is configured and enabled. v The image discovery for VMControl has been done. Moreover, check if the following information about the discovered image is available: v The number of the network interfaces that the image should get. v The type of networks that the image should connect to. v Which network interfaces should be the management one and which should be used for hostname resolvement. Finally, ensure that the following assumptions are not violated: v The number of network interface matches the discovery image. v Exactly one network interface is of the management type. v Exactly one network interface has the hostname resolve flag checked. v The network interfaces show up during provisioning in exactly the same sequence as they are registered. The first interface matches the first network definition in the VMControl deployable image and so forth. As part of the register image workflow, the above assumptions are enforced through checks and are realized during the Crate Project and Add Server offerings.
50
Registering a new image for a migrated resource pool

Follow these steps to register a new image for a resource pool that was migrated from a previous version.
About this task

Register an image for an upgraded resource pool according to the following pattern:
Procedure
1. Define a network interface for each subnet pool in the associated resource pool. 2. Determine which subnet pool is marked as ManagementNIC. Set the network interface type to Management. For all other subnet pools, set the type to Customer. 3. Determine which subnet pool is marked as HostnameResolveNIC
Modifications to the registered images

During the network migration process, the existing images are modified according to the new network model The new network model introduces two major changes according to which the images are modified: v Network configuration is moved from the resource pool level to the customer level. v Network requirements are attached to the registered images. Because of these changes, the following attributes are generated for the registered images during migration: v The number of network interfaces v Which of the network interfaces is the management interface v Which of the network interfaces is used for resolving the host name v Network usage that binds the image to the network configuration of the associated resource pool These attributes are generated on the registered images for each defined subnet pool in the associated resource pool. The x stands for 1 for the first subnet pool in the associated resource pool, and so on. v PMRDP.Net.x.NetworkType: Set to Management for the subnet pool that is marked as the Management NIC. Set it to Customer for all other subnet pools. v PMRDP.Net.x.HostnameResolve: Set to true for the subnet pool that is marked as HostnameResolveNIC. Set it to false for all other subnet pools. v PMRDP.Net.x.NetworkUsage: This usage value is generated based on the name of the resource pool, the network type, and a sequence number starting from 1 for the first network interface in the resource pool. For example, if the resource pool is named "RES1", the network type is "management", and it is the first network interface, the usage value is "RES1_Management_1".
51
Generated network segments

A network segment is generated for each enabled resource pool and each subnet pool. The network segments that are generated contain the following information from the resource pool: v The name of the generated network segment is concatenated from the name of the resource pool, the constant string NetworkSegment, and a sequence number starting with 0 for the first network segment (as the subnet pools also start with 0). For example, if the resource pool is named "RES1", and the segment corresponds to subnet pool 0, then the name is "RES1_NetworkSegment_0". v One subnet section for each subnet in the related subnet pool. v The segment type is Management for the subnet pool that is marked as ManagmentNIC. For all other subnet pools, the segment type is set to Customer. v The segment usage is generated based on the name of the resource pool, the network type, and a sequence number starting by 1 for the first network interface in the resource pool. For example, if a resource pool is named "RES1", the network type is Management, and it is the first network interface, then the usage value is "RES1_Management_1". This method assures that each network segment exactly matches to the corresponding network interface definition on the registered image. v The DNS section that is generated from the resource pools DNS definition
IBM Systems Director VMControl images

IBM Systems Director VMControl are processed in a special way because of the image metadata. Resource pools for this hypervisor have an additional property for each subnet pool. The name of the property is PMRDP.Net.SubnetAliasesPool_x. Each registered image for this resource pool has a list of network names. During the migration process, only the subnet pools that have a matching network name are migrated. Remember about the following points when migrating a VMControl network configuration: v The registered image must have a network interface of type Management. v The registered image must have a network interface resolving the host name. v The network names found in the registered image must be resolvable from the resource pool. The metadata properties on the registered images are generated in the same way as for all other resource pools as listed above.
Managing customers
You can create and remove customers by using the self-service user interface.
52
Creating customers
Use the self-service user interface to create customers. Additional setup steps may be required in the administrative user interface.
Before you begin

Before you can create a customer, the administrator must configure at least one network template.
About this task

In the self-service user interface for Tivoli Service Automation Manager version 7.2.2, each user is assigned to a customer. There is one predefined global customer: PMRDPCUST. Each new user is assigned to this customer if no other customers are defined and specified when the user is created. The customer assignment defines which resources a user can access. Administrators can define customer templates in the administrative user interface. These templates include configuration settings for a customer. When creating a customer, you can select a template. If no templates are available, after creating the customer in the self-service interface, the administrator must specify additional settings in the administrative interface. For more information about these tasks, see the Administering customers and their resources chapter in the Tivoli Service Automation Manager Installation and Administration Guide.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Manage Customers > Create Customer. 2. Specify a customer name. The name must be up to 12 characters and unique (not in use or deleted). 3. If configured, select Customer Template. If you do not select a customer template, additional settings must be configured in the administrative user interface to make the customer operational. 4. Select Network Configuration Template to define network configuration for the customer. 5. Select Customer Language Code. The value determines the default language for all users created for that customer. 6. Optional: Provide a description for the customer. 7. Click OK to submit the request.
Results
A customer object is created and network configuration is instantiated. If you used the customer template, the template configuration is copied to this customer object. If no template was used, the administrator must assign the resources to the customer in the administrative user interface, so that projects can be created.
What to do next
A cloud customer administrator who is associated with this customer can be created so that the customer's projects, teams, and users can be administered.
53
Removing customers
You can remove customers in the self-service user interface.
About this task

When you remove a customer, the customer itself and all user accounts for this customer become inactive. If any projects are still in progress, they will be decommissioned as scheduled, or cloud administrators can cancel them manually. The name of the removed customer can never be reused.
Procedure
1. In the Home panel, click Request a New Service > Virtual Server Management > Manage Customers > Remove Customer. 2. Select the customer from the list, and click OK to remove.
Results
The customer is changed to inactive state, and all user accounts related to this customer are deactivated as well. The users can no longer log on to the self-service user interface. By default, the state of the projects and resources does not change automatically. Projects are decommissioned according to their schedules. Cloud administrator can also cancel the projects and delete any saved images manually.
Managing users
Use these tasks to learn how to manage users and groups of users.
Creating users
Cloud and team administrators can create users and add them to the existing teams.
Before you begin

Ensure you meet the following prerequisites: v Users can only be created by cloud administrators, cloud customer administrators, and security administrators. v The requesting user must have grant option for the roles that they are assigning. v The requesting user must have grant option for the roles that they give grant option to. v The ability to assign to policy levels depends on the requesting user's level. For example, the users on cloud level can create users on cloud, and cloud customer levels. The users on cloud customer level can create users on the same level only. v The policy level must be registered in the system properties: pmrdp.security.cloud.level.group pmrdp.security.customer.level.group
About this task

Each user is assigned to a customer, security level, one or more security groups, and, optionally, to one or more teams:
54
v Cloud administrator can define for which customer the user is created by selecting this customer in the Home panel. The user can access only the resources assigned to the selected customer, global resources that are available to all customers. There is one predefined global customer: PMRDPCUST. Each new user is assigned to this customer if no other customers are specified during user creation. v The security level defines which cloud resources the user can access. There are two default security levels: Cloud level Users on cloud level can access the information and resources that are available in the cloud, regardless of customer limits. They are always assigned to a default global customer called PMRDPCUST. Customer level Users on this level are always assigned to one customer only, and they can only access information and resources assigned to that customer. Resource assignments are managed in the administrative user interface. v There are also nine security groups to which the user can belong. The group assignment determines which requests the user can access. Security groups are described in detail at http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/ topic/com.ibm.tsam_7.2.2.doc/c_tsam_userroles.html. A user belongs to exactly one policy level. v To be able to use a project, the user must be a member of the team that has access to this project. A user can be a member of more than one team, but all teams must belong to the same customer.
Procedure
1. In the Home panel, select the customer for which you want to create a user. 2. Click Request a New Service > Virtual Server Management > Manage Users and Teams > Create User. The Create User wizard opens. 3. In the Account Details tab: a. Enter a user ID and a display name for the user. The user ID can be up to 30 characters and must be unique. It cannot be in use or deleted. b. Specify and confirm the password. The password must be at least six characters in length. c. Select Make the account active to enable the user to log in after the new user registration is complete and click Next. 4. In the Security Groups tab: a. Select Security Policy. Cloud Level Policy If the user is subject to this policy, they can access all cloud resources and information regardless of which customer the information is assigned to. Cloud Customer Level Policy If the user is subject to this policy, they can only access the resources assigned to the customer they belong to. b. Assign the user to security groups. If you want the user to be able to assign other users to the selected group, select the Grant option check box. Click Next. 5. In the Personal Details tab, fill in the fields as required. Click Next. 6. In the Regional Settings tab, define locale. Click Next.
55
When you set the locale for the user in the self-service user interface, the same locale will be used in the administrative interface. Also, the language of the user interface will be set accordingly. 7. In the Team tab, define team membership. Note: v Team administrators can only select from teams they belong to. v A user can only be added to the teams that belong to the customer that was selected at the beginning of the user creation process. v Do not add cloud administrators to teams, because they can access them by default. If you add a cloud administrator to a team, the profile can be edited by team administrators. 8. Click Next to view a summary of the settings for the user. 9. Click Finish to submit the request.
Results
The user receives e-mail notification with their registration details.
Modifying user information

You can modify the user information and change their team membership.
Before you begin

Ensure you meet the following prerequisites: v Users can only be created by cloud administrators, cloud customer administrators, and security administrators. v The requesting user must have grant option for the roles that they are assigning. v The requesting user must have grant option for the roles that they give grant option to. v The ability to assign to policy levels depends on the requesting user's level. For example, the users on cloud level can create users on cloud, and cloud customer levels. The users on cloud customer level can create users on the same level only. v The policy level must be registered in the system properties: pmrdp.security.cloud.level.group pmrdp.security.customer.level.group
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Manage Users and Teams > Modify User. 2. Select the user from the list. The list includes only those users that meet the conditions for modification. 3. Modify the information as required. Note: User ID cannot be modified. 4. Click OK to submit the request.
56
Results
The user record will get updated accordingly. The affected user will receive e-mail notification about the changes.
User modification conditions

Learn about the conditions that must be met in order to modify a user. Team user, team administrator and cloud manager can modify only their own information. Cloud administrator, cloud customer administrator and security administrator can modify all users of the selected customer. Only users that meet the following conditions are displayed in the Modify User request panel and can be modified: 1. The user is active or inactive. 2. The user is in cloud level or cloud customer level policy. 3. The user meets one of the following conditions: v User is the same as the current user. v User is not PMRDPCAUSR. v User is a member of the same team as the current user. v Current user has permission to modify all users.
Removing a user
You can delete a user. The user account is removed and its ID can never be reused.
Before you begin

This task can only be performed by a cloud administrator. Ensure that you have the required privileges.
About this task

To remove a user:
Procedure
1. From the Home panel, select Request a New Service > Virtual Server Management > Manage Users and Teams > Remove User. 2. Select the user from the list. User details display. 3. Click OK to submit the request.
Results
The user is deleted from all teams that they were a member of, and the account ID can never be reused. Additionally, the deleted user's email address can be reused to create a new account ID.
57
Creating new teams

When you create a project, you need to define which team can access this project. Only one team can own a particular project and only the members of this team can access this project. Use the Create Team request to add new teams.
Before you begin

Ensure that you have the required privileges to submit this request.
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Manage Users and Teams > Create Team. 2. Provide the name for the team. It must be up to 8 characters and unique. 3. Optional: Specify the project account for the accounting purposes. 4. Optional: Provide team description. 5. Select the users from the list and click or to remove them. to add them to the team,
Note: v Up to 15 users can be added in one request. To add more users to the team, create a new request to modify the team once it has been created. v Cloud administrators should not be added to any teams, they can access them by default. 6. Click OK to submit the request.
Modifying team information

You can modify the details of the existing team and add or remove team users.
Before you begin

This task can be performed by cloud and team administrators. Team administrator can only modify the teams that he administers. Make sure that you have the required privileges. Team name cannot be modified.
About this task

To modify team information:
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Manage Users and Teams > Modify Team. 2. Select the name of the team that you want to modify. 3. Modify description or project account if necessary. 4. Use the and buttons to add or remove users.
Note: v Up to 15 users can be changed in one request. To add or remove more users, create a new request to modify the team. v Cloud administrators should not be added to any teams, they can access them by default.
58
Removing a team
You can use the Remove Team request to delete teams. Teams that own active projects cannot be deleted. To delete them, you need to cancel all the projects that the team can access beforehand.
Before you begin

This task can only be performed by cloud administrators. Make sure that you have the required privileges. Important: When you remove a team, its name can never be reused.
About this task

To remove a team:
Procedure
1. Select Home > Request a New Service > Virtual Server Management > Manage Users and Teams > Remove Team. 2. Select the name of the team that you want to delete. The list of users in this team is displayed. 3. Click OK to submit the request.
Results
The users are removed from the team and receive an e-mail notification that the team has been deleted. The accounts of the users of the deleted team remain active.
Viewing requests
You can view the full list of requests and their statuses using the My Requests section on the Home panel. The status bar shows the statuses of the last 20 requests by default. To see the data for all requests, click Show all requests in the left bottom corner of the section. Depending on the total number of requests, loading the full list can take up to a few minutes. Five last modified requests with recent activity and their statuses are listed in the My Requests section. When you click on the request name, the details for this request will be displayed in a separate window. Requests can be assigned one of the following statuses: v New - Service Request was created and is in the pre-approval stage. For Create Project, reservations are made in this stage. Next status is Waiting on Approval or Pending, depending on whether auto-approve is enabled. v Waiting on Approval - Request is waiting for an approver to approve it. Next status is Pending or Cancelled, depending on the decision of the approver. v Pending - The request is approved and post-approval tasks are run. Next state is Queued.
59
v Queued - Task is queued for execution. The request stays in this state until the requested start time is reached and no other request is run on the same project. Next state is In Progress. v In Progress - Management plan for a request is running. Next states are Resolved or Closed. v Resolved - Request was run successfully. v Partially Resolved - Request was only partially resolved, for example, because there was not enough resources to provision the requested number of servers. v Failed - The request failed to run. You can find more information on the failure in the Work Log section of the My Requests panel. v Canceled - The approver declined the request.
Procedure
1. In the left corner of the My Requests section on the Home panel, click Show all requests. Otherwise, you will be able to view the last 20 requests only. 2. Click Manage Requests... in the right corner of the section. A list of all submitted requests is displayed in a separate window, containing their statuses, the time the status was applied and the owner of the request. Note: To view the details for a request, select it in the table, and click the toolbar. The request details will be displayed in a separate window. on
Viewing the details of a submitted request

General details about a request and both work and communication logs are available to you for viewing. Tip: Five last modified requests with recent activity can be viewed in the My Requests section on the Home panel. Click on the request name to display the details.
Procedure
1. In the left corner of the My Requests section on the Home panel, click Show all requests. Otherwise, you will be able to view the last 20 requests only. 2. Click Manage Requests... in the right corner of the section. A list of all submitted requests will display in a separate window. on the toolbar. The View Service Request 3. Select a request and click window is displayed. 4. Use the General tab to view details about the request, the Work Log tab to view any error messages, or the Communication Log tab to view any notifications that were sent. The General tab displays the attribute list of the request with their respective values, except for security related values, like passwords.
60
Viewing and managing requests for approval

You can view the requests awaiting approval and approve, reject, or reassign them, if you have the required privileges. Tip: To enable the approval process, see Enabling or disabling automatic approval of requests in the Tivoli Service Automation Manager Installation and Administration Guide. Tip: Five approval requests with recent activity can be viewed in the My Approvals section on the Home panel. Click the approval request name to display its details.
About this task

The approval and delegation features are not configured by default, and need to be enabled in the administrative user interface.
Procedure
1. In the My Approvals section on the Home panel, select Manage Approvals... A list of approval requests that were assigned to you is displayed. 2. Select an approval request and click the Show Details button. The View Service Request window is displayed. 3. In the Approval section of the window, select one of the following options: v I reject this request v I approve this request v Reassign this request You can also provide justification for your choice in the Details field (no more than 50 characters in length). 4. Click OK to submit the request. Tip: If you do not want to view the details of the request, you can approve, reject, or reassign it using the corresponding buttons on the task bar of the Manage Approvals window.
Viewing projects
You can view the full list of projects and their statuses using the My Projects section on the Home panel. The status bar shows the statuses of the last 20 projects by default. To see the details for all projects, click Show all projects in the left corner of the section. Five last modified projects with recent activity and their statuses are listed in the My Projects section. When you click on the project name, the details for this project will be displayed in a separate window. Projects can be assigned one of the following statuses: v Approved v Canceled v Decommissioned v Decommissioning v Decommissioning Failed
61
v v v v v
Design Draft In Maintenance Not Set Operational
v Scheduled v In Transition
About this task

To view the full list of projects and their statuses:
Procedure
1. In the left corner of the My Projects section on the Home panel, click Show all projects. Otherwise, you will be able to view the last 20 projects only. 2. Click Manage Projects... in the right corner of the section. A list of all projects is displayed in a separate window, containing the information about the owner, status, the time the status was applied, and the dates for the project. 3. Select a project and click displayed. on the toolbar. The Project Details panel is
Results
You can now view details about the project.
Viewing and managing servers

You can view the list of all servers and manage them.
Procedure
1. From the Home panel on the Projects pod, select Manage Servers... A list of all servers will appear. Note: Server resource utilization values displayed as N/A indicate that a monitoring agent was not installed when the server was created. 2. Use the taskbar buttons to manage the selected server. Move the cursor over the button to view hover help or click ? on the title bar to view panel help.
Viewing Workload Deployer project details

General details about a Workload Deployer project and its servers is available to you for viewing.
Procedure
1. From the Home panel on the Projects pod, select Manage Projects... A list of all projects will appear. 2. Select a Workload Deployer project and click the Show Details button. The Workload Deployer Project Details panel is displayed.
Results
You can now view details about the project.
62
Tip: Five projects with recent activity and two upcoming projects can be viewed in the My Projects pod on the Home panel. Click on the project name to display the details.
63
64
Chapter 3. Using the WebSphere Cluster service

This section describes tasks related to the optional WebSphere Cluster Service, which is available as a separate chargeable component.
Customizing the WebSphere Cluster service definition

About this task
Before you begin to use the WebSphere Cluster Service, be sure you have completed the steps listed under Chapter 4. Configuring Service Automation Manager in the Installation and Configuration Guide. The WebSphere Cluster Service provides a ready-to-use service definition. You can customize the service definition as needed. The delivered definition is not modifiable, so that updates can be shipped to the existing service without interrupting existing deployments. To be able to start customizing, you can duplicate the provided definition.
Procedure
1. Log on to the administrative user interface. 2. Click Go To > Service Automation > Service Definitions. 3. 4. 5. 6. Search for the WebSphere Cluster service definition and open it. In the Select Action menu, click Duplicate Service Definition. Enter a number and a name. Click Save.
Results
The copy now contains its own instances of the management plans and topology templates, also comprising all the topology nodes. Refer to the applicable sections for a definition of these entities.
Instantiating the WebSphere Cluster Service

About this task
This section describes a scenario in which a WebSphere cluster is provisioned by instantiating an existing service definition for this service. To create such a service deployment instance the so called initial management plan of the service is executed internally. The initial management plan has three phases: preparation, approval, and execution. The following steps describe the procedure for performing these phases of the initial management plan. Note: This procedure assumes that no steps have been skipped within the service definition. If they have, the relevant inbox entry in each case is omitted.
65
Procedure
1. 2. 3. 4. Log on to the administrative user interface. Click Go To > Service Automation > Service Definitions. Press Enter to see all available service definitions. Select a service definition of the WebSphere Cluster service and press Enter.
5. Once the service definition is opened, choose the Service Deployment Instances tab. 6. Click Create Service Deployment Instance. An appropriate dialog is displayed. 7. Insert a name and optionally a requester for this instance. The requester ID will own the instance. The default is the current user. 8. Click Create Service Deployment Instance in the dialog to start the preparation phase. You will get a message that a workorder has been started. 9. 10. During the preparation phase, user interaction is required. The appropriate user (depending on the role) will receive workflow assignments. Log on with the appropriate user ID. 11. In the Start Center, you will see the next workflow assignment. Open this assignment to display the Service Topology Customization panel. 12. Depending on the values in the underlying service definition, you may need to add some missing data. When you want to add or change the initial cardinality (initial number of occurrences of this node), click Customize Selected Node and insert a value for the initial cardinality. 13. You then must specify the environment for each node you want to install. Click Customize Selected Node for each node and choose System p or Linux on System z allocation. Both heterogeneous and homogeneous environments are supported. 14. To finish your work on this screen, you must route the workflow. To do this, click the Route Workflow icon. 15. You will see the Edit Co-Location workflow assignment in the Start Center. Open this assignment to display the Co-Location Editor panel. 16. This panel allows you to specify multiple topology nodes that are to reside on the same physical server. To co-locate nodes: a. Define a group that will include the co-located topology nodes. b. Add the appropriate nodes to the newly created group. c. Click the Route Workflow icon to continue the workflow. In the Start Center you will see the next workflow assignment. Open this assignment to do the resource allocation. On this panel (Resource Allocation for Service Deployment Instance) you must specify the servers on which you want to provision the cluster elements. Each server must be referenced by a configuration item (CI). Select each row in sequence and determine the CI for which the provisioning is to apply. To determine the CI, from the detail menu click Filter using Requirements adjacent to the CI field. This shows you only the servers possible for your environment, such as only the servers applicable to an installation on System p. To finish your work on this screen, continue the workflow by clicking the Route Workflow icon.
17. 18.
19.
20.
66
21. In the Start Center, you will see the next workflow assignment. Open this assignment to view the contents of the job plan that is generated from the initial management plan. 22. On the Job Plan panel, you can view the details. 23. Continue by clicking on the Route Workflow icon. This terminates the preparation phase and begins the approval phase. 24. You will see the workflow assignment for approval in the Start Center. Open this assignment to approve the current configuration for the new service deployment instance. The Approve panel appears. On this panel, you can check all assignments done in the preparation phase. If you agree you can click the Approve icon in the toolbar. 25. Continue the workflow by clicking on the Route Workflow icon. If the request was approved, this will lead you into the execution phase, in which the actual deployment of the resources takes place. 26. In the execution phase, no user interaction is necessary unless an error situation occurs. In case of an error, you will see further assignments in your inbox in the Start Center. You then have the opportunity to try the current workflow again, ignore the failed action, or cancel the provisioning process. 27. The execution phase has completed when the status of the corresponding service deployment instance is set to Operational. Check the status with Go To > Service Automation > Service Deployment Instances.
Executing management plans for the WebSphere Cluster service

About this task
This section describes how to execute the existing management plans delivered with the service definition provided for the WebSphere Cluster service. Three management plans are used as examples. For a complete list of the available plans, see the WebSphere Cluster service section in the Installation and Configuration Guide. The process for each management plan is divided into preparation, approval, and execution phases.
Adding server
Learn how to add a server to an existing WebSphere cluster.
About this task

The following procedure guides you through the preparation, approval, and execution phases of the Add Server management plan of the WebSphere Cluster service. Note: This procedure assumes that no steps have been skipped within the service definition. If they have, the relevant inbox entry in each case is omitted.
Procedure
1. Log on to the administrative user interface (for example as a service instance operator). 2. Click Go To > Service Automation > Service Deployment Instances. 3. Filter for the service deployment instance. 4. Open the Management Plans tab.
67
5. To execute the ADDSERVER management plan click the green arrow to the right. You will be notified that a workorder has been started. During the preparation phase, user interaction is needed. The appropriate user will get workflow assignments. 6. Log on to the administrative user interface with the appropriate user role. In the Start Center, the Edit Co-Location workflow assignment is present. 7. Open the assignment to display the Co-Location Editor panel. 8. Decide if the new managed node is to be co-located with other topology nodes. If so, add this managed node to an existing group. Otherwise, the node remains in the Standalone Nodes list. 9. To continue the workflow, click the Route Workflow icon. 10. In the Start Center you will see the workflow assignment for resource allocation. Open this assignment to allocate the resources. 11. Insert the server CI on which to provision the new managed node. To determine the CI, select Filter using Requirements from the detail menu adjacent to the CI field. 12. Click the Route Workflow icon. In the Start Center, the workflow assignment for the job plan is displayed. 13. Open the assignment to view the contents of the job plan generated from the Add Server management plan. The details of the generated job plan are displayed in a new panel. 14. Click Route Workflow to continue the workflow. In the Start Center, you can see the workflow assignment for approving this change to the service deployment instance. 15. Open the assignment. This initiates the approval phase. 16. On the subsequent Approve panel, check all assignments made in the preparation phase. The instance manager can approve or reject the add-server operation. If you agree, click Approve in the toolbar and confirm with OK. Otherwise, click Reject. 17. Click Route Workflow to continue the workflow. If approval was granted, the execution phase is started. In the execution phase no user interaction is necessary unless an error situation occurs. If it does, you will see further assignments in your inbox in the Start Center. You then have the option to retry the current workflow, ignore the failed action, or cancel the provisioning process: a. Filter for the service deployment instance that you selected above. b. In the Workorders tab, check the state of management plan execution. c. If the state does not change to COMP (completed), open the Messages tab and check for error messages.
Removing server
Learn how to remove a server from an existing WebSphere cluster.
About this task

The following list describes how to step through the preparation, approval, and execution phases of the Remove Server management plan of the WebSphere Cluster service. Note: This procedure assumes that no steps have been skipped within the service definition. If they have, the relevant inbox entry in each case is omitted.
68
Procedure
1. Log on to the administrative user interface (for example as a service instance operator). 2. Click Go To > Service Automation > Service Deployment Instances. 3. Filter for the service deployment instance. 4. Open the Management Plans tab. 5. To execute the management plan REMOVESERVER, click the green arrow to the right. You will be notified that a workorder has been started. During the preparation phase, user interaction is required. The appropriate user will get workflow assignments. 6. Log on to the administrative user interface with the appropriate user role. In the Start Center, the job plan workflow assignment for Management Plan Target Selection is present. 7. On this screen, select and insert the managed node you want to remove. 8. Click Add node and select the appropriate node. 9. To continue the workflow, click the Route Workflow icon. In the Start Center, you will see the workflow assignment to review the job plan. 10. Open the assignment to view the contents of the job plan that is generated from the Remove Server management plan. A screen is displayed, where you can view the details of the generated job plan. 11. To continue the workflow, click the Route Workflow icon. In the Start Center, the workflow assignment for approval is displayed. 12. Open this assignment to approve this change to the service deployment instance. The approval phase is started. On the Approve panel, check the current server information and all the previous actions done in the preparation phase. For example, the instance manager can approve or deny the remove operation. 13. If you approve, click the Approve icon in the toolbar and then click OK. Otherwise, click the Reject icon. 14. Click the Route Workflow icon. If the request was approved, the execution phase is started. In the execution phase, no user interaction is necessary unless an error situation occurs. In case of an error, you will see further assignments in your inbox in the Start Center. You then have the choice to retry the current workflow, ignore the failed action, or cancel the provisioning process. a. Filter for the service deployment instance that you selected above. b. In the Workorders tab, check the state of management plan execution. c. If the state does not change to COMP (completed), open the Messages tab and check for error messages.
Stopping WebSphere Deployment Manager

Learn how to stop a WebSphere Deployment Manager.
About this task

The following procedure describes the steps for the preparation, approval, and execution phases of the Stop WebSphere Deployment Manager management plan of the WebSphere Cluster service. Note: This procedure assumes that no steps have been skipped within the service definition. If they have, the relevant inbox entry in each case is omitted.
69
Procedure
1. Log on to the administrative user interface (for example as a service instance operator). 2. Click Go To > Service Automation > Service Deployment Instances. 3. Filter for the service deployment instance. 4. Open the Management Plans tab. 5. To execute management plan STOPDMGR, click the green arrow to the right. You will be notified that a workorder has been started. During the preparation phase, user interaction is needed. The appropriate user will get workflow assignments. 6. Log on to the administrative user interface with the appropriate user role. In the Start Center, the job plan workflow assignment is present. 7. Open the assignment to view the job plan. A panel with the details of the generated job plan is displayed. 8. To continue the workflow, click the Route Workflow icon. In the Start Center, you will see the workflow assignment to approve this service deployment instance change. The approval phase starts. 9. On this panel you can check all assignments done in the preparation phase. For example, the instance manager can approve or reject the stop operation. If you agree, click the Approve icon in the toolbar and confirm with OK. Otherwise, click the Reject icon. 10. To finish your work on this screen, click Route Workflow. If the request was approved, execution phase starts. In the execution phase, no user interaction is necessary unless an error situation occurs. In the case of an error, further assignments are present in your inbox in the Start Center. You can then retry the current workflow, ignore the failed action, or cancel the provisioning process: a. Filter for the service deployment instance that you selected above. b. In the Workorders tab, check the state of management plan execution. c. If the state does not change to COMP (completed), open the Messages tab and check for error messages.
Deleting script logs from WebSphere Cluster servers

Scripts are executed on the servers provisioned by the WebSphere Cluster service to perform certain automated processes such as starting and stopping.
About this task

The scripts are executed in the directory /tmp/IBM/TSAM/<unique_ID>, where <unique_ID> is a unique 28-character ID for the associated request. These directories are not deleted automatically so that script execution logs can be reviewed as needed. It is advisable to set up a cron task that deletes directories older than a specified time, such as one week.
70
Appendix. Accessibility features

Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use software products successfully. The major accessibility features of Tivoli Service Automation Manager are described in this topic.
Accessibility features
User documentation provided in HTML and PDF format. Descriptive text is provided for all documentation images. The IT Service Management Information Center, and its related publications, are accessibility-enabled.
Related accessibility information

You can view the publications for Tivoli Service Automation Manager in Adobe Portable Document Format (PDF) using the Adobe Reader. PDF versions of the documentation are available in the information center.
IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility.
71
72
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
73
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
74
Glossary
This glossary includes terms and definitions for Tivoli Service Automation Manager. The following cross-references are used in this glossary: v See refers you from a term to a preferred synonym, or from an acronym or abbreviation to the defined full form. v See also refers you to a related or contrasting term. To view glossaries for other IBM products, go to www.ibm.com/software/globalization/ terminology. user ID and password are credentials that allow access to network and system resources.
E
escalation A course of action that runs when a task is not completed satisfactorily within a specific period of time.
H A
administrative system The hardware component of Tivoli Service Automation Manager from which software is installed on the management server and other administrative actions are taken. agent A process that performs an action on behalf of a user or other program without user intervention or on a regular schedule, and reports the results back to the user or program. hypervisor A program or a portion of Licensed Internal Code that allows multiple instances of operating systems to run simultaneously on the same hardware.
J
job plan A detailed description of work to be performed for a work order. A job plan typically includes required tasks and lists of estimated labor, materials, services, and tools needed to complete the work. job task An individual step in a job plan. Each job task triggers a specific workflow appropriate to that task.
application One or more computer programs or software components that provide a function in direct support of a specific business process or processes.
C
cardinality The number of elements in a set. configuration item Any component of an information technology infrastructure that is under the control of configuration management. credential Information acquired during authentication that describes a user, group associations, or other security-related identity attributes, and that is used to perform services such as authorization, auditing, or delegation. For example, a
M
managed environment An environment where services, such as transaction demarcation, security, and connections to Enterprise Information Systems (EISs), are managed on behalf of the running application. Examples of managed environments are the Web and Enterprise JavaBeans (EJB) containers. managed node A node that is federated to a deployment manager and contains a node agent and can contain managed servers.
75
management plan A set of tasks that modify a service deployment instance. management server The hardware component of Tivoli Service Automation Manager on which the product and its prerequisite middleware reside. Maximo business object A standardized data entity within Maximo. MBO See Maximo business object.
service topology In the context of a service definition, the set of physical IT components (such as hardware and software) that are available for inclusion in services based on that definition. On instantiation, the service topology is the actual set of these components in operation on behalf of the service deployment instance. service topology node In the context of a service definition, one element of the service topology to which resources can be allocated based on that definition. On instantiation, the service topology is the actual set of these components in operation on behalf of the service deployment instance. software definition The deployment configuration that describes how to install one or more installable software dependencies. It includes a list of installable files, software prerequisites, and advanced attributes. subnet See subnetwork. subnetwork A network that is divided into smaller independent subgroups, which still are interconnected.
middleware Software that acts as an intermediate layer between applications or between client and server. It is used most often to support complex, distributed applications in heterogeneous environments.
P
platform The combination of an operating system and hardware that makes up the operating environment in which a program runs. portlet A reusable component that is part of a Web application that provides specific information or services to be presented in the context of a portal.
T
TEMS See Tivoli Enterprise Monitoring Server. TEPS See Tivoli Enterprise Portal Server.
R
reservation The preallocation of configuration items for future deployments.
S
server image A file that contains the content and state of a virtual server, which can be saved and restored. service definition A set of data that provides the framework for deploying an IT landscape. service deployment instance An actual IT landscape derived from deploying a service definition.
Tivoli Enterprise Monitoring Server The monitoring server is the collection and control point for the performance and availability data and alerts received from monitoring agents. This server also manages the connection status of the agents and is responsible for tracking the online or offline status of the agents. Tivoli Enterprise Portal Server A Tivoli Monitoring server that provides the core presentation layer for retrieval, manipulation, analysis, and pre-formatting of data. The portal server receives data from the hub monitoring server in response to user actions at the portal client, and sends the data back to the portal client for presentation.
76
V
virtual server A server that shares its resources with other servers to support applications. VMware A commercially available, proprietary virtualization environment for System x and similar platforms.
W
WO See work order. workflow 1. The sequence of activities performed in accordance with the business processes of an enterprise. 2. The structured sequence of activities and tasks that are used to implement a specific change, release, or other process, including automatic routing and tracking of records for approval and other tasks. work order A record that contains information about work that must be performed for an asset, location, configuration item (CI), and so on.
X
Xen A open-source virtualization environment for System x and similar platforms.
Glossary
77
78
Trademarks and Service Marks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml. Adobe, the Adobe logo, PostScript, and the PostScript logo are trademarks or registered trademarks of Adobe Systems, Incorporated, in the United States and/or other countries. Intel, the Intel logo, Intel Inside, the Intel Inside logo, Intel Centrino, the Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others.
79
80
Index A
accessibility features 71 administrative user interface applications 3 applications Co-Location Editor 7 IT Topology Work Orders 8 Management Plan Input Parameters 9 Management Plan Target Selection 9 Monitoring Definition 4 Monitoring Definition Instances 4 Monitoring Definition Instantiation 4 Node Attribute Uniqueness Violations 7 overview 3 Resource Allocation for Service Deployment Instance 4 Resource Allocation Record 4 Service Automation Manager 9 Service Definitions 4 Service Deployment Instances 4 Service Topology 7 Service Topology Customization Editor 9 Service Topology Node 7 Service Topology Node Operation 7 Situation Analysis 5 Topology Customization 7 approvals 27
I
IBM Software Support submitting a problem xii IBM Support Assistant ix image unregistering 50 Image Library managing 45 registering KVM images 48 registering other images 48 registering POWER LPAR 46 registering VMware images 45, 49 registering Xen images 47 unregistering image 50 images registering 48 images, KVM registering 48 images, POWER LPAR registering 46 images, VMware registering 45, 49 images, Xen registering 47 Installation Launchpad overview 2 Internet, search for problem resolution ix Internet, searching for problem resolution ix
project (continued) creating with Workload Deployer pattern 33 modifying 34 modifying reservation dates 37 Workload Deployer pattern, canceling 34 project, Workload Deployer viewing 62 projects viewing 62
R
reporting overview 19 reports types 19 requests 60 accessing in self-service user interface 25 approving 28, 61 rejecting 61 viewing all 60 viewing status 60
S
self-service interface accessing 25 logging in 25 Self-Service Virtual Server Management 25 overview 2 Tivoli Provisioning Manager integration 3 Self-Service Virtual Server Provisioning adding virtual servers to existing project 34 approvals and notifications 27 canceling project 32 canceling Workload Deployer project 34 deleting server image 44 modifying reservation dates 37 modifying server capacity 38 new project 29 removing virtual server 37 restoring server from image 44 saving server image 43 server image management overview 22 service structure 17 services Self-Service Virtual Server Management 2 WebSphere Cluster Service 9 Software Support contact x
C
components overview 2 configuration registering a VMControl image customer creating 53 removing 54 customer support contact x 50
K
knowledge bases, searching ix
N
notifications 27
O
offerings accessing in self-service user interface 25
E
education see Tivoli technical training email notification overview 27 ix
P
performance monitoring 15 problem determination describing problem for IBM Software Support xi determining business impact for IBM Software Support xi submitting a problem to IBM Software xii project adding servers 34 canceling 32 creating 29
F
fixes, obtaining ix, x
G
glossary 75
81
Software Support (continued) describing problem for IBM Software Support xi determining business impact for IBM Software Support xi support information viii
T
team changing membership 58 creating 58 modifying information 58 removing 59 Tivoli Service Automation Manager components 2 Tivoli technical training ix topology node attributes 13 training, Tivoli technical ix
WebSphere Cluster service (continued) removing a server 68 stopping Deployment Manager 69 using 65 Workload Deployer overview 23 Workload Deployer pattern canceling a project 34 creating a project 33
U
usage and accounting function overview 20 user changing team membership create 54 managing 54 modifying information 56 removing 57 user interface 3 56
V
viewing details 60 virtual server adding 34 modifying 38 removing 37 resetting password 40 restarting 41 restoring from saved image starting 41 stopping 41 virtual server image backing up 42 creating 43 deleting 44 removing 44 restoring 42 saving 43 virtual servers managing 62 viewing 62
44
W
Websphere Cluster service deleting logs 70 management plans 67 WebSphere Cluster service adding a server 67 customizing 65 instantiating 65 management plans 67
82
Product Number: 5724-W78
Printed in USA
SC34-2656-00

TSAM User Guide

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

TSAM User Guide

Transféré par

Droits d'auteur :

Formats disponibles

Tivoli Service Automation Manager

Tivoli Service Automation Manager

Chapter 2. Using the Self-Service Virtual Server Management offerings. . 25

Chapter 1. Tivoli Service Automation Manager overview . . . . . . . . . . 1

Copyright IBM Corp. 2008, 2011

Appendix. Accessibility features. . . . 71 Notices . . . . . . . . . . . . . . 73 Glossary . . . . . . . . . . . . . . 75

Chapter 3. Using the WebSphere Cluster service . . . . . . . . . . . 65

Trademarks and Service Marks . . . . 79 Index . . . . . . . . . . . . . . . 81

Tivoli Service Automation Manager V7.2.2 User's Guide

Copyright IBM Corp. 2008, 2011

Tivoli Service Automation Manager V7.2.2 User's Guide

Who should read this information

What's new in this release

Copyright IBM Corp. 2008, 2011

Documentation URL http://publib.boulder.ibm.com/infocenter/ tivihelp/v45r1/index.jsp?topic= %2Fcom.ibm.tivoli.tpm.doc%2Fwelcome %2Fic-homepage.html

IBM Tivoli Directory Server, version 6.3

DB2, version 9.5

IBM WebSphere Application Server Network Deployment, version 6.1

Tivoli Service Automation Manager V7.2.2 User's Guide

Getting technical training

Searching knowledge bases

Searching the Internet

Using IBM Support Assistant

Finding product fixes

About this task

Getting email notification of product fixes

Contacting IBM Software Support

About this task

Setting up a software maintenance contract

Tivoli Service Automation Manager V7.2.2 User's Guide

Determine the business impact

Severity 2 Severity 3 Severity 4

Describe the problem and gather background information

Submit the problem to IBM Software Support

Tivoli Service Automation Manager V7.2.2 User's Guide

Chapter 1. Tivoli Service Automation Manager overview

Copyright IBM Corp. 2008, 2011

Tivoli Service Automation Manager Installation Launchpad

Self-Service Virtual Server Management

Tivoli Service Automation Manager V7.2.2 User's Guide

Applications in the administrative user interface

Chapter 1. Product overview

Service Definitions application

Service Deployment Instances application

Resource Allocation applications

Monitoring Definition applications for WebSphere Cluster service

Tivoli Service Automation Manager V7.2.2 User's Guide

Situation Analysis application

Cloud Server Pool Administration application

Cloud Storage Pool Administration application

Cloud Network Administration application

Cloud Customer Administration application

Tivoli Service Automation Manager V7.2.2 User's Guide

Service Topology application

Service Update Package application

Service Topology Node applications

Chapter 1. Product overview

IT Topology Work Orders application

Tivoli Service Automation Manager V7.2.2 User's Guide

WebSphere Cluster Service

Chapter 1. Product overview

Tivoli Service Automation Manager V7.2.2 User's Guide

Tivoli Service Automation Manager V7.2.2 User's Guide