Resolution:
Description:
============
Retrieving a session ID from the network element and then using it in each Work Order / command.

Environment:
============
TIBCO® KPSA - Mobile 3.x
TIBCO® KPSA - Broadband 3.x

Resolution:
===========
The idea is to implement two dataprocessors, one (dataprocessor after) to retrieve the session ID from the response and store it into an attribute, the other one to add it to the Work Order data set before processing (dataprocessor before).

1). DataProcessor After
In order to get a session ID from the network element, the cartridge has to execute a login Work Order. The dataprocessor is called after each step, so its logic is able to extract and parse the value of the provided session ID.

With the value it has to select/retrieve its dataprocessor counterpart and update its session ID attribute.

2. DataProcessor Before
The logic of the dataprocessor before is very simple. If it has a value for session ID, then it simply enriches the Work Order dataset under a specific NVSet key (for example #SESSION_ID).

3). Common Cartridge session key
The cartridge might have several sessions, each of them needing a distinct session ID value. Or there can be different cartridges needing a session ID so many instances of the dataprocessor before. For the DataProcessor After to efficiently retrieve the right dataprocessor before (the one being attached to the same session), the best is to rely on a common unique id : cartridge factory + cartridge type + cartridge instance + cartridge session, for example.

Attachments:
============
simpledp.soc, soc file of dataprocessor source code
simpledp.act, act file of dataprocessor source code
mycart.trn, cartridge TRN file, using the session ID
mycart.tst, create the cartridge with the DataProcessors

Manage a session ID into a Cartridge Session Layer.