Table 4–1 illustrates this ePM hierarchy of default override inheritance. Keep in mind that parameter categories only inherit from the same categories, for example, B2B Host Action Group Business Protocols from TP Action Group Business Protocols, and so on.
Table 4–1 ePM Override Inheritance Hierarchy
Major Component Being Configured |
Row in This Table |
Selected in ePM Explorer |
Parameter Categories in ePM Canvas |
Parameter Values Inherit Overrides as Follows: |
---|---|---|---|---|
B2B Host component:May have one or more Action Groups, which in turn may have one or more Transaction Profiles. |
Row 1 |
B2B Host under B2B Host Configuration tab |
Business Protocols |
Top level; no inheritance |
Delivery Protocols | ||||
Transports | ||||
Row 2 |
Action Group; “child” component relation to “parent” B2B Host above |
Business Protocols |
From B2B Host Configuration tab values set on ePM canvas |
|
Delivery Protocols | ||||
Row 3 |
Transaction Profile; “child” component relation to “parent” Action Group (and “grandparent” B2B Host) above |
Business Protocols |
From B2B Host ⇒ Action Group configuration values set on ePM canvas |
|
Delivery Protocols | ||||
Transports | ||||
Trading Partner (TP) component:May have one or more Action Groups, which in turn may have one or more Transaction Profiles. |
Row 4 |
TP under Trading Partner Configuration tab |
Business Protocols |
This Row 4 inherits from Row 1 above |
Delivery Protocols | ||||
Transports | ||||
Row 5 |
TP Action Group; same as Row 2 above (cannot be created at this level) |
Business Protocols |
This Row 5 inherits from Row 2 above |
|
Delivery Protocols | ||||
Row 6 |
Transaction Profile |
Business Protocols |
This Row 6 inherits from Row 3 above |
|
Delivery Protocols | ||||
|
Transports |
It is recommended that you set your necessary configurations at the “highest” level possible, according to the hierarchy shown in the previous table. For example at the B2B Host Business Protocol level or at the TP Business Protocol level. See the sample scenario ePM configuration for an example of these recommended configuration practices.
For more information parameter override inheritance in ePM, see the eXchange Integrator User’s Guide.