A service client binding is a definition that
gives details on how a requester is to access a service. The type
of binding depends on how the requested service is deployed.
Here are the types of bindings:
- SOAP (Web) binding. In this case, data is transferred across
the Web in a text-based format called SOAP.
A
Rich UI application or service can access a SOAP service. You can
define the binding in code or in the EGL deployment descriptor.
For
details on SOAP, see “Architectural styles in Web services."
- REST (Web) binding. In this case, data is transferred across
the Web in a text-based format but not in a SOAP format.
A Rich
UI application or service can access a REST or an EGL REST service.
You can define the binding in code or in the EGL deployment descriptor.
For
details on REST, see “Architectural styles in Web services."
- EGL binding. In this case, binary data is transferred in
a format that is specific to EGL. With an EGL binding, the connection
is relatively fast, but non-EGL-generated code cannot access the service.
Here
are details on the product's support for EGL binding:
- A Rich UI application can access an EGL service that is local
to the Rich UI proxy, but cannot access other EGL services. The deployment
descriptor is not used for accessing a local EGL service from a Rich
UI application; you use a simple syntax in code. For details on that
syntax, see “Declaring an access variable to access a local EGL service.”
- An EGL-generated service or related library can access these EGL
services:
- An EGL service that is local to the requester, in which case you
can define the binding in code or in the EGL deployment descriptor
- An EGL service that is remote from the requester, in which case
you can define the binding only in the EGL deployment descriptor
- Native binding. In this case, data is transferred in a
binary format that provides direct access to an IBM® i service program. You use the JAVA400 protocol.
A
service can access an IBM i
service program in this way. A Rich UI application cannot. You can
define a native binding only in the EGL deployment descriptor.