Creating a ROMA Connect Instance (Old Edition)

Overview

Before using ROMA Connect, you need to create a ROMA Connect instance. A ROMA Connect instance is an independent resource space. Resources of different instances are isolated from each other. You can use one or more ROMA Connect instances as required.

If you delete an instance, all resource data created in the instance will be deleted. Exercise caution when performing this operation. Before deleting an instance, back up data by exporting asset data of an instance.

Prerequisites

• A VPC is available, and a subnet and security group have been configured. (For details on how to create a VPC, subnet, and security group, see Required Resources.)
• The available quota of ROMA Connect instances is not 0. (If the available quota is 0, delete unnecessary instances or apply for increasing the instance quota.)

Required Resources

Prepare a Virtual Private Cloud (VPC), subnet, and security group before you start. Each ROMA Connect instance is deployed in a VPC and bound to a specific subnet and security group. In this way, ROMA Connect provides an isolated virtual network environment and security protection policies that can be easily configured and managed by users.

The following table lists the resources required by a ROMA Connect instance.

Creating an Instance

1. Log in to the ROMA Connect console. On the Instances page, click Buy ROMA Connect Instance.
2. On the Buy ROMA Connect Instance page, enter configuration information about the instance. The system automatically calculates the fee based on Edition and Required Duration. Then, click Next.

   Table 3 ROMA Connect instance parameters

   Parameter	Configuration
   Billing Mode	Billing mode of an instance. Select Yearly/Monthly.
   Region	Select the region where the instance resides. Instances in different regions cannot communicate with each other. Select the nearest region to reduce network latency.
   AZ	Select the availability zone (AZ) where the instance resides. Different AZs are physically isolated but can communicate with each other through a private network. To enhance ROMA Connect availability, create instances in different AZs. To shorten network latency, create instances in the same AZ.
   CPU Architecture	Select x86 or Kunpeng based on the CPU architecture supported by the current environment.
   Edition	Select the capacity specifications of the instance. The edition cannot be changed after the instance is created. Basic: 25 connections, integrating 5 to 10 systems Professional: 80 connections, integrating 10 to 20 systems Enterprise: 200 connections, integrating 20 to 30 systems Platinum: 800 connections, integrating over 30 systems NOTE: The number of connections and the number of systems are only used as a reference for selecting ROMA Connect instance edition. They do not limit the number of resources (such as integration tasks, APIs, and message topics) in an instance and are not directly associated with the resource quota of the instance. The number of systems refers to the number of users' service systems interconnecting with the ROMA Connect instance. Multiple connections can be set up between a service system and a ROMA Connect instance. A connection refers to an interaction between a service system and ROMA Connect. The number of connections varies depending on the functional module in ROMA Connect to connect. The mappings between the number of resources and the number of connections are as follows: FDI: Two data integration tasks in the running state occupy one connection. APIC: 10 hosting APIs (not published by custom backends) occupy one connection. Five function APIs or data APIs occupy one connection. MQS: Three topics occupy one connection. LINK: 1000 devices occupy one connection. Example: An enterprise integrates its services using ROMA Connect. If 50 data integration tasks need to be created for data synchronization but only a maximum of 20 data integration tasks can be running concurrently, the number of connections required by FDI is 10 (20/2). If 200 hosting APIs and 20 data APIs need to be created for function and data exposure, the number of connections required by APIC is 24 (200/10 + 20/5). If 30 topics need to be created for message integration across systems, the number of connections required by MQS is 10 (30/3). If 5000 devices need to be created for IoT management of enterprise assets, the number of connections required by LINK is 5 (5000/1000). In this example, the total number of connections required is 10 (FDI) +24 (APIC) +10 (MQS) +5 (LINK) = 49. Therefore, an instance of the professional edition or higher specifications should be selected.
   Enterprise Project	Select an enterprise project. You can associate an instance with the enterprise project. This configuration option is available only for enterprise accounts.
   Instance Name	Enter the instance name as planned.
   Description	Enter a brief description of the instance.
   VPC	Select the VPC and subnet associated with the instance. The VPC and subnet must have been created during resource preparation.
   Security Group	Select the security group to be associated with the instance. The security group must have been created in Required Resources.
   Public Access	Determine whether to enable the function of accessing ROMA Connect from a public network based on service requirements.
   EIP	This parameter is available only if Public Access is enabled. Select the elastic public IP associated with the instance. This elastic public IP must be applied for in advance, as described in Required Resources.
   Engine Version	Select the Kafka server version used by the instance. Supported versions: 1.1.0, 2.7
   MQS Capacity Threshold Policy	Select a processing policy that will be used when the number of messages in MQS reaches the capacity threshold (95% of the storage space). Stop creation: New message creation requests will be rejected until a message is deleted according to the configured aging time. After the available storage space is greater than 5%, new message creation requests can be received. This policy applies when message retrieval processing is slow or inventory messages need to be repeatedly retrieved and cannot be deleted in advance. Delete messages: The oldest messages (10% of the total number of messages) are automatically deleted to free up storage space for new requests. This policy has no adverse impact on message creation. It applies when message retrieval is fast and there are no accumulated messages.
   SASL_SSL	Determine whether to enable SASL transmission and SSL encryption for message transmission. Enabling this parameter better secures data transmission. Enabling SASL_SSL cannot be undone.
   Intra-VPC Plaintext Access	This parameter is available only when SASL_SSL is enabled. Specify whether plaintext access is used in the VPC. If intra-VPC plaintext access is enabled, SASL cannot be used to connect to MQS topics in the VPC. That is, no certificate is required for accessing topics.
   Required Duration	Select a validity period for the instance. The minimum duration is 1 month. If you select Auto renew, monthly subscriptions are renewed each month and yearly subscriptions are renewed each year.

3. On the Confirm page, select the item to confirm that you have read and agree to the customer agreement and privacy statement, and click Pay Now to create an instance.

   The instance creation takes about 18 to 25 minutes. After the instance is created, the instance status is Available on the Instances page.

   If the ROMA Connect instance fails to be created, delete the failed instance and create a new one. If the creation still fails, contact technical support.