Procedure 3.1. 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 3.1. 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 3.2. 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.

1. Open JBoss Developer Studio.
2. Click File → Import → Maven → Existing Maven Projects.
3. Select Browse and navigate to the quickstart directory, for example, EAP_HOME/quickstarts/switchyard/bean-service and then select OK.
   The import tool scans the directory to locate the associated pom.xml file.
4. Click Finish.
5. The quickstart is listed in the Project Explorer view. You can expand the project to explore its contents.
6. In the Project Explorer view, right-click on the project's name and click Run as → Run on server → EAP.

1. Start the Red Hat JBoss server (if not already running) by selecting the server from the server tab and click the start icon.
2. Select File → Import and navigate to the Git folder. Open the Git folder to select Projects from Git and click next.
3. Select the repository source as URI and click next.
4. Enter the details of the Git repository in the next window and click next.

   

   Figure 3.3. Git Repository Details

5. Select which branch you want to import in the next window and click next.
6. You are presented with the option to define the local storage for this project. Enter (or select) a non-empty directory, make any configuration changes and click next.
7. Import the project as a general project in the next window and click next. Name this project and click Finish.

1. Download and unzip the runtime jars files located in the jboss-brms-engine.zip archive of the JBoss BRMS Deployable zip archive (available from Red Hat Customer Portal).
2. From the Red Hat JBoss Developer Studio menu, select Window and click Preferences.
3. Select JBoss Rules → Installed JBoss Rules Runtimes → Runtime locations.
4. Click Add; provide a name for the new runtime, and click Browse to navigate to the directory where the runtime is located.
5. Click OK, select the new runtime and click OK again. A dialog box indicates, if you have existing projects, that JBoss Developer Studio must be restarted to update the Runtime.

1. In JBoss Developer Studio, click the Servers view. If the Servers view is not visible, click Window → Show View → Servers.
2. If no servers have been previously created then the Servers view displays a new server hyperlink. Click this link to create a new server.
   If there are one or more existing servers, right-click an existing server and click New → Server.
3. In the Define a New Server dialog, select a JBoss Enterprise Application Platform server from the Select the server type list.
4. The Server's host name and Server name fields are completed by default. In the Server name field, you can type a custom name by which to identify the server in the Servers view.
5. From the Server runtime environment list, select an existing server runtime environment for the application server type. Alternatively, to create a new runtime environment click Add and complete the fields and options as appropriate.

   Note

   If the Server runtime environment field is not shown, no server runtime environments exist for the selected application server type. To create a new server runtime environment without canceling the wizard, click Next and complete the fields and options as appropriate.
6. Click Next.
7. The server behavior options displayed vary depending on the selected application server type. To specify that the server life-cycle is to be managed from outside the IDE, select the Server is externally managed check box.
   To specify that the server should be launched to respond to requests on all hostnames, select the Listen on all interfaces to allow remote web connections check box.
   From the location list, select Local. Click Next.

   Note

   The Expose your management port as the server's hostname option, which enables management commands sent by the IDE to be successfully received by the server, is bypassed for local servers regardless of whether the check box is selected.
8. To select applications to deploy with this server, from the Available list select the applications and click Add. Applications to be deployed are detailed in the Configured list.
9. Click Finish to create the server.

• In JBoss Rules, the DSL configuration is stored in .dsl files. These can be created selecting File → New → Other → Drools → Domain Specific Language from the projects context menu.
  

  Figure 5.1. The DSL editor

Procedure 5.1. Task

1. Click the Add button and a dialog box appears.
2. Enter the details of your language mapping wizard into the relevant fields.
   

   Figure 5.2. Dialog box

1. This wizard can be opened by double-clicking a line in the table of language message mappings or by clicking the Edit button.
   

   Figure 5.3. Editing options

2. To change the mapping, edit the appropriate options and click the OK button.

1. Ruleflows can only be set by using the graphical flow editor which is part of the JBoss Rules plug-in for JBoss Developer Studio. Once you have set up a JBoss Rules project, you can start adding ruleflows. Add a ruleflow file (.rf) by clicking on the project and selecting File → New → Other → Flow File.
   By default these ruleflow files (.rf) are opened in the graphical Flow editor.
2. The Flow editor consists of a palette, a canvas and an outline view. Select the element you would like to create in the palette and then add it to the canvas by clicking on the preferred location.
3. Clicking on the Select option in the palette and then on the element in your ruleflow allows you to view and set the properties of that element in the Properties view.
4. The Outline view is useful for complex schemata where not all nodes are seen at one time. Using the Outline view allows you to easily navigate between parts of a schema.

