Creating Mediator Targets or Third-Party PEP Targets
Use the following procedure to create a target and save it to the CentraSite registry/repository.
Important: | Do not define multiple Mediator targets that point to the same Mediator instance, but are accessible from different ports. If you do this, the real effect is that all targets would be the same. |
To create a target
2. In CentraSite Control, go to Operations > Targets to display the target list.
3. On the Targets tab, click Add Target to open the Add Target wizard.
4. In panel 1, complete the following fields:
In this field... | Specify... |
Name | A name for the new target. Target names can contain alphanumeric characters, but cannot contain spaces or special characters (except underscores (_) and hyphens (-). When defining a Mediator target, you must also specify this identical target name in Mediator. To do this, in the Integration Server Administrator, go to Solutions > Mediator > Administration > CentraSite Communication and specify this name in the Target Name field. Note: | Keep the following in mind:  You cannot change the target name after the target is added to CentraSite. A target name does not need to be unique within the registry/repository. However, to reduce ambiguity, you should avoid giving multiple targets the same name. As a best practice, we recommend that you adopt appropriate naming conventions to ensure that targets are distinctly named within your organization. |
|
Description | Optional. A description for the new target. This description appears when a user displays a list of targets in the user interface. |
Organization | Choose the organization to which the target will be added. (The drop-down list will contain the list of organizations to which you are permitted to add targets.) |
Type | Select webMethods Integration Server (Mediator) or a third-party target type. Note: | It is not possible to change the target type after the target has been created. |
|
5. Click Next.
6. In panel 2, complete the following fields:
In this field... | Specify... |
Deployment Endpoint | Optional. The URL of the endpoint for the target's deployment service. If you are using webMethods Integration Server (Mediator) as your target type, specify the URL of the webMethods Mediator's deployment service directory as follows: http://<Host>:<Port>/ws/mediator.integration:Deployer The URL can be HTTP or HTTPS. |
User | Optional. The Integration Server user who is permitted to deploy assets to this target. By default, only a member of the Integration Server's Administrator group is permitted to deploy assets to this target. Note: | This note explains how to permit other users to deploy assets to this target. Mediator exposes several Web service operations to allow CentraSite to manage deployed assets. This Web service is invoked by CentraSite any time a user deploys or undeploys a virtual service or consumer application to Mediator. The User and Password fields identify an Integration Server user who is permitted to execute the Integration Server services associated with Mediator's deployer service. After installation, only members of the Integration Server's “Administrator” group are permitted to invoke these services. However, administrators have the flexibility to allow their own users or groups to invoke them. Access to these services is controlled by an ACL, called MediatorDeployer. Initially, only the predefined “Administrator” group is assigned to this ACL. An Integration Server administrator can remove this group and add other groups or individual users. For example, you can create your own deployer group, (e.g., “MyDeployers”) and add Integration Server user IDs to this group. Then, the user must update the MediatorDeployer ACL by removing the “Administrator” group and adding the “MyDeployers” group. Now, in the User and Password fields on this screen, you can specify any user ID that belongs to the “MyDeployers” group. |
|
Password | Optional. The password of the Integration Server user who is permitted to deployment assets to this target. The password of this user is by default manage. |
Sandbox | Optional. The sandbox category by which you want to classify the deployment endpoint for the Mediator target. a. Click Browse. b. When you click the button, the Browse Sandbox Categories dialog appears which allows you to select the required categories for the deployment endpoint. c. Click the expand node next to “Sandbox” taxonomy to view the categorization tree. d. Mark the checkbox beside the name of the category to classify the deployment endpoint. e. Click OK. CentraSite includes a set of predefined categories for the taxonomy node “Sandbox”, especially for classifying the deployment endpoint for targets. By default, the target's deployment endpoint can be classified into one of these following predefined categories: Development, Production and Test. For information on the “Sandbox” categories that CentraSite supports out-of-the-box, in CentraSite Control, go to Administration > Taxonomies. On the Taxonomies page, navigate to Sandbox in the list of taxonomies. If you would like to use sandbox categories that are not supported by CentraSite, you can define your own custom categories. Note: | Although it is possible to define subcategories for the predefined and custom categories within the Sandbox taxonomy, you cannot use these subcategories to classify the deployment endpoint. CentraSite only displays the names of the top-level categories (that is, categories that are defined for the Sandbox taxonomy) for the classification. |
|
7. Click Finish to save the new target to the CentraSite registry/repository.
8. To enable CentraSite to receive information about run-time events from the target, you must configure CentraSite's Event Receiver. The Event Receiver is a data collector that collects the run-time event data from the target. For details, see Run-Time Events and Key Performance Indicator
(KPI) Metrics. 