Connection Factory Exception

I just upgraded DI Metadata Integrator from 11.7.0.0 to 11.7.2.2. While trying to configure the Metadata Repository and test I get the following severe exceptions:

Oct 18, 2007 9:53:44 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Oracle:com.acta.db
.ActaOracleConnectionFactory. null
Oct 18, 2007 9:53:44 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Microsoft_SQL_Serv
er:com.acta.db.ActaMSSqlServerConnectionFactory. null
Oct 18, 2007 9:53:44 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Informix:com.acta.
db.ActaInformixConnectionFactory. null
Oct 18, 2007 9:53:44 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Sybase:com.acta.db
.ActaSybaseConnectionFactory. null
Oct 18, 2007 9:53:44 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for MySQL:com.acta.db.
ActaMySqlConnectionFactory. null
Oct 18, 2007 9:53:44 AM com.acta.db.ActaDbManager init
INFO: BODI-3013011: Delaying the loading of DB2 JDBC driver classes.

When running the test before upgrading I did not receive these severe messages. After the install of 11.7.2.2 is when I started to receive these messages.


cjrajsed (BOB member since 2007-10-18)

First of all, you should use 11.7.2.3 please. Not sure about the actual error. The ActaDBManager is the thing that handles all the connections for the different databases…


Werner Daehn :de: (BOB member since 2004-12-17)

I switched to 11.7.2.3 and this do not fix the problem.


cjrajsed (BOB member since 2007-10-18)

I reverted back to 11.7.0.1 and I no longer receive these exceptions and I can connect to the Metadata Repository. Not exactly the fix I was going for.


cjrajsed (BOB member since 2007-10-18)

Can anybody tell if they configured it successfully with the 11.7 release. Would help if we know it is a common or an exceptional case. We obviously tested it inside our labs but…who knows what the difference could be?


Werner Daehn :de: (BOB member since 2004-12-17)

The problem ended up being missing jars that are not installed when you just install the Metadata Integrator component. If you install the remaining DI components, the ncessary jar files are also installed.

I believe the missing jars were in the following directory:
Data Integrator 11.7\ext\diAdmin\WEB-INF\lib


cjrajsed (BOB member since 2007-10-18)

Thanks!


Werner Daehn :de: (BOB member since 2004-12-17)

I have the same issue;

Metadata Integrator version: 11.7.2.2
Jul 17, 2008 2:58:35 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Oracle:com.acta.db.ActaOracleConnectionFactory. null
Jul 17, 2008 2:58:35 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Microsoft_SQL_Server:com.acta.db.ActaMSSqlServerConnectionFactory. null
Jul 17, 2008 2:58:35 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Informix:com.acta.db.ActaInformixConnectionFactory. null
Jul 17, 2008 2:58:35 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Sybase:com.acta.db.ActaSybaseConnectionFactory. null
Jul 17, 2008 2:58:35 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for MySQL:com.acta.db.ActaMySqlConnectionFactory. null
Jul 17, 2008 2:58:35 PM com.acta.db.ActaDbManager init
INFO: BODI-3013011: Delaying the loading of DB2 JDBC driver classes.

My CMS is on a different server to the one DI is on. If I install the remaining DI components I think I would be in breach of my liscense no?

What is the actual fix for this please? Thanks!


Darth Services :uk: (BOB member since 2007-11-20)

No, it is not a license violation to install DI on your CMS server as long as you are not running the DI job service there (at least that is what support told us). We have had to do that on almost every version of DI to get the Metadata reports working.

  • Ernie

eepjr24 :us: (BOB member since 2005-09-16)

Thanks for the reply Ernie.

