Difference: APPXSessionMonitor (15 vs. 16)

Revision 162017-03-29 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPX500Features"

APPX Monitor

Line: 12 to 12
 

How to Enable the APPX Monitor Feature

To enable the APPX Monitor feature, each APPX session that is to be monitored must have two environment variables set at the time that the session is initiated. Any APPX session does not have these two environment variables set will simply not be displayed on the APPX Monitor display. The APPX License Server session should also have these two environment variables set.

Changed:
<
<
APPX_MONITOR_KEY=<key_number>
>
>
APPX_MONITOR_KEY=<key_number>
  APPX_MONITOR_SLOTS=<session_count>

The easiest way be ensure that these environment variables are set for all APPX sessions including the APPX License Server session is to define them in the appx.env configuration file. Simply add the two environment variables to the appx.env file with appropriate values. The example below assigns a key value of 1234 for the shared memory segment and specifies that the shared memory segment should be large enough to hold the status information for 100 APPX sessions.

Added:
>
>
 
Changed:
<
<

#============================================================================= # APPX Monitor configuration #============================================================================= APPX_MONITOR_KEY=1234 APPX_MONITOR_SLOTS=100

>
>
#============================================================================= # APPX Monitor configuration #============================================================================= APPX_MONITOR_KEY=1234 APPX_MONITOR_SLOTS=100
 

APPX_MONITOR_KEY Environment Variable

Line: 37 to 33
 

APPX_MONITOR_SLOTS Environment Variable

Changed:
<
<
The APPX_MONITOR_SLOTS environment variable defines how many "slots" should be allocated in the shared memory segment for the APPX Monitor. The minimum number of slots should correspond to the maximum number of APPX sessions ever run on your APPX server. For example, if you have 30 licensed users and each user runs no more than two sessions at a time, you should specify a value of at least 61. The following formula can be used to ensure that you allocate a sufficient number of slots:
<session_count> = <licensed_users> * 4 + 1
>
>
The APPX_MONITOR_SLOTS environment variable defines how many "slots" should be allocated in the shared memory segment for the APPX Monitor. The minimum number of slots should correspond to the maximum number of APPX sessions that could be run on your APPX server. For example, if you have 30 licensed users you should specify a value of at least 120 (each user can run as many as 4 sessions). The following formula can be used to ensure that you allocate a sufficient number of slots:
<session_count> = <licensed_users> * 4 + 1
  When the APPX Monitor's shared memory segment is created, it will always be created with the number of slots being a multiple of eight. If you specify a <session_count> that is not a multiple of eight, the number of slots allocated will be increased to the next multiple of eight.
Added:
>
>
Warning: Setting this too low will result in unpredictable behaviour! Use the forumla above as a minimum value. Add more slots if you routinely run background jobs as well as foreground sessions. There is no drawback to setting this higher than you need.
 

How to Run the APPX Monitor

The APPX Monitor status display process can be run from within APPX System Administration.

Changed:
<
<
System Administration --> System Setup --> Monitor APPX Sessions
>
>
System Administration --> System Setup --> Monitor APPX Sessions
  If the APPX Monitor feature has been properly configured, the APPX Monitor process should display a screen similar to the one below.
Changed:
<
<
Monitor.PNG
>
>
Monitor.PNG
 

The Role of the APPX License Server

The license server cleans up orphaned entries in the APPX Monitor's shared memory segment. When an APPX session terminates normally, it removes its entry from the APPX Monitor's shared memory segment. However, if an APPX session crashes or is otherwise abnormally terminated, the session's entry will be left in the APPX Monitor's shared memory segment. The APPX License Server session periodically identifies and removes entries for APPX sessions that are no longer running from the APPX Monitor shared memory segment.

Line: 60 to 58
 

Command to List Shared Memory Segments

The following command can be used on a Unix/Linux system to list the shared memory segments that have been created on the server:

Changed:
<
<
ipcs -m

>
>
ipcs -m

 

In the example below, the shared memory segment with an owner of "appx" is the shared memory segment for the APPX Monitor. The key value can be used to identify the shared memory segment of the APPX Monitor. In this case, the key value of 0x000004d2 is the hexadecimal equivalent of a decimal value of 1234 which is the value that we assigned to the APPX_MONITOR_KEY environment variable.

Changed:
<
<
icpsCommand.PNG
>
>
icpsCommand.PNG
 

Command to Remove Shared Memory Segment

In the event that your APPX server has a problem related to the APPX Monitor's shared memory segment, you can remove the APPX Monitor's shared memory segment. The following command can be used on a Unix/Linux system to remove a shared memory segment.

Changed:
<
<
ipcrm -m <shmid>

>
>
ipcrm -m <shmid>

 

The appropriate value for <shmid> can be determined by listing the shared memory segments on your server to identify the APPX Monitor's shared memory segment.

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback