Multiple Maximo Source Systems integrated with Single Financial or Accounting Systems needs Source System Identity.

A system property, mxe.int.expupdatesender, when set to 1, forces the value of maxvar MXSYSID to be sent outbound via SENDERSYSID.

By default, this value is MX.The IBM Product team discourages users from changing this as it becomes a large undertaking and invites regression testing.

In some business scenarios, however, multiple Maximo instances are integrated into a single financial or accounting system. This includes Generations, Distributions, and Substations. In an effort to standardize across interfaces of similar business processes, where all three systems publish into a single junction at middleware. Middleware wants to know the identity of the source system so that response from target system can be sent to right source.

In this case, a need arises to have an alias name defined for each source system.

For example:

GEAM : MX alias as MXG

DEAM: MX alias as MXD

SUBSTATION: MX alias as MXS

Automation scripts, or outbound rules, can achieve this, but this is not the best practice since it invites changes to existing and/or future interfaces. Consequently, our current system design should provide some configuration way that can be done once and used as many times as needed without effort on future interfaces, similar to today's design around MXSYSID maxvar. Even if we create new variable in MAXVAR table for alias and configure this for integration framework so that middleware can use original or alias name.