Is ADMA0115W expected when deploying ldx.war on WAS in CLM 6.0?
Configuration:
WAS said:
[...]
ADMA0115W: Resource assignment of name jdbc/LQEDB and type javax.sql.DataSource, with JNDI name jdbc/LQEDB is not found within scope of module ldx with URI ldx.war [...]
[...]
Can this warning be ignored?
Thanks,
Larry.
- Windows 2012-R2 Standard 64-bit
- DB2 10.5.600.232 (FP6)
- WAS Base 8.5.5.0
-
CLM 6.0.0
WAS said:
[...]
ADMA0115W: Resource assignment of name jdbc/LQEDB and type javax.sql.DataSource, with JNDI name jdbc/LQEDB is not found within scope of module ldx with URI ldx.war [...]
[...]
Can this warning be ignored?
Thanks,
Larry.
Accepted answer
I did a quick test and found that the warning could actually be ignored.
I believe the warning was thought to be the cause for LQE not functioning properly when Larry first raised the concern.
I believe the warning was thought to be the cause for LQE not functioning properly when Larry first raised the concern.
One other answer
You cannot ignore the warning. But first of all, where did you specify the name "jdbc/LQEDB"? I cannot find any references in the document referring to this JNDI name.
Also, can you please elaborate why "the jython clm-deploy script that ships with CLM 6.0.0 doesn't support ldx.war"? The script simply picks up all *.war files in the server/webapps folder and installs them in WAS, and I don't see a reason it cannot deploy lqe.war or ldx.war.
Also, can you please elaborate why "the jython clm-deploy script that ships with CLM 6.0.0 doesn't support ldx.war"? The script simply picks up all *.war files in the server/webapps folder and installs them in WAS, and I don't see a reason it cannot deploy lqe.war or ldx.war.
Comments
Hi Donald,
Thanks for taking the time to respond.
That JNDI name came from the WAS ISC, in the ADMA0115W error message generated by the install; I didn't put it in, so it must be some default, or something...
My mistake about the clm-deploy script; I was going by the wiki docs for it, which lists what WARs it deploys, and the list doesn't include gc, jrs, lqe, ldx. So, I'll give it a try!
I'm starting to think the problem (and other problems I'm having with this install) might be related to missing the JRS Shared Library for lqe and ldx, as @ryanpark mentioned in this answer ...
Thanks again,
Larry.