Example of an weblogic-ra.xml file

Example 4 shows the definition of the general configuration properties in the file weblogic-ra.xml.

Example 4 Configurations- properties in the weblogic-ra.xml file

The section containing the general configuration properties in the file weblogic-ra.xml has the following structure:

<weblogic-connector   
   xmlns="http://xmlns.oracle.com/weblogic/weblogic-connector"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-connector
   http://www.oracle.com/technology/weblogic/weblogic-connector/1.3/weblogic-connector.xsd">
   <jndi-name>BeanConnect</jndi-name>  
   <enable-global-access-to-classes>true</enable-global-access-to-classes> (1)
   <work-manager>
     <name>BeanConnect_WorkManager</name>
   </work-manager>
 <connector-work-manager>
     <!-- For inbound communication the BeanConnect resource adapter starts a long-running
          work instance, which listens at the inbound listener port. 
          Each BeanConnect proxy work process establishes a
          connection to the BeanConnect resource adapter. For each
          connection the BeanConnect resource adapter starts a long-running
          work instance.
          The maximum number of concurrent long-running Work instances will
          be specified with the following property. 

         Default value: 10
     -->
     <max-concurrent-long-running-requests>12
     </max-concurrent-long-running-requests>
   </connector-work-manager> 
<security>
   <security-work-context>
       <!-- Two choices related to establishing the caller identity for a 
            work instance are described in
            JSR 322: Java EE Connector Architecture 1.6 
            The default value is false, which means Case 1. 
            All caller-principal-mapping and group-principal-mapping
            subelements are ignored. 
            If set to true, it means Case 2. 
            All caller-principal-mapping and group-principal-mapping
            elements are used to determine the correct mapping from the
            EIS security domain to the WebLogic domain.
       -->
       <inbound-mapping-required>false</inbound-mapping-required>   
     <caller-principal-default-mapped>
        <!-- Used for Inbound Message Endpoint invocation if inbound mapping
             required and a user is inflowed who has no explicit mapped
             caller principal  -->
        <!-- 
          <use-anonymous-identity>true</use-anonymous-identity>
        -->
        <principal-name>BcDefaultMappedPrincipal1</principal-name>
      </caller-principal-default-mapped>
      <caller-principal-mapping>
        <eis-caller-principal>EISUSER1</eis-caller-principal>
        <mapped-caller-principal>      
          <!-- 
            <use-anonymous-identity>true</use-anonymous-identity>
          -->
          <principal-name>AsPrincipal1</principal-name>
        </mapped-caller-principal>
      </caller-principal-mapping>

      <caller-principal-mapping>
        <eis-caller-principal>EISUSER2</eis-caller-principal>
        <mapped-caller-principal>      
          <principal-name>AsPrincipal2</principal-name>
        </mapped-caller-principal>
      </caller-principal-mapping>
      <caller-principal-mapping>
        <eis-caller-principal>EISUSER3</eis-caller-principal>
        <mapped-caller-principal>      
          <principal-name>AsPrincipal3</principal-name>
        </mapped-caller-principal>
      </caller-principal-mapping>
      <caller-principal-mapping>
         <eis-caller-principal>EISUSER4</eis-caller-principal>
         <mapped-caller-principal>      
           <principal-name>AsPrincipal4</principal-name>
         </mapped-caller-principal>
      </caller-principal-mapping>
   </security-work-context>   
</security>
</weblogic-connector> 

(1) This property is absolutely essential for correct operation!