Message Routing Service Operations

The Message Routing Service operations enable you to manage message routing rules for your appliance.

Overview

The Message Routing Service operations enable you to create, read, update, and delete message routing rules as well as view all message routing rules in your appliance. Download the WSDL file from https://<lmi address>/logapp20/services/MsgRoutingService?wsdl

Using Message Routing Rules you can forward a copy of incoming log data from one appliance to another appliance or 3rd party device. In the appliance, you can view the user interface implementation by navigating to Administration > Message Routing.

Implementation Guidelines

The following are general implementation guidelines for the Message Routing Service operations:

  • A set of common request parameters are required for each operation. You must specify a value for all required parameters.
  • You must specify the value of the common request parameters only.
  • All parameters must be implemented in the order in which they appear in the Request Parameters section for each of the operations.
  • All values for common request parameters must be enclosed by double quotation marks (“value”). If the name of a device or a parameter value includes a forward slash (/), such as HP/UX, or IBM i5/OS, you must replace the forward slash with %2F. (The F is case-sensitive.)

Examples: HP%2FUX or IBM i5%2FOS

Status Codes

2000 Server success
4000 Unauthorized request
5000 Invalid parameter, getStatusMessage() contains detail information about the error

Description of Message Routing Service Operations

There are two kinds of operations:
  • local - operation is performed on the local appliance itself
  • remote - operations (names ending with Remote) performed on a specified remote appliance through the Management Station

The Message Routing Service contains the following operations: