Configuring Runtime Alerts

You can configure Unwired Orchestrator to send engine suspension or shutdown alert messages. When runtime alerts are configured and the runtime engine suspends or shuts down, an alert message is created, sent to a JMS transport, retrieved by the Alert Management System (AMS) component of Unwired Orchestrator and sent to the defined target, such as email.  

Two steps are required for runtime alerts to be operational with email: configure agent runtime properties and set up channels for email notification.

To configure agent runtime properties for alerts:

WARNING! Edit this file with caution.

Unwired Orchestrator is pre-configured to initiate and send runtime alerts. This step enables runtime alert functionality.

1. Edit settings in the agent.properties file as follows. The agent.properties file is located in the <server install dir>\config directory.

On the Unwired Orchestrator server, open the agent.properties file and uncomment the name-value pairings so that the lines appear as follows. Default values are supplied for each, such as AMS_IN_QUEUE for the agent.monitor.queue.

Do not uncomment and enter values for the Authenticated JMS Connection Password or Authenticated JMS Connection User Name unless the user and password properties are set for the AMS_IN_QUEUE in EAServer; by default the user and password properties are not set.

### Set to "true" or "false" to enable or disable the monitor
agent.monitor.enabled = true

### Monitor active instance verification frequency (in minutes)
agent.monitor.frequency = 5

### Target alert queue JNDI factory specification
agent.monitor.initialContextFactory = com.sybase.jms.InitialContextFactory

### Authenticated JMS connection password
#agent.monitor.password =

### Target alert queue JNDI provider specification
agent.monitor.providerURL = iiop://localhost:9000

### Target alert queue JMS queue specification
agent.monitor.queue = AMS_IN_QUEUE

### Target alert queue JMS queue factory specification
agent.monitor.queueFactory = javax.jms.QueueConnectionFactory

### Authenticated JMS connection user name (if non-blank)
#agent.monitor.user =
 

2. The Agent must be stopped and restarted for the changes to take effect.

1. For Windows: The AgentLauncher is a local service on your machine. Restart the service based on the method used for the particular operating system running on the machine.

2. For UNIX: Run the shutdown agent script using StopAgent.sh, located in the <install directory>\bin. Restart the Agent using AgentLauncher.sh.

To set up the channels for email notification:

Runtime alerts use a pre-configured channel named Unwired Orchestrator System Management.

1. Connect to the BizTracker Management Console.

1. Open a web browser, Internet Explorer or Netscape.

2. Type the following in the address:

http://<UO_server_machine_name>:8080/BT

The BizTracker Management Console login screen displays.

Notes:
A Java plug-in is required. If the plug-in is not detected, the browser will automatically take you to the download site.


If a connection to the Management Console cannot be made, check to verify that the UO_server_machine_name is correct and verify which port is being used. The default port is 8080.

To verify the port being used, locate the eas_install.props file in <server install directory>/EAServer directory. Open the eas_install.props in an editor. Check the port value for com.Sybase.jaguar.install.listeners.http to identify the port. Modify the address to use the port number identified.  http://<UO_server_machine_name>:<port>/BT

2. Log in to the BizTracker Management Console by entering the user id.

If a security window opens, select Null, click OK, then OK on the Connection Succeeded window, and finally Close on the Security Configuration window.

3. Select Alerts > Channel Subscription. The Channel Subscription window appears, allowing you to create a subscription for the alert messages.

4. Click Add in the Channel Subscription window. Enter the following in the fields:

5. Click OK.

The Channel Subscription list should show an entry for Unwired Orchestrator System Management with the appropriate email address.

6. Click Close to close the Channel Subscription window. You can exit the BizTracker Management Console or leave it open.

Configuration for runtime alerts is complete.

To test the runtime alerts:

1. Start the runtime instance.

2. Send a command shut down the psengine process (example command: kill -9 <process id>).

An email message to the designated email address should be generated. To troubleshoot problems if the email message is not received, check the agent.log file.