dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi there. Maybe we can discuss in Dushanbe next week, but as I see it,
I am not sure how to specify this at runtime with the Launch4j
wrapper.

Anyway, I have been doing a bit of testing while waiting for lots of
data to import, and can get the installer to trigger an unattended
Postgres installation, so I think the rest will be pretty easy.

Once I come up with something that actually works, I will commit it
back to the main branch for testing.

Regards,
Jason


On Tue, Mar 2, 2010 at 11:15 AM, Murodullo Latifov
<murodlatifov@xxxxxxxxx> wrote:
> Hi all,
>
> There are platform independent system variables that could be used by any Java installation in any environment, no need to spesify anything. Look here http://java.sun.com/docs/books/tutorial/essential/environment/sysprop.html and here http://www.mindspring.com/~mgrand/java-system-properties.htm.
>
> regards,
> murod
>
>
>
>
> ----- Original Message ----
> From: Jason Pickering <jason.p.pickering@xxxxxxxxx>
> To: Ola Hodne Titlestad <olatitle@xxxxxxxxx>
> Cc: dhis2-devs <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
> Sent: Tue, March 2, 2010 2:17:14 PM
> Subject: Re: [Dhis2-devs] New installer available: Testers wanted
>
> I am just chatting with Knut on this.
>
> I think the better solution would be in the Launch4j exe, where we can
> specify a path to the JRE with the <path> directive. We could do the
> same for the launch.sh script on Linux. Jetty is called by the
> Launch4j wrapper, which accept these parameters.
>
>  <jre>
>    <!-- Specify one of the following or both -->
>    <path>bundled JRE path</path>
>    <minVersion>x.x.x[_xx]</minVersion>
>    <maxVersion>x.x.x[_xx]</maxVersion>
>    <jdkPreference>jreOnly|preferJre|preferJdk|jdkOnly</jdkPreference>
>    <!-- Heap sizes in MB and % of free memory -->
>    <initialHeapSize>MB</initialHeapSize>
>    <initialHeapPercent>%</initialHeapPercent>
>    <maxHeapSize>MB</maxHeapSize>
>    <maxHeapPercent>%</maxHeapPercent>
>    <opt>text</opt>
>    ...
>  </jre>
>
> So as long as we bundle the JRE (which sounds like what needs to be
> done) then everything should work just fine. It will just increase the
> size of the install by about 15 MB.
>
>
> Maybe Lars or Bob could comment, but this seems like the solution to me.
>
> Regards,
> JPP
>
>
>
> On Tue, Mar 2, 2010 at 10:37 AM, Ola Hodne Titlestad <olatitle@xxxxxxxxx> wrote:
>> On 2 March 2010 09:21, Knut Staring <knutst@xxxxxxxxx> wrote:
>>>
>>> 2010/3/2 Jason Pickering <jason.p.pickering@xxxxxxxxx>
>>>>
>>>> >
>>>> > Lets not put BIRT in, we have Jasper, if people want BIRT they can
>>>> > download
>>>> > and install it separately, its quite big...
>>>> >
>>>>
>>>> Fine, but I need it here, and this was the original reason for the
>>>> installer, so I will have another version with BIRT.
>>>>
>>>>
>>>> >>
>>>> >> 2) A "lite install" allowing the user to download and manually
>>>> >> install, with H2. . Footprint is around 60 MB.
>>>> >
>>>> > This sounds good to me. I am envisioning this range of downloads:
>>>> >
>>>> > A. Cross-platform Live package
>>>> > (DHIS 2 Live with H2 as we have it today, no installer)
>>>>
>>>> Well, we can build multiple native installers for the Live Package. it
>>>> is just an extra line in the Pom. If we need a multiple platforms
>>>> (Mac, Linux, etc) we can build it during the installer build. Of
>>>> course, people can just grab the zip file if they want, but BitRock
>>>> can build for multiple platforms.
>>>>
>>>> > B. Windows on-line installer
>>>> > Similar to your 2. alternative.
>>>> > C. Windows off-line installer.
>>>> > Similar to your 1. alternative. A dedicated Java sounds like a good
>>>> > idea.
>>>> > Can we achieve this simply by setting JAVA_HOME "temporarily" while
>>>> > starting
>>>> > DHIS? I guess Bitrock allows for this..?
>>>>
>>>> BitRock can do this, but it may influence other programs. Could the
>>>> Launch4j wrapper be used for this, or maybe an alternative environment
>>>> variable?
>>>>
>>>
>>> Not sure JAVA_HOME is necessary - we are not compiling anything. I think
>>> it could be sufficient to modify the menu shortcut links that start DHIS.
>>
>> We set this environment variable (should perhaps think of JAVA_OPTS as well)
>> as a parameter temporarily on jetty startup, that way we are not interfering
>> with how other systems use it. Not sure how you start up jetty, but if its a
>> java -jar command we could just add JAVA_HOME=XX as a parameter to that
>> command like we could add JAVA_OPTS=XX as well.
>>
>>>
>>>
>>>>
>>>> > D. Linux debian package
>>>> > Bob's deb as we have it today.
>>>> >
>>>>
>>>> BitRock can also produce a RPM, Deb packages (somehow) but I have not
>>>> looked at the details. We might consider rolling all of this up into
>>>> BitRock at some point, but it is good to have the deb installer as
>>>> well.
>>>>
>>>>
>>>> Regards,
>>>> JPP
>>>>
>>>> --
>>>> --
>>>> Jason P. Pickering
>>>> email: jason.p.pickering@xxxxxxxxx
>>>> tel:+260968395190
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Knut Staring
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs
>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>
>
>
> --
> --
> Jason P. Pickering
> email: jason.p.pickering@xxxxxxxxx
> tel:+260968395190
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
>



-- 
--
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+260968395190