|Downloading the binaries|
|Installing JBoss Data Virtualization Runtime|
|Initial setup of JBoss Developer Studio|
|Configuring JBDS for JBoss Data Virtualization|
- Determine if the operating system is 32-bit or 64-bit and install the correct version of JDK 1.8 based on the bitness determined.
- On the development VM ensure atleast 4 GB of RAM and 10 GB of HDD space is available in addition to the OS needs.
- Ensure that environment variable JAVA_HOME is set to JDK folder. The folder bin should be one of the immediate subfolders of JAVA_HOME.
- Ensure that java is found on that system path. One should be able to run the command
javaat the command prompt from within any folder.
Downloading the binaries
Data Virtualization Server Runtime
- From https://developers.redhat.com/downloads/ here
- From Red Hat customer portal here (requires an account)
When done, one should find jboss-dv-6.3.0-1-installer.jar file downloaded.
Installing JBoss Data Virtualization Runtime
In the folder where the executable was downloaded, following command should be run. If the user account used for the installation does not have write permissions to the installation path, either the command must be run as root or prepended with
sudo in front of the command if the user is part of the sudoers list.
java -jar jboss-dv-installer-6.1.0.redhat-3.jar
On Windows, if the JAVA_HOME is set and PATH environment variable is updated to have java on the path, the jar can be double-clicked to start the installation.
Follow the steps below to complete the installation
Step 2 : Choose the installation path
Step 3 : Select the all of the default packs (image not shown) and proceed by clicking on Next
Step 4 : Provide passwords for Data Virtualization accounts
In this step, provide passwords for each account that will be created by JBoss Data Virtualization. For Teiid data access account, optionally choose to enable OData access.
One can choose to use the same password for all the accounts by checking the box provided at the very top.
When done, click Next to continue.
Step 5 : Configure Maven settings
In this step, configure Maven settings if the quickstarts packaged with the product need to be run. When installing locally on a developer’s VM, ideally point the asked path to
~/.m2/settings.xml (file under the user’s .m2 folder under the home directory). When installing on any other VM or environment, the asked path should point to settings.xml file containing all the Maven entries required for that environment.
Step 6 : If installing on a VM running on pure IPv6, choose to enable IPv6 by checking the box (image not shown).
Step 7 : Configure runtime environment
Step 8 : Provide a vault keystore password. Click Next to continue.
This screen is not shown when same password is applied to all data virtualization accounts
Step 9 : Verify all the chosen installation parameters in this step (image not shown) and click Next to continue.
Step 10 : Observe the component installation progress
Step 11: Testing of the installation
Click on Next to continue once the testing is successful.
Step 12: Click Done (image not shown) on the very last screen to end the installation
Initial setup of JBoss Developer Studio
For this portion follow the instructions in this article. The same post includes how to add the JBoss Data Virtualization Development integration stack, and must neccessarily executed as a prerequisite to further steps.
Configuring JBDS for JBoss Data Virtualization
This section would guide the last steps of configuring the JBDS for Data Virtualization.
Create a new server in JBDS
Launch JBDS. In the JBDS menu choose Window → Show View → Servers. If a link is shown that says No servers available …, click on it. A new dialog should be presented that resembles the images shown below. Create a new server by the name JBoss Data Virtualization and click Next to continue.
Create a new Server adapter
When creating a new Server adapter
- Choose local if the runtime server is on the same VM as JBDS. JBDS should ideally connect and work with local runtime server for development purposes and for this exercise that would be the choice
- Choose remote if the runtime server is running on a different VM but on a reachable network
- Ideally choose Management Operations in ‘Controlled by’ options
Create a new Server Runtime
Configure the newly created server
Once the server is created, click on the name of the server in the list at the bottom to launch a window displaying the configuration. Since the local profile is chosen, the only option that makes any difference in how JBDS interacts with the runtime server is whether the Server is externally managed checkbox under Server Behavior as shown in the image.
- If the box is checked, the server has to be started independently of JBDS. This approach doesn’t necessarily control server’s start/stop behavior.
- If the box is cleared, then the server can be started/stopped thru JBDS If the JBDS process exits, the server runtime is killed as well. The image below reflects this option.
Working in Teiid perspective
Getting started with projects
The last step before getting started with projects is to connect JDBS to the runtime server. This could be done by right clicking on the server name in the server list and then choosing ‘Start’. When started in this manner, in the Teiid perspective, on the left hand side under Default Server one can notice a blue glow next to label Teiid Version as shown below. This indicates a successful connection to the runtime server and the development can now begin.