Procedure 3.1. Download JBoss Data Virtualization Installer

1. Login to the Red Hat Customer Portal.

   1. Go to https://access.redhat.com/.
   2. Click Log in and enter your Red Hat Login and Password to access the Customer Portal. You will need to register for an account if you do not yet have one.

2. Download JBoss Data Virtualization Installer.

   1. Click Downloads -> Red Hat JBoss Data Virtualization.
   2. Click Download next to the Red Hat JBoss Data Virtualization [Version] Installer option.
   3. Save the file.

Procedure 3.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 package 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 md5 downloaded_file.
   3. Run shasum downloaded_file.
   Example output:

   [localhost]$ md5 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

   1. Compare the checksum values returned by the md5 and shasum commands with the corresponding values displayed on the Software Details page.
   2. 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.
   3. The downloaded file is safe to use if the two checksum values are identical.

Procedure 4.1. Install Open JDK on Red Hat Enterprise Linux

1. Subscribe to the Base Channel

   Obtain the OpenJDK from the RHN base channel. (Your installation of Red Hat Enterprise Linux is subscribed to this channel by default.)

2. Install the Package

   Use the yum utility to install OpenJDK: yum install java-1.7.0-openjdk-devel

3. Verify that OpenJDK is Now Your System Default

   You can ensure the correct JDK is set as the system default by following the steps below.
   1. As root, run the alternatives command for java:

      /usr/sbin/alternatives --config java

   2. Select /usr/lib/jvm/jre-1.7.0-openjdk/bin/java.
   3. Then do the same for javac:

      /usr/sbin/alternatives --config javac

   4. Select /usr/lib/jvm/java-1.7.0-openjdk/bin/javac.

Procedure 4.2. Install Maven

1. Download Maven.

   1. Enter http://maven.apache.org/download.cgi in the address bar of a browser.
   2. Download apache-maven-[latest-version] ZIP file and save it to your hard drive.

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 in a terminal: vi ~/.bash_profile.
     3. Add the M2_HOME environment variable to the file:

        export M2_HOME=/path/to/your/maven

     4. Also add the M2 environment variable to the file:

        export M2=$M2_HOME/bin

     5. Add the M2 environment variable to the file:

        export PATH=$M2:$PATH

     6. Make sure that JAVA_HOME is set to the location of your JDK. For example:

        export JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk.x86_64

     7. Make sure that $JAVA_HOME/bin is in your PATH environment variable.
     8. Save the file and exit your text editor.
     9. Run this command to ensure the changes take effect: source ~/.bash_profile
     10. 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 5.1. Install JBoss Data Virtualization

1. Open a terminal window and navigate to the location where the GUI installer was downloaded.
2. Enter the following command to 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 Modeshape Installation are ticked. Click Next.
6. You will be prompted to create a new EAP Admin, Dashboard Admin, Teiid data access user and ModeShape user 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. For this exercise, 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 is not suitable for production databases. Use it in testing and evaluation environments only.
9. 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.
10. Click Generate an automatic installation script if you wish to generate 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

    Note that an automatic installation script created for Red Hat JBoss Data Virtualization 6.0 will not work with Red Hat JBoss Data Virtualization 6.1.
11. Click Done to exit the installer.

Procedure 5.2. Install JBoss Data Virtualization

1. Open a terminal window and navigate to the location where the GUI installer was downloaded.
2. Enter the following command to 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. The final step involving generating automatic installation script. You can use this script to perform headless installation or identical installations across multiple instances.

Procedure 5.3. Installing with a Script

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

Procedure 6.1. Install JBoss Developer Studio Integration Stack

1. Start Red Hat JBoss Developer Studio.
2. In Red Hat JBoss Developer Studio, click Help > Install New Software... action from the main menu.
3. On the Available Software page, click the Add ... button.
4. On the Add Repository dialog, enter following details:
   Enter JBDSIS (or another unique name) in the Name field.
   Enter https://devstudio.redhat.com/9.0/stable/updates/integration-stack/earlyaccess/ in the Location field.
5. Click OK.
6. In the update site tree view, select the JBoss Data Virtualization Development folder and all its children.

   Note

   If JBDSIS is already installed then proceed to next step. You can confirm that JBDSIS is installed on your machine by clicking What is already installed link.
7. Click Next.
8. Accept any additional dependencies and license agreements, then click Finish to complete.

Procedure 7.1. Starting JBoss Data Virtualization

• Start the JBoss EAP Server

  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

