What Should I Do If the Application Name Displayed on Microservice Governance Is Different from That Displayed on ServiceStage Application Management After an Application Component Is Connected to a Microservice Engine?
Symptom
After an application component is connected to a microservice engine, the application name displayed on Microservice Governance is different from that displayed on ServiceStage Application Management. For example, after a component created and deployed under Application Management > canary-application is connected to the microservice engine, its application name is canary-application-batch displayed in Microservice Catalog > Microservice List.
Possible Cause
In ServiceStage, an application is a service system with complete functions and consists of one or more feature-related components.
In a microservice, an application can be regarded as a software system that implements a complete service. An application consists of multiple microservices, which can discover and call each other.
- In a Spring Cloud microservice architecture development project, the application name is usually defined in the bootstrap.yaml configuration file of a component in the project.
- In a Java Chassis microservice architecture development project, the application name is usually defined in the microservice.yaml configuration file of a component in the project.
Configuration files are stored in the /src/main/resources/ directory of components in the current project.
After a component instance of a ServiceStage application is connected to a microservice engine, its application name is the one defined in the configuration file of the component.
Solution
To ensure application name consistency:
- In a Spring Cloud microservice architecture, change the application name in the configuration file of each component to ${CAS_APPLICATION_NAME:basic-application}.
- In a Java Chassis microservice architecture, change the application name in the configuration file of each component to ${CAS_APPLICATION_NAME}.
Application Management FAQs
- How Do I View the Causes of Application Component Deployment Failures?
- What Should I Do If I Don't See the VM Agent After Installing It?
- What Should I Do If the VM Agent Is Offline?
- What If an Instance Is Being Created for a Long Time?
- How Do I Solve the Dependency Problem When a Node Program Runs in Docker?
- How Do I Customize a Tomcat Context Path?
- How Do I Use a Fixed Application Component IP?
- What Should I Do If an ECS Error Occurs When I Create and Deploy a Component on a VM?
- What Should I Do If I Cannot Access the Port When I Create and Deploy a Component on a VM?
- Which Directories Do I Use to Write Files for VM-Deployed Application Components?
- What Should I Do If "host status is not active" Is Reported When a VM-Deployed Component Fails to Be Deleted?
- How Do I Use the ServiceStage Source Code Deployment Function?
- What Should I Do If Components Fail to Be Upgraded in ServiceStage Dark Launch?
- How Do I Mount Items to Modify the Configuration File of a Container-based Component?
- What Should I Do If the Application Name Displayed on Microservice Governance Is Different from That Displayed on ServiceStage Application Management After an Application Component Is Connected to a Microservice Engine?
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.
Chatbotmore