Chapter 3. Installing Red Hat JBoss Data Virtualization 3.1. Graphical Installation The Graphical Installer allows you to install JBoss Data Virtualization on your machine using step-by-step GUI instructions. Prerequisites You must have already downloaded the Red Hat JBoss Data Virtualization jar file from the Customer Portal . Procedure 3.1. Install JBoss Data Virtualization Open a terminal window and navigate to the location where the GUI installer was downloaded. Launch the GUI installer: 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 . 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 . 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 . 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 . 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. 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 . The Configure password vault screen appears. Input your desired password, which must have no fewer than six characters. Click . Note The default H2 database used to store this data is not suitable for production systems. Use it in testing and evaluation environments only. 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 . A summary of the installation is displayed. Click for the installation to commence. This may take a few moments. Once all the components are installed, click . 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. Click Done to exit the installer. Note After installing JBoss Data Virtualization, if you move the product to another location, you may see some FileNotFound exceptions. This is because some file paths are hard-coded by the JBoss EAP Server. Warning If you attempt to use a vault with a keystore created with a different JDK than the one in which the data is stored, your server will fail to start. You must consistently use the same JDK when accessing the vault. Table 3.1. Other Installation Options Option Description Check to use one password for all default passwords. Allows you to use the default EAP password you create for all of the accounts. Add a security domain. If you select this option, the name of the field is mandatory. You can choose between a default and an Infinispan cache type and an authentication module for additional security. You can also add mapping elements to establish roles and credentials. You can also configure a JSSE element using either a keystore or a truststore. Install JDBC Driver. The JDBC driver converts application code to the relevant database language. Point to the location of your driver in the address field. You can add more than one. Configure audit/command logging. You can activate the logging level for the software to provide audit trails. Configure JAVA_OPTS. Configure additional Java options to override the normal defaults for both standalone and domain mode. Input the options you want in the provided fields. Enable SSL security. Generate a new keystore or point to an existing one. (The existing location should be that of your SSL certification file.) Add a security domain. Adds the server to a secure domain.

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