Option | Description |
Name | You can optionally change the step name. There are no naming restrictions. |
Type | (Read-only field.) Routing Rule. |
Protocol | (Read-only field.) HTTP. |
Routing Type | Select Content-Based. |
Rule Name | Assign a name to the rule. |
XPath | The XPath field is applicable only while creating SOAP Virtual Services. |
Route To | Specify where to route the request if the rule criteria are met. Specify either the URL of a native service or a connection pool name. Then, click the icon next to this field and complete the Configure Endpoint Properties dialog box as follows: |
![]() ![]() | |
![]() ![]() ![]() | |
HTTP Method | The HTTP method to pass to the rule. |
Default To | Enter a native service endpoint to route the request to in case all routing rules evaluate to False. Then, click the icon next to this field and complete the Configure Endpoint Properties dialog box, as described for the Route To field above. |
HTTP Method | The HTTP method to pass to the native service. Typically you want to pass each request to the native service with the same HTTP method that is contained in the request. For example, if a request contains a GET method, you allow the GET method to be passed to the native service. In this case, select the value CUSTOM, which is a context variable that contains the HTTP method that is contained in the request. However, in other cases you might want to change the HTTP method of a request to a different HTTP method. In this case, you can specify the different method explicitly (by selecting the GET, POST, PUT or DELETE value), or you can specify the different method dynamically on a per-request basis. If you want to specify the method dynamically, select the CUSTOM option and then write an IS service to set the value of the context variable. For more information, see Changing the HTTP Method of a REST
Virtual Service. |
Use credentials from incoming request | Default. Authenticates requests based on the credentials specified in the HTTP header. CloudStreams passes the Authorization header present in the original client request to the native service. |
Use specific credentials | Authenticates requests according to the values you specify in the User, Password and Domain fields. |
Invoke service anonymously | Does not authenticate requests. |
Use existing HTTP Headers | Use the HTTP headers that are contained in the requests. |
Customize HTTP Headers | Use the HTTP headers that you specify in the Name and Value columns on this page. If you need to specify multiple headers, use the plus button to add rows. |