Example
In this example, updateTool is invoked to update the content data for all services, classifications, and job plans that are installed with the product. The content data is modified to reference a new organization, site, set, and vendor. The referenced objects are selected from those available when demo data is installed.
Prior to running updateTool, the updateTool.properties file should be modified to identify the new organization, site, set, and vendor. For this example, we will use the values listed in the table below.
| Property | Required | Example |
|---|---|---|
| ORGID | YES | ORGID=EAGLENA |
| SITEID | YES | SITEID=BEDFORD |
| SETID | YES | SETID=SET1 |
| VENDORID | YES | VENDORID=UPS-2 |
The next step is to identify which services, classifications, and job plans should be updated. In this example, we will update all services, classifications, and job plans shipped with Service Catalog. These values should also be specified in the updateTool.properties file. By default, the updateTool.properties file includes the values for all service content data shipped with the product.
| Property | Required | Example |
|---|---|---|
| OFFERINGS | NO | OFFERINGS='PMSC_2001A','PMSC_2002A',… |
| JOBPLAN | NO | JOBPLAN='PMSC_0001A', 'PMSC_0002A',… |
| CLASSIFICATION | NO | CLASSIFICATION='PMSC_SM',… |
| TKTEMPLATE | NO | TKTEMPLATE='PMSC_0005T',… |
| WPEDITSTATUS | NO | WPEDITSTATUS='WAPPR',… |
| USERID | NO | USERID='PMSCADMUSR',… |
| LIMITGROUPS | NO | LIMITGROUPS='PMSCADM', |
| WORKTYPE | NO | WORKTYPE='PMSC',… |
The final step is to invoke the tool as follows:
updateTool -objectStructure=updateTool75.xml \ -input=updateTool75.properties
After this command has been run successfully, all the service content data should be accessible to users that are defined for the new organization and site. The default insert site will be updated for all users specified using the USERID property. In this example, the default insert site will be set to BEDFORD.