Creating Mediator or Insight Gateway Asset
To create and manage gateways, you must have the following roles:
CentraSite Administrator: to create and manage
Mediator and
Insight gateways within any organization.
Organization Administrator: to create and manage
Mediator and
Insight gateways within a specific organization.
Mediator Administrator: to create and manage
Mediator gateway.
To establish communication between CentraSite and an API Portal gateway, you must first capture the configuration details of Mediator or Insight gateway, and then register (publish) the Mediator or Insight gateway with the CentraSite registry.
You define the configuration details of Mediator or Insight gateway using the Add Gateway action in the Manage Governance Rules activity. If you do not see the Add Gateway action, it is probably because you do not have the required role to register the Mediator or Insight gateway with CentraSite.
To create a Mediator or Insight gateway
1. In the CentraSite Business UI activity bar, click Manage Governance Rules.
This displays a list of runtime policies, aliases, and gateways that are available to you.
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 | Mandatory. Name of the gateway. |
Description | Optional. Description of the gateway. |
Gateway | Type of the gateway: Mediator Insight |
Organization | Select an organization from the list to which you want to register the Mediator gateway. Note: | The drop-down list displays only the organizations to which you are permitted to add Mediator gateways. |
|
4. For the Mediator gateway only. Select the CentraSite Communication Information (Mediator to CentraSite) profile.
The CentraSite Communication Information is used to send events, metrics, and other information from Mediator to CentraSite. This information is updated in the CentraSite Communication page under Mediator Administration in Integration Server.
Field | Description |
Username | Mandatory. The CentraSite user ID. Note: | This user must have permission to update data for the APIs deployed on this Mediator instance, that is the Create Asset or Manage Assets permission. This user must also be part of the MyMediatorGateway Synchronization Group created for this Mediator instance. |
|
Password | Mandatory. The password for the CentraSite user specified in the Username box. |
Note: | CentraSite Endpoint displays the URL (host and port) of the Software AG Runtime in http://host:port/ format. The host is the machine on which Software AG Runtime is running and port is the port on which Software AG Runtime is listening. The default Software AG Runtime port number for CentraSite is 53307. |
5. For the Mediator gateway only. Configure the Mediator Communication Information (CentraSite to Mediator).
Field | Description |
Mediator Endpoint | Mandatory. Specify the URL of the Mediator instance. Format: http://<host>:<port>. |
Username | Optional. 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 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, (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 User and Password fields on this screen, you can specify any user ID that belongs to the MyDeployers group. |
|
Password | Optional. The password for the Integration Server user specified in the Username box. |
Sandbox | Optional. Select the sandbox category to be used to classify the Mediator gateway instance. 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 gateway instance is created in the specified organization and registered with the CentraSite registry or repository. The Mediator or Insight Gateway Asset Details page for the asset that you just created is displayed. For each Mediator gateway 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 will get permissions for all services published to this gateway.
