Classic client sessions

Administration PageApplication/ContractSyracuse/CollaborationClasscvgSessionsRepresentationcvgSession

A classic session (previously called Convergence session) is a session opened by the node.js server with version 6 protocol on the Sage X3 engine.

The classic session provides the following information:

Client IP

Defines the IP adress of the client that connects on the node.js server. It identifies the workstation or the device from which the connection is done.

User Login

Defines the user entered at login time on the node.js server.

Host

Identifies the host name of the process server in which the classic session connects to access the Sage X3 folder.

Port

Identifies the port used on the process server for the classic session connection to the Sage X3 folder.

Solution

Indicates the solution used on the process server for the classic session connection to the Sage X3 folder.

Folder

Defines the folder in which the classic session is connected.

User

Indicates the Sage ERP user code (defined in table AUTILIS in the folder) that is used for the classic connection.

Lang

Defines the language code (in iso) used for the classic session connection.

PID

Defines the process ID used for the classic session.

Last access

Defines the last time and date when an access was performed to this Sage X3 session.

Time out

Defines the time-out defined for the Sage X3 connection (in seconds).

Reused

If the check box is selected, the session is no longer used by the client that opened it and is waiting to be reused. Typically, this happens when the classic page is closed and you return to the home page, a menu page, or a native version 7 page. This allows you to avoid spending connection time when the user connects again on a classic page (the session will be reused). This type of session will be closed on time-out.

Open

Normally, this check box is always selected.

Http referer

Provides the http address of the node server that connects to the classic sessions.

Creation date

Indicates the date and time of creation for the classic session.

Icons present when log has been activated

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

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

When this link is used, a confirmation is asked. If this confirmation is given, the Sage X3 classic session is closed:

Activate X3 log

This function triggers the log mode for the X3 engine. This mode is global, and will be applicable to all the sessions (V7 like or classic) started after the log activation. Take care that using this mode is consuming additional CPU, memory and disk resources. This should be done only for a short period of time for debugging, profiling and optimisation purposes.

Deactivate X3 log

This function stops the log mode previously enabled. It doesn't stop the log for the running sessions, but the new sessions started will no more fill the log.