Procedure 1.1. Download JBoss Data Virtualization Installer

1. Go to https://access.redhat.com/.
2. Click Log in and enter your Red Hat Login and Password to access the Customer Portal.
3. Click Downloads -> Red Hat JBoss Data Virtualization.
4. Click Download next to the Red Hat JBoss Data Virtualization [Version] Installer option.
5. Save the file.

Procedure 1.2. Verify File Checksums on Red Hat Enterprise Linux

1. Obtain checksum values for the downloaded file

   1. Go to https://access.redhat.com/jbossnetwork/. Log in if required.
   2. Select your Product and Version.
   3. Select the packages you want to verify. Once you have chosen them, navigate to the Software Details page.
   4. Take note of the MD5 and SHA-256 checksum values.

2. Run a checksum tool on the file

   1. Navigate to the directory containing the downloaded file in a terminal window.
   2. Run md5sum downloaded_file.
   3. Run shasum downloaded_file.
   Example output:

   [localhost]$ md5sum jboss-dv-installer-[VERSION]-redhat-[VERSION].jar 
   MD5 (jboss-dv-installer-[VERSION]-redhat-[VERSION].jar) = 0d1e72a6b038d8bd27ed22b196e5887f
   [localhost]$ shasum jboss-dv-installer-[VERSION]-redhat-[VERSION].jar 
   a74841391bd243d2ca29f31cd9f190f3f1bdc02d  jboss-dv-installer-[VERSION]-redhat-[VERSION].jar
   

3. Compare the checksum values returned by the md5sum and shasum commands with the corresponding values displayed on the Software Details page.
4. Download the file again if the two checksum values are not identical. A difference between the checksum values indicates that the file has either been corrupted during download or has been modified since it was uploaded to the server. Contact Red Hat Support for assistance if after several downloads the checksum does not successfully validate.

1. Install the OpenJDK package:

   yum install java-[VERSION]-openjdk-devel

2. To install it to alternatives, run these commands:

   sudo alternatives --install /usr/bin/java java usr/lib/jvm/java-[VERSION]-openjdk/bin/java 1000

   sudo alternatives --install /usr/bin/javac javac /usr/lib/jvm/java-[VERSION]-openjdk/bin/javac 1000

3. As root, run the alternatives command for java:

   /usr/sbin/alternatives --config java

4. Select /usr/lib/jvm/jre-[VERSION]-openjdk/bin/java.
5. Then do the same for javac:

   /usr/sbin/alternatives --config javac

6. Select /usr/lib/jvm/java-[VERSION]-openjdk/bin/javac.

Procedure 2.1. Install Maven

1. Download Maven.

   1. Go to http://maven.apache.org/download.cgi.
   2. Download the apache-maven-[latest-version] ZIP file.

2. Install and configure Maven.

   • On Red Hat Enterprise Linux

     1. Extract the ZIP archive to the directory where you wish to install Maven.
     2. Open your .bash_profile file:

        vi ~/.bash_profile

     3. Add the M2_HOME environment variable to the file:

        export M2_HOME=/path/to/your/maven

     4. Add the M2 environment variable to the file:

        export M2=$M2_HOME/bin

     5. Add the variable $JAVA_HOME/bin to set the path to the correct Java installation.

        Note

        Make sure JAVA_HOME is pointing to a valid location.
     6. Add the M2 environment variable to the file:

        export PATH=$M2:$PATH

     7. Save the file and exit your text editor.
     8. Reload your profile:

        source ~/.bash_profile

     9. Run the following command to verify that Maven is installed successfully on your machine:

        mvn --version

   • On Microsoft Windows

     1. Extract the ZIP archive to the directory where you wish to install Maven. The subdirectory apache-maven-[latest-version] is created from the archive.
     2. Press Start+Pause|Break. The System Properties dialog box is displayed.
     3. Click the Advanced tab and click Environment Variables.
     4. Under System Variables, select Path.
     5. Click Edit and add the two Maven paths using a semicolon to separate each entry.
        • Add the M2_HOME variable and set the path to C:\path\to\your\Maven.
        • Add the M2 variable and set the value to %M2_HOME%\bin.
     6. Update or create the Path environment variable:
        • Add the %M2% variable to allow Maven to be executed from the command line.
        • Add the variable %JAVA_HOME%\bin to set the path to the correct Java installation.
     7. Click OK to close all the dialog boxes including the System Properties dialog box.
     8. Open Windows command prompt and run the following command to verify that Maven is installed successfully on your machine:

        mvn --version

