The following figure shows how OpenEdge allows you to define a client interface using the Open Client Toolkit.
Figure 15. Client interface definition for Open Clients
Using the ProxyGen tool, you specify the procedures of the AppServer application service that you want to include in the client interface and how you want to represent them in terms of the Open Client object model. From this common interface definition, you can then generate:
.NET Open Client — Proxy objects in the form of a .NET assembly.
Java Open Client — Proxy objects in the form of a set of Java classes.
Web service Open Client — The client interface definition in a form that eventually becomes a WSDL file for use by Web service clients (or client developers) to generate the client interface itself.
Sonic Web Service — The Sonic Web Service definition for the OpenEdge Adapter for Sonic ESB Web Service Invocation methodology. The Web Service Invocation methodology takes a WSM file as its primary input, and you can edit it with a custom OpenEdge resource editor accessed through the Sonic Management Console.
Sonic Native — The Sonic Native Invocation file (.esboe file) for the OpenEdge Adapter for Sonic ESB Native Invocation methodology. An invocation file is dropped onto the canvas of the Sonic ESB Process Editor in Sonic Workbench to create a new step in an ESB process.
The Open Client Toolkit contains additional tools to facilitate Open Client implementation, depending on the type of Open Client. For more information on ProxyGen and the entire Open Client Toolkit, see OpenEdge Development: Open Client Introduction and Programming.
.NET Open Client — Proxy objects in the form of a .NET assembly.