Advanced Customization > Info*Engine User’s Guide > SOAP Services > Example Standalone Java SOAP Client
  
Example Standalone Java SOAP Client
Standalone Java SOAP clients can use the Java EE connector to interact with Info*Engine. They do not, however, provide the added value that an application server can bring to your connections.
Writing a standalone Java SOAP client requires the following steps:
1. Decide on the classes and methods required by your application.
2. Implement the required tasks inside of a directory hierarchy that reflects the required classes.
In our example this includes the average.xml and sum.xml tasks in the org/myOrg/Math subdirectory of the task root. These are described in Implementing Tasks and Java Classes.
3. Create the required type identifiers and delegates in the LDAP directory. This is discussed in Registering Delegates.
4. Generate Data Access Objects (DAOs) for each class from Step 1. DAOs are discussed in Generating DAOs.
5. Decide how connections are to be created, and if necessary bind connection factory objects in the LDAP directory. This is described in Creating a Connection Handle and Managing Connection Factories in the LDAP Directory.
6. Write client source code that uses the DAOs from Step 4 to access Info*Engine. This is described in Putting It All Together.
The following sections use a simple example application to demonstrate how a standalone Java SOAP client should communicate with Info*Engine.