The Service Test builder generates the code necessary to execute and display the results of a service.
The service can be either a public service created by the Service Definition builder, or a local service produced by an integration builder (for example, the SQL Call or SAP Function builder).
This builder can generate an index page that allows you to choose a service operation to run. If the operation you select accepts inputs, an input page is also generated and displayed to collect input values. When the operation is complete, a result page is displayed.
If a service operation has inputs which need to be set to specific values, you can use the Specify Default Inputs
input to provide values for these inputs in the builder call. These input values are used as the default value in the generated input page.
This builder also generates one method that does not require any argument per service operation. You can use these methods to test the service without a user interface (UI). If these methods are present, they are used by the Service Stub builder to create sample data. If the Specify Default Inputs
input is chosen, these test methods pass the created data values to the corresponding operations. Otherwise, empty input values are passed, which may or may not work, depending on the requirements of the operation in question.
The Service Test and Service Documentation builders (and their use in the Service Definition builder and Web Service Multiple Operation builder) are for use in testing your service provider models and in running them stand-alone on an application server. Use the builders only in stand-alone environments to develop and to debug your service provider models.
Do not use these builders as the user interface (UI) in a portlet, because portlets typically consume service providers and not the service provider model itself.
Parent topic: Builder help
About using the builder call editor
Working with data services