Session infos

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 allows the listing of the connections in order to display their characteristics and force a disconnection.

Properties of a session

Session ID

Uniquely identifies 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.

User name

Identifies the user code that was used for the connection. Note that this user code is unique for a given session.

Last user access

Date and time of the latest exchange between the client and the Web server.

Server name

Identifies the Web server that manages the session. The following cases are possible:

• If the node.js server was started directly (without load balancer) on TCP port "port" of server "myhost", the name is "myhost:port". For example, "localhost:8124".
• If the load balancer is used and the session is executed on server "myhost", the name is "myhost" followed with ":N". The internal process number can be "server:N0" for the first process (number 0) or "server:N4" for the fifth process (number 4).

Badge

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).

Client ID

Uniquely identifies the client browser and is used when the license allows several sessions on the same browser just as if it were a single session.

Last URL

Corresponds to the latest URL used by the session. For the current session, URL /sdata/syracuse/collaboration/sessionInfos?representation=sessionInfos.$query&count=... is displayed.

X3 sessions

Lists the process IDs associated with the X3 sessions run for the Web server session. If "classic" pages are used, there are at least two processes. There can be more if several tabs are opened for "classic" pages.

Peer address

Contains the IP address of the client browser connected.

SAML Name ID

When using SAML authentication, this field contains the name ID of the connection.

SAML Session

When using SAML authentication, this field contains the session ID of the SAML connection.

Icons displayed when the log is activated

By using the corresponding operations, it is possible to log the execution of the code. A similar operation is possible for "classic"-pages linked code from the classic session administration page. After running this log, three types of information can be displayed through icons displayed on the following fields.

CPU graph

This icon gives you access to the flamegraph that displays the CPU repartition generated by the log for the corresponding session. If the log is still enabled, you can extract the latest status of the session by accessing it. More information about flamegraph representation can be found in the corresponding documentation.

Log

Clicking this icon allows you to extract all the instructions executed for the session during the activation period, and to display them on a dedicated page. This page is structured as follows:

channel 3>@SEED.TRT/MYSCRIPT.adx(200) For I=1 To 5 , tick 123channel 3>@SEED.TRT/MYSCRIPT.adx(201) | J+=1 , tick 123channel 3>@SEED.TRT/MYSCRIPT.adx(203) | If I=2 , tick 124channel 3>@SEED.TRT/MYSCRIPT.adx(204) | Call TEST(I) From OTHERSCRIPT , tick 124channel 3>@SEED.TRT/OTHERSCRIPT.adx(18) | | For [TB] Where mod(ABC,I)=3 , tick 124channel 3>@SEED.TRT/OTHERSCRIPT.adx(19) | | | K+=[TB]PROP , tick 125

Memory dump

This icon gives you access to the memory dump of the X3 server at the end of the last X3 log activation period. The results correspond to the format generated by the heapdmp instruction.

Operations available

Disconnecting

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.

Activating or deactivating the session trace

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:

• Error, which traces errors only.
• Warning, which traces errors and warnings.
• Info, which traces errors and warning, and adds information logs.
• Debug, which is more verbose and returns more information.
• Silly, which is the most verbose trace and returns even more information.

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.

You can update your session trace or deactivate it from the Actions button as well.