Session infos

When a user connects to the version 7 platform, it opens a connection that can be viewed with the list of sessions that are part of the administration pages. The version 7 web platform connects to several endpoints if necessary and acts as a proxy.

This function allows the listing of the connections, to display their characteristics and to force a disconnection.

Different properties of a session

A session has the following properties:

Session ID

This ID uniquely identifies the web session. For a given browser and a given IP address, only one session is created. If two tabs are present or two windows using the same browser on a workstation, there is a unique session ID assigned (it follows the rule of assignment of the session cookies).

User name

The code identifies the user code that was used for the connection. Note that this user is unique for a session. This means that a user who triggers the logout function on a tab will have to login on the first tab he will use.

Last user access

This is the date and the time of the last exchange between the client and the Version 7 web server.

Server name

This identifies the Version 7 web server that manages the session. The following cases are possible:

• If the node.js server has been started directly (without load balancer) on the server that is called myhost at the TCP port port, the name found will be myhost:port. For example, it can be localhost:8124
• If the load balancer is used and the session is executed on the server myhost, it is myhost, followed by :N. The internal process number can be server:N0 for the process with number 0 (first process) or server:N4 for the process with number 4 (fifth process).

Badge

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

For example, let's imagine that the badge ACCOUNTANT is associated with the role CFO. When user X is connected with the CFO role, ACCOUNTANT will appear on the line. If the user license grants 5 ACCOUNTANT badges, the number of sessions connected with the CFO role will be limited to 5 or less if the ACCOUNTANT badge is associated with other roles.

Client ID

This 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 last URL used by the session. If the session you look for is the current one, you will see the URL /sdata/syracuse/collaboration/sessionInfos?representation=sessionInfos.$query&count=... (ie. the page that corresponds to the query sent to know the list of sessions just before reading the current page).

Client ID

Lists the process id associated to the X3 sessions run for the web server session. If classic pages have been used, at least two processes are present, but it can be more (if several tabs are opened for classic pages).

Client ID

Contains the IP adresse of the client browser connected.

SAML Name ID

When a a SAML authentication is used, this field contains the name id of the connection.

SAML Session

When a a SAML authentication is used, this field contains the session id of the SAML connection.

Icons present when log has been activated

By using the corresponding operations (see above), it is possible to log the execution of the V7 style code. A similar operation is possible for classic pages linked code from the Classic session administration page. When this log has been run, three types of information can be displayed through icons present on the following fields:

CPU graph

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

Log

This icon extracts all instructions executed for the session during the activation period, and displays them in a dedicated page. The page looks like this:

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 access to the memory dump of the X3 server at the end of the last X3 log activation period). The result corresponds to the format generated by the heapdmp instruction.

Operations available

Disconnect operation

If the user is allowed, a disconnection can be forced by this operation. The connection is then lost and the user has to re-authenticate to open a session. The disconnection link is present on the line of the query and on the detail page (right list of actions).