I have fixed the link my update as well. Thanks.
- Ram.
Original Message:
Sent: Fri November 15, 2024 12:14 PM
From: Doug Breaux
Subject: Running IDSWebapp in Liberty container
Thank you! Yes, that's what I wanted but could not find.
Noting that your link added the period on the end, which doesn't work. This does:
https://www.ibm.com/docs/en/svd/10.0.3?topic=images-verify-directory-web-administration-tool
------------------------------
Doug Breaux
Software Engineer
Kyndryl
Original Message:
Sent: Fri November 15, 2024 09:25 AM
From: Ramamohan Reddy
Subject: Running IDSWebapp in Liberty container
Hi Doug,
It looks like you are trying to containerize the ISVD 10.0.3 Web Admin Tool. Just to let you know that a Web Admin Tool Container available. Please refer: https://www.ibm.com/docs/en/svd/10.0.3?topic=images-verify-directory-web-administration-tool.
I'd also suggest you to open a case with IBM so that the support/dev teams can review your observations and questions and respond to you.
-Ram.
------------------------------
Ramamohan Reddy
Original Message:
Sent: Thu November 14, 2024 01:15 PM
From: Doug Breaux
Subject: Running IDSWebapp in Liberty container
First, is all of this really necessary to run this app under Liberty?
Manual deployment of Web Administration Tool in WebSphere Liberty Profile
Next, I'm working on a Dockerfile
to replicate these steps, and while I have it at least kind-of working (I haven't run in a location that can actually reach any of our directory servers yet), there are some errors logged and unexpected requirements I'd like to ask about.
(And, of course, it would be great if IBM could provide a Docker image for this and own the setup to make sure it's correct & optimal!)
Attaching my current Dockerfile
.
Some notes and observations and questions:
1. The provided server.xml
only uses 3 features, but the installation of the custom portlet one requires 2 others, which themselves install newer features than the ones server.xml
uses.
CWWKF1011E: The feature com.ibm.websphere.appserver.portlet-2.1 depends on com.ibm.websphere.appserver.jsp-2.3 which is not installed.
CWWKF1011E: The feature com.ibm.websphere.appserver.portlet-2.1 depends on com.ibm.websphere.appserver.webCache-1.0 which is not installed.
2. Upon starting a container, the following error is logged, but the application seems to be working otherwise. Is JAXB actually needed?
[ERROR ] CWWKE0702E: Could not resolve module: com.ibm.ws.portletcontainer [107]
Unresolved requirement: Import-Package: javax.xml.bind
3. Upon hitting the application in a browser, the following is logged
[err] Can't load log handler "com.ibm.ldap.utils.TDSFileHandler"
[err] java.lang.ClassNotFoundException: com.ibm.ldap.utils.TDSFileHandler
Despite using the provided jvm.options
that does point to the IDSLogging.jar
file that I confirm is in the expected location in the running container.
4. I haven't yet tried to containerize the SSL setup instructions. Would welcome some guidance on that.
5. I could also use some guidance on how to externalize the application's settings so we don't lose like the admin login and configured LDAP servers when new containers spin up.
------------------------------
Doug Breaux
Kyndryl
------------------------------