Top Banner
WebSphere Process Server made easy, Part 3: Application deployment and server resource configuration Skill Level: Intermediate Addison Goering ([email protected]) Software Engineer IBM 06 Feb 2007 This tutorial is the last in a series of three on WebSphere Process Server. It focuses on the deployment of business integration applications and the configuration of server resources. You will follow a sample business integration application from the design phase through deployment. The Business Process Explorer is used as the interface to test and verify the deployed business process. Common Base Event Browser, one of the business integration applications installed with WebSphere Process Server, is used to view events emitted to the common event infrastructure by the business process. The final section discusses procedures for uninstalling and versioning business processes. Section 1. Before you start About this series IBM® WebSphere® Process Server is the deployment and runtime environment for business integration applications. It enables the deployment of applications built in a Service-Oriented Architecture (SOA) structure. This series of three tutorials explores the architecture, installation, configuration, application deployment, and system resource configuration of WebSphere Process Server. Application deployment and server resource configuration Trademarks © Copyright IBM Corporation 2007. All rights reserved. Page 1 of 24
24

Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

Oct 24, 2014

Download

Documents

minesh9
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

WebSphere Process Server made easy, Part 3:Application deployment and server resourceconfigurationSkill Level: Intermediate

Addison Goering ([email protected])Software EngineerIBM

06 Feb 2007

This tutorial is the last in a series of three on WebSphere Process Server. It focuseson the deployment of business integration applications and the configuration ofserver resources. You will follow a sample business integration application from thedesign phase through deployment. The Business Process Explorer is used as theinterface to test and verify the deployed business process. Common Base EventBrowser, one of the business integration applications installed with WebSphereProcess Server, is used to view events emitted to the common event infrastructure bythe business process. The final section discusses procedures for uninstalling andversioning business processes.

Section 1. Before you start

About this series

IBM® WebSphere® Process Server is the deployment and runtime environment forbusiness integration applications. It enables the deployment of applications built in aService-Oriented Architecture (SOA) structure. This series of three tutorials exploresthe architecture, installation, configuration, application deployment, and systemresource configuration of WebSphere Process Server.

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 1 of 24

Page 2: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

About this tutorial

This tutorial is the third in a series of three. It focuses on the deployment of abusiness integration application. Particular emphasis is placed on the managementof the business integration application once deployed to WebSphere ProcessServer.

Throughout this tutorial, WebSphere Process Server will be referred to ProcessServer. WebSphere Application Server will be referred to as Application Server.

Prerequisites and system requirements

This tutorial is written for administrators whose skills and experience are at theintermediate level. You should have a general familiarity with the administration ofWebSphere Application Server before you begin. No particular system requirementsare needed to complete this tutorial.

Section 2. Anatomy of a business integration application

Service Component Architecture overview

Business integration applications are similar to Java™ 2 Platform, Standard Edition(J2EE) applications in the manner in which they are packaged. J2EE applicationsare packaged as Enterprise Archive (EAR) files, standard Java JAR files with .earextensions. An application component provider is responsible for the creation of theEJB, Web, and application client modules. The application assembler is responsiblefor the packaging the modules together to create the J2EE application. The J2EEapplication file contains one or more J2EE modules and a deployment descriptor.You will see in this tutorial that the process of creating and packaging the EAR filesfor a business integration application is nearly the same as for a J2EE application.The major difference between a business integration application and a J2EEapplication is that business integration applications contain deployable modules thatsupport a Service-Oriented Architecture (SOA).

WebSphere Process Server provides the core infrastructure that supports an SOA.Much has been written about why an enterprise might want to move toward aService-Oriented Architecture; the Resources section at the end of this tutorial hasseveral links to general SOA information. Business integration applications are key

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 2 of 24

Page 3: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

to implementing an SOA. In order to build business integration applications, it isnecessary to have a common invocation model and common data model. A ServiceComponent Architecture (SCA) is the common invocation model. Just as J2EEprovides the infrastructure for enterprise applications, an SCA provides theinvocation model. An SCA describes all integration artifacts (the actual code thatdoes the work of a business integration application) as service components with welldefined interfaces. Part 1 of this tutorial series discussed service components andservice modules; the latter is illustrated in Figure 1 below. In an SCA, modules aredeployed into WebSphere Process Server and executed in the runtime environment.Modules may contain one or more components. There are many different types ofcomponents: examples include business processes, business state machines, Javacode, and business rules. In this tutorial, you will focus on a service component(business process) deployed in a business integration application.

Figure 1. Service module overview

Packaging business integration application artifacts

