![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Real-time transactions: When real-time transactions are used, all requests will be immediately executed by the CMI Protocol engine. The real-time transactions between private processes and CMI Protocol are called sessions.
• Batch transactions: When batch transactions are used, all data access requests are initially stored by the CMI Protocol engine. Later, the batch can be executed or cancelled by sending a special request from the private process or via the message queue logs from the Log Viewer.
• Explicit sessions: During an explicit session, login or logout requests are initiated in order to start or to terminate a session. Each login request contains client’s identity information. Once this identity is accepted and session established, any following requests carry only the sessionID.
• Implicit sessions: During an implicit session, each request is initiated with the client's identity information. CMI Protocol creates such session on-the-fly, executes operations, and terminates the session once the response is sent.
• Session Timeout: For security reasons, each user session will time out, and each sessionID will become invalid after a configurable time period.If a session times out, CMI Protocol updates the audit log entry to status COMPLETED WITH ERRORS, sends an ADVISORY message to the private process, and removes the session content. Any following incoming requests using the timed-out sessionID will trigger an error message.
1. Select BusinessConnect > System Settings > Activated Protocol Plug-ins and Properties.
2. Click on the CMI link.
3. In the dialog Edit Plug-in Properties: CMI enter the time interval for session expiry in the window cmi.sesson.expiry. Default is 1800 seconds.
4. Click Save to save the session settings.CMI Protocol will interpret a transaction request to be of the type batch if a property batchID is defined in AESchema. All requests with the same batchID will be executed one by one, according to the sequence in which they have been received. Batch transactions follow these rules:
• Allowed actions for batch transactions are EXECUTE and CANCEL (used to execute or cancel a batch execution).For each batchID, you will be able to see a record with information such as how many requests are in the batch. You can then decide whether to execute or cancel such a batch.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |