cancel
Showing results for 
Search instead for 
Did you mean: 

Nullpointer error when trying to test dispatcher in Identity Center

Former Member
0 Kudos

Hi all,

I am getting a nullpointer exception when I am trying to test my dispatcher in Identity Center. In tools/options/java I have defined where the java.exe and jvm.ddl are located.

I had tried to use a Java 1.6 before, but I got a 126 error which did not get me as far. It was 64 bit, so I have installed various versions of Java 1.5 32 bit and have tried them all with the same result as below.

I am running Identity Center 7.2 the latest patch (7.20.3.0-ORA-2011-11-16 with schema 1050).

Simple fix?

Thanks.

================================================

Running MxDispatcher_idf_dispatcher.

MxDispatcher version: 7.2.00.0 Built: 22.11.2010 18:36:12 (c) Copyright 2008 SAP

AG. All rights reserved.

Java VM: Sun Microsystems Inc. Version: 1.5.0_07

Java home: C:\Program Files (x86)\Java\jdk1.5.0_07\jre

Java lib/ext: C:\Program Files (x86)\Java\jdk1.5.0_07\jre\lib\ext

CLASSPATH: C:\usr\sap\IdM\Identity Center\Java\mxdispatcher.jar;C:\usr\sap\IdM\I

dentity Center\Java\mxmcapi.jar;C:\SAP\Oracle_OCI_10_2\ojdbc14.jar;

java.lang.NullPointerException

at com.sap.idm.ic.services.api.MXMCApi_Connection.getConnection(MXMCApi_

Connection.java:70)

at com.sap.idm.ic.services.api.MXMCApi_Connection.<init>(MXMCApi_Connect

ion.java:49)

at com.sap.idm.ic.services.api.MXMCApi_Connection.getInstance(MXMCApi_Co

nnection.java:22)

at com.sap.idm.ic.services.api.disp.MXMCApi_CTX_Dispatcher.getInstance(M

XMCApi_CTX_Dispatcher.java:39)

at com.sap.idm.ic.services.dispatcher.MxDispatcher.main(MxDispatcher.jav

a:170)

C:\Windows\system32>

Edited by: Chad Chromwell on Dec 7, 2011 6:25 PM

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

I was able to get past the issue with testing the dispatcher. I added the mxdispatcher.jar and mxmcapi.jar to the classpath.

So the test of the dispatcher looks fine. But when I try to actually run a job in the Identity Center, nothing seems to happen. I ran these jobs in 7.1 without a problem, but not now. When I click run now on the job, an entry never appears in the System log or Job log for the Job. Used to before.

In the MMC, AS Java process is running and I can get to the NWA via the web broswer on port 50000.

Not sure what is wrong.

-


Running MxDispatcher_idf_dispatcher.

MxDispatcher version: 7.2.00.0 Built: 22.11.2010 18:36:12 (c) Copyright 2008 SAP

AG. All rights reserved.

Java VM: Sun Microsystems Inc. Version: 1.5.0_12

Java home: C:\Java\jre1.5.0_12

Java lib/ext: C:\Java\jre1.5.0_12\lib\ext

CLASSPATH: C:\SAP\IdM\IC72\Java\mxdispatcher.jar;C:\SAP\IdM\IC72\Java\mxmcapi.ja

r;C:\SAP\Oracle_OCI_10_2\ojdbc5.jar;

[11.12.2011 18:53:21-883] - MxDispatcher:Waiting for succesfull start-up of the

thread:RELOAD

[11.12.2011 18:53:21-883] - MxDispatcher:Main loop for thread:IDS_DispThread-REL

OAD-idf_dispatcher

[11.12.2011 18:53:21-884] - MxDispatcher:Started thread:IDS_DispThread-RELOAD-id

f_dispatcher

[11.12.2011 18:53:21-884] - MxDispatcher:THREAD BODY Execution:IDS_DispThread-RE

LOAD-idf_dispatcher

[11.12.2011 18:53:21-884] - MxDispatcher:Reading main MxDispatcher configuration

...

[11.12.2011 18:53:21-888] - MxDispatcher:Global constant DISPATCHER_POLICY_TYPE

not found, using default = 0

[11.12.2011 18:53:21-888] - MxDispatcher:Global constant MX_MAX_CONCURRENT_RUNTI

ME_ENGINES not found, using default = 9999

[11.12.2011 18:53:21-979] - run_java: "C:\Java\jre1.5.0_12\bin\java.exe" -cp "C

