I will definitely use AJP for production ! That's out of question :) The problem is that you have only one localhost and only one 8009 port can be bound. For the 2nd OFBiz instance you have to 8009++ ( increase ) . But then you have the RMI port to take care of - if you start 2nd ofbiz instance you have to increase the default port 1099 by one.
Then you might probably want to enable the debug port... Anyway - I think it's easier to maintain many instances if each one is encapsulated on a single network virtual interface. All the containers are able to be configured to do so but one: NamingServiceContainer. So I created a patch to do so. If you think it's useful - cool. If not - I'll probably use it on my own :) Cheers, Deyan On Mon, 2009-05-25 at 08:12 -0700, BJ Freeman wrote: > The way I chose was to use ajp and change those ports. This makes > updating from the SVN easier. > http://docs.ofbiz.org/display/OFBIZ/FAQ+-+Tips+-+Tricks+-+Cookbook+-+HowTo#FAQ-Tips-Tricks-Cookbook-HowTo-HTTPD > > > Ashish Vijaywargiya sent the following on 5/25/2009 5:56 AM: > > Below is my post dated May 21, 2009 on the user mailing list on the User > > Mailing list. > > I guess you have missed my reply. > > Please read the details, give it a try and if got stuckup somewhere then > > come back to discuss the things. > > > > ------------------------------------------------------------ > > Yes this can be easily done in OFBiz. > > > > Open ofbiz-containers.xml file. > > (framework/base/config/ofbiz-containers.xml) > > Change the value of port in all the property by name "port". For ex. you > > can change http port from 8080 to 28080 > > > > Then open url.property file. (framework/webapp/config/url.properties) > > Keep the value of http & https port same as you set in the > > ofbiz-containers.xml file. > > > > So now we have two instance of OFBiz server on the same machine. > > > > -- One is running on 8080 & another one is running on 28080 port. > > > > For accessing the same database you should keep the settings of database > > same in entityengine.xml file. > > This is all from my side. > > > > Now its your turn to give it a try and if got stuck up somewhere in b/w > > then shoot an email on mailing list. > > Thanks ! > > >
