1. Section 1.1.2, “Installing Red Hat Container Development Kit and JBoss Developer Studio Using the Red Hat Development Suite Installer”
2. Section 1.1.3, “Installing Red Hat Container Development Kit and JBoss Developer Studio as Separate Entities”

1. Create a new OpenShift Container Platform project. These projects are like namespaces for OpenShift applications. They are different from how Eclipse projects relate to Eclipse applications. Additionally, Eclipse projects can be mapped to OpenShift applications.

   1. In the OpenShift Explorer view, right-click the name of the connection and select New > Project to create a new OpenShift Container Platform project.

      Note

      The CDK server adapter creates the OpenShift Container Platform connection when you start the CDK server adapter in the preceding sections.

   2. Add the name and any other relevant details for the new project and click Finish.

2. Create an application in your OpenShift Container Platform project using the templates:

   1. Right-click your new project name and click New > Application.
   2. In the Select Template dialog box, search box, type the application type required. For example, for a node.js application, type nodejs and from the displayed list, select the relevant nodejs template and click Finish.
   3. Click OK to accept the results of the application creation process.
   4. When prompted, enter a new git location or click Finish in the dialog box to use the listed default git location for your application.

3. Create a new OpenShift Container Platform server adapter for your project and application:

   1. In the OpenShift Explorer view, expand the connection and then the project.
   2. Right-click the service and click Server Adapter.

   3. In the OpenShift Adapter Settings window:

      1. Ensure that the Eclipse Project field, shows the relevant project or click Browse to locate the project.
      2. In the Services field, select the relevant service.
      3. Click Finish.

4. Debug the application, if required.

   1. In the Servers view, right-click the server adapter and click Restart in Debug.

1. In the OpenShift Explorer view, click New Connection Wizard. If the OpenShift Explorer view is not available, click Window → Show View → Other and then in the Show View window search for OpenShift Explorer and after you find it, click OK.

2. In the New OpenShift Connection wizard:

   1. In the Connection list, click <New Connection>.
   2. In the Server type list, click OpenShift 3.
   3. In the Server field, type the URL for an OpenShift Container Platform server.
   4. In the Authentication section, in the Protocol list, click OAuth to authenticate using the token or click Basic to authenticate using login credentials.
3. Click Finish.

1. In the OpenShift Explorer view, right-click the connection and click New → Project.

2. In the Create OpenShift Project window:

   1. In the Project Name field, type a name for the project. Project names must be alphanumeric and can contain the character “-” but must not begin or end with this character.
   2. In the Display Name field, type a display name for the project. This name is used as the display name for your project in the OpenShift Explorer view and on the OpenShift Container Platform web console after the project is created.
   3. In the Description field, type a description of the project.
3. Click Finish.

1. In the OpenShift Explorer view, right-click the connection and click New → Application.
2. If required, in the New OpenShift Application wizard, sign into your OpenShift Container Platform server using the Basic protocol (username and password) or the OAuth protocol (token) and click Next.

3. In the Select Template window, click the Server application source tab.

   Note

   To create an application from the a local template, click the Local template tab and then click Browse File System or Browse Workspace to locate the template that you want to base the project on.

4. From the list, click the template that you want to base your project on. You can also use the type filter text field to search for specific templates.

5. Click Next.

   Figure 2.2. Select a Template for Project Creation

   
6. In the Template Parameters window, confirm the parameter values and click Next.
7. In the Resource Labels window, confirm the labels that you want to add to each resource. You can also click Add or Edit to add labels or edit the existing ones.
8. Click Finish.
9. In the Results of creating the resources from the [template_name] window, review the details and click OK.

10. In the Import Application window, click Use default clone destination to clone the application at the default location or in the Git Clone Location field, type or browse for the location where you want to clone the application and click Finish.

    Figure 2.3. Select a Git Clone Location

    
    Note

    If the Git location chosen to clone the application already contains a folder with the application name that you are trying to import, you must select a new location for the Git clone. If you do not select a new location, the existing repository will be reused with the changes you made being retained but not reflected on the OpenShift Container Platform console.

    Figure 2.4. Git Clone Location Reuse

    

1. If required, sign into your OpenShift Container Platform server using the Basic protocol or the OAuth protocol.
2. In the OpenShift Explorer view, expand the connection to locate the application to import.

3. Right-click {project name} and click Import Application.

   Note

   To import a particular application from a service, right-click the service and then click Import Application. If you right-click a project and click Import Application, and if there are more than one build configs with source code under a project, you will be prompted to select the desired application for import because of existence of several applications under one project.