Further to this I came across the Knowledge Base Article No: 1203037 - Error: “BODI-3013019…” when activating cmsCollector.cmd in Data Integrator. Also I found out the following when applying it to my scenario of installing BOMM on the CMS server other than a DI server;
[list]

  1. In the knowledge base article under the Resolution heading initially advises to ‘backup the wrapper.properties file’, then it goes on to deal with modifying the ‘classloader.properties’ file. Therefore ‘classloader.properties’ is the actual file to back up.

  2. In the knowledge base article under the Cause heading mentions a file path that does actually not exist if the 11.7.2.2 installation of Metadata Manager only is performed on a server other than the DI server.

  3. According to the DIGettingStartedGuide, page 86, the default directory specified during the Metadata Manager only installation process is ‘C:\Program Files\Business Objects\Metadata Integrator\’. This is incorrect as the default directory shown is is ‘C:\Program Files\Business Objects\Data Integrator 11.7\’.

  4. In the DIGettingStartedGuide, page 71 says after a successful DI installation the Environment Variable ‘LINK_DIR’ should be set, however during the Metadata Manager only installation, a message box indicates it will do this however it does not. This environment variable had to be manually created on the server and the value set to the install path.

  5. The Metadata Manager only installation does not create the folder (and associated contents) ‘C:\Program Files\Business Objects\Data Integrator 11.7\ext\diAdmin*’ which is needed for the filepath and files specified in the ‘classloader.properties’ file and ‘LINK_DIR’ environment variable. I had to create the path specified in the ‘classloader.properties’ and copy the requried .jar files across from one of our DI servers.
    [/list]
    Result = one working metadata manager! :+1: (well almost - this is the universe to webi reports lineage sorted. I still have to figure out getting the universe to warehouse lineage sorted yet… any ideas? I have not used the universe builder facility in DI and manually made the universe from ground floor up).


Darth Services :uk: (BOB member since 2007-11-20)

OK, finally managed to get it working. It seems that when we created our universe, we removed the database owner details from the tables and the metadata profiler was unable to link this to the DI tables…

Filling in the table owner into all the tables in the Universe in Designer, populated the SELECT box of each universe object which subsequently updated the profiler.


Darth Services :uk: (BOB member since 2007-11-20)

Hi all,

I have the same issue. I’ve installed Metadata Integrator on my BOE server. I have faced the same problems as Darth Integrator and made the appropriate changes in my configuration to get it to work. But I still have the following errors when I run the job meta data refresh job from the CMC :


Locale= en_US
CMS Version: 1160
Metadata Integrator version: 11.7.3.6
Nov 10, 2008 8:56:36 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Oracle:com.acta.db.ActaOracleConnectionFactory. null
Nov 10, 2008 8:56:36 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Microsoft_SQL_Server:com.acta.db.ActaMSSqlServerConnectionFactory. null
Nov 10, 2008 8:56:36 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Informix:com.acta.db.ActaInformixConnectionFactory. null
Nov 10, 2008 8:56:36 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Sybase:com.acta.db.ActaSybaseConnectionFactory. null
Nov 10, 2008 8:56:36 AM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for MySQL:com.acta.db.ActaMySqlConnectionFactory. null
Nov 10, 2008 8:56:36 AM com.acta.db.ActaDbManager init
INFO: BODI-3013011: Delaying the loading of DB2 JDBC driver classes.
Unable to create connection to Data Integrator repository. Exception: BODI-3013014: Database driver for 'Oracle' is not loaded. 
Error running the program.
com.crystaldecisions.sdk.exception.SDKException$Unexpected: An unexpected error has occurred
cause:java.lang.Exception: Unable to create connection to Data Integrator repository. Exception: BODI-3013014: Database driver for 'Oracle' is not loaded. 
detail:An unexpected error has occurred
The exception originally thrown was java.lang.Exception: Unable to create connection to Data Integrator repository. Exception: BODI-3013014: Database driver for 'Oracle' is not loaded. 

I have re installed DI as mentioned in the support note #1203037 but I still get that error. :hb:

Could it be a java version issue ? Do you know which jar file contains com.acta.db.ActaOracleConnectionFactory ?
In classloader.properties file, variable %boe_dir% is used :


# Application jars
cp.0.directory=%link_dir%\\lib\\
cp.0.jars=acta_adapter_sdk.jar;acta_tool.jar;log4j-1.2.3.jar

