Skip navigation.

Upgrade Guide

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

Upgrading an Adapter Development Project

This section describes the steps for converting a WebLogic Integration 7.0 SP2 Adapter Development Kit (ADK) adapter development tree to an 8.1 ADK adapter development tree.

Note: In WebLogic Integration 8.1 SP2, connection factories are now part of the adapter instances. For more information, see Upgrading WebLogic Integration 7.0 SP2 Adapters Developed by ADK to WebLogic Integration 8.1 SP2

  1. Implement WebLogic Integration Resource Adapter by extending AbstractWLIResourceAdapter using BEA_HOME/weblogic81/integration/adapters/sample/src/sample/spi/ as a guide, where BEA_HOME represents the WebLogic Platform 8.1 home directory. Keep the following in mind as you implement the adapter.
  2. The following steps prepare your WebLogic Integration 7.0 SP2 adapter properties file to work in the build scheme for WebLogic Integration 8.1. The new scheme separates the adapter-specific properties from the ADK-defined properties into separate files. These files are merged at build time. See step 5 below for the build changes.
    1. Rename the adapter properties file named <Adapter Logical Name>.properties to <Adapter Logical Name> (for example, is renamed to
    2. In the renamed file, remove all properties not related to the JSP pages in your adapter's source tree. For example remove any properties starting with depappvw_ because the depappvw.jsp exists in the ADK, not your adapter.
    3. Remove all properties not related to the run-time messages that your adapter explicitly defines. The rule of thumb is that if the property or message exists in do not include it in your adapter properties file.
  3. The following steps prepare your WebLogic Integration 7.0 SP2 design-time Web application's web descriptors (web.xml, weblogic.xml) to work in WebLogic Integration 8.1 build scheme. The new scheme separates the adapter-specific information in these descriptors into separate files from the generic (ADK or WebLogic Server defined) information. The new scheme generates the web.xml and weblogic.xml files based on a simple properties file that you provide in your adapter source. See step 5 below for the build changes.
    1. Create a new .properties file called in your WebLogic Integration 8.1 <adapter root>/src/war/WEB-INF directory. The properties that go into this file are described in the steps that follow. Basically, these properties will be derived from the contents of the web.xml file in the same directory.
    2. Add a property called display-name, and give it the value you used for the display-name of you web.xml descriptor. For example, the following display-name element in the web.xml:
    3. <web-app>


    4. Add a property called version, and give it the value of the context-param element in web.xml with param-name of version.
    5. Add a property called request-handler-class and give its value as the class name for your design-time request handler. This value can be found in the existing web.xml file in the controller servlet definition's RequestHandlerClass init-param. It looks like this in the web.xml file:
    6. <!-- Controller servlet -->



      <description>Class that handles design time requests</description>


    7. Add a property called adapter-logical-name and give its value as the logical name for your adapter (for example, MyAdapter_1_0).
    8. Add a property called debug-setting and give it the value on or off. This should be the same value as the value in your controller servlet's init-params in the old web.xml file.
    9. Add a property called extra-jsp-list that lists the JSP pages you have added for your adapter. This is in addition to those JSP pages already defined in the ADK. This list is a comma-separated list of extra JSPs. The standard JSPs are addevent, addservc, confconn, edtevent, edtservc, event, service, and testform; do not include them in the extra-jsp-list. For example if you add a JSP called mybrowser.jsp, your extra-jsp-list would look like the following:
    10. extra-jsp-list=mybrowser
    11. Delete your existing web.xml and weblogic.xml descriptors. You can back up these files if you have customized them. Most adapters do not have custom web.xml and weblogic.xml descriptors.
  4. Edit the <adapter root>/src/ear/META-INF/application.xml file and remove the web module definition for the event router. For example, the text removed for the sample adapter is as follows:
  5. <module>
  6. Modify your <adapter root>/build.xml file, as follows:
  7. Note: The following instructions assume that your build.xml file is based on the build.xml file provided with the ADK. If your build.xml file in not based on the ADK's build.xml file or if you have extensively modified it, you will need to adjust these instructions to account for these differences.

    1. Eliminate the event router JAR and WAR.
    2. In build.xml, delete the eventrouter_jar and eventrouter_war targets and any references to them.
    3. Add <your adapter package>/event/*.class to the class includes definition of the JAR target. It looks like this:
    4. ...

      From the adapter's source directory, include the "includes" list
      For this adapter, all the classes in the sample/cci, sample/event
      and sample/spi packages are included as well as the log configuration
      file and message bundles
      <fileset dir='${SRC_DIR}'
      sample/spi/*.class, sample/eis/*.class,

    5. Add the following to the JAR command under your EAR target after the zipfileset element for the adk.jar file:
    6. <zipfileset src='${WLI_LIB_DIR}/adk-eventgenerator.jar'>
      <exclude name='META-INF/MANIFEST.MF'/>
    7. Add the following text to the top of your packages build target. This text calls ant tasks in the ADK that generate the web descriptors (web.xml and weblogic.xml) for your adapter. It also merges your adapter-specific properties file with the properties file to yield the final merged properties file required for proper operation of the adapter.
    8. <!-- Generate web descriptors. NOTE: You can turn this off if you want
      to tightly control your web.xml/weblogic.xml. In this case,
      simply maintain these files in your src/war/WEB-INF instead of -->
      <ant dir='${WLI_HOME}/adapters/utils/ant'
      <property name='web_gen_props_file'

      <!-- Merge the file and your adapter-specific properties
      into the final properties file that will be used by the adapter
      <ant dir='${WLI_HOME}/adapters/utils/ant'
      <property name='props_dir' value='${SRC_DIR}'/>
      <property name='adapter_props_file'
      <property name='target_props_file'
  8. Remove the entire <adapter root>/src/eventrouter directory.
  9. Change the SYSTEM identifier in <adapter root>/src/rar/META-INF/weblogic-ra.xml from
  10. PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 Connector//EN'


    PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 Connector//EN'
  11. Change the <shrink-period-minutes> element in <adapter root>/src/weblogic-ra.xml to <shrink-frequency-seconds> and multiply the current element's value by 60.

This completes upgrading your ADK.


Back to Top Previous Next