SAP IDM 7.2 SP7 - ABAP Initial Load Error "Creation of JCo2Proxy failed"

[Former Member]

Hi ,

System is getting upgraded from IDM 7.1 to IDM 7.2 SP7 . As part of the upgrade we are trying to execute ABAP Initial load for a Non Production System to review Attributes which are new as part of IDM 7.2 ( Ex : MX_IS_ACCOUNT etc ) . When we execute the ABAP load for a System repository , we are getting below mentioned error messages.

Pass: ReadABAPRoles

ERROR :    

     Creation of JCo2Proxy failed. Reason:

     java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO

     Initializing FromSAPIdentity pass

     java.lang.Exception: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO

     Init failed

Our Java Connection for IDM 7.2 is set us below :

     Path to JAVE.EXE   :C:\Program Files (x86)\Java\jdk1.6.0_38\bin\java.exe

     Path to JVM.DDL     :C:\Program Files (x86)\Java\jdk1.6.0_38\jre\bin\client\jvm.dll

Class Path Extension

: C:\usr\SAP\IdM\IdentityCenter\Java\sapjco3.jar;C:\oracle\ora102\jdbc\lib\classes12.jar;C:\oracle\ora102\jdbc\lib\ojdbc14_g.jar;C:\oracle\ora102\jdbc\lib\ojdbc14.jar

[ChrisPS · Accepted solution]

Hi Jerry - looks like the runtime can't invoke the jco. First review note 1658578 ->

http://www.service.sap.com/sap/support/notes/1658578.

Thanks,

Chris

[Former Member]

Hi Jerry,

i would recommend you (and any others having this JCo problem while using a 32bit Java Runtime) to use the SAP JCo 32Bit version instead of downgrading to an older version which isn't supported anymore.

The Runtime Components of the Identity Management only deliver the 64Bit version of SAP JCo, which also needs a 64Bit version of your Java Runtime and that's the issue you focused on.

Try to download release 3.0 of SAP Java Connector (SAP JCo) from Marketplace and replace sapco3.jar, sapco3.dll and sapco3.pdb in your \usr\sap\IdM\Identity Center\Java folder with the ones from marketplaces.

This worked very well for me.

Best wishes,

Bastian

[keith_zhang]

Hello Jerry,

I think the issue should be related to JCo 3 as Murali mentioned. When JCo3Proxy failed to be created, it will fall back to JCo2Proxy, then in this case, JCo2Proxy creation also failed. Please you can increase the dispatcher log level to Debug, and then the dse log can show more info/reason.

BR, Keith

[Former Member]

Thanks !!,

We are now downgrading JC03 to JC02 as per SAP OSS Note mentioned by Chris above .

[Murali_Shanmu]

Hi Jerry,

Did you have a look at the Release Notes for SP7. There is a section on JCo and the changes which are required,

Cheers,

Murali