Error with LDAP/ IBM Maximo Work Manager

[Former Member]

Hi Experts,

Configured SAP Work Manager for IBM Maximo 7.5 to now use LDAP authentication via websphere.   However, when attempting to connect from agentry 6 client- we get following error:-

System#notboundexception

java.lang.nullpointerexception

at com.ibm.ws.naming.util.commonhelpers$.run

at com.ibm.ws.naming.util.commonhelpers$.run

at com.ibm.ws.security.util.accesscontroller.doprivileged

com.ibm.ws.naming.util.commandcontroller.merge.jndiproviderspropeties

I am getting no java.util.logging.config option specified in no standard java option in Backend java log file.

We have configured link below:-

Configure settings to connect Agentry Server to Maximo WebSphere 6.1 LDAP Server - SAP Mobility - SC...

version info:

java version "1.6.0_45"

IBM Maximo version 7.5

Websphere Version 7.0

Regards:

Sumit

[bill_froelich]

Sumit,

System#notboundexception indicates there

a) a configuration problem in your settings for the connection

b) the instance is not up and running

c) there is a network issue preventing the connection from being established

I would start by verifying your configuration steps for the LDAP configuration.

--Bill

[Former Member]

After installation of the Application Client, copied the orb.properties is present in the lib directory of the JRE.

Copied the necessary jar files from the Maximo server to the Work Manager Server.

Made the following changes in javaBE.ini:

Uncomment the line beginning with appServerType and set its value to websphere.

Uncomment the line beginning with security.auth.login.config and verify that this line reads security.auth.login.config=./jaas_client.conf.

Uncomment and set the value for the naming.provider.url of the form iiop://<xxxx>:<xxxx>.

Uncomment and configure the property naming.factory.initial as described in the JavaBE.ini Properties

configured the property maximo.jndi.rootContext as described in the JavaBE.ini.

Uncomment the line beginning with maximo.jndi.ejb.accesstoken and verified that it readsmaximo.jndi.ejb.accesstoken=ejb/maximo/remote/accesstokenprovider.

Uncomment and configure the property com.ibm.CORBA.ConfigURL as described in the JavaBE.ini

   Modified the agentry.ini file in the Work Manager product directory by setting the classPath property in the [stage:Java] section as follows:               classPath=<JarFiles>\businessobjects.jar;<JarFiles>\mboejb.jar;<JarFiles>\mbojava.jar;.\Java;

  Add the nonStandardJavaOptions property to the [stage:Java] section and configure as follows:

nonStandardJavaOptions=-Djava.endorsed.dirs=<AppClientDir>\java\jre\lib\endorsed -Djava.ext.dirs=<xxxx>\JRE\lib\ext;<AppClient>\lib;<AppClient>\plugins;<AppClient>\lib\WMQ\java\lib

we made some change under sas.client.prop as per document.

Regards:

Sumit

[Former Member]

The jar files need to come from the websphere deployment server and not the Maximo Server.  This is because the needed class files for LDAP are only added to the jar files at the deployment folder.

[Former Member]

Stephen,

I have copied

Startup.jar

bootstrap.jar

urlpotocols.jar

Lmproxy.jar from path webser->appserver->lib folder and copied into Smart work manager server development folder under java folder.

Still i am getting erros:-

Java.naming.noinitialcontextexception:- cannot instantiate class: com.ibm.websphere.naming.wsninitialcontextfactory [root exception java.lang.classnotfoundexception: com.ibm.websphere.naming.wsninitialcontextfactory

Please have a look on above error:-

Regards:

Sumit