Procedure 7.2. Start the Platform Service as a Managed Domain

1. For Red Hat Enterprise Linux.

   Run the command: EAP_HOME/bin/domain.sh

2. For Microsoft Windows Server.

   Run the command: EAP_HOME\bin\domain.bat

3. Optional: Pass additional parameters to the start-up script.

   To list all available parameters for the start-up scripts, use the -h parameter.

Procedure 8.1. 

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 8.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 8.2. Update Maven User Settings

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. Once you have configured all the servers, start the "master" node: /bin/domain.sh
3. Start the "slave" nodes: /bin/domain.sh
   The slave nodes fetch their domain configuration settings from the "master" node.
   See the section "Start JBoss EAP 6 as a Managed Domain" for more information.
4. Once all the servers are running, complete the installation to run in domain mode by executing this command on the "master" node: /bin/jboss-cli.sh --file=[JBOSS_HOME_DIR]/cli-scripts/teiid-domain-mode-install.cli
   This only needs to be run once per domain (cluster) install. This script will install Red Hat JBoss Data Virtulization in the ha and full-ha profiles. It will also re-configure the 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 directory, so this script will deploy the default resources (such as file, ldap, salesforce and ws connectors) using the CLI interface.
5. If you need to install Red Hat JBoss Data Virtualization in profiles other than HA, edit the teiid-domain-mode-install.cli file before installing it, and make the appropriate changes to the profile, socket-bindings, and server-groups.
6. Once VDBs have been deployed, users can now connect their JDBC applications to Red Hat JBoss Data Virtualization.

1. Navigate to the docs/teiid/datasources/infinispan/ directory.
2. Execute the appropriate script: add-infinispan-cache-translator.cli or add-infinispan-cache-dsl-translator.cli.

Procedure 11.1. Install the ODBC Driver on Red Hat Enterprise Linux

1. Download the driver

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

2. Install the package

   Run sudo yum localinstall jboss-dv-psqlodbc-[version]-X.rpm.

• Configure the Environment

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

  [localhost etc]$ ./setenv.sh

  This script adds the required directories to the LD_LIBRARY_PATH and PATH environment variables. This script has to be run every time you want to use the driver.

• 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 11.2. 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 the 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, when you are happy, Click Next to begin installation.
8. When it has finished, a screen will appear to inform you the installation process has ended. Click Finish to exit the wizard.

Procedure 11.3. 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.

Procedure 11.4. Install the ODBC Driver on Solaris

1. Download the driver

   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

   Set 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 environmental variable

   Set ODBCINI environmental variable to 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, you will not need to run them every time. Likewise, if you are using Bash, save them in your ~/.bash_profile file instead.

• 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 11.5. Configure ODBC Options on Red Hat Enterprise Linux

1. Run this command to install the driver manager: yum install unixODBC.
2. Run this command to 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 11.6. Configure the Data Source Name (DSN) on Microsoft Windows

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.

Procedure 12.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 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, use 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 12.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.

Procedure 12.3. Connecting to Azure

1. Get the JDBC connection string for your Azure database. In the Azure management portal, click on the database then find the Connect to your database section.
2. Click on the View SQL Database connection strings... link. This will give you the JDBC strings you require.
3. The cloud database requires that the IP address of the machine accessing it be registered in its firewall rules. On the Azure database dashboard, click Manage allowed IP addresses, then add the IP address of your server. This is straightforward if the DV instance resides on your local server.
4. If the DV instance is deployed on OpenShift, ssh into your OpenShift instance. On the command line, enter ping $OPENSHIFT_GEAR_DNS. The first line of the ping response will look like this:

                      PING ec2-54-221-126-53.compute-1.amazonaws.com (10.181.128.66) 56(84) bytes of data.

   You can infer the IP of your server from the ec2 name:

   
           ec2-54-221-126-53  -->  ( 54.221.126.53 )

   Register the derived ip address in the cloud db firewall rules.
5. JBoss Data Virtualization uses a model-driven approach. First, you will create a source model by connecting to the source and importing its structure.
   In Teiid Designer, open the Teiid Designer perspective. Then create a new Model Project by selecting File - New - Teiid Model Project. On the first wizard page, enter MyProject for the project name - then click Finish. The project will be created.
