LAT Packaging and Installation

data pipelines are now the preferred method for loading data into the ocient system for details, see load data docid\ qxg07ea5hv1vxat6neyg the {{ocient}} lat supports multiple types of packages for deployment and installation {{debian}} deb package {{centos}} rpm package raw tar gz tar folder direct jar {{docker}} container contact ocient support for the latest package for a deployment method prerequisites {{java}} 17 or greater can either be system level java, or installed somewhere accessible by the user the lat must run on ocient loader nodes where you installed the ocient rpm to provide access to numerical libraries, ensuring the correct loading of geospatial data types if this condition is not met, some geospatial objects might load inaccurately debian/centos packages 1\ install/upgrade debian sudo dpkg i lat $version all deb centos sudo rpm i lat $version 1 noarch rpm 2\ setup java if the default system java is version 17 or greater, no action is required if not, edit the service file to contain a java home environment variable pointing to a java version 17 or greater installation run systemctl edit lat insert the following \[service] environment=java home="path to java home" 3\ configure modify the lat source configuration docid\ evqivwxf1b 6ujcmkn3si and lat log4j configuration docid\ qisttril51j7 ryjzftz (see lat packaging and installation docid 1ibcxeisabypihyk60vnj for file locations) it is recommended to use the conf file for most lat configuration however, lat memory and lat memory direct can only be set by using environment variable for these use the same process as setting java home as detailed in step 2 4\ start/stop start systemctl start lat stop systemctl stop lat package contents jar /opt/lat/lat $version jar service file /usr/lib/systemd/system/lat service configuration /etc/lat/ server configuration lat conf logging configuration log4j2 xml logs /var/log/lat/lat log lat data directory /opt/lat/ lat data tar folder 1\ extract file in your preferred location run tar xzf lat $version tar gz 2\ setup java if the default system java is version 17 or greater, no action is required if not, set the $java home environment variable to a java installation with version 17 or greater export java home="path to java home" 3\ configure modify the lat source configuration docid\ evqivwxf1b 6ujcmkn3si and lat log4j configuration docid\ qisttril51j7 ryjzftz (see lat packaging and installation docid 1ibcxeisabypihyk60vnj for file locations) it is recommended to use the conf file for most lat configuration however, lat memory and lat memory direct can only be set using environment variable for these use the same process as setting java home as detailed in step 2 4\ start/stop start /lat sh \[path] , where path is an optional parameter for the path to a server configuration file (e g , lat conf ) if path is not present, it will default to config/lat conf stop stop the running lat sh script with ctrl c folder contents jar lat $version jar configuration config/ server configuration lat conf logging configuration log4j2 xml start script lat sh lat data directory lat data jar direct the lat is a java jar that can be deployed on any machine running java 17+ to run the lat use the following command line statement java \[options] dlog4j configurationfile=\<log4j config path> jar \<lat jar path> \[lat config path] log4j config path required path to the log4j configuration file lat jar path required path to the lat jar lat config path optional path to a lat service configuration file recommended java command line options see the java command line documentation https //docs oracle com/en/java/javase/17/docs/specs/man/java html#overview of java options for options max direct memory size option xx\ maxdirectmemorysize recommended 32g example xx\ maxdirectmemorysize=32g minimum heap size option xms recommended 32g example xms=32g maximum heap size option xmx recommended 32g example xmx=32g example java command line java \\ dlog4j configurationfile=config/log4j2 xml \\ xx\ maxdirectmemorysize=32g \\ xms32g \\ xmx32g \\ jar lat \[version number] jar \\ config/lat conf docker container ocient provides a docker container for the lat for testing workloads the container is not recommended for production workloads and should be used for testing only configuration the only mode of configuring the lat within a docker container is by using the service configuration environment variables a lat conf file is not supported see lat service configuration docid\ qsaetjyytgqsqtwjwmvap for the list of supported environment variables it is not recommended to override the following environment variables lat data path lat api port logging within the docker container the lat logs stdout the user can use the docker logs command to view the lat logs the following environment variables are available to modify the log level of various loggers see lat log4j configuration docid\ qisttril51j7 ryjzftz for descriptions of the loggers and log levels root log level logger root default debug binders log level logger com ocient lat sink ocient binders binder default info http log level logger org eclipse jetty server httpchannel default debug kafka log level logger org apache kafka default info java the java opts environment variable is available for controlling {{jvm}} settings container defaults to default jvm settings see the java command line documentation https //docs oracle com/en/java/javase/17/docs/specs/man/java html#overview of java options for detail on the command line options example java opts=" xx\ maxdirectmemorysize=32g xms32g xmx32g" data volumes the lat in the docker container writes persistent data to /lat/data it is recommended to mount a volume to this path so that the data can outlive the container instance the lat advanced topics docid 1apr8kawdz0q swkx4u3r is also written to this path if configured if viewing this error file is necessary, a volume must be used do not use the lat data path configuration to override the data path inside the docker container it will cause the lat to write data and error logs into different locations and will require two volumes if using the local file source, the user must mount the data directory as a bind mount inside the container it is recommended to mount to a location under the /lat/ directory when configuring the local file source the bind mount path should be configured with a file group ports by default the lat api listens on port 8080 it is not recommended to override the lat api port environment variable and instead use docker’s port mapping functionality examples docker docker run rm name lat \\ \ env root log level=info \\ \ env java opts=" xx\ maxdirectmemorysize=32g xms32g xmx32g" \\ p 8080 8080 \\ \ mount source=lat data,target=/lat/data \\ lat 2 0 0 docker compose \ version '3 9' services lat image lat 2 0 0 ports \ "8080 8080" restart on failure volumes \ lat data /lat/data environment java opts " xx\ maxdirectmemorysize=32g xms32g xmx32g" root log level info volumes lat data related links install an ocient system docid\ clmx7aipvis6ctybuagzx ingest data with legacy lat reference docid\ luijhab6vyj6g1gn5bhth