Resource Registry overview

The Resource Registry application can be used to define resource name aliases for source and target resources that are specified in map cards.

A resource name is an alias that has different values defined for multiple deployment environments. A resource value can be either a command card setting for a map, an adapter command override setting for a map or system component, or an argument to environment functions within a map rule (RUN, PUT, GET, DBLOOKUP, DBQUERY, and EXIT). In addition, other resources that can be aliased include:

• backup files
• audit files and locations
• trace files and locations
• work space locations
• external parser location (defined in the Type Designer)
• map server location (defined in the Integration Flow Designer)

Using the Resource Registry, a resource name is associated with one or more logical virtual servers (deployment environments). Each logical virtual server might have a different resource value for a given resource name.

For example, suppose Payroll is a resource name. Payroll is associated with a Test, Development, and Production logical server. For Test, Payroll might be an SQL Server query. For Development, Payroll might be an Oracle query. For Production, Payroll could be a DB2® query.

This feature minimizes the maintenance of systems and maps when moving them to different environments.

With the Resource Registry you define the various resource values once, and those values get resolved at run-time (map execution) by the map server (Command Server, Launcher, or Transformation Extender Programming Interface), thereby eliminating the need to modify maps during design-time.

Without the Resource Registry, you must manually edit input and output card settings for each platform the system and/or maps are moved to in order to reflect the appropriate parameters (resource value) for that environment.

For the purpose of this documentation, the generic term map server is used when referencing the Command Server, Launcher, or Transformation Extender Programming Interface.

See the Command Server documentation for information on items to take into consideration if you use resource names in maps running on a OS/390® Batch or CICS® version of the Command Server.