AIAMigrationUtility avoid NullPointerException in CompositeUtil.java

Using the AIAMigrationUtility in AIA 11g R1 we encountered the following error:

invokeMigrationUtility:
[echo]

[exec] setupMDSstore:
[exec]
[exec] bpel:
[exec] [upgrade]

[exec] [upgrade] Reading WSDL Location http://lnx40.deltalounge.net:8001/soa-infra/services/default/AIAAsyncErrorHandlingBPELProcess/client?WSDL
[exec] [upgrade] Jul 26, 2010 3:27:34 PM oracle.viewgen.ViewGenerator main
[exec] [upgrade] SEVERE: Upgrade failed. Check the logs for any exceptions. Ensure that the WSDL URLs specified in the project are reachable and a valid 10.1.3.x project is used for upgrade. Before re-attempting upgrade, restore the original project code source from the backup directory.
[exec] [upgrade] java.lang.NullPointerException
[exec] [upgrade] at oracle.viewgen.composite.CompositeUtil.setupBinding(CompositeUtil.java:686)
[exec] [upgrade] at oracle.viewgen.composite.CompositeUtil.setupCompositeServices(CompositeUtil.java:444)
[exec] [upgrade] at oracle.viewgen.composite.CompositeUtil.createComposite(CompositeUtil.java:315)
[exec] [upgrade] at oracle.viewgen.ViewGenerator.main(ViewGenerator.java:316)
[exec] [upgrade] Exception in thread “Main Thread” java.lang.NullPointerException
[exec] [upgrade] at oracle.viewgen.composite.CompositeUtil.setupBinding(CompositeUtil.java:686)
[exec] [upgrade] at oracle.viewgen.composite.CompositeUtil.setupCompositeServices(CompositeUtil.java:444)
[exec] [upgrade] at oracle.viewgen.composite.CompositeUtil.createComposite(CompositeUtil.java:315)
[exec] [upgrade] at oracle.viewgen.ViewGenerator.main(ViewGenerator.java:316)
[exec]
[exec] BUILD FAILED
[exec] /fs01/app/oracle/esbtst01/weblogic/Oracle_SOA1/bin/ant-sca-upgrade.xml:71: Java returned: 1
[exec]
[exec] Total time: 5 seconds

BUILD FAILED
/fs01/app/oracle/esbtst01/weblogic/aia30/util/AIAMigrationUtility/AIAMigrationUtility.xml:58: The following error occurred while executing this line:
/fs01/app/oracle/esbtst01/weblogic/aia30/util/AIAMigrationUtility/AIAMigrationUtility.xml:140: exec returned: 1

Total time: 7 seconds

This was solved (unexpected) by altering the adf-config.xml in the .adf/META-INF/ directory for the workspace. The following was added:

          <namespace metadata-store-usage="mstore-usage_2"
                     path="/apps/AIAMetaData"/>
....
          <metadata-store-usage id="mstore-usage_2">
            <metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
              <property value="DEV_MDS" name="jdbc-userid"/>
              <property value="poctst01" name="jdbc-password"/>
              <property value="jdbc:oracle:thin:@lnx42.deltalounge.net:1521:poctst01"
                        name="jdbc-url"/>
              <property value="soa-infra" name="partition-name"/>
            </metadata-store>
          </metadata-store-usage>

In other words the connection information for the MDS has been provided.

Update ANT and MDS

Today I came across his blogpost on another ANT script using MDS during deployment. Which requires a similar solution: altering the adf-config.xml in the .adf/META-INF/ directory.

Leave a Reply

Your email address will not be published. Required fields are marked *