Select the Complex type radio button, expand the tree structure to IntegrationHelloWorld => Business Items => ReportRequest. (Figure 14)

Click OK. The Business item ReportRequest is now associated as an input of the process. Click the Outputs tab and repeat steps 4 through 7, then change the name to "outReportRequest". Select ReportRequest as the associated data. You can see the input and output icons on the outer boundaries of the RequestReport process diagram.

In a similar way, create the input and output associated data for the Tasks and the Simple Decision. To create an input for the task, select the task. Ensure that for each task, the input name is inReportRequest and that the output name is outReportRequest, and the type is ReportRequest.

Important: Please add two outputs for the Generate and Send Report task, one is as shown above, the other is associated with no data type. (Figure 15)

Create the connection between the Process input and the Receive Report Request task.Select the Connections icon on the toolbar. Click the input icon of the process, and then click the input icon (left side) of the Receive Report Request task to define the destination of the data flow. (See Figure 16)

Repeat the previous step to connect the other elements. Verify that the process diagram appears as shown in (Figure 17)

Save your work (Ctrl+S).

Step 4: Edit and create the data structure for the business item
Now, you can update the business process model by defining the data structure for the business item that we created.

In the Project Tree, double-click the existing ReportRequest business item under IntegrationHelloWorld => Business Items. Click Add to create the new attribute for your business item. (Figure 18)

Click the gray attribute field and name it ReportID. Use the default Type String.

Repeat step 2 and 3 to add the other attributes. Verify that the attributes appear as shown in (Figure 19)

Save your work (Ctrl+S).

Step 5: Define the decision expressions
Select Intermediate or Advanced for the mode. Select the "Is security level less than 3?" decision in the process diagram. Open the Attributes view and select the Output branches tab. Select the row with condition Yes. Scroll to the bottom of the Attributes view pane and click the Edit Expression button to open the Expression Builder. (Figure 20)

In the Expression Builder dialog, select Modeling artifact from the first term drop-down list. Expand Modeling artifact, and under Processes, select SecurityLevel => RequestReportProcess => Is security level less than 3? => inReportRequest. Select is less than under Operator. Select Number from the Second term drop-down list and enter 3.0 as the Second term details. (See Figure 21)

Click Apply. Review and verify the Expression Tree and Expression text as in (Figure 22)

Click OK. Save your work (Ctrl+S).

Step 6: Export the modeling project
Now, you can do some preparatory work for exporting the modeling project, so that WebSphere Integration Developer can import and implement the model.

Switch the Mode to WebSphere Process Server Mode. (Figure 23)

Select File => Export => WebSphere Business Modeler Export. (Figure 24)

Click Next and select WebSphere Process Server as the Type. (Figure 25)

Select the target directory and export project (make sure to check export entire project). (See Figure 26), below to verify you have the correct setting:

Click Finish. After the success notification displays, you can find the file folders "business items" and "processes" in the path you set.

We've listed a couple of things you should consider when exporting a modeling project.Export the entire project rather than specific elements to avoid missing the selection of required resources.

Specify the Library project name for "Interface" and "Business Items" since they are better stored in a library rather than a module. We did not specify a library project for this business scenario.

Conclusion
This article provided you with some basic knowledge of the IBM WebSphere Business Integration software portfolio and how to model a business process in WebSphere Business Modeler V6.0.