issues arise for:
1. keeping credentials session open with Oracle CRM On Demand because OCOD accept only 10 concurrent session + it is faster to re-use existing session
2. OCOD refuse 2 request to be made without 50ms between each requests
3. session need to be reset if OCOD server restart
An option is to add the session id to the end point of the partner link in the BPEL process.
Another option is to use java embedded code in BPEL and login and loggof to OCOD.
Those 2 options did not really fit with our requirements. Too slow, not scalable, dodgy to maintain, etc...
Our approach has been to use a proxy between our BPEL engine and OCOD.
An option is to add the session id to the end point of the partner link in the BPEL process.
Another option is to use java embedded code in BPEL and login and loggof to OCOD.
Those 2 options did not really fit with our requirements. Too slow, not scalable, dodgy to maintain, etc...
Our approach has been to use a proxy between our BPEL engine and OCOD.
So all partner link to OCOD from our BPEL process use this proxy as the end point for the partner link. Thus all calls from our application to OCOD is going through this proxy.
It consist of a Java web application deployed as a war file (11Kb) it manages:
- sessions
- authentication (so no password in clear text inside our BPEL process)
- the 50 ms wait that must exist between each request to OCOD
- sessions
- authentication (so no password in clear text inside our BPEL process)
- the 50 ms wait that must exist between each request to OCOD
The code for this proxy is located here:
you can check it out like that:
The idea is to make it public so that anybody can use it and tell if he meets any issues.
Then tell me if you want to modify and enhance it. I would provide an access to the SVN repository.
Then tell me if you want to modify and enhance it. I would provide an access to the SVN repository.
