Re: [Dhis2-devs] DHIS2 Live / Jetty v.3 / CORS

2017-12-18 Thread Jason Pickering 
Hi Chase,

We have an alternative Docker  project here
 as well with pre-built images on
Dockhub  as well which you also
may want to check out.

Regards,
Jason


On Tue, Dec 19, 2017 at 6:12 AM, Morten Olav Hansen 
wrote:

> Hi Chase
>
> It should be possible to add localhost to the CORS whitelist in settings
> (I'm pretty sure the entire frontend team is doing exactly that). What are
> you adding to it? I think you need the full protocol host and port, so
> something like http://localhost:8081 for example.
>
> Another solution would be to setup a proxy yourself, it kinda depends on
> your setup.. but if you are serving up your app using node, you can use one
> of the many the proxy libraries available for it.
>
> If you are using something like CRA (create-react-app), it includes a
> proxy already and you can just map that to your DHIS2 instance.
>
> Please be aware that the live package has some issues with analytics
> (unless you have mapped it to use a local postgres service), another
> approach could be to use dhis2-docker [1].
>
> [1] https://github.com/dhis2/dhis2-docker
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Tue, Dec 19, 2017 at 3:09 AM, Freeman, Chase  > wrote:
>
>> Hi all,
>>
>>
>>
>> I’m getting started with using the D2 library and I had intended to use
>> the DHIS2 Live package to quickly get started in a test environment. I’ve
>> run into some crippling CORS errors and investigated the Jetty Servlet’s
>> web.xml file to see if I could allow for cross-origin requests. Alas, when
>> I tried to insert the filter it would fail time no matter the
>> configuration. Is this because it is Jetty Version 3 (as opposed to 9.4
>> now)? Or is there a better work around? The CORS whitelist in Access
>> Settings is not working for Localhost.
>>
>>
>>
>> Any tips/assistance in using DHIS2 Live to work with the D2 Library would
>> be much appreciated.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> *Chase Freeman*
>>
>> Jr. Web Developer
>> Management Systems International
>> A Tetra Tech Company
>> Arlington, VA USA
>>
>> (Work) +1 703 979 7170 x219 <+1%20703-979-7170>
>>
>> chase.free...@msi-inc.com
>>
>>
>>
>> www.msiworldwide.com
>>
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Jason P. Pickering
email: jason.p.picker...@gmail.com
tel:+46764147049
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] DHIS2 Live / Jetty v.3 / CORS

2017-12-18 Thread Morten Olav Hansen 
Hi Chase

It should be possible to add localhost to the CORS whitelist in settings
(I'm pretty sure the entire frontend team is doing exactly that). What are
you adding to it? I think you need the full protocol host and port, so
something like http://localhost:8081 for example.

Another solution would be to setup a proxy yourself, it kinda depends on
your setup.. but if you are serving up your app using node, you can use one
of the many the proxy libraries available for it.

If you are using something like CRA (create-react-app), it includes a proxy
already and you can just map that to your DHIS2 instance.

Please be aware that the live package has some issues with analytics
(unless you have mapped it to use a local postgres service), another
approach could be to use dhis2-docker [1].

[1] https://github.com/dhis2/dhis2-docker

-- 
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org

On Tue, Dec 19, 2017 at 3:09 AM, Freeman, Chase 
wrote:

> Hi all,
>
>
>
> I’m getting started with using the D2 library and I had intended to use
> the DHIS2 Live package to quickly get started in a test environment. I’ve
> run into some crippling CORS errors and investigated the Jetty Servlet’s
> web.xml file to see if I could allow for cross-origin requests. Alas, when
> I tried to insert the filter it would fail time no matter the
> configuration. Is this because it is Jetty Version 3 (as opposed to 9.4
> now)? Or is there a better work around? The CORS whitelist in Access
> Settings is not working for Localhost.
>
>
>
> Any tips/assistance in using DHIS2 Live to work with the D2 Library would
> be much appreciated.
>
>
>
> Cheers,
>
>
>
> *Chase Freeman*
>
> Jr. Web Developer
> Management Systems International
> A Tetra Tech Company
> Arlington, VA USA
>
> (Work) +1 703 979 7170 x219
>
> chase.free...@msi-inc.com
>
>
>
> www.msiworldwide.com
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] DHIS2 Live / Jetty v.3 / CORS

2017-12-18 Thread Freeman, Chase 
Hi all,

I'm getting started with using the D2 library and I had intended to use the 
DHIS2 Live package to quickly get started in a test environment. I've run into 
some crippling CORS errors and investigated the Jetty Servlet's web.xml file to 
see if I could allow for cross-origin requests. Alas, when I tried to insert 
the filter it would fail time no matter the configuration. Is this because it 
is Jetty Version 3 (as opposed to 9.4 now)? Or is there a better work around? 
The CORS whitelist in Access Settings is not working for Localhost.

Any tips/assistance in using DHIS2 Live to work with the D2 Library would be 
much appreciated.

Cheers,

Chase Freeman
Jr. Web Developer
Management Systems International
A Tetra Tech Company
Arlington, VA USA
(Work) +1 703 979 7170 x219
chase.free...@msi-inc.com

www.msiworldwide.com

___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] [Dhis2-users] Installing Shiny App in dhis2

2017-12-18 Thread Jason Pickering 
Hi  Isaiah,

Shiny apps are written in the R programming language, so you would need to
run this on an external R server, and then use another app (I guess) to
connect with DHIS2 to the Shiny server.

DHIS2 itself has no capability to  run Shiny apps, which must be written in
pure HTML and JavaScript and utilize only the native API of DHIS2. If you
are using external services, such as Shiny, you would need to take that
into account in your DHIS2 facing app.

