Relationships are used to establish associations between business object attributes that cannot easily be mapped. The tool used for creating relationships is Relationship Designer Express. For more information about Relationship Designer Express, see the Map Development Guide.
When you expand the Relationships folder in the InterChange Server Component Management view, two subfolders appear: Dynamic and Static.
This section describes the following topics:
Steps for starting and stopping relationships
For a relationship to be executable, it must be activated. However, you cannot modify a relationship when it is active. Therefore, you must stop the relationship, modify it, and then restart it. See Appendix B, Requirements for restarting IBM WebSphere InterChange Server Express system components to find out what changes require relationships to be restarted.
Perform the following steps to start and stop relationships in System Monitor:
Perform the following steps to start and stop relationships in System Manager:
As part of the design process of a static relationship, a developer can indicate whether the relationship's tables are to be cached in memory. A static relationship is one whose data does not change frequently so is a good candidate for table caching. If the developer has indicated that the static relationship's tables can be cached, you can control whether to enable caching from System Manager. System Manager lists all static relationships in the folder labeled Static in the Relationships folder.
Perform the following steps to enable relationship table caching for a static relationship:
When the Cached option appears with a check mark to the left, InterChange Server reads the relationship tables into memory the next time the run-time data is accessed.
Perform the following steps to disable relationship table caching for a static relationship:
When the Cached option appears with no check mark to the left, InterChange Server reads run-time data from the tables in the relationship database.
Perform the following steps to tell InterChange Server to reread the relationship's tables into memory with the Reload feature:
InterChange Server reloads the cached relationship tables by rereading the tables from the relationship database into memory. This option is useful when the static relationship's tables are updated directly in the database through SQL statements. To get the more current version of the tables into cache, select the Reload option.
Perform the following steps to tell InterChange Server to log a trace message each time it loads and unloads relationship tables in memory:
RELATIONSHIP.CACHING=5
InterChange Server Express routes these messages to the trace file (if one is configured). By default, InterChange Server Express does not generate trace messages when it loads and unloads the relationship tables. Trace levels less than five (0-4) do not produce messages either.