# Business Objects Enterprise jars
cp.1.directory=%boe_dir% <-----------------------
cp.1.jars=cecore.jar;celib.jar;ceplugins.jar;cereports.jar;cesession.jar;corbaidl.jar;ebus405.jar;pluginhelper.jar;rasapp.jar;rascore.jar;serialization.jar;webi.jar;wilog.jar;jtools.jar;boconfig.jar;rebean.jar;rebean.wi.jar;rebean.common.jar

webi.directory=%boe_dir% <---------------------------
webi.jars=webi.jar;wilog.jar;jtools.jar;boconfig.jar

# CMS Metadata Integrator jar
cp.2.directory=%link_dir%\\ext\\cmsCollector\\lib\\
cp.2.jars=cms_md_collector.jar;MMCore.jar;MMCMS.jar

# External jars
cp.3.directory=%link_dir%\\ext\\lib\\
cp.3.jars=xerces.jar;msutil.jar;commons-logging.jar

# Web External jars
#cp.4.directory=%link_dir%\\ext\\diAdmin\\WEB-INF\\lib\\
cp.4.directory=%link_dir%\\ext\\lib\\
cp.4.jars=sqljdbc.jar;ojdbc14.jar;db2java.jar;ifxjdbc.jar;ifxjdbcx.jar;jconn2.jar;jconnect45.jar;mysql-connector-java-5.0.4-bin.jar

# Business Objects SSL jars
cp.5.directory=%boe_dir%\\external\\ <-----------------
cp.5.jars=freessl201.jar;certj.jar;jsafe.jar;asn1.jar;sslj.jar

I have no such environment variable defined on my system. Darth, did you set this variable on yours ?

Thanks in advance for your inputs.


ombo (BOB member since 2005-11-16)

ojdbc14.jar is the oracle library with the driver in it.


Werner Daehn :de: (BOB member since 2004-12-17)

Hi ombo,

While I did not set %boe_dir%, nor is it defined on our server our BOMM still works fine. So I’m not sure if you’re heading down the right path with this anomaly?

However, I noticed a difference in your classloader.properties file to mine. Yours:

Mine:

This depends of course on where you copied the files across from the DI box? Just wanted to clarify this.

Also, just check that all the files it needs to reference are there in that location.

Let us know how you go!

Cheers,

Darth


Darth Services :uk: (BOB member since 2007-11-20)

Another day another dollar - and I find myself faced with this one again.

Previously, with some hacking around it was possible to get this wokring on the windows client, which wasn’t ideal.

This time, trying to get the collector (11.7.3.5) working on an AIX server, where the program job object was installed from the windows client.

Does anyone know if there is a ‘proper’ way to do this for AIX?

For now, I corrected the classpath, removing Windows C:… stuff and replacing with the proper location of the .jar files.

I’ve verified EVERY library is available, including the ojdbc14.jar. All of the DI ones have been shipped in and referenced.
As the same errors were still there, I was scratching my head wondering where I had gone wrong.

I captured the command line, and executed it directly, with the java -verbose option, thinking “Ah, this will definitely show NoClassDefFound if a jar is missing”.
Actually it seemed very happy with my jars, but not happy with the collector code itself, which spawns a bunch of errors.

So, with all the Loaded messages removed, see how the orginal messages above are now interspersed with java/lang/ClassCastException

Don’t know if this will actually help anybody, but if it rings and bells PLEASE let me know for my sanity!

