Help Center> ROMA Connect> User Guide> Service Integration Guide> Exposing APIs> Binding Domain Names
View PDF

Binding Domain Names

Overview

Before you expose an API, you need to bind an independent domain name to the API group so that users can use the independent domain name to access the API.

For internal testing purposes, you can use the default subdomain name allocated by the system to access APIs in the API group a maximum of 1000 times a day. You cannot modify the subdomain name.

A ROMA Site instance does not support API calling using a subdomain name. It supports API calling only using the combination of IP address and host header.

Prerequisites

  • You have obtained an independent domain name. If not, you need to register a domain name.
  • You have obtained an ICP license for the independent domain name. The ICP filing takes several working days. You are advised to perform ICP filing in advance.
  • You have configured domain name resolution from the independent domain name to the APIC connection address. For details, see Adding an A Record Set.
  • If the API group contains HTTPS-compatible APIs, add an SSL certificate for the independent domain name bound to the group. Obtain the content and keys of the SSL certificate and create an SSL certificate in advance.

Procedure

  1. Log in to the ROMA Connect console. On the Instances page, click View Console next to a specific instance.
  2. In the navigation pane on the left, choose API Connect > API Management. On the API Groups tab page, click More > Manage Domain Name in the Operation column of the target API group.
  3. On the Domain Names tab page, click Bind Independent Domain Name.
  4. In the Bind Independent Domain Name dialog box displayed, enter the domain name and click OK.
    Table 1 Independent domain name configuration

    Parameter

    Description

    Domain Name

    Enter the domain name to be bound.

    TLS Version

    Select the minimum TLS version used for domain name access. This parameter applies only to HTTPS. Other modes, such as HTTP, are not affected.
  5. (Optional) If the API group contains HTTPS-compatible APIs, bind an SSL certificate for the independent domain name. Otherwise, skip this step.
    1. Click Select SSL Certificate on the right of the independent domain name.
    2. In the displayed dialog box, select the SSL certificate to be bound and click OK.

      If no SSL certificate is available, click Create SSL Certificate to create one. For details, see Creating an SSL Certificate.

Parent topic: Exposing APIs