<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

<meta name="Generator" content="Microsoft Word 15 (filtered medium)">

<style><!--

/* Font Definitions */

@font-face

        {font-family:Wingdings;

        panose-1:5 0 0 0 0 0 0 0 0 0;}

@font-face

        {font-family:"Cambria Math";

        panose-1:2 4 5 3 5 4 6 3 2 4;}

@font-face

        {font-family:Calibri;

        panose-1:2 15 5 2 2 2 4 3 2 4;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

        {margin:0cm;

        margin-bottom:.0001pt;

        font-size:11.0pt;

        font-family:"Calibri",sans-serif;}

a:link, span.MsoHyperlink

        {mso-style-priority:99;

        color:#0563C1;

        text-decoration:underline;}

a:visited, span.MsoHyperlinkFollowed

        {mso-style-priority:99;

        color:#954F72;

        text-decoration:underline;}

p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph

        {mso-style-priority:34;

        margin-top:0cm;

        margin-right:0cm;

        margin-bottom:0cm;

        margin-left:36.0pt;

        margin-bottom:.0001pt;

        font-size:11.0pt;

        font-family:"Calibri",sans-serif;}

span.Shkpostityyli17

        {mso-style-type:personal;

        font-family:"Calibri",sans-serif;

        color:windowtext;}

span.Shkpostityyli18

        {mso-style-type:personal-reply;

        font-family:"Calibri",sans-serif;

        color:#1F497D;}

.MsoChpDefault

        {mso-style-type:export-only;

        font-size:10.0pt;}

@page WordSection1

        {size:612.0pt 792.0pt;

        margin:72.0pt 72.0pt 72.0pt 72.0pt;}

div.WordSection1

        {page:WordSection1;}

/* List Definitions */

@list l0

        {mso-list-id:413359604;

        mso-list-type:hybrid;

        mso-list-template-ids:2070844236 -802522806 67829763 67829765 67829761 67829763 67829765 67829761 67829763 67829765;}

@list l0:level1

        {mso-level-start-at:0;

        mso-level-number-format:bullet;

        mso-level-text:-;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:"Calibri",sans-serif;

        mso-fareast-font-family:Calibri;

        mso-bidi-font-family:"Times New Roman";}

@list l0:level2

        {mso-level-number-format:bullet;

        mso-level-text:o;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:"Courier New";}

@list l0:level3

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:Wingdings;}

@list l0:level4

        {mso-level-number-format:bullet;

        mso-level-text:\F0B7;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:Symbol;}

@list l0:level5

        {mso-level-number-format:bullet;

        mso-level-text:o;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:"Courier New";}

@list l0:level6

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:Wingdings;}

@list l0:level7

        {mso-level-number-format:bullet;

        mso-level-text:\F0B7;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:Symbol;}

@list l0:level8

        {mso-level-number-format:bullet;

        mso-level-text:o;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:"Courier New";}

@list l0:level9

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:none;

        mso-level-number-position:left;

        text-indent:-18.0pt;

        font-family:Wingdings;}

ol

        {margin-bottom:0cm;}

ul

        {margin-bottom:0cm;}

--></style><!--[if gte mso 9]><xml>

<o:shapedefaults v:ext="edit" spidmax="1026" />

</xml><![endif]--><!--[if gte mso 9]><xml>

<o:shapelayout v:ext="edit">

<o:idmap v:ext="edit" data="1" />

</o:shapelayout></xml><![endif]-->

</head>

<body lang="FI" link="#0563C1" vlink="#954F72">

<div class="WordSection1">

<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>

<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Lets use english on the mailing list. The question was if the Jetty-zip downloadable from Oskari.org is usable in production as is. You can mostly use the packaging of

 zip file in production, but I heavily recommend creating a server extension for building a customized app:

<a href="http://oskari.org/documentation/backend/setup-server-extension">http://oskari.org/documentation/backend/setup-server-extension</a> This will makes upgrading easier. When you compile the extension it provides oskari-map.war and transport.war that you

 can just copy to the Jetty/webapps replacing the default ones.<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">With the recent versions of Oskari it’s encouraged to make a similar extension for the frontend. Here’s an example of a custom frontend:

