search cancel

Unsatifiedlink error when connecting to Policy Server during IDM startup on WAS & AIX.


Article ID: 50833


Updated On:


CA Directory CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On CA Security Command Center CA Data Protection (DataMinder) CA User Activity Reporting



Customer installed WAS 6.1 on an AIX 6.1 (64-bit) box and then installed and deployed IDM 12.5SP4 on it. IDM was integrated with SM R12SP2CR1. On starting up IDM, he noticed the following error trace in the WAS System.out log:

0 17:26:55:070 CST] 00000020 SystemOut O FATAL ERROR: Exception from System.loadLibrary java.lang.UnsatisfiedLinkError: smcommonutil (A file or
directory in the path name does not exist.)
[12/7/10 17:26:55:070 CST] 00000020 SystemOut O FATAL ERROR: Exception from AgentAPI.initialize() java.lang.UnsatisfiedLinkError:

He already verified that the 4x agent was created in SM, and that the agent name, shared secret and SM Admin passwords are encrypted correctly and specified in the ra.xml. Also, the LIBPATH in the WAS startup script was pointing to the /IdentityMinder.EAR/library where the 4x agent .so files are located.


IDM only works on 64bit WAS/JDK with 64bit SM libraries that are shipped with webagent SDK. These files have to be copied over to the /IdentityMinder.EAR/library. If you use the default .so files shipped with IDM install, it will still not work even if the WAS/JDK is 64bit.


Component: IDMGR