Tomcat to WAS migration question
Hi,
I'm trying to migrate from Tomcat 5.5 to WAS (WebSphere Application Server) 7.0.0.11 When we installed RTC we went with the default Tomcat option and it worked fine. We now want WAS as our application server and for that we installed WAS on the same box (SUSE Linux) as JTS. We deployed jts.war and ccm.war onto WAS as mentioned in the help. Now, how do I tell JTS to use WAS and not tomcat? Thanks! |
2 answers
In the "Deploying web applications on WAS" help section it is mentioned that:
10. Map security roles to user or group: Click the jts_war application and open it for editing. In the Detail properties section, click Security role to user/group mapping. Select a specific group, such as JazzAdmins and JazzUsers, and click Look up groups. (On WebSphere Application Server v7.0.0.7 and newer, click Map groups.) These groups are associated with every Jazz implementation and must be mapped to a particular group that contains the authorized users. >> I didn't understand this part. We don't use any LDAP. Can someone please help me to understand this mapping part? I'm stuck here. By the way, we are installing RTC from the scratch and we didn't choose Tomcat as the app server. Thanks! |
You don't need to "tell" the JTS to use WAS: if you have it deployed to
WAS than starting the WAS profile (and the jts app of course) starts the JTS. You need some way to manage your users. The default Tomcat install uses the tomcat-users.xml. Or you could cofigure it to use LDAP. With WAS you have number of options on where your users are maintained/managed See http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tsec_authusers.html * Federated repository * Local operating system * Standalone Lightweight Directory Access Protocol (LDAP) registry * Standalone custom registry On 3/03/2011 1:08 AM, theju wrote: In the "Deploying web applications on WAS" help section it |
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.