หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
Cloud Application Engine
Cloud Application Engine
- Service Overview
- Billing
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Environment Management
- Application Management
- Component Management
- Instance Management
- Component Configurations
- Component O&M
- System Settings
- Key Operations Recorded by CTS
-
Best Practices
- CAE Best Practices
- Using CAE to Host Nginx Static File Servers
- Interconnecting GitLab with Jenkins for Automatic Build and Deployment on CAE
- Deploying Components Based on the Dependency Sequence Using the Jenkins Pipeline
- Deploying Spring Cloud Applications to CAE to Automatically Connect to the Nacos Engine
- Graceful Startup of a Spring Cloud Application
- Health Check
- Lifecycle Management
- Sending Event Alarms to WeCom
-
Connecting to the CodeArts Pipeline to Automatically Upgrade CAE Components
- Overview
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to a CodeArts Release Repo
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to the OBS Bucket
- Upgrading a CAE Component After Uploading an Image Built Using the Pipeline to the SWR Image Repository
- Configuring PromQL to Implement Custom Auto Scaling
- Configuring the Interconnection Between CAE and DEW to Help Applications Obtain Encrypted Secrets from DEW
- Deploying ASP.NET Core Applications to CAE
- Connecting the Network Through Enterprise Routes
- API Reference
-
FAQs
- Component Management FAQs
- Environment Management
-
Component Configuration FAQs
- Is Manual Scaling Still Effective When a Scaling Policy Is Configured?
- Can Components Be Scaled Without a Scaling Policy?
- Why Is My Instance Abnormal After Cloud Storage Is Configured?
- What Do I Do If a Component Becomes Not Ready?
- How Does CAE Support Dark Launch?
- How Do I Provide Prometheus Metrics for a Java Application?
- System Configuration FAQs
- Service Resources FAQs
- General Reference
On this page
Copied.
Configuring CSE
CAE provides Cloud Service Engine (CSE) with service registry, service governance, and configuration management. It allows you to quickly develop microservice applications and implement high-availability O&M.
Prerequisites
You have created a microservice engine instance. For details, see Creating a ServiceComb Engine.
Binding a Microservice Engine
- Only microservice engines in the Available state can be bound.
- Multiple microservice engines cannot be bound at the same time.
- The microservice engine to be bound must be in the same VPC as the environment.
- Log in to CAE.
- Choose Component Configurations.
- Select the target component from the drop-down list in the upper part of the page.
Figure 1 Selecting a component
- Click Configure in the Cloud Service Engine (CSE) module.
- Select a microservice engine.
- Click Exclusive ServiceComb Engines and select a ServiceComb engine.
Figure 2 Exclusive ServiceComb engines
- If the existing microservice engines do not meet service requirements:
- Click Go to CSE Console to create a microservice engine. For details, see Creating a ServiceComb Engine.
- Select the created microservice engine.
- Click Exclusive ServiceComb Engines and select a ServiceComb engine.
- Click Save.
- Make the configurations take effect.
- If the component has been deployed, click Activate Settings in the upper part of the page. In the dialog box displayed on the right, confirm the configurations and click OK for the configurations to take effect.
- If the component has not been deployed, click Set and Deploy Component in the upper part of the page. In the dialog box displayed on the right, click OK. After the deployment is complete, the configurations take effect.
NOTE:
- After the ServiceComb engine is bound, you can view microservice running metrics and govern microservices based on real-time dashboard data. For details, see Using ServiceComb Engines.
- After the Nacos engine is bound, you can manage the services registered with the Nacos engine. For details, see Using Nacos Engines.
Viewing Microservice Engine Configurations
- Log in to CAE.
- Choose Component Configurations.
- Select the target component from the drop-down list in the upper part of the page.
- Click Configure in the Cloud Service Engine (CSE) module.
- View the microservice engine configurations, such as the name, status, version, private IP address, and binding status.
The bound microservice engine is labeled with Current Configuration.
Figure 3 Microservice engine configurations
Modifying Microservice Engine Configurations
- Log in to CAE.
- Choose Component Configurations.
- Select the target component from the drop-down list in the upper part of the page.
- Click Configure in the Cloud Service Engine (CSE) module.
- Select the target microservice engine and click Save.
- Click Activate Settings in the upper part of the Component Configurations page.
- In the displayed dialog box, confirm the configurations and click OK for the configurations to take effect.
Unbinding a Microservice Engine
- Log in to CAE.
- Choose Component Configurations.
- Select the target component from the drop-down list in the upper part of the page.
- Click Configure in the Cloud Service Engine (CSE) module.
- Click
to disable CSE settings.
- Click Save.
- In the displayed dialog box, enter SWITCHOFF and click OK.
- Click Activate Settings in the upper part of the Component Configurations page.
- In the displayed dialog box, confirm the configurations and click OK for the configurations to take effect.
Parent topic: Component Configurations
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