Enterprise Distributed Application Service:MSE gateway routing

Create an MSE gateway route

1. Log on to the EDAS console. In the left-side navigation pane, choose Traffic Management > Application Routing > MSE Gateway Routing.

2. On the MSE Gateway Routes page, click Create Route.

3. In the Create Route panel, configure the parameters as required and click Next.

   1. In the Request Information step, configure the parameters as required and click Next.

      Note

      • A route is matched when all conditions in its routing rule are met. The more conditions you specify, the fewer requests a route can match.

      • A request matches routes in their display order on the Routes page in the MSE console.

      

      Parameter		Description
      Route Name		The name of the route that you want to create.
      MSE Cloud Native Gateway		Select an MSE cloud-native gateway from the drop-down list. To create an MSE cloud-native gateway, click + Create an MSE cloud native gateway.
      Associated Domain Name		The domain name that you created on the Domain Names page in the MSE console. You can select multiple domain names.
      Match Rule	Path	The Path parameter in the HTTP requests that you want to forward in the route. If multiple routes have the same matching condition for the Path parameter, the longer the Path value in the rule, the higher priority a route has. The matching conditions for the Path parameter include Prefix Match, Exact Match, and Regex Match. Prefix Match: The prefix of the Path parameter is specified to match requests and a route. For example, you can specify the prefix as /user. Exact Match: The entire Path parameter value is specified to match requests and a route. For example, you can specify the Path value as /user. Regex Match: A regular expression is used to match requests and a route.
      	Method	The Method parameter in the HTTP requests that you want to forward in the route. If you do not specify this parameter, requests with any Method parameter value can match the route. You can specify multiple Method values in the matching condition to match more requests with a route.
      	Header	The Header parameter in the HTTP requests that you want to forward in the route. If multiple routes have the same matching conditions aside from the number of specified Header parameters, the more Header parameters in the rule, the higher priority a route has. Click + Request header to add a Header parameter in the routing rule.
      	Request Parameter (Query)	The Query parameter in the HTTP requests that you want to forward in the route. If multiple routes have the same matching conditions aside from the number of Query parameters, the more Query parameters in the rule, the higher priority a route has. Click + Request parameters to add a Query parameter in the routing rule.

   2. In the Destination Service step, configure the parameters as required and click Save.

      

      Parameter	Description
      Service Source	EDAS Registration Center: If your destination service is registered in an EDAS registry, select EDAS Registration Center as the service source. MSE Nacos: If your destination service is registered on an MSE Nacos instance, select MSE Nacos as the service source. ACK Container: If your destination service is a Kubernetes service, select ACK Container as the service source.
      MSE Nacos Instance	Note You need to configure this parameter only if you select MSE Nacos for the Service Source parameter. Select an MSE Nacos instance that you created from the drop-down list.
      Destination Service	Click + Add service to configure the following parameters: NameSpace, Application, Service, Port, and Weight (%).

Manage an MSE gateway route

Configure a policy

1. Log on to the EDAS console. In the left-side navigation pane, choose Traffic Management > Application Routing > MSE Gateway Routing.

2. On the MSE Gateway Routes page, click Policy Settings in the Actions column.

3. In the Policy Settings section, click the corresponding tab and click Configure policy to configure policies for your MSE gateway route.

   

   • Throttling: For more information, see Configure a throttling policy.

   • Rewrite: For more information, see Configure a rewrite policy.

   • Header Settings: For more information, see Configure a header setting policy.

   • CORS: For more information, see Configure a CORS policy.

   • Expiration: For more information, see Configure a timeout policy.

   • Retry: For more information, see Configure a retry policy.

Edit an MSE gateway route

1. Log on to the EDAS console. In the left-side navigation pane, choose Traffic Management > Application Routing > MSE Gateway Routing.

2. On the MSE Gateway Routes page, find the MSE gateway route that you want to modify and click Edit in the Actions column.

Monitor an MSE gateway route

1. Log on to the EDAS console. In the left-side navigation pane, choose Traffic Management > Application Routing > MSE Gateway Routing.

2. On the MSE Gateway Routes page, find the MSE gateway route that you want to monitor and click Monitor in the Actions column.

3. On the monitoring page, view the Global Kanban, Business TOP list, and Access Center tabs.

   • Click the Global Kanban tab and view the global monitoring data of the gateway that you select. You can select a time period in the upper-right corner to filter the data.

   • Click the Business TOP list tab and view the top ranked workloads. You can select a time period in the upper-right corner to filter the data.

   • Click the Access Center tab and view the user traffic data of the gateway. You can select a time period in the upper-right corner to filter the data.