API Management 10.4 | Using CentraSite | Runtime Governance | Gateway Management | Managing Gateways through CentraSite Business UI | Creating Mediator or Insight Server Gateway Asset
 
Creating Mediator or Insight Server Gateway Asset
Note: This section is not applicable if the CentraSite run-time aspects are not enabled. By default, run-time aspects configured from CentraSite are disabled. However, you can enable them if required. To enable the CentraSite run-time aspects, see Enabling CentraSite Run-Time Aspects.
Pre-requisites:
To create and manage (that is, view, modify, and delete) Mediator and Insight Server assets for an organization, you must have one of the following roles:
*CentraSite Administrator: instances of Mediator and Insight Server gateways in any organization in CentraSite.
*Organization Administrator: instances of Mediator and Insight Server gateways in your organization.
*Mediator Administrator: instances of Mediator and Insight Server gateways in the specific organization to which your Mediator Administrator role applies.
To establish communication between CentraSite and aMediator or Insight Server gateway instance, you must first capture configuration details of the Mediator or Insight Server instance with which you want to communicate, and then publish the CentraSite information to Mediator or Insight Server.
You specify the configuration details of a Mediator or Insight Server gateway using the Add Gateway action in the Governance Rules activity. If you do not see the Add Gateway action, it is probably because you do not have the required role to configure and register a Mediator or Insight Server gateway asset in CentraSite.
* To create a Mediator or Insight Server gateway
1. In the CentraSite Business UI activity bar, click Governance Rules.
2. On the actions bar of the Search Results page, click Add Gateway.
3. In the Create New Gateway page, provide the required information for each of the displayed data fields:
Field
Description
Name
Name of the Mediator or Insight Server asset.
A Mediator or Insight Server gateway can contain any character (including spaces).
The Mediator or Insight Server name does not need to be unique within the registry. However, to reduce ambiguity, you must avoid giving multiple Mediator or Insight Server instances the same name.
As a best practice, consider adopting appropriate naming conventions to ensure that Mediator or Insight Server instances are distinctly named within an organization.
Description
(Optional). Description of the Mediator or Insight Server gateway. This description appears when a user displays the list of Mediator or Insight Server instances in CentraSite Business UI.
Gateway
Select Mediator or Insight.
Organization
Name of an organization where you want to register this Mediator or Insight Server gateway. This value is set to Default Organization.
The drop-down list contains the list of organizations to which you are permitted to register the Mediator or Insight Server gateway.
4. For Mediator gateway only. In the CentraSite Communication Information (Mediator to CentraSite) section, provide the following information:
Field
Description
Username
The CentraSite user ID for authenticating against CentraSite when Mediator communicates with CentraSite.
This implies the user ID of a user who has the CentraSite Administrator role or the Mediator Administrator role.
Note: This user should have at least Modify permission to update details of the APIs published to this Mediator. This user could also be part of the MyMediatorGateway Synchronization Group created for this API Gateway. Users in the MyMediatorGateway Synchronization Group will always have Modify permission on the API once it is published to Mediator.
Password
The password of the CentraSite user specified in the Username field.
Note: The CentraSite Endpoint field shows the URL (scheme, host, and port) of the CentraSite Application Server Tier (CAST) in the format, <scheme>://<host>:<port>. The scheme is http or https. The host is the machine on which CAST is running, and port is the port on which CentraSite is listening. The value for the CentraSite Endpoint field is determined by the URL that you use to access the CentraSite Business UI.
The CentraSite Communication Information is used to send run-time events, performance metrics, and other information from Mediator to CentraSite. This information is updated in the CentraSite Communication page under Mediator Administration in Integration Server.
5. For Mediator gateway only. In the Mediator Communication Information (CentraSite to Mediator) section, provide the following information:
Field
Description
Mediator Endpoint
The Mediator's deployment endpoint, which is the endpoint that CentraSite uses to interact with Mediator for deployment of Virtual Service assets.
The Mediator Endpoint URL has the following format:
http://<host>:<port>.
Example: http://myHostname:5555
Use CentraSite Credentials
Selecting the check box enables reuse of the CentraSite credentials for authenticating against Mediator.
When you select the Use CentraSite Credentials check box, the subsequent Username and Password fields are automatically disabled.
Username
The Integration Server user who is permitted to deploy assets to Mediator gateway. By default, only a few of the Integration Server's Administrator group are permitted to deploy assets to this gateway.
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 Username 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, (for example, 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 Username and Password fields on this screen, you can specify any user ID that belongs to the MyDeployers group.
Password
The password for the Integration Server user specified in the Username box.
Sandbox
(Optional). The sandbox category that is to be used to classify this Mediator gateway.
a. Click Choose.
The Sandbox List is displayed with the predefined sandbox categories: Development, Production, and Test.
b. Select a sandbox category from the list.
c. Click OK.
For information on the Sandbox categories that CentraSite supports out-of-the-box, in CentraSite Control, go to Administration > Taxonomies. In the Taxonomies page, navigate to Sandbox in the list of taxonomies. If you want to use sandbox categories that are not supported by CentraSite, you can define custom categories.
6. Click Publish.
A Mediator or Insight Gateway asset instance is created in the specified organization, and registered with the CentraSite Registry Repository. The details page for the Mediator or Insight Gateway asset that you just created is displayed. For each Mediator gateway asset that is successfully created, CentraSite creates a MyMediatorGateway Synchronization Group, where MyMediatorGateway is the name of the Mediator gateway. You can add users who have access to the Mediator gateway to this Synchronization Group to send metrics for all services. This group gets permissions for all services published to this gateway.
Copyright © 2015- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release