[Signaling in VM: java/lang/ClassCastException, message: com.crystaldecisions.thirdparty.com.ooc.CORBA.StubForObject]
        at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAs.SessionBatchHelper.narrow(SessionBatchHelper.java:94)
        at com.crystaldecisions.sdk.occa.security.internal.e$3.narrow(Unknown Source)
        at com.crystaldecisions.enterprise.ocaframework.e.do(Unknown Source)
        at com.crystaldecisions.enterprise.ocaframework.o.try(Unknown Source)
        at com.crystaldecisions.enterprise.ocaframework.o.a(Unknown Source)
        at com.crystaldecisions.enterprise.ocaframework.o.a(Unknown Source)
        at com.crystaldecisions.enterprise.ocaframework.p.a(Unknown Source)
        at com.crystaldecisions.enterprise.ocaframework.ServiceMgr.getManagedService(Unknown Source)
        at com.crystaldecisions.sdk.occa.security.internal.e.if(Unknown Source)
        at com.crystaldecisions.sdk.occa.security.internal.e.<init>(Unknown Source)
        at com.crystaldecisions.sdk.occa.security.internal.SecurityFactory.makeSecuritySession(Unknown Source)
        at com.crystaldecisions.sdk.occa.security.internal.t.a(Unknown Source)
        at com.crystaldecisions.sdk.occa.security.internal.t.a(Unknown Source)
        at com.crystaldecisions.sdk.occa.security.internal.t.a(Unknown Source)
        at com.crystaldecisions.sdk.occa.security.internal.t.userLogon(Unknown Source)
        at com.crystaldecisions.sdk.occa.security.internal.l.userLogon(Unknown Source)
        at com.crystaldecisions.sdk.framework.internal.d.logon(Unknown Source)
        at com.bobj.mm.integrator.cms.collector.util.CMSSession.fetchEnterpriseSession(CMSSession.java:113)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.run(CrawlerProgramBase.java:94)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.getReportMetadata(CrystalCrawlerMain.java:204)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.main(CrystalCrawlerMain.java:80)
CMS Version: 1159
Metadata Integrator version: 11.7.3.5
[Signaling in VM: java/lang/reflect/InvocationTargetException, message: ]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.acta.db.ActaDbManager.addDBConnectionFactory(ActaDbManager.java:205)
        at com.acta.db.ActaDbManager.init(ActaDbManager.java:78)
        at com.acta.db.ActaDbManager.<init>(ActaDbManager.java:101)
        at com.acta.db.ActaDbManager.getDBManager(ActaDbManager.java:112)
        at com.acta.db.ActaDbManager.getConnection(ActaDbManager.java:145)
        at com.acta.crystalrepo.crawler.DIRepoHandler.initialize(DIRepoHandler.java:78)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.createRepoConnection(CrawlerProgramBase.java:211)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.run(CrawlerProgramBase.java:102)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.getReportMetadata(CrystalCrawlerMain.java:204)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.main(CrystalCrawlerMain.java:80)
Mar 25, 2009 4:28:04 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Oracle:com.acta.db.ActaOracleConnectionFactory. null
[Signaling in VM: java/lang/reflect/InvocationTargetException, message: ]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.acta.db.ActaDbManager.addDBConnectionFactory(ActaDbManager.java:205)
        at com.acta.db.ActaDbManager.init(ActaDbManager.java:79)
        at com.acta.db.ActaDbManager.<init>(ActaDbManager.java:101)
        at com.acta.db.ActaDbManager.getDBManager(ActaDbManager.java:112)
        at com.acta.db.ActaDbManager.getConnection(ActaDbManager.java:145)
        at com.acta.crystalrepo.crawler.DIRepoHandler.initialize(DIRepoHandler.java:78)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.createRepoConnection(CrawlerProgramBase.java:211)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.run(CrawlerProgramBase.java:102)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.getReportMetadata(CrystalCrawlerMain.java:204)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.main(CrystalCrawlerMain.java:80)
Mar 25, 2009 4:28:04 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Microsoft_SQL_Server:com.acta.db.ActaMSSqlServerConnectionFactory. null
[Signaling in VM: java/lang/reflect/InvocationTargetException, message: ]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.acta.db.ActaDbManager.addDBConnectionFactory(ActaDbManager.java:205)
        at com.acta.db.ActaDbManager.init(ActaDbManager.java:80)
        at com.acta.db.ActaDbManager.<init>(ActaDbManager.java:101)
        at com.acta.db.ActaDbManager.getDBManager(ActaDbManager.java:112)
        at com.acta.db.ActaDbManager.getConnection(ActaDbManager.java:145)
        at com.acta.crystalrepo.crawler.DIRepoHandler.initialize(DIRepoHandler.java:78)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.createRepoConnection(CrawlerProgramBase.java:211)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.run(CrawlerProgramBase.java:102)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.getReportMetadata(CrystalCrawlerMain.java:204)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.main(CrystalCrawlerMain.java:80)
