CentraSite Documentation : Getting Started with CentraSite : Implementation Concepts : Implementing the Mediation Environment
Implementing the Mediation Environment
 
Managing the Collection of Metrics
Managing the Collection of Events
Using CentraSite with Other Policy Enforcement Points
Using CentraSite with Insight
To use an instance of CentraSite with webMethods Mediator, you must define a target that identifies the specific webMethods Mediator that you want to use. A target is a registry object that represents a particular instance of a policy enforcement point (in this case, an instance of webMethods Mediator). The target object specifies the address of the Mediator's deployment endpoint, which is the endpoint that CentraSite uses to interact with Mediator to deploy virtual service.
If you use multiple Mediators with an instance of CentraSite, you must create a target for each Mediator. To make the Mediators easier to distinguish when they are viewed in CentraSite, consider adopting a naming convention for targets that clearly identifies to which environment the target belongs (e.g., development, test, production).
Targets are defined by an administrator with Manage Runtime Targets permission. Targets are system-wide objects that are shared by all the organizations within an instance of CentraSite.
To communicate with CentraSite, a Mediator must have a user account on CentraSite. You have to establish this user account before you can configure Mediator's connection to CentraSite. Because Mediator reads and writes to certain objects in the registry (such as virtual services), its user account requires a specific set of permissions. These permissions are identified in the Mediator user documentation.
Note:  
If you expect a high volume of traffic through a particular Mediator, consider clustering that Mediator. When you cluster Mediators, the cluster is represented by a single target within CentraSite.
Copyright © Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback