Monday, October 6, 2014

SailpointIQ 6.3 with SAP connector

If you are using SailpointIQ deployed in Jboss cluster environment instead of standalone environment so definitely you will also face test connection error with sap jco connector.We wasted couple of days to figure out of this test connection issue because OOB JCO files and ".so" deployed in Application lib folder but Jboss cluster environment is not picking those files and I was getting below error messages from IIQ console

>connectorDebug "SAP" test
java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
        at java.lang.ClassLoader.loadLibrary(Unknown Source)
        at java.lang.Runtime.loadLibrary0(Unknown Source)
        at java.lang.System.loadLibrary(Unknown Source)
        at com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.j
ava:444)
        at com.sap.conn.jco.rt.DefaultJCoRuntime.registerNativeMethods(DefaultJC
oRuntime.java:310)


So finally got solution:->

For this issue:
I explicitly added the following jars in class path and tried testing from CLI (iiq console) and WOW it works...
$ export CLASSPATH=$CLASSPATH:/opt/user_projects/sailpointws/sailpointws-host1/servers/SAILPOINTWS_Server01/tmp/vfs/temp567b30591bbe7c2f/content-b2d86a4624af7518/WEB-INF/lib/libsapjco3.so:/opt/user_projects/sailpointws/sailpointws-host1/servers/SAILPOINTWS_Server01/tmp/vfs/temp567b30591bbe7c2f/content-b2d86a4624af7518/WEB-INF/lib/sapidoc3.jar:/opt/user_projects/sailpointws/sailpointws-host1/servers/SAILPOINTWS_Server01/tmp/vfs/temp567b30591bbe7c2f/content-b2d86a4624af7518/WEB-INF/lib/sapjco3.jar

Tested from IIQ console
> connectorDebug "SAP" test
Test Succeeded
>

Please verify the below parameters from this link:->
http://yourhostname:port/identityiq/debug/about.jsf

sun.java.command: /opt/jboss/jboss-eap-6.1/jboss-modules.jar -mp /opt/jboss/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider  -Djboss.home.dir=/opt/jboss/jboss-eap-6.1 -Djboss.server.base.dir=/opt/user_projects/sailpointiiq


java.library.path:  /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/opt/user_projects/sailpointiiq/application/identityiq.war/WEB-INF/lib

Cheers..


SailpointIQ with Jboss EAP 6.3

Started to work on SailpointIQ.It is very interesting product and similar to Sun IDM (Oracle Waveset).
Last week I was trying to setup environment with cluster Jboss setup but really we spent lot of time to figure out that How to deploy the war file in Jboss EAP 6.1 and It is not easy steps as documents follow.

So coming to tech parts:
As we are using the cluster Environment so we can't use standalone deployment process in Jboss.
We are unable to configure or can say we should touch the "standalone.xml" file in case of cluster environment.finaly we tried below options:


Update the domain.xml file as below instead of standalone.xml
Comment out the xml node: <extension module="org.jboss.as.jaxrs"/>.
Comment out the node: <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/>

Then clear all cache/temp files and bring up the domain and servers. Now try to deploy the file.

https://community.jboss.org/message/579996

Then again we got some OOB hibernate setting error with Jboss EA
Basically the issue was due to the JVM option -XX:-UseSplitVerifier that was used to workaround a Hibernate problem (https://hibernate.atlassian.net/browse/HHH-7544). But since, sailpoint is using its ownIdentityIQ-hibernate  configuarations, the UseSplitVerifier option had to be removed. THis is because when this option is set, the NoClassDefFound exception is *not* caught within the class initializer!
After removing this option, the NoClassDefFound exception was caught, and the application came up fine with no errors.

Finally cheers....