This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

arsignal.exe or arsignal

In this topic:

arsignal description

The arsignal utility forces an BMC Remedy AR System server to load or reload information. The process can be run on any computer.

arsignal synopsis

arsignal {-a | -b | -c | -d | -e | -g | -l | -m | -p | -r | -u}
serverName[:port][sigArgument]

The server name identifies the server that is to reload information. If a TCP port is to be specified as well (needed if the server does not register with AR System Portmapper), it is appended to the server name, separated by a colon. The string sigArgument is applicable when using the -a, -d, -p, or -u options.

arsignal options

You can specify one of the following options:

-a — Causes the server to update internal Alert user information based on the details provided in sigArgument. See Configuring a hardware load balancer with BMC Remedy AR System.

-b — Causes the server to recache and reload archive definitions.

-c — Causes the server to reload information from its configuration file *ar.conf* (ar.cfg).

-d — Causes the server to transfer the signal to a DSO process.

-e — Causes the server to recache and reload escalation definitions.

-g — Causes the server to reload group and data dictionary information from the database.

-l — Causes the server to reload license information.

-m — Causes the server to reload computed group information.

-p — Causes the server to transfer the signal to an application process.

-r — Causes the server to recache definitions from the database.

-u — Causes the server to reload user information.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments