Skip to main content

Test 000-031: IBM Tivoli Service Automation Manager V7.2.1 Implementation

Tab navigation

Section 1: Architecture and Planning

  1. Given working experience with IBM Tivoli Service Automation Manager (Tivoli Service Automation Manager), describe the Tivoli Service Automation Manager Architecture, so that the understanding of the various process manager products (PMPs) and components that enable Tivoli Service Automation Manager is demonstrated.
    With emphasis on performing the following tasks:
    1. Describe the Self-Service User Interface Architecture.
    2. Describe the component Provisioning architecture.
    3. Describe the component Image Library architecture.
    4. Describe the components of Tivoli Service Automation Manager middleware.
      1. DB2
      2. LDAP
      3. WebSphere Application Server
      4. IBM http server
  2. Given working experience with Tivoli Service Automation Manager, describe the various Tivoli Service Automation Manager applications that enable the product, so that an understanding of the various Tivoli Service Automation Manager specific applications that enable the PMP is demonstrated.
    With emphasis on performing the following tasks:
    1. Describe the Service Definition and its function.
    2. Describe the how Service Topologies are created from the Service Definition.
    3. Describe the Service Topology Node application and its function.
    4. Describe the Service Topology Node Operations and its function.
    5. Describe the Service Deployment Instance application and its function.
    6. Describe the IT Topology Work order application and its functions.
  3. Given working experience with Tivoli Service Automation Manager, describe the process flow of a service request for a new project, with auto-approval enabled, and entered from the Self-Service User Interface, so that a high-level end-to-end service request process flow is described.
    With emphasis on performing the following tasks:
    1. Create a request to provision a virtual server by using the Self-Service User Interface.
    2. Self-Service User Interfaceinvokes the REST API to create the service request.
    3. Tivoli Service Automation Manager invokes reservation component to reserve resources to fulfil the request.
    4. Tivoli Service Automation Manager processes the service request and invokes the Resource_Master workflow.
    5. Tivoli Service Automation Manager issues another call to the REST API to invoke the provisioning component to fulfil the request.
    6. Provisioning component submits provisioning workflows to be executed by the TPM deployment engine.
      1. The primary workflow called to create the virtual server(s) is the RP.ClusterProvision workflow.
      2. All other workflows are called by the RP.ClusterProvision.
    7. The provisioning workflow (RP.ClusterProvision) invokes the respective commands on the hypervisor system to create the virtual systems and configure them.
    8. When complete the virtual servers are represented by objects in the data center model (DCM).
      1. The IT Topology Work order has a status of ‘COMP' (Complete).
      2. The Service Deployment Instance has a status of Operational.-The Service Topology for the project is populated with the DCM object ID and parameters of the virtual machines created.
      3. The Service Request status is set to ‘Resolved'.
  4. Given working experience with Tivoli Service Automation Manager, describe the various networking models and concepts supported in Tivoli Service Automation Manager, so that the networking models, management network, VLAN, and basic networking concepts applicable to all virtualization technologies are understood.
    With emphasis on performing the following tasks:
    1. Identify and describe the properties in the Cloud Global Properties XML file as that are related to the network models.
      1. Management Network
      2. Subnetwork setting
      3. Blocked IP Range
      4. Gateway
      5. Domains
      6. Virtual Switch DCM objects for each hypervisor
    2. Identify the components of the network that Tivoli Service Automation Manager will manage.
    3. Identify the network configuration for each resource pool.
    4. Identify the management VLAN for resource pools.
    5. Identify the external network requirement to ensure the management network can communicate with Tivoli Service Automation Manager Management System, Boot Servers, and hypervisors.
    6. Identify the Flat Network mode configuration.
    7. Identify the Multi-NIC mode configuration.
    8. Identify the property that specifies the number of network interfaces that can be connected to provisioned virtual servers.
    9. Identify the setting in the Cloud_Global_NetworkSetting.
    10. Describe setting up hostname resolution for resource pools.
    11. Describe the blocking and unblocking of IP address on saved virtual machine images.
    12. Describe the requirement for vSwitches.