:\SAP\IdM\IC72\Java\DSE.jar;C:\SAP\IdM\IC72\Java;C:\SAP\IdM\IC72\Java\sapjco.jar

;C:\SAP\Oracle_OCI_10_2\ojdbc5.jar;C:\SAP\IdM\IC72\Java\mxdispatcher.jar;C;SAP\I

dM\IC72\Java\mxmcapi.jar;C:\SAP\IdM\IC72\Java\mxdispatcher.jar;C:\SAP\IdM\IC72\J

ava\mxmcapi.jar;C:\SAP\Oracle_OCI_10_2\ojdbc5.jar; " "-DDSE_HOME=C:\SAP\IdM\IC72

" com.sap.idm.ic.DSERunTime "Drivers=com.microsoft.jdbc.sqlserver.SQLServerDrive

r;com.microsoft.sqlserver.jdbc.SQLServerDriver;com.sap.dbtech.jdbc.DriverSapDB;o

rg.gjt.mm.mysql.Driver;sun.jdbc.odbc.JdbcOdbcDriver;oracle.jdbc.driver.OracleDri

ver;COM.ibm.db2.jdbc.app.DB2Driver;COM.ibm.db2.jcc.DB2Driver;COM.ibm.db2.jdbc.ne

t.DB2Driver;com.sap.db.jdbc.Driver;oracle.jdbc.driver.OracleDriver" "DatabaseURL

=jdbc:oracle:thin:mxmc_rt/****@localhost:1521:ORCL" Machine=idf_dispatcher Log

Level=4 StackTrace=2 loop

[11.12.2011 18:53:27-191] - run_java: "C:\Java\jre1.5.0_12\bin\java.exe" -cp "C

:\SAP\IdM\IC72\Java\DSE.jar;C:\SAP\IdM\IC72\Java;C:\SAP\IdM\IC72\Java\sapjco.jar

;C:\SAP\Oracle_OCI_10_2\ojdbc5.jar;C:\SAP\IdM\IC72\Java\mxdispatcher.jar;C;SAP\I

dM\IC72\Java\mxmcapi.jar;C:\SAP\IdM\IC72\Java\mxdispatcher.jar;C:\SAP\IdM\IC72\J

ava\mxmcapi.jar;C:\SAP\Oracle_OCI_10_2\ojdbc5.jar; " "-DDSE_HOME=C:\SAP\IdM\IC72

" com.sap.idm.ic.DSERunTime "Drivers=com.microsoft.jdbc.sqlserver.SQLServerDrive

r;com.microsoft.sqlserver.jdbc.SQLServerDriver;com.sap.dbtech.jdbc.DriverSapDB;o

rg.gjt.mm.mysql.Driver;sun.jdbc.odbc.JdbcOdbcDriver;oracle.jdbc.driver.OracleDri

ver;COM.ibm.db2.jdbc.app.DB2Driver;COM.ibm.db2.jcc.DB2Driver;COM.ibm.db2.jdbc.ne

t.DB2Driver;com.sap.db.jdbc.Driver;oracle.jdbc.driver.OracleDriver" "DatabaseURL

=jdbc:oracle:thin:mxmc_rt/****@localhost:1521:ORCL" Machine=idf_dispatcher Log

Level=4 StackTrace=2 loop

Former Member
0 Kudos

Yes I have everytime. And I then exit IC and then restart it.

Edited by: Chad Chromwell on Dec 9, 2011 4:45 PM

Former Member
0 Kudos

While looking around SDN for a solution, I saw that someone had mxdispatcher.jar and mxmcapi.jar in their classpath. I change the CLASSPATH in tools/options/java.

It is now:

C:\usr\sap\IdM\Identity Center\Java\mxdispatcher.jar;C:\usr\sap\IdM\Identity Center\Java\MXMCAPI.jar;C:\SAP\Oracle_OCI_10_2\ojdbc5.jar

Unfortunately that too didn't work.

former_member2987
Active Contributor
0 Kudos

Chad,

As you have been updating the JAVA components, have you been recreating the dispatcher scripts?

Matt

mvoros
Active Contributor
0 Kudos

Hi,

as far as I know you should use ojdbc6.jar for JVM 5 and 6. ojdbc4.jar is for JVM 4.

Cheers

Former Member
0 Kudos

I think that ojdbc5.jar is for Java 1.5 and ojdbc6.jar is for Java 1.6.

I tried using ojdbc5.jar and the same thing happened.