To use an instance of CentraSite with Mediator, you must define a run-time gateway that identifies the specific instance of Mediator that you want to use. A run-time gateway is a registry object that represents a particular instance of a policy enforcement point (in this case, an instance of webMethods Mediator). The gateway object specifies the address of the Mediator's deployment endpoint, which is the endpoint that CentraSite uses to interact with Mediator to deploy virtualized services or virtualized APIs.

If you use multiple Mediators with an instance of CentraSite, you must create a gateway for each Mediator. To make the Mediators easier to distinguish when they are viewed in CentraSite, consider adopting a naming convention for gateways that clearly identifies to which environment the gateway belongs (for example, development, test, production). You can deploy any given virtualized service or virtualized API to one or more run-time gateways.

Instead of (or in addition to) using webMethods Mediator for mediation and/or policy enforcement, you can use other third-party products with CentraSite. Support for third-party policy-enforcement and run-time governance tools is available through integrations that are provided by members of the CentraSite Community. These tools are made available through the Software AG TECHcommunity Website .

In addition to using Mediator, you can use webMethods Insight. Insight is an additional monitoring tool from Software AG that you can use with CentraSite. Insight enables you to see what is happening in real-time with service transactions as they flow across any system. It provides visibility and control at the transaction level to heterogeneous SOA environments. CentraSite provides support for Insight as a gateway type out-of-the-box. For more information about Insight's uses and capabilities, see the Insight user documentation.

For detailed information about run-time gateways, see Run-Time Gateways