Managing Instances
Overview
After an instance is created, you can view and edit the instance configuration information on the console, including basic information, configuration parameters, and data dictionaries, as well as import and export assets.
Viewing Details of an Instance
Content |
Description |
---|---|
Instance |
Basic information about the instance, including the instance name, instance ID, instance edition, availability zone, and creation time.
|
VPC |
VPC associated with the instance. Click the VPC name to view the VPC configuration. |
Subnet |
Subnet associated with the instance. Click the subnet name to view the subnet configuration. |
Security Group |
Security group associated with the instance. You can click the security group name to view the security group configuration or click Edit to bind a new one. |
Routes |
Private network segment. After a ROMA Connect instance is created, it can communicate with the VPC subnet segment specified during instance creation by default. If other private network segments need to communicate with the instance, you can configure routes by setting this parameter. |
Message Storage Space |
Information about the MQS message storage space of the instance, including the storage class and space usage (percentage). |
MQS Information |
Basic configuration about MQS, including the bandwidth, maximum number of partitions, message tracing, MQS SASL_SSL, intra-VPC plaintext access, RESTful API, and capacity threshold policy.
|
Connection Addresses |
Connection addresses of the instance, including the addresses for connecting to ROMA Connect, LINK, APIC, and MQS. Click next to the connection address to copy the connection address. |
Public Access |
EIP bound to the instance.
|
Modifying Configuration Parameters
On the Instance Information page of the ROMA Connect console, click the Configuration Parameters tab and view the configuration parameters of the instance. You can also change the values of Current Value.
Content |
Description |
---|---|
Parameter Name |
Name of a parameter. You can move the cursor to before a parameter name to view its description. |
Default Value |
Default value of a parameter. |
Value Range |
Value range of a parameter. |
Current Value |
Current value of a parameter. |
Updated |
Time when a parameter was last updated. If the parameter has never been modified, this parameter is left blank. |
Operation |
Click Edit to change the value of Current Value. |
Creating a Data Dictionary
A data dictionary is used to open up key values in a system database to users. DEVICE_TYPE3 is the default data dictionary. You can also customize a data dictionary. To create a data dictionary, perform the following steps:
- On the Instance Information page of the console, click the Data Dictionaries tab.
- Click Create Data Dictionary.
- In the Create Data Dictionary dialog box, set dictionary parameters and click OK.
Table 3 Parameters for creating a data dictionary Parameter
Description
Dictionary Code
Enter the unique ID of a dictionary.
Dictionary Name
Enter a dictionary name.
Extended Field 1
These parameters are reserved for the dictionary and can be left empty.
Extended Field 2
Description
Enter a brief description of the dictionary.
- After the data dictionary is created, click next to the dictionary name to expand the dictionary item list.
- Click Create Dictionary Item.
- In the Create Dictionary Item dialog box, set dictionary item parameters and click OK.
Table 4 Parameters for creating a dictionary item Parameter
Description
Item Code
Enter the unique ID of a dictionary item.
Item Name
Enter the dictionary item name.
Extended Field 1
These parameters are reserved for the dictionary item and can be left empty.
Extended Field 2
Description
Enter a brief description of the dictionary item.
Importing and Exporting Assets
ROMA Connect allows you to export application and task assets of an instance as files to a local PC or import local asset files to ROMA Connect to migrate assets in batches.
- Ensure that the instance configurations during import and export are the same. Otherwise, the import may fail. For example, if app_route is not enabled on the exported instance but is enabled on the instance to be imported, the asset import may fail when the imported asset package contains APIs with conflict paths.
- Request throttling policies, access control policies, and signature keys of APIs cannot be imported or exported.
- Importing assets
- On the Instances page of the console, click Import Asset in the upper right corner.
- In the Import Asset dialog box, select Append or Overwrite based on the site requirements.
- The data source IDs of different instances must be different. If the data source IDs are the same, select Overwrite.
- The data integration task names in different instances must be different. If the data integration task names are the same, enter a prefix in the text box.
- In the dialog box displayed, select a local asset file and import it.
- After the import is complete, click Close. You can view the imported asset in the instance.
- The custom authorizer name is globally unique. If a custom authorizer with the same name already exists in the instance when the asset is imported, random characters will be added to the end of the imported custom authorizer name to avoid duplicate names.
- If the following error information is displayed during asset import, contact technical support to upgrade the instance:
"CipherEntry":{"reason":"{\"resourceType\":\"cipherEntries\",\"resourceId\":\"\",\"resourceName\":null,\"errorCode\":\"APIG.9999\",\"errorMsg\":\"System error\"}"}
- Exporting assets
- On the Instances page of the console, click Export Asset in the upper right corner.
- Export assets.
- Exporting specified assets: Select the application or task assets to be exported and click Export Selected to export the asset files to the local PC.
- Exporting all assets: Click Export All to export all asset files to the local PC.
If you need to export all API asset information when exporting application assets, select Export all assets in applications. All API asset information including self-created and authorized APIs will be exported. If you do not select this parameter, information about self-owned and self-authorized APIs will be exported.
- After the export is complete, click Close. You can view the exported assets in the local PC.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot