webMethods Mediator

FAQs

What is the relationship between webMethods Mediator and the webMethods ESB? Do I need to buy an IS/ESB license to run Mediator?
The webMethods Integration Server’s core run-time acts a robust container for Mediator. This core run-time ships as part of Mediator so you do not need to license it separately. If you already use webMethods IS, you’ll already be familiar with Mediator installation and administration.   

Do you need CentraSite to use Mediator?
Yes. Mediator works in conjunction with CentraSite. CentraSite provides the ability to define and configure virtual services and run-time policies. The virtual services and policies are then deployed to Mediator.

What kind of data is sent by Mediator to CentraSite?
Mediator captures and then sends run-time metrics, such as average response time, fault count and success count, and events, such as policy violation, log, error, lifecycle and monitoring/SLA, to CentraSite. CentraSite stores these metrics and events so it’s easy for application administrators, developers and architects to see them.

Can Mediator function if CentraSite becomes unavailable?
Yes. Mediator can continue to process incoming requests even if CentraSite server is down for some reason. Mediator is designed to be able to work even if other pieces of the infrastructure are experiencing issues to ensure that impact to your service transactions is minimal.

Does Mediator need a database to run?
Mediator does not need a database. Users can optionally configure Mediator to store logging information into a local database. In these situations, you’ll need to configure a database that can be used by Mediator.