I want to make two mediated web service calls
- from a BPM application on a SAP NetWeaver Java with SID NW2 (it's on NW Java 7.40)
- via a PI system with SID PI1 (it's on on NW double-stack 7.31)
- to a third system (it's an ABAP system, but it doesn't really matter).
The calls are going from
NewLoanBoardingProcessingManageNewLBrdngOut and NewLoanBoardingProcessingNewLBrdngActionOut to NewLoanBoardingProcessingManageNewLBrdngIn and NewLoanBoardingProcessingNewLBrdngActionIn.
(I'm leaving the namespaces out here for brevity/readability, but if you're interested, they are all in the namespace http://sap.com/xi/FS-AO/Global and the BPM is defined in note 1891861, which sadly doesn't explain the web service configuration part.)
There is a service group (called POL_BACKEND) defined on the Java system, as part of the software component test.sap.com/polnlbv0 (the BPM process). It contains NewLoanBoardingProcessingManageNewLBrdngIn and NewLoanBoardingProcessingNewLBrdngActionIn (the two interfaces on the PI it needs to call). I can't manage to configure it (I haven't configured service groups before). Also I'm not sure if my other steps are right.
I rely on the Services Registry on the Java system NW2. Both systems, also the PI1, are configured to refer to that Services Registry.
In PI in the integration builder I did the following:
- Defined a SOAP Sender Channel with XI 3.0 as the message protocol for the Business System that represents the Java system NW2, as I read that this is optimal for the communication between SAP NW Java BPM and SAP PI. I'm using version SAP BASIS 7.31 of the SOAP sender adapter. (It didn't like 7.40, as the PI itself is only on 7.31.)
- Defined two SOAP Sender Agreements, for NewLoanBoardingProcessingManageNewLBrdngOut and NewLoanBoardingProcessingNewLBrdngActionOut.
- From the "Sender Agreement" menu on each of them I chose "Publish in SR". => I can see them show up in the Services Registry on NW2 as expected on the tab "Service Definitions" (as NewLoanBoardingProcessingManageNewLBrdngOut and NewLoanBoardingProcessingNewLBrdngActionOut). Their system is listed as PI1_XPI on ILBNKPI1 (this is the PI1 host name). I'm not sure why it generated the name as PI1_XPI, this is not the business system name. Other services show up as "PI1 on ilbnkpi1", they seem to be BASIS or PI-monitoring related (provided by SAP). Then there are services that show up as "PI1 (001) on ilbnkpi1", which we have created ourselves. (And then there are other systems, like NW2.)
- Then I defined a receiver determination, interface determination and receiver agreement for both services. I'm fairly certain this part is okay.
Now I log onto the Java system NW2 on NetWeaver Administrator and go to SOA > Application and Scenario Communication > Application Communication. I search for the software component test.sap.com/polnlbv0. It is found and shows the consumed service group POL_BACKEND, which shows the interfaces NewLoanBoardingProcessingManageNewLBrdngIn and NewLoanBoardingProcessingNewLBrdngActionIn (the ones that need to be called).
Originally the provider system PI1_XPI was not available in the list (next to the consumed service group name), only PI1 (001) and NW2, but after clicking Edit one can choose "Create" in the dropdown list of provider systems, and in the following dialog one can use the value help button to select provider systems that are known to the Services Registry. So now PI1_XPI is selected. (I have also tried others, including NW2, just to be sure.)
After clicking on Configure and going through the process, I get the error "Following services not available in Services Registry; make sure they are published correctly and with endpoints" and it lists NewLoanBoardingProcessingManageNewLBrdngIn and NewLoanBoardingProcessingNewLBrdngActionIn.
I don't understand how this is possible, as I can see them right there in the Services Registry, with their end points.
On the configuration screens the SLD System ID is prefilled as PI1.SystemHome.ilbnkpi1, this seems to be okay, as in the Services Registry on the Systems tab, when I click on PI1_XPI this is the SLD System ID that is shown. (Also I get (with a green mark) "WS connection to system "PI1_XPI on ilbnkpi1" established using user "NW2_TO_PI1"".) In the simple layout only the SLD System ID and the user and password fields are available, in advanced mode many more, but not sure if it makes sense to change anything there.
After returning to the start screen the processing status is "To be processed" at first and soon changes to "Failed". When I click on Show Log I see this error:
Configuration for service group [POL_BACKEND] failed. Error details:
[No endpoints found. Check if the service is configured and if its endpoints are available in the SR. Service: [{http://sap.com/xi/FS-AO/Global}NewLoanBoardingProcessingManageNewLBrdngIn] Assigned Provider: [PI1_XPI on ilbnkpi1]
Service Group: [POL_BACKEND]
Service Group application: [test.sap.com/polnlbv0]
Service Reference application: [test.sap.com/polnlbv0]
No endpoints found. Check if the service is configured and if its endpoints are available in the SR. Service: [{http://sap.com/xi/FS-AO/Global}NewLoanBoardingProcessingNewLBrdngActionIn] Assigned Provider: [PI1_XPI on ilbnkpi1]
Service Group: [POL_BACKEND]
Service Group application: [test.sap.com/polnlbv0]
Service Reference application: [test.sap.com/polnlbv0]
]
For more information refer to the trace with ID [C0000A1A5653000900000029000010E4]. Details: [PI1.SystemHome.ilbnkpi1.IS] provider system, [test.sap.com/polnlbv0] service group application
I'm not sure where exactly to check this trace ID.
Are my steps sensible in principle or am I going about this completely wrong?
I tested the end point WSDL URL that I see in the Services Registry in the WS Navigator. It doesn't work there, either, I get this error: Invalid transport binding settingsHTTP Client, does not have endpoint url specified. I.e. the first part, where it loads the list of operations, works, but the actual call fails.