Updating metadata

You update the metadata to ensure that it matches the metadata in the new IBM® InfoSphere® Information Services Director environment. After you import InfoSphere Information Services Director resources into a new environment, run the UPDATE command to synchronize the imported metadata with the metadata in the new environment.

Before you begin

You must disable the operation or information provider before you can update the metadata for those resources. If you deploy an application that was imported at design time, run the DISABLE command to disable the information provider. If you import an application that was exported at run time, the application is automatically disabled.

About this task

The UPDATE command is supported only for runtime applications and information services connections.
You can update only one metadata attribute at a time. To update multiple metadata attributes, you must run a separate UPDATE command for each attribute.
There are three paths (application, agent host, or connection name) for using this command. Each path has different mandatory and optional options. For every metadata UPDATE command that you enter, you must specify one of the following options: -agenthost, -application, or -cname.

Procedure

Open a command line editor.

Update metadata by application, or agent host name, or connection name by running the appropriate UPDATE command:

To update metadata by application, use the following command:

ISDAdmin -action update 
-a <application name> -s <service name> -o <operation name> 
-key <key for the metadata attribute to be updated> 
-subkey <job parameter argument you want to modify> 
-oldvalue <old value of the attribute you want to modify> 
-newvalue <new value for the attribute that you are modifying> 
-dsproject <project name> -dsjob <job name> -providerUser <service provider>

To update metadata by agent host name, use the following command:

ISDAdmin -action update 
-agentHost <agent host name> -providerType <DS, DB2, ORA, or DB2CF> 
-providerHost <service provider server host name> 
-key <key for the metadata attribute to be updated> 
-subkey <job parameter argument you want to modify> 
-oldvalue <old value of the attribute you want to modify> 
-newvalue <new value for the attribute that you are modifying> 
-dsproject <project name> -dsjob <job name> -providerUser <service provider>

To update metadata by connection name, use the following command:

ISDAdmin -action update 
-cname <connection name> -key <key for the metadata attribute to be updated> 
-oldvalue <old value of the attribute you want to modify> 
-newvalue <new value for the attribute that you are modifying>

Examples of updating metadata

This section contains examples for the following scenarios:

Bulk updates for provider-specific metadata
Bulk updates for service provider metadata
Bulk updates for operation metadata
Updates to IBM InfoSphere Information Server connections metadata
Updates to IBM InfoSphere Information Services Director job parameters

Examples of bulk updates for provider-specific metadata

The following commands show you how to make bulk metadata updates to the providers by using IBM InfoSphere DataStage® metadata and DB2® metadata as examples.

Update the InfoSphere DataStage password for a specific agent host and InfoSphere DataStage user ID:

Note: The -oldvalue parameter is optional because the identifiers (the combination of agent host and user ID) uniquely qualify the key that is being updated. Also, for a key of DS_PASSWORD, the value for -newvalue can be provided as a string encrypted with the encrypt command.

ISDAdmin -action update -agentHost <agent host name> -key DS_PASSWORD -providerUser <DataStage user ID> -oldvalue <old DataStage password> -newvalue <new DS password>
Update the InfoSphere DataStage user ID for a specific agent host:

Note: You must use the -oldvalue parameter to specify which user ID you are updating.

ISDAdmin -action update -agentHost <agent host name> -key DS_USERID -oldvalue <old DataStage user ID> -newvalue <new DataStage user ID>
Update the InfoSphere DataStage job name for a specific agent host and project:

Note: You must use the -oldvalue parameter to specify which job name you are updating.

ISDAdmin -action update -agentHost -key DS_JOBNAME -dsproject <DataStage project name> -oldvalue <old job name> -newvalue <new job name>
Update the DataStage project name for a specific agent host:

Note: You must use the -oldvalue parameter to specify which InfoSphere DataStage project name you are updating.

ISDAdmin -action update -agentHost <agent host name> -key DS_PROJECT_NAME -oldvalue <old DS project name> -newvalue <new DS project name>
Update the agent host for a specific InfoSphere DataStage host:

Note: It is not possible to have more than one InfoSphere DataStage host for a given agent, so the -oldvalue parameter is not required in this scenario.

ISDAdmin -action update -agentHost <agent host name> -key AGENT_HOST -providerHost <DS server host name> -newvalue <new agent host name>
Update the InfoSphere DataStage port number for a specific agent host:

ISDAdmin -action update -agentHost <agent host name> -key DS_PORT -newvalue <new DS server port number>
Update the DB2 host name for a specific agent host:

Note: You must use the -oldvalue parameter to specify which DB2 host name you are updating.

ISDAdmin -action update -agentHost <agent host name> -key DB2_HOST -oldvalue <old DB2 server host name> -newvalue <new DB2 server host name>
Update the DB2 port number for a specific agent host and DB2 host:

Note: You must use the -oldvalue parameter to specify which port number you are updating.

