As an alternative to web services, EGL client applications can access EGL service applications as EGL services. This method offers better performance then web services, but it can be used only between two EGL applications. For the broadest compatibility, this tutorial uses web services, which can be used between two EGL applications, two non-EGL applications, or an EGL application and a non-EGL application. For more information, see the EGL documentation by clicking .
Service binding information is contained in an EGL deployment descriptor. In these steps, you work with the project's deployment descriptor and configure the project's build descriptor to use that deployment descriptor.


WSDL files communicate information about services to clients, describing the functions provided in the service and specifying the location of the service. In this section, you generate a WSDL file from the service. Later, your client application will import this WSDL file and use the information in it.
EGL uses the information in the deployment descriptor file and the service part itself to generate a WSDL file, but it needs one more piece of information: on which port the server will host the service. By default, the port is 9080. Follow these steps to find out the port number of your server:




In the real world, services run independently of the clients that use them. To simulate this situation, you could create a new instance of the application server and run the service there. For the sake of this tutorial, there is no advantage to consuming these additional resources, so you will run the service on your existing application server at the time you test your client.