Service-client bindings contain information about how the
EGL runtime code connects to a service that is being invoked by your
logic.
To add the binding information:
- In the deployment descriptor editor, open the deployment descriptor.
- On the Service Client Bindings tab, under
Service Client Bindings, click Add.
- In the Add a Service Binding window, click Native
Binding and then click Next. The Add
a native binding window is displayed.
- Specify a binding key, which is the name of the client-service
binding. You also reference that name in the @BindService property
in your code; the name ties the service-access variable to the binding.
Either enter the binding key or do as follows:
- Click the Browse button, which is next
to the Native Binding Name field. The Interface
Selection window is displayed.
- Select the name of the Interface part that is the basis of a service-access
variable in your code. If that name is the binding key, you do not
need to specify the name when you code the @BindService property
in your code.
- Click OK.
- Choose a protocol type for the service-client binding:
- If you have defined a sharable protocol for the service, click Choose
from protocols and select the shared protocol from the
list
- Choose the protocol JAVA400. With JAVA400, the Java™ client manages the connection details.
- Set the following attributes:
- conversionTable
- The name of the conversion table that converts data on a call
to the service. Conversion is necessary when the code page that is
used for encoding text on the service is different from the encoding
that is used on the client. For more information about conversion
tables, see "Data conversion."
- library
- The name of the library in which the service is located on the IBM® i system
- location
- The server and path on which the service is located, such as myServer.myCompany.com/myService
- password
- The password for the IBM i
system. Specify the user ID with the userID option.
- userID
- The user ID for the IBM i
system. If the connection type is JAVA400J2C, the security credentials
are usually handled by the application server; but if you specify
user ID and password in the connection, the values that you specify
are used.
- Click Finish. The new client binding is
listed in the Service Bindings list. You can
update the binding information later by returning to the Native Binding
Details section.