Deploying CLM 4.0 with WAS 8.0
Hi, I have deployed CLM 4.0 into WAS 8.0. I have followed all required steps like defining custom properties, mapping users etc. but when I open the JTS setup URL like https://server:9443/jts/setup.. I get following error: " Internet Explorer cannot display the webpage Any suggestions please? |
4 answers
Ralph Schoon (63.4k●3●36●46)
| answered Jun 21 '12, 10:47 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Have you considers looking into https://jazz.net/library/article/662 . it is for the upgrade to 3.0.1.x, however it contains a troubleshooting guide you might want to check. We tried to sum up all the issues we saw with deploying on WAS and what can be done. it should be valid for WAS 8 as well in general.
Connection problem means that the page can not be reached. I would assume, WAS is not started, the deployment failed at least for JTS. Check if WAS is started in the services. Try to restart WAS. check for the application that are deployed. If you can reach WAS using the admin console, WAS is up and then it indicates the deployment failed. Try removing the App and redeploying. Make sure the context roots are set properly etc. You would see other errors if you ran into the most common issues: - Wrong JazzHome - Global security settings wrong, e.g. missed a step/checkbox - LDAP/Authentication setup incorrect |
Karl Weinert (2.0k●5●27●36)
| answered Jun 21 '12, 9:50 a.m.
JAZZ DEVELOPER edited Jun 21 '12, 11:05 a.m.
That's a pretty generic error.
One thing that comes to mind is if the profile is using 9443 Do you have any other WAS profiles? What port are you using to access the WAS console? What happens if you use localhost instead of servername? Does the application show as running in the WAS console? Edit: Is tomcat currently running? Are any applications deployed into tomcat? You can use both but you need to configure one or the other to use a different set of ports. If tomcat is running try stopping it then stopping and starting WAS. If that works then we can figure out the best way to proceed. Another suggestion: Make sure you restarted the profile and not just the applications when you finished configuring them. Occasionally that will cause unexpected results. As for checking the port, 9043 is the default secure port for the first WebSphere profile so the other ports should also be the default including 9443 Comments Hi Karl, I need to check on which port profile is using.. how do I check this? I do not have any other profiles, I have only one profile. I use 9043 port to access WAS console. I cannot use localhost since apps are in linux box and I am accessing from windows box. Application is perfectly running in WAS.. I checked it many times. Any suggestions? I want to mention one more thing here.. on same machine we have an tomcat instance also. we are planning to have both WAS and Tomcat instance. Is this causing the issue ? Karl, Currently tomcat is not running and CLM is deployed. I have restarted WAS many times and all apps are deployed correctly and running properly.. Hi Karl, There was issue with port and now I corrected it. But when I open JTS setup page I get following error on browser: " Error 500: java.lang.NoClassDefFoundError: sun.awt.X11GraphicsEnvironment (initialization failure) ". I tried to set the DISPLAY variable also.. any suggestions please? |
|
Karl Weinert (2.0k●5●27●36)
| answered Jun 25 '12, 8:11 a.m.
JAZZ DEVELOPER edited Jun 25 '12, 8:18 a.m.
In response to :
When I open JTS setup page I get following error on browser: " Error 500: java.lang.NoClassDefFoundError: sun.awt.X11GraphicsEnvironment (initialization failure) ". I tried to set the DISPLAY variable also.. any suggestions please? That looks like it has to do with the java.awt.headless value in WebSphere. It is supposed to be set to true See step 12 in the Setting up a WebSphere Application Server section of the information center |
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.
Comments
See edit to my original answer
Couple more thoughts. Make sure there is enough memory, I have seen some issues with too many open file handles on Linux. But it is probably time to open a PMR so they can analyze the logs.