Multiple BLS as web service calls from ABAP proxies?

[Former Member]

We would like to call multiple MII BLSu2019s as web services from ABAP proxies.

Unfortunately, when we generate the proxy (even with a unique prefix), the generated objects collide and/or overwrite each other. This is because the external key (name XacuteWSSoap and namespace http://www.sap.com/xMII) is the same in the WSDL for all BLSu2019s.

The only solution we have found thus far is to generate each proxy in its own package, which is not an acceptable solution for us.

Does anyone know how to get around this without manually changing the WSDL or using separate ABAP packages for the proxies? Calling MII BLSu2019s from ABAP proxies is a critical piece of our planned application.

[salvatore_castro]

Kristjan,

Some suggestions:

You can create a "Delegator" transaction that provides a single WSDL interface for multiple different transaction functions. Just provide a "Command" parameter and use the switch action to route you request to the appropriate transaction.

Another is that you can make a straight HTTP request through the "Runner" servlet of MII to any transaction.

Some questions:

What version of MII?

What are the services providing to ERP?

Hope this helps,

Sam

[Former Member]

Thanks Sam,

We considered a u201Cdelegatoru201D transaction architecture and decided it was a bit too convoluted. We also considered a straight HTTP request (as in CL_HTTP_CLIENT) from ABAP but didnu2019t want to worry about the intricacies of designing/maintaining such a call.

I just wanted to make sure we werenu2019t missing something obvious. Currently, we are opting to place each proxy in its own development subpackage, which appears to resolve the issue. Not ideal, but itu2019s low maintenance.

We are using MII 12.1, and providing services to read/write some basic OPC tags from an ABAP system.

Thanks for your response!

Kris

[salvatore_castro]

Kris,

Ok, I understand the tech side, what's the business purpose of the application? Perhaps there's a better way to go about this using some other capabilities/components of MII.

Regards,

Sam

[Former Member]

Some shop floor business functionality is currently presented to the users in an ABAP-based system via a standard SAP GUI interface. The desire is to call out of that ABAP-based system to set or read a PLC value through an OPC tag, at the click of a button in the ABAP-based screen (like reading a torque or something similar). An MII BLS is basically acting as middleware to fulfill this requirement, and would receive a web service call from ABAP to interact with the PLC via OPC.

[salvatore_castro]

Kris,

First off I understand that this approach is already in place and the user is comfortable with it and it's probably a Phase 1 of a larger initiative. However, I still have to question the architecture just for completeness.

As I understand it, the current design is to have someone at the plant logging into a central SAP ERP instance via SAP GUI which makes multiple calls to the MII system that is local to their plant. Since you have MII why not utilize it? It is easy to devise a web page that displays the local plant information and ERP data together and you will get better performance and better reliability out of the application.

Hope this helps,

Sam