Consumer-Proxy configuration

[former_member429661]

Hi everybody,

i'm working on SRM 701 and i want to work with an external application(Service Manager) via webservices. The SAP generated Consumer-Proxy works fine for me. But on every connection with the SAP defined proxy, the proxy established a new session on the external application server... but i want to reuse an established session.

I found these information to use the webservice connection with the external application.

Service Manager server creates a new session for each subsequent request and quickly run out of

available sessions.

To avoid running out of available sessions, there are two options to consider:

Option A: Set the HTTP header "connection:closed" so that the Service Managerserver will not

keep a Web Services session open after the current request is finished.

Option B: Utilize the Web Services session persistence by doing one of the following to reuse the

existing Web Services session on theService Managerserver.

1. 1. Use connection: keep-alive. If the connection header is missing, it defaults to "keepalive"

    for HTTP/1.1.    

1. 2. The Web Services client needs to supply a session cookie with the same user log-in

information that created the session.

Note: Even with Web Services session persistence, each SOAP API request is stateless, so

that requests are handled independently between one another.

I don't know where i set the header information from "Option A" in the Consumer-Proxy configuration!?

With an client tool (SOAPSonar) i tried "Option B 1". That didn't work either but i can see in the responsed header data that there are cookie information.

The SAP generated proxy interface includes a "handle" but these responsed data isn't filled with information (i think there could be set the cookie information)

I'm neither a webservice specialist nor an SAP proxy specialist but... is there a option to configure the SAP Proxy in that way, that the Proxy can handle the cookie so that i can reuse with these cookie information the established external server Option B 2) ?

Or i'm wrong with these ideas?

Thanks in advance for help or hints

--Bernward Henkel

[former_member429661]

Hi Trevor,

i found out, that when i set the "connection: keepalive" parameter (Option A), the session closed immediatly after the request.

That works although for me. Now i read in your link, that we can set these parameter in the SOAMANAGER configuration.

But... i can't find these option in the transport settings tab of the SOAMANAGER.

Do you have an idea where i can set these parameter ?

Thx for your help.

--Bernward Henkel

[former_member429661]

Hi guys,

no hints, no idea?

Plse help!

Thanks in advance

--Bernward Henkel

[Former Member]

Hi Bernward,

I have very limited access to any decent SAP backend to provide further useful input, but if you look at the screenshot below:

I used the manual configuration option to get this view. That's as useful as I can be at this point.

Regards, Trevor

[former_member429661]

Hi Trevor,

i see you are using something with "XI

-Integration". Maybe that is the difference in the interface between my SOAMANAGER and your's. I don't have the tab "State Management'.

My constellation with this WSDL stuff is:

1. create with the .wsdl an client proxy (SE80 Create Enterprise Services)
2. Configuration a logical port (LP) with SOAMANAGER
   1. (that generates an HTTP entry in SM59 which i cannot change)
3. Using this LP in ABAP

     TRY.
      CREATE OBJECT lo_wsproxy
        EXPORTING
          logical_port_name = 'LP_SRM_CM'.

    CATCH cx_ai_system_fault INTO lo_sys_exception.
  ENDTRY.

That's it. And therefor i look for the place where i can change the HTTP Parameter "Connection: keepalive".

No XI stuff etc.

Regards, Bernward

[Former Member]

Hi Bernward;

we have the same issue. did you find any solution to this problem

[former_member429661]

Hi Mustafa,

sorry for the late answer... had a long vacation 🙂

There is no solution for the "keep alive" connection. So the hole application ist optimized for the bi-directional communication. That means that the SAP-System send an question and waited for an answer. If the answer arrived the communication-task is over.

Regards,

Bernward

[Former Member]

Hi! Do you have an update on this?

We are trying to keep an HTTP Connection alive.

[Former Member]

Hi Bernward,

I haven't really dealt with a situation like this but it appears that HTTP cookies are supported when configuring your logical port for the consumer proxy. Not sure how useful this is to you but it could be a start to find what you are looking for.

http://help.sap.com/saphelp_nwce711/helpdata/en/47/f8af96fdb84aa7e10000000a421937/content.htm

Regards, Trevor