ISDAdmin -action update -agentHost <agent host name> -key DB2_PORT -providerHost <DB2 server host name> -oldvalue <old DB2 server port number> -newvalue <new DB2 server port number>
Update the DB2 database name for a specific agent host and DB2 host:

Note: You must use the -oldvalue parameter to specify which database name you are updating.

ISDAdmin -action update -agentHost <agent host name> -key DB2_DATABASE -providerHost <DB2 server host name> -oldvalue <old DB2 database name> -newvalue <new DB2 database name>
Update the DB2 user ID for a specific agent host and DB2 host:

Note: You must use the -oldvalue parameter to specify which user ID you are updating.

ISDAdmin -action update -agentHost <agent host name> -key DB2_USERID -providerHost <DB2 server host name> -oldvalue <old DB2 user ID> -newvalue <new DB2 user ID>
Update the DB2 password for a specific agent host, DB2 host, and DB2 user ID:

Note: The -oldvalue parameter is optional because the -providerUser parameter is used. Also, for a key of DB2_PASSWORD, the value for -newvalue can be provided as a string encrypted with the encrypt command.

ISDAdmin -action update -agentHost <agent host name> -key DB2_PASSWORD -providerHost <DB2 server host name> -providerUser <DB2 user ID> -oldvalue <old DB2 password (optional because the providerUser parameter is used> -newvalue <new DB2 password>

Examples of bulk updates for service provider metadata

The following commands show you how to make updates to service provider metadata:

In the following examples, the -oldvalue parameter is optional. You can use this parameter to update only one specific value.

Change the activation threshold for all InfoSphere DataStage service providers across applications for a specific agent host:

ISDAdmin -action update -agentHost <agent host name> -key ACTIVATION_THRESHOLD -providerType DS -oldvalue <old activation threshold> -newvalue <new activation threshold>
Change the activation delay for a specific DB2 service provider across applications for a specific agent host:

ISDAdmin -action update -agentHost <agent host name> -providerType DB2 -key ACTIVATION_DELAY -oldvalue <old activation delay> -newvalue <new activation delay>
Change the activation delay for a specific DB2 service provider residing on a specific host across applications for a specific agent host:

ISDAdmin -action update -agentHost <agent host name> -providerType DB2 -key ACTIVATION_DELAY -providerHost <DB2 server host name> -oldvalue <old activation delay> -newvalue <new activation delay>
Change the maximum idle time for all of the operations in a specified application and service:

ISDAdmin -action update -a <application name> -s <service name> -key MAX_IDLE -oldvalue <old max idle> -newvalue <new max idle>

Examples of bulk updates for operation metadata

The following commands show you bulk updates for operation metadata:

In the following examples, the -oldvalue parameter is optional. You can use this parameter to update only one specific value.

Change the load balancer for all operations for a specific agent server host:

ISDAdmin -action update -agentHost <agent host name> -key LOAD_BALANCER -oldvalue <old load balancer> -newvalue <new load balancer>
Change the maximum number of retries for all operations of a specified service in an application:

ISDAdmin -action update -a <application name> -s <service name> -key MAX_RETRIES -oldvalue <old max retries> -newvalue <new max retries>

Example of updating common providers

The following command shows you how to update metadata for a common provider:

Update the agent server port number for a specific agent host:

ISDAdmin -action update -agentHost <agent host name> -key AGENT_PORT -newvalue <new agent server port number>

Example of updating IBM InfoSphere Information Server connections metadata

The following command shows you how to update metadata for connections:

Update the DataStage or DB2 user ID for a specific connection:
ISDAdmin -action update -cname <connection name> -key USER -oldvalue <old DS user ID or old DB2 user ID> -newvalue <new DS or DB2 user ID>

Examples of updating IBM InfoSphere Information Services Director job parameters

The following commands show you how to update IBM InfoSphere Information Services Director job parameters:

Update an IBM InfoSphere Information Services Director job parameter:

Note: If you do not specify a service name and operation name, then all matches within the application will be updated. You can use the InfoSphere DataStage project name and job name to identify a specific project or job attached to an operation for the update.
In the following examples, the -oldvalue parameter is optional. You can use this parameter to update only one specific value.

ISDAdmin -action update -a <application name> -s <service name> -o <operation name> -dsproject <DataStage project name> -dsjob <DataStage job name> -key JOB_PARAMETER -subkey <specific job parameter whose value is being modified> -oldvalue <old value> -newvalue <new value of the job parameter being modified>
Update a job parameter value across multiple applications for a bulk scenario:
ISDAdmin -action update -agenthost <agent host name> -dsproject <DataStage project name> -dsjob <DataStage job name> -key JOB_PARAMETER -subkey <specific job parameter for the value that is being modified>

What to do next

After you finish updating metadata, run the ENABLE command to enable the information provider.