Procedure 3.1. Install JBoss Data Virtualization

1. Open a terminal window and navigate to the location where the GUI installer was downloaded.
2. Launch the GUI installer:

   java -jar jboss-dv-VERSION-installer.jar

3. A dialogue box will open followed by the End User License Agreement. If you accept the terms of the agreement, click I accept the terms of this license agreement and then click Next.
4. Tell Red Hat JBoss Data Virtualization where Red Hat JBoss EAP is installed on your server or specify a new location if you do not have it installed as it comes bundled with the product. (If you have a pre-existing installation of Red Hat JBoss EAP, ensure that it is patched to the latest version of 6.4.x.) Click Next.
5. Ensure Teiid Installation and Dashboard Builder are selected. Click Data Services Builder if you want the graphical design tool as well or Modeshape Installation if you want that (you cannot have both Data Services Builder and Modeshape). Click Next.
6. You will be prompted to create a new EAP Admin, Dashboard Admin, Teiid data access user and Modeshape user (if Modeshape is selected) and whether you want to enable OData access. Once created, EAP Admin is added to the ManagementRealm and can be used to access the Management Console. The other users are added to the ApplicationRealm and can be used to access specific components of JBoss Data Virtualization. Enter the new username and password in the appropriate fields and click Next.
   You must ensure that you remember all of these passwords. They give you access to different parts of the system. The EAP account and password allows you to administer the EAP Server, the Dashboard password is for administrative functions related to the web interface, and the Teiid data access user and ModeShape user are for standard user access.
   Note that the username and password are not allowed to match and the password must have at least eight characters, with one alphabetical character, one numeric character and one non-numeric character.
7. You can install Red Hat JBoss Data Virtualization either with default configuration or with additional configuration options. In this example installation, we will be using the defaults only, so select Perform default configuration to install Red Hat JBoss Data Virtualization with default options. Click Next.
8. The Configure password vault screen appears. Input your desired password, which must have no fewer than six characters. Click Next.

   Note

   The default H2 database used to store this data is not suitable for production systems. Use it in testing and evaluation environments only.
9. If you selected the Data Services Builder option, you will be prompted for SSL security information. Click Generate new keystore or use the option to configure your existing keystore if you already have one you set up previously. Leave the SSL Keystore alias as "jboss". Input a password of six characters. Leave the filepath as the default. Click Next.
10. A summary of the installation is displayed. Click Next for the installation to commence. This may take a few moments. Once all the components are installed, click Next.
11. Click Generate an automatic installation script if you wish to generate an automatic script. This allows you to quickly reinstall or mass-deploy the product using the settings you have configured during the initial installation, without having to step through the wizard each time.

    Note

    An automatic installation script created for a given minor release will only work with that release. For example, you cannot use a script created with 6.0 for 6.1 or a script created for 6.3 with 6.4.
12. Click Done to exit the installer.

Procedure 3.2. Install JBoss Data Virtualization

1. Open a terminal window and navigate to the location where the GUI installer was downloaded.
2. Start the installation process:

   java -jar jboss-dv-VERSION-installer.jar -console

3. Follow the installation prompts displayed on the terminal. You can either install with default configuration or you can complete additional configuration steps.
4. Finally, generate the automatic installation script. You can use this script to perform headless installation or identical installations across multiple instances.

Procedure 3.3. Installing with a Script

• java -jar jboss-PRODUCT-installer-VERSION.jar SCRIPT.xml

Procedure 4.1. Install the Latest Version of Teiid Designer

1. Go to https://access.redhat.com/ and log in to the Customer Portal with your Red Hat login.
2. Click Downloads → Red Hat JBoss Data Virtualization.
3. Click Download next to the Red Hat JBoss Data Virtualization Teiid Designer [VERSION] Update Site Zip option and save the datavirt-teiid-designer-[VERSION]-updatesite.zip file.
4. Start Red Hat Developer Studio.
5. In Red Hat Developer Studio, select Help → Install New Software... from the main menu.
6. On the Available Software page, click the Add ... button.
7. On the Add Repository dialog:
   1. Enter “Red Hat Data Virtualization Teiid Designer” (or another unique name) in the Name field.
   2. Click the Archive... button, navigate to the location where the datavirt-teiid-designer-[VERSION]-updatesite.zip file was downloaded, and click OK.
   3. Click Add.
