I mean Sql-step in the setup
@ZakarFin Thanks for the answer! So in order to get Capabilities updated, let say for example in every hour, I must edit oskari-ext.properties file and put "oskari.scheduler.job.UpdateCapabilitiesJob.cronLine=0 0 * ?" to there. I'll try this and will report a result here :-) Btw, when the next Oskari release is coming out? I have discussed earlier (during Oskari event held in Joensuu) with @SannaJokela about this, but she didn't remember/know the exact date. Have you any specific date on your mind? We are looking forward to get Oskari updated and waiting 3D functionalities (we hope that we could use this functionality for publishing our 3D city model / drone captured Mesh-models).
@ZakarFin Now everything seems to go as intented during migration but frontend gives "Attempt to add layer that is not available.". Steepping into the findMapLayer, it tries to find a layer with the ID 3 (this can be found from the DB as expected) but fails because layerList is empty (as returned by this._loadedLayersList).
Hi, @ZakarFin currently all Finnish Oskari servers that get metadata from paikkatietohakemisto.fi do not seem to be able to show metadata (at least Tampere, Lounaispaikka, HSY and Joensuu). Jussi Tahvainainen asked help from NLS and according to a person from NLS the paikkatietohakemisto.fi service has changed from http to https a few weeks ago but they couldn't help otherwise. I wonder if this is the reason because at least request to URL https://geonetwork.nls.fi/geonetwork/srv/fin/resources.get.uuid?access=public&bed0e9ee-0856-4ba7-91b9-801875608188 returns "service not found" error. Do you happen to have suggestions how the metadata could be fetched succesfully by Oskari? The oskari-ext.properties, at least in Tampere, currently has e.g. line search.channel.METADATA_CATALOGUE_CHANNEL.image.url.fi=http://geonetwork.nls.fi/geonetwork/srv/fi/resources.get.uuid?access=public& . Should the config file be edited somehow or is there, for example, something that should be done by paikkatietoikkuna.fi people?
and the s letter was added in the beginning of the urls: 
.
@ernoma I think there's some redirects happening still since fi is now fin etc. Here's the configs we use:
service.metadata.url=https://www.paikkatietohakemisto.fi/geonetwork/srv/fin/csw
search.channel.METADATA_CATALOGUE_CHANNEL.query.url=http://geonetwork.nls.fi/geonetwork/srv/fin/csw
search.channel.METADATA_CATALOGUE_CHANNEL.server.url=http://geonetwork.nls.fi
# metadatasearch results in liferay portal search use this as base url (updated for GN3)
search.channel.METADATA_CATALOGUE_CHANNEL.fetchpage.url.fi=https://www.paikkatietohakemisto.fi/geonetwork/srv/fin/catalog.search#/metadata/
search.channel.METADATA_CATALOGUE_CHANNEL.fetchpage.url.sv=https://www.paikkatietohakemisto.fi/geonetwork/srv/swe/catalog.search#/metadata/
search.channel.METADATA_CATALOGUE_CHANNEL.fetchpage.url.en=https://www.paikkatietohakemisto.fi/geonetwork/srv/eng/catalog.search#/metadata/
search.channel.METADATA_CATALOGUE_CHANNEL.metadata.catalogue.server=https://www.paikkatietohakemisto.fi
search.channel.METADATA_CATALOGUE_CHANNEL.metadata.catalogue.path=/geonetwork/srv/fin/csw
search.channel.METADATA_CATALOGUE_CHANNEL.metadata.catalogue.queryParams=SERVICE=CSW&VERSION=2.0.2&request=GetDomain&PropertyName=
Though I guess search.channel.METADATA_CATALOGUE_CHANNEL.query.url is an old one since it doesn't have https and things still work
Also Liferay is not involved :D That is an old comment
I mean if your code runs on the same scope/document as Oskari code
You can register a layer to something called MapLayerService and it appears on layer listings etc. The you can add a registered layer to the map by another request/function call. Or if you want you can call methods in openlayers directly
I can’t link specifics now as I’m on a phone
Here's some old'ish documentation about this: https://oskari.org/documentation/data/maplayer-definitions
You can try calling Oskari.getSandbox().getService('Oskari.mapframework.service.MapLayerService') and see what it offers. Adding the maplayer to map is done with Oskari.getSandbox().getMap().addLayer()
The object returned by getMap() is https://github.com/oskariorg/oskari-frontend/blob/master/bundles/mapping/mapmodule/service/map.state.js
A direct access to openlayers can be fetched by Oskari.getSandbox().findRegisteredModuleInstance('MainMapModule').getMap()
@Terminal-Redux ^
What do you recommend to do to access the Oskari.getSandbox().getService...etc. line when placing it the separate code? I mean the app that I've developed is on Angular, but obviously, it will not have access to oskari.min.js until it is deployed onto our server which has Oskari running. Thus, if I want to compile it (which I do in order to make it run alongside Oskari), it will throw an error because Oskari is undefined inside of the app.
I haven't really done Angular in a while but what you want to search for is how to access global variables from [something]. Not really sure what causes the error but here's something for typescript https://stackoverflow.com/questions/13252225/call-a-global-variable-inside-module
For Webpack https://webpack.js.org/configuration/externals/
If I remember correctly Angular has been TypeScript since version 2
Short addition to the previous message. The first step I'd like to do, is to change requested attribute data from columns into rows (to get better readability when there are many attributes in data) or maybe do some pattern based renaming for attribute names or generating pressable hyperlinks (if data contain some values starting with http prefix). Hopefully that kind of modifications could be done. Thanks in advance!
@jarnokin_twitter There's some things that can be done if you know xslt transforms but it's not very refined. Basically you can transform an xml-response from the server to a certain type of JSON-message using the XSLT. I don't think we have it documented what the JSON-format is :P
Basically something like this but instead of HTML you transform to JSON https://www.w3schools.com/xml/tryxslt.asp?xmlfile=cdcatalog&xsltfile=cdcatalog
@ZakarFin Thanks for the answer. I think this is not the solution in my case. XML to Html transformation could help (if services returns a valid XML), but I'm not sure. Btw, Is there any way to set template/default settings how GFI response will be parsed in Oskari? At the moment I'm getting wide response windows and due that, the reponse is not so readable. When requesting data from own hosted WMS Server, I'm able to use FTL templates to format GFI response, but when requesting data from 3rd party services, this is not possible. Data which causes this consern is luonnonsuojelualueet (protected sites) requested from SYKE's WMS interface. There is same "wide feature information window" syndrome also in paikkatietoikkuna.fi website too - so nothing can be done for this in Oskari side?