El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
Cloud Service Engine
Cloud Service Engine
- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Before You Start
- Permissions Management
-
Exclusive ServiceComb Engine
- Creating a ServiceComb Engine
-
Managing ServiceComb Engines
- Viewing ServiceComb Engine Information
- Obtaining the Service Center Address of a ServiceComb Engine
- Obtaining the Configuration Center Address of a ServiceComb Engine
- Viewing the Instance Quota of a ServiceComb Engine
- Viewing the Configuration Item Quota of a ServiceComb Engine
- Configuring Backup and Restoration of a ServiceComb Engine
- Managing Public Network Access for a ServiceComb Engine
- Viewing ServiceComb Engine Operation Logs
- Upgrading a ServiceComb Engine Version
- Deleting a ServiceComb Engine
- Changing ServiceComb Engine Specifications
- Managing Security Authentication for a ServiceComb Engine
- Managing Tags
- Using ServiceComb Engines
- Registry/Configuration Center
- Key Operations Recorded by CTS
-
Best Practices
- CSE Best Practices
-
ServiceComb Engines
-
ServiceComb Engine Application Hosting
- Hosting Spring Cloud Applications Using Spring Cloud Huawei SDK
- Hosting a Java Chassis Application
-
ServiceComb Engine Application Hosting
- Registry/Configuration Centers
-
Developer Guide
- Overview
- Developing Microservice Applications
- Preparing the Environment
- Connecting Microservice Applications
- Deploying Microservice Applications
- Using ServiceComb Engine Functions
- Appendix
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Examples
-
CSE API
- API Calling
- Dynamic Configuration
-
Engine Management
- Querying Flavors Supported by a Microservice Engine
- Querying the Microservice Engine List
- Creating an Exclusive Microservice Engine
- Querying Details About a Microservice Engine
- Deleting a Microservice Engine
- Querying Details About a Microservice Engine Job
- Retrying an Exclusive ServiceComb Engine
- Upgrading an Exclusive ServiceComb Engine
- Changing Microservice Engine Specifications
- Updating the Configuration of an Exclusive Microservice Engine
-
Microservice Governance
- Querying the Governance Policy List
- Creating a Dark Launch Policy
- Querying a Dark Launch Rule of a Microservice
- Deleting a Dark Launch Policy
- Changing a Governance Policy
- Deleting a Governance Policy
- Querying Governance Policy Details
- Creating a Governance Policy
- Querying the Governance Policy List of a Specified Kind
- Nacos API
-
ServiceComb API
- API Calling
- Authentication
-
Microservice
- Querying Information About a Microservice
- Deleting Definition Information About a Microservice
- Querying Information About All Microservices
- Creating Static Information for a Microservice
- Deleting Static Information About Microservices in Batches
- Modifying Extended Attributes of a Microservice
- Querying the Unique Service or Schema ID of a Microservice
- Schema
-
Microservice Instance
- Registering a Microservice Instance
- Querying a Microservice Instance Based on service_id
- Deregistering a Microservice Instance
- Querying Details About a Microservice Instance
- Modifying the Extended Information About a Microservice Instance
- Modifying Status of a Microservice Instance
- Sending Heartbeat Information
- Querying a Microservice Instance by Filter Criteria
- Querying Microservice Instances in Batches
- Dependency
- Configuration Management
- Appendixes
- Change History
- SDK Reference
-
FAQs
- Precautions When Using Huawei Cloud CSE
- Nacos Engines
-
ServiceComb Engines
- How Do I Perform Local Development and Testing?
- How Can I Handle a Certificate Loading Error?
- What If the Header Name Is Invalid?
- What Is the Performance Loss of Mesher?
- Why Is "Version validate failed" Displayed When I Attempt to Connect to the Service Center?
- Why Is "Not enough quota" Displayed When I Attempt to Connect to the Service Center?
- What Should I Do If the Service Registration Fails After IPv6 Is Enabled for the Exclusive ServiceComb Engine with Security Authentication Enabled?
- What Is Service Name Duplication Check?
- Why Do I Have to Define Service Contracts?
- Why Are Microservice Development Framework and Netty Versions Unmatched?
- What Do I Need to Know Before Upgrading an Exclusive ServiceComb Engine?
- What Must I Check Before Migrating Services from the Professional to the Exclusive Microservice Engine?
- Why Is "Duplicate cluster name" Displayed?
- Error Message "the subnet could not be found" Is Displayed When the Access Address Fails to Be Processed During Engine Creation
- Why Is Error "does not match rule: {Max: 100, Regexp: ^[a-zA-Z0-9]{1,160}$|^[a-zA-Z0-9][a-zA-Z0-9_\-.]{0,158}[a-zA-Z0-9]$}"}" Reported?
- What Should I Do If SpringCloud Applications Fail to Connect to the Configuration Center of ServiceComb Engine 2.x?
- Why Could My the Global Configuration Not Be Modified?
- Obtain Configurations Failed
- Videos
- General Reference
On this page
Help Center/
Cloud Service Engine/
Best Practices/
Registry/Configuration Centers/
Connecting Spring Cloud Eureka Applications to Nacos Engines
Copied.
Connecting Spring Cloud Eureka Applications to Nacos Engines
This section uses a demo to demonstrate how to connect Spring Cloud Eureka applications to Nacos engines.
Connect a provider service and a consumer service to a Nacos engine.
Prerequisites
- You have created a Nacos engine. For details, see Creating a Registry/Configuration Center.
- You have downloaded the demo source code from GitHub to the local host and decompressed it.
- The Java JDK and Maven have been installed on the local host for compilation, building, and packaging, and the Maven central library can be accessed.
Restrictions
- Nacos is compatible with Eureka APIs on the Eureka server side and saves and updates client instance information registered on the service side. Therefore, if you use only Eureka as the registry center, many features of Nacos, such as namespace and configuration management, cannot be used.
- Eureka is used as the client and can be viewed only on the Service Management page of Nacos. Eureka services are displayed using the default attributes of Nacos.
- Default namespace: public
- Default group: DEFAULT_GROUP
- The value of Protection Threshold for creating a service on the Service Management page of Nacos is a feature of Nacos and does not apply to the Eureka service.
Connecting Spring Cloud Eureka Applications to Nacos Engines
- Log in to CSE.
- Obtain the registry center address of a Nacos engine.
- In the left navigation pane, choose Registry/Configuration Center and click the Nacos engine instance.
- In the Connection Information area on the Basic Information page, obtain the service center address.
- Change the registry center address and microservice name in the demo.
- Configure the Nacos service center address and microservice name in the application.properties file.
- Find the eureka-demo-master\eureka-consumer\src\main\resources\application.properties file in the demo source code directory downloaded to the local host and configure the consumer service.
server.port=9001 spring.application.name= eureka-client-consumer //Microservice name eureka.client.serviceUrl.defaultZone= XXX.nacos.cse.com:8848/nacos/eureka //Service center address of Nacos eureka.instance.lease-renewal-interval-in-seconds=15 //Service heartbeat update interval eureka.client.registry-fetch-interval-seconds=15 //Interval for pulling the registry center. It is recommended that the value be the same as the heartbeat interval.
- Find the eureka-demo-master\eureka-provider\src\main\resources\application.properties file in the demo source code directory downloaded to the local host and configure the provider service.
server.port=9000 spring.application.name= eureka-client-provider //Microservice name eureka.client.serviceUrl.defaultZone= XXX.nacos.cse.com:8848/nacos/eureka //Service center address of Nacos eureka.instance.lease-renewal-interval-in-seconds=15 //Service heartbeat update interval eureka.client.registry-fetch-interval-seconds=15 //Interval for pulling the registry center. It is recommended that the value be the same as the heartbeat interval.
- Find the eureka-demo-master\eureka-consumer\src\main\resources\application.properties file in the demo source code directory downloaded to the local host and configure the consumer service.
- Configure the Nacos service center address and microservice name in the application.properties file.
- Pack the demo source code into a JAR package.
- In the root directory of the demo source code, open the Command Prompt and run the mvn clean package command to package and compile the project.
- After the compilation is successful, two JAR packages are generated, as shown in Table 1.
- Deploy Spring Cloud applications.
Deploy provider and consumer on the ECS node in the VPC where the Nacos engine is located.
- Create an ECS node in the VPC where the engine instance is located and log in to the ECS node. For details, see Purchasing and Logging In to a Linux ECS.
- Install JRE to provide a running environment for services.
- Upload the JAR package generated in 4 to the ECS node.
- Run the java -jar {JAR package} command to run the generated JAR package.
- Confirm the deployment results.
- Optional: On the CSE console, choose Registry/Configuration Center and click the Nacos engine created in Prerequisites.
- Choose Service Management and check the number of instances of microservices eureka-client-consumer and eureka-client-provider.
- If Instances is not 0, the demo has been connected to the Nacos engine.
- If Instances is 0 or the eureka-client-consumer and eureka-client-provider services cannot be found, the demo fails to be connected to the Nacos engine.
Parent topic: Registry/Configuration Centers
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot