WS Routing tutorial
Making an SOAP router endpoint Setting up a SOAP router endpoint

## Example

This chapter describes general guide lines for using routing capabilities of the Virtuoso SOAP server.

In order to have the rest of examples of this section working, the following steps must be performed.

- If you are going to try .NET examples the MS WSDK toolkit must be installed on a W2K machine. The .NET examples are tested with 1.0.0.0 version of Microsoft.WSDK.dll, so make sure that version of that assembly is the same.
- Make sure that WS Routing examples of MS WSDK working before trying any of interoperability examples.
- From this page run the setup script (set the initial state), this will define the routing and ultimate endpoints.

The SOAP directory option we are using to setup a WS Routing (SOAP router) is:

- WS-RP - yes/no , this is to enable WS Routing filter

The VSP page is example how Virtuoso SOAP client can be used to invoke the sample services as AddInt or echoString.Form this page we can invoke these operations via different routers. Note that "Operation to invoke" option must be set properly depending of type of endpoint (see remarks on select page).

The .NET client example must be complied before trying it. To do this follow the steps:

- Change in the RoutingClient.cs and referalCache.config files <virtuoso:port> to host and port where your virtuoso HTTP server is listening.
- compile the example issuing nmake command in the tutorial/services/rp_s_1 directory. On that step you may need to have .NET Visual Studio installed and .NET Framework SDK
- if you going to compile the client on an other box, make sure that referralCache.config file is in the same directory where is .exe file.