Mandatory application server
Before you can use Interstage Studio to develop Web services, the Interstage Application Server function or Interstage Application Server client package must be installed.
WSDL location information
Location information (URL of the Web service) as defined in a WSDL file will be output to files that are created from the WSDL file. To change the runtime environment, you can change the connection destination by customizing the environment setting without rebuilding the application. However, it is easier to use the WSDL file that contains location information for the Web service to be used.
Publicly available WSDL files that can be acquired through Interstage Management Console contain location information that is updated to reflect the environment at the deployment destination. By using these files, you need not consider the connection destination.
If you are also developing a Web service application at the same time, however, you can use the WSDL files of development resources as is, without having to perform deployment or other such work, by specifying debugging environment location information in the Web Service wizard in advance. Web service applications and Web service clients can thereby be developed in parallel.
If the Web Service Client is a J2EE application and JNDI lookup is used to acquire the service interface, you do not need to know the location information that is described in the WSDL file.
Interoperable destinations
The WS-I Basic Profile has been established to provide guidelines for Web services to improve interoperability. These guidelines mainly specify the formats of messages exchanged by Web services, and they include WSDL coding instructions.
Migration of old resources
Older versions supported the Messaging and RPC methods as message exchange methods.
The RPC method can still be applied to the application implementation code, though it involves an incompatibility, such as in the available types.
From the viewpoint of interconnectivity and for other reasons, Interstage does not recommend using an existing WSDL file. To reuse existing development resources, follow the procedure below.
Create a service endpoint interface.
If you have been using an interface that conforms to the applicable standards for service endpoint interfaces, you can continue using it as is. If the used data type of the interface does not conform to the standards, re-create the service endpoint interface with a valid data type.
If you have no existing interface, create a service endpoint interface with a valid data type appropriate for publicly available functions.
Create files with the Web Service wizard.
Create the files required for Web services from the service endpoint interface.
Port the implementation process.
Using existing implementation code, port the process with consideration of essential information such as the changes to the data type or the differences in the execution environment.
Web services operating only in J2EE execution environments with the same VM type
Web services operate only in the [Web and EJB Applications run in the same Java VM] type of J2EE execution environment.
