There are a few Tivoli products focusing on cloud computing.  This training mainly deals with IBM Service Delivery Manager(ISDM). Since we have FIVE different books, by default I am using the first week’s books, for instance p12-37means the first week’s book on p12-27; while book2 p2-29means the second week’s book on p2-29; thus student2 means the second week’s student book.

IBM has a few cloud products. From easy to difficult it is TSAM, ISDM and Cloud Burst。The installation and configuration of TSAM is the hardest. It may require more than 18 hours (some cases even 3 days);Cloud Burst is the easiest one.  All the configurations are done before hand. What the customer need is just to configure something like IP address etc. Cloud Burst ships with hardwares (The configurations are fixed in hardware) ISDM requires at least 9Power7 CPU,20Gmemory and 170G hard disk). The software structure is as follows:

ISDM is composed of TSAM(Tivoli Service Automation Manager),ITM (IBM Tivoli Monitor),TUAM (Tivoli Usage and Accounting Manager), and NFS. Those FOUR pars are installed on different Linux virtual boxes (at least our lab environment looks like this). Every part has its own, versionof,DB2 (you can’t mix those DB2s or else unexpected exceptions will be raised). People can use Putty (since it is Linux)to access the Linux virtual box; people can use vSphereClient (VMware vSphere is a cloud operating system, which manages large pools of virtualized computing infrastructure, including software and hardware) to operate (restart/halt) on those boxes. Below is a screen dump of vSphere Client:

The relationships between those FOUR parts can be found in Below is a brief:

The following text describes the relationships as numbered in the above image:

  1. Tivoli Service Automation Manager and IBM Tivoli Usage and Accounting Manager have a two-way relationship:

1.1   TUAM_image imports data from TivSAM_image that is needed for usage and accounting management

1.2   TivSAM_image connects to TUAM_image for report generation

  1. The IBM Tivoli Monitoring agent on the TivSAM_image sends data to the IBM Tivoli Monitoring server.
  2. System x: TSAM and the NFS_image/NFS-HA_image have a two-way relationship:

3.1   Tivoli Service Automation Manager collects binaries from the file repository present on the NFS_image/NFS-HA_image at provisioning time.

3.2   NFS_image/NFS-HA_image redirects the Tivoli Service Automation Manager user interface and the Tivoli Provisioning Manager user interface

  1. The IBM Tivoli Monitoring agent running on the TUAM_image sends data to the IBM Tivoli Monitoring server.
  2. NFS_image(and the NFS-HA_image on System x) redirect the IBM Tivoli Usage and Accounting Manager user interface.
  3. The IBM Tivoli Monitoring agent on the NFS_image sends data to the IBM Tivoli Monitoring server.
  4. System x: The IBM Tivoli Monitoring agent on the NFS-HA_image sends data to the IBM Tivoli Monitoring server.
  5. System x: In a high availability configuration, Tivoli System Automation needs to constantly exchange data between the NFS_image and the NFS-HA_image to be ready to manage failover situations.
  6. System x: The IBM Tivoli Monitoring agent on the TivSAM-HA_image sends data to the IBM Tivoli Monitoring server.
  7. System x: In a high availability configuration, Tivoli System Automation needs to constantly exchange data between the TIVSAM_image and the TivSAM-HA_image to be ready to manage failover situations.

