1. IBM Software Group © 2009 IBM Corporation IBM Tivoli Provisioning Manager 7.1.1 Compliance Check Import/Export Tool

2. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 Topics  Feature Objective (Problems Solved)  Feature Overview  Common Use Cases

3. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Tool Objective  Provides command line tools to import and export compliance checks. -Moving the compliance checks from the development environment to the production environment. -Append/update compliance checks to a new target -Export and import a subset of the compliance checks

4. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 Topics  Feature Objective (Problems Solved)  Feature Overview  Common Use Cases

5. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Tool Overview  Compliance Check Export Tool: ccexport -f [-c computerList.txt ] [-g groupList.txt ]  Compliance Check Import Tool: ccimport -f [-p importCfg.properties]  Tools’ location: - windows: %TIO_HOME%\tools - unix: $TIO_HOME/tools

6. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 Topics  Feature Objective (Problems Solved)  Feature Overview  Common Use Cases

7. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Use Case 1  Export Compliance Checks for selected computers and/or groups from DCM - TPM Administrator exports compliance checks for the selected targets (computers and/or groups) using the command line as the following: ccexport -f myCompChecksOutput.xml -c compList.txt -g groupList.txt Where input files “compList.txt” and “groupList.txt” contain the list of the computer or group names to be export. (Note: “ccexport” stands for compliance checks export) - An XML output is created and it includes all compliance checks for the selected targets. (e.g. myCompChecksOutput.xml). From the command line, a message is displayed and indicated that the command has been successfully run.

8. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Use Case 2  Export Compliance Checks for all computers and groups from DCM - TPM Administrator exports all compliance checks without specifying any targets using the command line as the following: ccexport -f myCompChecksOutput.xml -An XML output is created and it includes the compliance checks stored on all targets (computers and groups) from DCM. (e.g. myCompChecksOutput.xml). -From the command line, a message is displayed and indicated that the command has been successfully run.

9. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Use Case 3  Import all Compliance Checks into DCM - TPM Administrator imports all compliance checks without specifying any targets using the command line as the following: ccimport -f myCompChecksOutput.xml - All compliance checks defined in the xml file will be imported into the target TPM server. The same computers and groups in the target TPM server will be correlated properly while importing the checks defined in the xml file. From the command line, a message is displayed and indicated that the command has been successfully run.

10. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Use Case 4  Import the Compliance Checks for the selected computers and/or groups - TPM Administrator exports compliance checks for the selected targets using the command line as the following: ccexport -f myCompChecksOutput.xml -c compList.txt -g groupList.txt where input files “compList.txt” and “groupList.txt” contain only the target name list that require to be imported to the production system. - After ccexport command is successfully performed, an output file “myCompChecksOutput.xml” is created. TPM administrator takes this output xml file, and copy onto the TPM production system or the TPM server which the checks need to be imported. - From the TPM production system, TPM administrator runs the following command to import the compliance checks to the TPM server: ccimport -f myCompChecksOutput.xml - All compliance checks defined in the xml file will be imported into the target TPM server. The same computers and groups in the target TPM server will be correlated properly while importing the checks defined in the xml file. From the command line, a message is displayed and indicated that the command has been successfully run.

11. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Use Case 5  Import the Compliance Checks to the different targets - TPM Administrator exports compliance checks from computer ‘A’ using the command line as the following: (Note: the same use case can be applied to group) ccexport -f myCompChecksOutput.xml -c compList.txt Where input file “compList.txt” contains the name of the computer ‘A’. After ccexport command is successfully performed, an output file “myCompChecksOutput.xml” is created. - TPM administrator runs the following command to import the compliance checks for computer ‘A’ to computer ‘B’: ccimport -f myCompChecksOutput.xml -p importCfg.properties - Where file importCfg.properties stores the mapping information between computer ‘A’ and ‘B’ for the checks. This properties file will guide this command tool to reallocate computer ‘B’ and take the compliance checks from computer ‘A’, and add them to computer ‘B’. - TPM administrator should see the compliance checks listed under the computer ‘B’ from TPM UI after the command is performed.

12. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Use Case 6  Import the Compliance Checks to the different targets - TPM Administrator exports compliance checks from computer ‘A’ using the command line as the following: (Note: the same use case can be applied to group) ccexport -f myCompChecksOutput.xml -c compList.txt Where input file “compList.txt” contains the name of the computer ‘A’. - After ccexport command is successfully performed, an output file “myCompChecksOutput.xml” is created. - TPM administrator runs the following command to import the compliance checks for computer ‘A’ to computer ‘B’: ccimport -f myCompChecksOutput.xml -p importCfg.properties - Where file importCfg.properties stores the mapping information between computer ‘A’ and ‘B’ for the checks. This properties file will guide this command tool to reallocate computer ‘B’ and take the compliance checks from computer ‘A’, and add them to computer ‘B’. - TPM administrator should see the compliance checks listed under the computer ‘B’ from TPM UI after the command is performed.

13. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 TPM 7.1.1 Compliance Check Import/Export Use Case 7  Run xmlimport script - TPM Administrator runs the following xmlimport command: xmlimport myXMLimport.xml Where input file “myXMLimport.xml” is in xmlimport.dtd format - All TPM data defined in the xml file including the compliance checks are imported into the date model.

14. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1

15. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 Command Line Syntax  ccexport -f [-c computerList.txt ] [-g groupList.txt ] Description: Export a set of compliance checks into the specified output file. The output file is an xml file that describes the list of the targets (computers or groups) and their compliance checks associated. (cc stands for compliance check)  ccimport -f [-p importCfg.properties] Description: Imports a set of compliance checks defined in the file into TPM server. By default (without –p option specified) all the checks defined in the file will be imported into TPM server to correlate with the same targets. If there are duplicate checks on the targets, the command will throw an error and indicate that there are duplicate checks on the target. If there are already some compliance checks (not duplicate checks) on the targets, they will not be deleted and replaced, the checks defined in xml files will be added to the targets without touching these existing checks on the target. (Note: “/d” option defined inside importCfg.properties can be used to delete all existing checks before the import)

16. IBM Software Group | Tivoli software © 2009 IBM Corporation Tivoli Provisioning Manager 7.1.1 -p option for importCfg.properties  This option specify the path of a file that defines the list of the computers, groups and the related mapping for the compliance checks required to be imported into TPM server.  The file passed to the –p options has the following structure: # a line beginning with # is a comment c/source/target/ c/source/target/d g/source/target/ g/source/target/d