Configuring AR Server Systems

AR environment

Specify a user-defined unique name for the Remedy AR Server environment you want to monitor.

Remedy server name

Specify the Remedy AR Server name you want to monitor. You can either specify the actual server name or an alias name.

Note: Information about some System forms belongs to the core of the Remedy server. To enable the KM to collect data about such System forms, you must have AR Administrator privileges with read and write permission on the Remedy AR Server.

Override server IP

(Optional) Specify the IP address of the Remedy AR Server. 

 If you have specified an alias name in the Remedy server name field, then you must specify the IP address of the Remedy AR Server in the Override server IP field.

Port number

 Specify the port number for the Remedy AR Server connection.

User name

Specify the user name with which you login to the Remedy AR Server. The user license must be of type 'Fixed'.

Password

(Optional) Specify the password you use for logging into to the Remedy AR Server.

Authentication

(Optional) Specify the authentication token.

Connection type

Select an option to either monitor a single server or all the servers in the group:

• Single server connection (non-admin user): Select this option to monitor a single AR server. Administrator rights are not required for monitoring a single server. If you select this option, you must setup the monitoring details for each server separately.
• Group connection (admin user): Select this option to monitor all the AR servers within a single group. Administrator rights are required to connect to the monitored AR system.

AR monitor label

Enter a unique user-defined label for the Remedy AR Server System form you want to monitor. 

Add to List

Click this option for adding the Remedy AR Server System form in the list.

Modify Selection

Click this option for modifying the added Remedy AR Server System form.

Remove from List

Click this option for removing the added Remedy AR Server System form.

JAVA_HOME

Specify the Java Home directory.

The environment variable, Java home or operating default, JAVA_HOME will be used by leaving this field empty. (Not all patrol agent version are shipped with JRE.)

Activate debug

Select this option to enable logging. The log files are created at %PATROL_HOME%\logs\AR-KM-AR_Environment_Name-PATROL_Agent_name and%PATROL_HOME%\arskm\logs\java\ArsKM-AR Environment_Name.

Enable device mapping

Select this check box for displaying monitor instances as devices on the Operations console.

By default, this option is enabled

Default JAVA_HOME

Specify the Java Home directory as a global configuration for all environments running on the specified PATROL Agent.

Global KM debug

Select this option to enable logging for all environments running on the specified PATROL Agent.. The log files are created at %PATROL_HOME%\logs\AR-KM-AR_Environment_Name-PATROL_Agent_name and%PATROL_HOME%\arskm\logs\java\ArsKM-AR Environment_Name.

Add to List

Click this option for confirming the configuration information that you provided.

Modify Selection

Select one of the items that you added to the list in the preceding step, and click this option to modify details.

Remove from List

Select the items added earlier and click this option to delete that item from the list of configured objects and to clear the details provided in the earlier fields.

Reset

Click this option to clear off your configuration details and revert to default settings.

Add

Add Click this option to add this monitoring configuration. This information is displayed on the Monitor Configuration.

After you click this option, you can continue to add more objects for monitoring.

Close

Click this option to exit without saving any changes.