8. Back on the Available Software page, select Data Virtualization and all of its children from the list of available items.
9. Click Next.
10. On the Install Details page, review the items to be installed and click Next.
11. Accept any additional dependencies and license agreements, then click Finish.

• You can run JBoss Data Virtualization by starting the JBoss EAP server. To start the JBoss EAP server:

  • Red Hat Enterprise Linux

    Open a terminal and enter the command:
    $ EAP_HOME/bin/standalone.sh

  • Microsoft Windows

    Open a terminal and enter the command:
    $ EAP_HOME\bin\standalone.bat

1. To start the server in "Domain" mode, install Red Hat JBoss Data Virtualization 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.)
2. On the domain controller, copy the domain-controller/init.d directory to JBOSS_HOME/bin.
3. On the host controller, copy the host-controller/init.d directory to JBOSS_HOME/bin.
4. Prepare the directory structure:

   adduser jboss
   mkdir /opt/jdv
   mkdir /etc/jboss-as
   mkdir /var/log/jboss
   mkdir /var/run/jboss
   chown -R jboss: /opt/jdv
   chown -R jboss: /etc/jboss-as
   chown -R jboss: /var/log/jboss
   chown -R jboss: /var/run/jboss
   

5. Configure the domain:

   cat > /etc/jboss-as/jboss-as.conf <<EOF
   JBOSS_HOME=/opt/jdv/jboss-data-virtualization
   JBOSS_PIDFILE=/var/run/jboss/jboss-as-domain.pid
   JBOSS_HOST_CONFIG=host.xml
   JBOSS_ADDRESS_MANAGEMENT=10.255.0.82
   JBOSS_USER=jboss
   JBOSS_CONSOLE_LOG=/var/log/jboss/console.log
   EOF
   

6. Configure the host controller:

   cat > /etc/jboss-as/jboss-as.conf <<EOF
   JBOSS_HOME=/opt/jdv/jboss-data-virtualization
   JBOSS_PIDFILE=/var/run/jboss/jboss-as-domain.pid
   JBOSS_HOST_CONFIG=host-slave.xml
   JBOSS_MASTER_ADDRESS=10.255.0.82
   JBOSS_PUBLIC_ADDRESS=10.255.0.83
   JBOSS_USER=jboss
   JBOSS_CONSOLE_LOG=/var/log/jboss/console.log
   EOF
   

7. Add this Red Hat JBoss Data Virtualization script to systemd:

   JBOSS_HOME=/opt/jdv/jboss-data-virtualization
   cat > /tmp/teste <<EOF
   [Unit]
   Description=JBoss Data Virtualization Systemctl script
   After=NetworkManager.service
   [Service]
   Type=forking
   ExecStart=$JBOSS_HOME/bin/init.d/jboss-as-domain.sh start
   ExecStop=$JBOSS_HOME/bin/init.d/jboss-as-domain.sh stop
   ExecReload=$JBOSS_HOME/bin/init.d/jboss-as-domain.sh restart
   PIDFile=/var/run/jboss/jboss-as-domain.pid
   [Install]
   WantedBy=multi-user.target
   EOF
   

8. Configure the firewall ports on both hosts:

   cat > /etc/firewalld/services/jboss-data-virtualization.xml
   <?xml version="1.0" encoding="utf-8"?>
   <service version="1.0">
       <short>jboss-data-virtualization</short>
       <port port="31000" protocol="tcp"/>
       <port port="8080" protocol="tcp"/>
       <port port="8443" protocol="udp"/>
       <port port="8009" protocol="tcp"/>
       <port port="4447" protocol="tcp"/>
       <port port="9990" protocol="udp"/>
       <port port="9999" protocol="tcp"/>
   </service>
   EOF
   

   firewall-cmd --zone=public --add-service=jboss-data-virtualization
   firewall-cmd --permanent --zone=public --add-service=jboss-data-virtualization
   firewall-cmd --zone=public --list-services
   firewall-cmd --permanent --zone=public --list-services
   

   If you are using port offsets, adjust the values by adding the offset.
9. Once you have configured all the servers, start the "master" node:

   /bin/domain.sh

