Monitor a running adapter using RemoteControl and RemoteLogger interfaces.
RemoteControl and RemoteLogger are optional adapter implementations. Specify the interfaces in the adapter properties.
A running adapter contains a controller that supports a dynamic control interface, that can be invoked by a RemoteControl. A RemoteControl provides an interface for operators to communicate with running adapters to establish the current status and resolve problems. To specify a RemoteControl, use this properties syntax:
adapterName. Controller.RemoteControl.ClassName = Class
Remote logging filters the log output of the adapter and generates alerts or messages. You can configure remote loggers to send all log lines with a specific log level such as FATAL, WARN, and so on. You can also use a regular expression to pattern match for explicit errors. To specify a RemoteLogger, use this syntax:
adapterName. Logging.RemoteLogger.ClassName = Class
Sybase provides some standard implementations for remote control and remote logging.
| Interface | Description |
|---|---|
| HTTPRemote-Control | Turns adapter into a Web server. Point a browser at the machine on which the adapter is running, and the port (default value is 80) on which the HTTPRemoteControl is listening, and HTTPRemote-Control returns a simple control interface. |
| RvRemote-Control | Allows you to use TIBCO Rendezvous to communicate with the adapter without knowing where the adapter is running. |
| JMXRemote-Control | A JMX-compliant remote control. |
| RMIRemote-Control | Registers as an RMI service and allows clients to support, administer, and configure an adapter using RMI. |
| RvRemoteLogger | Publishes log lines on a specified Rendezvous subject |
| MailRemote-Logger | Sends e-mail messages using the Java Mail API. |