Accessing a service

In EGL, you can access several different types of services. To learn the access procedures, see the links in the following table.

Goal Tasks
Access a dedicated or local EGL service
  1. Declaring a variable to access a dedicated or local EGL service
  2. Then, complete either of these tasks:
    1. Invoking a service asynchronously from a Rich UI application
    2. Invoking a service synchronously from outside of Rich UI
Access an EGL REST-RPC service or third-party REST service
  1. Creating an Interface part to access a REST service
  2. Declaring a variable to access a REST service
  3. Optionally, complete this task, which gives you flexibility over time:
  4. Then, complete either of these tasks:
    1. Invoking a service asynchronously from a Rich UI application
    2. Invoking a service synchronously from outside of Rich UI

For details on accessing an EGL REST-RPC service from logic written outside of EGL, see “EGL REST-RPC message structure.”

Access a SOAP service
  1. To create an Interface part, complete either of these processes:
    1. Creating an Interface part to access a SOAP service
    2. Create an Interface part when adding a SOAP binding, as described in Adding a SOAP service binding to the deployment descriptor
  2. Declaring a variable to access a SOAP service
  3. Then, complete either of these tasks:
    1. Invoking a service asynchronously from a Rich UI application
    2. Invoking a service synchronously from outside of Rich UI
Access a remote EGL service, which is possible only from outside of Rich UI
  1. Creating an Interface part from a Service or ExternalType part
  2. Declaring a variable to access a remote EGL or native service
  3. Adding an EGL binding to the deployment descriptor
  4. Invoking a service synchronously from outside of Rich UI
Directly access a native IBM i service program, which is possible only from outside of Rich UI
  1. Creating an Interface part from a Service or ExternalType part
  2. Declaring a variable to access a remote EGL or native service
  3. Adding a native binding to the deployment descriptor
  4. Invoking a service synchronously from outside of Rich UI