It's all about the answers!

Ask a question

How to Upgrade from Tomcat to WebSphere and Tomcat to LDAP?


Rob Olsen (3511852) | asked May 26 '16, 6:56 p.m.

I have searched the Forum for other related articles on this and found some, but not sure they cover the full issue that I think we are faced with.  One of the on-line articles I read was https://rsjazz.wordpress.com/2012/10/12/changing-the-jazz-user-id-using-the-rtc-plain-java-client-libraries/ and that referenced another http://www-01.ibm.com/support/docview.wss?uid=swg21470141.  Between the two, I think they covered stuff, but not sure if they cover our full issue.  So I am going to put this out on this Forum and see if we get any further information that kind of puts it all together.

Our situation is this; we have a single Jazz Configuration server running both JTS and RTC.  This system uses Tomcat for the Web Server and Tomcat for the User authentication.  Our goal is to (1) move to WebSphere and (2)incorporate LDAP.  We assume the first step would be to upgrade the system to WebSphere first and then deal with the Tomcat Users to LDAP Users issue.  Would this be correct?  So after we upgrade to WebSphere, what would be the correct steps to convert the existing Tomcat users and Tomcat user artifacts from their current value and map them to their respective LDAP accounts?  How could I safely change a user from "JoeUser" (Tomcat) to JP1234 (LDAP) and map all of the existing "JoeUser" artifacts to the new "JP1234" User name?  So after this is all said and done, I log in as LP1234 and still have access to all of my Tasks and all that I originally created under the JoeUser name?

Thanks for your help!

2 answers



permanent link
Donald Nong (14.5k414) | answered May 26 '16, 8:20 p.m.
I would not say it is an "upgrade" from Tomcat to WebSphere. It's a "switch", and you will get more hits when Googling with this keyword. In fact, it is similar to a discussion that we are currently have.
https://jazz.net/forum/questions/221609/any-step-by-step-guide-to-switching-clm-502-from-tomcat-to-was

There are a few steps you need to take if you want to do it on one go.
1. Deploy JTS and RTC to WAS.
2. Configure LDAP on WAS. You may want to use a temporary user for verifying the configuration before proceed further. For example, create an LDAP user "test_ldap", and import or create an RTC user with the same ID, then use this user account to verify the functionality.
3. Verify the LDAP user accounts. You should be able to authenticate, but can't access the actual contents in RTC as it should complain about unrecognized users, such as "LP1234".
4. Change the RTC user IDs to match the LDAP accounts following the steps in the technote that you found.
http://www-01.ibm.com/support/docview.wss?uid=swg21470141
(Note that if you want to go back to Tomcat, you need to change the user ID back, or configure Tomcat to use LDAP instead).
5. Final verification.

Comments
Rob Olsen commented May 26 '16, 9:56 p.m.

Thanks Don, I don't think I can change the title so I will have to go with as is. 

We will give your steps a try and provide feedback.  Thanks for responding so quickly!


permanent link
Alex Hendry (11) | answered May 27 '16, 3:14 a.m.
 Thanks for giving information.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.