Configuring multiple Gateway services to have the same host name

If you have configured your API Connect cloud to use Dynamic DNS, you can give the same host name to two or more Gateway services. Use this capability to give the appearance that the APIs that are deployed to the separate Gateway services are on the same Gateway.

When your API Connect cloud is configured to use Dynamic DNS, API Connect prepends the Gateway service host name with the provider organization and catalog to form the fully qualified host name of the gateway address that is used for API calls. The format of the fully qualified host name is as follows:

api.provider_organization.catalog.gateway_service_host_name

Therefore, if you give the same host name to two or more Gateway services, the URLs that are used to call APIs that are deployed to those Gateway services differ only in the provider_organization and catalog components of the fully qualified host name.

The following table provides an illustrative example:

Table 1. Gateway services with the same host name
Gateway service name	Host name	Port	Provider organization	Catalog	Host name for API calls
Service 1	gateway.mybank.com	443	accounts	test	api.test.accounts.gateway.mybank.com
Service 2	gateway.mybank.com	443	accounts	production	api.production.accounts.gateway.mybank.com

You must ensure that your DNS configuration maps the fully qualified host names appropriately.

For information on configuring your cloud to use Dynamic DNS, see Selecting the DNS scheme.

For information on adding Gateway services to your cloud, see Configuring the initial Gateway service and Adding more Gateway services.

For information on provider organizations, see Administering provider organizations.

For information on Catalogs, see Working with Catalogs.