Mar 25, 2009 4:28:04 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Informix:com.acta.db.ActaInformixConnectionFactory. null
[Signaling in VM: java/lang/reflect/InvocationTargetException, message: ]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.acta.db.ActaDbManager.addDBConnectionFactory(ActaDbManager.java:205)
        at com.acta.db.ActaDbManager.init(ActaDbManager.java:81)
        at com.acta.db.ActaDbManager.<init>(ActaDbManager.java:101)
        at com.acta.db.ActaDbManager.getDBManager(ActaDbManager.java:112)
        at com.acta.db.ActaDbManager.getConnection(ActaDbManager.java:145)
        at com.acta.crystalrepo.crawler.DIRepoHandler.initialize(DIRepoHandler.java:78)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.createRepoConnection(CrawlerProgramBase.java:211)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.run(CrawlerProgramBase.java:102)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.getReportMetadata(CrystalCrawlerMain.java:204)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.main(CrystalCrawlerMain.java:80)
Mar 25, 2009 4:28:04 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for Sybase:com.acta.db.ActaSybaseConnectionFactory. null
[Signaling in VM: java/lang/reflect/InvocationTargetException, message: ]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.acta.db.ActaDbManager.addDBConnectionFactory(ActaDbManager.java:205)
        at com.acta.db.ActaDbManager.init(ActaDbManager.java:83)
        at com.acta.db.ActaDbManager.<init>(ActaDbManager.java:101)
        at com.acta.db.ActaDbManager.getDBManager(ActaDbManager.java:112)
        at com.acta.db.ActaDbManager.getConnection(ActaDbManager.java:145)
        at com.acta.crystalrepo.crawler.DIRepoHandler.initialize(DIRepoHandler.java:78)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.createRepoConnection(CrawlerProgramBase.java:211)
        at com.acta.crystalrepo.crawler.CrawlerProgramBase.run(CrawlerProgramBase.java:102)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.getReportMetadata(CrystalCrawlerMain.java:204)
        at com.acta.crystalrepo.crawler.CrystalCrawlerMain.main(CrystalCrawlerMain.java:80)
Mar 25, 2009 4:28:04 PM com.acta.db.ActaDbManager addDBConnectionFactory
SEVERE: BODI-3013019: Unable to create connection factory for MySQL:com.acta.db.ActaMySqlConnectionFactory. null
Mar 25, 2009 4:28:04 PM com.acta.db.ActaDbManager init
INFO: BODI-3013011: Delaying the loading of DB2 JDBC driver classes.
Unable to create connection to Data Integrator repository. Exception: BODI-3013014: Database driver for 'Oracle' is not loaded. 
[CrystalCrawlerMain]getReportMetadata failed: An unexpected error has occurred
CMS Integrator failed: getReportMetadata failed: An unexpected error has occurred

philmorris :uk: (BOB member since 2002-11-12)

you can’t run CMSCollector on Unix env, the Metadata Integrator works only from windows env, the cmsCollector application is dependent on BO Designer (Universe Designer) and DesKI to collect Universes and DesKI reports

the database driver classpath error will happen in following scenarios
1 - Standalone installation of Metadata Integrator (the installer is not copying all the jar files, this issue is fixed in 11.7.3.8 )

2 - The DI web Server (Management Console) is not installed on the same machine as Metadata Integrator, the following path will not be available in that case (this is also fixed in 11.7.3.8 )
%link_dir%\ext\diAdmin\WEB-INF\lib\

This sholud point to %link_dir%\ext\lib\ which will be available to Metadata Integrator
cp.4.directory=%link_dir%\ext\lib\

modify this in %LINK_DIR%\ext\cmsCollector\classloader.properties file as below
Web External jars
#cp.4.directory=%link_dir%\ext\diAdmin\WEB-INF\lib\
cp.4.directory=%link_dir%\ext\lib\

if your BOE is on AIX, then I think there a way to make cmsCollector to work, by adding a JobServer in CMS which is running on windows, I have to check the steps for that


manoj_d (BOB member since 2009-01-02)