IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Defining and transforming data > Create relationships
Static relationships
A static relationship is used when to map data from one application to the other and to define the values for the mapping during the definition time of the relationship (for example, for state codes). In one application the state code may be “ California”, while in another application it may be “ CA”. A static relationship is created between these two pieces of data indicating that they are equivalent. The participant data that these types of relationships contain have values that do not change frequently. These relationships exist for both identity relationships and the non-identity relationships.
During the creation of the relationship, the same rules apply for identity and non-identity relationships with the following differences:
- There is no managed role allowed as it is not needed for a static mapping.
- The allowed depth of attribute level is infinite.
- Instance data can be predefined within the relationship editor.
The following topics describe how to create and use static relationships in IBM Integration Designer:
- Create static relationships
Static relationships have roles that are based on business objects or on simple data types.- Pre-populating static relationships
The data for static relationships can be pre-populated.- Deploying relationships
You can deploy a relationship to IBM BPM. The underlying tables are created and the configuration is completed in the administrative console.
- Invoking static relationships from maps
There are two ways to invoke a static relationship from maps. You can either call a static relationship from an inbound map or call a static relationship in an outbound map.