Logical port error (WS_LOGICAL_PORT) when consuming WS in PI

[Former Member]

Hi All,

I am trying to integrate simple Currency Conversion Web Service witm my ECC program.

Program displays two fields in the selection screen (Currency From and Currency To)

WS is: http://www.webservicex.com/ws/WSDetails.aspx?WSID=10&CATID=2

The scenario is as below:

Proxy (Z-PROGRAM ) <-sync-> PI <-sync-> WS (Currency Convertor)

Looks like ABAP Proxy is done ok.

PI configuration also looks ok as I am trying it in IB's Test Configuration tool - all steps are 'Green / Passed'

Based on WSDL 3 interfaces were generated:

CurrencyConvertorHttpPost

CurrencyConvertorHttpGet

CurrencyConvertorSoap

I am using Soap one... along with WS Communication Channel

CC has configuren itself based on WSDL likn provided,

Technical Transport Settings were set to:

Target Host: www.webservicex.net

Service Name / Port: -1

URL Access Path: /CurrencyConvertor.asmx

Transport Binding: SOAP 1.1 Using HTTP

Why am I getting logical port error?

Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap

I searched the web for error message and I found obsolete logical port configuration using LPCONFIG, and also some 'new' approach with SOAMANAGER LogPort configuraton

(When I try to do this as suggested in [document |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b04408cc-f10e-2c10-b5b7-af11026b2393?QuickLink=index&overridelayout=true]

then I cannot see my newly created services on the list)

... but is this the right track to follow?

Should I run Logical Port configuration in PI?

I would appreciate your comments on this.

Regards,

bob.

[markangelo_dihiansan · Accepted solution]

Hello,

Why am I getting logical port error?
Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap

WS Adapter is used for those that are using WS-RM (Webservice-Reliable Messaging)...See this blog

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b00bbb77-75bc-2a10-6b9a-a6f81615..., but I think for now this is limited to SAP-to-SAP connections. That is why in your error it is searching for a logical port (ABAP Proxy).

You should be using the SOAP Receiver Adapter instead.

Hope this helps,

Mark