Refer to the application server manuals for information on designing and developing a user-developed Web service. This section explains the points to consider when designing a user-developed Web service, as follows.
Integrating similar processes
If multiple recommendations are to be made to an individual, rather than separating Web services by recommendation, group them into one Web service to create one SOAP listener definition, and then use calling parameters to divide up the Web service processes to be executed.
Separating processes with different responses or targets
If processes have different responses or targets, as with "recommend to a person" and "control a device", the internal logic of the Web service and testing methods will differ, so consider developing such processes as separate applications.
Execution environment of a Web service with operation checked
This product checks the operation of user-developed Web services in the Web service execution environments below. If executing using another product, perform sufficient connection testing.
Product name | Details |
|---|---|
Interstage Application Server | Checked if a Java EE Web service is used. |
Apache Axis2 | Open source Web service execution framework. The URL is as follows: http://axis.apache.org/axis2/java/core/ |
If a product other than those above is to be used, check that "Content-Length", "Content-Type", and each value have been set correctly in the HTTP header that will form the response from the user-developed Web service to the CEP engine.
