IBM


IBM Professional Certification Program

Accelerate insight. Improve skills. Get certified now.

Test 000-567: IBM Tivoli Provisioning Manager V7.2.0.2 Implementation


Note: This test will be withdrawn on Nov 30 2013.

Section 1: Planning


  1. Given the need to perform a IBM Tivoli Provisioning Manager V7.2.0.2 (TPM) installation, study the customer's network diagram, document the network locations, devices, bandwidth, connectivity, number of TPM depots to install so that the TPM performance and usability will be properly set up.
    With emphasis on performing the following tasks:

    1. Study the customer's network diagram and interview the network operational personnel.

    2. Document the network locations and devices which need "service" from the management servers.

    3. Document the network bandwidth and connectivity from the management servers to the managed devices.

    4. Document the managed devices which have low bandwidth connectivity from the management servers.

    5. Document the strategic placement for TPM depots in locations where bandwidth is poor.

  2. Given the need to perform a TPM installation in a customer's scenario, determine the customer's requirements such as language, name space, backup and recovery strategy, implementation plan so that the TPM installation will be properly deployed as for customer's expectations.
    With emphasis on performing the following tasks:

    1. Determine what language pack customer wants to be used for future TPM installation.

    2. Determine name space and identity of the management environment.

    3. Identify backup and recovery strategy.

    4. Identify the implementation plan.

  3. Given the need to perform a TPM installation in a customer's scenario, determine the customer's business objectives by identifying the Patch Management, integration and reporting requirements,and the management of virtualization environment so that the TPM installation can be properly set up as per customer's objectives.
    With emphasis on performing the following tasks:

    1. Identify the patch management requirements.

    2. Identify integration requirements.

    3. Identify the management of virtualization environment.

    4. Determine the reporting requirements.

  4. Given the proper scope of a customer's security environment within the target IT architecture, identify the security requirements necessary so that a properly documented security environment has been identified, which will support a successful TPM environment.
    With emphasis on performing the following tasks:

    1. Identify firewall requirements.

      1. Query customer security representative, acquire customer security operating standards.

      2. Document/Obtain customer firewall configuration.

      3. Identify potential changes to port assignments of TPM Middleware or core components.

      4. Recommend firewall changes for successful TPM implementation.

    2. Determine REMOTE EXECUTION AND ACCESS (RXA) requirements.

      1. Identify and confirm the presence of Windows access points. -Remote registry administration enabled.-Default hidden administrative shares are enabled (C$, D$, etc...).-Simple File Sharing for Windows XP is disabled.-Disable password protected sharing in Windows 7 and Windows 2008.-Modify registry entry in Windows 7 and Windows 2008.-Windows Scripting Host or Window Module Instrumentation is enabled.-Disable Internet connection firewall or Windows firewall.-Identify Windows machines requiring SSH if the common agent is not planned to be installed on Windows machines.

      2. Identify and confirm the presence of UNIX Access points.-SSHD is operational.-Root or administrative level privileges.

    3. Determine Service Access Points (SAPs).

      1. RXA-SAPs

      2. SSH-server

      3. SSH-client

      4. SCP-server

      5. SCP-client

      6. Telnet-server

      7. Telnet-client

      8. FTP-server

      9. FTP-client

      10. SDI-SAP

      11. Agent-server

  5. Given the need to perform a TPM installation, identify the deployment topology so that the TPM installation matches all the TPM software/hardware/product requirements.
    With emphasis on performing the following tasks:

    1. Identify the IP stack requirements (IPv4 and/or IPv6).

    2. A 64-bit management architecture is required for the TPM server.

    3. Determine the middleware requirements.

    4. Validate the management of the target infrastructure (HW/SW) which is supported by TPM.

    5. Determine the necessary hardware, in particular memory and disk space resources.

  6. Given a customer's environment and delivery requirements, determine the installation type and method so that an installation type has been determined.
    With emphasis on performing the following tasks:

    1. Review customers' environment to identify needs/requirements.

      1. Verify OS.

      2. Verify the number of machines for implementation.

      3. Identify if any existing middleware.

    2. Determine whether the requirements can be met with the default installation (i.e. single machine, Windows only, no existing middleware, default names can be used).

    3. If a default installation cannot meet the customer's requirements, evaluate what customized settings are needed (i.e. database version, Tivoli Directory Server or Microsoft Active Directory or WebSphere Application Server, OS types) .

    4. Review customer's deployment plan for installation (i.e. GUI or silent ) .


