Behavior of "Web Service SOA" business class is modified, so that they send packages without comments.

Behavior of functionality is altered, so that it is not possible changing WSS user after it has been published.

The requirements which must be met so that Apia is capable of publishing business classes/user's queries/processes' start/ processes' tasks as WebServices.

Web Services in Apia are modified so that "Date" values travel in a standard format.

Environment's information is added to the list of Web Services.

Generation of the classes (ej. Java) necessary to communicate with the Web Services provided by Apia.

A business class was created so that Apia can access to Web Services only specifying: URL, URI, name of the method, parameters of entrance to the method and the return of the method.

Create a zip with the documents attached to an entity and transform it into a String. Then, perform the opposite procedure, from a String generate once more the zip and associate it to an entity. It is useful to send documents through Web Services because they are send through parameters of String type.

The business classes executed through the Web Service available (using the class ApiaWSSoapBindingStub) will have to return an error code that corresponds to each problem found in the exchange.

It is desirable to be able to communicate from an external system with APIA as to establish an interaction, whether it is with the purpose of executing a business class or queries that are configured in APIA.

Synchronize two Apia processes in different servers. Lets suppose that there is an origin process A that wants to send information to a destination process B.

The business classes executed through the available Web Service (using the class ApiaWSSoapBindingStub) must return an error code that corresponds to each problem found in the exchange.

This document explains the creation of Web Services starting from Apia's wdsl file and the possible problems found in the .Net and J2EE platforms.