1. To create breakpoints in the Package Explorer view or Navigator view of the JBoss Rules perspective, double-click the selected .drl file to open it in the editor.
2. You can add and remove rule breakpoints in the .drl files in two ways:
   • Double-click the rule in the Rule editor at the line where you want to add a breakpoint. A breakpoint can be removed by double-clicking the rule once more.

     Note

     Rule breakpoints can only be created in the consequence of a rule. Double-clicking on a line where no breakpoint is allowed does nothing.
   • Right-click the ruler. Select the Toggle Breakpoint action in the context menu. Choosing this action adds a breakpoint at the selected line or remove it if there is one already.
3. The Debug perspective contains a Breakpoints view which can be used to see all defined breakpoints, get their properties, enable/disable and remove them. You can switch to it by clicking Window → Perspective → Others → Debug .

1. JBoss Rules breakpoints are only enabled if you debug your application as a JBoss Rules Application. To do this you should perform one of two actions:
   • Select the main class of your application. Right-click on it and select Debug As → JBoss Rules Application .
   • Alternatively, select Debug As → Debug Configuration to open a new dialog window for creating, managing and running debug configurations.
     Select the JBoss Rules Application item in the left tree and click the New launch configuration button (leftmost icon in the toolbar above the tree). This creates a new configuration with a number of the properties already filled in based on main class you selected in the beginning. All properties shown here are the same as any standard Java program.

   Note

   Remember to change the name of your debug configuration to something meaningful.
2. Click the Debug button on the bottom to start debugging your application.
3. After enabling the debugging, the application starts executing and halts if any breakpoint is encountered. This can be a JBoss Rules rule breakpoint, or any other standard Java breakpoint. Whenever a JBoss Rules rule breakpoint is encountered, the corresponding .drl file is opened and the active line is highlighted. The Variables view also contains all rule parameters and their value. You can then use the default Java debug actions to decide what to do next (resume, terminate, step over, etc). The debug views can also be used to determine the contents of the working memory and agenda at that time as well (the current executing working memory is automatically shown).

Procedure 6.1. Task

1. Access the BPEL console at the following URL: http://localhost:8080/bpel-console. A login screen appears.
2. Enter your credentials. The default username is admin with password admin.
3. To change your login details, access the Settings tab in the BPEL editor and click on Users. In this section there are fields to change your username and password.

1. First, select File → New → Project → BPEL 2.0 → BPEL Project or Legacy BPEL Project from the menu bar. Then click the Next button.
   

   Figure 6.1. Diagram 1

2. Enter a project name in the Project Name field.
   

   Figure 6.2. Diagram 2

3. Click the Finish button. The following screen appears.
   

   Figure 6.3. Diagram 3

4. You have now created a new project.

1. First, select File → New → Others → BPEL 2.0 → BPEL Process File and click Next.
   

   Figure 6.4. Diagram 1

2. From here you can choose to create a BPEL process from a template or a service description. The former is recommended.
3. Enter the following information:

   Table 6.1. Fields and Values

   Field	Value
   BPEL Process Name	Enter a process name. For example, HelloWorld.
   Namespace	Enter or select a namespace for the BPEL process.
   Template	Select the appropriate template for the BPEL process. When you select the template, you can see information about it. Select Synchronous BPEL Process.

   

   Figure 6.5. Diagram 2

4. Click Next. On this page, you can customize your WSDL service details using a template. Enter the following information:

   Table 6.2. Fields and Values

   Field	Value
   Service Name	A WSDL service name for the BPEL process. The default name is HelloWorld.
   Port Name	A WSDL port name for the BPEL process. The default name is HelloWorldPort.
   Service Address	An address of the WSDL service for the BPEL process. The default value is http://localhost:8080/HelloWorld.
   Binding Protocol	The binding protocol that you use in the WSDL. You can choose SOAP or HTTP. The default value is SOAP.

   

   Figure 6.6. Diagram 3

5. Click the Next button. On the this page, you can select a folder for the process file from the projects in your workspace. If a folder is not selected, the default folder HelloWorld/bpelContent is used.
6. Click the Finish button. The process is complete.

   Note

   All of the files used in your BPEL project must be under the bpelContent folder of a BPEL project.

Procedure 6.2. Task