Section 2: IBM Tivoli Service Automation Manager Management Server Configuration

  1. Given that IBM Tivoli Service Automation Manager (Tivoli Service Automation Manager) is running, modify a communication template from Tivoli Service Automation Manager predefined communication template so that the desired communication template is modified and activated.
    With emphasis on performing the following tasks:
    1. Access the Service Definitions application.
    2. View the Service Definition notifications tab.
    3. Start the communication templates application.
    4. Modify the communication template.
    5. Activate the communication template.
  2. Given that a Service Request is submitted through the Self-Service User Interface, describe how the classification structure and attributes defined on that structure are used to drive the provisioning process of virtual machines, so that the user is provided an offering that they can request and provision through Tivoli Service Automation Manager.
    With emphasis on performing the following tasks:
    1. Create classification structure.
    2. Identify objects that will use the classification structure, and see inputs and dependencies to determine which objects may be needed.
    3. Create attributes that will be passed into object.
    4. Create object and related records that are needed to deploy and provision the request service and associate classification structure(s).
  3. Given that a service request is submitted through the Self-Service User Interface, describe how offering available are created and deployed to the Self-Service User Interface so that User is provided an offering that they can request and provision through Tivoli Service Automation Manager.
    With emphasis on performing the following tasks:
    1. Create Classification.
    2. Create TPAE Workflow.
    3. Create New Service Definition.
    4. Create Service Offering.
    5. Add offering to Catalog.
    6. Create JavaScript file that implements offering.
    7. Create the HTML template file.
    8. Extend the Server Operation JavaScript.
    9. Test.
  4. Given that a customer requires deployment of services describe the major components and their functions of the Service Definition, so that an understanding of the features and functions of the service definition components is demonstrated.
    With emphasis on performing the following tasks:
    1. Describe what the various automation options accomplish.
    2. Describe how the Service Topology is created.
    3. Describe the various statuses of the Service Definition and there meaning.
    4. Create a new Management Plan.
    5. Create customer extension points and explain their purpose.
    6. Create and link Management Tasks to Service Topology Node and Service Topology Node Operation.
    7. Create Service Update Packages for deployment.
    8. Identify the linkage between the Service Definition and the Service Deployment Instance.
  5. Given the Service Topology Node Operation, classifications and cardinality, create service topology so that service topology is created.
    With emphasis on performing the following tasks:
    1. Create a new service topology.
    2. Create a new classification structure for the nodes.
    3. Set up cardinality for each node.
    4. Identify the node operations.
  6. Given Service Definition, Management tasks, preparation workflows, and customer extension points create a management plan so that a management plan is available.
    With emphasis on performing the following tasks:
    1. Designate the management plan as initial management plan if required.
    2. Choose the appropriate preparation workflows based on the management plan type(new, modify, or delete).
    3. Attach any customer extension workflows.
    4. Add management tasks.
    5. Change the status to "approved".
  7. Given a service definition, management plan, service topology, Service Topology Nodes, Service Topology Node Operation, Classification, and Job Plans create a new management task, so that a new management task is available.
    With emphasis on performing the following tasks:
    1. Select the execute and affected nodes.
    2. Select the topology node operation.
    3. Map input and output parameters for the Management Task.
  8. Given Service Definition, Management Plan, Service Topology, Service Topology Nodes, Classification, and Management Tasks create job plan and topology node operation, so that job plan and topology node operation are available.
    With emphasis on performing the following tasks:
    1. Create the Service Topology Node Operation.
    2. Create a new job plan or duplicate an existing job plan.
      1. Create TPAE workflow.
      2. Create a TPM workflow.
      3. Create tasks to be executed by the job plan.
      4. Identify the classification structure.
      5. Ensure the job plan is under flow control.
      6. Identify flow action for job tasks.
      7. Specify TPM and/or TPAE workflow to be executed.
      8. Create input and output parameters.
    3. Associate job plan with topology node operation.
    4. Classify the Service Topology Node Operation.
  9. Given running Tivoli Service Automation Manager system with one or more images configure and perform new software stack installation, so that a new software product is available.
    With emphasis on performing the following tasks:
    1. Create the software definition.
    2. Identify the software installable.
    3. Identify the requirements.
    4. Create the software configuration template.
    5. Add variables to the software product.

