Retrofit BAM Data Objects when encountering: BAM-02501: There is no data object named

In the logfile of our Oracle SOA Suite environment, I noticed error messages relating to BAM.

####<Dec 19, 2013 11:41:50 AM CET> <Notice> <Stdout> <soasuite.vanesch.org> <soa_server1> <BAMActionMDB> <<WLS Kernel>> <> <b326bf8f2481a86f:21628deb:1430a284ec9:-8000-00000000000048d0> <1387449710775> <BEA-000000> <<Dec 19, 2013 11:41:50 AM CET> <Error> <oracle.soa.bpmn.engine.sensor> <BEA-000000> <<?xml version="1.0"?><ICommandLog Login="BAMAdapter"><OracleBAMExport Version="2025"><Error Command="Export"><![CDATA[BAM-02501: There is no data object named /Demos/Tony/BI_cube. [ErrorSource="ImportExport", ErrorID="Export.DataObject.NotFound"]]]></Error></OracleBAMExport>BAM-06001: details -- {0}BAM-02501: There is no data object named /Demos/Tony/BI_cube.>>

The Oracle BPM engine has sensor values, which are processed through the BAM adapter. The BAM adapter tries to push these values to the BAM repository, but fails because some data objects are missing (BAM-02501: There is no data object named /Demos/Tony/BI_cube). These data object definitions are related to BPM composites. Let’s check which data objects are actually available. Through the BAM webinterface we can start the BAM Architect to browse the data objects.

Go to the url http://yoursoaserver:9001/OracleBAM logon and click on ‘Architect’

You are now presented with a view of all the objects in BAM.

You can browse the folders and see wether and/or what (sub)folder is missing.

The rootcause for this problem is not exactly clear. We do know that at deploytime of the composites, the BAM Adapter was not yet correctly configured. So it could be that this faulty BAM adapter configuration contributed to the missing BAM Data Object definitions.

To fix this problem, we need to have the relevant metadata inserted into the BAM repository again. There are some solutions available to solve this problem.

• Deploy the concerning composites again, with a working BAM adapter, so the Data Objects get created. But we do not need a new version of the composite, as the composite itself is fine.
• Export the data object definitions from another repository and import them into the problematic repository. This would be the least disruptive way to correct the issue.

With Oracle BAM comes a commanline tool called ICommand to manipulate the Active Data Cache. To use the tool we need to configure one attribute in $SOA_ORACLE_HOME/bam/config/BAMICommandConfig.xml

Change the value of ServerName tag from localhost to the name of your machine running BAM (eg: <ServerName>soasuite.vanesch.org</ServerName>). This is necessary if your weblogic server is explicitely listening on a specific ipaddress or you are running this command from another machine. Now we can execute the icommand utility.

Let’s export the data definitions from a BAM repository. This export file can be used to import definitions into another BAM repository.

$SOA_ORACLE_HOME/bam/bin/icommand -CMD export -MATCH "/Demos/*" -file $ORACLE_BASE/backup/BAM_DO_Demos_full_definition_only_$(date +%Y%m%d).xml -contents 0 -debug 1

Importing the definitions into another repository.

$SOA_ORACLE_HOME/bam/bin/icommand -CMD import -file $ORACLE_BASE/backup/BAM_DO_Demos_full_definition_only_20131219.xml -preserveowner 1 -debug 1

To verify that the data objects are now present, logon to the BAM architect. The BAM adapter should now have no problem anymore in pushing the sensor values.

References

Fusion Middleware Developer’s Guide for Oracle SOA Suite – G Oracle BAM ICommand Operations and File Formats