The Application Window
Status Tab
Monitoring Interval Tab
Last Data Tab
Status Bar
Configuring Applications
The Application Window contains all information for a single
application within Isis.
Each Application window displays
the name of the application in the title bar for the window.
The window contains four key areas: the Status tab, the Monitoring
Interval tab, the Last Data tab and the status bar.
The Status Tab displays information regarding the application's
current status.
The application's current status. An application's status can
be one of three values:
| Connected |
|
The application is currently connected
to the application being monitored. |
| Disconnected |
|
The user has disconnected the application
from the application being monitored. |
| Error |
|
An attempt has been made to connect
to the application being monitored, which has failed. |
Displays the frequency with which Isis will sample data from
the application being monitored, in seconds. The monitoring
period for an application must in the range 10-3600 seconds.
If monitoring is currently disabled for the application, the
Monitoring Period will appear as 'N/A'.
Displays the time at which the next set of data will be sampled
from the application. If monitoring is currently disabled
for the application, the Next Monitoring time will appear
as 'N/A'.
top of page
The monitoring interval tab allows the user to both enable
and disable monitoring, but also defined the amount of time
between each monitoring period.
To adjust the monitoring settings for an application at runtime,
select the Monitoring Interval tab on the Application window.
To disable monitoring for an application, un-check the Perform
Monitoring? checkbox and click Apply and the monitoring will
now be disabled.
To enable monitoring for an application, check the Perform
Monitoring? checkbox, and enter the monitoring period for
the application (in seconds) in the Polling Period (secs)
field.
The monitoring period for an application can be between 10
and 3600 seconds (one hour). If monitoring is enabled for
an application, each time the monitoring period for an application
passes (eg. every 10 seconds if the monitoring period is 10)
Isis will check that the application is currently connected.
If it is currently connected, then Isis will poll the application
being monitored and sample important data indicating the application's
current load.
The Monitoring Interval Tab allows the user to configure monitoring
settings for the application.
This checkbox allows the user to control whether monitoring
is performed for the current application. If the checkbox is
ticked, then the user may enter a polling period (in seconds)
in the field below. If the checkbox is un-checked, then the
entry field below is non-functional.
If the Perform Monitoring checkbox is checked, the user may
enter a polling period (in seconds) in this entry field. The
information entered must be a number between 10 and 3600, indicating
a polling period which can be from 10 seconds to 1 hour.
To affect a change in the monitoring settings for an application,
click the Apply button. When the Apply button is clicked, the
new monitoring period will take effect and Isis will perform
monitoring immediately. This information is also summarized
in configuring Monitoring.
top of page
The Last Data Tab shows the last batch of data sampled from
the application, if any. Monitoring data will only be displayed
for monitoring performed during the current Isis session.
The data gathered from monitoring is displayed in a scrollable
list. The name of each object or function being monitored is
shown in the first column, and the value when last fetched is
shown in the second column.
This displays the time that data was last successfully fetched
by runtime monitoring. If no data has successfully been fetched
during the current session, this will appear as 'N/A'.
This displays the next time that Isis will perform runtime monitoring.
Note: If monitoring is enabled for the current application,
and the application is disconnected, the Next Fetch time will
continue to update as Isis moves through each monitoring period.
If the application is connected successfully, Isis will update
the Last Fetch time immediately after successfully performing
monitoring.
top of page
The status bar appears the bottom of the Application window,
and displays any messages particular to that application.
For example, if an application was performing runtime monitoring
and experienced an error, a message would appear in the status
bar for that application informing the user that 'Monitoring
failed to return data'.
Note that the status bar for an application window only displays
information particular to that application - any information
or error message that is related to the application as a whole
is displayed in the status bar for the main window.
top of page
Configuring connection settings Before an application can be
monitored, connection settings for that application must be
configured so that Isis can connect successfully to the application
being monitored.
To configure connection settings for an application, select
Application / Connection Settings from the menu. Isis will also
prompt the user to configure connection settings for a new application
once it is created, and if the user attempts to connect to the
application.
The connection settings dialog will appear different for each
application type, as each application type requires different
information in order to connect and perform monitoring.
If the application that you are trying to configure is Tuxedo
application, the following dialog will appear.
In order to configure connection to a Tuxedo application, a
number of pieces of information must be supplied.
| WSNADDR |
|
The listen address of the Workstation
Listener for the Tuxedo application. To confirm this value,
refer to the UBBconfig for the relevant Tuxedo application. |
| Username |
|
This should be set to Isis, but
any value may be supplied. |
| Clt. Name |
|
The client name must always be set
to 'tpsysadm'. |
| Password |
|
The application password for the
Tuxedo application. Or, if ACLs are in use, the password
for the 'tpsysadm' user. |
The information entered can be tested by clicking the 'Test
Connection' button.
Isis will attempt to connect to the application using the information
supplied, and will display the result of the test in the status
bar for the Connection Settings dialog.
For more information regarding troubleshooting connection to
a Tuxedo application, refer to
If the application that you are trying to configure is WebLogic
application, the following dialog will appear.
In order to connect to a WebLogic application, there are a number
of pieces of information that must be supplied.
| Host address |
|
The IP address of the machine the
WebLogic application is running on. |
| Community name |
|
This should always be set to 'public'
by default. If you have adjusted the SNMP community name
in the WebLogic configuration, then the community name
provided here must match. |
| Timeout (msecs) |
|
The amount of time in milliseconds
Isis should attempt to connect to the application being
monitored. |
| Connection retries |
|
The number of times Isis should
attempt to connect to the application before failing. |
Note that the total amount of time Isis will take to attempt
to connect to an application will be the timeout value multiplied
by the number of connection retries, with a small overhead on
top of that total.
The information entered can be tested by clicking the 'Test
Connection' button. Isis will attempt to connect to the application
using the information supplied, and will display the result
of the test in the status bar for the Connection Settings dialog.
While Isis attempts to connect to the application, the OK and
Cancel buttons will be temporarily disabled.
Once Isis has determined whether the connection attempt succeeded
or failed, the buttons will be enabled again.
For more information on troubleshooting connection to a WebLogic
application, refer to the Isis troubleshooting guide.
top of page
|