<a href="https://github.com/nls-oskari/pti-frontend">https://github.com/nls-oskari/pti-frontend</a> The documentation is a bit lacking for this, but the interesting part is that your own custom code is in your own repository and you just include the bits from

 Oskari-frontend that you need by referencing them in the applications minifierAppsetup,json with “oskari-frontend” prefix like here:

<a href="https://github.com/nls-oskari/pti-frontend/blob/master/applications/paikkatietoikkuna.fi/full-map/minifierAppSetup.json#L17">

https://github.com/nls-oskari/pti-frontend/blob/master/applications/paikkatietoikkuna.fi/full-map/minifierAppSetup.json#L17</a>. The “magic” that makes this work is having Oskari-frontend repository cloned next to your own repository when building the frontend

 (<a href="https://github.com/nls-oskari/pti-frontend/blob/master/package.json#L10">https://github.com/nls-oskari/pti-frontend/blob/master/package.json#L10</a>) and it’s all explained on the README.md:

<a href="https://github.com/nls-oskari/pti-frontend/blob/master/README.md">https://github.com/nls-oskari/pti-frontend/blob/master/README.md</a> That being said you can skip the minifierAppsetup.json part for new apps and just starting using this kind of main.js

<a href="https://github.com/kartat-tampere/tampere-frontend/blob/master/apps/geoportal/main.js">

https://github.com/kartat-tampere/tampere-frontend/blob/master/apps/geoportal/main.js</a> which uses imports to bring code in to your app. Actually running the build with minifierAppsetup.json creates a main.js that you can start using instead of the JSON-file.<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Most of our systems use nginx in front of Jetty (here’s an example config: https://github.com/oskariorg/sample-configs/tree/master/nginx  ). Note that you can just configure

 the TLS-certificate on nginx and pass the http-requests to Jetty to separate the concerns. We have environments running the Oskari-server, transport and included geoserver on a single Jetty and environments where all of these have their own Jetty instance.

 Both work so it’s up to you if you want to split the webapps on multiple Jettys or not. Having them on the same Jetty means that they all go down if you need to restart the service, but having them on multiple Jettys means a bit more work and you need something

 like nginx to forward the requests to different instances.<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">So to summarize:<o:p></o:p></span></p>

<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">         

</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">create a server-extension for custom server code (even if you don’t have custom code having a customized default view is good enough reason to do this)<o:p></o:p></span></p>

<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">         

</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">consider creating a frontend-extension (if you need

<i>any</i> customization)<o:p></o:p></span></p>

<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">         

</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">consider if you want to have clients directly connect to Jetty or having nginx/apache httpd or similar in between.<o:p></o:p></span></p>

<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">         

</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">setup TLS (https)<o:p></o:p></span></p>

<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">         

</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">If you use the included GeoServer change the credentials and/or block access to it from the internet<o:p></o:p></span></p>

<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">         

</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Change the credentials for default users in Oskari<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">I guess that’s mostly it.<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">BR,<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">       Sami<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<div>

<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">

<p class="MsoNormal"><b>L�hett�j�:</b> Oskari-user [mailto:oskari-user-bounces@lists.osgeo.org]

<b>Puolesta </b>Jere Gr�nman (TAU)<br>

<b>L�hetetty:</b> 15. tammikuuta 2019 15:47<br>

<b>Vastaanottaja:</b> Oskari-user@lists.osgeo.org<br>

<b>Aihe:</b> [Oskari-user] Oskarin tuotantopalvelimen asennus<o:p></o:p></p>

</div>

</div>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal"><span lang="EN-US">Hei<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal">Meill� on k�ynniss� Tampreen yliopistossa peltodata-hanke, jossa olemme testauksessa k�ytt�neet Oskari-alustaa. Nyt saimme uutta palvelinrautaa ja ajateltiin tehd� Oskarista oikea tuotantoversio.<o:p></o:p></p>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal">Mik� olisi paras tapa tehd� virallinen Oskari-tuotantoversio? Onko jetty-zipin k�ytt� riitt�v�� vai pit��k� ladata githubista eri komponentit?<o:p></o:p></p>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal">Terveisin Jere Gr�nman<o:p></o:p></p>

</div>

</body>

</html>