I have a web integration with 3 transactions:

Login
Query Data A
Query Data B

I'm using the sequencer to string them together for a single result of A and B, but I don't necessarily want to login each time I call the sequence.

Is there a way to call the Login xaction separately to establish the session, and then re-use that session when executing the sequence?

Hi Adam,

You can try to use the context attribute. The main idea is to start with the Login transaction; a context is created for this transaction. Then call the sequence (TrA + TrB) with this specific context.

Here is the detailed procedure:

First, set the Context name parameter of the transaction steps (Query data A and Query data B) of your sequence to "mycontext" for instance (do not forget the double quote characters, because this property is javascriptable!). This parameter will tell the engine to use the given context name (within the current JESSIONID).

Then request the Login transaction with the input parameter __context=mycontext (thru the request URL). You should get a result such as:

<?xml version="1.0" encoding="ISO-8859-1"?>

<document connector="Test5250Connector" context="mycontext" contextId="6AEF58497AC06D1AF111B15E419F653A_context" cursorColumn="0" cursorLine="0" fromcache="false" generated="Tue May 11 10:28:07 CEST 2010" project="Test5250" screenHeight="24" screenWidth="80" screenclass="DefaultScreenClass" sequence="" signature="1273566487794" transaction="Login" version="5.0.5">
<result code="0"/>
</document>

Then just invoke your sequence; its internal CallTransaction steps will automatically use the specific context mycontext according to point #1.

I hope this is clear enough

And depending on the C-EMS version you use, you could have to set a specific parameter of the engine in order that procedure to correctly work.

Could you give the C-EMS version you use?

If you use version 5.x, you have nothing to configure.

Yes I am using 5.0.0.

The solution you've provided works perfectly, thank you!

Hello !

I have to do the same, but it's a server which calls the Web services. So for Convertigo there is only one client. I don't find contextid in SOAP requests, so I don't know what to do in order to get and set this value for each call.

So the question is: how can I manage concurrent sessions with a server who makes SOAP requests between final client and Convertigo?

Hello HUG!

According to me, the only thing you have to take care is to correctly setup your web service client stub.

For example, if you work with Java and Axis, once you have created the Java stub for the Convertigo web services you want to call, you must call the stub's setMaintainSession(true) in order to tell the stub to maintain the session between the different WS calls.

You also have to create as many stub instances as concurrent sessions you want to have, of course!

In web services, the session concept is maintained "thru the protocol".

With this procedure, thus, your server will be seen as several clients from Convertigo's point of view.

Hope this helps!