cancel
Showing results for 
Search instead for 
Did you mean: 

Dispatcher issue

Ckumar
Contributor
0 Kudos

Hello Experts,

I have just installed SAP IDM 7.2 SP0 on Windows 2008 server. After creation of new Identity Center, I have created a Dispatcher and tried to test it after generation of script and got below output in cmd.

Running MxDispatcher_idmdispatcher.

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

AG. All rights reserved.

Java VM: Oracle Corporation   Version: 1.8.0_60

Java home: C:\Program Files\Java\jre1.8.0_60

Java lib/ext: C:\Program Files\Java\jre1.8.0_60\lib\ext;C:\Windows\Sun\Java\lib\

ext

CLASSPATH: D:\usr\sap\IdM720\Identity Center\Java\mxdispatcher.jar;D:\usr\sap\Id

M720\Identity Center\Java\mxmcapi.jar;C:\Program Files\Microsoft JDBC Driver 4.1

for SQL Server\sqljdbc_4.1\enu\sqljdbc41.jar;C:\Program Files\Microsoft JDBC Dr

iver 4.1 for SQL Server\sqljdbc_4.1\enu;C:\Program Files\Microsoft JDBC Driver 4

.1 for SQL Server\sqljdbc_4.1\enu\sqljdbc41.jar

[25.09.2015 12:19:02-210] - MxDispatcher:Waiting for succesfull start-up of the

thread:RELOAD

[25.09.2015 12:19:02-211] - MxDispatcher:Main loop for thread:IDS_DispThread-REL

OAD-idmdispatcher

[25.09.2015 12:19:02-211] - MxDispatcher:Started thread:IDS_DispThread-RELOAD-id

mdispatcher

[25.09.2015 12:19:02-211] - MxDispatcher:THREAD BODY Execution:IDS_DispThread-RE

LOAD-idmdispatcher

[25.09.2015 12:19:02-211] - MxDispatcher:Reading main MxDispatcher configuration

...

[25.09.2015 12:19:02-215] - MxDispatcher:Global constant DISPATCHER_POLICY_TYPE

not found, using default = 0

[25.09.2015 12:19:02-217] - MxDispatcher:Global constant MX_MAX_CONCURRENT_RUNTI

ME_ENGINES not found, using default = 9999

Could you please tell me what is wrong here and how to fix it.

Regards,

C Kumar

Accepted Solutions (1)

Accepted Solutions (1)

jaisuryan
Active Contributor
0 Kudos

Hi Kumar,

Are you sure you want to stick with 7.2 SP0 dispatcher and not move to latest one?

The logs doesn't seem like dispatcher encountered the problem. There are couple of global constants you need create for dispatchers.

Create an empty job and see if you were able to run successfully?

I haven't set up DISPATCHER_POLICY_TYPE explicitly anytime. May be its not needed in latest ones or it is automatically set when you select options in dispatcher 'policy' tab.

But for the other constant, you will get an better idea if you go thru below document.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1069b670-621a-2e10-9598-99d3b7d99...

Kind regards,

Jai

former_member2987
Active Contributor
0 Kudos

I agree with Jai.  Make sure that the errors are real ones and not just errors that are actually warnings.

Also, try rolling back to Java 7.

Matt

Ckumar
Contributor
0 Kudos

Hello Jaisuryan,

Thanks for reply!

I have installed SP0 and have plan to move to SP10 (In fact I have upgraded to SP10 now).

You were right, It is warning only. I have created a test job and it run successfully.

Regards,

C Kumar

Ckumar
Contributor
0 Kudos

Thanks for reply Matt!

I got it now. Its warning only and my newly created job is running successfully.

I have installed SAP IDM 7.2 earlier too but this time I got different logs so I thought it might be error.

Could you please share what could be the probable reason for this difference.

Regards,

C Kumar

former_member2987
Active Contributor
0 Kudos

Hi Kumar,

I'm guessing if you have different log information SOMETHING changed.

Probably environmental (JAVA)

Probably not worth investigating deeper unless the issue happens again.

Please don't forget to close out the thread!

Matt

Ckumar
Contributor
0 Kudos

Ok Matt I will check my environment variables.

Answers (0)