Supervisor Administration Process Management

This page is used to access the different Sage X3 connected processes on the Sage X3 solution associated with the current endpoint. It shares similarities with the PSADX function in the version 6 client but it does not allow you to kill sessions. If you ever need to kill sessions, the PSADX function is still available and it allows you to do so.

1. Process list

When the page is launched, a list of processes appears, including the following information:

Ident 1

This is the unique identifier of a process. It corresponds to the value obtained by function adxuid(1) when executed by the process.

Client workstation

Gives the IP address of the client. Can also be "BATCH" if the process has been started by the Sage X3 batch scheduler.

Login

Corresponds to the login code of the Sage X3 process.

Folder

This is the folder that the Sage X3 process is connected to.

Service

The IP service used to connect to the Sage X3 folder. Several services can access the same solution.

Module and function

The application module and the function currently executed by the process. The function can be:

• A Sage X3 version 6 function code when a function works in "classic" mode.
• A representation code called "R_xxxx", where "xxxx" is the code of the representation. For example, as the process management function runs with the APSADX representation, there should be at least one "R_APSADX" function on the list.

System login

The login code used to connect to the server.

Date and hour

The date and hour of creation of the session.

Type

The type of connection, which can be either:

• Primary: Default connection used in most cases.
• Batch: Connections initiated by the batch server to execute Sage X3 tasks in the background.
• Eclipse: Connection from the Eclipse editor that corresponds to the Console view in which calculations can be done.

On environments where version 6 folders still exist, you can also have some other connection types:

• Secondary: Secondary connections.
• Java Bridge: Connection initiated from Java Bridge (reserved for some specific applications).
• Web services: SOAP Web services connection.
• Terminal: Terminals connection.

2. Process details

When clicking the process identifier (Ident 1) on a line in the query page, the detail of the process appears. The information within the query is displayed, as well as the following elements.

CPU

Gives the CPU time spent by the process.

Ident 2

This is the unique process identifier. It corresponds to the value obtained by function adxuid(2) when executed by the process.

Process list

This grid displays the list of processes associated with the connection that are executed on the server. Usually, there are at least two processes:

• adonix, which corresponds to the Sage X3 code execution process.
• sadora or sadoss, which correspond to the database driver.

Additional processes can exist:

• sadsfq when sequential system files are accessed.
• sadsys when system calls have been done.

For these processes, the process ID is listed, as well as the server on which it runs. This server can be different from the process server.

3. Cancellation operation

This operation can be run either from a query page by clicking the "X" icon on the line, or from a detail page by clicking Cancel.

It stops the processes that are attached to the current connection. This can only be done if the connection rights enable the user to execute this stop process function. If not, an error log is displayed.