multi-instance install of the scheduler

Just a quick question.

I know I can run multiple instances of the scheduler on one box as long as I change the port number.
My question is, when logging into the web console how do I login to each instance ?

specify the port number after the server?

Thanks

That is not going to work. The console uses the same port number that is either hard-coded or stored in some config file. You may need to deploy the console's .WAR file twice to the same web server using different names for the .WAR file (for example scheduler_1.war and scheduler_2.war) which will create 2 different instances of the console on the web server, and make them connect on different port numbers. This way, to manage instance 1 you will go to http://webserver:8080/scheduler_1, to manage second instance you will go to I will go to http://webserver:8080/scheduler_2. I will find out for you where to change the port number. I think we also had some build or sample somewhere having port number exposed as an editable field on the logon page.

If you do have the build that exposes the port number, I would love to get a copy of that.
Let me know.

Thanks

I have found it. Basically you just need to replace one file. I am going to email it to you shortly.

OK thanks,

Please send to seanwconway@nospam.yahoo.com

remove nospam.

Just an update.

I was able to deploy the war file 3 times to the tomcat server.
I then edited the login_proceed.jsp page, just changing the port number for the instance I want to connect to.

Hi there,

I got the file, I will probably try running it this way so I don't have to run 3 instances of the web app.
It's been running just fine though, but I think to save on resources, I will run just one instances.

Thanks for the great support!

OK I tried the new login.jsp page, but no matter what port I specify, it logs me into the same instance.
I think the login_proceed.jsp page needs to change because this is where the default port numbers are specified.

Can you verify this and if that's the case send me this file?

Thanks again.

That file was taken from build #258. In that build, the port number is passed as a parameter from the initial logon screen (login.jsp) and in case that parameter is not available, a default number is used in the other file.

You may need to delete files in the Apache work subdirectory, to make it recompile JSP pages.

Actually, let me take it back. I just checked the login_proceed.jsp file again and it is not looking for a parameter, it is looking for a session attribute, which is not exactly the same thing. I don't know, which build you are running, but in 258, you can update 1 line in the login_proceed.jsp to make it work with a dynamic port number as described below

Find

	Code:
	String portStr = (String)session.getAttribute("port");

Replace with

	Code:
	String portStr = request.getParameter("port"); if (portStr == null) portStr = (String)session.getAttribute("port");

Please let me know if this works for you.

OK that did the trick thanks again!