Regards,
Jason


On Mon, Dec 18, 2017 at 11:03 AM, Isaiah Nyabuto 
wrote:

> Hi.
>
> Has anyone ever tried to install  shiny app in dhis2?
>
> I am not able to install my shiny app. I get an error when uploading the
> zip file: Manifest file missing.
>
> Does dhis2 support shiny apps?
>
> Kindest regards - Isaiah
> --
> 
> 
> Isaiah Nyabuto
> +254 729 572 616
> Bsc. Health Records Management & Informatics, JKUAT.
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Jason P. Pickering
email: jason.p.picker...@gmail.com
tel:+46764147049
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] 2.28 analytics - problem with validation result

2017-12-18 Thread Olav Poppe 
So just to highlight, this is where it seems to go wrong, but it is not clear 
why/what:

* INFO  2017-12-17 19:18:00,843 [Level: INFO, category: ANALYTICSTABLE_UPDATE, 
time: Sun Dec 17 19:18:00 UTC 2017, message: Applying aggregation levels] 
(InMemoryNotifier.java [taskScheduler-19])
* INFO  2017-12-17 19:18:00,845 [Level: ERROR, category: ANALYTICSTABLE_UPDATE, 
time: Sun Dec 17 19:18:00 UTC 2017, message: Process failed: null] 
(InMemoryNotifier.java [taskScheduler-19])

> 18. des. 2017 kl. 07:42 skrev Olav Poppe :
> 
> Thanks Alex, but those email adresses have just been removed from the log for 
> the purpose of sharing it here - they are in the system.
> 
> Regards
> Olav
> 
> 18. des. 2017 kl. 04:07 skrev Alex Tumwesigye  >:
> 
>> Hello Olav
>> Add an email address to user sakibou
>> 
>> Alex
>> 
>> On Monday, December 18, 2017, Olav Poppe > > wrote:
>> Hi devs, 
>> we have an instance newly upgraded to 2.28 where analytics fails on 
>> generation of VALIDATION_RESULTS. This does not happen on the staging server 
>> we used for testing, which has a copy of the production server from a few 
>> weeks back, so only minor differences. Unfortunately, there is limited info 
>> in the log (copied below) - any advice on troubleshooting? Is 
>> VALIDATION_RESULTS supposed to have the result of running validation rules? 
>> If so, these are the same on the staging and production server.
>> 
>> Regards
>> Olav
>> 
>> 
>> 
>> * INFO  2017-12-17 19:18:00,789 Table update done: analytics_orgunittarget: 
>> 00:00:00.577 (Clock.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,789 [Level: INFO, category: 
>> ANALYTICSTABLE_UPDATE, time: Sun Dec 17 19:18:00 UTC 2017, message: Table 
>> update done] (InMemoryNotifier.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,789 [Level: INFO, category: 
>> ANALYTICSTABLE_UPDATE, time: Sun Dec 17 19:18:00 UTC 2017, message: Updating 
>> tables: VALIDATION_RESULT] (InMemoryNotifier.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,790 Starting update: analytics_validationresult, 
>> processes: 11, org unit levels: 6: 00:00:00.000 (Clock.java 
>> [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,793 Get tables using earliest: Sun Jan 01 
>> 00:00:00 UTC 2017 (JdbcValidationResultTableManager.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,796 Table update start: 
>> analytics_validationresult, partitions: [analytics_validationresult_2017], 
>> last years: 1, earliest: Sun Jan 01 00:00:00 UTC 2017: 00:00:00.006 
>> (Clock.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,797 [Level: INFO, category: 
>> ANALYTICSTABLE_UPDATE, time: Sun Dec 17 19:18:00 UTC 2017, message: 
>> Performing pre-create table work, org unit levels: 6] (InMemoryNotifier.java 
>> [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,797 Performed pre-create table work: 
>> 00:00:00.007 (Clock.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,797 [Level: INFO, category: 
>> ANALYTICSTABLE_UPDATE, time: Sun Dec 17 19:18:00 UTC 2017, message: Creating 
>> analytics tables] (InMemoryNotifier.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,805 Creating table: 
>> analytics_validationresult_temp_2017, columns: 28 
>> (JdbcValidationResultTableManager.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,807 Created analytics tables: 00:00:00.017 
>> (Clock.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,807 [Level: INFO, category: 
>> ANALYTICSTABLE_UPDATE, time: Sun Dec 17 19:18:00 UTC 2017, message: 
>> Populating analytics tables] (InMemoryNotifier.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,808 Populate table task number: 1 
>> (DefaultAnalyticsTableService.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,843 Populated table in 0.03 seconds: 
>> analytics_validationresult_temp_2017 (AbstractJdbcTableManager.java 
>> [taskScheduler-15])
>> * INFO  2017-12-17 19:18:00,843 Populated analytics tables: 00:00:00.053 
>> (Clock.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,843 [Level: INFO, category: 
>> ANALYTICSTABLE_UPDATE, time: Sun Dec 17 19:18:00 UTC 2017, message: Applying 
>> aggregation levels] (InMemoryNotifier.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,845 [Level: ERROR, category: 
>> ANALYTICSTABLE_UPDATE, time: Sun Dec 17 19:18:00 UTC 2017, message: Process 
>> failed: null] (InMemoryNotifier.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,849 'system-process' create 
>> org.hisp.dhis.message.MessageConversation, name: Analytics table process 
>> failed, uid: rTGPfiuHkgV (AuditLogUtil.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,851 Gateway configuration does not exist 
>> (SmsMessageSender.java [taskScheduler-19])
>> * INFO  2017-12-17 19:18:00,853 Sending email to user: null with email 
>> address:  to host: smtp.gmail.com:587  
>>