Difference: APPXSessionMonitor (9 vs. 10)

Revision 102008-09-24 - SteveFrizzell

 			 META TOPICPARENT 
			 name="APPX500Features"
- META TOPICPARENT
+ name="APPX500Features"
-<
<
  APPX Monitor 
Effective with Release 5.0.0, APPX System Administration includes a utility that allows an APPX System Administrator to monitor all APPX sessions .
  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.  Any APPX session does not have these two environment variables will simply not be displayed on the APPX Monitor display. The APPX License Server session should also have these two environment variables set.
-<
<
+APPX_MONITOR_KEY=<key_number>
APPX_MONITOR_SLOTS=<session_count>
->
>
+ 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 assigned 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.
->
>
-<
<
+#=============================================================================
->
>
+#=============================================================================
 # APPX Monitor configuration
#=============================================================================
APPX_MONITOR_KEY=1234
APPX_MONITOR_SLOTS=100
->
>
+ APPX_MONITOR_KEY Environment Variable 

The APPX_MONITOR_KEY environment variable defines the IPC (interprocess communication) key of the shared memory segment in which the APPX session information is stored.  The <key_number> that you assign to the APPX_MONITOR_KEY environment variable must be a number and must not already be in use by any other shared memory segments that may exist on your system.  You should list the shared memory segments for your system and choose a key value that is not already in use. 

Each APPX session updates the shared memory segment with information relating to which APPX process is being run and the status of the process. The APPX Monitor reads the shared memory segment to obtain and display the information for each APPX session.  

 
 APPX_MONITOR_SLOTS Environment Variable 

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
  How to Run the APPX Monitor
 If the APPX Monitor feature has been properly configured, the APPX Monitor process should display a screen similar to the one below.
-<
<
+ APPX_MONITOR_KEY Environment Variable
->
>
+ The Role of the APPX License Server 

The license server cleans up orphaned entries in the 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 terminated without ending normally, the session's entry will be left in the APPX Monitor shared memory segment.  The APPX License Server session periodically identifies and removes entries for APPX sessions that are no logner running from the APPX Monitor shared memory segment.  
 Managing Share Memory Segments 

Under ideal conditions, once you have configured the APPX Monitor feature, there should be no need to be concerned with shared memory segments.  However, in the event that you do encounter a problem that is somehow related to the shared memory segment there a couple of things you can do.  First, you can reboot your server.  Rebooting the server removes all shared memory segments and will clear any problems that might be related to a shared memory segment.  However, if you don't want to reboot your server, there are two commands on Unix/Linux systems which you may find useful for managing shared memory segments.  One command will list the shared memory segments that exist on your server.  There other command can be used to remove a shared memory segment. 

 
 Command to List Shared Memory Segments
-<
<
+The APPX_MONITOR_KEY environment variable defines the IPC (interprocess communication) key of the shared memory segment in which the APPX session information is stored.  The <key_number> that you assign to the APPX_MONITOR_KEY environment variable must be a number and must not already be in use by any other shared memory segments that may exist on your system.  On a Unix/Linux system, the shared memory segments can be displayed by executing the following command:
->
>
+The following command can be used on a Unix/Linux system to list the shared memory segments that have been created on the server:
 ipcs -m
-<
<
+Each APPX session updates the shared memory segment with information relating to which APPX process is being run and the status of the process. The APPX Monitor reads the shared memory segment to obtain and display the information for each APPX session.  
 APPX_MONITOR_SLOTS Environment Variable
->
>
+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.
-<
<
+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:
->
>
+ 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.
-<
<
+<session_count> = <licensed_users> * 4 + 1
->
>
+ipcrm -m <shmid>
-<
<
+ The APPX License Server
->
>
-<
<
+The license server cleans up orphaned entries - if you don't want to clutter up your monitor table with crashed sessions, make sure you define APPX_MONITOR_KEY and APPX_MONITOR_SLOTS before starting the license server. (Of course, if an engine exits gracefully, it removes itself from the monitor table so the license server will only clean up orphans).
->
>
+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.
  Concerns 
From Pete Brower:
   (Edit - Preview)
 
<--/commentPlugin-->
-<
<
+-- AlKalter - 04 Apr 2008
->
>
+-- AlKalter - 04 Apr 2008 
 

 icps Command on Linux:
 			 META FILEATTACHMENT 
			 attachment="Monitor.PNG" attr="h" comment="Monitor Running Sessions" date="1222260660" name="Monitor.PNG" path="C:\Documents and Settings\steve\My Documents\My Pictures\Monitor.PNG" size="31065" stream="C:\Documents and Settings\steve\My Documents\My Pictures\Monitor.PNG" user="Main.SteveFrizzell" version="1"
- META FILEATTACHMENT
+ attachment="Monitor.PNG" attr="h" comment="Monitor Running Sessions" date="1222260660" name="Monitor.PNG" path="C:\Documents and Settings\steve\My Documents\My Pictures\Monitor.PNG" size="31065" stream="C:\Documents and Settings\steve\My Documents\My Pictures\Monitor.PNG" user="Main.SteveFrizzell" version="1"
->
>
+			 META FILEATTACHMENT 
			 attachment="icpsCommand.PNG" attr="h" comment="icps Command on Linux" date="1222281339" name="icpsCommand.PNG" path="C:\Documents and Settings\steve\My Documents\My Pictures\icpsCommand.PNG" size="21713" stream="C:\Documents and Settings\steve\My Documents\My Pictures\icpsCommand.PNG" user="Main.SteveFrizzell" version="1"
- META FILEATTACHMENT
+ attachment="icpsCommand.PNG" attr="h" comment="icps Command on Linux" date="1222281339" name="icpsCommand.PNG" path="C:\Documents and Settings\steve\My Documents\My Pictures\icpsCommand.PNG" size="21713" stream="C:\Documents and Settings\steve\My Documents\My Pictures\icpsCommand.PNG" user="Main.SteveFrizzell" version="1"

View topic | History: r17 < r16 < r15 < r14 | More topic actions...