CRM On Demand - Web Services Integration (MOSC)

MOSC Banner

Stateless webservice session using JSESSIONID

in CRM On Demand - Web Services Integration (MOSC) Question

Hi everyone,

Upon adding additional tasks to our CRM-OD integration web services and having studied the Oracle Web Services On Demand Guide, I've come to believe that our web services implementation does not take advantage of the SOAP header parameter <SessionKeepAlive> and sending the JSESSIONID with subsequent calls. I did not create our web services but have inherited them.  My understanding is that best practices suggest providing username and password on the initial web service call and then send the JSESSIONID on subsequent calls; allthewhile, using the SessionKeepAlive attribute.

I'm having difficulty trying to find any good examples for implementing this technique.  Our services have been build with java using Apache Axis.  I think I've got the SessionKeepAlive attribute set with the following code:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center