Resource registration response file

Use a response file to register a resource that is managed by the administration service provider in the resource registry.

Create a resource registration response file, with a file extension of .response and save it to a directory, for example, c:/TaskBundleResponse.

Table 1. Properties in the resource registration response file
Property	Description
`version`	Resource version
`name`	Unique resource name
`identifier`	Unique identifier for the resource
`DependsOnURLs`	Dependencies for the resource
`description`	Description for the resource
`ServiceType`	Type of service management system that the resource represents, with the following valid options: 1 – ITM 2 – Omnibus 3 – TCR 4 – DASH 5 – FRS `number` – `user_defined_service_type`

Examples

This example shows the content of the TCR.response file. When you run the Administration Services client with the -registerResource operation and this file, it registers the IBM® Tivoli® Common Reporting resource in the resource registry.

ServiceType=TCR
identifier=20
description=Tivoli Common Reporting provides an integrated reporting solution
for the products in the Tivoli portfolio. 
TCR allows to link multiple reports across various 
Tivoli products to simplify the report navigation and 
accelerate access to key reporting information.
name=IBM Tivoli Common Reporting
version=3.1
DependsOnURLs=

Note: To use a DBCS locale like Japanese, Chinese or Korean, the DBCS locale-specific content in the response file must be in the Unicode format.

Response file in a Unicode format:

ServiceType=ITM
identifier=128
description=\u00e3\ufffd\u201c\u00e3\u201a\u0152\u00e3\ufffd
\u00af\u00e3\u20ac\ufffd\u00e6\u2014\u00a5\u00e6\u0153\u00ac
\u00e3\ufffd\u00ae\u00e8\u00a3\u00bd\u00e5\u201c\ufffd\u00e3
\ufffd\u00a7\u00e3\ufffd\u2122
name=JP\u00e8\u00a3\u00bd\u00e5\u201c\ufffd
version=2.1
DependsOnURLs=