SAP MII Java Resource Adapter (XMIIIDOC) HA LB into multiple ECC/EWM App Server Gateways

[alex_smith]

Greetings SAP Community,

We run SAP MII 15.5 PL24 on HANA in a centralized deployment. SAP MII system has three Application Server JAVA. This MII system is fed by one SAP PCo system per plant and sometimes directly from other plant systems such as MES/Wonderware etc. This all works great so far. SAP MII then has two Resource Adapters (XMIIDOC) connecting into SAP ABAP EWM(SAP EWM 9.5) and SAP ABAP ECC (EHP7 FOR SAP ERP 6.0) application server gateways by registered program in SM59 RFCs. Understand that SAP ABAP EWM and SAP ABAP ECC each have multiple ABAP Application Servers and so they naturally have one Tcode SMGW gateway per Application Server ABAP.

This brings us to the problem. As we know, in the SAP MII XMIIDOC Resource Adapter configuration you may point a Resource Adapter to exactly one SAP EWM or SAP ECC Application Server respectively. This config can be extended to point to a message server, but that was tested and does not achieve what we want. It will register in the gateway of that one Application Server ABAP and you may not have it register across all the Application Server ABAP Gateways at the same time in order to achieve redundancy that multiple App Server ABAPs provide ECC and EWM. Therefore, this connection is always dependent on one of your ECC and EWM Application Servers being online 24/7. At this time this is one of the only single points of failure in our entire production SAP environment and a thorn in our side during rolling maintenance of ABAP App servers. The adapters need to be manually pointed away from the APP Server to undergo maintenance, not to mention the risk of the SPOF.

Has anyone else encountered and overcome this problem?

The goal is to, as we do with all other interfaces, introduce High Availability Load Balancing. We received a recommendation under component "Java-Connector (BC-MID-CON-JCO)" to install SAP Stand-Alone Gateway on the SAP MII ASCS. Point XMIIDOC01 Resource Adapters to the Stand-Alone Gateway. Configure Stand-Alone Gateway to act as HA Load Balancer into ECC and EWM, but are yet to locate any official documentation to give confidence that this is workable in production. Thoughts welcome!

Thank you,

Alex

[cillian_cahill2]

Hi Alex,

Did you resolve this? I don't see why SAP suggested installing a standalone GW on the MII side. We did look at this, and I think the only way around it is a standalone GW on the ABAP side. Or, if you have enough free resource adapters on the MII system, you could try the following (which will need some testing):

(Below will all have the same program ID XMIIIDOCECC)

XMIIIIDOC01 -> ECC APP1

XMIIIIDOC02 -> ECC APP2

XMIIIIDOC03 -> ECC APP3

XMIIIIDOC04 -> ECC APP4

XMIIIIDOC05 -> ECC APP5

(Below will all have the same program ID XMIIIDOCEWM)

XMIIIIDOC06 -> EWM APP1

XMIIIIDOC07 -> EWM APP2

XMIIIIDOC08 -> EWM APP3

XMIIIIDOC09 -> EWM APP4

XMIIIIDOC010 -> EWM APP5

If the gateway in SM59 is left blank, it will default to the APP server running the background job. The message listeners and process rules on MII must be configured the same for 1-5 and 6-10.

[alex_smith]

No takers yet, maybe I can summarize in short form:

XMIIDOC01 JCO connection to ECC (registered program) must not rely on single ECC APP. It must survive a rolling restart of ECC Apps one at a time.

When each ECC APP goes down, the connection should use the remaining apps without manual intervention.