When you develop objects or resources in a development tool such as WebSphereIntegration Developer, the tool will create libraries that contain certain artifacts. Fordeployment, these artifacts are contained in JAR files, RAR files, or WAR files (Javaarchives, resource archives or Web service archives, respectively). In WebSphereProcess Server, the assembled version of the module, along with all the supportingreferences and interfaces to any other service components used by the module, ispackaged in a JAR file. You need this JAR file to deploy the application, along withany other libraries, including other JAR files, WAR files, RAR files, staging libraries(Enterprise JavaBeans, or EJBs), or any other archives. An installable EAR file mustthen be created using either the WebSphere Process Server administrative consoleor the serviceDeploy command. You'll learn about each of these methods later inthis tutorial.

Meet the business process: orderProcess

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 3 of 24

Page 4: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

The business process used in this tutorial is quite simple and straightforward. Figure2 shows the process as it was developed using WebSphere Integration Developer.The Business Process Execution Language (BPEL) code has three execution paths:

1. If an order number is equal to 123, then the sendMail activity is triggeredand an apology e-mail is sent.

2. If an order number is 111, a Wait activity is triggered and the processwaits for 500 seconds.

3. If the order number is anything other than 123 or 111, a Shipment activityis triggered. After shipment is complete, a sendMail activity is triggered.

Figure 2. orderProcess was developed using WebSphere IntegrationDeveloper

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 4 of 24

Page 5: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

Section 3. Installation of the business integrationapplication

