Skip to main content
Mitratech Success Center
Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

WebSphere Liberty 25.0.0.4 Installation

  1. Last updated
  2. Save as PDF

    Important Note: Upgrade from Version 7.x to 8.0

    • It is no longer necessary to explicitly add saaj-impl-1.5.1.jar through Jenkins for WebSphere Application Server (WAS) deployments in TeamConnect Enterprise version 8.0.

    • The newer version included in the WAR file is sufficient and fully compatible with TeamConnect Enterprise version 8.0.

    To resolve the issue, we removed the logic from the Jenkins job that added saaj-impl-1.5.1.jar, and then redeployed the WAR file to WebSphere.

    Follow the below instruction for the Installation of WebShpere Liberty 25.0.0.4:

    1. Pull the WebSphere Liberty 25.0.0.4 from https://hub.docker.com/.
    2. The WebSphere liberty consist of relevant JDK version.
    3. Add <application context-root=" CONTEXT_ROOT" type="ear" id="CONTEXT_ROOT" location="CONTEXT_ROOT.ear" name="CONTEXT_ROOT"/>' to your server.xml
    4. Copy the server.xml to /opt/ibm/wlp/usr/servers/defaultServer/
    5. Place ojdbc8.jar file in the TeamConnect War file by using Total Commander and then place the TeamConnect application WAR file in the \usr\servers\TeamConnect\dropins folder.
    6. Copy the .ear file to /opt/ibm/wlp/usr/servers/defaultServer/apps/
    7. The user can also place ojdbc8.jar/sqljdbc4.jar /opt/ibm/wlp/usr/servers/defaultServer/apps/expanded/CONTEXT_ROOT.ear/CONTEXT_ROOT.war/WEB-INF/lib
    8. Start the TeamConnect.
    9. Check the console logs and if it states the TeamConnect is started then open the browser http://localhost:9080/context_root/standardLogin (where 9080 is an APP_PORT you can use one you preferred).
    10. If there are any errors, please check the logs that are captured in the WLP TeamConnect logs.