system#notboundexception Error Smart Work Manager for Maximo 7.5

[Former Member]

Hello.

I have run into an error while trying to connect the Agentry Test Environment to Work Manager.  We are upgrading from version 6.2 to 7.5 and I have already installed Work Manager 7.5 agentry server, editor and ATE successfully and was able to import our existing jar files into the editor successfully.  The source code compiled correctly and I was able to export the newly created MMWM and MaximoMobile jar files to the Java folder for ServerDev.  The agentry server then starts without errors, but I cannot connect via the ATE.  I receive the error listed above.

I have attached the error portion of the Server-Agentry.log portion for review.  Any assistance would be greatly appreciated.

Thanks,

Pete

Tags edited by: Michael Appleby

Server-agentry-snipit.txt.zip

[nancy_burke · Accepted solution]

Peter,

Be certain that you are adhering to all the steps in the latest WM 7.5(2) installation guide for configuring/installing WM for websphere LDAP.

Since you are installing a new instance of WM 7.5.x and authenticating via Websphere running LDAP, be sure that you are following all the steps in the guide and that you are bringing over the businessobjects.jar, mbojava.jar, and the mboejbclient.jar from the maximo.ear from the  Websphere directory (not the Maximo directory).  They should have been copied over from the .ear from the Websphere directory, as those files would contain extra items needed for LDAP.  The files from the Maximo directory wouldn’t contain those. There is a jaas_client.conf file too that needs to come over.  Then update the classpath entry in Agentry.ini to reflect the location of those files on the local server.  There are other setups required in various files outlined in the install guide - so you may wish to review.  Restart the Agentry server afterwards.

I assume that your userid/password can authenicate via the frontend as well.

Are you connecting to just one server or are you configuring clustered servers in websphere?

Nancy Burke

AGS Tech Support

[Former Member · Accepted solution]

Thank you all in advance for your assistance.

I think I've gotten past the original error by reinstalling the Websphere client and making some changes to the paths in the agentry.ini.  But when I try to connect the ATE now there's a pop up box saying invalid password.  The username/password is correct and works with Maximo's frontend.  When I try to run the connecttest.bat with changes made to paths to match the agentry.ini setting, I get an error that states:

javax.naming.NamingException:Error during resolve [Root exception is org.omg.COBRA.TRANSIENT:

     >>SERVER (id=144d42ac, host=maximoserver-fully_qualified) TRACE START:

     >>org.omg.COBRA.TRANSIENT: java.net.ConnectException: Connection ref used:host=maximoserver-fully_qualified,port=10500 vmcid: IBM minor code: E02 completed: No

I of course edited the server name in italics.  At this point I'm troubleshooting SSL connectivity between the client and websphere.

I confirmed the com.ibm.COBRA.ConfigURL settings were correct and well as the other javaBE.ini and agentry.ini settings.

We are connecting to a Websphere cluster but will try to connect to a single server to see if it helps.

I've combed through the install guide and I don't think I've missed any steps.  Any further pointers would be greatly appreciated.

Thanks,

Pete

[nancy_burke · Accepted solution]

Hi Peter,

What version of websphere, please?  What version of Agentry server?

It's easier to start with a connection to a single server within the cluster then once that works. change over to clustered.

Can you connect to that server via telnet? From the javabe.ini iiop:// entry

from a cmd prompt:

telnet (servername) space (port#)

Have you also tried a restart of AppServer, followed by Maximo server and then Agentry server?

You may wish to attach the Agentry.ini, Javabe.ini, connecttest.bat (that shows your classpath settings) and the output of connecttest so we can take a look.

Nancy Burke

[Former Member · Accepted solution]

Hi Nancy.

I finally got it fixed.  Turns out the last problem was with the Websphere JVM itself.  We redeployed and restarted and it's working now.  So ultimately the answer to this was changes to two paths in the agentry.ini file (our path string is pretty convoluted), and a corrupt JVM that required a rebuild.

Thanks again for all your help!

Regards,

Pete

[nancy_burke · Accepted solution]

Most Excellent!   Glad it's working now for you!

Clustered too?

Nancy

[Former Member · Accepted solution]

Yes it's using a Websphere Cluster.

Thanks again for your help

Pete

[bill_froelich]

Pete,

The system#notboundexception is typically due to an issue withteh Maximo backend you are connecting to.  This may be a result of the configurtion in your ini files or it may be an issue with the actual backend system.  Double check your setting and if possible restart the Maximo instance and try the connection again.

You may also want to test using the connecttest.bat file to confirm the settings externally to Agentry.  Remember to update the connecttest.bat file to set the correct options.

--Bill