Service-client bindings contain information about how the
EGL runtime code connects to a service that is being invoked by your
EGL code.
To add the EGL 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 EGL
Binding and then click Next. The Add
an EGL 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 EGL 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 client binding:
- If you have defined a shared protocol for the service, click Choose
from protocols and select the shared protocol from the
list.
- Choose a specific protocol type. EGL supports the following types
for accessing an EGL service:
- Local
- For a client that accesses a service locally, without use of a
protocol
- CICSECI
- For a Java™ client that accesses
a COBOL service through the CICS® Transaction
Gateway (CTG) ECI interface
- CICSJ2C
- For a Java client that accesses
a COBOL service through a J2C connector for the CICS Transaction Gateway
- CICSSSL
- For a Java client that accesses
a COBOL service through the Secure Socket Layer (SSL) features of CICS Transaction Gateway (CTG)
- JAVA400
- For a Java client that accesses
a COBOL service that is on IBM® i.
In this case, the Java client
manages the connection details.
- JAVA400J2C
- For a Java client that accesses
a COBOL service that is on IBM i.
This option is available only if the Java client
is running under a fully JEE-compliant application server: for example, IBM WebSphere® Application
Server rather
than Apache Tomcat. When JAVA400J2C is in use, the application server
manages the connection details, such as security credentials. EGL-generated
applications should not share J2C connectors with non-EGL-generated
applications.
JAVA400J2C does not support a stateful connection,
but people can use it to control the current library and library list
that is used on the host.
- TCPIP
- For a Java client that accesses
a Java service through the TCP/IP
protocol
- Depending on the type of protocol, the deployment descriptor editor
will prompt you for some of the following values for 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 information about conversion tables,
see "Data conversion."
- ctgKeyStore
- The name of the key store that is generated with the IKEYMAN CICS Transaction Gateway tool
- ctgKeyStorePassword
- The password that is used when generating the key store
- ctgLocation
- The URL for accessing the service through a CICS Transaction Gateway (CTG) server. Specify
the related port with the ctgPort option.
- ctgPort
- The port through which to access a service through a CICS Transaction Gateway (CTG) server
- library
- For a JAVA400 connection, the name of the library in which the
service is located on the IBM i
system. For a JAVA400J2C connection, specify a value in the following
form:
currentLibrary:libraryList
- currentLibrary
- The current library, which sets the library on the host job. For
example, *USRPRF.or *CRTDFT.
- libraryList
- A list of libraries, in which each entry is a library name that
is followed by a position value that defaults to * LAST. This structure
ensures that the entry is placed after any entries that have the alternative
position value, which is *FIRST.
This example shows a value for
library:
*USRPRF:MYMQLIB,MYFILLIB,MYDBLIB *FIRST
- location
- For a TCP/IP connection, the location is the TCP/IP host name
or address. For a JAVA400 connection, the location is the server and
path on which the service is located, such as myServer.myCompany.com/myService.
For a JAVA400J2C connection, the location is the JNDI name in the
application server. For a CICSECI or CICSSSL connection, the location
is a CICS system identifier.
For a CICSJ2C connection, the location is the JNDI name of the ConnectionFactory
object that you establish for the CICS transaction
that is started by the call.
- password
- The password for the IBM i
system. Specify the user ID with the userID option.
- serverID
- For a TCP/IP connection, the port number of the listener of the
service. For a CICSJ2C, CICSSSL, or CICSECI connection, the ID of
a CICS transaction that is
being called. The default is the CICS server
system mirror transaction (CPMI).
- 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. If you specify the
user ID and password in the connection, the values that you specify
are used in place of any others.
- Click Finish. The new client binding is
listed in the Service Bindings list. You can
update the binding information later by returning to the EGL Service
Binding section.