Section 3: Hypervisor Configuration

  1. Given the fully installed IBM Tivoli Service Automation Manager (Tivoli Service Automation Manager), create , import and register Virtual Server Image, so that the virtual image template is created, registered, and available for self-service virtual server deployments.
    With emphasis on performing the following tasks:
    1. Create the Linux image template for VMWare.
    2. Create the Microsoft Windows image template for VMware.
    3. Create operating system image templates for PowerVM.
    4. Create operating system image templates for KVM.
    5. Prepare OS image templates for Tivoli Service Automation Manager.
    6. Import the virtual machine template.
    7. Discover the virtual machine template.
  2. Given the fully installed Tivoli Service Automation Manager, customize and import the Hypervisor Independent Data Center Models (DCM) items such as Cloud Global Properties and Cloud Global NetworkSettings , so that Cloud Pool Object to specific hypervisor can be configured.
    With emphasis on performing the following tasks:
    1. Copy the following files from the install files DCM directory on the Tivoli Service Automation Manager to a local location:
      1. 00_Cloud_Global_Properties.xml
      2. 10_Cloud_Global_NetworkSettings.xml
    2. Customize the 00_Cloud_Global_Properties.xml file.
    3. Customize the 10_Cloud_Global_NetworkSettings.xml file.
      1. Customize the Management Subnetwork.
      2. Customize the Customer Subnetwork.
    4. Import the customized Global Properties DCM XML.
  3. Given the fully installed Tivoli Service Automation Manager, create and configure all objects required for the Cloud Pool such as file repository, computer object for hypervisor host, Hypervisor Manager,and network definition in the DCM, so that the backend hypervisor is ready to be used for cloud provisioning.
    With emphasis on performing the following tasks:
    1. Copy the specific hypervisor configuration XML template files from the install files DCM directory on the Tivoli Service Automation Manager to a local location:
      123
      Hypervisor Template Description
      VMWare 11_Cloud_NetworkSettings_VMware.xml Hypervisor network configuration for VMWare. Virtual Switch Templates for Management and Customer network.
      31_Cloud_Pool_VMware.xml Cloud Pool Definition for VMWare.
      PowerVM 12_Cloud_NetworkSettings_Systemp.xml Hypervisor network configuration for System P. Virtual Switch Templates for Management and Customer network.
      32_Cloud_Pool_Systemp.xml Cloud Pool Definition for System p.
      KVM 14_Cloud_NetworkSettings_KVM.xml Hypervisor network configuration for KVM. Virtual Switch Templates for Management and Customer network.
      34_Cloud_Pool_KVM.xml Cloud Pool Definition for KVM.
      XEN 15_Cloud_NetworkSettings_XEN.xml Hypervisor network configuration for XEN. Virtual Switch Templates for Management and Customer network.
      35_Cloud_Pool_XEN.xml Cloud Pool Definition for XEN.
      z/VM 13_Cloud_NetworkSettings_zVM.xml Hypervisor network configuration for z/VM. Virtual Switch Templates for Management and Customer network.
      33_Cloud_Pool_zVM.xml Cloud Pool Definition for z/VM.
      23_0_Cloud_Bootserver_zVM.xml Boot Server configuration for z/VM.
      23_1_Cloud_zLinuxImage_SLES10_zVM.xml Image definition of SLES10 for z/VM.
      23_2_Cloud_VSwitches_zVM.xml VSwitch definition for z/VM.
    2. Customize the XML files to create all objects required for the cloud pool, such as:
      1. Computer object for the hypervisor host;
      2. Computer object for the Hypervisor Manager;
      3. File repositories for the virtual machine images,;
      4. Network definitions (subnetwork, switch);
      5. Resource pools.
    3. Enter the Cloud Pool Administration application by clicking :Go To -> Service Automation -> Cloud Pool Administration.
    4. Import the customized DCM for specific hypervisor templates:
      1. Click the Import DCM Objects button.
      2. Browse for and select the DCM import XML files you customized
    5. Create a new CloudPool for specific hypervisor type(VMWare/KVM/XEN/PowerVM/ z/VM) or import Virtual Resources Pool from pre-configured cloud pool file : vrpool.properties.
    6. Create host objects (only for KVM hypervisor type).
    7. Add VMWare Server Trust Certificate to WebSphere Application Server(only for VMWare hypervisor type).
    8. Discover the Hypervisor Manager to examine the back end and create appropriate objects in the DCM.
    9. Discover image templates that are to be used for the provisioning of servers.
    10. Create Image Library Resources (only for VMware and LPAR hypervisor types).
    11. Configure the Save/Restore Settings.
    12. Configure Cloud Pool NetworkSettings.
    13. Validate and enable the cloud pool.
    14. Review the object references in the Related Resources-Overview section.
      1. Review the variables in the Hypervisor Manager tab.
      2. Review the variables in the Resource Pool tab.
      3. Review the variables in the File Repository tab.

