Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

IBM BPM V7.5 orchestration scenarios, Part 1: Top-down design using IBM Process Designer and IBM Integration Designer

Ashok Iyengar (ashoki@us.ibm.com), Executive IT Specialist, IBM
Ashok Iyengar photo
Ashok Iyengar is a member of IBM for Software Services for WebSphere (ISSW). He has worked extensively with the IBM Business Process Management platform doing proof of concepts, pilots, and architecture design. Currently his focus is on the cloud, specializing in Platform as a Service (PaaS). He helps customers deploy patterns on IBM PureApplication Systems and IBM SmartCloud.
(An IBM developerWorks Contributing Author)
Kent Below (kbelow@us.ibm.com), Advisory Software Engineer, IBM
Author photo of Kent Below
Kent Below is a Software Engineer in the Business Process Management Bring-up Lab in Rochester, Minnesota. Kent has over 10 years of experience with BPM, automation, and integration. He works with BPM development teams to deliver products that allow customers to continuously improve their business processes. He is currently working to integrate multiple IBM products to support common business patterns.

Summary:  Learn to create a simple top-down process in IBM® Business Process Manager Advanced V7.5 by creating a Business Process Model and Notation business process in IBM Process Designer and invoking a BPEL integration service that is created in IBM Integration Designer. This tutorial shows how a BPMN process can easily invoke an SCA service.

Date:  14 Sep 2011
Level:  Intermediate PDF:  A4 and Letter (1041 KB | 22 pages)Get Adobe® Reader®

Activity:  18580 views
Comments:  

Part 2: Working with Integration Designer

Bring up Integration Designer to implement an SCA-based Plain Old Java Object (POJO) service that will be used by the second of the three activities in TopDown1Bpd.

Create a new workspace

  1. Launch Integration Designer.
  2. In the Workspace Launcher window, enter a workspace name, such as C:\IBM\workspaces\TopDown (Figure 20).

    Figure 20. Selecting a workspace
    Selecting a workspace

  3. Click OK.

    Note: Do not check the box that says “Use this as the default and do not ask again”.

  4. You are asked for the Process Center connection details:
    1. Enter the Process Center URL as http://<SERVER_NAME>:<PORT_NUMBER>/ProcessCenter, as shown in Figure 18.
    2. Enter the appropriate credentials, such as tw_admin/tw_admin.
    3. Click Login (Figure 21).

      Figure 21. Process Center login
      Process                         Center login

    4. If a Getting Started welcome screen is displayed, close it.
    5. You are now in the Process Center perspective.

      Note: In case you are taken to the Business Integration perspective, which is the default perspective in the Integration Designer, click the tab on the top right to open the Process Center perspective. You can also get to that perspective by selecting Windows > Open Perspective > Process Center.

  5. Once you are in the Process Center screen, open the Top Down 1 Process Application in the Integration Designer workspace by clicking Open in workspace.
    1. Notice the subtle difference between the Process Center screens. In Process Designer, the menu option reads "Open in designer", whereas in Integration Designer, the menu option reads "Open in workspace" (see Figure 22).

      Figure 22. Process app listed in Process Center perspective
      Process app listed in Process Center perspective

      Note: The Process Center, which is the common repository, is accessible via Process Designer as well as Integration Designer.

    2. Select Top Down 1 in the Open Process Applications pop-up window and click OK, as shown in Figure 23.

      Figure 23. Process apps to be opened in the workspace
      Process apps to be opened in the workspace

  6. It takes some time for the Process Application information to be populated and built in Integration Designer. Watch the little status bar at the bottom right of the tool.

After everything is loaded, let's explore the creation and deployment of a Service Component Architecture (SCA) service.


Implementing an SCA Service

  1. In the Business Integration perspective, navigate down to Top Down 1 > Advanced Integration Services.
  2. Right-mouse click on sca service and choose Implement as shown in Figure 24.

    Figure 24. Context menu in Integration Designer
    Context menu in Integration Designer

  3. From the four choices for implementation type, select Java component (Figure 25) and click Finish.

    Figure 25. Implementation types
    Implementation types

  4. The Java™ implementation window is displayed.

    In another tab, the Assembly diagram is updated. If you browse it, you see that there are two components wired together: scaservice is an import component that is wired to the reference of the Java component named scaservice_JavaImplementation.

    Note: The tooling generates most of the Java code for you.

  5. Go back to the Java implementation tab. Scroll to the bottom and implement the invoke method. Similar to what you did in Process Designer, you added println (see Listing 3). The output shows up on the log and returns a new string.

    Listing 3. Java implementation code
    public String invoke(String data) {
    	System.out.println("BU: sca service  "+data);
    	data = "hi dad";
    	return data;
    

  6. Press Ctrl+S to save the edits and then close the Java editor.

The service, although a simple println statement, has been implemented. At this time, the updates only exist in the Integration Designer workspace. You need to update the Process Center with these code changes.


Publishing to the Process Center

  1. Still in the Business Integration perspective, right-mouse click on the project folder, Top Down 1 Main, and choose Refresh and Publish (Figure 26). Watch the little status bar at the bottom right of the tool to make sure all the artifacts get updated.

    Figure 26. Context menu in Integration Designer to sync up with Process Center
    Context menu in Integratio Designer to sync up with Process Center

  2. Choose Yes, if prompted to close the editors.

You may minimize the Integration Designer for now. Next, you will run the process using Process Designer.

3 of 7 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management, WebSphere
ArticleID=757232
TutorialTitle=IBM BPM V7.5 orchestration scenarios, Part 1: Top-down design using IBM Process Designer and IBM Integration Designer
publish-date=09142011
author1-email=ashoki@us.ibm.com
author1-email-cc=dwu@us.ibm.com
author2-email=kbelow@us.ibm.com
author2-email-cc=dwu@us.ibm.com