6. In Model Explorer, click MyProject, then Right-Click - Import... - JDBC Database - Source Model. Click Next.
7. In the Import Database via JDBC wizard, click the New... button to create a new Connection Profile. Select Generic JDBC for the type. Enter AzureCP for the Name. Click Next.
8. Next to the Drivers combo box, select the New Driver Definition icon to create a new driver. Select the Generic JDBC Driver template, then enter AzureDriver for the Name.
9. On the JAR List tab, click the Add JAR/Zip... button, then select a SQL Server type 4 driver jar that you've previously downloaded to your file system. Click OK to finish creating the Driver Definition.
10. For the connection, enter the general properties using your database name and so forth as provided in the cloud db connection string.
11. Enter the Optional properties from the connection string.
12. Click the Test Connection button to ensure a successful connection. Click Finish.
13. Continue in the JDBC import wizard, selecting the tables and so forth that you want to import. Choose a name for your source model (such as AzureSourceModel). Upon completion of the import wizard, the source model will be created within your model project.

Procedure 12.4. Previewing Data

1. In Designer, make sure your server is running.
2. Select a table, then click the 'running man' icon in the toolbar. This will display the content in your cloud database table.
3. You can also create more complex transformations using the source model that you just created: Create additional views which transform and join sources in any way you like.

1. Create an OpenShift user account.
2. Launch the OpenShift Web Console and go to the Applications page at https://openshift.redhat.com/app/console/applications
3. Go to the Applications tab and select Add Application...
4. Go to the xPaaS section and select the JBoss Data Virtualization cartridge.
5. Enter the name of the application (for example, "jbossdv").
6. If your account allows it, select a medium gear.
7. Click the Create Application button.
8. The Red hat JBoss Data Virtualization Cartridge will now deploy.

   Important

   Copy and save the username and password information somewhere secure for future use.
9. Click on Continue to the application overview page to see the Data Virtualization cartridge overview.
   Verify that the status is Started.
10. If you click on the application link you will see the Data Virtualization Welcome page. This page contains cartridge information and some helpful links.
11. After the cartridge has deployed, go to this address to check its status: http://[MYAPP]-[MYDOMAIN].rhcloud.com
    A user has been automatically generated with user, odata and rest roles.
12. Access ModeShape at http://[MYAPP]-[MYDOMAIN].rhcloud.com/modeshape-webdav and http://[MYAPP]-[MYDOMAIN].rhcloud.com/modeshape-rest
    Two ModeShape users, msuser and msadmin, are generated with the installation.
13. Access the Dashboard Builder at http://[MYAPP]-[MYDOMAIN].rhcloud.com/dashboard
    A dashboard administrator, dbadmin, is generated with the installation. (The Teiid 'user' is allowed dashboard read-only user access).

Procedure 13.1. Install a Box Grinder plug-in

1. Firstly, assign a MySQL database to your OpenShift Data Virtualization instance. Go to the overview page for your Data Virtualization application Click on the Add MySQL 5.5 link (found under the Databases section.)
   The MySQL cartridge will deploy. When complete, you will see a success screen

   Important

   Ensure that you save the credentials information for later reference.
2. Under Tools and Support, click on the Add phpMyAdmin 4.0 link. This adds the web interface for easy management of your MySQL database.
   The MySQL database and management interface deployments are now complete.
3. Load some data into the database using the phpMyAdmin interface. Use the link that was displayed when you installed the phpMyAdmin cartridge at https://myApp-myDomain.rhcloud.com/phpmyadmin
   Use the Root User and Root Password you received when the cartridge was installed.
   In the left tree panel, click on the database that matches the name of your DV application (for instance, jbossdv1). Select the SQL tab. On the SQL tab, copy this DDL and paste it into the text area:

   CREATE TABLE PricesTable  
   (  
     ProdCode    CHAR(40) NOT NULL,  
     SalePrice   DECIMAL,  
     PRIMARY KEY (ProdCode)  
   );  
     
   INSERT INTO PricesTable VALUES   
   ('GC1020', 3499.0),  
   ('GC1040', 19990.0),  
   ('GC1060', 75000.0),  
   ('GC3020', 10200.0),  
   ('GC3040', 38000.0),  
   ('GC3060', 95000.0),  
   ('GC5020', 28000.0),  
   ('GC5040', 59900.0),  
   ('GC5060', 110000.0),  
   ('IN7020', 4000.0),  
   ('IN7040', 16000.0),  
   ('IN7060', 42000.0),  
   ('IN7080', 69000.0),  
   ('SL9020', 4999.0),  
   ('SL9040', 9999.0),  
   ('SL9060', 14999.0),  
   ('SL9080', 19999.0); 
   

   Finally, click the GO button on the far right of the management interface.
   The PricesTable table has now been created and populated. You can verify the contents by clicking on it.
