Example of Multiple Inheritance and Overrides

In this example, a B2B Host was created that included a custom delivery protocol named dpad2 that included three custom messaging attribute definitions (MADs). In ePM, various of the outbound parameter settings were modified at every possible level. (This is poor practice, and employed here simply to illustrate the principles.)

Figure 5–21 and Figure 5–22 show parameters at the highest level in ePM — the protocol level itself. In the example, three parameters in the host protocol are overridden by the TP protocol.

Figure 5–21 Host Parameters at the Protocol Level

Figure 5–22 TP Parameters at the Protocol Level

Figure 5–23 and Figure 5–24 show parameters at the second-highest ePM level — the action group level. In the example, the host action group overrides two parameter settings inherited from the host protocol, and the TP action group overrides two different parameter settings inherited from the host action group. In this example, the TP action group setting for Duplication Checking is inherited from its parallel host action group (because there is no explicit override at TP protocol level), and that the settings for mad2NumberPi, Encryption, and Character Set Encoding are inherited from its immediate parent, the TP protocol level.

Figure 5–23 Host Parameters at the Action Group Level

Figure 5–24 TP Parameters at the Action Group Level

Figure 5–25 and Figure 5–26 show parameters at the third-highest level in ePM — the action level. In the example, the host action overrides two parameter settings inherited from the protocol and one inherited from the action group. The TP action overrides one parameter setting inherited from the TP action group, one inherited from the TP protocol, and one inherited from the host protocol. In this example, the TP action setting for mad2Boolean is inherited from its parallel host action (because there is no explicit override in the TP inheritance chain, either at the TP protocol or the TP action group level), and that the setting for Use Signature is inherited from its immediate parent, the TP action group level.

Figure 5–25 Host Parameters at the Action Level

Figure 5–26 TP Parameters at the Action Level

Figure 5–27 and Figure 5–28 show parameters at the bottom level in ePM — the transaction profile level. In the example, the host transaction profile overrides one parameter settings inherited from the protocol, one inherited from the action group, and one inherited from the action. The TP transaction profile overrides two parameter settings, both inherited from the host protocol, but one of them deserves special attention: The parameter setting for Expect Acknowledgments, which was set to Yes in the host protocol , is overridden and set to Yes — the same value (see Figure 5–21). The effect of this is to break the inheritance but keep the value: Even if the setting in the host protocol should change in the future, the parameter setting in the TP transaction profile does not change.

Figure 5–27 Host Parameters at the Transaction Profile Level

Figure 5–28 TP Parameters at the Transaction Profile Level