Creating a Gateway Asset
Use the following procedure to create a gateway and register it with the CentraSite registry/repository.
Note: | This procedure specifies how you can create a Mediator or Insight gateway. For detailed information on creating, listing, updating, deleting an API-Portal gateway, and how to use CentraSite with API-Portal gateway see Using CentraSite with webMethods API-Portal section in Working with the CentraSite Business UI. |
To create a gateway
1. In CentraSite Business UI, click Manage Governance Rules.
2. Click the Add Gateway action to open the Create New Gateway page and complete the following fields:
Note: | If you do not see Add Gateway in the action bar, it is probably because you are not assigned the required role or do not have the permission to perform the action in CentraSite. |
Field | Description |
Name | Mandatory. Assign a name to the gateway. The name specified here should be unique for an asset of this type in CentraSite. |
Description | Optional. Write a description for the gateway. |
Gateway | Select a gateway type.  API-PortalMediator Insight |
Organization | Choose an organization from the list to which you want to register the Mediator gateway. Note: | The drop-down list shows only the organizations to which you are permitted to add Mediator gateways. |
|
3. Configure CentraSite Communication Information (Mediator to CentraSite).
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 should also be part of the MyMediatorGateway Synchronization Group created for this Mediator instance. |
|
Password | Mandatory. The password for the user specified in Username. |
Note: | CentraSite Endpoint shows the URL (host and port) of the Software AG Runtime in the format, http://host:port/. 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. |
4. Configure the Mediator Communication Information (CentraSite to Mediator).
Field | Description |
Mediator Endpoint | Mandatory. Specify the URL of the Mediator instance. Format: http://<host>:<port>. |
Use CentraSite Credentials | Select this option if you want to enable the reuse of existing CentraSite user credentials. If this checkbox is selected, CentraSite automatically disables the subsequent Username and Password fields. |
Username | Optional. The Integration Server user who is permitted to deploy assets to this Mediator gateway. By default, only a member of the Integration Server's Administrator group is 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 of the Integration Server user who is permitted to deployment assets to this gateway. The default password is the Integration Server Administrator password. |
Sandbox | Optional. Choose 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 Control UI, go to Administration > Taxonomies. In 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 custom categories. |
5. If you have selected Insight in the Gateway field as a gateway type, configure the following parameters in the Create Gateway page:
Field | Description |
Name | Mandatory. Assign a name to the gateway. For example, InsightGateway. |
Description | Write a description for the gateway. |
Gateway | Select Insight as the gateway type from the drop down list. |
Organization | Choose an organization from the list to which you want to register the Insight gateway. |
6. Click Publish.
A gateway instance is created in the specified organization and registered with the CentraSite registry/repository. The Mediator 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 group so that you can assign permissions to the group instead of assigning permission to individual users.