ITM(p3-36,p3-38)—–SaaS and PaaS are TWO core concepts of Cloud Computing. In realy environment, Cloud provider always provides resources (Platform, Software) to its customers. How to monitor the usage of those resources, like memories,CPU, hard disk, is critical for  the Cloud providers.  To fulfil this goal, IBM developed ITM. Those usage data mentioned above can be accessed through IBM Tivoli Enterprise Portal Webstart Client(http://ITM_image:1920)(p3-46) A report chart can be found in Student Book p11-8

TUAM—– Cloud providers can get the resource usage data from ITM. The next step is to pass these data to customers’ financial department in some specific format (CSR file) so that finally the providers can be paid. TUAM is used to generate/configure  financial reports(p12-36,p12-43,p12-45). To fully use the audit functionality in TUAM, we must change some settings in “Database Configuration” from TUAM. Think about IBM’s SCE (Smart Cloud Enterprise) service. In SCE to provision a virtual box will cost eirteic, the user, 60 aud/month. I guarantee SCM is using ISDM. A tutorial of managing reports in ISDM can be found in

Here is a screen dump of the generated report:

NFS—–provides mails support in ISDM.  For instance if you provision a virtual server by ”Request  A New Service”  then ”Create A New Virtual Server” When this service request is resolved, the result will be sent to your pre-defined email address. If the request is to create a new virtual box, then the root user name and password will be sent to the email address as well(a screen dump can be found instudent book p7-21). Another powerful functionality of NFS is to provide URL re-direction service. It provides a Single point of access to SimpleSRM GUI, TPAE GUI, TUAM GUI. Users can access TSAM through this SimpleSRM GUI(https://cloudx_tsam:9443/SimpleSRM) (student book p7-20)(structure can be found in book2 p1-4).The presentation of service management functionality implemented in Tivoli Service Automation Manager towards end-users is done in the form of Service Offerings that can be requested by users via an Offering Catalog interface – both of these concepts are implemented using the Tivoli Service Request Manager (SRM) component. In addition, such service offerings can also be accessed through external user interfaces (such as the Web 2.0 UI shipped with Tivoli Service Automation Manager 7.2) that access TPAe functionality, for example, using REST-based interfaces.

TSAM—–TSAM is the core software of the IBM Cloud strategy,and it is the most complex one in ISDM. Just like TSRM (Tivoli Service Request Manager), TPM(Tivoli Provisioning Manager), TSAM is based on TPAE(Tivoli Provisioning Automate Engine) i.e. workflow. There are a bunch of predefined workflows shipped with TSAM (But the disadvantage is the names of most of those workflows are meaningless. For instance PMZHBSIWWA is one of the workflows.) Biz based workflow is from TPAE (p3-23 TSAM glossary) Workflows can be modified through a specific GUI from TSAM. For instance, in book2 p3-17 there is a workflow called PMZHBSIWWA. When you hit any node of this workflow, you can find the description at the bottom of the screen (book2 p2-29 Workflow Designer Basics)

Every page, for instance the “Create Project with VMWare Servers” page, has its own HTML and JS files. Thus by editing the HTML and JS files we can customized our own pages. If there is something wrong with the JS file, the system will raise aGeneral Form; while if there is some HTML error a pink dialogue will appear.

Any Service Request, for instance “Create New Project”, has its ownservice definition, management plan, management task ,job plan, offering, node operation(book2 p2-14) etc. Of course it is the workflow that really does the work. THREEworkflows are important.Resource_Master: One for each request;ClusterProvision: One for each virtual server been provisioned(p9-29). This workflow contains the most relevant information about the provisioning process.Resource_Master->RP.ClusterProvision->RP.CreateVirtualServer. TPM can run Cloud_Discover_VirtualCenter workflowto discover all clusters defined in the vCenter (Software to manage VMware vSphere. It provides unified management of all the hosts and virtual machines in a datacenter from a single console with an aggregate performance monitoring of clusters, hosts and virtual machines.).

Self Service Interface provides the following basic functionalities:

  1. Virtual Server Management->Create Project With VMWare Servers
  2. Backup and Restore Server Image
  3. Team/User creation
  4. Software stack(Student Book p8-4—p8-8)
  5. Create/Manage Project

After creating a new service request, the new service request will be listed in the”My Requests” page(Student Book p7-24).The status of the new request will be changed from initially “New” to “Queued” then “In Progress” and finally “ Resolved (Fail)”( The process can be found in book2 p2-8) Each status has its own colour. For instance the colour for “Resolved” is GREEN.  As stated in the previous section, when it comes to “Resolved” a notification email will be sent to the predefined mail address.

The most powerful functionality of TSAM is that it can create Virtual Image and install software into a specific Virtual Image. Users even can customize the virtual image and make it a Template. Other providers like Intalio does not have such functionalities. (Based on my knowledge Intalio is just a CRM SaaS) When creating a virtual server, people can define CPU numbers, Memories, Disk Space etc. (The usage of those resources will be monitored by ITM and finally goes to customer financial department through TUAM). Please refer to Student Book p7-21-p7-28 for how to do that.  The process of the creation virtual image can be monitored by vSphere. Please keep in mind only images that are registered in Image Library can be provisioned. (The Image Library is used as the source for software images to be used in provisioning the virtual servers. After image discovery, you need to register discovered images with the library so that they can be used for provisioning. After the registration, they become available in “Create project” or “Add server” tasks.)Please to Student Book exercise 7,8,10.ISDM supports a bunch of virtual box operation system from SUSE Linux toWindows2008. When finishing provisioning a virtual image, an email will be sent to the predefined email.  The email will tell you the virtual hostname(for instance vm1921680130),CPU,memory,hard disk space,Admin password and the URL of your provisioned machine(for instance http://vm1921680130:80)

People can backup/restore Server from Image.

Please refer toTSAM Provisioning 1 Virtual Server – YouTube.mp4on How to create a virtual image.

Cloud Poolis critical in TSAM( p7-20 or book2 p1-31). A cloud pool is the central object that TSAM uses to define cloud environments. It contains references to all DCM resources needed for the pool (e.g. hypervisor manager, host platform, file repositories, and resource pools). People can configure Cloud Pool by editing the file (which can be created by yourself or imported).  Every time a new cloud virtual environment is required to be provisioned, a new virtual resource pool must be created.

A few hypervisor Cloud Pools are supported by TSAM. Users can set up a KVM environment, for instance, so that TSAM can provision and manage virtual servers with the KVM hypervisor. More information can be found in IBM TSAM Infocenter Configuring Cloud Pools section.

DCM templates are defined in some xml configuration files. From those XML files, we can define something like sub network route, gateway etc. please refer to Data Center Model (DCM) object templates.docx

A project is a group of virtual resources of the same type that can be used by a group of users. Each project is assigned to one team, and all team members can access the virtual machines provisioned in that project and monitor the state of the project. The resources provisioned in a project can be modified – you can add and remove servers, install additional software on the servers, or modify server capacity.Project can be created through the Self Service  Interface page. A tutorial is as follows:(

Another useful GUI is TSAM GUI(https://cloudx_nfs/maximo) Please be careful although here it is called TSAM GUI, the URL requiresURL to redirect. P5-33 provides a screen dump of that GUI(It looks similar as TSRM’s however the content of the menus are quite different). It is the core feature of TSAM .  Through this, people can createservice definition,management plan, managementtask, job plan,offering etc. For more details about other ways of accessing the user interfaces and the credentials that are used for this purpose, see

Usually after creating a Service Request in SimpleSRM, we can monitor the status of the request in TSAMGUI. Meanwhile from editing service definition, we can customize the display content of the SimpleSRM page.

TSAM provides 4 roles which areCloud Manager, Cloud Administrator,Team Manager andTeam Administrator.We can create user and group from the Self Service GUI. Below is the screendump:

A new user can be added to up to FIVE teams when created from the Self-Service User Interface. However a new user can only have ONE role.

Service Definition and Service Deployment Instances are TWO critical terms in TSAM. Service Definitions are the structural model of a service, describing how the managed service looks i.e. the service topology. The structural model of a Tivoli® Service Automation Manager Service includes all the components that make up a service, and the relationships between these components. The model has physical components and logical components. Physical components are usually software or hardware components. Logical components are domain-specific constructs. For each component, the type and a set of attributes that are required for a particular service are contained in the structural model. Tivoli Service Automation Manager also uses the term service topology model for this description of a service. The model objects that represent the components of the service are called service topology nodes. The level of abstraction used in a service topology model is dependent on the scope of the managed service. Service Deployment Instances are the operational model of a service, defining what processes can be executed on the service/management plans)(book2 p7-5)

Book2 p7-6 gives us a Service Definitionsample. The id of this Service Definition is RDPVS(Every Service Definition is supposed to have an ID) The Service Definition topology can be found in book2 p7-8. Each service definition has a bunch of management plans(In this sample the management plans for Service Definition RDPVS  areNEW PROJEC,ADDSERVER,MODSERVER,DELSERVER and CANPROJECT book2 p7-13). Management plans are the main method used to fulfil service requests. They are started with either the self-service user interface or with external tools that interface with the Representational State Transfer (REST) API.) Every Management Plan is composed ofa few Management tasks; Every Management task is composed of a few job plans. A job plan performs a specific set of tasks related to instantiating a service or executing a management plan for the service.)(book2 p7-14)

When a Service Definition is changed(For instance oneManagement Plan has been changed), you are required to generate aUpdate Package to “notify” other Service Deployment Instances.

P9-14 gives details about Service Deployment Instances. By using Service Deployment Instances application, you can view the service topology; execute management plans and monitor the status of the deployment (p9-16). P9-17 provides a sample screen dump.

Offerings (book2 p2-19 A typical TSAM offering)—–As the name suggests it answers one question  i.e. what the Service Request can do?Offering has a bunch of attributes which can be defined in the Offering Specification tab (book2 p6-3;book2 p8-3;book2 p2-19. To change/add the specification of an Offering, you have to change the status of the offering to “Pending”. After the change, you have to change it back to “Active”(Or else some buttons like”Add” ,“OK” areinvisible)(student2 p7-29).To add a created Offering to the Service Catalogue makes the offering visible in the Self-Service User Interface.

Since it is called Service Topology, we have Service Topology Node as well. The node can be linked to Job Plan via the job plan identifier(student2 p8-22) Now we have a problem about mapping the import/export parameters from  Service Topology NodeToManagement Task(student2 p8-35).

The diagram in Basic Concepts-Relationship in TSAM.pdf illustrates the relationship between Service Definition, Management Plan, Service Topology, Service Topology Node etc.To make things more clear please refer to Basic Concepts of Tivoli Service Automation Manager.docx;The High-Level Overview of a TSAM Solution.docx

REST is a kind of Web Service.TSAM provides a few TPAe REST API(book2 p9-4).Different  RESTquery has different IEURL(book2 p9-10) A concrete sample can be found inbook2 p9-12 (Samples can be found by AA01_Query_Offering.html; AA03_Create_SR.html and AA04_Update_SR_Attributes.html ). Via the REST interface it is possible to access data stored in Maximo Business Objects (MBOs), or to even work with complex structures of multiple MBOs.