Section 4: Product Integration

  1. Given that IBM Tivoli Service Automation Manager (Tivoli Service Automation Manager) and IBM Tivoli Monitoring (ITM) are installed, configure integration between the two products, so that Tivoli Service Automation Manager and ITM are integrated.
    With emphasis on performing the following tasks:
    1. Obtain a copy of the Tivoli Monitoring agent installable for UNIX® and Windows® from the ITM media.
    2. Prepare a Tivoli Monitoring agent installable for UNIX operating systems, locate an NFS server and ensure that it belongs to the same subnetwork of the provisioned virtual machines.
    3. Prepare a Tivoli Service Automation Manager agent installable for Windows Operating Systems, then locate a Samba server and ensure that it belongs to the same subnetwork of the provisioned virtual machines.
    4. Choose the appropriate DCM XML file to edit:
      1. Windows: 41_Cloud_ITM_Agent_Windows.xml
      2. Linux: 42_Cloud_ITM_Agent_Linux.xml
      3. AIX: 43_Cloud_ITM_Agent_AIX.xml
      4. Multiple OSs: 44_Cloud_ITM_Agent_AIX_Linux_Windows.xml
    5. Verify that the proper file repositories are defined in Tivoli Provisioning Manager and they reflect the previously mentioned NFS and Samba servers.
    6. Perform the appropriate step.
      1. File repository is already defined in Tivoli Provisioning Manager. Update the IP address and subnetwork mask in the network interface settings for each repository in Tivoli Provisioning Manager to match the corresponding NFS and Samba servers that you prepared previously.
      2. File repository is not defined in Tivoli Provisioning Manager. In the chosen DCM XML files, customize the clients environment.
    7. Ensure that there are not any software definitions in Tivoli Provisioning Manager with the same name as the software definition described above, specifically ITM Agent, otherwise, the next step might fail.
    8. Customize the ITM agent software definition and define it in Tivoli Provisioning Manager.
    9. Import the DCM XML file by using the Cloud Pool Administration application: Go To -> Service Automation -> Cloud Pool Administration.
    10. Update the ITM agent software definition with the Tivoli Provisioning Manager object ID of all the installable software definitions in Tivoli Provisioning Manager, that represent the operating systems on which the ITM agent will be installed.
    11. Add the ITM agent software definition to the software stack associated to the resource pool that represents the virtual environment for which you have configured Tivoli Service Automation Manager.
    12. Configure the ITM server endpoint PMRDPITM.
    13. Enable monitoring agent installation during provisioning for each of following offerings:
      1. PMRDP_0211A_72 (Add VMWare Servers)
      2. PMRDP_0212A_72 (Add System p® LPAR Servers)
      3. PMRDP_0213A_72 (Add Xen Servers)
      4. PMRDP_0214A_72 (Add z/VM® Linux Servers)
      5. PMRDP_0215A_72 (Add KVM Servers)
      6. PMRDP_0202A_72 (Create Project with System p LPAR Servers)
      7. PMRDP_0203A_72 (Create Project with Xen Servers)
      8. PMRDP_0204A_72 (Create Project with z/VM Linux Servers)
      9. PMRDP_0205A_72 (Create Project with KVM Servers)
  2. Given that Tivoli Service Automation Manager and IBM Tivoli Usage and Accounting Manager (Tivoli Usage and Accounting Manager) are installed configure the products to communicate with one another in order to provide Usage and Accounting data.
    With emphasis on performing the following tasks:
    1. Configure Tivoli Service Automation Manager server to enable SSH communication.
    2. Enable table auditing for Tivoli Usage and Accounting Manager data collection.
    3. Define the escalation to enable Tivoli Usage and Accounting Manager CSR file generation.
    4. Define the directory for CSR file generation.
    5. Configure Tivoli Usage and Accounting Manager.
  3. Given a running Tivoli Service Automation Manager system and Maximo Business Objects configure the REST API, so that provisioning is available thru Self-Service User Interface.
    With emphasis on performing the following tasks:
    1. Configure the PMRDPBC endpoint.
    2. Configure the integration application URL.
    3. Deploy the PMRDPBC API Web service.
    4. Deploy the ticket Web service.
    5. Enable the Self-Service User Interface User Management.

