Installation Guide

Teiid needs to be installed into an existing WildFly 17.0.0 installation.

Note

Teiid provides an embedded kit, however it should be considered a tech preview as its APIs will likely evolve and there is sparse documentation.

Steps to install Teiid

Download the WildFly application server. Install the server by unzipping into a known location. Ex: /apps/jboss-install

Note

You may also choose to use an existing AS installation. However if a previous version of Teiid was already installed, you must remove the old Teiid distribution artifacts before installing the new version.

Download Teiid. Unzip the downloaded artifact inside the WildFly installation. Teiid 12.3 directory structure matches WildFly directly - it is just an overlay. This will add necessary modules and configuration files to install Teiid in WildFly 17.0.0 in both Standalone and Domain modes. Teiid provides separate configuration files for both standalone mode and domain mode. Based on mode type you selected to run WildFly 17.0.0 , you may have to run a CLI script to complete the Teiid installation.

The "Domain" mode recommended in a clustered environment to take advantage of clustered caching and cluster safe distribution of events. Teiid’s default configuration for Domain mode through CLI script configured for high availability and clustered caching.

Standalone Mode

if you want to start the "standalone" profile, execute the following command

<jboss-install>/bin/standalone.sh -c=standalone-teiid.xml

Installing Teiid using CLI script

The above is starting WildFly in a separate Teiid specific configuration that is based standalone.xml. However, if you already working with a predefined configuration for example default standalone.xml and would like to install Teiid into that configuration, then you can execute the following JBoss CLI script. First, start the server

this will install Teiid subsystem into the running configuration of the WildFly 17.0.0 in standalone mode.

Note: If you are using standalone ha or standalone full-ha, you should use the teiid-standalone-ha-mode-install.cli script instead.

Domain Mode

To start the server in "Domain" mode, install WildFly 17.0.0 and Teiid 12.3 on all the servers that are going to be part of the cluster. Select one of the servers as the "master" domain controller, the rest of the servers will be slaves that connect to the "master" domain controller for all the administrative operations. Please refer to WildFly 17.0.0 provided documentation for full details.

Once you configured all the servers, start the "master" node with following command

<jboss-install>/bin/domain.sh

and on "slave" nodes

<jboss-install>/bin/domain.sh

The slave nodes fetch their domain configuration from the "master" node.

Once all the servers are up, complete the installation to run in domain mode by executing the following command against the "master" node. Note that this only needs to be run once per domain (i.e. cluster) install. This script will install Teiid in the ha and full-ha profiles. It will also re-configure main-server-group to start the ha profile. Once in domain mode, you can not statically deploy resources by dropping them in the domain/deployments folder, so this script will deploy the default resources (file, ldap, salesforce and ws connectors) using the CLI interface.

This directory contains Teiid client libraries. It has the Teiid JDBC driver jar, "teiid-12.3.0-jdbc.jar", and also contains "teiid-hibernate-dialect-12.3.0.jar" that contains Teiid’s Hibernate dialect.

{standalone or domain}/tmp/teiid

This directory under standalone or domain, contains temporary files created by Teiid. These are mostly created by the buffer manager. These files are not needed across a VM restart. Creation of Teiid lob values(for example through SQL/XML) will typically create one file per lob once it exceeds the allowable in memory size of 8KB. In heavy usage scenarios, consider pointing the buffer directory at a partition that is routinely defragmented.

{standalone or domain}/data/teiid-data

This directory under standalone or domain, contains cached vdb metadata files. Do not edit them manually.