Sessions information
| Administration Page | Application/Contract | Syracuse/Collaboration | Class | sessionState | Representation | sessionState |
|---|
When a user connects to the platform, it opens a connection that can be viewed with the list of sessions that are part of the administration pages. The web platform connects to several endpoints, if necessary, and acts as a proxy.
This function displays the list of connections with the associated X3 sessions to display their characteristics and force a disconnection.
| Different properties of a session | Operations | Services |
The type of connection, which could be Standard, related to an end user connection; Batch, related to the batch server; or SOAP, related to the SOAP web services.
Identifies a unique ID for the web session. For a given browser and IP address, only one session is created. If two tabs are open, or if two windows using the same browser on a workstation are open, a unique session ID is assigned. It follows the assignment rule of the session cookies.
Identifies the user code that was used for the connection. Note that this user code is unique for a given session.
Identifies the exact status of the session in the authentication or disconnection process.
Contains the IP address of the client browser connected.
Identifies the web server that manages the session.
If the load balancer is used, the process number is mentionned with this Pid.
Identifies the endpoint and the X3 login.
Indicates the number of X3 sessions that are associated with the web server session.
Detailed information on those X3 sessions displays when the line is expanded or by clicking the value.
Identifies a list of badge values (usually one). A badge is a code that represents a resource available in the user license and is associated with a role. The badges listed are used and deducted from the stock allowed by the license.
Example: The ACCOUNTANT badge is associated with the CFO role. When user X is connected with the CFO role, ACCOUNTANT is displayed on the line. If the user license grants five ACCOUNTANT badges, the number of sessions connected with the CFO role is limited to five or less if the ACCOUNTANT badge is associated with other roles.
Shows the date and time of the latest exchange between the client and the web server.
Displays the date and time when the session expires if there are no additional exchanges. The delay corresponds to the session timeout defined in the nodelocal.js file plus 5 minutes.
Two tabs can be displayed if the line is expanded.
Displays detailed information on the X3 sessions that are associated with the web server session.
Displays the latest URL used by the session.
Authorized users can force a disconnection by clicking Disconnect. The connection is then lost and the user has to re-authenticate to open a session. The Disconnect action is available from the query line or from the details page.
From version 2018.R3, you can activate the session trace from the Web client sessions page. Click the Actions button of the session you want to trace and click Activate session trace. You can then select the error levels for each code. Five levels are available:
By default, all traces are stored in the logs folder for Syracuse. You can change this default folder in the nodelocal.js configuration file by changing the logpath attribute in the collaboration section.
The following services are available from the right panel:
Link to the Lincense usage information page.
This page displays all the X3 sessions that are known from the web server.
It should correspond to the list of the sessions displayed in the User monitoring entry menu (APSADX) for the entie X3 Solutions.
The service Unknown X3 sessions displays the sessions that are in the APASADX function and not on the X3 sessions page. Those sessions have to be checked in the APSADX function because they could be ghost sessions.