10. Start the "slave" nodes:

    /bin/domain.sh

    The slave nodes fetch their domain configuration settings from the "master" node.
11. Once VDBs have been deployed, users can connect their JDBC applications to Red Hat JBoss Data Virtualization.
12. You can enable Red Hat JBoss Data Virtualization as a service with the operating system, using this command:

    systemctl enable jboss-data-virtualization
    

    You can now start the service like this:

    systemctl start jdv
    

    To stop it, run this command:

    systemctl stop jdv
    

    To restart, run this command:

    systemctl restart jdv
    

Procedure 5.1. Start the Platform Service as a Managed Domain

1. For Red Hat Enterprise Linux, run this command: EAP_HOME/bin/domain.sh
2. For Microsoft Windows, run this command: EAP_HOME\bin\domain.bat
3. To list all available parameters for the start-up scripts, use the -h parameter.

Procedure 6.1. Configure Maven

1. Go to https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=data.services.platform.
2. Download the desired version.
3. Unzip the file on the local file system into a directory of your choosing.
4. Add entries for the unzipped repositories to Maven's settings.xml file. The following code sample contains a profile with the repositories and an activation entry for the profile:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/xsd/settings-1.0.0.xsd">
     <localRepository/>
     <profiles>
       <!-- Profile with local repositories required by Data Virtualization -->
       <profile>
         <id>dv-local-repos</id>
         <repositories>
           <repository>
             <id>dv-[VERSION]-repository</id>
             <name>DV [VERSION] GA Repository</name>
             <url>file://<!-- path to the repository -->/jboss-dv-[VERSION].redhat-[VERSION]-maven-repository/maven-repository</url>
             <layout>default</layout>
             <releases>
               <enabled>true</enabled>
               <updatePolicy>never</updatePolicy>
             </releases>
             <snapshots>
               <enabled>false</enabled>
               <updatePolicy>never</updatePolicy>
             </snapshots>
           </repository>
         </repositories>
         <pluginRepositories>
           <pluginRepository>
             <id>dv-[VERSION].GA-redhat-[VERSION]-repository</id>
             <name>DV [VERSION] GA Repository</name>
             <url>file://<!-- path to the repository -->/jboss-dv-[VERSION].redhat-[VERSION]-maven-repository/maven-repository</url>
             <layout>default</layout>
             <releases>
               <enabled>true</enabled>
               <updatePolicy>never</updatePolicy>
             </releases>
             <snapshots>
               <enabled>false</enabled>
               <updatePolicy>never</updatePolicy>
             </snapshots>
           </pluginRepository>
           
         </pluginRepositories>
       </profile>
     </profiles>
     <activeProfiles>
      <!-- Activation of the Data Virtualization profile -->
      <activeProfile>dv-local-repos</activeProfile>
     </activeProfiles>
   </settings>

Procedure 6.2. Configuring Maven to Use the Online Repositories

1. Add entries for the online repositories to Maven's settings.xml file:

   <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" 
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
         xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
   
     <profiles>
       <!-- Profile with online repositories required by Data Virtualization -->
       <profile>
         <id>dv-online-profile</id>
         <repositories>
           <repository>
             <id>jboss-ga-repository</id>
             <url>http://maven.repository.redhat.com/techpreview/all</url>
             <releases>
               <enabled>true</enabled>
             </releases>
             <snapshots>
               <enabled>false</enabled>
             </snapshots>
           </repository>
         </repositories>
         <pluginRepositories>
           <pluginRepository>
             <id>jboss-ga-plugin-repository</id>
             <url>http://maven.repository.redhat.com/techpreview/all</url>
             <releases>
               <enabled>true</enabled>
             </releases>
             <snapshots>
               <enabled>false</enabled>
             </snapshots>
           </pluginRepository>
           
         </pluginRepositories>
       </profile>    
     </profiles>
   
     <activeProfiles>
       <!-- Activation of the Data Virtualization profile -->
       <activeProfile>dv-online-profile</activeProfile>
     </activeProfiles>
   
   </settings>

2. If you modified the settings.xml file while JBoss Developer Studio was running, you must refresh Maven settings in the IDE. From the menu, choose Window → Preferences. In the Preferences Window, expand Maven and choose User Settings. Click the Update Settings button to refresh the Maven user settings in JBoss Developer Studio.
   

   Figure 6.1. Update Maven User Settings

