Configuration Guide

10.3 HotFix 3

Back Next

Generating and Deploying ORS-specific Schemas

The Java software development kit (SDK) includes a compiler in

tools.jar

This operation requires access to a Java compiler on the application server machine. The Java software development kit (SDK) includes a compiler in

tools.jar

. The Java runtime environment (JRE) does not contain a compiler. If the SDK is not available, you will need to add the

tools.jar

file to the classpath of the application server.

If there are two databases that have the same schema (for example, CMX_ORS), the logical name (which is the same as the schema name) will be duplicated for JMS Events when the configuration is initially saved. Consequently, the database display name is unique and should be used as the initial logical name instead of the schema name to be consistent with the SIF APIs. You will need to change the logical name before generating the schema.

The following procedure assumes that you have already configured the base objects, packages, and mappings of the ORS. If you subsequently change any of these, regenerate the ORS-specific schemas.

Also, the JMS Event Schema generation requires at least one secure package or remote package.

To generate and deploy ORS-specific schemas:

Start the JMS Event Schema Manager.

The Hub Console displays the JMS Event Schema Manager tool.

Enter a value in the Logical Name field for the event schema.

In order to make any changes to the schema, you must have a write lock.

Click

Generate and Deploy ORS-specific Schemas

There must be at least one secure package or remote package configured to generate the schema. If there are no secure objects to generate, the Informatica MDM Hub generates a runtime error message.

ORS-specific Message Schemas

Downloading an XSD File

Finding Out-of-Sync Objects

Auto-searching for Out-of-Sync Objects

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal