User Monitor
This function is used to view the different Adonix tasks in process on the server. By default, the current process server tasks are displayed, but any server accessible via the network that has a software connection process with the same service number can be accessed.
Prerequisite
Refer to documentation Implementation
Screen management
This function is presented as a single screen without a left list.
Entry screen
Presentation
On entering this function, the connection characteristics for the default server are displayed. If the user wants to view the connections on another server, it is necessary to give its name. It will be possible to view it provided the service number is the same as the remote server.
In this screen, three data sections are displayed.
Open sessions
This first section contains a grid named Open sessions, which displays the characteristics of the Adonix tasks in process :
the identification of the connection in terms of the operating system. This identification is defined by four items of information : the login (in the sense of the operating system), the service connection number (characteristic of the adxdtask to which the workstation that is attached to the connection request.), the IP address for the connection and the name of the client workstation.
This latter information is either the network name of the client workstation to which the task is attached or the ADAPI (connection to an Adonix API, for example via ADONIX XTEND™), or BATCH (batch task). If the connection is made via a Web server (it is the case when using a Web client), it is the name of the Web server that is displayed here.
the folder, the login for the software, the module, the function. This information identifies the context of the session itself, that is to say both the connection folder and the user code (AUTILIS table), plus the function that is currently being executed (AFONCTION) table and the corresponding module. If the user in a menu rather than a function, the function code is empty.
The batch server itself is present as a task called SERVEUR, functioning in the folder SERVX3.
the date and time of the connection start.
the Ident1 and Ident2 fields are unique identifiers managed by the Adonix engine for the user connection. The first is unique for a given folder, it corresponds to the result of the evaluation of the adxuid(1) function and is used in the APLLCK file (this is the LCKPID field). The second is unique for a given server and service number, it corresponds with the result of the evaluation of the adxuid(2) function.
the connection type (batch, primary, secondary, or ADAPI).
Active processes
The grid present in the second section displays, when the user selects a specific line in the upper grid (Open sessions), the active processes managed for the session. These processes are called sadora, sadoss, or sadudb (access the database according to the Oracle, SQLServer or DB2 UDB database), of the type adonix (process execution), sadfsq (access to the application objects), sadsys (system order execution). In addition to the process number (UNIX or NT according to the case), the server name on which the process is running is also displayed (this can be the client, the server or a third party machine if for example there are tables open in another folder on another machine).
By right click, there is access from each line in this grid, to the Process stop function, which can be used to stop the corresponding process(by kill under UNIX, by the killadx function under NT). From the point of view of the database, the stopping of a process not only signifies the actual stopping of the transaction in process but also the loss of data in the process of being entered. It is therefore important to be very careful with the use of this function, which is reserved for the resolution of operational incidents. In fact, the rights of the user to carryout this type of function depend on the characteristics of the user connection. If a user wants to stop tasks that they have not themselves launched, they must be connected as a super-user (root in the case of UNIX).
Session totals
This section displays the number of active sessions by session types (primary, secondary, batch, ADAPI) along with a general total. In addition, after each session type the total number of connections authorised by type is displayed (in italic and within brackets).
Close
Fields
The following fields are present on this tab :
Block number 1
| Define the process server on which the processes are viewed. By default, the server that is proposed when starting the function is the current application server. |
| Define the license number assigned by Sage for the installation. This license number is unique. It is associated with a group of authorizations (umber of sessions, options...) as well as two series of texts identifying the user client for the license and the partner that has implemented the solution. A dedicated function to view all this information. |
Table Open sessions
| Define the network name of the workstation used to establish the connection for the session. It should be noted that this network name can be :
|
| Defines the connection type of the current session It corresponds to one of the choices defined in local menu 924. |
|
|
| Defines the user code (in the software sense) under which the session has been opened. |
| Define the folder in which the current session is executed. |
| Define the module to which the function that is being executed is attached. The list of modules vary according to the software. It corresponds to local menu number 14. |
| Define the code for the function executed by the connected user. This code corresponds to the value of the GFONCTION variable on the workstation itself. If the user is connected without being in this function (if they are positioned in a menu), this field is empty. It should be noted that the batch server itself is present as a task called SERVEUR, functioning in BATCH mode on the folder where the name depends on the software, but which start in principle with the letters "SERV". |
| Define the user code (in the system login sense) in which the connected user is known. |
| Define the connection service number (characteristic of the adxd task to which the workstation is attached at the connection request). |
| Define the date and time of the start of the connection to the workstation. |
|
|
| Display the CPU time used by the adonix process from its startup. This time is expressed in minutes:seconds |
| The Ident1 and Ident2 fields are unique identifiers managed by the Adonix engine for the user connection. The first is unique for a given folder, it corresponds to the result of the evaluation of the adxuid(1) function and is used in the APLLCK file (this is the LCKPID field). The second is unique for a given server and service number, it corresponds with the result of the evaluation of the adxuid(2) function. |
|
|
Table Active processes
| For each process associated with the current line session in the upper grid, a unique process number is found here linked to the server on which this process is executed (it is aprocess idoperating system sense, whether UNIX, Linux or Windows). |
| Defines the name of the processes being executed on the process server corresponding to the current session in the upper grid. Amongst the names frequently present on line are the following :
|
| Identify the computers on which each process operates associated with the current session in the upper grid. It can be one of the network servers (notably the process server, the application server, but also the client workstation, in the case for example when writing on the local workstation : a sadfsq process is then open on the workstation). |
Total sessions
| Gives the total number of primary sessions currently connected to one of the folders managed by the application server. A primary session is a session directly opened by a user, whether in client server or Web mode. |
| Define the maximum number of authorized sessions corresponding to the license to the user. |
| Gives the total number of secondary sessions currently connected to one of the folders managed by the application server. A secondary session is a session opened from an already active primary session, in order to allow the user to have a second active window available on the same folder and with the same user code as the corresponding primary session. |
|
|
| Gives the total number of batch sessions currently connected to one of the folders managed by the application server. A batch session corresponds to the execution of a task in the background, which can notably carryout updates or print reports. The functioning of the batch server is defined in an annex documentation. |
|
|
| Gives the total number of Web service type connections one of the folders managed by the application server. A Web service connection is a connection established from a connection pool managed by a Web server, which responds to the solicitations coming from external processes. |
|
|
| Gives the total number of portable terminal type sessions currently connected to one of the folders managed by the application server. A portable terminal type session is a session open on a VT type terminal, via the intermediary of a terminals server managed by a Web server. |
| Define the maximum number of authorized sessions corresponding to the license to the user. |
|
|
|
|
|
|
|
|
| Gives the total number of sessions (irrespective of their type) currently connected to one of the folders managed by the application server. |
|
|
Close
Functions accessed by right click on the grid
Menu Bar
This button, also accessible using the short cut , is used to refresh the display of the open sessions. |
Menu Bar
Sort / Folder
This function is used to sort the lines in the order of the folders.
Sort / Client
This function is used to sort the lines by order of client workstation.
Sort / Login
This function is used to sort the lines in order of the connection code.
Sort / System Login
This function is used to sort the lines in order of the connection code in the system sense.
Sort / Date
This function is used to sort the lines in order of the date.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
xxxx : server not accessible
This message signifies either that the server whose name is given does not exist or that it is not connected to the network or that no adxd connection service is pending for the current service number. Warning, this message can be displayed after a long wait time (the time that the wait times give to the network functions needs to elapse).