Configuring the MTM Transaction Pathway

The Activity Implementations for each HTTP extension you wish to integrate with the EUEM product should be configured to inject the EUEM header. It is recommended you use the DEFAULT setting but you can customize whether the header is injected in the request, response or both as well as whether existing EUEM headers are left, replaced or removed. These advanced options might be necessary if more than one product is injecting EUEM headers or in special cases where an HTTP application doesn't tolerate the injected header. At a minimum you should inject the EUEM header on the response.

If you are injecting the EUEM headers using the BTM servlet filter, see Running the BTM Servlet Filter.

When configuring an Activity which uses an Activity Implementation with EUEM header injection you might also wish to enable the "EUEM" and "EUEM Replaced" Technology Data on the Payload Data tab of the Activity's properties. This contains the header content injected and replaced if applicable. Enabling the technology data is required if you wish to launch the EUEM console from the MTM Management Console as these are the identifiers used to locate the data in EUEM. Pre-defined launch menu items are provided for launching the EUEM console. The pre-defined launch menu uses the payload named "EUEM". You might need to replace it with the payload named "EUEM Replaced". Refer to the URL Launch Menus section on how to modify launch menus.

You do not need to replace "EUEM Hostname" in the URL prefix as the value is replaced with the value from the [BTM_Launch_Menu_Hosts] stanza in services.cfg. See also the section on configuration of services.cfg.