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]

developerWorks Community:

  • Close [x]

Build and deploy a business process model using WebSphere Business Process Modeler Advanced and Lotus Forms, Part 2: Implement and test the BPEL process using WebSphere Integration Developer

Attila Kiss (attila_kiss_bme@yahoo.com), Student, Budapest University of Technology and Economics
Attila Kiss
Attila Kiss attends Budapest University of Technology and Economics and will graduate as a Computer Science Engineer in 2008. He specializes in IT infrastructure management. He has been working with WebSphere products with special focus on business modeling.
Viktor Muller (viktormuller@gmail.com), Student, Budapest University of Technology and Economics
Viktor Muller Photo
Viktor Müller attends Budapest University of Technology and Economics and graduates as a Computer Science Engineer in 2009. He specializes in information system development. He has worked with WebSphere products with a special focus on BPEL development.

Summary:  Learn how to use IBM® WebSphere® Integration Developer to implement and customize a Business Process Execution Language (BPEL) process and then test it in WebSphere Process Server. Part 2 of this tutorial series shows you the steps for generating the Web interface, assembling the components, and testing the solution.

View more content in this series

Date:  15 Apr 2009
Level:  Intermediate PDF:  A4 and Letter (3098 KB | 55 pages)Get Adobe® Reader®

Activity:  13364 views
Comments:  

Prepare the environment for deployment

This section describes the steps to set up the database in preparation for deployment.

Setting up the DB

This tutorial uses Derby Network Server, but you can use any relational DBMS that is supported by the Process Server (refer to Resources for a list of supported databases. We chose Derby Network Server because it is shipped with the Process Server and it can handle multiple connections (as opposed to Derby Embedded), which makes it easier to use during development. Derby is not recommended for a production system.

In the next steps you create an appropriate table in Derby in a new database. If you are using a different database, you can skip this part and create your table in that database. In this case you will have to configure the data source (described in the following section) accordingly.

  1. Navigate to the installation directory of Integration Developer.
  2. Navigate to runtimes/bi_v61/derby/bin/networkServer.
  3. Run the startNetworkServer.bat script. This starts the Derby network server.

    Figure 70. Starting the Derby Network Server
    Starting the Derby Network Serve

  4. Run the ij.bat script to start the database administrator command-line tool of Derby.
  5. Connect to and create (if it does not exist) the database HR by typing:
    connect ‘jdbc:derby://localhost:1527/databases/HR;create=true’;
    

  6. Press Enter.
  7. Run the script provided with this tutorial by executing the following command:
    run ‘TUTORIAL_DIR/HRSchema.sql’;
    

    Where TUTORIAL_DIR is the directory where you extracted the archive for this tutorial.

  8. Type exit;.

    Figure 71. Running the HRSchema.sql script
    unning                                 the HRSchema.sql script

  9. Press Enter to disconnect from the databases and exit from ij.

Setting up the data source

Next, you configure the database connection (data source) that will be used in the information service activities on Process Server.

First start the Process Server embedded in Integration Developer and start the administrative console.

  1. Start Process Server (if you have not yet done so). Right-click WebSphere Process Server in the Servers view and select Start.

    Figure 72. Start WebSphere Process Server
    Start                                 WebSphere Process Server

  2. Wait until the message “server is open for e-business” in visible in the Console view. (This may take some time.) The Console view by default shows the standard output log of the Process Server.
  3. Open the administrative console in your favorite web browser. The administrative console is found at http://localhost:9060/ibm/console.
  4. Click Yes to the security alert.
  5. Log in by entering admin for username and admin for password.

    Figure 73. Logging into the Integrated Solutions Console
    Logging                                 into the Integrated Solutions Console

By default, security is enabled for Process Server embedded in Integration Developer; the credentials mentioned above are the default values. However, the embedded server does not have a Java Database Connectivity (JDBC) provider configured for Derby by default. Use the following steps to create a JDBC provider:

  1. Select Resources > JDBC Providers from the menu.

    Figure 74. Creating a JDBC provider
    Creating a JDBC provider

  2. Select Node=node1, Server=server1 from the scope drop down list.

    Figure 75. Selecting the scope for the JDBC provider
    Selecting the scope for the JDBC provider

  3. Click New.
  4. Select Derby for Database type.
  5. Select Derby Network Server Using Derby Client for Provider type.
  6. Select XA data source for Implementation type.
  7. Click Next and review the summary.

    Figure 76. Summary of JDBC provider properties
    Summary                                 of JDBC provider properties

  8. Click Finish.

    On the top of the next page you see a notification saying that there are unsaved changes to the server’s configuration. You must save all changes in order for them to take effect.

  9. Click Save.

Now that you have a JDBC Provider for Derby Network Server, you will create a data source to access the database.

  1. Click Resources > JDBC > Data sources on the menu.
  2. Select Node=node1, Server=server1 from the scope drop down list.
  3. Click New.
  4. Type HR data source for the Data source name.
  5. Type jdbc/HRDataSource for the JNDI name.
  6. Click Next.
  7. Select Select an existing JDBC provider.
  8. Select Derby Network Server Using Derby Client XA.
  9. Click Next.
  10. Type databases/HR for Database name.
  11. Click Next.

    Figure 77. Summary of data source properties
    Summary                                 of data source properties

  12. Click Finish.
  13. Click Save.

    You can test your data source configuration in the administrative console.

  14. Select the HR data source on the data sources view by clicking the checkbox in front of it.
  15. Click Test connection.

The message in the top of the view should indicate that the connection was successful.


Figure 78. A successful test connection to the data source
Successful                         test connection to the data source

Enabling identity assertion

In this section you enable identity assertion to allow inter-module communication while security is enabled.

  1. Open the administrative console.
  2. Click Security > Secure administration, applications, and infrastructure.
  3. Click RMI IIOP security > CSIv2 inbound authentication in the Authentication view.

    Figure 79. Enabling identity assertion
    Enabling identity assertion

  4. Enable Identity Assertion.
  5. Specify * in the field Trusted Identities.
  6. Click OK.
  7. Click RMI IIOP security > CSIv2 outbound authentication in the Authentication view.
  8. Enable Identity Assertion.
  9. Click OK.
  10. Click Save.

    After any changes made to the security configuration of the server the server must be restarted.

  11. Right-click WebSphere Process Server in the Servers view of Integration Developer.
  12. Select Restart.

9 of 14 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management, WebSphere
ArticleID=432422
TutorialTitle=Build and deploy a business process model using WebSphere Business Process Modeler Advanced and Lotus Forms, Part 2: Implement and test the BPEL process using WebSphere Integration Developer
publish-date=04152009
author1-email=attila_kiss_bme@yahoo.com
author1-email-cc=crothemi@us.ibm.com
author2-email=viktormuller@gmail.com
author2-email-cc=crothemi@us.ibm.com