Procedure 3.1. Log in and Download Files from the Red Hat Customer Portal

1. Browse to https://access.redhat.com and click the Log in link in the top right corner. Enter your credentials and click Log In.
   Result

   You are logged into RHN and you are returned to the main web page at https://access.redhat.com.

2. Navigate to the Downloads page.

   Use one of the following options to navigate to the Downloads page.
   • Click the Downloads link in the top navigation bar.
   • Navigate directly to https://access.redhat.com/downloads/.

3. Select the product and version to download.

   Use one of the following ways to choose the correct product and version to download.
   • Step through the navigation one level at a time.
   • Search for your product using the search area at the top right-hand side of the screen.

4. Download the appropriate file for your operating system and installation method of choice.

   Depending on the product you choose, you may have the choice of a Zip archive, RPM, or native installer for a specific operating system and architecture. Click either the file name or the Download link to the right of the file you want to download.

Procedure 3.2. Verify File Checksums on Red Hat Enterprise Linux

1. Obtain checksum values for the downloaded file

   1. Navigate to https://access.redhat.com/jbossnetwork/. Login if required.
   2. Select your Product and Version.
   3. Select the package you want to verify to 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 sha256sum downloaded_file.
   Example output:

   [localhost]$ md5sum downloaded_file
   4564d1a5190110dbe8170e50d7353a97  downloaded_file
   [localhost]$ sha256sum downloaded_file
   25b6bd3c5f47b316639b014d041cdb6a515e3a4a32d30a479141cd8ceecb853e  downloaded_file

3. Compare the checksum values

   1. Compare the checksum values returned by the md5sum and sha256sum 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 JBoss Fuse Service Works

1. Open a new terminal and navigate to the folder where you have downloaded the JBoss Fuse Service Works installer file.
2. Run the following command, replacing 6.0.0.GA-redhat-4 for the version you downloaded if required:

   java -jar jboss-fsw-installer-6.0.0.GA-redhat-4.jar

3. You are presented with the End User License Agreement. If you agree with the terms, select I accept the terms of this license agreement and then select Next to continue.
4. You are prompted for the location in which you want to install JBoss Fuse Service Works. Specify a location and select Next. You will be notified that an instance of JBoss EAP will be placed in the chosen location. Select OK to proceed.

   Warning

   A warning message is displayed if the directory already exists. Red Hat does not recommend installing over the top of an existing installation. However, if you wish to proceed, select Yes to continue.
5. You are prompted for the installation packs to install. Select Next to continue with the default options.

   Note

   Depending on your deployment, you can select packs other than the default options. For example, if you do not wish to install every pack, you could select SwitchYard and Runtime Governance Client only, for a basic installation.
6. You are prompted to create an administrative user. Once created, this user will be added to the ManagementRealm and can be used to access the Management Console and other applications secured using ManagementRealm. Enter the new username and password in the appropriate fields and select Next.
7. You are prompted to create a governance user. It will give you access to S-RAMP, DTGov and RTGov consoles along with the S-RAMP Command Line Interface. Enter a username and password and select Next.
8. You are then prompted to setup your Maven repository. This will enable you to build the quickstarts provided. Specify the location of an existing or new location for your Maven settings file (typically ~/.m2/settings.xml). If you do not currently have a settings file, a new settings.xml file will be created for you in the location you provide. Select Next.

   Note

   If you choose to skip the maven repository setup, you will be asked to confirm this decision. Select Yes to continue.
9. You are prompted to configure the SAML keystore. It is used by a Java KeyStore to sign authentication tokens. Enter the SAML keystore password and select Next.
10. You are then prompted to enable the Java Security Manager. It enforces access rules at the JVM runtime based on one or more security polices. Select Next when you are ready to proceed.

    Important

    Enabling the Java Security Manager may reduce server performance.
11. At this point you are asked to choose between the default or advanced configuration. Select the default configuration for a basic configuration, and select Next to continue.
12. You are prompted to configure the password vault. Enter the Vault keystore password in the appropriate fields and select Next.
13. You are presented with a screen specifying default database settings. The installer creates a database that is used to hold data for various components of JBoss Fuse Service Works, including BPEL, jBPM and S-RAMP.
    Change the username and password to something secure and select Next to continue.

    Warning

    The default database is an H2 database. Red Hat recommends configuring an alternative database for production systems, using the advanced configuration options.
14. You are presented with a list of packages that will be installed. Select Next to proceed.
15. The installation will commence. A status bar for each component will display its progress. Once this is complete, select Next.
16. Additional processing of tasks will commence. When the status bar indicates this has been completed, select Next.
17. The console displays a message to let you know that the application has been successfully installed. Also, it offers you a list of URLs for accessing the Administration and BPEL Consoles, S-RAMP and DTGov User Interfaces and Gadget Server.
    If you want to repeat the same installation on other machines, select Generate installation script and properties file and choose a location and filename for the script.
18. Select Done.

Procedure 4.3. 

