In my development environment, I see that the $WEBSERVER_HOME/ext/conf/server.xml file has connection port = 8085. But the web admin url we are using has 28080. So when i do telnet from my desktop to that server on port 28080, I get connection failed. But when I do 8085 it works. I tried to change web server port to 8085 using svrcfg and tried to open the web admin using port 8085 in the url. It still does not work. Strangely what I noticed is that in our test and prod environments, we have the same setup in server.xml that 8085 as connection port and then in the urls its 28080 but they work fine. What I think the issue was the setup or installation was not done properly. I was able to see the login page yesterday and when i login i got http error. I restarted the application, and after restarting it, now i when i go to web admin page it says page not found error. I think the test and prod environments might also have the same issue but its just that since they were not restarted since long time, the web admin page works fine in those. Its only for development that we have this issue. Could anyone correct me if I am thinking wrong. Also, there are so many xml files, which one is correct one to check what port the web server is working on and which line exactly will tell me what port since I see the port numbers in various lines.
the xml file used by DI Web server will be server-di-1.xml
check the output of ps -aef | grep java
you will see a java process, that will have the command line arguments with the server-di-1.xml in it, thats the tomcat process on which DI Web server is running, if it started successfully
also check the tomcat log file in %LINK_DIR/ext/WebServer/logs folder, do you see any errors related to port in use etc
if you have changed the port from svrcfg, check which xml file is getting modified in $LINK_DIR/ext/WebServer/conf directory, that is the xml used by DI Web Server
Thanks for your response. I am planning to uninstall and re-install DI to address this issue. Would this be a good option. I am reading the documentation (Getting Started Guide) and it has 3 to 4 steps to uninstall DI. Does this remove complete DI installation that was there before and do I need to reboot the server before re-installing DI again. This is a server running Solaris 10 OS.
I have not tried uninstall on Solaris or Unix machine any time, you can re-install on top of the same directory, just stop the al_jobservice
you don’t have do a complete uninstall since your are having issues with web admin only, you can either delete the foder/files extracted from war files from $LINK_DIR/ext/WebServer/webapps before re-install
no you don’t have to stop the Solaris server before or after re-install