MxDispatcher:Error reading main MxDispatcher configuration

[Former Member]

Hello,

Our System is Linux Redhat, Oracle 10.2.0.4 and NW 7.0 SP14. It should be a demo system of IDM so I installed the latest available software for version 7.1 of designtime, runtime and userinterface on the machine. I created the database on the same database as the sap system - no problem. Connect to the db over jdbc worked fine too. I changed the start scripts of the dispatcher (*.sh and *.prop) so that the drivers and directories could be found. Now i want to start the dispatcher and geht the following error:

[18.11.2010 12:27:52-894] - Initialized log for com.sap.idm.ic.services.api.MXMCApi. Log level is Debug

MxDispatcher version: 7.10.05.0 Built: 08.05.2010 23:06:58 (c) Copyright 2008 SAP AG. All rights reserved.

Java VM: IBM Corporation Version: 1.4.2

Java home: /usr/lib/jvm/java-1.4.2-ibm-1.4.2.13.6.x86_64/jre

Java lib/ext: /usr/lib/jvm/java-1.4.2-ibm-1.4.2.13.6.x86_64/jre/lib/ext

CLASSPATH: /usr/sap/idm/identitycenter/Java:/usr/sap/idm/identitycenter/Java/mxdispatcher.jar:/usr/sap/idm/identitycenter/Java/mxmcapi.jar:/usr/sap/idm/identitycenter/Java/ojdbc14.jar

[18.11.2010 12:27:52-948] - MxDispatcher:Reading prop files

[18.11.2010 12:27:52-949] - MxDispatcher:Loading driver: oracle.jdbc.driver.OracleDriver

[18.11.2010 12:27:52-962] - MxDispatcher:Creating connection to : jdbc:oracle:thin:MXMC_RT/************@10.33.1.80:1527:S3R

[18.11.2010 12:27:53-410] - MxDispatcher:Reading main MxDispatcher configuration ...

[18.11.2010 12:27:53-417] - MxDispatcher:Error reading DISPATCHER_POLICY_TYPE - using default (no policy)

[18.11.2010 12:27:53-447] - MxDispatcher:Dispatcher configuration wlsap7 not found

[18.11.2010 12:27:53-448] - MxDispatcher:Error reading main MxDispatcher configuration ...

[18.11.2010 12:27:53-450] - The first config load failed:Dispatcher configuration wlsap7 not found

What is the problem? Can anyone help me?

Info: I don't have installed windows components!

Thanks for help...

Thorsten

[former_member2987]

Don't know if you ever found an answer to this, but I had this recently and it was due to connection string problems.

Make suret that the correct database, user and password are specified correctly. Once we fixed that, the issue was resolved.

Good luck!