4. Restart the Data Virtualization cartridge. This is required to initialize the MySQL datasource. Click the Restart application icon on the application overview page
5. Go to http://www.developerforce.com/events/regular/registration.php?d=70130000000EjHb , to register for a Salesforce account. (You will receive an email with a link to login into your account.)
6. Log in to Salesforce interface with your user name an dpassword, then go to Personal Setup - Reset My Security Token. Reset the security token. You will get another email with the security token.
7. When you establish connectivity to the Salesforce instance in the example below, use the Salesforce username. (The password is the combination of Salesforce password and security token.)
8. go to the deployed Web interface on OpenShift at http://APP-NAME-DOMAIN-NAME.rhcloud.com/dv-ui. (APP-NAME is the name you gave the application and DOMAIN-NAME is your OpenShift domain name).
9. From the Data Library screen, click the Create Data Services link. You will be directed to the Create Data Service page.
10. Click on the Manage Sources button. You will be directed to the Manage Data Sources page
11. Click on the MySQLDS source: it is configured, but inactive. Select the mysql5 translator for the source and click the Save Changes button. Upon deployment, the source should become active (a green check mark will appear).
12. Click the Add Source button. This will create a default H2 source called MyNewSource.
13. Click on MyNewSource.
    In the displayed properties, enter SalesforceDS for the Name, Under Source Type, click on the salesforce button. Click the Ok button as this will change the source to salesforce type and set the translator to salesforce. Under Connection Properties, enter the user name for your salesforce account. Enter the password and token combination for the password.
14. Click on the Save Changes button. Click Ok for each dialog box. The salesforce source will deploy (it will take a couple of minutes to finish).
15. Click the back link to go back to the Create Data Service page
16. The next phase is to carete a data service which accesses the MySQL database table. Enter MySQLService for the service name. Enter a description for the service.
17. Click on MySQLDS on the Service Helpers Active Sources tab.
18. Click on the dv61.PricesTable under Tables, then select both columns via the checkboxes.
19. To create the Service View Definition, click the Create Service View button. This will populate the Service View Definition text area.
20. Click the Test Service button to test the service.
21. Click Create Data Service. This will accept your entries and create the service. You will be redirected to the Data Service Details page.
22. The steps to create a salesforce-only service follow the same pattern. Go back to the Data Library then click the Create Data Service button to create a new service.
23. Enter SalesforceProductService for the service name. Enter a description for the service.
24. Click on SalesforceDS on the Service Helpers Active Sources tab
25. Click on Product2 under Tables, then select the Name and ProductCode columns via the checkboxes.
26. To create the Service view definition, click the Create Service View button. This will populate the Service View Definition text area.
27. Test the service as before to see sample data, the click Create Service to create the service.
28. The steps to create a mashup service once more follow the same pattern. Go back to the Data Library then click the Create Data Service button to create a new service.
29. Enter MashupService for the service name. Enter a description for the service.
30. In the Service Helpers section, click on the Join Definition tab. (It is here that you define the join.)
31. Select MySQLDS in the Available Sources drop-down. Under Source Tables, click the PricesTable. Then click the left-hand button to specify it as the Left table.
32. Select SalesforceDS in the Available Sources drop-down. Under Source Tables, click the Product2 table. Then click the right-hand button to specify it as the Right table.
33. In the left-hand side Prices table, check the ProdCode and SalePrice columns. In the right-hand side Product2 table, check the Name column.
34. Leave the JoinType selection on Inner Join.
35. Select ProdCode for the left-hand side Join Criteria column.
36. Select ProductCode for the right-hand side Join Criteria column.
37. Click the Apply button to generate the Service Definition DDL.
38. Click the Test Service button to see example data.
39. Click the Create Service button to create the Mashup service. You will be redirected to the Data Service Details page. The Data Service Details page shows a sample of data and also provides connection instructions and URLs for the different connection options.
40. Click the Back to Library link to go back to your Data Library. On the Data Library page you will see the three services that you just created.

    Note

    Notice that for each service, there are more actions available to you:

    • Edit Service - redirects to the Edit Data Service page.
    • Duplicate Service - makes a copy of the selected service.
    • Test Service - redirects to the Data Service Details page.
    • Delete Service - delete the selected service.
    • Save to File - A service is backed by a teiid 'Dynamic VDB'. This action saves the dynamic VDB xml to a file.