Section 2: Installation


  1. Given the proper scope of a customer's provisioning requirements, prepare for the installation of IBM Tivoli Provisioning Manager V7.2.0.2 (TPM)'s middleware, base, Core, and Web Components so that the user can precede with the installation of the Middleware components.
    With emphasis on performing the following tasks:

    1. Read the release notes and READMEs associated with the installation.

    2. Verify component requirements.

    3. Determine installation method.

    4. Plan hardware usage based on product requirements.

    5. Review user account requirements.

    6. Verify environment variables including naming conventions, fully qualified domain names, remote connections required.

    7. Obtain software.

      1. Download assemblies or images from IBM Passport Advantage.

      2. Stage installation software after uncompressing.

  2. Given a right-sized server and supported operating systems, install required Middleware components so that user can proceed with the installation of TPM 7.2 server.
    With emphasis on performing the following tasks:

    1. Obtain software.

    2. Verify installation prerequisites in the GUI.

    3. Choose method of installation: default or custom.

    4. Determine hostname values of only 8 characters.

    5. Determine if IBM Autonomic Deployment Engine is operational.

    6. Input by using the GUI or in a silent installation response file: locations of middleware files, user accounts, and security contexts.

    7. Verify the operability of Middleware components.

  3. Given a supported operating system with right sized/supported hardware and the proper inputs for Middleware components, perform a TPM installation so that an operational TPM management server is available for post-installation activities.
    With emphasis on performing the following tasks:

    1. Input to either the TPM GUI or the silent installation response file: Database, Operating System, Application, Directory Server credentials and configuration information (for multiple server installations), location of base services files and/or server.

    2. Input to either the TPM GUI or the silent installation response file: Database, Operating System, Application, Directory Server credentials, location of Agent Manager files, location of DMS files, location of TPM server.

    3. Verify prerequisites before installing a component of the TPM server.

    4. Verify Cygwin version as 1.5.10.

    5. Input port assignments for Agent Manager.

    6. Activate Directory Server before base services installation.

    7. Determine fully qualified domain name space or service IP Address for Agent ,Manager use.

  4. Given the need to configure TPM after installation, perform post-installation tasks so that TPM is ready to be used.
    With emphasis on performing the following tasks:

    1. Back up the administrative workstation.

      1. Create a backup of the installed base services and Web components packages that have been deployed to the Application Server. In C:\Program Files\IBM\Common\acsi\bin run the command: de_backupdb.cmd -bfile C:\IBM\SMP\DE_BACKUPS\AFTER_INSTALL_PMP_7.2.0.0

      2. Create a backup of the deployment directory. The default location is C:\IBM\SMP.

      3. Create a backup of the registry entries.

    2. DHCP server configuration for TPM for OS deployment (when DCHP server and TPM for OS deployment server are on different computers).

      1. Without information about Preboot eXecution Environment (PXE) server location, if DHCP options 43 and 60 are set, remove them.

      2. Without information about PXE server location, if the DHCP server is not running on the same target as the OS deployment server, the DHCP configuration does not change. The OS deployment server detects DHCP packets sent over the network by PXE bootroms and offers PXE parameters without disturbing standard DHCP negotiation process. This behavior is called DHCP Proxy.

      3. With information about PXE server location, set option 60 (Class identifier) to _PXEClient_ to inform the computer that the location of the PXE server is known.

      4. With information about PXE server location, set option 43 to indicate that the PXE server does not reside on the same computer as the DHCP server and to precise the location of the PXE server.

    3. DHCP server configuration for TPM for OS deployment (when DCHP server and TPM for OS deployment server are on the same computer).

      1. If DHCP option 43 is set, remove it.

      2. Set option 60 (Class identifier) to "_PXEClient_" to inform the target that the location of the PXE server is known.

    4. Configure SSL with IBM HTTP server.

      1. On UNIX, configure IBM HTTP server to run as tioadmin.

      2. Configure an SSL connection with IBM HTTP server.

      3. Remove unused ports from maximo_host in WebSphere Application Server.

    5. Upgrade DB2 to V 9.5.

      1. Verify the requirements for DB2 V9.5 installation.

      2. Back up the current DB2 database and its settings (by offline maintenance).

      3. Ensure the database is stopped as well as TPM components and all middleware.

      4. Perform the upgrading to V9.5 plus fix pack 2a or later.

      5. Start the TPM Middleware and Core Components.

    6. Manually configure the VMMSYNC Cron task for Microsoft Active Directory.

      1. Reconfigure the VMMSYNC Cron task for use with Microsoft Active Directory.

      2. Open a Web browser and point to http://hostname/maximo.

      3. Log in to TPM by using the maxadmin user ID.

      4. From the TPM interface, navigate to Go To -> System Configuration ->Platform Configuration -> Cron Task Setup. 6.1.4 Type VMM in the Cron Task field, and hit Enter.

      5. Locate the VMMSYNC Cron task, and click it.

      6. Configure the appropriate values.

      7. Click the Save icon.

    7. Synchronize users and groups.

      1. Log in to the TPM Start Center GUI with maxadmin user ID then locate and configure the VMMSYNC Cron task: -Open a Web browser and point to http://hostname/maximo. -Log in to TPM by using the maxadmin user ID. -From the TPM interface, navigate to Go To -> System Configuration -> Platform Configuration -> Cron Task Setup. -Type VMM in the Cron Task field, and hit Enter. -Locate the VMMSYNC Cron task, and click it. -Ensure the appropriate values are used for each field.-Set the task to Active.-Click the Save icon.

    8. Configure TPM security.

      1. Login as MAXADMIN security group member user ID.

      2. Create a new user and a new security group in WebSphere Administrative Console V6.1.

      3. Assign the created user to the chosen security group in WebSphere Administrative Console V6.1.

      4. Import them into Tivoli Provisioning Manager by means of setting up synchronization between the Virtual Member Manager and the system.

    9. Use the Tivoli Monitoring Agent.

      1. Prepare an ITM V6.x environment (monitoring agent support on the IBM Tivoli Enterprise Monitoring Server, IBM Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal Server desktop client).

      2. Install the Tivoli Monitoring Agent on the TPM server computer.

    10. Configure a Web browser for Federal Information Processing Standard 140-2 compliance

      1. Select Use TLS 1.0 to configuring a Web browser for Federal Information Processing Standard 140-2 compliance.

    11. Manually configure directory synchronization.

    12. Configure LDAP server.

    13. Secure files in WebSphere Application ServerA number of files must be reconfigured with the correct permissions. This can be done by running command chmod -R 755 $WAS_HOME/systemApps/isclite.ear

  5. Given an operational TPM V7.2 server, prepare the server for the upgrade and perform upgrade the server to fix pack 1 level so that the fully operational TPM 7.2.0.1 server which can now be used for post upgrade tasks.
    With emphasis on performing the following tasks:

    1. Verify the disk space requirements.

    2. Before starting fix pack installation, verify the required utilities.

    3. Verify automation packages.

    4. Remove Actuate files.

    5. Back up your installation.

    6. Verify the fix pack installation package.

    7. Configure DB2 parameters / Check Oracle status.

    8. Update core components to version 7.2.0.1.

      1. Run the following command to update the core components. These options are case-sensitive. Windows: winCoreCompUpgrade.bat -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin db_adminID-DBAdminPWD db_admin_pwd -DB2Inst db2_instance -AMPWD am_pwd UNIX : For DB2 Universal Database: unixCoreCompUpgrade.sh -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin db_adminID-DBAdminPWD db_admin_pwd -AMPWD am_pwd For Oracle Database: unixCoreCompUpgrade.sh -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin sys -DBAdminPWD db_admin_pwd -AMPWD am_pwd -CDSOraclePWD cds_schema_pwd-Manually back up your application data.-Stop the WebSphere Application Server.-Manually back up your database.- If you have the IBM® monitoring agent installed, you must restart it after the core components update is complete.

    9. Update Web components to version 7.2.0.1.

      1. Back up the administrative workstation.

      2. Input values to the Web components installer which is to be run by using C:\IBM\SMP\bin\solutionInstallerGUI.bat/opt/IBM/SMP/bin/solutionInstallerGUI.sh.

  6. Given that Fix pack 01 has been performed on a TPM V7.2 server, perform post upgrade actions to the server so that post install tasks have been performed on the Tivoli Provisioning Manager 7.2.0.1 server.
    With emphasis on performing the following tasks:

    1. Upgrade reports. This step should be followed after installing TPM V7.2 Fix Pack 1, or TPM V7.2 with an interim fix installed.

    2. Update virtual server templates.

    3. Configure RSA credentials.

    4. Reload Maximo classes and update detection properties.

  7. Given a fully running TPM 7.2.0.1 Server, perform pre-upgrade tasks and perform the steps to upgrade the server to 7.2.0.2, so that the TPM server is ready for post installation steps.
    With emphasis on performing the following tasks:

    1. Verify the disk space requirements.

    2. Verify the required utilities.

    3. Verify automation packages.

    4. Back up your installation.

      1. If Possible backup the full System. If not, follow the below steps.

      2. Back up the Tivoli Provisioning Manager installation directory.

      3. Back up the Agent Manager.

      4. If your database is on a separate computer, back up that data also.

      5. Back up the administrative workstation.

      6. Back up the application server.

      7. Save workflows that you created in the Web interface that you want to keep.

    5. Update the base services.

      1. This involves upgrading Maximo® Base Services to 7.1.1.8 Fix Pack.

      2. Manually back up the administrative workstation by using: Windows: de_backupdb.cmd -bfile MAXIMO_HOME\DE_BACKUPS\AFTER_INSTALL_PMP_7.2.0.2 UNIX: ./de_backupdb -bfile MAXIMO_HOME/DE_BACKUPS/AFTER_INSTALL_PMP_7.2.0.2

      3. Install the Maximo Base Services 7.1.1.8 hotfix.

    6. Update core components.

      1. Back up the Tivoli Provisioning Manager installation directory.

      2. Back up your database.

      3. Back up the Agent Manager.

      4. Run the below command to update the core components. Windows: winCoreCompUpgrade.bat -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin db_adminID -DBAdminPWD db_admin_pwd -DB2Inst db2_instance -AMPWD am_pwd UNIX: For DB2 Universal Database: unixCoreCompUpgrade.sh -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin db_adminID -DBAdminPWD db_admin_pwd -AMPWD am_pwd For Oracle Database: unixCoreCompUpgrade.sh -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin sys -DBAdminPWD db_admin_pwd -AMPWD am_pwd -CDSOraclePWD cds_schema_pwd

    7. Manually back up the application server data.

    8. Manually back up the Database.

    9. Update Web components.

      1. Back up the administrative workstation.

      2. Run the below command and input values on the GUI screen. Windows: C:\IBM\SMP\bin\solutionInstallerGUI.bat UNIX: UNIX /opt/IBM/SMP/bin/solutionInstallerGUI.sh

  8. Given a fully running TPM 7.2.0.2 Server, perform the post Upgrade steps so that the TPM 7.2.0.2 server is fully operational.
    With emphasis on performing the following tasks:

    1. Update maximo.properties file.

    2. Tivoli Common Agent Services and WebSphere Application Server upgrades.

    3. Reinstall Agent Manager with Bundled Java Virtual Machine (JVM).

      1. Preinstallation tasks to install the Agent Manager with Bundled JVM.

      2. Recreate and configure casprofile to run as tioadmin.

      3. Installation of Agent Manager with Bundled JVM.

      4. Post-installation tasks for reinstalling Agent Manager with Bundled JVM.

    4. Sync Maximo business objects.

    5. Update virtual server templates.

    6. Reload Maximo classes and update detection properties.

    7. Optional: Upgrade DB2 to version 9.7.

    8. Optional: Enable tivoli09 as the default skin.

    9. Optional: Update the Start Center.

  9. Given the need to verify the installation, log on to the Web interface, and stop TPM. Also configure the Web browser to use the TPM certificate and verify that core components are installed correctly and they can be started or stopped individually so that the TPM installation has been validated.
    With emphasis on performing the following tasks:

    1. Start and stop server on Windows.

      1. Execute tio.cmd start command in order to startup the TPM server.

      2. Execute tio.cmd stop command in order to startup the TPM server.

    2. Start and stop server on UNIX and Linux.

      1. Execute tio.sh start command in order to startup the TPM server.

      2. Execute tio.sh stop command in order to startup the TPM server.

    3. Start and stop TPM components.

      1. Execute the following commands in order to start TPMfOSD component: -On Windows:-Log in as administrator. -In a command window, type the following commands: net start remboserver net start remboagent-On Linux:- Log on as root.- Run the following commands: /etc/init.d/rembo start /etc/init.d/rbagent start

      2. Execute the following commands in order to start Tivoli Monitoring Agent component: -On Windows-tacmd startagent -t pe -On UNIX or Linux -/itmcmd agent start pe

      3. Execute the following commands in order to start Agent Manager component: -On Windows-Change to the AM_HOME\bin directory.-Run the following command: startServer.bat server1-On UNIX or Linux-Change to the AM_HOME/bin directory.-Run the following command: ./startServer.sh server1

      4. Execute the following commands in order to stop TPMfOSD component : - On Windows-Log in as administrator. -In a command window, type the following commands: net stop remboagent net stop remboserver-On UNIX or Linux -Log on as root. -Run the following commands: /etc/init.d/rbagent stop /etc/init.d/rembo

      5. Execute the following commands in order to stop Tivoli Monitoring Agent component: -On Windows-tacmd stopagent -t pe-On UNIX or Linux- ./itmcmd agent stop pe

      6. Execute the following commands in order to stop Agent Manager component: -On Windows-Change to the AM_HOME/bin directory. -Run the following command: stopServer.bat server1 -username wasadmin_username -password wasadmin_password- On UNIX or Linux-Change to the AM_HOME/bin directory.-Run the following command: ./stopServer.sh server1 -username wasadmin_username -password wasadmin_password

    4. Log on to the provisioning server.

      1. Launch the Web browser and enter the URL: https://hostname/maximo (replace hostname with the fully qualified domain name of the provisioning server)

      2. In the Log On window, type the User ID and Password and click Log On.

      3. Or https://:9443/maximo/ui/login

    5. Sign out the provisioning server.

      1. Click Sign Out to sign out of the Web interface.

    6. Verify components

      1. Start TPM.

      2. Log on to the Web interface.

      3. Verify the installation of device manager service.

      4. Verify that user can log on to the DCD Management Console.

      5. Verify status of the Agent Manager.

      6. If TPM for OS deployment has been installed, verify the installation.

      7. Verify that user can log on to the WebSphere administrator console.


