The contents below will provide you with insight and tips to get to run the workpoint utilties Designer.sh and Archive.sh on a Linux machine where Identity Manager is installed into Web Sphere.
To run Designer and Archiver we first needed to edit the workpoint-client.properties file. In that file we made sure to uncomment the two parameters for web sphere:
java.naming.factory.initial
java.naming.provider.
When uncommenting the second one, we made sure to use the BOOTSTRAP_ADDRESS port of our cluster member. You can find it by logging into WAS admin
console -> editing your cluster member and looking at ports.
Also, we edited the init.sh (under tools\workpoint\bin) and uncommented the section for web sphere towards the bottom. We ensured JAVA_HOME and
WAS_HOME were properly set and uncommented all else which is in that section.
After all of that we didn't get Designer and Archive to run. When executing them we received the following errors:
Setting EJB client classpath
Setting WorkPoint classpath
Starting WorkPoint Designer
2014-01-24 13:34:47,031 [main] INFO com.workpoint.gui.designer.Designer -
PRODUCT = WorkPoint; VERSION = 3.4.2; BUILD = 20080602.P033; BUILD DATE =
November 28, 2012
2014-01-24 13:34:47,853 [main] INFO com.workpoint.client.ClientContext -
Loaded client properties from
file:/opt/CA/IDMVanGuard/IAM_Suite/IdentityManager/tools/Workpoint/conf/work
point-client.properties
Jan 24, 2014 1:34:49 PM null null
SEVERE: security.JSAS1480I
Jan 24, 2014 1:34:50 PM null null
WARNING: WSVR0072W
Jan 24, 2014 1:34:50 PM null null
INFO: Client code attempting to load security configuration
Jan 24, 2014 1:35:20 PM null null
AUDIT: WLMKEY_SERVER_MARKED_UNUSABLE
Jan 24, 2014 1:35:20 PM null null
WARNING: WLMKEY_SERVER_MARKED_UNUSABLE
Jan 24, 2014 1:35:50 PM null null
AUDIT: WLMKEY_SERVER_MARKED_UNUSABLE
Jan 24, 2014 1:35:50 PM null null
WARNING: WLMKEY_SERVER_MARKED_UNUSABLE
2014-01-24 13:35:50,782 [P=489692:O=0:CT] ERROR
com.workpoint.gui.common.ErrorDialog - Cannot retrieve authentication
information. NamingException caught attempting to locate the
'ServerConfigPvt_EJB' object. Please verify that the server is running and
the client configuration is correct.; nested exception is:
javax.naming.NamingException: Error during resolve [Root exception is
org.omg.CORBA.NO_IMPLEMENT:
>> SERVER (id=11c328fe, host=andromeda) TRACE START:
>> org.omg.CORBA.NO_IMPLEMENT: No Cluster Data Available vmcid:
>>0x49421000 minor code: 42 completed: No
>> at
>>com.ibm.ws.cluster.router.selection.WLMLSDRouter.select(WLMLSDRouter.j
>>ava:295)
>> at
>>com.ibm.ws.cluster.propagation.ServerClusterContextListenerImpl.forwar
>>dRequest(ServerClusterContextListenerImpl.java:635)
>> at
and ....
javax.naming.NamingException: Error during resolve [Root exception is
org.omg.CORBA.NO_IMPLEMENT:
>> SERVER (id=11c328fe, host=andromeda) TRACE START:
>> org.omg.CORBA.NO_IMPLEMENT: No Cluster Data Available vmcid:
>>0x49421000 minor code: 42 completed: No
>> at
>>com.ibm.ws.cluster.router.selection.WLMLSDRouter.select(WLMLSDRouter.j
>>ava:295)
>> at
Here is IBM's page that has information on the issue:
This page suggests that your deployment manager, as well as your member servers as well as your nodeagents all need to be part of the same core group. To fix this we used the WAS admin console -> located the core group -> clicked Preferred Coordinator Servers -> added these elements to the list. We ordered the list so that the member server is first, the node agent is second and deployment manager last.
We then had to restart the deployment manager and the node agent and the IDM cluster.
Once all that restarted then Designer and Archiver now both work
Yours,
Sagi Gabay,
CA Technologies.