1. Go to the New Server wizard.
2. Click on Add.
3. Fill in the name if you wish to do so (this step is optional because the name is preset.
4. Click on Browse and select the home directory.
5. Select one of the available configurations (the configuration you choose must have the BPEL engine available).
6. Click on Finish.

1. Open the Properties view and Palette view by right-clicking the BPEL editor and selecting the Show in Properties or Show Palette in Palette view options.
   

   Figure 6.7. Diagram 1

2. In the Palette view, drag and drop your chosen BPEL element into the BPEL editor.
3. Switch to the Properties view to see information on the BPEL process.
4. The contents of the Properties view is automatically updated as elements are selected in the BPEL editor.

1. Change the Empty element between elements receiveInput and replyOutput to Assign.
2. Add an Assign element between the receiveInput element and replyOutput element.
3. Click the Assign element in the BPEL editor to see the properties information in the Properties view.
4. Set its name in the Description tab as assignHelloMesg.
5. In the Details section of Properties view, click the New button to add a copy sub-element to the element. Assign "Variable to Variable" (input:string to result:string). An " initializer" popup dialog box appears. Click the Yes button.
6. Navigate down to the desired component and click it. The icon to the left of the component name indicates its type: a blue dot is the BPEL variable, an envelope is a message, an "e" is an XML element. Click the New button once more and select Expression to Variable (assign concat($input.payload/tns:input, ' World')) to result:string.

1. Open the file HelloWorldArtifacts.wsdl in the HelloWorld project.
2. Right-click the WSDL editor and select the Add Service option. A new service should appear in the editor. Name it HelloWorldProcessService. It has the Port named NewPort. Select it, right-click on it and rename it to HelloWorldProcessPort in the Properties view.
   

   Figure 6.8. Diagram 1

3. Right-click in the whitespace of the WSDL editor and select the Add Binding option. A new Binding component appears in the editor. Name it HelloWorldSOAPBinding. Select it, and in the General tab of the Properties view and select HelloWorld as a port type in the PortType field.
4. Click on the Generate Binding Content button to open the Binding Wizard.
5. In the wizard, select SOAP as the Protocol. Click the Finish button to close the wizard.
   

   Figure 6.9. Diagram 2

6. Click the HelloWorldProcessPort property in the General section of the Properties view.
7. Select HelloWorldSOAPBinding in the Binding combobox.
8. Enter http://localhost:8080/bpel/processes/HelloWorld?wsdl in the Address field.
   

   Figure 6.10. Diagram 3

1. To create a new deploy.xml file for deploying BPEL projects, select File → New → Other → BPEL 2.0 → BPEL Deployment Descriptor. Click the Next button.
   

   Figure 6.11. Diagram 1

2. On this page of the wizard, enter the BPEL Project. Do so by clicking the Browse button to select the BPEL project in your workspace that you want to deploy to the runtime.
3. Select the bpelContent folder in your new BPEL project for the BPEL Project field. Do not change the default file name which is deploy.xml.
4. Click on the Finish button to close the wizard and a new deploy.xml file is created.
   

   Figure 6.12. Diagram 2

5. Finally, double-click the deploy.xml file to open it in ODE Descriptor Deployment Editor. In the Inbound Interfaces section, click the Associated Port column and select HelloWorldProcessPort in the combobox.The Related Service and Binding Used columns should be automatically filled in. Save the changes to the deploy.xml file.
   

   Figure 6.13. Diagram 3

1. Open the Servers view by selecting Windows → Show View → Other → Server → Servers.
2. Right-click the Servers view and select New → Server to open the New Server wizard.
3. Select JBoss EAP 6 as a server type.
4. Click the Next button. On this page, input your JBoss EAP location. Then click Next.
5. Select HelloWorld, then click the Add button to add the project to the server. Finally, click the Finish button.
6. Start the server by right-clicking on the server and selecting the Start item.
7. Enter the link http://localhost:8080/bpel-console/app.html in your web browser to access the deployed processes.

1. To create a correlation for a messaging activity, go to the dashboard tab Correlation Sets and click the plus button. Set a name for the set when prompted.
2. In Properties view, click the Details tab and then click the Add button. The Select a Property dialog box appears.
3. Enter a name for the new WSDL property and its type. (Either an XSD simple type or an XML Schema element.)
4. Click the Browse button to select a type. The Type Selection dialog box appears.
5. Click New in the Aliases section to create a new WSDL property alias.
6. Select either the Message Type, XSD Simple Type or XML scheme Element radio button and click Browse to select its type. Click OK.
7. A correlation can be assigned to a messaging activity (for example, Invoke, Receive, Reply). Select the activity, click Add on the Correlation property tab and choose the appropriate correlation set.

Procedure 6.3. Task

1. Access the cheat sheet by clicking Help → Cheat Sheets.
2. The cheat sheet opens in a separate view as show below. Click on the Click to begin link to begin.
   

   Figure 6.15. Diagram 1

3. You can now view tutorials for plug-in tools.

1. In the JBoss Developer Studio workbench menu, select Window → Open Perspective → Other to view the perspective list.
2. Choose the perspective you wish to use. JBoss Developer Studio standard views such as Properties and Resource Navigator are useful.
   

   Figure 7.1. Perspective list

1. Open a new connection.
2. Start the Guvnor Connection wizard in one of the following ways:
   • Select File → New → Other → Guvnor → Guvnor repository location within JBoss Developer Studio.
   • Go to the Guvnor Repositories view using the drop-down menu.
   • Use the menu button to select a new connection. This is added to JBoss Developer Studio automatically.

1. Default values appear in the Location, Port and Repository fields. You can edit these fields using their corresponding text boxes.
2. To input a Guvnor repository URL into the respective fields, drag and drop it into the Location field.

   Important

   When using JBoss Developer Studio tooling, you cannot access Guvnor data if this Guvnor is deployed on a secured HTTP (HTTPS).
3. The EGT calls the Guvnor repository at various times, such as when it is determining if any resource updates are available. If you use session authentication, the authentication dialog appears at different times during the JBoss Developer Studio workbench session, depending on what actions you take. We recommend saving the authentication information in the JBoss Developer Studio keyring.
   Click on save username and password to save your details into the JBoss Developer Studio workbench's keyring file.

   Note

   If the authentication information is not stored in the keyring, then the EGT uses a session authentication. This means that the credentials supplied are only used during the lifetime of the JBoss Developer Studio workbench instance.

   Note

   If an authentication failure error occurs, you can retry the same operation and supply different authentication information.

   Note

   The JBoss Developer Studio keyring file is distinct from keyring files found in some platforms such as Mac OS X and many forms of Linux. Thus, sometimes if you access a Guvnor repository outside the EGT, the keyring files might become outdated, and you are unexpectedly prompted for your credentials in JBoss Developer Studio. Enter your username and password to continue.

1. To get local copies of Guvnor repository resources, you can drag-and-drop them from the Guvnor Repositories View. You can also perform this action in the Guvnor Wizard.
2. Local copies of Guvnor repository files are created. The EGT sets an association between the local copy and the master file in the repository. You should not alter this information. The association allows for operations such as update and commit in synchronization with the master copy held in the Guvnor repository.
   

   Figure 7.2. Diagram

   The EGT decorates local resources associated with Guvnor repository master copies. This decoration appears in JBoss Developer Studio views conforming to the JBoss Developer Studio Common Navigator framework, such as the JBoss Developer Studio Resource Navigator and the Java Package Explorer. The Dummy rule.drl file with the decoration in the Resource Navigator. The Guvnor icon decorator is on the top right of the file image, and the Guvnor revision details are appended to the file name. You can change the location of these in the Local Guvnor Repository Resource Decoration Preferences.
3. You can see that the Dummy rule.drl file is associated with a Guvnor repository resource, and the local copy is based on revision 0, with a 02-10-2008, 4:21:53 date/time stamp. However, the file Sample.drl is not associated with a Guvnor repository file.
4. The EGT adds a property page to the standard JBoss Developer Studio properties dialog. Use it to view the specific Guvnor repository, the location within the repository, the version (date/time stamp) and the revision number.
   

   Figure 7.3. Properties

1. Open the wizard by selecting File → Import → Guvnor → Resource from Guvnor or File → New → Other → Guvnor → Resource from Guvnor.
2. You are prompted to enter the source Guvnor repository. You can also create a new Guvnor repository connection.
3. Once the source Guvnor repository is chosen, the wizard prompts for the resources to be copied.
4. Finally, choose the target location for the files in the local workspace.
5. On completion the wizard copies the selected files from the Guvnor repository to the local workspace. If a file with the same name already exists in the destination, you are prompted to rename it.

1. Select Show History in the local Guvnor context menu. Alternatively, select it in the context menu for a Guvnor repository file in the Guvnor Repositories View.
2. The Guvnor Resource History view is refreshed to display the revision history.
3. To open a JBoss Developer Studio read-only editor with the revision contents, double-click on a revision row or select the Open (Read only) option from the context menu.
4. Click on the Save As option when a file is open in a read-only editor to save a local writable copy of the contents. (This does not associate the file created with its Guvnor source.)