1. You can change the installation directory by editing the script and modifying the value specified within the <installpath> element.

   Note

   You can specify either a full directory path or a path relative to the directory in which you run the script.

   Warning

   Red Hat does not support installing over an existing instance of Fuse Service Works. Therefore be sure to select a new or empty directory.
2. Run the script using the following command, replacing 6.0.0.GA-redhat-4 for the version you downloaded if required:

   java -jar jboss-fsw-installer-6.0.0.GA-redhat-4.jar InstallConfigRecord.xml

   The script runs and prompts you to provide Governance, SAML keystore, and Vault keystore passwords, as shown below:

   [ Starting automated installation ]
   Read pack list from xml definition.
   Try to add to selection [Name: Red Hat JBoss Enterprise Application Platform and Index: 0]
   Try to add to selection [Name: Red Hat JBoss Fuse Service Works and Index: 1]
   Try to add to selection [Name: Switchyard quickstarts and Index: 2]
   Try to remove from selection [Name: RT-Gov Client-only and Index: 3]
   Try to add to selection [Name: RT-Gov Server+Client and Index: 4]
   Try to add to selection [Name: RTGov Server quickstarts and Index: 5]
   Try to add to selection [Name: DT-Gov run-time and Index: 6]
   Try to add to selection [Name: DT-Gov quickstarts and Index: 7]
   Try to add to selection [Name: S-RAMP run-time and Index: 8]
   Try to add to selection [Name: S-RAMP quickstarts and Index: 9]
   Try to add to selection [Name: Red Hat JBoss Fuse Service Works quickstarts and Index: 10]
   Modify pack selection.
   Pack [Name: RT-Gov Client-only and Index: 3] removed from selection.
   Governance password:
   Confirm Governance password:
   SAML keystore password:
   Re-enter SAML keystore password:
   Vault keystore password:
   Re-enter vault keystore password:

Procedure 5.1. Start the Platform Service as a Standalone Server

1. For Red Hat Enterprise Linux.

   Run the command: EAP_HOME/bin/standalone.sh

2. For Microsoft Windows Server.

   Run the command: EAP_HOME\bin\standalone.bat

3. Optional: Specify additional parameters.

   To print a list of additional parameters to pass to the start-up scripts, use the -h parameter.

1. Stopping JBoss Enterprise Application Platform using the Management CLI.

   • Run the EAP_HOME/bin/jboss-cli.sh command to launch the Management CLI.

     $ EAP_HOME/bin/jboss-cli.sh

   • Run the connect command to connect to the server.

     [disconnected /] connect

   • Run the shutdown command to stop the server.

     [standalone@localhost:9999 /] shutdown

   • Run the quit command to close the Management CLI.

     [standalone@localhost:9999 /] quit

2. Stopping JBoss Enterprise Application Platform by pressing CTRL+C.

   Press Ctrl+C in the server window (the terminal window where JBoss Enterprise Application Platform was started).
   Result

   Each of these alternatives stops JBoss Enterprise Application Platform.

Procedure 6.1. 

1. Download the following ZIP archives containing the required repositories:
   • http://maven.repository.redhat.com/techpreview/fsw6/6.0.0/fsw-6.0.0.GA-redhat-2-repository.zip
   • http://maven.repository.redhat.com/techpreview/eap6/6.1.1/jboss-eap-6.1.1-maven-repository.zip

   Note

   Alternatively, the ZIP archives can be downloaded from http://access.redhat.com/jbossnetwork/.
2. Unzip the downloaded ZIP files into an arbitrary location in a local file system.
3. 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 Fuse Service Works -->
       <profile>
         <id>fsw-local-repos</id>
         <repositories>
           <repository>
             <id>fsw-6.0.0.GA-redhat-2-repository</id>
             <name>FSW 6.0.0.GA Repository</name>
             <url>file://<!-- path to the repository -->/fsw-6.0.0.GA-redhat-2-repository</url>
             <layout>default</layout>
             <releases>
               <enabled>true</enabled>
               <updatePolicy>never</updatePolicy>
             </releases>
             <snapshots>
               <enabled>false</enabled>
               <updatePolicy>never</updatePolicy>
             </snapshots>
           </repository>
           <repository>
             <id>jboss-eap-6.1.1.GA-maven-repository</id>
             <name>EAP 6.1.1.GA Repository</name>
             <url>file://<!-- path to the repository -->/jboss-eap-6.1.1.GA-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>fsw-6.0.0.GA-redhat-2-repository</id>
             <name>FSW 6.0.0.GA Repository</name>
             <url>file://<!-- path to the repository -->/fsw-6.0.0.GA-redhat-2-repository</url>
             <layout>default</layout>
             <releases>
               <enabled>true</enabled>
               <updatePolicy>never</updatePolicy>
             </releases>
             <snapshots>
               <enabled>false</enabled>
               <updatePolicy>never</updatePolicy>
             </snapshots>
           </pluginRepository>
           <pluginRepository>
             <id>jboss-eap-6.1.1.GA-maven-repository</id>
             <name>EAP 6.1.1 GA Repository</name>
             <url>file://<!-- path to the repository -->/jboss-eap-6.1.1.GA-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 Fuse Service Works profile -->
      <activeProfile>fsw-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 as in the code sample below:

   <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 Fuse Service Works -->
       <profile>
         <id>fsw-online-repos</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>
           <repository>
             <id>jboss-public-repository</id>
             <url>http://repository.jboss.org/nexus/content/repositories/public/</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>
           <pluginRepository>
             <id>jboss-public-plugin-repository</id>
             <url>http://repository.jboss.org/nexus/content/repositories/public/</url>
             <releases>
               <enabled>true</enabled>
             </releases>
             <snapshots>
               <enabled>false</enabled>
             </snapshots>
           </pluginRepository>
         </pluginRepositories>
       </profile>    
     </profiles>
   
     <activeProfiles>
       <!-- Activation of the Fuse Service Works profile -->
       <activeProfile>fsw-online-repos</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.2. Update Maven User Settings