In this section of the tutorial, you will install and test a simple business integrationapplication. This application is a SCA EJB module that contains the interruptible orlong-running business process introduced in the previous section. The businessprocess, called orderProcess, has been packaged as part of thesampleOrderBPELApp.jar. (You'll learn more about where you can find this file in amoment.) Its target is a server -- in this case, WebSphere Process Server. When theapplication is installed, the business process template is deployed to the BPEDB,which is the persistent storage for any interruptible business process.

Installing the sample business integration application is quite similar to installing anyother J2EE application. As noted previously, the application is packaged as an EARfile by the developer or assembler. In a typical enterprise environment, it would beturned over to an administrator for installation. The steps for installing the applicationfrom the WebSphere Process Server administrative console are outlined below. In aproduction environment, best practices recommend scripting this procedure.

1. The business integration application must reside either on the network orthe local filesystem. The EAR file for this tutorial, sampleOrderBPEL.ear,is available in the Downloads section of this tutorial; download it and saveit somewhere on your local filesystem, then locate it in the Process Serveradministrative console, as shown in Figure 3. Then click Next.Figure 3. Locate the application on the network or file system

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 5 of 24

Page 6: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

2. The next pane provides options to generate default bindings andmappings. In this tutorial, none of the bindings or mappings needchanging. Click Next to continue.

3. There are a number of installation steps listed on the next pane. In thistutorial, no changes are necessary at this point. Go directly to theSummary page, illustrated in Figure 4.Figure 4. Summary of installation settings

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 6 of 24

Page 7: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

4. Click Finish and locate the message, illustrated in Figure 5, indicatingthat the application was successfully installed. Save the configurationchanges to the master configuration.Figure 5. Save changes before starting the application

5. Start the application by selecting Applications > EnterpriseApplications. Locate the application you just installed, select it, and clickStart. You should see a screen like the one in Figure 6 verifying that theapplication has started successfully.Figure 6. Application started successfully

6. The sampleOrderBPELApp application is an SCA EJB module that

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 7 of 24

Page 8: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

contains a business process. Locate the business process by selectingApplications > Enterprise Applications > sampleOrderBPELAppSelect EJB Modules > sampleOrderBPELApp.jar. Under AdditionalProperties, select Business processes. The panel displays the singlebusiness process that was packaged as part ofsampleOrderBPELApp.jar. The screen illustrated in Figure 7 indicatesthat the business process can be started and stopped from this panel.Figure 7. How to locate business processes in an application

Using serviceDeploy

Another option for installing business integration applications uses the serviceDeploycommand. This command prepares an EAR file from a JAR or zip file that containsservice components. Remember, the orderProcess business process (servicecomponent) is packaged in a JAR file called sampleOrderBPELApp.jar. The syntaxfor the command is as follows:

serviceDeploy sampleOrderBPELApp.jar -keep

The service components are taken from the JAR file and an installable EAR filenamed sampleOrderBPELApp.ear is generated. The EAR file is then deployed to theapplication server. The -keep option saves the temporary files generated duringdeployment, which may be useful for troubleshooting. There is anothercommand-line option, -noJ2EEdeploy, which skips the deployment of theapplication to the application server. You should consider this option if you need toonly generate the EAR file and do not wish to deploy the application immediately.

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 8 of 24

Page 9: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

Section 4. Working with business processes

Using Business Process Choreographer Explorer to work withbusiness processes

After you deploy your applications and business processes, you should test andverify them. The Business Process Choreographer Explorer (BPC Explorer) is aWeb-based application that allows you to work with business processes and humantasks. It can be installed as an option during the installation of the business processcontainer and human task container. The BPC Explorer can be installed either on asingle application server or on a cluster where both a business process containerand a human task container are installed. The BPC Explorer is commonly usedeither by business users in a test environment or by administrators in test, staging,or production environments. Access to objects and actions on those objects issubject to user group membership and the authorizations granted to user groups.

Use the following steps to view a process template (orderProcess) and severalprocess instances that were instantiated from it. BPC Explorer allows you to view thetemplate and instance attributes, as well manage the template and any processinstances.

1. To work with the BPC Explorer, verify that the business processcontainer, human task container, and BPC Explorer applications areinstalled and started using WebSphere Process Server's administrativeconsole. Figure 8 indicates that the applications have been startedsuccessfully from the administrative console.Figure 8. These applications must be started before using BPCExplorer

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 9 of 24

Page 10: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

2. Access the BPC Explorer through the URLs http://localhost:9080/bpc andhttp://appserver_hostname:portnumber/bpc. As shown in Figure 9, theapplication will initially not display any process templates, processinstances, task templates, or tasks.Figure 9. Initial view of BPC Explorer

To review, process templates describe the business process model; theyare deployed to the business process container. Process instancesrepresent individual instances of running business processes and aremanaged by the business flow manager. Multiple process instances of thesame business process can run simultaneously. Task templatesrepresent standalone tasks packaged in the enterprise application. Taskinstances are individual instances of tasks and are managed by thehuman task manager. Figure 10 illustrates support in WebSphereProcess Server for several types of tasks.

Figure 10. WebSphere Process Server supports these tasks

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 10 of 24

Page 11: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

• In a participating task, a service component can assign a task to aperson. An example would be a bank manager determining whetherto approve a loan request.

• Originating tasks permit a person to assign a task to a servicecomponent. For example, a bank manager could invoke anautomated process to discover and analyze the credit history of acustomer.

• Purely human tasks invoke services, but those services arecompleted by another person. As an example, a bank manager mightwant one of her analysts to perform a credit review of a customer andmake a recommendation. This task can be posted and any of theanalysts can claim it and complete it.

3. When sampleOrderBPELApp.ear was installed, there was one processtemplate installed and started. To view the process template, selectProcess Templates > My Process Templates; you should see a screenlike Figure 11. The name of the process template is orderProcess. Notethat it has been started and its execution mode is interruptible, whichindicates that is a long-running business process.Figure 11. View of orderProcess in BPC Explorer

4. To start an instance of the business process, check the box next to

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 11 of 24

Page 12: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

orderProcess and click Start Instance. This particular business processexpects values for several fields. Once you've entered those values asshown in Figure 12, click Submit.Figure 12. Starting a business process instance

5. Verify that the new process instance has been started by selectingProcess Instances > Started by Me. The newly created processinstance, named Process1, will be in the list, as shown in Figure 13. Notethe name of the process template (orderProcess) from which the instancewas instantiated. The number of available actions listed is determined bythe access level of the user.Figure 13. Process instance Process1

6. Using the procedure outlined above, start two more instances of thebusiness process. Depending upon the access control of the user, BPC

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 12 of 24

Page 13: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

Explorer has several options for working with process instances. In Figure14, all of the options are available, since the user was logged in as anadministrator. In this example, Process3 was suspended. In Figure 15,the process was resumed by the administrator.Figure 14. Example of a suspended business process instance

Figure 15. Example of a running business process instance

Viewing business process activities with the Common BaseEvent Browser

Supplementing the common invocation model is the common event infrastructure(CEI), which is used to capture events fired from service components. The CEI is thefoundation for monitoring and managing event points of business integrationapplications. Service component event points are configurable within an applicationin two different modes. Static monitoring consists of specifying event points forcontinuous monitoring after the application has been deployed and running on theprocess. In dynamic monitoring, event points can be enabled and disabled on a

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 13 of 24

Page 14: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

running application on a running server. The common structure for an eventcaptured by either technique is a common base event. The Common Base Eventconsists of header information, component identification (emitter and reporter),situation information, message data, context data, and any associated events.

When WebSphere Process Server is installed, there are several integrationapplications installed by default along with it. One of these is the Common BaseEvent Browser, which is accessible from the WebSphere Process Serveradministrative console. Recall that you started three business process instances inthe section Using Business Process Choreographer Explorer to work with businessprocesses. The instance of interest here is Process1. It has two activities thattriggered events that were captured in the common event infrastructure. You'll nowlearn how to access these events.

1. From the administrative console, select Integration Applications >Common Base Event Browser. You can also access the browserthrough the URL http://localhost:9060/ibm/console/cbebrowser/events.Figure 16 shows the initial page of the Common Base Event Browser.Figure 16. Common Base Event Browser

2. There are three types of events that can be raised from the infrastructure,

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 14 of 24

Page 15: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

and each has its own view. The Event Views panel, shown in Figure 17,indicates that you can view BPEL Process Events, User Data Events,Server Events, or All Events.Figure 17. Event views in the Common Base Event Browser

3. As noted earlier, the orderProcess business process is the servicecomponent that was deployed as part of sampleOrderBPELApp.ear.Events raised from the service component can be viewed from the ServerEvents view. To begin retrieving events, click Get Events, which islocated at the bottom of the window. The number of events should belarger than zero, since the component is coded to fire events upon entryand exit. In the case illustrated in Figure 18, 26 events have beencaptured by the common event infrastructure; the number you will see onyour system may vary.Figure 18. Events raised from orderProcess

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 15 of 24

Page 16: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

4. Select Server Events. Select cellName\nodeName\server1. A list of allserver events is displayed. Figure 19 shows one selected common baseevent with its details listed below. The selected event indicates entry intothe orderProcess (subcomponent) running on WebSphere ProcessServer (component).Figure 19. Detailed view of events raised from orderProcess

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 16 of 24

Page 17: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

5. If BPEL Process Events had been selected from the Event Views panels,you might see something similar to Figure 20. The Process pane (labeled2 in the figure) lists all installed business processes. The Instance pane(3) lists all the process instances of the selected business process. TheEvent List pane (4) displays all the Common Base Events associated withthe selected process instance. The Event Data pane (5) shows theproperties and values of the selected Common Base Event event.Figure 20. Detailed view of BPEL process events

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 17 of 24

Page 18: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

Section 5. Business process management: Uninstallingand versioning

Uninstalling a business process

At times, it may be necessary to remove business processes (or human tasks) fromWebSphere Process Server. You may need to remove a business process formaintenance reasons, or the business itself may change and the process may thusno longer be valid. Uninstalling a business process can be somewhat involved. Bearin mind that there are several levels of dependency when working with businessprocesses. From an administrative perspective, the state of business processinstances are dependent upon the status of process templates, which are in turndependent on the state of the enterprise application.

The first step in uninstalling a business process is to stop all processes and tasktemplates in the application. The following procedure outlines how to perform thisstep.

1. From the administrative console of WebSphere Process Server, selectApplications > Enterprise Applications.

2. Select the enterprise application that contains the business integration

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 18 of 24

Page 19: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

module. In the example you've been working with throughout this tutorial,you would select sampleOrderBPELApp.ear. Under Related Items, selectEJB Modules.

3. Now you need to select the EJB. For the tutorial example, theorderProcess module is contained in sampleOrderBPELApp.jar. Selectthe business processes link and stop all process templates. If there werehuman task templates deployed in the JAR file, you would select thehuman tasks link and stop all of these as well.

The second step is to remove all business process instances or the human taskinstances before uninstalling the business process template or task template. Thefollowing procedure outlines how to perform this step.

1. Start Business Process Choreographer Explorer. Log in as anadministrator.

2. If working with task instances, list all task instances by selecting TaskInstances > Administered by Me.

3. If working with process instances, list all process instances spawned froma business process template by selecting Process Templates > MyProcess Templates. Select the business process template and selectInstances.

4. Select the process instances and select Delete. This removes theprocess instances.

The final step is to stop the business module that contains either the businessprocess or human task.

1. From the administrative console, select Applications > EnterpriseApplications. For this tutorial, select the enterprise application namedsampleOrderBPELApp.

2. Click Stop. If a message returns indicating a failure, verify that all theprocess instances (or task instances) have been deleted. Retry the step ifnecessary.

3. Verify that the enterprise application's status is stopped. Select theenterprise application once again and click Uninstall.

To effectively manage business processes, you need to be aware that you cannotstop enterprise applications (including business integration applications) that containrunning process instances. You cannot stop enterprise applications that contain

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 19 of 24

Page 20: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

stopped but undeleted process instances. And, finally, before you can removebusiness integration applications, you must stop the associated process templates.

Versioning a business process

Imagine this scenario: Your enterprise deployed a business process and over time itperformed quite well. However, changes are inevitable. Through careful monitoringand analysis, you determined that the business process had to be modified. Thus,the business process model changed and the deployed business process wasupdated. Multiple instances of a business process can run simultaneously in theruntime environment. Recall that process instances are instantiated from businessprocess templates. In the runtime environment, a process instance is identified by itsname, namespace, and valid-from date. Both the name and namespace of multipleinstances are shared between instances. However, it is the valid-from date thatdifferentiates multiple instances of the same business process.

Returning to the sample business process, when orderProcess was initiallydeployed, it had the valid-from date shown in Figure 21. The process was valid fromJanuary 1, 2004.

Figure 21. Valid-from date example configuration

Imagine that the deployment team decided to deploy an updated version oforderProcess on January 1, 2007. The name and namespace of the new version areexactly the same as the old version. Only the valid-from date has been modified(and some aspects of the business process itself, obviously).

To deploy this update, the developer would make changes to business processusing WebSphere Integration Developer as indicated by the business processmodel. Once the business process has been changed accordingly, the valid-fromdate of the business process must be modified. The new business process code isregenerated, modules are repackaged, and a new application is ready fordeployment. The application can be deployed either through the administrativeconsole of WebSphere Process Server or through serviceDeploy (remember, yousaw both of these deployment procedures earlier in this tutorial).

Once the application has been deployed, a new table is created in the BPEDB. Thebusiness process container will use the new table when any new process instancesare created. The net effect of updating, repackaging, and redeploying the applicationis that the new version of the business process coexists with the existing version.In-flight instances of the process continue to use the existing template and databasetable.

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 20 of 24

Page 21: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

Section 6. Conclusion

In this tutorial, you explored WebSphere Process Server's rich set of integrationapplications and the robust environment for the deployment and management ofbusiness integration applications. Business integration applications are similar toJ2EE applications in many ways. Both application types are packaged as enterprisearchives and deployed to an application server environment, WebSphere ProcessServer. One of the main differentiators between the two is that business integrationapplications support Service Component Architecture (SCA) modules andcomponents. When SCA modules (business processes, in particular) are deployedto the WebSphere Process Server environment in an EAR file, they exploit theapplication server environment runtime capabilities. Additional support is provided bythe business process container for the deployment and execution of businessprocesses. The BPC Explorer provides a user interface for the management ofbusiness process templates and business process instances. Other integrationapplications, such as the Common Base Event Browser, also support themanagement of SCA modules deployed in business integration applications.

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 21 of 24

Page 22: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

Downloads

Description Name Size Downloadmethod

Sample application for this article sampleOrderBPELApp.ear 180KB HTTP

Information about download methods

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 22 of 24

Page 23: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

Resources

Learn

• See WebSphere Process Server made easy: Parts 1 and 2 for an overview ofkey architectural concepts and for installation and configuration best practices.

• "WebSphere Process Server: IBM's new foundation for SOA," WolfgangKulhanek and Carol Serna (developerWorks, September 2005): This articlediscusses very basic product features.

• IBM Certified Deployment Professional: WebSphere Process Server V6.0: Getcertified on WebSphere Process Server.

• IBM WebSphere Business Process Management Version 6.0 informationcenter: More documentation on the IBM WebSphere Business ProcessManagement products.

• Recommended reading list: Service-Oriented Architecture and WebSphereProcess Server: This is an excellent set of general resources regarding SOAand WebSphere Process Server.

• WebSphere education: More information on training with IBM WebSphereproducts.

• "Business Process Management: Modeling through Monitoring UsingWebSphere V6 Products": Check out this Redbook™, which discusses usingWebSphere Process Server in a larger context.

• "WebSphere Application Server V6 System Management and ConfigurationHandbook": This Redbook provides several good sections on WebSphereApplication Server architecture.

Get products and technologies

• IBM Trial Software: Build your next development project with these packages,available for download directly from developerWorks.

About the author

Addison GoeringAddison Goering is a member of the WebSphere Educationdevelopment team. He has been involved in the development ofadministration courses for WebSphere Application Server, WebSpherePortal, WebSphere Process Server, and WebSphere ESB. He hasdelivered courses to internal IBM users, business partners andcustomers. Prior to joining IBM, he worked as a software developer for

ibm.com/developerWorks developerWorks®

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 23 of 24

Page 24: Wes-wpsprim3-PDF - WebSphere Process Server Made Easy, Part 3

a large consulting company. And, many years ago, he taughtelementary and middle school. Addison resides in the Chicago areawith his wife, five children, four dogs, and four cats.

developerWorks® ibm.com/developerWorks

Application deployment and server resource configuration Trademarks© Copyright IBM Corporation 2007. All rights reserved. Page 24 of 24