The WebLogic-specific properties of the resource adapter are described in the deployment descriptor file weblogic-ra.xml
.
The following general configuration properties are relevant:
The JNDI name of the resource adapter is defined in the element
<jndi-name>
in the form in which it must be specified during inbound communication in the elementresource-adapter-jndi-name
of the file<weblogic-ejb-jar.xml>
for each OLTP message-driven bean.The property
<enable-global-access-to-classes>
must be set totrue
in order to prevent errors during the deployment of the applications.In the element
<connector-work-manager>
, the tag<max-concurrent-long-running-requests>
specifies the number of long-running work instances. The default value is 10.Set this number to one higher than the number of work processes for the BeanConnect proxy container. Note that in a cluster configuration, you must take account of the work processes of all the proxy containers in the cluster.
In the
<security-work-context>
element of the<security>
block, you can use the tag<inbound-mapping-required>
to specify whether you want to use case 1 or case 2 of the security inflow types described in the JCA specification.The default value is
false
and stands for case 1. In this case, each user ID that is to be propagated by EIS in the application server must also be configured in the application server. The passwords that have to be defined for the user IDs in the application server are not validated for inbound communication.In case 2, you must configure a mapping of the EIS user ID to a user ID in the application server in the element
<security-work-context>
.See also "Configurations-properties in the weblogic-ra.xml file" in Example of an weblogic-ra.xml file .