A service of the UTM application can be called from WebService clients using WS4UTM. This allows the user to access certain services of a UTM application over the Web.
The WebService client can be used to structure the sign-on process via WS4UTM:
The user specifies a WebService name and a method in his/her WebService client. The WebService is permanently linked to a UTM application by the configuration. A connection to the UTM application is established over UPIC.
The WebService client may possibly execute an intermediate dialog, for instance to obtain proof of authorization.As when using a terminal, the user may have to specify their UTM user ID and password. Whether or not the user has to go through an authorization dialog of this type and the appearance of any such dialog will depend on the way in which the WebService client is structured. It is, for instance possible to "hide" the UTM user ID/password in the WebService client or to specify it within the configuration of the WebService, with the result that the authorization dialog is handled internally.
The job data (TAC and user data) is sent together with the authorization data to a WebService server via http/Soap and then to the UTM application over the UPIC connection. The UPIC connection is cleared again after the response has been returned to the WebService client.
The Apache Axis server is used as the WebService server.
Communication takes place over Apache Tomcat and Axis using Soap messages and the http protocol. WS4UTM uses the UPIC interface in openUTM in order to connect to the UTM application.
For further information, refer to the manual "Web-Services for openUTM".