Forcing cartridge session disconnection.
Article ID: KB0086043
Updated On:
| Products | Versions |
|---|---|
| TIBCO Fulfillment Provisioning | - |
| Not Applicable | - |
Description
Description:
Some Network Elements implement a business session on top of the protocol connection. On occasion, the business session is lost or corrupted though the protocol connection remains valid. In that case it is up to the Dataprocessor to detect and end the cartridge session to trigger a full reconnection (both protocol & business session). This can be done by using the "StopSession" procedure. This procedure disables the cartridge session which will then automatically be re-enabled (as per its own reconnect policy).
Resolution
In order to use the "StopSession" procedure, you should:
- In cartridge type configuration, declare its usage by setting the NVSet parameter "StopSessionAllowed" to "true".
- Call "StopSession" procedure in your trn file in the Post section of the work order.
Example:
//Setting StopSessionAllowed to true .
TRGT:PoolFactory:HLRAlcatelR5
ACT:configure
NVSET:TrnFilePath=./conf/hlralcatelr5.trn|XMLFilePath=./conf/hlralcatelr5.xml|TrnNumFields=1|StopSessionAllowed=true
//Calling the procedure in Post section:
STATE:Activate,AddServices,Post
(...)
CALL_PROC:StopSession
- In cartridge type configuration, declare its usage by setting the NVSet parameter "StopSessionAllowed" to "true".
- Call "StopSession" procedure in your trn file in the Post section of the work order.
Example:
//Setting StopSessionAllowed to true .
TRGT:PoolFactory:HLRAlcatelR5
ACT:configure
NVSET:TrnFilePath=./conf/hlralcatelr5.trn|XMLFilePath=./conf/hlralcatelr5.xml|TrnNumFields=1|StopSessionAllowed=true
//Calling the procedure in Post section:
STATE:Activate,AddServices,Post
(...)
CALL_PROC:StopSession
Issue/Introduction
Forcing cartridge session disconnection.
Feedback
Yes
No
Powered by