Procedure 7.1. Install with the Universal Installer

1. Log into the Customer Portal at https://access.redhat.com.
2. From the menu bar click Downloads.
3. Under Red Hat JBoss Middleware, click Download Software.
   

   Figure 7.1. Download Red Hat JBoss Middleware Software on the Customer Portal

4. Under Software Downloads, select the following options:
   • From the Product list, select JBoss Developer Studio.
   • From the Version list, select 7.1.x.
5. • For the JBoss Developer Studio universal installer, click Download for the Red Hat JBoss Developer Studio 7.1.x Stand Alone Universal Binary download file.
   • For the JBoss Developer Studio and JBoss EAP universal installer, click Download for the Red Hat JBoss Developer Studio 7.1.x Universal Binary with JBoss EAP download file.
   This downloads a universal installer .jar file.
6. On the command line, navigate to path/to/.jar and enter

   java -jar jbdevstudio-product-universal-version.jar

   where version is substituted to match the name of the .jar file.

   Note

   Alternatively, to start the installer you may be able to double-click the .jar file.
7. When the Installer window opens, click Next.
8. After reading and agreeing to the terms of the End User License Agreement, click I accept the terms of this license agreement and click Next.
9. In the Select the installation path field, type the path where you want JBoss Developer Studio to be installed or click Browse to navigate to the location. When the Select the installation path field shows the correct path, click Next. When you are prompted about the specified location being created or overwritten, review the message and, if satisfied, click OK or Yes as appropriate.
   

   Figure 7.2. Installation Step 3: Select Target Folder

10. In the Select Java VM step, Default Java VM is automatically selected. Ensure that the disabled text field contains the path of the Java developer kit you want to use. This is based on the default Java developer kit of your system. To change the specified Java developer kit, click Specific Java VM and type the path of the Java developer kit in the text field or use the Browse button to locate the Java developer kit. When the text field shows the correct Java developer kit path, click Next.

    Important

    You must specify a Java developer kit with a 32-bit JRE to install a 32-bit version of JBoss Developer Studio and a 64-bit JRE to install a 64-bit version of JBoss Developer Studio. To change the bit version of the Java developer kit to be used for installing JBoss Developer Studio, complete the appropriate step for your operating system:

    • On OS X operating systems, from the Installation type list click the appropriate bit version.
    • On Linux distributions and Microsoft Windows operating systems, in the text field type the path to the appropriate bit version of the Java developer kit.
    

    Figure 7.3. Installation Step 4: Select Java VM

11. Review the details in the Summary Information window and, if they are correct, click Next. Installation commences.
12. When the Pack installation progress bar shows Finished, click Next. The installation process is now complete.
    

    Figure 7.4. Installation Step 7: Installation Progress in Finished State

13. To create shortcuts for starting JBoss Developer Studio, select the Create shortcuts in the Start-Menu and Create additional shortcut on the desktop check boxes and click Next.
14. To automatically start JBoss Developer Studio when the Installer window closes, select the Run JBoss Developer Studio after installation check box. Click Done to close the Installer window.

Procedure 7.2. Install JBoss Developer Studio Integration Stack

1. Start JBoss Developer Studio.
2. In JBoss Central, select the Software/Update tab. Scroll through the list to locate JBoss Developer Studio Integration Stack. Select the check box next to JBoss Integration and SOA Development and click Install.
   

   Figure 7.5. Find JBoss Developer Studio Integration Stack in JBoss Central Software/Update Tab

3. In the Install wizard, ensure the check boxes are selected for the software you want to install and click Next. It is recommended that you install all of the selected components.
4. Review the details of the items listed for install and click Next. After reading and agreeing to the license(s), click I accept the terms of the license agreement(s) and click Finish. The Installing Software window opens and reports the progress of the installation.
5. During the installation process you may receive warnings about installing unsigned content. If this is the case, check the details of the content and if satisfied click OK to continue with the installation.
   

   Figure 7.6. Warning Prompt for Installing Unsigned Content

6. Once installing is complete, you are prompted to restart the IDE. Click Yes to restart now and No if you need to save any unsaved changes to open projects. Note that changes do not take effect until the IDE is restarted.