Deploying service stubs

You deploy and run service stubs on a stub server, which is a small application server dedicated to running service stubs. The client application, or test, addresses the stub server instead of the actual application of the original service.

Before you begin

The local stub server runs in the workbench on the local computer. Service stubs can be accessed locally. The local stub server is automatically stopped when you close the workbench.

To use a service stub instead of the original service, you must be able to change the endpoint of the client application or service test to replace the URL of the original application with the URL of the stub server.


  1. In the stub editor, click the Deploy button.
    Alternatively, you can right-click the stub in the test navigator and select Deploy On > Local stub server
    This opens the Stub Monitor view.
  2. In the Stub Monitor view, click Run iconRun.
    If you make any changes to the service stub, the stub is redeployed to the stub server after saving.
  3. To add more service stubs to the stub server, click Add and select a service stub from the workspace.
  4. Copy the URL of the service stub from the Stub Monitor view and paste it into the configuration of the client application.
    You can also directly access the WSDL specification of the service stub, which is a copy of the original WSDL with replaced URL endpoints.

What to do next

You can validate that the service stub is responding correctly by using the generic service client to invoke a call.