1. Download the required Java web client and apply overlay to the modules directory.
2. Navigate to the docs/teiid/datasources/infinispan/ directory (and to the docs/teiid/datasources/infinispan-hotrod-7.1/ directoryfor Hotrod).
3. Execute the appropriate script: add-infinispan-cache-translator.cli, add-infinispan-cache-dsl-translator.cli and infinispan-hotrod-translator.cli.

1. Download the correct ODBC driver package (jboss-dv-psqlodbc-[version]-X.rpm) from https://access.redhat.com/jbossnetwork/.
2. Install the package: sudo yum localinstall jboss-dv-psqlodbc-[version]-X.rpm.

• Run the /opt/redhat/jboss-dv/v6/psqlodbc/etc/setenv.sh script:

  [localhost etc]$ ./setenv.sh

• Edit the /opt/redhat/jboss-dv/v6/psqlodbc/etc/odbc.ini file and update it with the correct username, password, and database. The database name is the VDB name.
  ODBC is enabled in JBoss Data Virtualization on port 35432 by default.

Procedure 8.1. Install the ODBC Driver on Microsoft Windows

1. Download the correct ODBC driver package (jboss-dv-psqlodbc-[version]-X.zip) from https://access.redhat.com/jbossnetwork/.
2. Unzip the installation package.
3. Double-click the jboss-dv-psqlodbc-[version]-X.msi file to start the installer.
4. The installer wizard is displayed. Click Next.
5. The End-User License Agreement will be displayed. Click I accept the terms in the License Agreement if you accept the licensing terms and then click Next.
6. If you want to install in a different directory other than the default directory shown, click the Browse button and select a directory. Click Next.
7. You are presented with a confirmation screen. Review the choices you have made and click Next to begin installation.
8. Click Finish .

Procedure 8.2. Configure the DSN for Windows Installation

1. Set the ODBC driver basic options.
2. Set the ODBC driver datasource options.
3. Set the ODBC driver global options.

1. From the Start menu, select Settings -> Control Panel.
2. The Control Panel displays. Double-click Administrative Tools.
3. Double-click Data Sources (ODBC).
4. The ODBC Data Source Administrator applet displays. Click the tab associated with the type of DSN you want to add.
5. The Create New Data Source dialog box displays. In the Select a driver for which you want to set up a data source table, select PostgreSQL Unicode.
6. Click Finish.
7. In the Data Source Name edit box, type the name you want to assign to this data source.
8. In the Database edit box, type the name of the virtual database you want to access through this data source.
9. In the Server edit box, type the host name or IP address of your Teiid runtime.

   Note

   If you are connecting via a firewall or NAT address, you must enter either the firewall address or the NAT address.
10. In the Port edit box, type the port number to which the system listens for ODBC requests. (By default, Red Hat JBoss Data Virtualization listens for ODBC requests on port 35432.)
11. In the User Name and Password edit boxes, supply the user name and password for the Teiid runtime access.
12. Leave SSL Mode to disabled. (SSL connections are unsupported at present.)
13. Provide any description about the data source in the Description field.
14. Click on the Datasource button and configure the options. Tick Parse Statements, Recognize Unique Indexes, Maximum, Text as LongVarChar and Bool as Char and set MaxVarChar to 255, Max LongVarChar to 8190, Cache Size to 100 and SysTable Prefixes to dd_:.
    On the second page, click LF, Server side prepare, default, 7.4+ and set the Extra Opts to 0x0.
15. Click Save.
    You can optionally click Test to validate your connection if Red Hat JBoss Data Virtualization is running.

1. Download the correct ODBC driver package (jboss-dv-psqlodbc-[VERSION]-X.zip) from https://access.redhat.com/jbossnetwork/.

2. Unzip the installation package

   Unzip the installation package to /opt directory.
3. Set the PATH property so that the ODBC binaries are used from the directory where you have unzipped the driver.
   $ export PATH = $PATH:/opt/redhat/jboss-dv/v6/psqlodbc/bin
4. Set the ODBCINI environmental variable to match the existing odbc.ini.
   $ export ODBCINI=/opt/redhat/jboss-dv/v6/psqlodbc/etc/odbc.ini

   Note

   If you are using the Bourne Shell as your Solaris terminal, you can add the two export commands above to your ~/.profile file, so that you do not need to run them every time. Likewise, if you are using Bash, save them in your ~/.bash_profile file instead.