Section 3: Configuration


  1. Given that IBM Tivoli Provisioning Manager V7.2.0.2 (TPM) is installed, configure the management environment so that the managed environment has been configured to maximize the device discovery success rate.
    With emphasis on performing the following tasks:

    1. By using a network administrator ID with the proper access and authority, set all of the switch ports to auto-negotiate.

    2. Configure firewalls to accept the UDP/TCP connections required for proper TPM operation.

    3. For a complete list of TPM's default ports, including the Usage, Protocol, TPM server port number, Data flow direction, and Target device port number, Reference the Installation Guide-> Preinstallation Tasks-> Step 6: Verify the environment-> Table 1.

    4. Change the automatic session timeout setting from the default of 30 minutes through the web.xml configuration file.

      1. Back up the web.xml file located in the $MAXIMO_HOME/applications/maximo/maximouiweb/webmodule/WEB-INF directory.

      2. Search for the tag in the section of the web.xml file.

      3. Specify a new value for the tag.

      4. Save the web.xml file.

      5. Rebuild the maximo.ear file.

      6. Deploy the maximo.ear file.

    5. Configure email status notification for tasks, workflows, reports, software distribution, discoveries, and compliance activities.

      1. On the TPM server, select Go To-> Administration-> Provisioning-> Provisioning Global Settings.

      2. Select the Notification tab and configure the SMTP mail server by setting the variables.

  2. Given a working TPM server, a TPM user with the appropriate roles, and knowledge about the location and credential information for computers to be discovered, initiate an initial discovery in the TPM user interface, provide the network and credential information for the task, and submit the discovery so that desired computers and their information will be added to the DCM.
    With emphasis on performing the following tasks:

    1. Log on to the TPM server Web interface.

    2. Navigate to Discovery Configurations.

    3. Click on Initial Discovery.

    4. Select the appropriate network address option for the target computer(s) (IP Address Range or Subnetwork).

    5. Add a new row for the desired target computers/subnet.

    6. Add the appropriate Credentials for the computer(s) specifying both the user name and the password.

    7. Specify a schedule or notification if required.

    8. Submit the discovery.

  3. Given a working TPM server, a TPM user with the appropriate roles, a network diagram and the list of customer requirements for logically grouping systems, use the TPM user interface to create the appropriate regions and zones so that the regions and zones will be defined in the TPM management environment.
    With emphasis on performing the following tasks:

    1. Log on to the TPM server Web interface.

    2. Navigate to Go To -> Administration -> Provisioning -> Dynamic Content Delivery Configuration.

    3. Click on the Regions tab.

    4. Determine how to implement the customer requirements and network setup into TPM regions and zones.

    5. Add a new row for each desired region and save each region.

    6. Click on the Zones tab.

    7. Add a new row for each zone desired.

    8. Provide the region name and IP address range or domain name for the zone.

    9. Select the appropriate options according to the customer's requirements for peering, minimizing traffic ,and other network settings.

  4. Given a working TPM server, a TPM user with the appropriate roles, a network diagram, the customer requirements for the distribution hierarchy, computers on which to deploy the components, and predefined regions and zones, specify the relevant information about the depot and install the appropriate software product to the eDMS target so that the software depots and device manager federated agents are deployed into the TPM management environment.
    With emphasis on performing the following tasks:

    1. Deploy a software depot.

      1. Determine where depots are required in the customer environment.

      2. Log on to the TPM server Web interface.

      3. Navigate to Dynamic Content Delivery Configuration.

      4. Click on the Depot tab.

      5. Add a new row for each desired depot, specifying the appropriate IP address, region name, zone name, and target computer.

      6. Select to install the depot agent services.

      7. Specify the data directory limits and any network requirements imposed by the customer.

      8. Save the depot information and monitor the deployment.

    2. Deploy a device manager federated agent. (eDMS).

      1. Determine where eDMSs are required in the customer environment.

      2. Verify the target computers meet the requirements for hosting an eDMS.

      3. Run a discovery scan to discover the target computer.

      4. Ensure the appropriate operating system is specified for the target computer.

      5. Install the eDMS_LWI software product to the target.

      6. Verify that the software product was installed successfully.

  5. Given a working TPM server, a TPM user with the appropriate roles and the customer requirements for file repositories, use the TPM user interface to create and configure the file repository so that the file repository will be defined in the TPM management environment.
    With emphasis on performing the following tasks:

    1. Log on to the TPM server Web interface.

    2. Navigate to Go To -> IT Infrastructure -> Provisioning Inventory -> File Repositories.

    3. Click on the New icon.

    4. Specify the name and root path of the file repository.

    5. Save the form.

    6. Configure the file repository with the appropriate network interface card, Service Access Point and device model.

  6. Given the customer environment, computers are organized into groups so that multiple computers can be managed as a single target.
    With emphasis on performing the following tasks:

    1. Organize computers into groups based on type, function, location, or other characteristics.

    2. Determine which groups should use static group definitions and which should use dynamic group definitions.

    3. Build queries to define members of dynamic groups.

      1. Navigate to the Provisioning Computers application.

      2. Type query string into fields.

      3. Click Save Query.

    4. Create group objects in TPM.

      1. Click Go To -> Deployment -> Provisioning Groups.

      2. Click the New Provisioning Group icon.

      3. Type in the name and description of the group.

    5. Assign computer objects to static groups.

    6. Assign queries to dynamic groups.

  7. Given that TPM is installed and the environment is ready, navigate to the correct section of the GUI and deploy the Tivoli Common Agent (TCA) to target systems or alternatively install TCA as stand-alone, with considerations for timing settings so that the TCA is successfully deployed.
    With emphasis on performing the following tasks:

    1. Configure the agent with environment specific time considerations:

      1. Click Go To -> IT Infrastructure -> Software Catalog -> Software Stacks.

      2. Find the software stack called Tivoli Common Agent Stack or CDS_Depot_Stack and click it.

      3. Under Configuration Templates, expand the TCA-TPM-Base Feature default template

      4. Select TCA-JES Default.

      5. Click the icon for the PollingInterval parameter and type the new interval in the Value field. For example, if you want to set it to 10 minutes, enter 00:10

    2. Perform the agent installation:

      1. Click Go To -> Deployment -> Software Management -> Common Agent Installation.

      2. Under Common Agent Stacks, select the common agent software stack to install on the target systems. The default software stack is Tivoli Common Agent Stack.

      3. Click Select -> Groups and select the provisioning group that someone wants to work with, for example, Test group, then click OK.

      4. Leave the Create Credentials check box unchecked. No credentials are required, as they were added to the target computers during discovery.

      5. Click Schedule to specify the date and time when the task starts.

      6. Click Submit.

    3. Perform TCA stand-alone installation

      1. Log on as tioadmin to the provisioning server.

      2. At a command prompt, change directory to %TIO_HOME%\tools (Windows) or $TIO_HOME/tools (UNIX).

      3. Run the following command: prepareTCAImage.cmd/.sh [-o ]

      4. Transfer the installation image by using mount or CD/DVD to the remote target computer on which you want to install the common agent and the subagents.

      5. On the target computer, log on as Administrator (Windows) or root (UNIX or Linux), and run install.bat (Windows) or install.sh (UNIX or Linux) to silently install the common agent and all the subagents on the remote computer, by using the image created in step above.

  8. Given a working TPM server, a TPM user with the appropriate roles, and the customer requirements for security and access permissions, create the required users and security groups by using LDAP authentication, assign the users to the appropriate security groups, and assign TPM permissions to security groups so that the users and security groups are defined in the TPM environment.
    With emphasis on performing the following tasks:

    1. Create a user and security group.

      1. Log on to the WebSphere Administrative Console V6.1.

      2. Select Users and Groups, then Manage Users.

      3. Click Create… and specify the relevant information for the desired user ensuring that passwords meet the password rules.

      4. Submit the form to create the user.

      5. Select Users and Groups, then Manage Groups.

      6. Click Create… and specify the relevant information for the desired group.

      7. Submit the form to create the group.

    2. Add a user to a security group.

      1. Log on to the WebSphere Administrative Console V6.1.

      2. Select Users and Groups, then Manage Users.

      3. Search for and select the desired user.

      4. Click the Groups tab.

      5. Search for and select the group to which the user should be added.

    3. Configure user and security group synchronization.

      1. Log on to Tivoli Provisioning Manager.

      2. Click Go To -> System Configuration -> Platform Configuration -> Cron Task Setup.

      3. Type VMMSync into the Cron Task field and press Enter.

      4. Activate the Virtual Member Manager synchronization by clicking the Active check box.

      5. To ensure that you retrieve the user or security name from LDAP correctly, click the Next Page arrow on the Parameters tab and select userMapping.

      6. Change the displayName value in the Value field from the displayName<\column> expression to an appropriate attribute value defined in LDAP, for example, uid as in uid<\column>.

      7. Save the changes.

      8. To view all of the imported objects, restart Tivoli Provisioning Manager.

    4. Assign read/write type of permissions to security groups.

      1. Log on to the TPM User Interface.

      2. Click Go To -> Security -> Security Group.

      3. Select the desired security group.

      4. Click on the Provisioning Permissions tab and click Read/Write Permissions.

      5. Add the appropriate read-only or read/write permission.

      6. Save the changes.

    5. Assign workflow permissions to security groups.

      1. Log on to the TPM User Interface.

      2. Click Go To -> Security -> Security Group.

      3. Select the desired security group.

      4. Click the Provisioning Permissions tab, and click Workflow Permissions

      5. Add the access to a workflow by clicking New Row, and specifying Provisioning Group and Permission Group.

      6. Save the settings.

      7. Enable the workflow permission by clicking Go To -> Security -> Security Group, and choosing the security group for which you want to add workflow permission.

      8. Go to the Data Restrictions tab, and click New Row.

      9. Specify TPACCESSDOMAIN for Object, and QUALIFIED for the Type field. Verify that the Reevaluate box is checked, and choose TPMWKFCOND for the Condition field.

      10. Save the settings.

  9. Given a working TPM server and an available automation package, install or update the automation package so that its contents are available to TPM.
    With emphasis on performing the following tasks:

    1. Save the automation package to %TIO_HOME%\drivers (Windows) or $TIO_HOME/drivers (UNIX/Linux).

    2. Open a command prompt or shell on the TPM server and change directories to %TIO_HOME%\tools (Windows) or $TIO_HOME/tools (UNIX/Linux).

    3. Use the tc-driver-manager.cmd (Windows) or the tc-driver-manager.sh (UNIX/Linux) command to install the driver ensuring not to use the .tcdriver extension when entering the driver name. For example, run "tc-driver-manager.cmd installDriver SPBHandler" command to install SPBHandler.tcdriver driver.

    4. Use the tc-driver-manager.cmd (Windows) or the tc-driver-manager.sh (UNIX/Linux) command to update an existing driver. For example, run "tc-driver-manager.cmd forceInstallDriver SPBHandler" command to update SPBHandler.tcdriver driver.

    5. Verify that the automation package was successfully installed. For example run this command: "tc-driver-manager.cmd getDriverStatus SPBHandler".

  10. Given that TPM if fully installed, determine the type of information customer wants for reporting so that a report can be identified or created to return the desired information.
    With emphasis on performing the following tasks:

    1. Review the information that the customer would like to report on (i.e. compliance information, software deployments, patch deployments, etc.).

    2. Check for Predefined reports available in Report Administration feature: Provisioning Computers, Provisioning Groups compliance, Patch reports, Discovery Configuration, Provisioning Task Tracking, Provisioning Global Settings, Provisioning Workflows, Virtualization Management report).

    3. Determine if reporting of Provisioning Computers is required and add Report to list of reports:

      1. Log on to the TPM Web interface with at least Provisioning Configuration Librarian authorization.

      2. Click Go To -> Administration -> Reporting -> Report Administration.

      3. Search for the report by entering TPSERVERS in the Report Folder column, or by entering tp* in the Report File Name field. (All reports related to Provisioning computers start with tp_).

      4. Locate tp_servers.rptdesign report in the list of reports. Verify that the description is: What computers are in the data model.

      5. Click on the report name.

      6. Click Generate Request page and verify that the command completes successfully.

      7. Click Preview button and on the Request Page select the desired parameters and click Submit.

      8. The Business Intelligent and Reporting Tool (BIRT) Report Viewer page will get displayed with "What computers are in the data model?" report showing the detailed info about all computers in the data model.

      9. Inside the report click on some computer ID link and a different linked report "What are the computer details, including networking and other resource details?" for this particular computer will get displayed.

      10. Click on Export Report icon in the top menu and Export Report page gets displayed.

      11. Select the Export Format from the drop-down menu: ppt, doc, pdf, postscript, xls, and click OK. tp_serverDetails.ppt file gets generated.

    4. If the predefined report does not satisfy your needs, create an ad hoc report. This built-in function in TPM can be used instead of installing and configuring BIRT Report Designer.

      1. Click Go To -> Administration -> Reporting -> Report Administration.

      2. At the top menu, click on Create Report icon.

      3. At the query Based Report page select the style "Summary Report" and enter Report Title.

      4. At Select and Format tabs select desired items.

      5. At Submit tab click Submit button to run the report.

    5. Review Report Developer Guide for in depth tasks such as creating a BIRT reports, importing and exporting report design files, and setting up localized reports.

  11. Given the customer requirements, customize the TPM Web user interface so that it has been customized to meet the customer's requirements.
    With emphasis on performing the following tasks:

    1. Define the list of TPM administrators. All TPM applications can use the Start Center based on Tivoli process automation engine. Other Tivoli software products use the same infrastructure, which include among others Tivoli Application Dependency Discovery, Tivoli Service Request Manager and Tivoli Change and Configuration Management Database.After the installation of TPM, the following new default security groups are added: TPADMIN, TPDEPLOYMENTSPECIALIST, TPCOMPLIANCEANALYST, TPCONFIGURATIONLIBRARIAN, TPDEVELOPER, and TPWEBSERVICEUSER.

    2. Determine what and how to modify the Start Center. A TPM maxadmin administrator has the authority to create new templates that allows modifications to be made to the GUI. However, a user that does not have enough authority can only perform limited changes to its assigned user interface. Users can change what is displayed in the Start Center providing that the user is authorized to do so.

    3. Create Start Center template.

      1. Only a restricted number of administrators can create templates. The maxadmin administrator has the authority to create template. Here are steps used to create a new template: Click on Create New Template.

      2. Provide a name.

      3. In the Portrait Selection window, select how to show the layout, which portlets to display in the left or in the right columns.

      4. Proceed to create the new template. In order to change the layout, click on Change Content/Layout then proceed with the changes and save.

    4. Assign permissions to Security Groups. Once a template has been created, the administrator maxadmin must specify which applications can be accessed from the Start Center template and how permissions can be granted to read, modify or delete objects. Here are the steps necessary to specify which applications can be managed by the newly-created template.

      1. Select Go To -> Security -> Security Groups. Select some group.

      2. From the Security Group window, the Start Center that users will see after a successful login is shown. Here you can change the Start Center Template assigned to the security group.

      3. MAXADMIN security group is Independent of Other Groups, so it can see all start centers.

      4. For the changes to take effect you need to click on Update Start Center, then the new template will show among other start centers.

      5. From the Sites tabs in the Security Group page, new user can be assigned to an existing site.

      6. Also, at Provisioning Permissions tab access can be granted for Delete, Add Read-only, Add Read/Write Permissions and Reset Conditions for DCM Objects.

    5. Create Key Performance Indicators (KPIs). KPIs provide the ability to track critical performance metric over a set period of time. Existing KPI can be duplicated and renamed, which makes it easy to create new KPIs.

      1. Select Go To -> Administration -> Reporting -> KPI Manager.

      2. Select an existing KPI, duplicate an existing one or create a new KPI by defining a select statement for a query by using the following parameters: target level, threshold level for warning and threshold for critical.

      3. Select Go To -> System Configuration -> Platform Configuration -> Cron Task Setup.

      4. Select KPI Cron Task, then select Active and save.

    6. Customize the Start Center for users From any loaded Start Center instance, a user can modify the layout of the portlets by selecting the applications accessible for the group user belongs to. However, a user cannot grant himself/herself additional access to applications and their managed resources.

  12. Given customer requirements and an operational TPM server, create software and security compliance checks so that computer states can be verified and reported.
    With emphasis on performing the following tasks:

    1. Open Provisioning groups (Start Center or Go To menu).

    2. Select desired group or create new group.

    3. Select the Compliance tab.

    4. Security checks.

      1. Select the Security Check tab.

      2. Press the New Security Check button.

      3. Select Patch or Security Check then select desired check(s).

      4. Press Save.

    5. Software checks.

      1. Select the Software Checks tab.

      2. Press the New Software Check button.

      3. Select the Software type check then the desired software check(s).

      4. Press Save.

    6. SOX checks.

      1. Select the SOX Checks tab.

      2. Press the New SOX Check button.

      3. Select the SOX type check then the desired SOX check(s).

      4. Press Save.

    7. Schedule or Run check.

      1. Press the Run button to execute the check immediately.

      2. Press the Schedule button to schedule the check or check and scan.

      3. After the check and scan are completed go to Recommendations tab.

      4. A single remediation dialog appears when the user selects a set of recommendations for implementing them. Click the Implement button for a list of different types of recommendations to apply the remediation.


