Microservices Engine:Migrate applications from a self-managed to an MSE Nacos configuration center

Migrate a Spring Cloud Alibaba application

1. Check whether your application is a Spring Cloud Alibaba application.

   If the following dependency is found in the pom.xml file, your application is a Spring Cloud Alibaba application.

   <dependency>
       <groupId>com.alibaba.cloud</groupId>
       <artifactId>spring-cloud-starter-alibaba-nacos-config</artifactId>
   </dependency>

2. If your application is a Spring Cloud Alibaba application, modify the bootstrap.properties configuration file of the application.

   Replace {Public or internal endpoint of the MSE Nacos instance} with the endpoint of the destination MSE Nacos instance. You can obtain the public or internal endpoint of your MSE Nacos instance from the Basic Information page of the instance.

   spring.cloud.nacos.config.server-addr=${Public or internal endpoint of the self-managed Nacos instance}

   In the configuration file, replace the namespace ID with the ID of the namespace to which the MSE Nacos instance belongs. If the namespace ID does not change, modifications are not required. If you use the default namespace, the namespace does not have an ID. In this case, you can leave the namespace ID empty. If the imported namespace ID is not empty, you can obtain the ID on the Namespace page of the MSE Nacos instance.

Migrate a Java application

1. Check whether your application is deployed by using the Nacos SDK for Java.

   If the following dependency is found in the pom.xml file, your application is deployed by using the Nacos SDK for Java.

   <dependency>
     <groupId>com.alibaba.nacos</groupId>
     <artifactId>nacos-client</artifactId>
   </dependency>

2. If your application is deployed by using the Nacos SDK for Java, replace ${Endpoint of the MSE Nacos instance} in the following code with the registration endpoint of the MSE Nacos instance. Replace ${namespaceId} with the ID of the namespace to which the MSE Nacos instance belongs. If you use the default namespace, you can leave the namespace ID empty. If the namespace ID does not change, modifications are not required. Then, redeploy the application.

   properties.put("serverAddr", "${Endpoint of the MSE Nacos instance}");
   properties.put("namespace", "${namespaceId}");

Migrate a Nacos Spring Boot application

If your application is a Nacos Spring Boot application, modify the application.properties configuration file of the application.

Replace ${Endpoint of the MSE Nacos instance} with the registration endpoint of the MSE Nacos instance

nacos.config.server-addr=${Endpoint of the self-managed Nacos instance}

Specify the namespace ID of your MSE Nacos instance in the following configuration:

nacos.config.namespace=${ID of a namespace in your MSE Nacos instance}

Migrate a Go application

If your application is deployed by using the Nacos SDK for Golang, you must replace ${serverAddr} with the registration endpoint of the MSE Nacos instance.

sc := []constant.ServerConfig{
    {
    IpAddr: "${serverAddr}",
    Port:   8848,
    },
}

Migrate a Python application

If your application is deployed by using the Nacos SDK for Python, you must replace ${server_address} with the registration endpoint of the MSE Nacos instance and replace ${namespace_id} with the namespace ID of the MSE Nacos instance.

SERVER_ADDRESSES = "${server_address}"
NAMESPACE = "${namespace_id}"
client = nacos.NacosClient(SERVER_ADDRESSES, namespace=NAMESPACE)

Migrate a Node.js application

If your application is deployed by using the Nacos SDK for Node.js, you must replace ${server_address} with the registration endpoint of the MSE Nacos instance and replace ${namespace_id} with the namespace ID of the MSE Nacos instance.

const configClient = new NacosConfigClient({
  serverAddr: '${server_address}',
  namespace: '${namespace_id}',
  accessKey: 'MSE_AK',
  secretKey: 'MSE_SK',
  requestTimeout: 6000,
});

Migrate a C# application

Replace ${server_address} with the registration endpoint of the MSE Nacos instance and replace namespace_id with the namespace ID of the MSE Nacos instance.

{
  "NacosConfig": {
    "Listeners": [
      {
        "Optional": false,
        "DataId": "common",
        "Group": "DEFAULT_GROUP"
      },
      {
        "Optional": false,
        "DataId": "demo",
        "Group": "DEFAULT_GROUP"
      }
    ],
    "Namespace": "namespace_id", 
    "ServerAddresses": [ "http://${server_address}:8848/" ],
    "UserName": "test2",
    "Password": "123456",
    "AccessKey": "MSE_AK",
    "SecretKey": "MSE_SK",
    "EndPoint": "acm.aliyun.com",
    "ConfigFilterAssemblies": ["YouPrefix.AssemblyName"],
    "ConfigFilterExtInfo": "some ext information"
  }
}

Migrating a C++ application

If your application is deployed by using the Nacos SDK for C++, replace ${server_address} with the registration endpoint of the MSE Nacos instance and replace {namspaceId} with the namespace ID of the MSE Nacos instance.

Properties props;
props[PropertyKeyConst::SERVER_ADDR] = "${server_address}:8848";
props[PropertyKeyConst::NAMESPACE] = "{namspaceId}";