The Mediation Service provides an interface to external systems and devices. Mediation Services come from one or more Mediation Agents. In a single host installation, application server typically also starts the mediation service.
Mediation Server can start separately from the Application Server. To do this, start the Mediation Server by typing startmedagent at a command line (Start > Run startmedagent in Windows).
Except for authentication (logins and passwords for devices) and connectivity to the managed network, device drivers automate most mediation configuration. For example, if you want to manage XYZ devices, connect your hardware to the network with those devices and install the application’s XYZ device driver (XYZ is an example, not a real driver). You supply the login and password for those devices during device discovery.
Default external protocols supported can include:
• General ASCII
• Web Services
• Partial Q3
A Mediation Agent contains Managed Beans (MBeans) that manage the physical connections to a mediation target system or device. Connections might include communications with serial port devices, telnet sessions, TCP sockets, and external databases. The mediation agent executes dialogs with the mediation target (at the instruction of the client application) to retrieve and/or send data with the connection. You can access mediation through a rule or from client code.
The Mediation Agent is essential for all operations involving communications with external systems and devices. If one is not running, you can still make administrative changes to the system, but it processes no traps or other external communication.