TSAM User Guide

Tivoli Service Automation ManagerVersion 7.2.2

User's Guide

SC34-2656-00

��

Tivoli Service Automation ManagerVersion 7.2.2

User's Guide

SC34-2656-00

��

NoteBefore 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 (programnumber 5724–W78), available as a licensed program product, and to all subsequent releases and modifications untilotherwise 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 arenot stocked at the addresses given below.

Address comments on this publication to:

IBM Deutschland Research and Development GmbHIBM Systems and Technology GroupSystems Software DevelopmentDept. 2705, Bldg. 71032-16Schoenaicher Str. 22071032 BoeblingenGermany

FAX (Germany): 07031 16 4240FAX (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 anyway 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 Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . v

Preface . . . . . . . . . . . . . . viiWho should read this information. . . . . . . viiWhat's new in this release . . . . . . . . . viiUseful links . . . . . . . . . . . . . . viiiSupport information . . . . . . . . . . . viii

Getting technical training . . . . . . . . . ixSearching knowledge bases . . . . . . . . ix

Searching the Internet . . . . . . . . . ixUsing IBM Support Assistant . . . . . . ixFinding product fixes . . . . . . . . . ixGetting email notification of product fixes . . x

Contacting IBM Software Support . . . . . . xSetting up a software maintenance contract . . xDetermine the business impact . . . . . . xiDescribe the problem and gather backgroundinformation . . . . . . . . . . . . xiSubmit the problem to IBM Software Support xii

Chapter 1. Tivoli Service AutomationManager overview . . . . . . . . . . 1Product components . . . . . . . . . . . . 2

Tivoli Service Automation Manager InstallationLaunchpad . . . . . . . . . . . . . . 2Self-Service Virtual Server Management . . . . 2User interfaces. . . . . . . . . . . . . 3Applications in the administrative user interface . 3

Service Definitions application . . . . . . 4Service Deployment Instances application . . 4Resource Allocation applications . . . . . . 4Monitoring Definition applications forWebSphere Cluster service . . . . . . . . 4Situation Analysis application . . . . . . 5Cloud Server Pool Administration application 5Cloud Storage Pool Administration application 5Cloud Network Administration application . . 5Cloud Customer Administration application . . 6Service Topology application . . . . . . . 7Service Update Package application. . . . . 7Service Topology Node applications . . . . 7IT Topology Work Orders application . . . . 8Auxiliary applications . . . . . . . . . 9

WebSphere Cluster Service. . . . . . . . . 9Service topology node attributes . . . . . 13Performance monitoring support for theWebSphere Cluster service . . . . . . . 15

Service structure. . . . . . . . . . . . . 17Service provider support . . . . . . . . . . 18Reporting function . . . . . . . . . . . . 19

Tivoli Service Automation Manager report typesand content . . . . . . . . . . . . . 19Tivoli Usage and Accounting Manager reportingfunction . . . . . . . . . . . . . . 20

Additional software installation on the provisionedservers . . . . . . . . . . . . . . . . 21Managing POWER LPAR provisioning withVMControl . . . . . . . . . . . . . . 22Image management. . . . . . . . . . . . 22Workload Deployer overview . . . . . . . . 23

Chapter 2. Using the Self-ServiceVirtual Server Management offerings. . 25Submitting requests in the self-service user interface 25Approvals and notifications . . . . . . . . . 26

Email notifications . . . . . . . . . . . 27Approving requests. . . . . . . . . . . 28

Creating a project and adding virtual servers . . . 29Creating a project from a saved server image . . . 31Canceling a project . . . . . . . . . . . . 32Creating projects with a Workload Deployer pattern 33Canceling Workload Deployer pattern projects. . . 34Modifying project . . . . . . . . . . . . 34

Adding virtual servers to an existing project . . 34Adding a server from a saved image . . . . . 36Modifying reservation dates . . . . . . . . 37Removing a virtual server . . . . . . . . 37

Modifying server . . . . . . . . . . . . 38Modifying server resources . . . . . . . . 38

Windows disk size modification afterchanging password . . . . . . . . . . 40

Resetting a server password . . . . . . . . 40Starting a server . . . . . . . . . . . . 41Stopping a server . . . . . . . . . . . 41Restarting a server . . . . . . . . . . . 41Installing software on server. . . . . . . . 41

Backing up and restoring server images . . . . . 42Creating server image . . . . . . . . . . 43Restoring a server from image . . . . . . . 44Removing saved images . . . . . . . . . 44

Managing Image Library . . . . . . . . . . 45Registering VMware images . . . . . . . . 45Registering POWER LPAR images . . . . . . 46Registering Xen images . . . . . . . . . 47Registering KVM images . . . . . . . . . 48Registering z/VM image . . . . . . . . . 48Registering POWER LPAR images via IBMSystems Director VMControl . . . . . . . 49Unregistering an image in the Image Library . . 50Registering a VMControl image . . . . . . 50Registering a new image for a migrated resourcepool . . . . . . . . . . . . . . . . 51

Modifications to the registered images . . . 51Generated network segments . . . . . . 52

Managing customers . . . . . . . . . . . 52Creating customers . . . . . . . . . . . 53Removing customers . . . . . . . . . . 54

Managing users . . . . . . . . . . . . . 54Creating users . . . . . . . . . . . . 54

© Copyright IBM Corp. 2008, 2011 iii

Modifying user information . . . . . . . . 56User modification conditions . . . . . . 57

Removing a user . . . . . . . . . . . 57Creating new teams . . . . . . . . . . 58Modifying team information. . . . . . . . 58Removing a team . . . . . . . . . . . 59

Viewing requests . . . . . . . . . . . . 59Viewing the details of a submitted request . . . . 60Viewing and managing requests for approval . . . 61Viewing projects . . . . . . . . . . . . . 61Viewing and managing servers . . . . . . . . 62Viewing Workload Deployer project details . . . . 62

Chapter 3. Using the WebSphereCluster service . . . . . . . . . . . 65Customizing the WebSphere Cluster servicedefinition . . . . . . . . . . . . . . . 65Instantiating the WebSphere Cluster Service . . . 65Executing management plans for the WebSphereCluster service . . . . . . . . . . . . . 67

Adding server . . . . . . . . . . . . 67Removing server . . . . . . . . . . . 68Stopping WebSphere Deployment Manager. . . 69

Deleting script logs from WebSphere Cluster servers 70

Appendix. Accessibility features. . . . 71

Notices . . . . . . . . . . . . . . 73

Glossary . . . . . . . . . . . . . . 75A . . . . . . . . . . . . . . . . . . 75C . . . . . . . . . . . . . . . . . . 75E . . . . . . . . . . . . . . . . . . 75H. . . . . . . . . . . . . . . . . . 75J . . . . . . . . . . . . . . . . . . 75M . . . . . . . . . . . . . . . . . 75P . . . . . . . . . . . . . . . . . . 76R . . . . . . . . . . . . . . . . . . 76S . . . . . . . . . . . . . . . . . . 76T . . . . . . . . . . . . . . . . . . 76V . . . . . . . . . . . . . . . . . . 77W . . . . . . . . . . . . . . . . . 77X . . . . . . . . . . . . . . . . . . 77

Trademarks and Service Marks . . . . 79

Index . . . . . . . . . . . . . . . 81

iv Tivoli Service Automation Manager V7.2.2 User's Guide

Tables

1. Documentation links for Tivoli ServiceAutomation Manager component products . . viii

2. Uniqueness scopes for topology nodeattributes . . . . . . . . . . . . . 14

3. Uniqueness specifications for attribute names 144. Uniqueness resolution rule . . . . . . . 155. Summary of Tivoli Service Automation

Manager Reports and Content . . . . . . 19

6. Access to requests depending on the securitygroup . . . . . . . . . . . . . . 26

7. Restrictions for the resources values . . . . 298. Restrictions for the resources values . . . . 359. OS Family and Version values . . . . . . 46

© Copyright IBM Corp. 2008, 2011 v

vi Tivoli Service Automation Manager V7.2.2 User's Guide

Preface

This publication documents how to use the online user interfaces of Tivoli® ServiceAutomation Manager.

Who should read this informationThis information is intended for users of the online interfaces provided by TivoliService Automation Manager.

What's new in this releaseThis section provides a summary of new product features and enhancements toexisting functions.

Extensions Guide

The new guide available for Tivoli Service Automation Manager version 7.2.2documents how to build new or extend existing solutions in the areas of cloudcomputing or IT service management using the product.

Service provider support

The service provider feature introduced with Tivoli Service Automation Manager7.2.2 allows for creating clouds that can be used by multiple customers. Resourcescan be used more efficiently and customers are able to support multiple internalorganizations. The Cloud Customer Administration application allows you toconfigure 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 toassign additional storage resources to your System p virtual machines. The newCloud Storage Pool Administration application enables you to easily manage yourcloud storage pools.

Reliability, availability, and serviceability (RAS)

To support troubleshooting when using Tivoli Service Automation Manager, sevenRAS functions are introduced in version 7.2.2, including three new types of BIRTreports, and documentation on best practices.

New application for managing your cloud server pools

The Cloud Server Pool Administration application enables you to create cloudserver pools in two ways. You can either use the application to import the

© Copyright IBM Corp. 2008, 2011 vii

customized DCM items, or you can create a cloud server pool using the interfaceof the application. You can also use it to perform a variety of operations on thecloud server pools.

Network changes

You can define the network metadata of an image, for example how many andwhat kind of network interfaces the image requires. You can also use the extensiblenetwork model. The new Cloud Network Administration application enables youto manage network templates, network segments, subnetworks, virtual switchtemplates, and network configuration instances.

Useful linksTivoli Service Automation Manager is a component product. Use the followingtopic to find more information about the related products and the requirementsthat must be met for them.

Table 1. Documentation links for Tivoli Service Automation Manager component products

Product name Documentation URL

IBM® Tivoli Provisioning Manager, version7.2.0.2

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, version7.2.0.1

http://publib.boulder.ibm.com/infocenter/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

IBM Tivoli Directory Server, version 6.3 http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=%2Fcom.ibm.IBMDS.doc%2Fwelcome.htm

DB2®, version 9.5 http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.doc/welcome.html

IBM WebSphere® Application ServerNetwork Deployment, version 6.1

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.doc/info/aes/ae/welcome_base61.html

Support informationYou can find support information for IBM products from a variety of sources.v “Getting technical training” on page ixv “Searching knowledge bases” on page ixv “Contacting IBM Software Support” on page x

viii Tivoli Service Automation Manager V7.2.2 User's Guide








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







Getting technical trainingInformation about Tivoli technical training courses is available online.

Go to http://www.ibm.com/software/tivoli/education/.

Searching knowledge basesIf you have a problem with Tivoli Service Automation Manager, search throughone of the many available knowledge bases.

You can begin with the IT Service Management Information Center athttp://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/index.jsp.

Searching the InternetIf you cannot find an answer to your question in the IT Service Managementinformation center, search the Internet for the latest, most complete information tohelp you resolve your problem.

To search multiple Internet resources, go to the IBM Tivoli Support website. Fromthere, you can search a number of resources, including:v IBM technotesv IBM downloadsv IBM Redbooks®

If you still cannot find a solution to the problem, you can search forums andnewsgroups on the Internet for the latest information to help you resolve it.

Using IBM Support AssistantAt no additional cost, you can install on any workstation the IBM SupportAssistant, a stand-alone application. You can then enhance the application byinstalling product-specific plug-in modules for the IBM products that you use.

The IBM Support Assistant helps you gather support information when you needto open a problem management record (PMR), which you can then use to track theproblem. The product-specific plug-in modules provide you with the followingresources:v Support linksv Education linksv Ability to submit problem management reports

For more information, see the IBM Support Assistant Web site athttp://www-01.ibm.com/software/support/isa/.

Finding product fixesA 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.

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

http://www.ibm.com/software/tivoli/education/

http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/index.jsp

http://www-01.ibm.com/software/support/isa/

http://www.ibm.com/software/tivoli/products/

http://www.ibm.com/software/tivoli/products/

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 fixesYou can get notifications about fixes and other news about IBM products.

Procedure1. 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 theappropriate 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 SupportYou can contact IBM Software Support if you have an active IBM softwaremaintenance contract and if you are authorized to submit problems to IBM.

About this task

Before you contact IBM Software Support, follow these steps:

Procedure1. 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 forinformation on contacting IBM Software Support.

Setting up a software maintenance contractTo be able to submit a problem to IBM, you need to have a software maintenancecontract. The type of contract that you need depends on the type of product youhave.

Procedurev For IBM distributed software products (including, but not limited to, Tivoli,

Lotus®, and Rational® products, as well as IBM DB2 and IBM WebSphereproducts that run on Microsoft Windows or UNIX operating systems), enroll inIBM Passport Advantage®:– Enrolling online: Go to the Passport Advantage Web page at

http://www.ibm.com/software/lotus/passportadvantage/, click How toenroll, and follow the instructions.

x Tivoli Service Automation Manager V7.2.2 User's Guide

http://www.ibm.com/software/lotus/passportadvantage/

– Enrolling by Telephone: For the telephone number for your country, go tothe IBM Software Support Handbook webpage at http://www14.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html andclick Contacts.

v For IBM eServer™ software products, you can purchase a software maintenanceagreement by working directly with an IBM marketing representative or an IBMBusiness Partner. For more information about support for eServer softwareproducts, go to the IBM Technical support advantage webpage athttp://www.ibm.com/servers/eserver/techsupport.html.

What to do next

If you are not sure which type of software maintenance contract you need, call1-800-IBMSERV (1-800-426-7378) in the United States. For a list of supporttelephone numbers for your location, go to the Software Support Handbook pageat http://www14.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html.

Determine the business impactWhen you report a problem to IBM, you are asked to supply a severity level. Inorder to provide this information, understand and assess the business impact ofthe problem you are reporting.

Severity 1 Critical business impact: You are unable to use the program,resulting in a critical impact on operations. This conditionrequires an immediate solution.

Severity 2 Significant business impact: The program is usable but isseverely limited.

Severity 3 Some business impact: The program is usable with lesssignificant features (not critical to operations) unavailable.

Severity 4 Minimal business impact: The problem causes little impact onoperations, or a reasonable circumvention to the problem hasbeen implemented.

Describe the problem and gather background informationWhen explaining a problem to IBM, it is helpful to be as specific as possible.Include all relevant background information so that IBM Software Supportspecialists 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

http://www14.software.ibm.com/webapp/set2/sas/f/handbook/contacts.html


http://www.ibm.com/servers/eserver/techsupport.html


Submit the problem to IBM Software SupportYou can submit the problem to IBM Software Support online or by telephone.

OnlineGo to the IBM Software Support Web site at http://www.ibm.com/software/support/probsub.html. Enter your information into theappropriate problem submission tool.

By TelephoneFor the telephone number to call in your country, go to the contacts pageof 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 inaccuratedocumentation, IBM Software Support creates an Authorized Program AnalysisReport (APAR). The APAR describes the problem in detail. If a workaround ispossible, IBM Software Support provides one for you to implement until the APARis resolved and a fix is delivered.

xii Tivoli Service Automation Manager V7.2.2 User's Guide

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/probsub.html



Chapter 1. Tivoli Service Automation Manager overviewTivoli Service Automation Manager assists inthe automated provisioning, management,and deprovisioning of cloud resources,comprised of hardware servers, networks,operating systems, middleware, andapplication-level software. Severalvirtualization environments (hypervisors) aresupported in the process of individual virtualserver provisioning.

Tivoli Service Automation Manager also provides management support for servicesconsisting of a specific set of middleware, in combination with AIX®, and Linux(System x® and System z®). IBM provides many automation and best-practiceservice definition templates, including specialized job plans or workflows. TivoliService Automation Manager makes use of the entire spectrum of Tivoli processautomation engine tools.

Tivoli Service Automation Manager helps you define and automate services thatare lifecycle oriented, for example, a service to establish and administer an ITserver network for a limited period of time, to satisfy increased demand forprocessing capacity or to serve as a test environment. Predefined service definitionsdetermine the overall framework for the services. The actual service instances arerequested using these service definitions. The Self-Service Virtual ServerManagement environment, is used by the cloud users to request provisioning andmanage the virtual environments.

Tivoli Service Automation Manager uses IBM Service Management and the Tivoliprocess automation engine as an integration platform. IBM Service Management isan approach designed to automate and simplify the management of businessservices. It concentrates on four areas:v Technology integration and standardsv Improved collaboration among IT people spread across organizational silosv Best-practices based process modules for automated process executionv Sharing of business-critical IT information to improve decision making

Tivoli Service Automation Manager offers the following standard serviceenvironments and definitions:

Self-Service Virtual Server Management environmentIn this service environment, which is a collection of service offerings, usersrequest the provisioning of projects comprising virtual servers. The serviceenvironment has an intuitive self-service user interface with Web 2.0technology for enhanced interactive feedback. An administrator function isalso provided.

WebSphere Cluster ServiceThis optional, separately priced service provisions and manages aWebSphere cluster.

© Copyright IBM Corp. 2008, 2011 1

Product componentsThis section provides the overview the components of Tivoli Service AutomationManager.

Tivoli Service Automation Manager Installation LaunchpadThe Tivoli Service Automation Manager Installation Launchpad guides the userthrough the installation process.

For details, see "Installing Tivoli Service Automation Manager" in the Installationand Administration Guide.

Self-Service Virtual Server ManagementTivoli Service Automation Manager provides support for user-initiatedprovisioning and management of virtual servers on System x, System p, or Systemz. The product also supports the IBM CloudBurst® and IBM Workload Deployerproducts, which are based on System x hardware. The self-service environment issupported by the self-service user interface. The Self-Service Virtual ServerManagement functional addresses a long-standing need for efficient managementof self-service deployment of virtual servers and associated software. Using a set ofsimple, point-and-click tools, the user can select a software stack and have thesoftware automatically installed or uninstalled in a virtual host that isautomatically provisioned.

These tools integrate with Tivoli Service Request Manager® to provide aself-service portal for reserving, provisioning, recycling, and modifying virtualservers, 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 xv KVM on System xv LPARs on Power Systemsv z/VM® guests on System zv WebSphere CloudBurst Appliance

This function ensures the integrity of fulfillment operations that involve a widerange 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 atsome future time

v For each virtual server created, installing a software image that includes anoperating system and other applications that are associated with the image.

v Installing additional software on the provisioned virtual machinesv Deleting a virtual server when it is no longer needed, freeing up resources for

other serversv Saving virtual server images and restoring the servers to their previous statev 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.

2 Tivoli Service Automation Manager V7.2.2 User's Guide

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-servicevirtual server provisioning process, growing and adapting the process at your ownpace, and adding task automation to further reduce labor costs around definedprovisioning 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 imagesacross the data center.

After this initial setup has been completed, the administrator associates the virtualserver offerings with Tivoli Provisioning Manager virtual server templates. TheImage Library is used as the source for software images to be used in provisioningthe virtual servers.

User interfacesTivoli Service Automation Manager provides two options for user interaction: aself-service user interface and an administrative user interface.

The administrative user interface is the standard interface within the Tivoliprocess automation engine framework (formerly known as Maximo). It is intendedprimarily 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 andadministrators. It is based on the Web 2.0 standard, which enables for thecontext-sensitive and real-time display updating based on the current entry orselection made by the user. The result is a faster access to the necessaryinformation without having to go through a sequence of clicks, dialogs, andpanels.Related tasks:“Submitting requests in the self-service user interface” on page 25Log on to the self-service user interface, where you can access the offerings andrequest provisioning.

Applications in the administrative user interfaceMany of the components of Tivoli Service Automation Manager are implementedin the form of applications within the administrative user interface. This sectiondescribes the available applications and their functions.

Chapter 1. Product overview 3

Service Definitions applicationYou use the Service Definitions application to create or modify a service definitionand to instantiate services based on that definition. You can also customize theservice definition delivered with Tivoli Service Automation Manager to suit yourrequirements more precisely.

For services that are instantiated (that is, represented with actual hardware) basedon an approved service definition, the Service Definitions application triggers theinstantiation workflow. Self-Service Virtual Server Management, however, employsan interactive process for instantiation that is carried out using the Service RequestManager.

Service Deployment Instances applicationYou use the Service Deployment Instances application to manage existingdeployments (physical implementations) of a service.

Resource Allocation applicationsYou use Resource Allocation applications allow you to document and reviewrequirements and allocate configuration items (CIs). Resources are allocated tofulfill 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 tofulfill. These items are classified using the standard Tivoli process automationengine classification mechanism, which means that the user can reuse predefinedforms.

v Allocate configuration items (CIs)

Once the requirements are set and approved, a CI has to be allocated thatmatches those requirements. The user can review and change the setrequirements. 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 Recordv Resource Allocation for Service Deployment Instance

Monitoring Definition applications for WebSphere Cluster serviceIf you need to modify the service definition delivered with Tivoli ServiceAutomation Manager to match your requirements for performance monitoring, youcan change the monitoring definition using the set of Monitoring Definitionapplications.

Note: This section pertains only to performance monitoring within the scope ofthe Tivoli Service Automation Manager WebSphere Cluster service. It does notdescribe displaying resource usage data collected by Tivoli Monitoring agents thatare installed on servers provisioned using the Self-Service Virtual ServerManagement component.

Performance monitoring is supported in combination with IBM Tivoli Monitoringon distributed platforms (Linux on System x, System p, and System z, and AIX).The Monitoring Definition applications refer to the monitoring environment beingused with respect to any given service definition and service deployment instance.


IBM Tivoli Monitoring must be installed separately. It is no longer offered as aninstallation option for Tivoli Service Automation Manager. Alternatively, aseparately installed Tivoli Monitoring environment can be used.

For details on setting up IBM Tivoli Monitoring, see the documentation for thisproduct 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 Definitionv Monitoring Definition Instantiationv Monitoring Definition Instances

The handling of performance-related situations detected by the monitoring agentsin a deployed landscape is provided by the Situation Analysis application.

Situation Analysis applicationYou use the Situation Analysis application to review the context of the servicedeployment instance in which a performance-related event occurred, including thetopology of the service instance, the CIs involved, and the monitoring definitions.

For an overview of the situation analysis function, see “Performance monitoringsupport for the WebSphere Cluster service” on page 15.

Note: This information pertains only to performance monitoring within the scopeof the Tivoli Service Automation Manager WebSphere Cluster service. It is notrelated to displaying resource usage data collected by Tivoli Monitoring agentsthat are installed on servers provisioned using the Self-Service Virtual ServerManagement component.

Cloud Server Pool Administration applicationUse this application to define and configure cloud server pools after theinstallation of Tivoli Service Automation Manager.

This application helps you define and configure a cloud server pool for each backend on which you want to provision servers.

Cloud Storage Pool Administration applicationUse this application to create and configure cloud storage pools.

Cloud storage pools are a flexible solution to add additional storage to yourprovisioned servers. They are a collection of storage resources for additional disksthat can be assigned to a newly created image if you need more storage space thanjust the boot disk.

Cloud Network Administration applicationThis application is used to perform cloud configurations and to manage them in aproduction environment.

The Cloud Network Administration application is one of the applications that areused during the Tivoli Service Automation Manager configuration process. Use itafter performing the configuration of the backend resources and of the storagepool. The network configurations handled by this application include:v Importing network Data Center Model (DCM) objects and parameters that

describe subnetworks and virtual switches


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=/com.ibm.itm.doc/toc.xml


v Importing network templates that contain predefined network configurationparameters

After performing these initial configurations and setting up a productionenvironment, Tivoli Service Automation Manager configurations change over time.The Cloud Network Administration application helps you manage these changesby handling the following tasks:v Importing a new revision of a network templatev Changing the status of a network templatev Deleting a network templatev Listing network templatesv Showing details of a network template

Cloud Customer Administration applicationThe Cloud Customer Administration application provides the administrator withan overview of the allocated resources of a specific customer. The application isorganized into multiple tabs. These tabs show the resources, requests, andreservations of the selected customer. The main purpose of the Cloud CustomerAdministration application is to maintain customers individually. Theadministrator can also perform configuration tasks for individual customers andaccess other applications that serve this purpose.

Tasks that are available within the Cloud Customer Administration applicationinclude:v Viewing customer-specific information (users, teams, submitted requests,

projects, saved images, reserved resources, and quotas)v Creating and removing customer templates and customersv Assigning resources to customers and returning resourcesv 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 iscreated and modified in the administrative user interface. Then it becomesavailable in the self-service interface as part of the Create Customerrequest. A template customer is not operational, which means that no usercan belong to a customer of type CT.

Cloud Customer (type=CC)This customer type can be created in the self-service user interface andthen configured or modified in the administrative user interface. Ifcustomer templates are configured, you can use them to create newcustomers of type CC. A cloud customer is operational. Users assigned to itcan request and use resources. One user can be assigned to one customeronly, and that user can never be migrated between customers. When a useris assigned to a customer, that user can access and request resources thatare assigned to that customer.

Service Provider (type=SP)A predefined global customer that is delivered with Tivoli ServiceAutomation Manager 7.2.2, with a default name PMRDPCUST. If no othercustomers are defined, all users belong to this default customer. Newcustomers of type SP cannot be created.


The application is useful if the customer reports a problem with the cloud. Theadministrative user can view and find the resources related to that customer. Forexample, if the customer reports that a service request on a project failed, theadministrator can easily navigate to the list of all service requests and projectsrelated to this customer. From this application, the administrator can navigate tothe service request application to get further details about the specific servicerequest.

For specific information about the features of each tab that is available in thisapplication, click the ? Help button within the application.

Service Topology applicationThe Service Topology application is the main application for viewing and editingservice topology templates and instances. If you need to modify the servicedefinition delivered with Tivoli Service Automation Manager to exactly match yourrequirements, you can change the service topology using this application.

The Service Topology application operates mainly on the topology and topologynode data model objects. You use it to view and edit the following:v Name and description of a topologyv Nodes of a topologyv Basic relationships between nodes (parent-child relationships)v Monitoring agent assignments for nodesv Resource allocation records for nodes

Service Update Package applicationYou use this application to manage existing Service Update Packages and deploythem on one or more Service Definitions or Service Deployment Instances.

Service Topology Node applicationsYou use these applications to work with topology node objects. These applicationsprovide more sophisticated and detailed ways for browsing and editing topologynode objects than available with the Service Topology application.

The applications in this category include:v Service Topology Nodev Service Topology Node Operationv Node Attribute Uniqueness Violationsv Co-Location Editorv Topology Customization

In addition to the node viewing capabilities provided by the Service Topologyapplication, it is possible to change relationships between nodes. For one topologynode, you can display all related nodes (direct parent or child, or otherwise relatednodes) in a list. A child node can be selected and set as the main object for theapplication in order to inspect the child node. In this way, you can walk throughand inspect complete hierarchies of topology nodes. This application also allowsyou to define custom relationships (in contrast to standard parent-childrelationships) between nodes. Use this when relationships between nodes have tobe defined that cannot be modeled using standard parent-child relationships.


IT Topology Work Orders applicationThe IT Topology Work Orders application displays the status of an IT topologywork order. This application can be accessed either in the Work Orders tab of theService Deployment Instances application or when the error handling workflowcreates an assignment due to an error during processing.

An IT topology work order is used as a frame of reference during managementplan processing. It contains the state of the work order and references to the inputand output definitions for work order operation. When the management plan isbeing executed, there is one work order that contains the state of the overallmanagement 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 workorder, the operation work order, is created for the operation and its state. Workflowsthat run within the context of an operation focus on the corresponding operationwork order.

Many Tivoli Service Automation Manager operations use a common mainworkflow for tasks. This workflow is called the error handling workflow. Thisworkflow calls the operation-specific implementation workflow. If the workflowreturns an error by ending via the negative-action connection line, the errorhandling workflow provides an assignment to the operator entitled 'A WorkflowFailed'. The operation work order is opened in the IT Topology Work Ordersapplication. The problem is described in the Messages tab of the application. Theoperator can then route the workflow assignment and take one of the followingactions: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 bythe operator or if it can be omitted. Tivoli Service Automation Managercontinues processing by starting the next operation.

v Continue by re-executing the failed workflow. This option may be useful iferrors occur due to temporary problems (such as a temporary network outage).Tivoli Service Automation Manager restarts the same operation with the currentinput 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 longerpractical.

Note: Tivoli Service Automation Manager does not perform a cleanup in thiscase.Canceling means that all remaining job plans and tasks are still executed, buteach job task is considered completed when it is encountered, meaning that thecorresponding workflow is skipped. If an initial management plan is canceled bythe operator, the service deployment instance state is set to 'Canceled'. The userhas 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 Serverworkflow. It also includes changes made to the managed environment or TivoliProvisioning Manager.

You can also use the IT Topology Work Orders application to suspend and resumework orders and send notifications to users about issues related to the currentmanagement plan.


Auxiliary applicationsSeveral auxiliary applications support special-purpose editing or process controlfunctions:v Service Automation Managerv Management Plan Input Parametersv Management Plan Target Selectionv Service Topology Customization Editor

WebSphere Cluster ServiceThe WebSphere Cluster Service allows you to provision the IBM WebSphereApplication Server Network Deployment V6.1 product and manage its life cycle.

This section is relevant only if you have purchased and installed the Tivoli ServiceAutomation 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 Managerinstallation or at a later time.

The WebSphere Cluster Service provisions a WebSphere cluster consisting of thefollowing elements:v WebSphere Cellv WebSphere Network Deployment (ND) Managerv WebSphere Network Deployment managed nodev WebSphere Application Server instancev WebSphere Clusterv HTTP Server node

This service comprises the following components:v WebSphere Cluster Service definition, comprising best-practice WebSphere

topology templates and management plansv Updated automation package (.tcdriver file), which enables Tivoli Provisioning

Manager to provision WebSphere server instances together with Tivoli ServiceAutomation Manager. Also included are sample XML files to configure TivoliProvisioning Manager to use the WebSphere Cluster service

v Scripts that perform changes in the WebSphere Application Server when they areexecuted from Tivoli Service Automation Manager using the Script Adapter

The management plans include internal plans for creating a WebSphere cell oradding a managed node to an existing cell. Plans for basic management tasks inthe 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 ServiceAutomation Manager concepts and applications, utilizing the existing ServiceDefinitions and Service Topologies applications and processes such as Approval.The following WebSphere components are part of each service deploymentinstance. 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 alsocalled a cluster member.

v Provisioning and management of an IBM HTTP server instance are alsosupported.

WebSphere topology

In the following sections, the types of topology nodes used in the WebSpherecluster service are listed. Each of these node types is defined by a Service RequestManager classification that declares the attributes. Operations for topology nodesare summarized for each type of node as applicable.

WebSphere CellA WebSphere ND Deployment Manager node that manages the cell and allof its components, one or more WebSphere ND managed nodes hostingapplication server instances, and a number of IBM HTTP Server nodesrepresenting the Web tier of the environment. Furthermore, a cell candefine multiple WebSphere clusters that group similar application serverinstances.

Deployment ManagerA special type of WebSphere node for controlling a WebSphere cell and allof its components. WebSphere components are configured within a cell isdone using the Deployment Manager node. The following operations aresupported:v Installing WebSphere ND on a server and creating a Deployment

Manager profile (and thus a Deployment Manager node). This implicitlydefines a WebSphere cell that is managed by the new DeploymentManager

v Defining a new WebSphere cluster within a cell. The cluster is initiallycreated without members

v Creating a new cluster member (application server instance) for anexisting cluster on an existing WebSphere managed node

v Start the deployment manager. The deployment manager has to bestarted for most other operations to succeed. This is done during initialprovisioning.

v Stopping the deployment managerv Starting a complete cluster, that is all members within a clusterv Stopping a complete cluster, that is all members within a clusterv Starting a managed node and all cluster members that are managed by

this nodev 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 needsmaintenance

v Starting the application server instancev Stopping the application server instancev Generating the plug-in configuration for the web servers configured for

a cell and propagate it to the web server. The web server must thenroute web traffic based on the new configuration, for example handlingload for newly deployed applications or routing to newly created clustermembers


v If you use Tivoli Monitoring in conjunction with Tivoli ServiceAutomation Manager, install a Tivoli Monitoring agent on the server thisinstance runs on

v If you use Tivoli Monitoring in conjunction with Tivoli ServiceAutomation Manager, uninstall a Tivoli Monitoring agent from theserver this instance runs on

v Enabling administrative security on this managed node. You can set auser name and password for the administrative console of thedeployment manager, for example

v Incorporating a managed node in the cell that is managed by thisDeployment Manager. In this way, the Deployment Manager canintroduce changes to the given node

v Removing the given managed node from this cellv Copying the HTTP Server configuration script that was created by the

HTTP Server installation to the Deployment Manager, so that it can beinvoked 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 ismanaged/controlled by the cell Deployment Manager and does not haveits own management interface (such as an administration console).Managed nodes host application server instances for deploying J2EEapplications. 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 withTivoli Service Automation Manager.

v Uninstalling a Tivoli Monitoring agent from the server this instance runson. This is only applicable if you use Tivoli Monitoring in conjunctionwith Tivoli Service Automation Manager.

WebSphere Application Server instanceA WebSphere Application Server instance is an implementation of theWebSphere Application Server. It is a container for hosting J2EEapplications and corresponds to one instance of a Java Virtual Machine onthe respective node. Application server instances can be hosted onmanaged or stand-alone WebSphere nodes; they cannot be hosted byDeployment Manager nodes, that is, they cannot be defined withinDeployment Manager profiles.

WebSphere ClusterA WebSphere cluster is a logical grouping defined within a WebSphere cellfor managing similar application server instances, that is, those of equalconfiguration. The typical reasons for clustering are load balancing andhigh availability.

IBM HTTP Server nodeAn IBM HTTP Server is the web server product of the WebSphere family.In a clustered environment, instances of HTTP Server form the web orfront-end tier of a J2EE application-hosting landscape and distribute HTTPtraffic among members of a cluster of WebSphere Application Servers.Supported operations are as follows:v Installing and configuring IBM HTTP Server on a server.


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 TivoliService 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 withTivoli Service Automation Manager.

DBMS serverA database management server. This is used in the optional TivoliMonitoring integration, such that events reported by this database servercan be correlated to a service deployment instance.

Database instanceA database instance managed by a DBMS server. This is used in theoptional Tivoli Monitoring integration, such that events detected by thisdatabase can be correlated to a service deployment instance.

Management plans

The following processes can be performed on a deployed instance of theWebSphere Cluster Service:

Add ServerAdds a WebSphere managed node to a cell and creates a member that isadded to an existing cluster

Remove ServerRemoves an existing member from a cluster and deprovisions itsassociated WebSphere managed node from a cell

Start WebSphere Deployment ManagerStarts the Deployment Manager for this service deployment instance

Stop WebSphere Deployment ManagerStops the Deployment Manager for this service deployment instance

Start WebSphere NodeStarts a complete WebSphere managed node, including all applicationserver instances hosted by the node

Stop WebSphere NodeStops a complete WebSphere managed node, including all applicationserver instances hosted by the node

Start WebSphere Cluster MemberStarts a specific application server instance on a managed node

Stop WebSphere Cluster MemberStops a specific application server instance on a managed node

Start WebSphere ClusterStarts a complete WebSphere cluster, that is, all of the members of thecluster

Stop WebSphere ClusterStops a complete WebSphere cluster, that is, all of the members of thecluster


Service topology node attributesThe service topology is the set of individual hardware and software componentsthat constitute the defined or instantiated service. Each element of the topology isreferred to as a node. The following section describes a topology using theWebSphere Cluster Service as a sample framework.

In the WebSphere Cluster Service, the main logical component of the environmentto be managed is a WebSphere Cell. Consequently, the top node in the hierarchy isa WebSphere Cell node. A WebSphere Cell contains an IBM HTTP Server, aDeployment Manager, and one or more managed nodes. A cell can also definemultiple 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 resourceallocation 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. Thatgroup is then assigned to the physical resource. Nodes not assigned to a group areclassified as stand-alone nodes. Nodes in a co-location group can later beselectively deleted from the group, or an entire group can be dissolved, in eachcase the affected nodes are returned to stand-alone status.

The WebSphere Cell contains one or more managed nodes. Each node has threespecial attributes:v Minimum cardinalityv Maximum cardinalityv Maximum cardinality unlimited

These attributes are used to define how often a node can occur in an instance ofthe topology.

Other attributes indicate whether the node participates in performance monitoringand whether it needs a hardware resource to run, for example.

Since selected nodes in a service topology can occur multiple times, a mechanismis required to ensure that the attributes that describe these nodes are unique acrossthe topology or even across all services.

Node attributes must allow for the definition of a uniqueness scope in order toprevent conflicts with attributes of other nodes in a topology. For example, allnodes within a topology should have a unique name. WebSphere ApplicationServer nodes that are deployed on the same host must also have unique,non-conflicting port number assignments. A simple resolution of conflicts isprovided through placeholders in character-string-type attributes that are replacedwith numbers that are automatically incremented at instantiation time. Thesenumbers 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, automatedresolution of conflicts is done based on numeric variable substitution according touser-defined rules (see below). With numeric attributes, the entire attribute issubject to substitution. With string attributes, placeholders for such numericvariables are placed in the string. It is possible to insert multiple placeholders intoone string, and each of these is replaced. If placeholders in one string are identical,


the same value is inserted for each occurrence in a string. The complete identifierof such a placeholder variable comprises the fully qualified name (including nodeclassification ID) of the attribute (see also Attribute Name Handling below) and thename of the placeholder variable. For numeric attributes, the fully-qualified nameof the attribute itself identifies the replacement variable.

Uniqueness scope: A uniqueness_scope parameter can be set for all specificationattributes that defines which type of uniqueness is to be enforced for thatparameter of a node within a topology. The following uniqueness scopes can beset:

Table 2. Uniqueness scopes for topology node attributes

Uniqueness scope Meaning

None Uniqueness not enforced (default scope)

Global Uniqueness is enforced across all topology nodes known to thesystem

Service Definition Uniqueness is enforced across all topologies of service deploymentinstances derived from one service definition

Topology Uniqueness is enforced within the topology. The value of thatattribute of a node must be unique within the entire topology,meaning that no other node in the same topology can have the samevalue for that attribute

Host Uniqueness is enforced on a per-host basis. Nodes deployed on thesame host must not define the value for an attribute

Group Uniqueness is enforced in a user-defined group; once defined, agroup can be referenced by attributes of all nodes, and uniquenessis enforced in the scope of the selected group

Attribute name handling: The user can define how the name of an attribute istreated with respect to uniqueness, that is how the uniqueness is enforced betweenthe attributes of one node and the attributes of other nodes. The following types ofattributes handling can be set:

Table 3. Uniqueness specifications for attribute names

Attribute nameuniqueness Meaning

Exact Only values of identically named attributes are considered foruniqueness handling (default)

Wildcard An expression containing wildcard characters (%) can be specified todefine a range of attributes that are considered for uniquenesshandling. Not only can the Wildcard specification can be used notonly for selecting a wider range of actual attribute names, it can alsobe used to select attributes from multiple classifications. Forexample, if attributes PORT_ONE and PORT_TWO are to becorrelated during uniqueness handling (to prevent port assignmentconflicts), the wildcard expression PORT_% could be used


Table 3. Uniqueness specifications for attribute names (continued)

Attribute nameuniqueness Meaning

Alias group Arbitrarily named attributes can be assigned to user-defined aliasgroups. All attributes that belong to the same alias group are thenconsidered for uniqueness handling. This allows for correlatingattributes, for example, of different node classifications, that wouldbe correlatable by name. For example, an attribute of a WebSpherenode named SOAP_PORT (a TCP/IP port) and an attributeBOOTSTRAP_ADDRESS (also a TCP/IP port) of an ApplicationServer instance could be assigned to an alias groupNETWORK_PORTS with host scope in order to keep allocatedTCP/IP ports unique on a host.

Uniqueness resolution rules: Within the user-defined uniqueness scope of anattribute, variables are substituted according to a set of rules that define howsubstitution values are calculated. Resolution is always performed on the basis of anumeric calculation. There is currently one rule defined:

Table 4. Uniqueness resolution rule

Uniqueness resolution rule Meaning

Increment Increments the substitution variable by auser-defined step value (default 1) startingat a certain base value (default 1). A uniquevalue is calculated by obtaining the highestvalue for an existing attribute andincrementing it to assign the value to thenew attribute. The value of a numericattribute defines the base value andoverrides any such value specified in therule.

Numeric placeholders in character strings are treated the same way as numericattributes except that the base value is always the one defined in the rule.Identically named placeholders within one string are assigned the same value. Fortext-only attributes without placeholders, the uniqueness requirements can bedefined, but no automatic uniqueness resolution is performed.

Tivoli Service Automation Manager detects violations of the uniqueness rules forattributes and displays the affected parts of the topology in the Node AttributeUniqueness Violations panel.

Performance monitoring support for the WebSphere ClusterserviceYou can also use the Tivoli Service Automation Manager to install performancemonitoring software (agents) on the servers it provisions. This software detectssituations that cause degraded performance. Tivoli Service Automation Managerreacts to such situations by presenting the user with options to analyze and resolvethe problems based on procedures that have been accepted as recommendedpractices.

Note: This section applies only to the Tivoli Service Automation ManagerWebSphere Cluster service. It does not apply to the Tivoli Monitoring basedresource usage collection functions offered with the Self-Service Virtual ServerProvisioning component.


Each Tivoli Service Automation Manager service definition can have an associatedmonitoring definition. These definitions provide the framework for implementingthe monitoring agents and controlling which types of events it will react to.

If you need to modify the service definition delivered with Tivoli ServiceAutomation Manager to suit your requirements for performance monitoring, youcan change it using the set of Monitoring Definition applications.

Performance monitoring is supported in combination with IBM Tivoli Monitoringon distributed platforms (Linux on System x, System p, and System z, and AIX).The Monitoring Definition applications refer to the monitoring environment beingused with respect to any given service definition and service deployment instance.

IBM Tivoli Monitoring must be installed separately. It is no longer offered as aninstallation option for Tivoli Service Automation Manager.

For details on setting up IBM Tivoli Monitoring, see the documentation for thisproduct (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 themonitoring agents in a deployed landscape.

When a monitoring agent detects a situation, it triggers the execution of aworkflow within Tivoli Service Automation Manager. The Situation Analysisapplication, which is part of this workflow, is called and assigned to the user withthe role corresponding to the domain that applies to the agent and situation. Forexample, if the scenario is part of the domain AIX or DB2, the applicationexecution within the workflow is assigned to the respective AIX administrator orDB2 administrator role. A customer can also add a new domain by enhancing thesituation analysis workflow, adding new roles and adding new values to thedomain. An assignment to analyze the event appears in the inbox of thecorresponding user within the Start Center panel of the Tivoli process automationengine user interface. When the user clicks on this assignment, the application toanalyze 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 situationindicated.You can then browse the entire context of the instance within which the situationoccurred, including the topology, the CIs involved, and the monitoringdefinitions. Deployment instances are only shown when the affected systembelongs to that instance and the situation was defined for one of the agent typesdeployed on the system for that instance. Each instance includes a link to theService Deployment Instances application so that you can browse all informationand details related to that instance.

v when a service deployment instance is selected, the recommended practices (alsocalled good practices) for the situation in the context of this instance.You use analysis practices to analyze a situation and management practices toresolve a situation. These practices can refer to actions in the Select Action menu




to launch another management tool (such as the TEP console) in order toanalyze or resolve a situation. Analysis practices are displayed as plain text. Amanagement practice can be either a management action described in text formand intended to be executed manually by the user, or a Tivoli ServiceAutomation Manager management plan that can be executed automatically bythe system.The list of practices is sorted by the probability that the practice will resolve theevent. The number of times the practice was chosen to resolve an event of thistype is used as the sorting criterion. That is, the practice chosen most often andconsidered the best approach by an administrator (by clicking on the FeedbackGood Practice button) is displayed as the first element in the list.

Depending on the analysis of the event, you can choose among the followingactions 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 structureServices offered by Tivoli Service Automation Manager are organized as follows:

Service definitionBasic set of rules for creating a specific IT landscape. Tivoli ServiceAutomation Manager delivers preconfigured service definitions that can beused as templates for customizing the definition to meet your specificneeds.

Service deployment instanceActual IT landscape described by the service definition.

Service topologyA set of hardware servers and software representing the IT landscape.

Monitoring definitionA framework for activating monitoring software to detect possibleperformance problems in a deployed landscape.

Management planPredefined modification of the provisioned landscape.

Job planA tool that implements management plans in terms of software.

WorkflowsPreconfigured sequence of steps that perform a specific function. Forexample, there are workflows to instantiate (deploy) a service, makemanagement changes once the instance has been deployed, and performerror handling.

Work orderA tool that provides the framework for executing management plans.

ResourcesActual hardware and software that can be used in constructing thelandscape.


Service provider supportThe new service provider feature introduced with Tivoli Service AutomationManager 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 thatare assigned to customers individually, and multi-customer objects that can beshared among customers. The underlying idea of the solution is data segregation,which is used to associate resources with one or more customers. Resources can beused more efficiently and customers are able to support multiple internalorganizations.

A customer level is introduced in the self-service user interface. Each customer isassociated with a specific group of teams and users. Users are always assigned toone customer only. They can be assigned to multiple teams, but all of these teamsmust belong to the same customer. Users can view only the information andresources 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 organizedinto tabs. The tabs support the following actions:v Viewing the list of customers, their teams and users, requests, resources,

reservations, quotas, and limitsv Creating customer templates and modifying existing customersv Assigning and returning customer resourcesv Setting quotas and limits on customer resources

In Tivoli Service Automation Manager 7.2.2, there is a clear distinction betweenobjects that are assigned to only one customer and resources that can be shared bymany or even all customers within a cloud. The Tivoli Process Automation engineservice provider functionality segregates the data for this purpose. Multi-customerresources are associated manually. Association tasks related to those resources areperformed in the Cloud Customer Administration application. Single customerresources are assigned automatically to the customer for which the requesting useris working. For example, if a person who is assigned to a specific customersubmits a request for a new team, the fulfillment flow associates the team with thecustomer automatically.

Resources that can be shared by customers are:v Cloud server poolsv Cloud network templatesv Cloud storage poolsv Master imagesv Software products

Resources that can be assigned only to individual customers are:v Teamsv Usersv Service deployment instances, also called projectsv Saved server images

The multi-customer support in Tivoli Service Automation Manager 7.2.2 introducesnew tasks related to the data segregation system. This system must ensure thatusers see only the data assigned to them.


Three new roles are introduced in the self-service user interface: cloud customeradministrator, approver, and security administrator. Some significant changes werealso made to the authorities of the existing user roles. The main reason for theoverall reorganization is the introduction of the cloud customer level.

Cloud customer administrator role is strictly connected with the cloud customerlevel. Users in this role have authorities similar to the authorities of a cloudadministrator, but they are dedicated to individual customers. They have noauthority to create or remove users and register or unregister software images.

Another role that is strictly connected with the cloud customer level is theapprover role. Approvers can check the status of projects, and see the servicerequests associated with their customers. They are also authorized to approvethose service requests. Cloud administrators and cloud customer administratorscan 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 ofmultiple security groups.

In Tivoli Service Automation Manager 7.2.2, you can add new customized securitygroups. For example, you can define a separate security group that is authorized touse VMware specific offerings. You can also reuse the existing roles and groupmanagement from LDAP. These procedures are described in details in the TivoliService Automation Manager Extended Solution Guide.

Related information

For more information about creating and removing customers in the self-serviceuser interface, see Managing customers in the Tivoli Service Automation ManagerUser's Guide.

For more information about the features of the Cloud Customer Administrationapplication, see “Cloud Customer Administration application” on page 6.

Reporting functionReports show information related to service definitions and deployments.

Tivoli Service Automation Manager report types and contentThe following types of reports are available with Tivoli Service AutomationManager. The type of information shown in each report differs depending on theservice.

Table 5. Summary of Tivoli Service Automation Manager Reports and Content

Tivoli ServiceAutomation ManagerApplication Report Type Report Name Selection Parameters Content

Service Definitions All Service Definitions AllSD<service>.rptdesign

List of all service definitionsand instances.

Service Definitions Service DefinitionSummary

SDSummary<service>.rptdesign

StatusOwnerFrom DateTo Date

Basic service definitioninformation and list of servicedefinitions and deployments.


Table 5. Summary of Tivoli Service Automation Manager Reports and Content (continued)

Tivoli ServiceAutomation ManagerApplication Report Type Report Name Selection Parameters Content

Service Definitions Service DefinitionDetails

SDDetail<service>.rptdesign

Service Name Service-dependent content withidentifying information, status,topology, monitoring andresource assignments, andservice definition history

Service DeploymentInstances

Service DeploymentSummary

SISummary<service>.rptdesign

StatusOwnerService Definition NameFrom DateTo Date

Service-dependent graphicsand lists showing CPU andmemory levels, servers byowner, servers by platformarchitecture, monitoring agentsby type, and instances


Service DeploymentDetails

SIDetail<service>.rptdesign

Service Name Service-dependent contentincluding graphics showingCPU, memory, servers byarchitecture, monitoring agents,and service history


Co-Located Nodes coLocation<service>.rptdesign

Host Name Information concerningcomponents of the serviceinstance that are located on thesame physical server


Service DeploymentHistory Summary

SISummaryHistory<service>.rptdesign

From DateTo Date

Service-dependent graphicsshowing CPU, memory, servers(over time and for alldeployments)

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 andAdministration Guide. For post-installation setup tasks required to activate theReporting function, see "Configuring the Reporting function" in the Installation andAdministration Guide.

Tivoli Usage and Accounting Manager reporting functionAs an option, Tivoli Service Automation Manager can use the Tivoli Usage andAccounting Manager metering function. Tivoli Usage and Accounting Managerhelps 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 manyother criteria.

Tivoli Service Automation Manager instantiates and manages service instances. It isable to track creation, modification, and deletion of a service instance itself, as wellas the capacity assigned to it. This information can be periodically extracted andtransformed into a so-called CSR (Common Server Resource) file, which can thenbe retrieved by Tivoli Usage and Accounting Manager to generate reports.

Tivoli Usage and Accounting Manager helps measure service usage data. In theTivoli Service Automation Manager context, this data is the amount of resources(CPUs and memory) allocated or assigned to servers provisioned by theSelf-Service Virtual Server Provisioning component over time. Servers belong to


projects and projects belong to the service. Each deployment has a user. The usercan own deployments coming from different services, request new deployments, orrequest 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 eachproject, you can distinguish between the requester of the project and theorganization being charged with the project. You can define organizationalinformation for a project by adding an (optional) project account code for the teamthat is using the project. Reports can then be generated based on the team and itsusers. It is also important that no two deployment instances are created with thesame name, because this will result in inaccurate usage and accounting data.

Before you can start using this function, you need to configure both Tivoli ServiceAutomation Manager and Tivoli Usage and Accounting Manager. For moreinformation, see Integrating Tivoli Usage and Accounting Manager in the Tivoli ServiceAutomation Manager Installation and Administration Guide.

To find out how to employ the collected data in the form of reports, see Workingwith the usage and accounting reports in the Tivoli Service Automation ManagerInstallation and Administration Guide.

Additional software installation on the provisioned serversWith Tivoli Service Automation Manager, you can install one or more softwaremodules when you create a virtual machine, or you can install them on virtualmachines that were already provisioned.

You can use one of the product components, Tivoli Provisioning Manager, to definesoftware 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 virtualmachines.

Before you install any software modules on a provisioned machine, create softwareproduct definitions using the administrative user interface. See Tivoli ServiceAutomation Manager Installation and Administration Guide for more information oncreating software product definitions.

In the self-service interface, you can install software modules by submitting threetypes of requests:

Create Project with server typeYou can select software to be installed on the servers that are to beprovisioned in a project. All servers have the same software installed.

Add server typeYou can select software to be installed on a new server that is added to aproject.

Install Additional Software on a ServerYou can install software modules on a server that is already provisioned.

You can select multiple software items and install them in a specified order. Youcan also specify additional configuration parameters for the software items to beinstalled.


Related tasks:“Installing software on server” on page 41If the administrator added any software module templates and configured them inthe administrative interface, you can install additional software items on anexisting virtual server.

Managing POWER LPAR provisioning with VMControlThis topic provides reference information about managing POWER® LPAR virtualservers using IBM Systems Director VMControl.

VMControl quick reference

VMControl is a plug-in of IBM Systems Director. Tivoli Service AutomationManager supports IBM Systems Director VMControl 2.3.0.2 Enterprise Edition.

VMControl is an alternative way to provide POWER LPAR virtualization andimage management functions.

For more information about VMControl, see the section on VMControl 2.3.0.2 inthe 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 POWERLPAR computers using VMControl, the environment needs to be configured. Formore information on the procedure, see Configuring Cloud Pools in the Tivoli ServiceAutomation Manager Installation and Administration Guide.

Managing provisioning

All self-service requests, apart from modifying disk size and saving/restoringvirtual servers, are available for POWER LPAR provisioning via VMControl.

Recovering form errors

For troubleshooting when using VMControl, see Recovering from errors when usingIBM Systems Director VMControl in the Tivoli Service Automation Manager Installationand Administration Guide.

Image managementSoftware and server images can be maintained in the Tivoli Provisioning ManagerImage Library for selection at provisioning time. New Server image templates canbe created and imported to the library. Once the images are in the library, theymust be registered so that they can be used to provision new virtual servers. Asnapshot-like image of an entire provisioned server can also be saved and restoredin the current project, so that the server can be initialized at the state representedby the image.

The Tivoli Service Automation Manager User's Guide describes the image-related tasksthat are available to administrators and users working with the self-service userinterface.


http://publib.boulder.ibm.com/infocenter/director/v6r2x/topic/com.ibm.director.vim.helps.doc/fsd0_vim_c_vmc_230.html



For other administrative tasks, see "Managing server images" in the Installation andAdministration Guide.

Workload Deployer overviewIBM Workload Deployer is an optional, separately paid appliance that can beintegrated 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 thatfocus on addressing WebSphere workloads. It enables creating, deploying,monitoring, and managing service construction and delivery within Tivoli ServiceAutomation Manager. The appliance is based on special virtual images, such as theWebSphere Application Sever Hypervisor Edition, and allows creating patterns thatrepresent the target application environment. These patterns include theinfrastructure nodes of the application and the necessary configuration for theenvironment. By using Workload Deployer, you can deploy them into your privatecloud. In this way, the appliance provides management and monitoring capabilitiesthat 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 arecomplementary in nature.Workload Deployer allows users to create, deploy, andmanage customized environments based on the WebSphere application and locatedin a private cloud. Tivoli Service Automation Manager provides the tools toperform the standardization and the automation in the cloud environment, therebyenabling rapid provisioning for a wide breadth of workloads. The integrationprovides:v the service delivery and management capability of Tivoli Service Automation

Managerv the Workload Deployer patterns and capabilitiesv a unified interface from which users can deploy and manage their cloud-based

environments

Tivoli Service Automation Manager enables creating and deploying applicationenvironments based on any kind of software. Workload Deployer offers capabilitiesfor application environments based on IBM software, thereby simplifyinginstallation, configuration, integration, and orchestration scripting procedures forthose workloads.

The integration of the two applications can be made according to differentscenarios. Depending on what services you want to deliver via the cloud, the mostcommon 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 primarymanagement device for your private cloud. The capabilities of both the productsremain the same. Tivoli Service Automation Manager enables the provisioning andmanagement of a wide array of cloud-based services including operating systems,application platforms, and end-user applications. The integration of WorkloadDeployer enhances the time to value for delivering WebSphere environmentsregardless of what other services you deliver through Tivoli Service Automation


Manager. Moreover, integrating the products allows you to unify management ofyour cloud services using the self-service user interface. Workload Deployerdelivers its patterns, namely rapid provisioning, consistent configurations, andinherent product knowledge for WebSphere workloads without the need to switchbetween multiple service management portals.


Chapter 2. Using the Self-Service Virtual Server Managementofferings

Tivoli Service Automation Manager provides robust functionality for selecting andprovisioning standard software packages on virtual servers of various type. Asimple, easy-to-use set of applications enable data center personnel to achieverapid time-to-value for virtual server provisioning from these platforms. Theconfiguration that is provided for these applications supports fully automatedprovisioning with a standardized set of deployment activities.

Submitting requests in the self-service user interfaceLog on to the self-service user interface, where you can access the offerings andrequest provisioning.

Before you beginv 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 nativeXMLHTTP support check box.

v Enable JavaScript, CSS, SSL, and cookies.v Set your browser resolution to a minimum of 1024x768.

Procedure1. 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: PMRDPCAUSRPassword: maxadmin

3. Select Request a new service > Virtual Server Management to get access to allofferings, or select Frequent requests. This option lists 4 most frequentofferings, 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 onthe security group that you are assigned to, a different set of requests will beavailable in the menu:


Table 6. Access to requests depending on the security group

CloudAdministrator

CloudManager

TeamAdministrator Team User

CloudCustomer

Administrator ApproverSecurity

Administrator

Create project v - v - v - -

Create projectfrom savedimage

v - v - v - -

Add server v - v - v - -

Add serverfrom savedimage

v - v - v - -

Modifyreservation

v - v - v - -

Cancel project v - v - v - -

Modify serverresources

v - v - v - -

Reset serverpassword

v - v - v - -

Start, stop, orrestart server

v - v - v - -

Installsoftware

v - v - v - -

Remove server v - v - v - -

Create serverimage

v - v - v - -

Restore serverfrom image

v - v - v - -

Remove savedimages

v - v - v - -

Register image v - - - - - -

Unregisterimage

v - - - - -

Create user v - - - v - v

Modify user v - v - v - v

Remove user v - - - v - v

Create team v - - - v - -

Modify team v - v - v - -

Remove team v - - - v - -

Createcustomer

v - - - - - -

Removecustomer

v - - - - - -

Approve andreject requests

v v - - v v -

View requests v v v v v v -

View projects v v v v v v -

View servers v v v v v v -

Related concepts:“User interfaces” on page 3Tivoli Service Automation Manager provides two options for user interaction: aself-service user interface and an administrative user interface.

Approvals and notificationsThe product is shipped with a set of built-in approval workflows and notificationsthat are invoked after self-service provisioning requests are created.

Approvals

By default, all self-service requests are automatically approved. Administrators canenable the approval process for server-related requests. Three groups of users arethen allowed to approve the requests:v Cloud administrators


v Cloud customer administratorsv Cloud approversv Cloud managers

If a request for a customer is sent for approval, all approvers associated with thecustomer are notified, and any of them can approve the request.

The following requests cannot be sent for approval:v Install Softwarev Manage Users requestsv Manage Teams requestsv Manage Image Library requests

Tip: To enable the approval process, see Enabling or disabling automatic approval ofrequests in the Tivoli Service Automation Manager Installation and Administration Guide.

Notifications

Email notifications are sent out whenever one of the project-related request issubmitted:v Create/Cancel Projectv Save/Restore Imagev Start/Stop/Modify/Add/Remove Server

The same notification is sent to three groups of users:v Requesterv 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 theneeds of your organization.

Email notificationsYou can stay informed about your requests without being logged on to TivoliService Automation Manger through automatic email notifications. The systemadministrator 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 Requesterv Project ownerv Project team (CC list)

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

By default, the requester and all customer team members receive a notificationregarding submitted requests. Cloud administrators must be registered as a teammembers to receive notifications.

Note: Ensure that the team users have email addresses that can be relayed by yourmail server, else email cannot be sent.

ExampleDear John SmithYour Service Request 00048 "Project Request" has been approved and QUEUED forprocessing.Do not reply to this message as it was automatically generated.

Regards,Your Service Automation Team

Approving requestsWhen the approval process is enabled, a group of users with approval privilegescan approve or decline the requests that the users submit. They can also reassignthe requests for other users approval.


The following users are able to approve and decline requests:v Cloud administratorsv Cloud customer administratorsv Cloud approversv Cloud managers

If a request for a customer is sent for approval, all approvers associated with thecustomer are notified, and any of them can approve the request.

Procedure1. 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 anotheruser. This functionality must be enabled as described in Enabling or disablingdelegation of approval requests in the Tivoli Service Automation ManagerInstallation and Administration Guide. Otherwise the option is not available.


Creating a project and adding virtual serversUse 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 beingscheduled by the same user, the resources are not updated for projects that are inthe queued or new status. This may allow a user to create projects for which thereare not enough resources.

Procedure1. In the Home panel, click Request a New Service > Virtual Server

Management > Create Project with server type. The Create Project wizardopens.

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 seton your local machine when the request is submitted. Ensure that your timeis 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 ImageLibrary” 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 therequested resources as required.

Restriction: The following values are restricted for certain platforms:

Table 7. Restrictions for the resources values

VMware POWER LPAR

Memory a multiple of 4 MB a multiple of 128 MB

Swap Memory a multiple of 1 GB - decimal values are not allowed

Virtual CPU 1, 2 or 4 -

Disk - For POWER LPAR serversprovisioned via IBM SystemsDirector VMControl™ diskspace value is static andcannot be modified.

Click Next.


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 interfaceb. 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 onthe 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 whichthe items are to be installed. If the software item requirements can befulfilled, its name will appear in the Selected Software box. Otherwise anerror message will be displayed.

Note: Software installation feature is independent of hypervisor at thebackend. If a server fulfills the requirements of the selected softwaremodule then that software module is listed as installable on it.

b. To specify any additional parameters for each software item, select an itemand click Configure Software. Fill in the fields as required.Default values for the parameters are displayed in the input fields and areeditable if they can be modified. Input for encrypted parameters isdisplayed as passwords. Hidden parameters are not displayed on the userinterface.

If no items are available in the Available Software box, verify that they havebeen 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 networkinterface.

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 isbeing decommissioned

Select this checkbox to configure the project to automatically save anew image of each virtual server in this project at the time theproject is canceled.

Keep saved images after the project has been decommissionedSelect this checkbox to configure the project so that the existingserver images are not removed along with the serves at the time theproject is canceled.

b. Select Monitoring Agent to be Installed, if required. This agent performsscans to identify server resource utilization (memory, CPU and disk space).The usage values can then be viewed in the Manage Servers panel. Thisfield is only available if configured.

c. Click Next.


9. In the Summary tab, review the settings for your project. Click Finish to submitthe request.

Results

A service request is created to complete the virtual server project that you havedefined or to reserve the hardware for deployment on the indicated start date. Anynotifications that are defined for this operation are sent out, and any approvalsthat are part of the work order are requested.

Immediate fulfillment: After any required approvals are received, host names forthe virtual servers are automatically assigned from a pool of host names that ismaintained by your administrator. You receive an e-mail notification when the newproject is completed.

Scheduled fulfillment: You will receive an indication of whether the request hasbeen approved or rejected. If the request is approved, it becomes a reservation forthe indicated hardware capacity and network parameters on the start date. If therequest is not approved, the reason may be that the requested hardware capacityor network parameters are not available for the indicated time frame.

Note: The virtual machine disk size value may differ from the one requested. ForTivoli Service Automation Manager, 1GB = 230 bytes, 1MB = 210 bytes. On a Linuxoperating system these values will differ, as 1GB = 109 bytes.

Creating a project from a saved server imageYou can create a new project and use the saved server images to provision a serverin that project. This functionality is only available for VMware, POWER LPAR andKVM.

About this task

The parameters of the server to be provisioned are defined by the image. Theserver 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, theadministrator needs to enable agent installation in some of the request panels first.For more information see Enabling the monitoring agent installation on restored imagesin the Tivoli Service Automation Manager Installation and Administration Guide.


Management > Create Project from Saved Image.2. Enter a Project Name.3. Select the team that should have access to the project.4. Optional: Type a description for the project.5. Set the start date and time, and duration.

Important: The time of provisioning is based on the time and timezone set onyour local machine when the request is submitted. Ensure that your time is setcorrectly.

6. Select resource group used to reserve resources.


7. Select the image to be deployed. The list that is displayed shows all availableimages for the servers that are not currently provisioned.

8. For VMware, POWER LPAR and KVM projects, select the following options ifrequired:


Select this checkbox to configure the project to automatically save anew image of each virtual server in this project at the time the projectis canceled.

Keep saved images after the project has been decommissionedSelect this checkbox to configure the project so that the existing serverimages are not removed along with the serves at the time the project iscanceled.

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 Serverfrom Saved Image request.

Canceling a projectYou 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 withinthat project are deprovisioned. The host names that were automatically assigned tothese servers are freed up for use by other virtual servers that are created in thedata 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:


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:


Select this checkbox to configure the project to automatically save anew image of each virtual server in this project at the time the projectis canceled.

Keep saved images after the project has been decommissionedSelect this checkbox to configure the project so that the existing serverimages are not removed along with the serves at the time the project iscanceled.



Results

A service request is created to cancel the project. Any notifications that are definedfor this operation are sent out, and any approvals that are part of the work orderare requested. After any required approvals are received, the project is canceled,and you receive an e-mail notification.

Creating projects with a Workload Deployer patternLearn how to create and save a cloud project using a Workload Deployer pattern.This task can be performed after integrating Tivoli Service Automation Managerwith IBM Workload Deployer.

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


Results

A service request is created to complete the virtual server project that you havedefined or to reserve the hardware for project on the indicated start date. Anynotifications that are defined for this operation are sent out, and any approvalsthat are part of the work order are requested.

Immediate fulfillment: After any required approvals are received, host names forthe virtual servers are automatically assigned from a pool of host names that ismaintained by your administrator. You receive an e-mail notification when the newdeployment is completed.

Scheduled fulfillment: You will receive an indication of whether the request hasbeen approved or rejected. If it has been approved, the request becomes areservation for the indicated hardware capacity and network parameters on thestart date. If the request is not approved, the reason may be that the requestedhardware capacity or network parameters are not available for the indicated timeframe.

Subsequently, Workload Deployer determines what machines in the cloud are thehosts for each part in the pattern. At the end of the successful deployment, thenewly created virtual system is listed in the Manage Projects window of Tivoli


Service Automation Manager.

Canceling Workload Deployer pattern projectsYou can cancel a project saved with Workload Deployer pattern, also if it isscheduled for a future date. When you cancel a project, all of the servers that havebeen provisioned within that project are deprovisioned. The host names that wereautomatically assigned to these servers are freed up for use by other virtual serversthat are created in the data center. Any image saved for a server that participatedin the project is deleted.

Procedure1. 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 definedfor this operation are sent out, and any approvals that are part of the work orderare requested. After any required approvals are received, the project is canceled,and you receive an e-mail notification.

Modifying projectUse these tasks to learn how to add new servers to a project or modify thereservation date.

Adding virtual servers to an existing projectWhen, for example, the scope of a project increases substantially, you can add oneor more virtual servers to an existing project.

Select an active project and add one or more new servers, specifying the number ofCPUs, the memory, and the software to be deployed for each. The new serversreceive automatically assigned host names.

Before you begin


About this task

To add servers to a project:


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:


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 ImageLibrary” 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 therequested resources as required.


Table 8. Restrictions for the resources values

VMware POWER LPAR

Memory a multiple of 4 MB a multiple of 128 MB

Swap Memory a multiple of 1 GB - decimal values are not allowed

Virtual CPU 1, 2 or 4 -

Disk - For POWER LPAR serversprovisioned via IBM SystemsDirector VMControl diskspace value is static andcannot 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 interfaceb. 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 onthe 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 whichthe items are to be installed. If the software item requirements can befulfilled, its name will appear in the Selected Software box. Otherwise anerror message will be displayed.


b. To specify any additional parameters for each software item, select an itemand click Configure Software. Fill in the fields as required.


Default values for the parameters are displayed in the input fields and areeditable if they can be modified. Input for encrypted parameters isdisplayed as passwords. Hidden parameters are not displayed on the userinterface.

If no items are available in the Available Software box, verify that they havebeen 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 networkinterface.

9. In the Summary tab, review the settings for your project. Click Finish to submitthe request.

Results

A service request is created to add the new servers to the specified project. Anynotifications that are defined for this operation are sent out, and any approvalsthat are part of the work order are requested.

Immediate fulfillment: After any required approvals are received, host names forthe virtual servers are automatically assigned from a pool of host names that ismaintained by your administrator. You receive an email notification when the newproject is completed.

Scheduled fulfillment: You will receive an indication of whether the request hasbeen approved or rejected. If approved, the request becomes a reservation for theindicated hardware capacity on the start date. If the request is not approved, thereason may be that the requested hardware capacity is not available for theindicated time frame.


Adding a server from a saved imageYou can create a server using one of the saved images and add this server to aproject. 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. Theserver 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, theadministrator needs to enable agent installation in some of the request panels first.For more information see Enabling the monitoring agent installation on restored imagesin the Tivoli Service Automation Manager Installation and Administration Guide.


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.


4. Select an image to be deployed. The list that is displayed shows all availableimages for the servers that are not currently provisioned.


Modifying reservation datesYou can modify the start date of the scheduled project with a future start date, andthe end date of all projects.

Before you begin



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 onyour local machine when the request is submitted. Ensure that your time is setcorrectly.


Remember: When the reservation time is changed for a project and whenquotas and limits exist for the respective customer and pool, then these limitsare checked when you try to modify the reservation time. It is only possible tomodify the reservation time within the previously specified limits.

Results

A service request is created to modify the dates as specified. Any notifications thatare defined for this operation are sent out, and any approvals that are part of thework order are requested. After any required approvals are received, the dates ofthe reservation are changed (if possible) and you receive an e-mail notification.

Removing a virtual serverYou 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 provisioningon a future date. When you delete a server, the host name that was automaticallyassigned to that server is freed up for use by another virtual server that is createdin the data center.

Important:

v You cannot remove the last server in the project. Instead, the whole project canbe canceled.

v You cannot remove the first server in a project with future reservation date.Instead, the whole project can be canceled.

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


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 removedSelect 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 removedSelect this check box to keep any existing images of the server to beremoved.

Otherwise, when you remove a virtual server, any images saved for this serverwill also be deleted.


Results

A new service request is created to delete the specified server and, optionally, itsimages. Any notifications that are defined for this operation are sent out, and anyapprovals that are part of the work order are requested. After any requiredapprovals are received, the server is deleted, and you receive an email notification.

Modifying serverUse these tasks to learn how to modify the state of a server, its resources, or resetpassword for a server.

Modifying server resourcesYou can modify the number of CPUs, the amount of memory, or increase the diskspace to be allocated to any supported virtual server that is currently provisioned.Requests for server capacity modification might be submitted when a projectrequires more capacity than was originally assigned. Similarly, the requests mightarise 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, theseservers are restarted, and any running services are interrupted. POWER LPARservers are not restarted.

To modify the capacity of an existing 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.


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 therequested resources are available.


Memory

v VMware: must be a multiple of 4 MBv POWER LPAR: must be a multiple of 128 MBv 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 onPOWER 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.4SUSE 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 higherv 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 VirtualizationManager (IVM) that is configured to use storage from MPIO mapped SANdisks. No additional disk can be mapped to extend the current one, and noalready mapped MPIO SAN disk can be unmapped from the LPAR.

v On Power®, the disk extension is added to the VIO server by this servicerequest. The extension on System p LPAR is visible only after manuallytriggering 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 thepassword was modified manually, see “Windows disk size modification afterchanging password” on page 40.


Results

A service request is created to change the virtual server capacity as specified. Anynotifications that are defined for this operation are sent out, and any approvalsthat are part of the work order are requested. If you are using the built-in, defaultapproval workflow, requests that you submit on your own behalf are automaticallyapproved.


After any required approvals are received, the capacity is changed, and you receivean email notification.


Windows disk size modification after changing passwordThere are some restrictions on modifying disk size on Windows after the passwordwas changed manually.

To successfully process a disk modification request for Windows, the passwordmust be set by Tivoli Service Automation Manager. If the password was changedmanually, you can use a Reset Server Password request to change the passwordagain so that it is synchronized with Tivoli Service Automation Manager.

Any disk modification request that is submitted after the Windows password waschanged manually is failed. Even though the request fails, the disk size is in factmodified in VMware. Both VMware and Tivoli Service Automation Manager showthe new disk size. The disk space resulting from the resize operation is available asunallocated disk space in Windows, but the file system is not enlarged.

Important: Do not use the unallocated space to create a second partition withinWindows, 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 passwordYou can reset a server password and have it e-mailed to members of teams thathave access to the project.

Before you begin

Ensure that you have the required privileges to submit this request.

Procedure1. Select Home > Request a New Service > Virtual Server Management >

Modify Server > Reset server password. The Reset Server Password windowdisplays.

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.


Results

The password is reset and the members of teams that have access to the project getan e-mail notification with new password.

Starting a serverYou can start a server in a project.


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 serverwas created, the list of servers will include all servers regardless of their state.

3. Select a server to start and click OK.

Stopping a serverYou can stop a server in a project.


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 serverwas created, the list of servers will include all servers regardless of their state.

3. Select a server to stop and click OK.

Restarting a serverYou can restart a server in a project.


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 serverIf the administrator added any software module templates and configured them inthe administrative interface, you can install additional software items on anexisting virtual server.

Before you begin

Ensure that the software product definition for the item that you want to installhas been configured by the Tivoli Service Automation Manager administrator. Formore information, see Tivoli Service Automation Manager Installation andAdministration Guide.



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 theprovisioned servers. Use the vertical arrows to set the order in which theitems are to be installed. If the software item requirements can be fulfilled,its name will appear in the Selected Software box. Otherwise an errormessage will be displayed.


b. To specify any additional parameters for each software item, select an itemand click Configure Software. Fill in the fields as required. Default valuesfor the parameters are displayed in the input fields and are editable if theycan 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 theyhave 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 21With Tivoli Service Automation Manager, you can install one or more softwaremodules when you create a virtual machine, or you can install them on virtualmachines that were already provisioned.

Backing up and restoring server imagesUse 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 IBMSystems Director VMControl.

v All images saved by a user in the self-service user interface are owned by thisuser. Only this user can ever restore the saved image. Each user can view onlythe images that he or she created, and does not have access to the images ofother users. If an image is automatically saved at the end date of a project, theuser 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, theadministrator needs to enable agent installation in some of the request panelsfirst. For more information see Enabling the monitoring agent installation on restoredimages in the Tivoli Service Automation Manager Installation and AdministrationGuide.


Creating server imageYou can save multiple images of a provisioned server in its current state. You canthen use the images in a subsequent request to restore a server, create a projectwith 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 IBMSystems Director VMControl.

v All images saved by a user in the self-service user interface are owned by thisuser. Only this user can ever restore the saved image. Each user can view onlythe images that he or she created, and does not have access to the images ofother users. If an image is automatically saved at the end date of a project, theuser 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, theadministrator needs to enable agent installation in some of the request panelsfirst. For more information see Enabling the monitoring agent installation on restoredimages in the Tivoli Service Automation Manager Installation and AdministrationGuide.

Important: When creating a server image, make sure that you have enough freespace on the data store.Tivoli Service Automation Manager does not check whetherthere is enough space available. If there is not enough space available, an inboxassignment is created in the administrative user interface and the situation must beresolved manually, as described in Configuring cloud pools in the Installation andAdministration Guide.


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. Anynotifications that are defined for this operation are sent out, and any approvalsthat are part of the work order are requested. After the required approvals arereceived, you will receive an email notification when the image is saved.


Restoring a server from imageYou can restore a virtual server back to its previous state using an image that yousaved before.

About this taskv 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.


Management > Backup and Restore Server Image > Restore Server FromImage.

2. From the Project Name list, select a project for which you want to restore aserver.

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


Results

A service request is created to restore the server from the selected image. Anynotifications that are defined for this operation are sent out, and any approvalsthat are part of the work order are requested. After the required approvals areprocessed, you will receive an email notification when the image has been restored.

Removing saved imagesYou can remove previously saved server images from the inventory.


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 otherusers are not displayed.


Results

A service request is created to remove the image from the inventory. Anynotifications that are defined for this operation are sent out, and any approvalsthat are part of the work order are requested. After the required approvals arereceived, you will receive an e-mail notification when the image has been deleted.


Managing Image LibraryTivoli Provisioning Manager Image Library is the source for software images to beused in provisioning the virtual servers. Once the image templates discovery hasbeen performed in Tivoli Provisioning Manager by the system administrator, theimages need to be registered in the Image Library, so that they can be used forprovisioning. Use these tasks to learn how to register or unregister server images.

For more information about discovering images, see the corresponding sections inthe Tivoli Service Automation Manager Installation and Administration Guide.

Registering VMware imagesUse this task to learn how to register a VMware image in the Image Library.

Before you beginv 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:

Procedure1. 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 Managementv Customerv Backup-Restorev Storage

b. Select Use this interface for host name resolution if the network interfaceis to be used for host name resolution.

c. Optional: In the Network Usage section, select a set of usage valuesapplicable to a particular interface.

d. To add more network interfaces, click Add Network Interface, and specifythe settings.

6. In the Resources section, specify the Minimum and Recommended values forvirtual CPUs, physical CPUs, memory, and disk space.

7. Specify the details of the operating system of the image according to Table 9on page 46.

8. Depending on the operating system, specify the Administrator Password orRoot Password that match the password set on the image from which thevirtual machines will be created.

9. If you are registering a Windows image, enter the Product Key.



Table 9. OS Family and Version values

FamilyInstalled (operating systemof the software stack) Version

Linux

Red Hat Enterprise Linux 5.3 or 5.4

CentOS 5.3 or 5.4

SUSE Linux EnterpriseServer

10.2 or 11

Windows

Windows XP Not required

Windows 2003 2003

Windows Server 2008 2008

Windows Server 2008 R2 2008

Windows 7 7

Registering POWER LPAR imagesUse this task to learn how to register a POWER LPAR image in the Image Library.




About this task

To register an image:

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








7. Enter the Root Password for the image.8. Click OK to submit the request.

Registering Xen imagesUse this task to learn how to register a Xen image in the Image Library.




About this task

To register a Xen image:

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







7. Enter the File Name of the Image.8. Click OK to submit the request.


Registering KVM imagesUse this task to learn how to register a KVM image in the Image Library.




About this task

To register a KVM image:


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








Registering z/VM imageUse this task to learn how to register a z/VM image in the Image Library.





Management > Manage Image Library > Register z/VM 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








Registering POWER LPAR images via IBM Systems DirectorVMControl

Use this task to learn how to register a POWER LPAR image in the Image Libraryusing VMControl.




About this task

To register an image:

Procedure1. Select Home > Request a new service > Virtual Server Management >

Manage Image Library > Register VM Image via IBM Systems DirectorVMControl.

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.


Unregistering an image in the Image LibraryYou can unregister an image in the Tivoli Provisioning Manager Image Library, sothat 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 haverequired privileges.


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 imageThis task describes the procedure necessary to deploy a project based onVMControl.

About this task

Starting with Tivoli Service Automation Manager 7.2.2, the network requirementsare placed on the deployable images. For the VMControl configuration, you mustannotate the network requirements in the discovered VMControl image.This step isaccomplished by using the Register VM Image via IBM Systems DirectorVMControl 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 isavailable: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 networkdefinition in the VMControl deployable image and so forth.

As part of the register image workflow, the above assumptions are enforcedthrough checks and are realized during the Crate Project and Add Serverofferings.


Registering a new image for a migrated resource poolFollow these steps to register a new image for a resource pool that was migratedfrom a previous version.

About this task

Register an image for an upgraded resource pool according to the followingpattern:

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

3. Determine which subnet pool is marked as HostnameResolveNIC

Modifications to the registered imagesDuring the network migration process, the existing images are modified accordingto the new network model

The new network model introduces two major changes according to which theimages 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 registeredimages during migration:v The number of network interfacesv Which of the network interfaces is the management interfacev Which of the network interfaces is used for resolving the host namev 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 subnetpool in the associated resource pool. The x stands for 1 for the first subnet pool inthe 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 forthe first network interface in the resource pool. For example, if the resource poolis named "RES1", the network type is "management", and it is the first networkinterface, the usage value is "RES1_Management_1".


Generated network segmentsA network segment is generated for each enabled resource pool and each subnetpool.

The network segments that are generated contain the following information fromthe 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 numberstarting with 0 for the first network segment (as the subnet pools also start with0). For example, if the resource pool is named "RES1", and the segmentcorresponds 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 networkinterface 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 theusage value is "RES1_Management_1". This method assures that each networksegment exactly matches to the corresponding network interface definition onthe 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 theimage metadata. Resource pools for this hypervisor have an additional propertyfor 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. Duringthe migration process, only the subnet pools that have a matching network nameare migrated. Remember about the following points when migrating a VMControlnetwork 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 wayas for all other resource pools as listed above.

Managing customersYou can create and remove customers by using the self-service user interface.


Creating customersUse the self-service user interface to create customers. Additional setup steps maybe required in the administrative user interface.

Before you begin

Before you can create a customer, the administrator must configure at least onenetwork template.

About this task

In the self-service user interface for Tivoli Service Automation Manager version7.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 aredefined and specified when the user is created. The customer assignment defineswhich 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 acustomer, you can select a template. If no templates are available, after creating thecustomer in the self-service interface, the administrator must specify additionalsettings in the administrative interface. For more information about these tasks, seethe Administering customers and their resources chapter in the Tivoli ServiceAutomation Manager Installation and Administration Guide.


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 userinterface to make the customer operational.

4. Select Network Configuration Template to define network configuration forthe customer.

5. Select Customer Language Code. The value determines the default languagefor 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 usedthe customer template, the template configuration is copied to this customer object.If no template was used, the administrator must assign the resources to thecustomer 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 becreated so that the customer's projects, teams, and users can be administered.


Removing customersYou 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 thiscustomer become inactive. If any projects are still in progress, they will bedecommissioned as scheduled, or cloud administrators can cancel them manually.The name of the removed customer can never be reused.


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 thiscustomer are deactivated as well. The users can no longer log on to the self-serviceuser interface. By default, the state of the projects and resources does not changeautomatically. Projects are decommissioned according to their schedules. Cloudadministrator can also cancel the projects and delete any saved images manually.

Managing usersUse these tasks to learn how to manage users and groups of users.

Creating usersCloud and team administrators can create users and add them to the existingteams.

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 customerlevels. The users on cloud customer level can create users on the same levelonly.

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:


v Cloud administrator can define for which customer the user is created byselecting this customer in the Home panel. The user can access only theresources assigned to the selected customer, global resources that are available toall customers. There is one predefined global customer: PMRDPCUST. Each newuser is assigned to this customer if no other customers are specified during usercreation.

v The security level defines which cloud resources the user can access. There aretwo default security levels:

Cloud levelUsers on cloud level can access the information and resources that areavailable in the cloud, regardless of customer limits. They are alwaysassigned to a default global customer called PMRDPCUST.

Customer levelUsers on this level are always assigned to one customer only, and theycan 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 groupassignment determines which requests the user can access. Security groups aredescribed 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 exactlyone policy level.

v To be able to use a project, the user must be a member of the team that hasaccess to this project. A user can be a member of more than one team, but allteams must belong to the same customer.

Procedure1. 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 to30 characters and must be unique. It cannot be in use or deleted.

b. Specify and confirm the password. The password must be at least sixcharacters in length.

c. Select Make the account active to enable the user to log in after the newuser registration is complete and click Next.

4. In the Security Groups tab:a. Select Security Policy.

Cloud Level PolicyIf the user is subject to this policy, they can access all cloudresources and information regardless of which customer theinformation is assigned to.

Cloud Customer Level PolicyIf the user is subject to this policy, they can only access theresources assigned to the customer they belong to.

b. Assign the user to security groups. If you want the user to be able to assignother users to the selected group, select the Grant option check box. ClickNext.

5. In the Personal Details tab, fill in the fields as required. Click Next.6. In the Regional Settings tab, define locale. Click Next.


http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.tsam_7.2.2.doc/c_tsam_userroles.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.tsam_7.2.2.doc/c_tsam_userroles.html

When you set the locale for the user in the self-service user interface, the samelocale will be used in the administrative interface. Also, the language of theuser 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 editedby 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 informationYou 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 customerlevels. The users on cloud customer level can create users on the same levelonly.

v The policy level must be registered in the system properties:– pmrdp.security.cloud.level.group

– pmrdp.security.customer.level.group


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.


Results

The user record will get updated accordingly. The affected user will receive e-mailnotification about the changes.

User modification conditionsLearn about the conditions that must be met in order to modify a user.

Team user, team administrator and cloud manager can modify only their owninformation.

Cloud administrator, cloud customer administrator and security administrator canmodify all users of the selected customer.

Only users that meet the following conditions are displayed in the Modify Userrequest 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 userYou 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 havethe required privileges.

About this task

To remove a user:

Procedure1. 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 IDcan never be reused. Additionally, the deleted user's email address can be reusedto create a new account ID.


Creating new teamsWhen 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 canaccess 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.


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 to add them to the team,

or to remove them.

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 accessthem by default.


Modifying team informationYou 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 administratorcan only modify the teams that he administers. Make sure that you have therequired privileges. Team name cannot be modified.

About this task

To modify team information:


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 accessthem by default.



Removing a teamYou can use the Remove Team request to delete teams. Teams that own activeprojects cannot be deleted. To delete them, you need to cancel all the projects thatthe team can access beforehand.

Before you begin

This task can only be performed by cloud administrators. Make sure that you havethe required privileges.

Important: When you remove a team, its name can never be reused.

About this task

To remove a team:


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 theteam has been deleted. The accounts of the users of the deleted team remain active.

Viewing requestsYou can view the full list of requests and their statuses using the My Requestssection on the Home panel.

The status bar shows the statuses of the last 20 requests by default. To see the datafor 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 afew minutes.

Five last modified requests with recent activity and their statuses are listed in theMy Requests section. When you click on the request name, the details for thisrequest 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 Approvalor Pending, depending on whether auto-approve is enabled.

v Waiting on Approval - Request is waiting for an approver to approve it. Nextstatus 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 isQueued.


v Queued - Task is queued for execution. The request stays in this state until therequested 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 areResolved 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.

Procedure1. 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 onthe toolbar. The request details will be displayed in a separate window.

Viewing the details of a submitted requestGeneral details about a request and both work and communication logs areavailable to you for viewing.

Tip: Five last modified requests with recent activity can be viewed in the MyRequests section on the Home panel. Click on the request name to display thedetails.

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

3. Select a request and click on the toolbar. The View Service Requestwindow is displayed.

4. Use the General tab to view details about the request, the Work Log tab toview any error messages, or the Communication Log tab to view anynotifications that were sent. The General tab displays the attribute list of therequest with their respective values, except for security related values, likepasswords.


Viewing and managing requests for approvalYou can view the requests awaiting approval and approve, reject, or reassign them,if you have the required privileges.


Tip: Five approval requests with recent activity can be viewed in the MyApprovals section on the Home panel. Click the approval request name to displayits details.

About this task

The approval and delegation features are not configured by default, and need to beenabled in the administrative user interface.

Procedure1. 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 morethan 50 characters in length).


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 theManage Approvals window.

Viewing projectsYou can view the full list of projects and their statuses using the My Projectssection on the Home panel.

The status bar shows the statuses of the last 20 projects by default. To see thedetails 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 theMy Projects section. When you click on the project name, the details for this projectwill be displayed in a separate window.

Projects can be assigned one of the following statuses:v Approvedv Canceledv Decommissionedv Decommissioningv Decommissioning Failed


v Designv Draftv In Maintenancev Not Setv Operationalv Scheduledv In Transition

About this task

To view the full list of projects and their statuses:

Procedure1. 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 on the toolbar. The Project Details panel isdisplayed.

Results

You can now view details about the project.

Viewing and managing serversYou can view the list of all servers and manage them.

Procedure1. 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 amonitoring agent was not installed when the server was created.

2. Use the taskbar buttons to manage the selected server. Move the cursor overthe button to view hover help or click ? on the title bar to view panel help.

Viewing Workload Deployer project detailsGeneral details about a Workload Deployer project and its servers is available toyou for viewing.

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


Tip: Five projects with recent activity and two upcoming projects can be viewed inthe My Projects pod on the Home panel. Click on the project name to display thedetails.



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 definitionAbout this task

Before you begin to use the WebSphere Cluster Service, be sure you havecompleted the steps listed under Chapter 4. Configuring Service Automation Managerin the Installation and Configuration Guide.

The WebSphere Cluster Service provides a ready-to-use service definition. You cancustomize the service definition as needed. The delivered definition is notmodifiable, so that updates can be shipped to the existing service withoutinterrupting existing deployments. To be able to start customizing, you canduplicate the provided definition.

Procedure1. Log on to the administrative user interface.2. Click Go To > Service Automation > Service Definitions.3. Search for the WebSphere Cluster service definition and open it.4. In the Select Action menu, click Duplicate Service Definition.5. Enter a number and a name.6. Click Save.

Results

The copy now contains its own instances of the management plans and topologytemplates, also comprising all the topology nodes. Refer to the applicable sectionsfor a definition of these entities.

Instantiating the WebSphere Cluster ServiceAbout this task

This section describes a scenario in which a WebSphere cluster is provisioned byinstantiating an existing service definition for this service. To create such a servicedeployment instance the so called initial management plan of the service isexecuted internally. The initial management plan has three phases: preparation,approval, and execution.

The following steps describe the procedure for performing these phases of theinitial management plan.

Note: This procedure assumes that no steps have been skipped within the servicedefinition. If they have, the relevant inbox entry in each case is omitted.


Procedure1. Log on to the administrative user interface.2. Click Go To > Service Automation > Service Definitions.3. Press Enter to see all available service definitions.4. 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 appropriateuser (depending on the role) will receive workflow assignments. Log on withthe appropriate user ID.

11. In the Start Center, you will see the next workflow assignment. Open thisassignment to display the Service Topology Customization panel.

12. Depending on the values in the underlying service definition, you may needto add some missing data. When you want to add or change the initialcardinality (initial number of occurrences of this node), click CustomizeSelected 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 Linuxon System z allocation. Both heterogeneous and homogeneous environmentsare 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 onthe 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.

17. In the Start Center you will see the next workflow assignment. Open thisassignment to do the resource allocation.

18. On this panel (Resource Allocation for Service Deployment Instance) you mustspecify the servers on which you want to provision the cluster elements. Eachserver must be referenced by a configuration item (CI).

19. Select each row in sequence and determine the CI for which the provisioningis to apply. To determine the CI, from the detail menu click Filter usingRequirements adjacent to the CI field. This shows you only the serverspossible for your environment, such as only the servers applicable to aninstallation on System p.

20. To finish your work on this screen, continue the workflow by clicking theRoute Workflow icon.


21. In the Start Center, you will see the next workflow assignment. Open thisassignment to view the contents of the job plan that is generated from theinitial 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 servicedeployment instance. The Approve panel appears. On this panel, you cancheck all assignments done in the preparation phase. If you agree you canclick the Approve icon in the toolbar.

25. Continue the workflow by clicking on the Route Workflow icon. If the requestwas approved, this will lead you into the execution phase, in which the actualdeployment of the resources takes place.

26. In the execution phase, no user interaction is necessary unless an errorsituation occurs. In case of an error, you will see further assignments in yourinbox in the Start Center. You then have the opportunity to try the currentworkflow again, ignore the failed action, or cancel the provisioning process.

27. The execution phase has completed when the status of the correspondingservice deployment instance is set to “Operational”. Check the status with GoTo > Service Automation > Service Deployment Instances.

Executing management plans for the WebSphere Cluster serviceAbout this task

This section describes how to execute the existing management plans deliveredwith the service definition provided for the WebSphere Cluster service. Threemanagement 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, andexecution phases.

Adding serverLearn how to add a server to an existing WebSphere cluster.

About this task

The following procedure guides you through the preparation, approval, andexecution phases of the Add Server management plan of the WebSphere Clusterservice.


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

Chapter 3. Using the WebSphere Cluster service 67

5. To execute the ADDSERVER management plan click the green arrow to theright. You will be notified that a workorder has been started.During the preparation phase, user interaction is needed. The appropriate userwill get workflow assignments.

6. Log on to the administrative user interface with the appropriate user role. Inthe 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 noderemains 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 menuadjacent to the CI field.

12. Click the Route Workflow icon. In the Start Center, the workflow assignmentfor the job plan is displayed.

13. Open the assignment to view the contents of the job plan generated from theAdd Server management plan. The details of the generated job plan aredisplayed in a new panel.

14. Click Route Workflow to continue the workflow. In the Start Center, you cansee the workflow assignment for approving this change to the servicedeployment 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-serveroperation. 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, theexecution phase is started. In the execution phase no user interaction isnecessary unless an error situation occurs. If it does, you will see furtherassignments in your inbox in the Start Center. You then have the option toretry the current workflow, ignore the failed action, or cancel the provisioningprocess: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 serverLearn how to remove a server from an existing WebSphere cluster.

About this task

The following list describes how to step through the preparation, approval, andexecution phases of the Remove Server management plan of the WebSphereCluster service.




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 thepreparation phase, user interaction is required. The appropriate user will getworkflow assignments.

6. Log on to the administrative user interface with the appropriate user role. Inthe Start Center, the job plan workflow assignment for Management PlanTarget 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 youcan 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 deploymentinstance. The approval phase is started.On the Approve panel, check the current server information and all theprevious actions done in the preparation phase. For example, the instancemanager 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 executionphase is started. In the execution phase, no user interaction is necessary unlessan error situation occurs. In case of an error, you will see further assignmentsin your inbox in the Start Center. You then have the choice to retry the currentworkflow, 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


Stopping WebSphere Deployment ManagerLearn how to stop a WebSphere Deployment Manager.

About this task

The following procedure describes the steps for the preparation, approval, andexecution phases of the Stop WebSphere Deployment Manager management planof the WebSphere Cluster service.


Chapter 3. Using the WebSphere Cluster service 69


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 userwill get workflow assignments.

6. Log on to the administrative user interface with the appropriate user role. Inthe Start Center, the job plan workflow assignment is present.

7. Open the assignment to view the job plan. A panel with the details of thegenerated 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 deploymentinstance 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. Ifyou 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 wasapproved, execution phase starts. In the execution phase, no user interaction isnecessary unless an error situation occurs.In the case of an error, further assignments are present in your inbox in theStart 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


Deleting script logs from WebSphere Cluster serversScripts are executed on the servers provisioned by the WebSphere Cluster serviceto 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. Thesedirectories are not deleted automatically so that script execution logs can bereviewed as needed. It is advisable to set up a cron task that deletes directoriesolder than a specified time, such as one week.


Appendix. Accessibility features

Accessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features of Tivoli Service Automation Manager are described in thistopic.

Accessibility features

User documentation provided in HTML and PDF format. Descriptive text isprovided for all documentation images.

The IT Service Management Information Center, and its related publications, areaccessibility-enabled.

Related accessibility information

You can view the publications for Tivoli Service Automation Manager in AdobePortable Document Format (PDF) using the Adobe Reader. PDF versions of thedocumentation are available in the information center.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information aboutthe commitment that IBM has to accessibility.


http://www.ibm.com/able


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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.


Glossary

This glossary includes terms and definitions for Tivoli Service Automation Manager.

The following cross-references are used in thisglossary:v See refers you from a term to a preferred

synonym, or from an acronym or abbreviationto the defined full form.

v See also refers you to a related or contrastingterm.

To view glossaries for other IBM products, go towww.ibm.com/software/globalization/terminology.

Aadministrative system

The hardware component of Tivoli ServiceAutomation Manager from whichsoftware is installed on the managementserver and other administrative actionsare taken.

agent A process that performs an action onbehalf of a user or other program withoutuser intervention or on a regularschedule, and reports the results back tothe user or program.

applicationOne or more computer programs orsoftware components that provide afunction in direct support of a specificbusiness process or processes.

Ccardinality

The number of elements in a set.

configuration itemAny component of an informationtechnology infrastructure that is under thecontrol of configuration management.

credentialInformation acquired duringauthentication that describes a user, groupassociations, or other security-relatedidentity attributes, and that is used toperform services such as authorization,auditing, or delegation. For example, a

user ID and password are credentials thatallow access to network and systemresources.

Eescalation

A course of action that runs when a taskis not completed satisfactorily within aspecific period of time.

Hhypervisor

A program or a portion of LicensedInternal Code that allows multipleinstances of operating systems to runsimultaneously on the same hardware.

Jjob plan

A detailed description of work to beperformed for a work order. A job plantypically includes required tasks and listsof estimated labor, materials, services, andtools needed to complete the work.

job taskAn individual step in a job plan. Each jobtask triggers a specific workflowappropriate to that task.

Mmanaged environment

An environment where services, such astransaction demarcation, security, andconnections to Enterprise InformationSystems (EISs), are managed on behalf ofthe running application. Examples ofmanaged environments are the Web andEnterprise JavaBeans (EJB) containers.

managed nodeA node that is federated to a deploymentmanager and contains a node agent andcan contain managed servers.


http://www-306.ibm.com/software/globalization/terminology/

http://www-306.ibm.com/software/globalization/terminology/

management planA set of tasks that modify a servicedeployment instance.

management serverThe hardware component of Tivoli ServiceAutomation Manager on which theproduct and its prerequisite middlewarereside.

Maximo business objectA standardized data entity withinMaximo.

MBO See Maximo business object.

middlewareSoftware that acts as an intermediatelayer between applications or betweenclient and server. It is used most often tosupport complex, distributed applicationsin heterogeneous environments.

Pplatform

The combination of an operating systemand hardware that makes up theoperating environment in which aprogram runs.

portletA reusable component that is part of aWeb application that provides specificinformation or services to be presented inthe context of a portal.

Rreservation

The preallocation of configuration itemsfor future deployments.

Sserver image

A file that contains the content and stateof a virtual server, which can be savedand restored.

service definitionA set of data that provides the frameworkfor deploying an IT landscape.

service deployment instanceAn actual IT landscape derived fromdeploying a service definition.

service topologyIn the context of a service definition, theset of physical IT components (such ashardware and software) that are availablefor inclusion in services based on thatdefinition. On instantiation, the servicetopology is the actual set of thesecomponents in operation on behalf of theservice deployment instance.

service topology nodeIn the context of a service definition, oneelement of the service topology to whichresources can be allocated based on thatdefinition. On instantiation, the servicetopology is the actual set of thesecomponents in operation on behalf of theservice deployment instance.

software definitionThe deployment configuration thatdescribes how to install one or moreinstallable software dependencies. Itincludes a list of installable files, softwareprerequisites, and advanced attributes.

subnetSee subnetwork.

subnetworkA network that is divided into smallerindependent subgroups, which still areinterconnected.

TTEMS See Tivoli Enterprise Monitoring Server.

TEPS See Tivoli Enterprise Portal Server.

Tivoli Enterprise Monitoring ServerThe monitoring server is the collectionand control point for the performance andavailability data and alerts received frommonitoring agents. This server alsomanages the connection status of theagents and is responsible for tracking theonline or offline status of the agents.

Tivoli Enterprise Portal ServerA Tivoli Monitoring server that providesthe core presentation layer for retrieval,manipulation, analysis, andpre-formatting of data. The portal serverreceives data from the hub monitoringserver in response to user actions at theportal client, and sends the data back tothe portal client for presentation.


Vvirtual server

A server that shares its resources withother servers to support applications.

VMwareA commercially available, proprietaryvirtualization environment for System xand similar platforms.

WWO See work order.

workflow

1. The sequence of activities performed inaccordance with the business processes ofan enterprise.

2. The structured sequence of activitiesand tasks that are used to implement aspecific change, release, or other process,including automatic routing and trackingof records for approval and other tasks.

work orderA record that contains information aboutwork that must be performed for an asset,location, configuration item (CI), and soon.

XXen A open-source virtualization environment

for System x and similar platforms.

Glossary 77


Trademarks and Service Marks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries. A current list of IBM trademarks is available onthe Web at http://www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are trademarks orregistered trademarks of Adobe Systems, Incorporated, in the United States and/orother countries.

Intel, the Intel logo, Intel Inside, the Intel Inside logo, Intel Centrino, the IntelCentrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium aretrademarks or registered trademarks of Intel Corporation or its subsidiaries in theUnited States and other countries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.


http://www.ibm.com/legal/copytrade.shtml


Index

Aaccessibility features 71administrative user interface

applications 3applications

Co-Location Editor 7IT Topology Work Orders 8Management Plan Input

Parameters 9Management Plan Target Selection 9Monitoring Definition 4Monitoring Definition Instances 4Monitoring Definition Instantiation 4Node Attribute Uniqueness

Violations 7overview 3Resource Allocation for Service

Deployment Instance 4Resource Allocation Record 4Service Automation Manager 9Service Definitions 4Service Deployment Instances 4Service Topology 7Service Topology Customization

Editor 9Service Topology Node 7Service Topology Node Operation 7Situation Analysis 5Topology Customization 7

approvals 27

Ccomponents

overview 2configuration

registering a VMControl image 50customer

creating 53removing 54

customer supportcontact x

Eeducation

see Tivoli technical training ixemail notification

overview 27

Ffixes, obtaining ix, x

Gglossary 75

IIBM Software Support

submitting a problem xiiIBM Support Assistant iximage

unregistering 50Image Library

managing 45registering KVM images 48registering other images 48registering POWER LPAR 46registering VMware images 45, 49registering Xen images 47unregistering image 50

imagesregistering 48

images, KVMregistering 48

images, POWER LPARregistering 46

images, VMwareregistering 45, 49

images, Xenregistering 47

Installation Launchpadoverview 2

Internet, search for problemresolution ix

Internet, searching for problemresolution ix

Kknowledge bases, searching ix

Nnotifications 27

Oofferings

accessing in self-service userinterface 25

Pperformance monitoring 15problem determination

describing problem for IBM SoftwareSupport xi

determining business impact for IBMSoftware Support xi

submitting a problem to IBMSoftware xii

projectadding servers 34canceling 32creating 29

project (continued)creating with Workload Deployer

pattern 33modifying 34modifying reservation dates 37Workload Deployer pattern,

canceling 34project, Workload Deployer

viewing 62projects

viewing 62

Rreporting

overview 19reports

types 19requests 60

accessing in self-service userinterface 25

approving 28, 61rejecting 61viewing all 60viewing status 60

Sself-service interface

accessing 25logging in 25

Self-Service Virtual ServerManagement 25

overview 2Tivoli Provisioning Manager

integration 3Self-Service Virtual Server Provisioning

adding virtual servers to existingproject 34

approvals and notifications 27canceling project 32canceling Workload Deployer

project 34deleting server image 44modifying reservation dates 37modifying server capacity 38new project 29removing virtual server 37restoring server from image 44saving server image 43

server image managementoverview 22

service structure 17services

Self-Service Virtual ServerManagement 2

WebSphere Cluster Service 9Software Support

contact x


Software Support (continued)describing problem for IBM Software

Support xidetermining business impact for IBM

Software Support xisupport information viii

Tteam

changing membership 58creating 58modifying information 58removing 59

Tivoli Service Automation Managercomponents 2

Tivoli technical training ixtopology node attributes 13training, Tivoli technical ix

Uusage and accounting function

overview 20user

changing team membership 56create 54managing 54modifying information 56removing 57

user interface 3

Vviewing details 60virtual server

adding 34modifying 38removing 37resetting password 40restarting 41restoring from saved image 44starting 41stopping 41

virtual server imagebacking up 42creating 43deleting 44removing 44restoring 42saving 43

virtual serversmanaging 62viewing 62

WWebsphere Cluster service

deleting logs 70management plans 67

WebSphere Cluster serviceadding a server 67customizing 65instantiating 65management plans 67

WebSphere Cluster service (continued)removing a server 68stopping Deployment Manager 69using 65

Workload Deployeroverview 23

Workload Deployer patterncanceling a project 34creating a project 33


��

Product Number: 5724-W78

Printed in USA

SC34-2656-00

Documents

TSAM User Guide