4. In the Import OpenShift Application wizard, Existing Build Configs list, click the application that you want to import and click Next.
5. Ensure the location in the Git Clone Destination field corresponds to where you want to make a local copy of the application Git repository and click Finish.

1. In the OpenShift Explorer view, expand the connection, the project, and then the application.

2. Right-click the and click Server Adapter. In the Server Settings window, Services section, select the service.

   Note

   A workspace project will be selected automatically, if the OpenShift service has a Build Config with a git URL matching the git remote URL of one of the workspace projects.

3. Click Finish.

1. In the OpenShift Explorer view, expand the connection and then the project to locate the application you want to delete.
2. Right-click {project name} and click Delete Project.
3. In the OpenShift resource deletion window, click OK.

1. In the IDE, click Windows > Preferences > JBoss Tools > OpenShift v3.
2. Click the here link.
3. In the Download from GitHub section, click the Release page link.
4. Scroll to the Downloads section and click the appropriate link to begin the client tools download for the binary for your operating system.
5. After the download is complete, extract the contents of the file.
6. Click Windows > Preferences > JBoss Tools > OpenShift v3.
7. Click Browse and select the location of the OpenShift Client executable file.
8. Click Apply and then click OK.

1. In the OpenShift Explorer view, expand the connection and then expand the project, the services, and then the Pods.

2. Right-click the relevant pod and then click Port Forwarding.

   Figure 2.6. Set up Port Forwarding

   
3. In the Application Port Forwarding window, click the Find free local ports for remote ports check box.
4. Click Start All.

1. In the OpenShift Explorer view, expand the project, the services, and then the Pods.
2. Right-click the relevant Pod and then click Pod Log.

1. In the OpenShift Explorer view, expand the project, the services, and then the build.
2. Right-click the relevant build instance and click Build Log.

1. Install nmp: Before running JBoss Developer Studio, install npm on your system. See the npm documentation for instructions for various platforms: https://docs.npmjs.com/getting-started/what-is-npm.
2. Download and install JDK 8.

