Binding a VM-Deployed Component to a Microservice Engine
Microservice engines (ServiceComb engines and registry/configuration centers) can be bound to VM-deployed components with a Java or Tomcat technology stack.
Microservice Engine is a one-stop management platform for microservice solutions. After microservice components are connected to CSE, you can use service registry, service governance, and configuration management of CSE. In this way, you can focus on service development and improve product delivery efficiency and quality. You can bind a microservice engine when configuring Cloud Service Settings.
- CAS_APPLICATION_ID: ID of the application to which the component belongs.
- CAS_COMPONENT_NAME: component name.
- CAS_ENVIRONMENT_ID: ID of the component deployment environment.
- CAS_INSTANCE_ID: component instance ID.
- CAS_INSTANCE_VERSION: component instance version.
For details about the MicroServiceInstance parameter, see MicroServiceInstance.
Binding a VM-Deployed Component to a Microservice Engine
- Choose Cloud Service Settings.
- Click Bind Microservice Engine.
- Select a microservice engine instance that has been bound in the environment and click OK.
If no microservice engine instance is bound to the environment, click Add one and add a microservice engine instance to the environment. For details, see Managing Basic Resources.
Move the cursor to a bound microservice engine and perform the following operations:
- Rebind a microservice engine: Click , select the target microservice engine again, and click OK.
- Delete a bound microservice engine: Click .
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