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. |
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. |
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. |