Section 5: Managing Tivoli Service Automation Manager

  1. Given working experience with IBM Tivoli Service Automation Manager (Tivoli Service Automation Manager), describe the Tivoli Service Automation Manager roles, so that various roles within Tivoli Service Automation Manager can be properly assigned.
    With emphasis on performing the following tasks:
    1. Describe the Self-Service User Interface roles.
      1. Cloud administrator role
      2. Cloud manager role
      3. Team administrator role
      4. Team user role
    2. Describe the Administration GUI roles.
      1. Service Administrator
      2. Service Definition Designer
      3. Service Definition Manager
      4. Service Deployment Instance Manager
      5. Service Deployment Instance Operator
      6. Service Resource Allocation Manager
      7. Performance - AIX® Administrators
      8. Performance - DB2® Administrators
      9. Performance - WAS Administrators
      10. Performance - z/OS® Administrators
      11. Performance - Linux® Administrators
      12. Performance Monitoring Administrator
      13. OS Appliance - z/VM® Administrator
      14. OS Appliance - Linux on System z® Administrator
      15. OS Appliance - z/OS Administrator
      16. OS Appliance - Network Administrator
  2. Given that Tivoli Service Automation Manager is running, and rights, create a new user so that the user can use the provisioned servers.
    With emphasis on performing the following tasks:
    1. From the Self-Service User Interface, select Request a New Service -> Virtual Server Management -> Manage Users -> Create User.
    2. Provide user ID and a display name for the user.
    3. Specify and confirm password.
    4. Select a role for the user (Team user).
  3. Given that Tivoli Service Automation Manager is installed and configured ,Use self-service virtual server management offering so that the project is created, modified or cancelled.
    With emphasis on performing the following tasks:
    1. Create project and add virtual server.
    2. Create project from saved image.
    3. Modify the project.
    4. Modify server.
    5. Cancel the project.
  4. Given the fully configured Tivoli Service Automation Manager, register virtual server images into the Image Library, so that Virtual Images are available to be used for provisioning.
    With emphasis on performing the following tasks:
    1. Register an image with Image Library.
      1. Verify that the Image Library is accessible.
      2. Register the image by using the self-service offering.-Specify the name of the image, and optionally provide its description.-Select the Resource Pool from the drop-down list.-Select Discovered Image from the drop-down list. The list contains only the unregistered images.
      3. In the Resources section, specify the Minimum and Recommended values for virtual CPUs, physical CPUs, memory, and disk space.-Click OK to submit the request.
    2. Unregister an image in the Image Library by using the unregister image self-service offering.
      1. Select Home -> Request a New Service -> Virtual Server Management -> Manage Image Library -> Unregister Image.
      2. Select a Resource Pool from the list.
      3. Select the image that you want to unregister.
      4. Click OK to submit the request.
  5. Given the working Tivoli Service Automation Manager, create server images, and restore a server from image and remove server image, so that Snapshot-like server images can be created or removed.
    With emphasis on performing the following tasks:
    1. Create Server Image
      1. In the Home panel, click Request a New Service -> Virtual Server Management -> Backup and Restore Server Image -> Create Server Image.
      2. In the corresponding fields, type in 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. A list of all images available for this server is displayed.
      5. Click OK to submit the request.
    2. Restoring a server from Image
      1. In the Home panel, click Request a New Service -> Virtual Server Management -> Backup and Restore Server Image -> Restore Server From Image.
      2. From the Project Name list, select a project for which you want to restore a server.
      3. Select a server that you want to restore.
      4. From the list that displays, select the image that is to be used for restoring the server.
      5. Click OK to submit the request.
    3. Removing server image
      1. In the Home panel, click Request a New Service -> Virtual Server Management -> Backup and Restore Server Image -> Remove Saved Images.
      2. From the list that displays, select the image that is to be removed.
      3. Click OK to submit the request.
  6. Given the working Tivoli Service Automation Manager with ITM Agent software definition configured, create a self-service request to create project and add virtual servers with ITM agent, so that the ITM Agent is deployed to virtual server.
    With emphasis on performing the following tasks:
    1. In the Home panel, click Request a New Service -> Virtual Server Management -> Create Project with server type.
    2. Enter a Project Name.
    3. Select the team that should have access to the project.
    4. Set the start / end date and time.
    5. Select resource group used to reserve resources.
    6. Select Monitoring Agent to be installed. This agent performs scans to identify server resource utilization (memory, CPU and disk space).
    7. Select the image to be deployed.
    8. In the Resources section, adjust the settings of the requested resources as required.
    9. Click OK to submit the request.
    10. Verify the Provisioning Status. In the Self-Service User Interface, select your projects from My Projects portlet.
  7. Given that Tivoli Service Automation Manager is fully installed and the appropriate data is collected by Tivoli Service Automation Manager, configure the reporting function and authorise the users to access reports, so that the appropriate report can be scheduled and created.
    With emphasis on performing the following tasks:
    1. Create the Request Pages.
    2. Enable table auditing.
    3. Authorize users to access reports.
    4. Generate the specific report immediately.
    5. Schedule a report to run in the future.
  8. Given a modified service definition, build a service update package and deploy it on the existing service deployment instances, so that service definition modifications are applied to existing projects.
    With emphasis on performing the following tasks:
    1. Build a service update package from an existing service definition.
      1. Create a new service update package by using the service definition application.
      2. Open the inbox assignment and refine the new service update package
      3. Route the workflow.
      4. Approve the new service update package.
    2. Deploy a service update package on existing service deployment instances.
      1. Start the deployment of the service update package on existing service deployment instances.
      2. Monitor the deployment process.
  9. Given customized service definitions, management plans, topology, classifications, attributes, service offerings and workflows, build and deploy migration manager packages, so that new or customized Tivoli Service Automation Manager solution artifacts are migrated and available on the target system.
    With emphasis on performing the following tasks:
    1. Make sure that all prerequisite structures are available in the target database by packaging these separately (in a so-called library part) and importing this package on the target system.
      1. Document all new artifacts and their dependencies,Classifications.
      2. domains
      3. TPAE workflows, actions, action groups, roles
      4. escalations, communication templates
      5. service definitions, topology templates, management plans, Topology Node Operations, Job plans, TPM workflows
      6. any custom class file
    2. Using migration manager, create new packages by using the appropriate predefined migration groups.
      1. DATADICTIONARY (classifications, domain etc)
      2. BPM (workflow and related artifacts)
      3. Tivoli Service Automation Manager_TNOPS (service definitions, management plans, topology templates)
    3. Select only custom records by using "Set where clause" in the migration manager application.
    4. Activate the migration manager packages.
    5. Create a new target for the migration package.
    6. Distribute the migration package to the target system.
    7. Upload the migration package on the target system.
    8. Deploy the migration package on the target system.
    9. If applicable, manually deploy the class files.
      1. Copy the class files from the migration package zip file on the administrative workstation.
      2. Expand the files into the directory structure.
      3. Regenerate the maximo.ear file.
      4. Deploy the ear file into WAS.
    10. If applicable, install the TPM workflows.
      1. Import any customer automation package by using the command line tool.
      2. Import any individual TPM workflow that is not included in an automation package.