3. Install JBoss Developer Studio and Red Hat Container Development Kit.

   1. On a Windows system: Install Red Hat Development Suite to automatically install both: JBoss Developer Studio and Red Hat Container Development Kit (for installation instructions, see https://access.redhat.com/documentation/en/red-hat-development-suite/1.1/paged/installation-guide/).
   2. On other operating systems: Install JBoss Developer Studio (for installation instructions, see: https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/10.1/paged/installation-guide/) and install Red Hat Container Development Kit (for installation instructions, see https://access.redhat.com/documentation/en/red-hat-container-development-kit/2.2/paged/installation-guide/).

4. Clone the following projects and then import them into JBoss Developer Studio using the Import wizard (from File > Open Projects from File System).

   1. bonjour project from: https://github.com/redhat-helloworld-msa/bonjour
   2. frontend project from: https://github.com/redhat-helloworld-msa/frontend
5. Set up the oc client binaries in the IDE from Window > Preferences, expand JBoss Tools, and then click OpenShift 3.

1. In the Project Explorer view, expand frontend and right-click package.json.
2. Click Run As > npm Install to download and install the required javascript modules in the project.

1. In the Project Explorer view, expand frontend and right-click Dockerfile and then click Run As > Docker Image Build.

2. In the Docker Image Build Configuration window:

   1. In the Connection list, select Container Development Environment.
   2. In the Repository Name field, type demo/frontend.
3. Click OK.

1. In the Project Explorer view, expand bonjour and right-click package.json.
2. Click Run As > npm Install.
3. In the Project Explorer view, expand bonjour and right-click Dockerfile.
4. Click Run As > Docker Image Build.

5. In the Docker Image Build Configuration window:

   1. In the Connectio*n list, select *Container Development Environment.
   2. In the Repository Name field, type demo/bonjour.
6. Click OK.

1. In the Project Explorer view, expand bonjour, and double-click bonjour.js to open it in the default editor.

2. Find

   function say_bonjour(){
       Return “Bonjour de “ + os.hostname();

3. Change it to:

       function say_bonjour(){
       Return “Salut de “ + os.hostname();

4. Save the file.

1. In JBoss Central, under Start from scratch, click OpenShift Application.

1. Click the link provided to sign up for an OpenShift account and follow the instructions on the OpenShift website.

   Figure 3.1. Link to Sign up for a New OpenShift Online User Account

   
2. When you have completed the sign-up process, restart the OpenShift Application wizard from JBoss Central.

1. Complete the fields about your OpenShift Online account as follows:

   1. From the Connection list, select New Connection.
   2. Ensure the disabled Server field states https://openshift.redhat.com.

   3. In the Username and Password fields, type your account credentials.

      Figure 3.2. Connection Information Provided for OpenShift Online Account

      
2. Click Next.

1. Click New.

2. Complete the fields about the SSH Keys to be created as follows:

   1. In the Name field, type a name for the SSH key pair.
   2. From the Key Type list, ensure SSH_RSA is selected.
   3. In the SSH2 Home field, ensure your .ssh directory path is correct.

   4. In the Private Key File Name field, type a name for the private key file name. The Public Key File Name field populates automatically with the name of the private key file name with .pub appended.

      Figure 3.3. New SSH Key Information for OpenShift Online Provided

      
3. Click Finish.
4. Click Finish to close the Add SSH Keys window.

1. In the Domain Name field, type an alphanumeric name for your new OpenShift Online domain and click Finish. The provided domain name must be unique across all domains on OpenShift Online; if it is not unique, you are directed back to the Create Domain window to provide a unique domain name.

   Figure 3.4. New OpenShift Domain Name Provided

   

1. Complete the fields about the type of OpenShift application you want to create as follows:

   1. Ensure Create a new OpenShift application is selected.

   2. Expand Basic Cartridges and select JBoss Application Server 7.

      Figure 3.5. Basic Cartridge Selected for the New OpenShift Online Application

      
2. Click Next.

3. Complete the fields about your OpenShift application as follows:

   1. Ensure the Domain field displays the OpenShift Online domain with which you want to host your application.
   2. In the Name field, type an alphanumeric name for your application.
   3. From the Gear profile list, select small.

   4. Select the Enable scaling check box.

      Figure 3.6. New OpenShift Application Information Provided

      
4. Click Next.

1. Complete the fields about the corresponding workspace project as follows:

   1. Ensure the Create a new project check box is selected.
   2. Ensure the Create and set up a server for easy publishing check box is selected. This automatically creates an OpenShift server adapter for the application, enabling you to easily publish project changes to the OpenShift server.
2. Click Next.

3. Ensure the location in the Git Clone Destination field corresponds to where you want to make a local git repository for the project source code.

   Figure 3.7. Git Clone Destination Specified

   

18. Click Finish for the wizard to start generating the new OpenShift application. This process may take some time to complete.
19. If you are prompted that the authenticity of the host cannot be established and asked whether you want to continue connecting, ensure that the host name matches that of your application and domain and click Yes.

20. In the OpenShift Explorer view, expand the connection and domain.
21. Right-click {application name} and click Show In → Web Browser.

1. In the OpenShift Explorer view, ensure your OpenShift Online connection is listed or click the Connection icon and complete your OpenShift Online account details to create a new connection.
2. In the OpenShift Explorer view, expand the connection and domain to locate the application you want to import.
3. Right-click {application name} and click Import Application.

4. Complete the fields about the application to be imported as follows:

   1. Ensure that Use my existing OpenShift application is selected.

   2. Ensure that the name of the application you want to import is listed. If this is not the case, type the name of the application or click Browse to select the application.

      Figure 3.8. Existing OpenShift Online Application Information Provided

      
5. Click Next.

6. Complete the fields about the corresponding new workspace project as follows:

   1. Ensure the Create a new project check box is selected.
   2. Ensure the Create and set up a server adapter for easy publishing check box is selected.
7. Click Next.
8. Ensure the location in the Git Clone Destination field corresponds to where you want to make a local copy of the OpenShift Online application Git repository.
9. Ensure a public SSH key is uploaded to OpenShift Online and private key location is specified in the IDE preferences by clicking SSH Keys Wizard and reviewing the information.
10. Click Finish.

1. In the Project Explorer view, expand {project name} → src → main → webapp.
2. Double-click index.html to open it in the JBoss Tools HTML Editor.

3. After the opening <body> tag add the following line:

   <h1>This is a change made to my OpenShift Online app from the IDE.</h1>

4. Save the index.html file by pressing Ctrl+S (or Cmd+S).

1. In the Servers view, right-click {application name} at OpenShift and click Publish. Or you can drag the from the Project Explorer view and drop it on the server adapter in the Servers view.

2. Complete the fields about the project changes to commit and push to the OpenShift Online application Git repository as follows:

   1. In the Commit message field, type the following message

      Added new heading in body of index.html

   2. In the table of files, ensure the index.html file is selected.

      Figure 3.9. Commit Message Provided and Changed Project File Selected

      
3. Click Commit and Publish.

1. In the OpenShift Explorer view, expand the connection and the domain.
2. Right-click {application name} and click Show In → Web Browser.

1. In the Project Explorer view, right-click {project name} and click OpenShift → Configure Markers.

2. From the Marker table, select Hot Deploy and click OK.

   Figure 3.10. Hot Deploy Marker Selected

   

   An empty .openshift/markers/hot_deploy file is added to the application. OpenShift Tools automatically completes the git add action so that this new file is added to the Git index and can be committed and pushed to the OpenShift application repository when ready.

Create the post deploy action hook

1. In the Navigator view, expand {project name} → .openshift.
2. Right-click action_hooks and click New → File.
3. In the File name field, type post_deploy and click Finish.

4. In the file editor, add the following lines to the post_deploy file:

   #!/bin/bash
   echo "This is my post-deploy bash script”

5. Save the file by pressing Ctrl+S (or Cmd+S).

Make the post deploy action hook executable

6. In the Navigator view, right-click the post_deploy file and click Properties.

7. In the Permissions table, select the Execute check boxes for all user types.

   Figure 3.11. Execute Permissions Check Boxes Selected for All Users

   
8. Click Apply and click OK.

1. Click Window → Preferences → Team → Git.

2. In the Remote connection timeout (seconds) field, type a value in seconds.

   Figure 3.12. Git Remote Connection Timeout Set

   
3. Click Apply and click OK to close the Preferences window.

1. In the Servers view, right-click {application name} at OpenShift and click Publish.

2. Complete the fields about the application changes to commit and push to the OpenShift Online application repository as follows:

   1. In the Commit message field, type the following message:

      Added hot_deploy marker and post_deploy bash script

   2. In the Files table, ensure the hot_deploy file is selected and select the post_deploy file.

      Figure 3.13. Commit Message Supplied and Files Selected for Committing and Publishing

      
3. Click Commit and Publish.

1. In the Project Explorer view, right-click {project name} and click OpenShift → Configure Markers.

2. In the Configure OpenShift Markers window, select the Enable JPDA check box and click OK.

   Figure 3.14. OpenShift Enable JPDA Marker Selected

   
3. In the Servers view, right-click {application name} at OpenShift and click Publish.
4. In the Publish Changes window, in the Commit message field type a message for the commit.
5. From the Files list, ensure the .openshift/markers/enable_jpda check box is selected and click Commit and Publish.

1. In the OpenShift Explorer view, right-click {application name} and click Port Forwarding.

2. In the Application port forwarding window, click Start All. Ensure the Status value shows Started for the debug ports and click OK to close the Application port forwarding window.

   Figure 3.15. Port Forwarding Started for All Ports

   

1. In the global toolbar of the JBoss perspective, click the drop-down list for the Debug icon and select Debug Configurations.
2. From the debug configurations list, select Remote Java Application and click the New launch configuration icon

3. In the Connect tab, complete the following fields:

   1. In the Project field, type the name of the workspace project associated with the OpenShift application or click Browse to locate the project.
   2. In the Port field, type the value of the debug port.

   3. Click Apply and then click Debug.

      Figure 3.16. Debug Configuration Ready for Your OpenShift Application

      

1. In the Project Explorer, right-click {project name} and click Configure → New/Import OpenShift Application.

2. Complete the fields about your OpenShift Online account as follows:

   1. In the Connection list, select the connection.
   2. In the Password field, type your OpenShift Online account password.
3. Click Next.

4. Complete the fields about the type of OpenShift application you want to create as follows:

   1. Ensure Create a new OpenShift application is selected.
   2. Expand Basic Cartridges and select the core cartridge to match the application type; for example, for applications with Java-based server-side functionality select jbossas-7, jboss-wildfly-8, or jbosseap-6.
5. Click Next.

6. Complete the fields about your OpenShift application as follows:

   1. Ensure that the 'Domain' list displays the domain in which you want to host your application.
   2. Ensure the Name field contains a valid alphanumeric name for your application.
   3. In the Gear profile field, select the gear size that you want for your application or leave blank to use the default gear profile.
   4. Select the Enable Scaling check box to make your application scalable.
7. Click Next.

8. Complete the fields about the corresponding workspace project as follows:

   1. Ensure the Create a new project check box is clear.
   2. Ensure the Use existing project field lists the workspace project that you want to deploy on OpenShift.

   3. Ensure the Create and set up a server adapter for easy publishing check box is selected.

      Figure 3.17. Existing Workspace Project Selected for the New OpenShift Application

      
9. Click Next.
10. Ensure the location in the Git Clone Destination field exists and corresponds to where you want to make a local git repository for the project source code.
11. Ensure a public SSH key is uploaded to OpenShift Online and private key location specified in the IDE preferences by clicking SSH Keys wizard and reviewing the information.
12. Click Finish.
13. At the prompt informing that changes will be made to the workspace project, click OK.

1. In the Servers view, right-click {application name} at OpenShift and click Full Publish.
2. When prompted if you want to publish the committed project changes to OpenShift, click Yes.

1. In the OpenShift Explorer view, expand the connection and the domain.
2. Right-click {application name} and click Show In → Web Browser.

1. In the OpenShift Explorer view, right-click the connection and click Manage SSH Keys.
2. In the Manage SSH Keys wizard, click New.

3. Complete the fields about the new SSH keys as follows:

   • In the Name field, type a name to distinguish the key pair from any other keys associated with the connection.
   • From the Key Type list, select SSH_RSA.
   • Ensure that the SSH2 Home field contains the location where you want to create the files associated with the key pair. To change the location, clear the Default check box and type the location in the SSH2 Home field or click Browse to navigate to the desired location.

   • In the Private Key File Name field, type a name for the private key file. The Public Key File Name field is automatically completed and displays the private key file name appended with .pub.

     Figure 3.18. Completed Fields for the New SSH Key Pair

     
4. Click Finish and click OK to close the Manage SSH Keys wizard.

1. In the OpenShift Explorer view, right-click the connection and click Manage SSH Keys.
2. Click Add Existing.

3. Complete the fields about the existing public SSH key as follows:

   • In the Name field, type a name for the SSH key.

   • In the Public Key field, type the path of the public key file or click Browse to locate the public key file.

     Figure 3.19. Completed Fields for Adding an Existing SSH Public Key

     
4. Click the SSH2 Preferences link.
5. In the Private keys field, click Add Private Key and locate the private key file.
6. Click Apply and click OK to close the Preferences window.
7. Click Finish and click OK.

1. Click Window → Preferences → General → Network Connections → SSH2.
2. In the General tab, click Add Private Key and locate the private key file.
3. Click Apply and click OK to close the Preferences window.

1. Install and set up JBoss Tools 4.3.0 Beta1 or higher.
2. Install and set up Docker.

3. Establish a connection to a Docker daemon within JBoss Tools as follows:

   1. Click Window → Show View → Other…​.
   2. In the View window, type docker in the filter text box to view Docker-related options in the list.
   3. Expand the Docker item in the results and select Docker Explorer.

   4. In the Docker Explorer view, if no connection is configured, a message appears stating that "No connection to a Docker daemon is available. Click this link to create a new connection…”. Click the link to start configuring a new Docker daemon connection.

      Figure 4.1. No Connection to a Docker Daemon is Available

      

   5. In the Connect to a Docker daemon wizard:

      1. Use the default value or set a desired connection name in the Connection Name field.
      2. Check the Use custom connection settings field.
      3. Add the relevant socket information for your host. If you are unsure about this step, use the default Unix socket Location value.
      4. Click Test Connection to test the connection.

      5. When a connection is successfully established, the following message appears:

         Figure 4.2. Ping Success Message

         
      6. This message indicates that the Docker daemon connection is successfully established.

1. Click Window → Show View → Other…​.
2. Type Docker in the filter text field to view Docker-related options in the list.
3. Expand the Docker entry and double click Docker Images.

4. In the listed entries for the Docker Images view, locate the entry that ends with wildfly:latest. If this entry is not listed, pull the Wildfly image as follows:

   1. Click the Pull Image icon at the top bar of the Docker Images view.

   2. In the resulting wizard, type jboss/wildfly and click finish.

      Figure 4.3. Pull WildFly Image from JBoss Registry

      

   3. The bottom right corner displays the progress as the image is pulled down from the registry. When the pulling process completes, the appropriate entry appears on the Docker Images list as follows:

      Figure 4.4. The Docker WildFly Image

      

      Result: You have now pulled a new image for Wildfly from the JBoss registry and run the Docker Image.

1. Click Window → Show View → Other…​.
2. Type Docker in the filter text field to view Docker-related options in the list.
3. In the search results, expand the Docker entry and double-click Docker Containers.
4. The Docker Containers view appears, displaying a list of all containers running on the Docker host.

5. Click the desired container to select it. You can now manage your containers using the following operations:

   1. Click the pause button from the icons on the top right corner of the view to pause the container.
   2. Click the green triangle icon in the row to unpause the container.
   3. To view the container logs, right click the container name and click Display Log.
   4. To view a list of all containers, click on the right-most icon in the list of icons in the view, which displays a drop-down option to view all containers. Click this option to view all available containers.