Section 4: Problem Determination


  1. Given that the IBM Tivoli Provisioning Manager V7.2 (TPM) installation has failed, identify and review the appropriate log and trace files so that the root cause of the installation failure can be identified and remediated.
    With emphasis on performing the following tasks:

    1. If one of TPM's components fails during installation, review the appropriate log files to diagnose the problem.

      1. For a Middleware installation failure, review: $MWI_workspace/hostname/mwi.log, $MWI_workspace/hostname/deploymentPlan/logs/[INSTALL_timestamp]

      2. For a DB2 installation failure, review: $MWI_workspace/hostname/deploymentPlan/MachinePlan_hostname/00003_DB2_9/install/01_BASE/[INSTALL_timestamp]/logs/db2setup.log,

      3. For a WebSphere Application Server failure, review: $MWI_workspace/hostname/deploymentPlan/MachinePlan_hostname/00008_WAS_ND_6.1/install/01BASE/[INSTALL_timestamp]/logs/ and the directory $WAS_HOME/logs/install/

      4. For a Tivoli Directory Server installation failure, review: $MWI_workspace/deploymentPlan/MachinePlan_hostname/00006_ITDS_6.2/install/02_BASE/[INSTALL_timestamp]/logs/ $MWI_workspace/hostname/deploymentPlan/MachinePlan_hostname/00005_ITDS_DB2_CCMDB/logs $MWI_workspace/hostname/deploymentPlan/MachinePlan_hostname/00007_ITDS_Configuration/logs

      5. For a base services installation failure, review: $Maximo_home\logs\CTGInstallMessage[nn].log and $Maximo_home\logs\CTGInstallTrace[nn].log. Run the LogZipper.sh from the $Maximo_home\scripts directory and find the date_time.zip file in the $Maximo_home\debug directory.

      6. For TPM Core Components installation failure, review: $TEMP\tclog_wrapper, $TEMP\tclog.

      7. For TPM Web Components installation failure, review: MAXIMO_HOME\solutions\logs\\

    2. For specific recovery actions for default core components installation failure, review the appropriate log files to diagnose the problem.

      1. For a Cygwin issue on Windows, review: C:\cygwin\var\log\, %TEMP%\tclog_wrapper\downloadCygwinSetup.log, %TEMP%\tclog_wrapper\downloadCygwinRep.log, %TEMP%\tclog_wrapper\instCygwin.log, %TEMP%\tclog_wrapper\cygwin_ssh_config.log, %TEMP%\tclog_wrapper\cygwin_ssh_config.err

      2. For a base services backup issue, review:%TEMP%\tclog_wrapper\MBSBackupB4TPM-stdout.log, %TEMP%\tclog_wrapper\MBSBackupB4TPM-stderr.log

      3. For a DB2 backup issue, review: %TEMP%\tclog_wrapper\DBbackupafterMBS-stdout.log, %TEMP%\tclog_wrapper\DBbackupafterMBS-stderr.log

      4. For a WebSphere Application Server (WAS) backup issue, review: %TEMP%\tclog_wrapper\WASbackupctgDmgr01-afterMBS-stdout.log, %TEMP%\tclog_wrapper\WASbackupctgDmgr01-afterMBS-stderr.log, %TEMP%\tclog_wrapper\WASbackupAppSrv01-afterMBS-stdout.log, %TEMP%\tclog_wrapper\WASbackupAppSrv01-afterMBS-stderr.log

      5. For a WebSphere Application Server (WAS) configuration and Java virtual machine(JVM) setup issue, review: %TEMP%\tclog_wrapper\call_was_config.log, %TEMP%\tclog_wrapper\call_was_config_fips.log

      6. For a TPM engines installation issue, review: %TEMP%\tclog_wrapper\nonUI_install.log, %TEMP%\tclog_wrapper\nonUI_install_err.log, %TEMP%\tclog

      7. For an Agent Manager installation issue, review: %TEMP%\tclog_wrapper\amtrace.log, %TEMP%\tclog_wrapper\amtrace.err, $TCA_HOME/logs, TCA_HOME/toolkit/logs

      8. For issues with the Dynamic Content Delivery (DCD) registration with the common agent, review: %TEMP%\tclog_wrapper\preparePingAM.log, %TEMP%\tclog_wrapper\preparePingAM.err, %TEMP%\tclog_wrapper\call_pingam.log, %TEMP%\tclog_wrapper\call_pingam_err.log

      9. For issues with the DCD SSL configuration, review: %TEMP%\tclog_wrapper\config_ssl.log, %TEMP%\tclog_wrapper\config_ssl.err, %TEMP%\tclog_wrapper\soap-sslconfig.log, %TEMP%\tclog_wrapper\soap-sslconfig.err

      10. For issues with the DCD installation, review: %TEMP%\tclog_wrapper\getAMPass4CDS.log, %TEMP%\tclog_wrapper\getAMPass4CDS.err, %TEMP%\tclog_wrapper\CDSinstall-stdout.log, %TEMP%\tclog_wrapper\CDSinstall-stderr.log, DCD_HOME\log

      11. For DMS installation issues, review: %TEMP%\tclog_wrapper\dmsinstalltrace.log, %TEMP%\tclog_wrapper\dmsinstalltrace.err

      12. For DMS configuration issues, review %TEMP%\tclog_wrapper\dmsconfigtrace.log, %TEMP%\tclog_wrapper\dmsconfigtrace.err, DMS_HOME\logs\dms_config_trace.log, DMS_HOME\logs\dms_config.log

      13. For DMS SSL configuration issues, review: %TEMP%\tclog_wrapper\dms_getpass.log, %TEMP%\tclog_wrapper\dms_getpass_err.log

      14. For TPM for OS deployment installation issues, review: %TEMP%\tclog_wrapper\tpmfosd.log, %TEMP%\tclog_wrapper\tpmfosd.err, %TEMP%\tclog_wrapper\call_importXML4OSD.log, %TEMP%\tclog_wrapper\call_importXML4OSD.err

      15. For issues with restarting a local DB2, review: %TEMP%\tclog_wrapper\call_db2_restart.log, %TEMP%\tclog_wrapper\call_db2_restart.err

      16. For database backup issues, review: %TEMP%\tclog_wrapper\DBbackupafterTPMCore-stdout.log, %TEMP%\tclog_wrapper\DBbackupafterTPMCore-stderr.log

      17. For WAS backup issues, review: %TEMP%\tclog_wrapper\WASbackupctgDmgr01-afterTPMCore-stdout.log, %TEMP%\tclog_wrapper\WASbackupctgDmgr01-afterTPMCore-stderr.log, %TEMP%\tclog_wrapper\WASbackupAppSrv01-afterTPMCore-stdout.log, %TEMP%\tclog_wrapper\WASbackupAppSrv01-afterTPMCore-stderr.log,

      18. For Process Solutions Installer (PSI) issues, review: %TEMP%\tclog_wrapper\psi_tpm.log, MAXIMO_HOME\solutions\logs\TPM_PMP

    3. For a specific failure, after diagnosis in the appropriate log file, take recovery actions.

      1. Resolve the cause of the problem.

      2. Restore the database.

      3. Restore WebSphere Application Server.

      4. Restore base services backup and deployment engine database backup from after the base services installation.

      5. Try again.

  2. Given an operational TPM environment, troubleshoot target system problems so that the root cause of a problem can be determined.
    With emphasis on performing the following tasks:

    1. Troubleshoot the Tivoli Common Agent (TCA).

      1. Check the Workflow logs for errors during installation.

      2. Check the /runtime/agent/logs/install directory for agent installation errors.

      3. Check the nonstop.log for the availability of the TCA watchdog process.

      4. Check the error-log-*.xml and trace-log-*.xml for TCA related errors.

      5. Use netstat -an |grep 9510 to check for LISTEN status on port 9510.

      6. Use the $TIO_HOME/ISALite/ISALite/runISALite.sh to gather the TCA endpoint logs. From the Problem Type list, click Target Computer Problem. Enter the maxadmin credentials and object ID of the target computer for which you want to collect log files. The resulting logs package will be stored under the $TIO_LOGS location.

      7. From TPM, use the TCA_PingAgent workflow to verify that the TCA is running and operational.

      8. Use the TCA_Collect_Logs workflow to gather the endpoint logs and store them under $TIO_LOGS/tivolicommonagent/.

      9. To manually gather the logs from a failed TCA target, use the runtime/agent/toolkit/bin/service.sh

    2. Troubleshoot deployment engine (DE)_operations.

      1. Verify the requirements for Remote Execution and Access on the target systems are met.

      2. Check the Workflow logs during DE operations for errors.

      3. Check the target system for the logs or scripts which were copied through workflow execution.

      4. Check the $TIO_LOGS/console.log for errors.

  3. Given the need to troubleshoot authentication and communication errors, locate the appropriate log files so that the root cause can be determined.
    With emphasis on performing the following tasks:

    1. Troubleshoot DE common errors.

      1. All DE run time results are logged to the TIO_LOGS\console.log file. If user is looking for additional details to help determine why a particular provisioning workflow has failed, review this log file first.

      2. Log files for tcdriver packages are stored in the TIO_LOGS\tcdrivermanager.log.

      3. Enable the debug mode in two places:-The log4j.prop file in the TIO_HOME\config directory should have lines that read:log4j.appender.errorfile.threshold=debuglog4j.appender.consolefile.threshold=debug log4j.rootCategory=DEBUG, consolefile, errorfile-To log commands issued by the DE, enable full debug mode:Click Go To -> Administration -> Provisioning -> Provisioning Global Settings.Click the Variables tab.Click Edit -> Add Variable.Name the variable debug in the Key field, with a component of DE, and a value of true.-Restart the TPM server.

    2. Troubleshoot Microsoft Active Directory authentications.

      1. Ensure that the computer meets the hardware and software requirements for Microsoft Active Directory on Windows 2003 or Windows 2008. Microsoft Active Directory must be installed on a separate computer.-The latest Windows 2003 or Windows 2008 service pack is installed.-The primary network card has a static IP address. This setting is required for the DNS and Active Directory subsystems.-Click Start -> Control Panel -> Network Connections.-Right-click the connection that represents the primary network adapter and click Properties.-Select Internet Protocol (TCP/IP) and click Properties.-Ensure that use the following IP address is selected and enter the IP address and subnet mask for the server. Add a gateway if required.-Enter the IP address of the server in the Preferred DNS server field.-Install and configure DNS. If it is not currently installed, perform the following steps:-In the Windows Control Panel, double-click Add or Remove Programs and then click Add/Remove Windows Components.-Click Networking Services in the list of components, but do not select the check box if it was not already selected. Click Details and select the Domain Name System check box.-Click OK and then Next and complete the installation of DNS.

    3. Troubleshoot Tivoli Directory Server authentication.

      1. Check the \logs directory. These logs files can be reviewed by using either the Web Administration Tool or the system command line. Check the following log files for errors: -ibmdiradm.log: The administration daemon error log. View status and errors encountered by the administrative daemon.-adminaudit.log: The administration daemon audit log. Use the records in the log to check for suspicious patterns of activity in an attempt to detect security violations. -audit.log: Audit logging is used to improve the security of the directory server.-bulkload.log: The bulkload log allows user to view status and errors related to bulkload.-idstools.log: The configuration tools log contains status and error messages related to the configuration tools.-db2cli.log: This log records database errors that occur as a result of LDAP operations.-lostandfound.log: This log archives entries that were replaced due to replication and conflict resolution. The log allows user to recover the data in the replaced entries, if necessary.-ibmslapd.log: The server error log contains status and error messages related to the server. This is the most important log.

  4. Given an operational TPM server where a workflow has been run, navigate to the workflow execution history page so that the workflow execution history can be reviewed.
    With emphasis on performing the following tasks:

    1. Log in to TPM.

    2. Click Go To -> Administration -> Provisioning -> Provisioning Workflow Status.

    3. Click the deployments request ID for the workflow that user wants to review.

    4. Click the Status Detail Menu and read the error message.

    5. Interpret the workflow log details.

      1. The entire first line tagged with deployment-request has a majority of the information, however, there are 5 critical points to review:-This will give us the unique deployment-request number (####) of the workflow operation which can later be correlated against our $TIO_LOGS\console.log.-This will also give us the error-details string which will be a complete error stack that we can use to trace the stack exception. -Review any meaningful solution which is given in the string error-message. This can also be a good starting point for troubleshooting purposes.-At the end of this line will be the error-code which gives us a TPM specific error code, usually of the form ABCDEF###E. For example, COPDEX040E or COPCOM123E or COPINF029E. -The status code at the end of the line will be of interest and can indicate "failed" or "success" or "in-progress". It is good to keep this in mind when reviewing the workflow execution.

      2. Search the text of the workflow log you will want to find the actual line on which the error occurred. Usually a workflow will be a series of steps which are all completed successfully, then the error occurs and a message is printed in the workflowLog, and then the workflow code has to 'wrap-up' and complete. Therefore the error is not necessarily at the end of the XML file but usually somewhere in the latter 2/3rds. Compare the workflow log output against the source workflow code to understand what steps were completed and where the failure occurred.

      3. Review the workflowLog to see what actions the workflow was taking before and after the text "Failed workflow".

  5. Given a failed depot, perform diagnostic steps so that the depot problem has been identified.
    With emphasis on performing the following tasks:

    1. Check if the depot is active from the TPM DCD configuration page or the DCD Management Console :

      1. Telnet into port 2100 on the Depot Server. Example: telnet linclient.tivoli.edu 2100

      2. Type "syst" once the connection has been established to retrieve system information.User can get a response similar to this example:-Connected to linclient.tivoli.edu (192.168.94.101). -Escape character is '^]'.-syst-DS:linclient.tivoli.edu=2.1.0.1(20090730D2) MC=tpm.tivoli.edu:9046 CONN=0 OS=Linux ARCH=x86_32

      3. Stop and start the agent to see if the port 2100 becomes active.

      4. Verify the fqdn of the Depot Server matches the TPM computer object defined in the DCM.

    2. To enable logging and tracing on the TPM Management Center:

      1. Set the server.logger.message.logging property to true in the cdslog.properties file on the management center.

      2. Set the log levels by editing the server.logger.level entry and setting it to any of the following:-ERROR Only error messages are logged. No tracing is logged.-WARN Only warning and error messages are logged. No tracing is logged.-INFO All messages (informational, warning and error) are logged. No tracing is logged.-DEBUG_MIN All messages are logged. Minimal tracing information is logged.-DEBUG_MID All messages are logged. Moderate tracing information is logged.-DEBUG_MAX All messages are logged. All tracing information is logged.

    3. Look for suspicious entries in log files located in /usr/ibm/tivoli/common/ctgde/logs on the TPM management center server.

    4. Look for the following items in the depot logs, /opt/tivoli/ep/logs/trace-log*.xml and error-log*.xml:

      1. grep for addFile entries to see if a file got published.

      2. grep for SPBDistribute to confirm that a file copy job was received:-

      3. Check the trace file to confirm that the file was copied. For example:

  6. Given an operational TPM server, supported browser and compatible Java version, launch the Java Web Start Software Package Editor (SPE) and troubleshoot any problems so that the Java Web Start SPE is available for building packages.
    With emphasis on performing the following tasks:

    1. Set the following environment variables. LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/.speWebStart/swd_cli/binTISDIR=$HOME/.speWebStart/swd_cli/codesetNLSPATH=$HOME/.speWebStart/swd_cli/msg_cat/C/spcatalog.cat

    2. Connect to https://tpm.hostname.com:9443/SPEWebStart/spe.jnlp by using a supported browser.

    3. When prompted, associate the jnlp extension with the correct javaws binary.

    4. Once the Software Package Editor launched, click Settings -> Preferences and enter the information to connect to the TPM server.

    5. Troubleshoot SPE Web Start launch and connectivity by confirming the following:

      1. TPM is running.

      2. The correct version of Java has been installed.

      3. The browser is supported by TPM.

      4. The environment variables have been set properly.

      5. The URL for downloading the Web Start version of SPE is correct.

      6. The correct version of javaws is used.

      7. Pop-up windows are allowed.

      8. The connectivity settings in Settings -> Preferences are correct.


Section 5: Administration


  1. Given customer requirements and an operational IBM Tivoli Provisioning Manager V7.2.0.2 (TPM) server, create discovery configurations to populate the DCM so that the discovery data is inserted into the DCM.
    With emphasis on performing the following tasks:

    1. Define discovery configurations (servers, routers, switches, etc).

      1. Go To Discovery -> Discovery Configurations -> Provisioning Discovery and click on Discovery Configurations.

      2. Press the New Discovery Configuration button.

      3. Provide a Name and Description, category Hardware Discovery, and then select "Discover Devices (computers, switches routers) by using SNMP" (if computers have SNMP enabled) or "Discover Computers by using Remote Execution and Access " for non-SNMP enabled computers for the desired method.

      4. Specify the Hostname, IP Address Ranges and/or subnetworks to scan.

      5. Specify the credentials and protocols to use.

      6. Specify response timeouts.

      7. Press Save button.

    2. Discover devices in the infrastructure.

      1. Go To Discovery -> Discovery Configurations -> Provisioning Discovery and click on Discovery Configurations.

      2. Press Enter to list all Discovery Configurations or use the filters to limit the list.

      3. Click on the desired Discovery Configuration.

      4. Click the Run Discovery button.

      5. If desired, modify the Provisioning Task name.

      6. Press Submit.

    3. Perform Inventory Discovery.

      1. Go To Discovery -> Discovery Configurations -> Provisioning Discovery and click on Discovery Configurations.

      2. Select the TPM Inventory Discovery.

      3. Define the scope for hardware and software as necessary.

      4. Click the Run Discovery button.

      5. If desired, modify the Provisioning Task name.

      6. Select the desired targets.

      7. Press Submit.

    4. Create Custom Inventory Discoveries.

      1. Gather customer requirements.

      2. On the TPM server. -Create Custom table in the data model.-Create pre and/or post scripts for the target computer.-Create properties file for the inventory extension.

      3. On the target computers. -Create the output files for the inventory extension data.

  2. Given an operational Tivoli Provisioning Management server, provision virtual instances or machines so that the virtual instance or machine is properly configured and operational.
    With emphasis on performing the following tasks:

    1. Define virtualization basic concepts. Virtualization is a software technology that allows virtual machines to be provisioned on a powerful physical computer that provides hosting capabilities. This hosting machine is registered in the DCM as a host platform server. Virtual machines are created by using a virtual server template. This template allocates the hardware resources required for the virtual machine to properly operate.Once a virtual machine is created, some resources are permanently allocated to the virtual machine. When a virtual machine is deleted, then the resources go back to the available pool or resources.

    2. Set up a VMware ESX environment.TPMfOSD is used to install a form of physical servers ESX servers. Once this is done, the Virtual Center must be installed on a separate computer. Each Secure Sockets Layer (SSL) Certificate will have to be imported by TPM so that TPM can use HTTPS protocol to connect to the VI 3 Virtual Center or ESX servers directly. Then Service Access Points will have to be defined for the discoveries to work.

    3. Manage virtualization with VMware ESX. TPM will be able to discover existing VMware machine by performing a VMware Infrastructure 3 Virtual Center discovery. Then, TPM will be able to fully manage existing virtual machines.

    4. Create a VMware Virtual server. Using TPM, VMware Virtual Machines can be provisioned as required as long as resources are available in the pool of resources.

    5. Manage virtualization with VMware ESX. A virtual machine can be rebooted. Extra resources can be allocated but in some cases the VMware virtual machine has to be restarted for some changes to be taken into account.

    6. Manage virtualization with AIX LPARs. Using LPARs allows a virtual machine full use of the provisioned hardware. An AIX OS is installed, configured and running in each LPARs. To setup a new AIX LPAR Virtual Machine:

      1. Add the Hardware Management Console (HMC) to the provisioning data model.

      2. Define SSH and System Control Process credentials on the HMC. RSA credentials require the public key of the user tioadmin.

      3. Run an HMC Discovery to identify any existing LPARs and associated resources.

      4. Add hardware resources and credentials to the virtual server.

    7. Manage virtualization with AIX WPARS. A virtualized OS environment can be created within a single AIX 6.1 image. To setup a new AIX WPAR Virtual Machine:

      1. Perform an HMC Discovery.

      2. Define SSH and SCP credentials on the HMC.

      3. Run an HMC Discovery.

      4. Add hardware resources and credentials to the virtual server.

  3. Given customer requirements and an operational TPM server, manage the catalogue of images so that master images, saved images and instance images can be administered.
    With emphasis on performing the following tasks:

    1. The Image Repository application contains details about the repositories where images are kept, and also provides a view of the contents of these repositories. An image repository can contain master images, saved images, instance images, or any combination of these three types. The following types of image repositories are supported: VMware, KVM, PowerVM™, and VMControl repositories. The image repository is the managed system where master images are physically located. For example, VMware Virtual Center data store is an image repository that contains VMware master images.

      1. Create image repositories so that you can create master images, instance images, and saved images.

      2. Manually creating an image repository is only required for PowerVM™ and KVM.

      3. For VMware, the image repository is created when you run the VMware Virtual Center Discovery. The information discovered from the data stores in the Virtual Center populates the image repository. Similarly for VMControl, the image repository is created during the discovery process.

      4. For a KVM file-based boot server, the image repository is automatically created when you install the boot server. This image repository is only master images enabled by default. If you need to create an image repository which is saved images enabled or instance images enabled, you must create it manually.

      5. To manually create a PowerVM or KVM image repository, complete these steps:-Click Go To -> IT Infrastructure -> Image Library -> Image Repositories.-From the Select Action menu, select PowerVM or KVM as the type of image repository that you want to create.-Type a name for the Repository. You can also add a Description.-*Optional Type a value for the Available Space and Total Space. These values represent the deallocated space and total space on the image repository.-Select which type of image you want to save in this repository. If you want to save all types of images, select all of the check boxes:-Master Images Enabled- Saved Images Enabled-Instance Images EnabledIf you do not select all of the image types, only the image type that you enable can be added to the image repository. When you create an image, the repository options are filtered by the type of images that you have enabled.-Click Submit to save your changes and create the image repository.-From the List tab, select the repository that you created.-On the Repository tab, click New Repository Location.-Click Select Value and select the computer, or (only for PowerVM repository) the managed system ID of the NIM boot server, where the images will be physically located. Click OK.-For KVM, VMFS, and VMControl image repositories, a section called Mount Points is present. PowerVM does not use mount points. The mount point is the association between the repository and the host platform server. The location can be on any accessible remote managed system that can store the virtual files. The mount points for VMFS are automatically configured by the VMware Virtual Center Discovery. The mount point for VMControl is also automatically configured by its discovery process. For file-based KVM boot server, the mount point is automatically associated to the image repository with the file-based boot server. For KVM-OVF and the KVM image repository that is manually created, the mount point must be manually configured. Click New Mount Point.-In the Mount Point field, type the path to the mount point. The path value is the path to the managed system from your local computer.-Note: Ensure that you specify a different directory from where your KVM virtual servers are created. Sharing a directory structure for virtual servers and master images is not supported.

      6. Synchronizing the image library. The image library and the images in the repository of the virtualization technology must be synchronized so that the images can be used in the provisioning server. The synchronization updates the image library with any new master images in the image repository. Master images can only be used if they are entries in the image library, so synchronizing periodically is a best practice to follow. Only master images are synchronized against the existing content of the image library. Saved images and instance images are created by using the provisioning server, so they are added to the image repository when they are created.-Click Go To -> IT Infrastructure -> Image Library -> Image Repositories.-Click an image repository.-On the Repository tab, click Synchronize Repository.

      7. After you synchronize to add master images as entries in the image library, you can review the image information about the Master Image tab for each image.

      8. If master images are discovered, a virtual server template might not be associated to the image. This is the case for pSeries® master images that are discovered by the IBM AIX NIM Discovery that runs when you click Synchronize Repository. Add a virtual server template to the master image if it does not have one.-From the Master Images application, select the master image.-On the Master Image tab, beside Virtual Server Template, click Lookup button -> Select Value.-Select the virtual server template that you want to add to the master image.-Important: Virtual server templates that are manually associated to a master image that is discovered are deleted if the master image record is deleted. Create a duplicate of the virtual server template before you associate the template to the master image. To duplicate the virtual server template, click Go To -> IT Infrastructure -> Provisioning Inventory -> Virtual Server Templates. Select the virtual server template from the list. From the Select Action menu, click Duplicate Virtual Server Template. When the template has been duplicated, return to the Master Images application and associate the virtual server template to the master image.

    2. Image Types.

      1. Master images are used to provision computers and virtual servers. The images contain hardware and software resources. You can create many versions of a master image and deploy the images on multiple computers. Each time you deploy an image, an instance image is created. The instance image represents the computer that has been created and its relationship with the master image that was used to create it. Master images can be simple or composite. A composite image contains several member master images. When you deploy a composite master image, one virtual server is created for each member master image contained in the composite.

      2. A composite image is a set of images captured from two or more computers, in cases where you would like to deal with the set as a logical single entity. Typically, the set of computers would collectively provide an application service: for example, a WebSphere® Application Server with a deployed J2EE application on one computer, that uses a DB2® database installed on a second computer.-Composite images are treated as a single entity for the following image management operations: Capturing master images Deploying an instance of a master image Capturing a version of a deployed master image instance Publishing master images

      3. Saved images are backups of various states of your virtual server. Use saved images to replace an existing virtual server, or to restore a deleted virtual server. The Saved Images application is only applicable for virtual server. Saved images can also be thought of as image backups. When you restore a saved image, it re-creates a virtual server. Create the virtual server on the host platform server that hosted the original virtual server, or choose a different host platform server.

  4. Given customer requirements and an operational TPM server, create and execute workflows so that automation can be written to update/query the DCM and perform actions within the TPM environment.
    With emphasis on performing the following tasks:

    1. Install the Automation Package Developer Environment (APDE) environment manually (by using DB2).

      1. Check Hardware and Operating system requirements.

      2. Download and install Eclipse V3.2.2 or V3.6.

      3. Create a directory for APDE in any drive. (for e.g. C:\APDE or /opt/APDE) This will be APDE_HOME.

      4. Unzip Eclipse SDK into APDE_HOME.

      5. Unzip the apde.zip (or apde_3.6.zip) file, which is located in TIO_HOME/apde/ to APDE_HOME (will create the directory "eclipse").

      6. Create a directory named config and another named logs, both in APDE_HOME.

      7. Copy the log4j.prop, dcm.xml and crypto.xml files from the TPM server under TIO_HOME/config dir to the config directory created in 5.4.1.6.

      8. Copy the JDBC Type 4 jar files db2jcc.jar and db2jcc_license_cu.jar to APDE_HOME/config. The .jar files are available in the DB2_HOME\java directory, on the TPM or DB2 server.

      9. Modify APDE_HOME\eclipse\eclipse.ini to look like this:-vmargs-Xms40m-Xmx1024m-Dbusinessobjects.home= APDE_HOME/plugins/tpm_pmp/maximoLibs/businessobjects.jar-Dkanaha.config=file:APDE_HOME/config-Dmaximodbaccess=true-Dlog4j.configuration=file:APDE_HOME/config/log4j.prop-Dkanaha.logs=APDE_HOME/logs-Dstart.tpm.engines=false-Dtrace=y-Dtio.home.unix=/cygdrive/C/PROGRA~1/IBM/tivoli/tpm-Dtio.home=C:/PROGRA~1/IBM/tivoli/tpm

      10. Open the dcm.xml file. In the element, change the path of the .jar files to the location where they are stored in the local Eclipse installation. A forward slash must be used.

      11. Install IBM Java Runtime Environment V1.5 (JRE).

      12. Set a system environment variable JAVA_HOME to the path of the directory where JRE is installed. e.g C:\Program Files\Java\jre1.5.0_05-Edit the system path variable to include the path of the "bin" directory where JRE is installed.-In JAVA_HOME\lib\security add the following permission to the java.policy file:grant {permission java.security.AllPermission;};

      13. Copy the following files from TIO_HOME\lwi\runtime\tpm\eclipse\plugins to APDE_HOME\eclipse\plugins. tpm_pmp/*/TC-INF/*/wkfclasses/*/workflow/

      14. Copy the following files from TIO_HOME\config to your APDE_HOME\config directory:-algorithmSetting.xml-crypto.xml-dcm.xml-deploymentengine.xml-fipsSetting.xml-Locales.properties-log4j.prop-trace_globalization.properties-user-factory.xml-tcdrivermanager.xml

      15. Edit the deploymentengine.xml file and replace the tpm-bundle-home with your APDE_HOME.APDE_HOME

      16. Copy pe.jar and deploymentengine_1.0.jar from the TPM server at TIO_HOME/eclipse/plugins to APDE_HOME/eclipse/plugins.

      17. From the TPM server, copy %TIO_HOME%\lwi\runtime\tpm\eclipse\plugins\tpm_pmp\properties\maximo.properties to APDE_HOME\eclipse\plugins\tpm_pmp\properties\maximo.properties

      18. Modify the maximo.properties as given below:mxe.rmi.port=0mxe.crontask.donotrun=ALLmxe.report.birt.disablequeuemanager=1mxe.db.driver=com.ibm.db2.jcc.DB2Drivermxe.db.schemaowner=maximomxe.name=MXServermxe.db.url=jdbc:db2://:50005/MAXDB71mxe.registry.port=13400mxe.db.user=maximomxe.encrypted=falsemxe.db.password=

      19. Also there may be garbage text at the end of the file, remove it if it exists.

      20. From the command prompt change directory to APDE_HOME\eclipse and run to start eclipse:eclipse -clean -debug -console -consolelog

      21. Go to Windows ->Preferences.-Click Automation Package (Displaying the tree under Automation Packages may take some time).-In the Automation Package tree, click Database.-In the Database configuration panel, click Import.-Browse to the directory where the dcm.xml is copied. i.e. APDE_HOME/config.-Click OK.-In the Automation Package tree, click Encryption.-In the Encryption configuration panel, click import.-Browse to the directory where the crypto.xml is copied. i.e. APDE_HOME/config.-Click OK.-Click Apply. Eclipse will be restarted.

    2. Install the APDE environment automatically (by using a shell script).

      1. The Configure_APDE.sh script is present in the %TIO_HOME%\apde directory. Run the script from the provisioning server by using the following parameters. Use Cygwin if the provisioning server runs on Windows.

      2. Replaces steps 6-10 and 13-19 detailed aboveConfigure_APDE.sh <"APDE_install_location"> <3.2.2|3.6> "[ECLIPSE_PATH]" "[JRE_PATH]"where:-lin|win: Specifies the operating system. Use win for Windows and lin for Linux.-APDE_installation_location: Specifies the path where you want to install APDE on the remote target. Please enclose the path in quotation marks.-MACHINE_NAME: Specifies the IP address or host name of the remote target computer. Set it to none if the transfer to the target must be ignored.-USER_NAME: Specifies the user name of the remote target. Set it to none if the installation on the target must be ignored.-3.2.2|3.6: The Eclipse version to be used for APDE.-ECLIPSE_PATH: Specifies the full path and file name of the Eclipse bundle (a .zip or a .tar file). It must contain the folder eclipse. Set it to none if Eclipse is already configured.-JRE_PATH: Specifies the full path and file name of the JRE bundle (a .zip or a .tar file). It must contain the java/bin folder. Set it to none if IBM® Java 1.5 is installed and configured.

    3. Write provisioning workflows.

      1. Start the APDE.

      2. Start a new project.

      3. Right click on workflow and select New -> Workflow.

      4. Write, Debug and Save the workflow in the Workflow window.

      5. Use the Execution Results and Problems windows to debug workflows.

      6. Use the Queries window to assist in the creation of DCM query statements.

      7. Use existing workflows as templates to determine syntax and data sources.

      8. Use TIO_HOME\xml\DcmObjectMappingsDocument.xml for reference.

    4. Query the DCM.

      1. Use the DCMQuery function to access data within the DCM.

      2. Build queries by using the auto-completion keystrokes CTRL+Space.

    5. Launching SOAP Command Line Interface (CLI) commands.

      1. Use the command soapcli to execute workflows.

  5. Given that TPM environment is set up and running, create software packages so that they can be used to distribute and install software on targets.
    With emphasis on performing the following tasks:

    1. Determine what software is to be packaged and how to use the Software Package Editor (SPE) to perform packaging. There are multiple ways to build a software package. The Packager will have to decide how to build a specific software package. For example, the Packager may decide to embed a Microsoft MSI file or a Linux RPM file instead of performing the installation by launching an installation program with a proper response file.

    2. Launch the SPE. The SPE is usually launched on a machine that is primarily dedicated to packaging. It is generally referred to as a software package preparation workstation. The SPE can be easily launched by using any supported Web Browser. By using the SPE Selector, the packager will select the type of packages to build. In most cases, selecting General Package will provide all the flexibility required. The SPE is compatible with the one provided with ITCM V4.3.1 or V4.2.3 including the latest versions of the fix pack.

    3. Load a software package template. In order to save time and to ensure consistency when building software packages, it is recommended to always start by loading a template. Because there are so many options, it becomes easy to forget to set important options.

    4. Provide a name and a version. Properly naming a software package is a critical task. Because Change Management Control is based on the full name of the software package. The software package's name is composed of two distinct parts. First there is the package name and second there is the version number which starts after the first separating "dot". By default, Change Management Control prevents an older software package from being installed over a newer version. Change Management Control first compares the package name. If it is the same, it then compares each and every level of the version. In the end, there will be three different cases, if the software package to install is newer, then the installation will go ahead. If it is older, the installation will be cancelled by condition. If it is equal, then only a Force option will reinstall the software package.Before going any further, this early version of the software package should be saved ensuring that the full name is reserved.

    5. Insert Actions in a software package.A software package contains a number of actions that are executed in a specific order at installation time. In a Software Package Definition (SPD) file, each action corresponds to a Stanza and each Stanza includes parameters. Whatever possible installation parameters should use variables and should never be hard coded. As an example, if user needs to install a particular drive and directory, define a variable that says Install_Dir and set to D:\MyDirectory.

    6. Add variables to customize a software installationExplain how variables can be passed from TPM into a software package block (SPB) by using a software resource template to customize a software installation.

    7. System actions These are actions that will be carried out on targets when the package is deployed. Here are some examples of System actions:-Check for available disk space just prior to the installation.-Restart the target system (equivalent of rebooting).-Define a software signature for a positive identification that the software package was installed.Reboots are tied to specific Change Management operations. Therefore, it is possible to specify that a reboot is required after the installation of a software package but is not required when the same package is uninstalled. Software packages that include reboots have to be handled very carefully at deployment time.

    8. Add/Remove actions These types of actions will add or remove objects on the target. Examples could be directory creation, a file removal, a UNIX symbolic link, an icon added on the desktop, an entry in the Start menu, a Windows service added, creation of a registry key.

    9. Program Execution action.These actions will initiate any kind of programs at deployment time. They include, Microsoft MSI, Linux RPM Package Manager, AIX Install, Solaris pkgadd. Return codes generated by the embedded program can be defined and interpreted by TPM to ensure a smooth transition to the next action.

    10. Save the software package.A software package can be saved in three different formats, each having its own use. The most common one and useful one is the SPB. An SPB is a single compressed file that includes everything required to install a software package. It contains the actions to perform a complete installation as well as all the files required. The second most useful one is the SPD file. This is an ASCII file that contains all Stanzas and Objects. An SPD file can be reviewed when the package does not do what it was intended for. The third format is SP and is not used by TPM.

    11. Test the software package. Every Packager must test its own software package by performing Change Management operations by using specially provided disconnected commands. They are called disconnected commands because they can be used on a stand-alone workstation and because Change Management operations are not tracked in the DCM.

  6. Given that TPM is installed: describe the start order of the TPM components so that the understanding of the start order has been demonstrated.
    With emphasis on performing the following tasks:

    1. Describe the start of the TPM server by listing the following services in order:

      1. DB2

      2. Directory Server

      3. HTTP server

      4. Web Application Server

      5. TPM Engines

  7. Given customer requirements and an operational TPM server, export and import XML files within the TPM environment so that data within the DCM can easily be managed through command line tools.
    With emphasis on performing the following tasks:

    1. Export objects by using TIO_HOME\tools\dcmexport.(sh|cmd).

      1. Use the dcmexport command to extract data from the DCM into an XML file.

      2. Use exported data for obtaining information about specific objects to be used with workflows, dcmQueryCommand or xmlimport.

    2. Import objects by using TIO_HOME\tools\xmlimport.(sh|cmd).

      1. Use the xmlimport command to insert data in XMl format into the DCM.

      2. Must adhere to the xmlimport.dtd file.

      3. Imported data can allow for mass imports of objects.

    3. Export compliance checks by using TIO_HOME\tools\ccexport.(sh|cmd)

      1. Use the ccexport command to extract compliance checks into an XML file

      2. Explain difference between using ccexport and dcmexport for exporting compliance checks.

    4. Import compliance checks by using TIO_HOME\tools\ccimport.(sh|cmd)

      1. Use the ccimport command to insert compliance checks in XML format into the DCM

      2. Explain difference between using ccimport and dcmimport for importing compliance checks.

      3. Explain how to use ccimport to import a compliance check from a dcmexport

    5. Import software signature by using TIO_HOME\tools\importSoftwareSignature.(sh|cmd)

      1. Use importSoftwareSignature command to import software signatures

      2. Use importSoftwareSignature to refresh signature caching files

    6. Import software signature by using TIO_HOME\tools\importSignatureAssociation.(sh|cmd)

      1. Describe the 2 use cases for the command: -Associate an existing software signature to an existing software module.-Associate a new software signature to an existing software module.

  8. Given a non-compliant computer, perform steps to remedy the problems so that user can have a compliant computer.
    With emphasis on performing the following tasks:

    1. In the Start Center, click Provisioning Groups or Provisioning Computers.

    2. Select the provisioning group or provisioning computer for which user has run compliance checks, then click the Recommendations tab.

    3. Select the check box for each recommendation and click Approve.

    4. Select the check box for each approved recommendation that needs to be fixed and click the Run button to perform the fixes.

    5. Monitor the remediation task and verify that it was completed successfully.

    6. Navigate to the Compliance tab for the group or computer and click Run -> Scan and check.

    7. Confirm that the group or computer is now compliant.

  9. Given customer requirements and an operational TPM server, identify and describe TPM components used for deployments and show an understanding of their tuning parameters so that an understanding of the TPM components used to perform automation has been defined.
    With emphasis on performing the following tasks:

    1. scalable distribution infrastructure (SDI) Infrastructure Components

      1. Asynchronous deployment method

      2. Limited use of workflows

      3. Automates operations on large and small sets of computers

      4. Describe components that make up SDI-DCD - Dynamic Content Delivery Service-Management Center-Depot-Client Subagent-DMS - Device Management Service-Device Manager Federator-Device Manager Results Server-Device Manager Federated Agent-Device Manager Subagent (JES)

      5. Describe configuration items for DCD-Region-Zone-Depot Server-Peering

      6. Describe scenarios that leverage SDI-SPB distribution and installation-Patch Management-Inventory Scan

      7. Performance tuning-JES Polling Interval-Device manager federated polling interval-DCD Client and Depot Cache Size-Bandwidth Control-Minimize Traffic, Block incoming requests, Block outgoing requests.-Use local IP address for peering-Task concurrency level

    2. deployment engine

      1. Synchronous deployment method

      2. Automates operations on smaller sets of computers.

      3. Performance tuning.-Task concurrency level



Promotions


Connect with Us