I would like to create more than 1 ODK aggregate instances for use by
different people in my organization on one server , i hope this is
possible and if so how do you configure it .I am running tomcat on port
8080 and when i try to do the setup of another one it is overwriting the
current one i hope there is a way of renaming the .WAR file so that they
are on different paths
Yes, you should run the installer a 2nd time and specify a different
database for the 2nd instance. This ensures that the two instances do not
overwrite or otherwise interfere with each other.
Then name the WAR file something different (e.g, ODKOtherName), and the two
independent Aggregate instances will be reachable via the two paths ending
with the names you gave your WAR files -- e.g,, http://your.org/ODKAggregateand http://your.org/ODKOtherName
Mitch
···
On Wed, Aug 29, 2012 at 6:11 AM, Mukanya wrote:
good day guys
I would like to create more than 1 ODK aggregate instances for use by
different people in my organization on one server , i hope this is
possible and if so how do you configure it .I am running tomcat on port
8080 and when i try to do the setup of another one it is overwriting the
current one i hope there is a way of renaming the .WAR file so that they
are on different paths
Aggregate, in its default configuration, takes a monstrous amount of server
resources. Thus, spinning up multiple instances on a single Tomcat can
quickly exhaust, e.g., the amount of memory available to the Java virtual
machine. See this thread, e.g., in the developer's group:
We have since spent many hours tweaking the codebase and server
configuration in order to stably run many instances on AWS servers. It has
been a bit of an ongoing project for us. We now have a system that works
very well, but it's somewhat specific to our modified codebase (which uses
some components that require extra resources) -- so our final configuration
parameters are unlikely to work in your case. I would suggest, though,
trying the parameters I suggested on the above thread. Those may work for
you.
Best,
Chris
···
On Wed, Jan 16, 2013 at 7:25 AM, wrote:
On Wednesday, August 29, 2012 10:28:30 PM UTC+8, Mitch wrote:
Yes, you should run the installer a 2nd time and specify a different
database for the 2nd instance. This ensures that the two instances do not
overwrite or otherwise interfere with each other.
Then name the WAR file something different (e.g, ODKOtherName), and the
two independent Aggregate instances will be reachable via the two paths
ending with the names you gave your WAR files -- e.g,, http://your.org/ODKAggregate and http://your.org/ODKOtherName
I would like to create more than 1 ODK aggregate instances for use by
different people in my organization on one server , i hope this is
possible and if so how do you configure it .I am running tomcat on port
8080 and when i try to do the setup of another one it is overwriting the
current one i hope there is a way of renaming the .WAR file so that they
are on different paths
--
Mitch Sundt
Software Engineer
University of Washington mitche...@gmail.com
I was able to install 2 odk instances in one server. I created a 3rd
instance but when I started it in Tomcat Manager it fails to start with the
following message "FAIL - Application at context path /assessor could not
be started"
Also, you'll want to investigate the Tomcat log files to really dig down
into what's failing in your case.
Good luck,
Chris
···
On Wed, Jan 16, 2013 at 7:45 AM, Christopher Robert wrote:
ruelluis,
Aggregate, in its default configuration, takes a monstrous amount of
server resources. Thus, spinning up multiple instances on a single Tomcat
can quickly exhaust, e.g., the amount of memory available to the Java
virtual machine. See this thread, e.g., in the developer's group:
We have since spent many hours tweaking the codebase and server
configuration in order to stably run many instances on AWS servers. It has
been a bit of an ongoing project for us. We now have a system that works
very well, but it's somewhat specific to our modified codebase (which uses
some components that require extra resources) -- so our final configuration
parameters are unlikely to work in your case. I would suggest, though,
trying the parameters I suggested on the above thread. Those may work for
you.
On Wednesday, August 29, 2012 10:28:30 PM UTC+8, Mitch wrote:
Yes, you should run the installer a 2nd time and specify a different
database for the 2nd instance. This ensures that the two instances do not
overwrite or otherwise interfere with each other.
Then name the WAR file something different (e.g, ODKOtherName), and the
two independent Aggregate instances will be reachable via the two paths
ending with the names you gave your WAR files -- e.g,, http://your.org/ODKAggregate and http://your.org/ODKOtherName
I would like to create more than 1 ODK aggregate instances for use by
different people in my organization on one server , i hope this is
possible and if so how do you configure it .I am running tomcat on port
8080 and when i try to do the setup of another one it is overwriting the
current one i hope there is a way of renaming the .WAR file so that they
are on different paths
--
Mitch Sundt
Software Engineer
University of Washington mitche...@gmail.com
I was able to install 2 odk instances in one server. I created a 3rd
instance but when I started it in Tomcat Manager it fails to start with the
following message "FAIL - Application at context path /assessor could not
be started"