Steps in Using a Service
Using a Service involves the following steps:
| 1. | Write the Service, or adapt existing implementations. A Service can be virtually any type of implementation: a library (DLL or .so), a .NET assembly, a Java class, an R function, a command, script or executable, or even an Excel spreadsheet. You do not need to link a Service with any DataSynapse libraries, but make sure that the remotely callable methods of the Service follow conventions that enable cross-language execution and support stateful Services. For details, see Client Calling Conventions. |
For examples of code using Services, see the GridServer SDK and the GridServer Service-Oriented Integration Tutorial.
| 2. | Deploy the Service. Make the implementation and other resources required for the Service accessible from all Engines. Do this through GridServer’s mechanism of resource deployment. |
| 3. | Register the Service Type. Make the Service visible to clients by registering it as a Service Type in the GridServer Administration Tool. |
| 4. | Create a Service Session from a Client. Develop a Client Application that accesses the registered Service Type and creates a Service Session. Each Service Session has its own state that is client-specific. |
| 5. | Make requests. The Client Application calls the methods of a Service Implementation either synchronously or asynchronously. |
| 6. | Destroying the Service Session. Client Applications destroy Service Sessions when they are done with them. |
This section describes how to develop a Service Implementation that runs on an Engine. Accessing Services describes how to use this Service Implementation from a Client Application.