Section 6: Customization

  1. Given the existing business processes and operational IBM Tivoli Service Automation Manager(Tivoli Service Automation Manager) environment, create a new TPAE sub-workflow so that the desired approval process is used as part of the self-service offerings.
    With emphasis on performing the following tasks:
    1. Describe the out-of-the-box approval process.
    2. Identify the existing Cloud role(s) that will need to approve the requests.
      1. Team Manager
      2. Team Administrator
      3. Cloud Administrator
    3. Identify the offerings and management plans that will be used with the new approval workflow.
    4. Disable the global auto-approval system property.
    5. Identify the approval criteria(s).
    6. Create relationships to ticket specifications in the Service Request object.
    7. Create a new TPAE workflow by using the workflow designer.
      1. Use condition nodes.
      2. Use inbox assignments.
    8. Assign the approval workflow to the customer extension point on the management plan.
  2. Given the automation task and input parameters, create and test a new TPM workflow so that the desired automation is achieved.
    With emphasis on performing the following tasks:
    1. Determine if there are existing scripts that can be used as part of the new workflow.
    2. Determine the best tool to use for creating TPM workflows.
      1. A text editor which doesn't require any special software and configuration.
      2. Built-in web based workflow application which is easily accessible from the administration user interface.
      3. Automation Package Development Environment (APDE) which provides extra features such as data center query, running workflows, automation package creation and more.
    3. Identify the input and output parameters based on the design specifications.
      1. Determine how the workflow will be called.
      2. Tivoli Service Automation Manager topology node operation.
      3. Another TPM workflow.
      4. As part of a logical device operation.
    4. Configure the data center model (DCM).
    5. Create a workflow by using the DCM objects queries, logical device operations, other workflows, logical device operations, Jython, log and documentation statements.
    6. Test the workflow by using valid input parameters and check to see if the desired automation and output parameters are obtained.
    7. Document the steps required to successfully run the workflow.
    8. Perform an end-to-end test that involves other components of Tivoli Service Automation Manager such as management plans, offerings, Self-Service User Interface.
  3. Given the service offering and input parameters, identify the input parameters, modify the appropriate classification and define new values, so that the parameters are passed from the service offering to the automation layer.
    With emphasis on performing the following tasks:
    1. Identify the parameters to pass and data types (ALN, NUMERIC).
    2. Determine where these parameters will be used:
      1. Service Request
      2. Service Offering
      3. Management Plans
      4. TPAE workflows
      5. TPM workflows
    3. Add a new parameter to the classification on the offering.
    4. Reclassify the offering.
    5. Define values for the attributes and test the solution.