Procedure 8.3. Configure ODBC Options on Red Hat Enterprise Linux

1. Install the driver manager:

   yum install unixODBC

2. Verify that your PostGreSQLdriver has installed correctly:

   odbcinst -q -d

3. To create the DSN, open the configuration file in a text editor:

   sudo vi /opt/redhat/odbc.ini

   Note

   You must either use sudo or be logged in as root to open this file.
4. Add the following configuration settings to the file:

    [<DSN name>] Driver = /usr/lib/psqlodbc.so 
    Description = PostgreSQL Data Source 
    Servername = <Teiid Host name or ip> 
    Port = 35432 Protocol = 7.4 
    UserName = <user-name> 
    Password = <password> 
    Database = <vdb-name> 
    ReadOnly = no 
    ServerType = Postgres 
    ConnSettings = UseServerSidePrepare=1 
    ByteaAsLongVarBinary=1 
    Optimizer=0 
    Ksqo=0 Trace = 
    No TraceFile = /var/log/trace.log
    Debug = No DebugFile = /var/log/debug.log 
   

5. Save the file and exit the text editor.
6. Run this command to test the DSN:

     isql <DSN-name> [<user-name> <password>] < commands.sql 
   

   To connect without DSN, use this DSN-less connection string:

      ODBC;DRIVER={PostgreSQL};DATABASE=<vdb-name>;SERVER=<host-name>;PORT=<port>;Uid=<username>;Pwd=<password> 
   

   If you run isql but you encounter an error whereby you see this message: "Can't open lib '/opt/redhat/jboss-dv/v6/psqlodbc/lib64/psqlodbc.so' : file not found" it means that some of the postgres libraries are missing.
   To fix this issue, run this command as root: yum install postgres
   To verify that the packages are now installed, run this command: rpm -qa|grep post
   You should see the postgresql and postgresql-jdbc packages listed.

Procedure 9.1. Running Red Hat JBoss Data Virtualization in an Amazon Cloud

1. Open ports by updating the security group. (At a minimum, you will need to open the TCP, HTTP and SSH ports.)
2. To start the server, add the following parameters to bind the management and host ports: -Djboss.bind.address.management=0.0.0.0 and -b 0.0.0.0

   Note

   -b is a shortcut for -Djboss.bind.address
   Here is an example:
   ./standalone.sh -Djboss.bind.address.management=0.0.0.0 -b 0.0.0.0
3. To access the AWS instance from Teiid Designer, go to the JBDS preferences and select General -> Network Connections SSH2.
   Next, under the Key Management tab, click Load Existing Key to add the key generated by Amazon.
4. To create a server connection, on the Server Configuration Overview Panel, under Server Behavior, select Remote System Deployment. Also ensure you check Server is externally managed...
   Click the New Host button, select the SSH Only option and click Next.
   Set the Host Name to match the Amazon public IP address and make the connection name the same.
   Click Finish.
5. Open the Remote Systems tab.
   Right mouse click the new connection and click connect. Fill in the User ID. (You do not need to provide a password if your SSH key is configured.)
6. Go back to the server configuration overview panel and confirm that the Host drop-down has selected the new host that you have created.
7. Start the server. (This switches the state of the server you already started.)

Procedure 9.2. Run Red Hat JBoss Data Virtualization in a Google Compute Instance

1. Open the necessary ports: Google Developers Console -> Compute -> Compute Engine -> VM Instance -> [name of your instance] -> Network.
2. Upload your public SSH key: Google Developers Console - Compute -> Compute Engine -> VM Instance -> [name of your instance] -> SSH Keys.
3. Bind the management ports (jboss.bind.address.management) to an external interface. (The default value for management ports is localhost.)

1. Go here to learn how to create an Azure virtual machine: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/tutorial-manage-vm.
2. Connect to the Azure virtual machine using SSH.
3. Copy the Red Hat JBoss Data Virtualization installer to that machine over SSH.
4. Run the installer as per normal:

   java -jar jboss-dv-VERSION-installer.jar

5. To start the server, add the following parameters to bind the management and host ports:

   -Djboss.bind.address.management=0.0.0.0

   -b 0.0.0.0

   Here is an example:

    ./standalone.sh -Djboss.bind.address.management=0.0.0.0 -b 0.0.0.0