The properties of an EIS export binding are shown in the properties
view of the assembly editor after generating the SCA artifacts using the enterprise
service discovery wizard.
Prerequisite: You should have a module and an export with an
EIS binding.
This section describes the EIS export binding properties you would
have and could modify after generation of SCA artifacts by the enterprise
service discovery wizard. Why would you modify the values in the properties?
You might want to change the size of log and trace files or user names and
passwords. In this set of steps, we will look at the properties view where
these changes could be made.
After generating an EIS export binding with
the wizard, you can also use hover help to get descriptions of the fields
in the properties view.
- To see the EIS export binding properties, open the export in the
assembly editor. Right-click the export and from the contextual menu, select Show
in Properties. Select the Binding tab. The name of the
adapter, the data binding class name and the function selector class name
are shown. You can add a binding description.

- Selecting the Endpoint configuration tab
and the Connection tab, opens the connection properties.
You may specify a JNDI lookup name. If a JNDI lookup name is specified, the
activation specification class and its properties will be disabled. In our
case, a JNDI lookup name was not specified. The Activation Spec
Properties section specifies the properties for the activationspec
class, which represents the configuration required to establish the connection
between the service and the EIS system. Specifically, these properties specify
the database name, the user id and password, polling period and credentials. Show
Advanced specifies the listener type.

- Selecting the Endpoint configuration tab
and the Resource Adapter tab, specifies the resource
adapter name, class name and the properties of the resource adapter. The name
of the resource adapter needs to match the name of the resource adapter as
it is deployed. If the resource adapter is embedded in the module, then the
name must be the application name (that is, the module name)+'App'+'.'+'<display
name of the resource adapter>', as you see it presented here. If the resource
adapter is not embedded in the module, then it must match the name of the
resource adapter as it is installed on the server.

- Selecting the Method bindings tab, provides interaction
information at the method level. Specifically, methods and, if necessary,
data binding classes for input and output at the method level.

- Selecting Security attributes and expanding
the Authentication Properties section opens the authentication properties.
The J2C authentication data entry name is shown (if it had been specified
when the component was developed). If Show Advanced is selected, authentication
properties are opened such as the level of the authentication; for example,
at the container level.

- Selecting the Performance attributes tab
shows performance-related properties. The Interaction Style property
can have these values: sync (default), async or any.
Select sync if you want a synchronous form of delivery;
that is, the transfer of data will take place in real time. Select async if
you want an asynchronous form of delivery; that is, the transfer of data will
be passed to a messaging system where it will be stored and passed on to the
target component. Selecting any will result in the
sync behavior. The Asynchronous Reliability property can have these
values: assured (default) or bestEffort.
Select assured if you want a message to persist through
a transaction. In other words, if you want guaranteed delivery of the message.
Select bestEffort if you want a high throughput of
messages and your application can accept and handle the loss of a message,
as persistence is not guaranteed.

You have examined the properties of a generated EIS export binding.
Compare these properties with the properties of a generated EIS import binding.