CM API development with eclipse and Tomcat

[fla...@gmail.com]

I've historically used IBM WSAD / WAS for development of CM API
Applications. Our IT department is trying to switch to using eclipse
and Tomcat instead.

Can anyone tell me what the jar dependencies, etc. are for working in
an eclipse / tomcat environment?

I seem to have this problem using the Content Manager APIS -

I'm getting a NoClassDefFoundError on a class
com/ibm/mm/sdk/common/DKPropertyPoolJDBC

When attempting to logon

Also if anyone has any tips or insight on using eclipse and/or Tomcat
with Content Manager APIs it would be appreciated

[Workn]

DKPropertyPoolJDBC is found in these jar files: cmbcm81.jar,
cmbjdbc81.jar cmbsdk81.jar, at least one will need to be in the Tomcat
classpath for your application. Also be sure to include your
IBMCMROOT to the classpath, this is needed to find the CM configuration
files locally.

[fla...@gmail.com]

OK,

I got past the NoClassDefFoundError by adding cmbsdk81.jar to my Tomcat
classpath.

Now I'm getting this:

javax.servlet.ServletException:
com.ibm.mm.beans.CMBConnectFailedException: DGL0394A: Error in
::DriverManager.getConnection; No suitable driver (STATE) : ; [SERVER =
ICMNLSDB, USERID = icmconct, SQL RC = 0, SQL STATE = 08001]
org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

Ideas?

[Workn]

SQL STATE = 08001 is CONNECTION FAILED FOR SECURITY REASON reason-code
(reason-string), so it may be as simple as the password for the icmcont
id in the .../cmgmt/connectors/cmbicmenv.ini files is wrong. Or you
are passing the incorrect password on the connect.

However the "No suitable driver" may be a more subtle problem. If the
password is not the problem, turn on tracing on your DB2 connect
instance. In the past I've found that not all versions of DB2 connect
work, we're using 8.1.7 here and have failed with either 8.1.10 or
8.1.11. I've also found in the trace file where some stored procedures
were either stopped or not installed, in either case the error reported
back to your application was incorrect.

[Javier Plumey]

Also,

Make sure that the db2java.zip files is in the your classpath for both your eclipse environment as well as your Apache runtime environment.

Javier Plumey
Technical Lead, SYSCOM, Inc.
954-272-8116 :: www.syscom.com

--
Regards,

Javier Plumey