Creating an Instance

Overview

Before using ROMA Connect, you need to create a ROMA Connect instance. A ROMA Connect instance is an independent resource space. All operations are performed in an instance. Resources of different instances are isolated from each other. You can use one or more ROMA Connect instances based on service requirements.

Prerequisites

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

Procedure

1. Log in to the ROMA Connect console. On the Instances page, click Create ROMA Connect Instance.
2. On the Create ROMA Connect Instance page, enter configuration information about the instance. Then, click Next.

   Table 1 ROMA Connect instance parameters

   Parameter	Configuration
   Edition	Select the capacity specifications of the instance. The edition cannot be changed after the instance is created. Basic (for small enterprises): This edition supports the integration of 5 to 10 systems and 25 connections. Professional (for SMEs): This edition supports the integration of 10 to 20 systems and 80 connections. Enterprise (for medium-sized or large enterprises): This edition supports the integration of 20 to 30 systems and 200 connections. Platinum (for large enterprises): This edition supports the integration of more than 30 systems and 800 connections. 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: One data integration task occupies one connection. APIC: 10 hosting APIs (not using custom backends as the backend services) occupy one connection. Two function APIs or data APIs occupy one connection. MQS: Three topics occupy one connection. LINK: 1000 devices occupy one connection.
   CPU Architecture	Select x86 or Kunpeng based on the CPU architecture supported by the current environment.
   AZ	Select the availability zone (AZ) where the instance resides. Different AZs are physically isolated but can communicate with each other through an internal network. To enhance ROMA Connect availability, create instances in different AZs. To shorten network latency, create instances in the same AZ.
   Instance Name	Enter the instance name as planned.
   Enterprise Project	Associate the instance with an enterprise project. Available for enterprise accounts.
   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 in Preparing Required Resources.
   Security Group	Select the security group associated with the instance. The security group must have been created in Preparing 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 EIP associated with the instance. The EIP must be applied for in advance.
   Kafka Version	Select the Kafka server version used by the instance. Currently, both 1.1.0 and 2.3.0 are supported. Select a version based on the site requirements. Version 2.3.0 is recommended.
   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). 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. 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.
   MQS SASL_SSL	Determine whether to enable SASL authentication and SSL encryption for message transmission. It is recommended that you enable this parameter to improve data transmission security.
   Intra-VPC Plaintext Access	This parameter is available only if MQS SASL_SSL is enabled. Specify whether plaintext access is used in the VPC. If intra-VPC plaintext access is enabled, you cannot use SASL to connect to message integration topics in the VPC. In this case, no certificate is required for connecting to topics.

3. On the Confirm page, click Submit 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.