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}.