Section 7: Problem Determination

  1. Given a failed image registration, troubleshoot the image registration so that an image is successfully registered.
    With emphasis on performing the following tasks:
    1. Look at the system out log file.
    2. Analyse the file.
    3. Perform the appropriate action.
    4. Edit the discovered software stacks to:
      1. Modify the software-capability attributes.
      2. Add a software resource template (SRT) to define the root password of the discovered VMWare template.
    5. Ensure os.family and os.version attributes are set.
  2. Given a resource pool is not available, verify that discoveries for Cloud Pool Administration were run successfully, so that resource pool definitions are imported successfully.
    With emphasis on performing the following tasks:
    1. Go to vrpool properties to ensure resource pools are defined correctly.
    2. Go to Cloud Pool Administration application.
    3. Verify that the resource pool has property "cloud" set to "true".
    4. Ensure appropriate variables are defined for hypervisor.
  3. Given an issue with an IT topology work order, troubleshoot the IT topology work order, so that the IT Topology Work Order is processed successfully.
    With emphasis on performing the following tasks:
    1. Go to the IT Topology Work orders application.
    2. Review messages and status changes related to the current work order.
    3. Review requests, and their status, made by Tivoli Service Automation Manager.
  4. Given provisioning issues, troubleshoot the issues so that the provisioning process for VM is successful.
    With emphasis on performing the following tasks:
    1. Go to Cloud Pool Administration application.
      1. Verify Cloud Pool discoveries have run successfully.
    2. Go to Provisioning Workflow Status application.
    3. Click
    4. Set Cloud.PROVISION_FAILURE_DEBUG_SLEEP_TIME to keep the VM from being deleting for debugging purposes.
  5. Given a file-transfer, or execute-command error in the TPM workflow, verify and update TPM Server SAP, Hypervisor Manager SAP, so that the problem related to file-transfer or execute-command in the workflow is identified.
    With emphasis on performing the following tasks:
    1. Verify that RSA keys are exchanged between TPM and the virtual server.
    2. Verify the SSH-Server, SSH-Client, SCP-Client, tiocred SAP credential of TPM Server.
    3. Verify the SSH and SCP SAP Credential of Hypervisor Manager.
  6. Given an operational Tivoli Provisioning Management environment and Hypervisor Manager, troubleshoot the RP.ClusterProvision TPM workflow, so that the root cause of a problem can be determined.
    With emphasis on performing the following tasks:
    1. Review the virtual machine resource requirements in the service request.
    2. Review error log in the RP.ClusterProvision Workflow.
    3. Review logs in the Hypervisor Manager.
    4. Verify that virtual server can be provisioned through Hypervisor Manager.
    5. Refer to Troubleshooting section in the Tivoli Service Automation Manager Installation and Administration Guide documentation.

Register for a test

Register for an IBM Certification test at Prometric and take a step into your future.

IBM at Prometric