Modeling Your First Process with SAP NetWeaver Business Process Management

Transcription

1 Modeling Your First Process with SAP NetWeaver Business Process Management Applies to: SAP enhancement package 1 for SAP NetWeaver Composition Environment 7.1 including SAP NetWeaver Business Process Management Summary This tutorial describes how to model and execute an end-to-end business process using SAP NetWeaver Business Process Management. The tutorial contains also information about how to monitor the business process, as well as a problem analysis section. Download the needed source files from here. Company: SAP AG Created on: 6 May SAP AG 1

2 Table of Contents Modeling Your First Process...3 Preparation Steps...6 Create the Users...6 Deploy the EAR File and Create the Logical Destination...9 Configure the HTTP Proxy...11 Configure the Developer Studio...13 Import the Necessary Files...15 Modeling the Process...20 Create the Development Component and Configure Dependencies...20 Create the Tasks...24 Import the WSDL file...31 Model the Process...33 Define Data Mappings...45 Executing the Process...54 Build and Deploy the Process...54 Start and Execute the Process...54 Monitor the Process...58 Analysis of Potential Problems...60 References...65 Copyright SAP AG 2

3 Modeling Your First Process Note: This document is for informational purposes only. Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. The author does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code. Use Modeling a composite business process with the SAP NetWeaver Business Process Management (BPM) requires the combination of human interaction and system integration in one model. You model the process in the Process Composer using the BPMN (Business Process Modeling Notation). SAP NetWeaver BPM supports the key process concepts through their lifecycle, for example events, tasks, rules. This tutorial describes how to model the business process Purchase Process in the Process Composer as well as executing it at the Process Desk. The process in the picture below describes the procedure of purchasing of stock, e.g. SAP AG or Oracle. In the PurchaseSelection human activity, you choose which stock to purchase and put a number of stocks in. The getquote automated activity delivers the price of stock. After that the total value is calculated ( SumPrice Calculation ) and if it is greater than 1000, then a manager has to agree to purchase ( PurchaseApproval human activity). Finally, in PurchaseNotification all the data and the decision of the manager is shown SAP AG 3

4 2009 SAP AG 4

5 Prerequisites You work in the SAP NetWeaver Developer Studio (SAP NetWeaver CE 7.1. EHP 1) for modeling the process. Your Developer Studio version includes the Process Composer perspective. You have SAP NetWeaver Composition Environment with SAP NetWeaver Business Process Management installed for executing the process at runtime. Procedure 1. Preparation Steps a) Create the users. b) Create the logical destination. c) Configure the HTTP proxy. d) Configure the Developer Studio. e) Import the necessary files. 2. Modeling the Process a) Create the development component and configure dependencies. b) Create the tasks. c) Import the WSDL file. d) Model the process. e) Define data mappings. 3. Executing the Process a) Build and deploy the process. b) Start and execute the process. c) Monitor the process SAP AG 5

6 Preparation Steps Before start modeling the process, you have to do some preparation steps, which allow you to deploy the process and execute it at runtime. You do the preparation steps in the in SAP NetWeaver Administrator and in the Developer Studio. Create the Users Use A user can be assigned as a potential owner to an individual task, which he/she has to execute. A user can also be assigned as a potential owner to a lane and executes all the tasks in this lane. Every user has at least two roles: BPEM End User and Every User Core Role (optional Administrator). Roles are needed to collect several user rights. You may have to change the password during the first login. For the process Purchase Process you need 2 users: LoginID Last name First name Password purchaser Pure Peter galaxy1 manager Meier Michael galaxy1 You may have to change the password during the first login SAP AG 6

7 Procedure 1. To open the SAP NetWeaver Administrator, enter the path in your browser. 2. Navigate to Operation Management Users and Access Identity Management. 3. From the Search Criteria dropdown menu, select User and choose the Go pushbutton. You get the list with all users. 4. Choose the Create User pushbutton and on the General Information tab page, fill in all required fields (marked with an asterisk (*)) SAP AG 7

8 5. On the Assigned Roles tab page, select Portal Role from the Search Criteria dropdown menu and choose the Go pushbutton. 6. Select Every User Core Role and choose the Add pushbutton. 7. Add BPEM End User role. To do that, repeat the last two steps. You can see which roles are assigned to a user, under Assigned Roles on the right. If necessary remove roles. 8. Choose the Save pushbutton SAP AG 8

9 Deploy the EAR File and Create the Logical Destination Use Before you create the logical destination you need to deploy the HelloWorld.ear file that is included in the _Source Files ZIP file. Logical destination contains the URL (end point) where the Web service is. You have to enter a logical destination for the Web service when you model the process. Procedure 1. Deploy the HelloWorld.ear to your server. 2. To open the Single Service Administration in the SAP NetWeaver Administrator, enter the following path in your browser: 3. Search for World as you can see in the screenshot below: 4. Go to the WSDLs tab and copy the URL. 5. To open the SAP NetWeaver Administrator, enter the following path: 6. Navigate to SOA Management Technical Configuration Destination Template Management SAP AG 9

10 The list with all logical destinations appears. When you select a logical destination, you can see the information about it. 7. Choose the New pushbutton. 8. Select WSDL from the Destination Type dropdown menu and enter SO in the Destination Name field. 9. Enter the WSDL URL you have just copied in the URL field. 10. Choose the Next pushbutton and then the Finish pushbutton SAP AG 10

11 Configure the HTTP Proxy Use You need to configure HTTP proxy to ensure the connection to the Web service from your system. Procedure 1. To open the SAP NetWeaver Administrator, enter the following path in your browser: 2. Navigate to SOA Management Technical Configuration SOA Middleware Global Setting. 3. On the HTTP Proxy tab page, enter proxy in the Host field, enter 8080 in the Port field and then *.sap.corp;localhost in the Exclude List field and choose the Save pushbutton. 4. On the WS Navigator tab page, in the Allowed Hosts field, enter an asterisk (*) and choose the Save pushbutton SAP AG 11

12 2009 SAP AG 12

13 Configure the Developer Studio Use You need to configure the AS Java in the Developer Studio to be able to deploy and execute your process on the server. Procedure 1. In the Developer Studio, choose Window Preferences and then select SAP AS Java from the list. 2. Choose the Add new SAP System pushbutton. 3. In the dialog box that appears, enter the necessary information in the Instance Hostname and Instance Number fields and choose the OK pushbutton. Important: If your server runs on your local machine, enter full qualified machine name or IP; otherwise you won t be able to assign a user to a task SAP AG 13

14 4. Select Java and then Compiler from the list. Select 5.0 from the Compiler compliance level dropdown menu SAP AG 14

15 Import the Necessary Files Use You import in the Developer Studio a software component archive (sca) that contains the necessary user interfaces (UI), which you use in the model. Procedure 1. Unpack the attached file. This file contains the HelloWorld.sca. The file also contains test.sap.com~tc~glx~helloworld_ear.ear, which you need to deploy to your server. It provides you the URL of the WSDL file that makes the automated activity in the model work. 2. Start the Developer Studio and choose Window Open Perspective Other... Development Infrastructure SAP AG 15

16 To not overwrite the development components (DC) that you have already created in the MyComponents SC, create a new SC and move all the existing components to the new SC. a) In the context menu of Local Development node in the Component Browser view, choose New Software Component. b) In the New Software Component dialog box, enter a name for the new software component (SC) and choose Finish. c) The new SC appears in the Component Browser view. d) Select all DCs in the MyComponents SC and move them with drag & drop to the new SC. e) Confirm the Move Development Components dialog box with OK. All DCs are moved to the new SC. The MyComponents SC is empty. 3. In the context menu of Local Development node in the Component Browser view, choose Import SC SAP AG 16

17 4. In the dialog that appears, enter the path to the sca file or browse the file system. Choose the Finish pushbutton. The new software component (SC) MyComponents appears in the Component Browser view. We recommend creating a new SC (GLX-TUTORIAL) for the DCs of this tutorial. a) In the context menu of Local Development node in the Component Browser view, choose New Software Component SAP AG 17

18 b) In the New Software Component dialog box, enter as name for the new software component (SC) GLX- TUTORIAL and choose Finish. c) The new GLX-TUTORIAL SC appears in the Component Browser view. d) Select all DCs in the recently imported MyComponents SC and move them with drag & drop to the GLX- TUTORIAL SC. e) Confirm the Move Development Components dialog box with OK. All DCs are moved to the new SC. The MyComponents SC is empty. 5. Select the GLX-TUTORIAL SC and in the Component Properties view, open the Dependencies tab page SAP AG 18

19 All dependencies shown in the picture below are required for successful execution of process. 6. Choose the Add pushbutton and select all required dependencies. Choose the Finish pushbutton SAP AG 19

20 Modeling the Process Create the Development Component and Configure Dependencies Use You create a development component (DC) to store the process model in the DC. You also configure dependencies to other DC to be able to use the necessary user interfaces (UI) stored in the other DC. Procedure 1. In the context menu of GLX-TUTORIAL, choose New Development Component SAP AG 20

21 2. In the dialog that appears, select Process Composer DC type and choose the Next pushbutton. 3. In the next dialog, in the Name field, enter glx/tutorial/pm and in the Vendor field, demo.sap.com. 4. Choose the Finish pushbutton. You have created a new DC. You need to configure a dependency to the glx/tutorial/wdui DC that contains the UIs you need to use in the process. If prompted to switch to the Process Composer perspective, choose the No pushbutton SAP AG 21

22 5. Select the glx/tutorial/pm DC and open the Dependencies tab page in the Component Properties view. 6. Choose the Add pushbutton, expand the GLX-TUTORIAL SC and select the glx/tutorial/wdui DC to configure a dependency to it. 7. Choose the Next pushbutton. 8. In the Dependency Details, select the Design Time, Deploy Time, Runtime and Build Time checkboxes fields and choose the Finish pushbutton SAP AG 22

23 9. In the Component Browser view, create projects from the DCs you have created. To do that, open the context menu of the glx/tutorial/pm DC and choose Sync/Create Project Create Project. If Create Project option is disabled, then the project has already been created SAP AG 23

24 If you are asked to sync sources and used DCs, choose the Select All pushbutton and then the OK pushbutton. Web Dynpro project for the glx/tutorial/wdui DC is created automatically. Create the Tasks Use When you model a process you create human activities (HA) and automated activities (AA). The automated activity calls the Web service, which is assigned to it and the activity is executed automatically. The human activity must have a task assigned to it. The task must have a UI component assigned to it, which is implemented in Web Dynpro, to enable the interaction between the user and the process. You have to configure the necessary dependencies from the Process Composer DC to the Web Dynpro DC that contains the UI components to be able to assign a UI to a task. You have to create the following tasks: Task Name in the Model Web Dynpro Component (for HA) Potential Owner 1 Purchase Selection (HA) PurchaseSelection Peter Pure 2 Purchase Approval (HA) PurchaseApproval Michael Meier 3 Purchase Notification (HA) PurchaseNotifacation Peter Pure 4 getquote (AA) Procedure 1. Before you start modeling the process, you must build the DCs to load the imported files into the Process Modeling Repository. In the Component Browser view, open the context menu of the glx/tutorial/pm DC and choose Build. 2. In the dialog that appears, choose the Select All pushbutton and than the OK pushbutton SAP AG 24

25 3. Choose Window Open Perspective Others Process Composer to open the Process Composer perspective. 4. In Project Explorer view, expand the [LocalDevelopment]glx/tutorial/pm DC, then expand Process Modeling and in the context menu of Tasks, choose New SAP AG 25

26 5. In the dialog that appears, enter Purchase Selection in the Name field and choose the Finish pushbutton. The task you created opens in the Task Editor. You have to assign a UI component and a potential owner to the task SAP AG 26

27 6. On the Overview tab page, choose the Choose pushbutton under User Interface. In the dialog that appears, select glx/tutorial/wdui from the Dev.Component field and then select API (containing the WD component) from the Public Part field. Choose the Next pushbutton. 7. Select PurchaseSelection from the Component field and select the interface view of the component from the Interface View field. Choose the Next pushbutton SAP AG 27

28 2009 SAP AG 28

29 8. Select complete from the Completion Event field and error from the Error Event field. Choose the Finish pushbutton. 9. Open the Roles tab page and under Potential Owners choose the Choose pushbutton in the Principals field. 10. In the dialog that appears, select User from the Principal name dropdown menu and choose the Search pushbutton. Logon to the server with your credentials if prompted. 11. Select Pure, Peter from the Search Results field, which contains all users that have been created, and choose the Add-> pushbutton. You can assign multiple potential owners to a task SAP AG 29

30 12. Save the Purchase Selection task. To create the Purchase Approval and Purchase Notification tasks, follow the above steps. To assign the necessary potential owners, see the table in the Use section of Create the Tasks SAP AG 30

31 Import the WSDL file Use When you create an automated activity, you assign a service interface definition (WSDL file) to the automated activity. You have to import the WSDL in the Developer Studio. When the process is executed at runtime, the Web service whose WSDL is assigned to the automated activity is called and the activity is executed automatically. Procedure 1. In Project Explorer view, expand the [LocalDevelopment]glx/tutorial/pm DC, then expand Process Modeling and Service Interfaces. 2. In the context menu of the WSDL File node, choose Import WSDL 3. Select the Remote Location/File System radio button and enter the URL of the WSDL file you imported or browse it in the file system. Choose the Finish pushbutton. You have copied the URL after you have deployed the EAR file and created the logical destination (see Deploy the EAR File and Create the Logical Destination) 2009 SAP AG 31

32 2009 SAP AG 32

33 Model the Process Use You create a process with the necessary swimlanes, flow objects, artifacts and connections between them. You have to create a process like the one shown in the graphic at the beginning of this document. Procedure 1. Create a New Process with a Pool. 2. Create Lanes. 3. Create Human and Automated Activities. 4. Create the Data Object. 5. Create the Gateway. 6. Create the Mapping Activity. 7. Create Connections. 1. Create a New Process with a Pool 1) In Project Explorer view, expand the [LocalDevelopment]glx/tutorial/pm DC, and then expand Process Modeling. 2) In the context menu of Processes, choose New. 3) In the dialog that appears, enter Stock Purchase in the Name field and choose the Next pushbutton. 4) In the dialog that appears, select the Create start and end event from a service operation and Create a new pool checkboxes and choose the Finish pushbutton SAP AG 33

34 The process you created appears in the Diagram Editor. A pool and start and end event, containing the same service operation are also created. You can delete the connection between the start and end event. 5) Select the pool and in the Properties view open the General tab page. Enter Purchase Process in the Name field. 6) Select the Make the pool active checkbox if it is not selected. 7) In the Properties view, open the User Texts tab page. Enter Purchase Process in the Subject field under Parameterized Texts SAP AG 34

35 8) On the Administrators tab page, define an administrator of the process. To do that, follow the steps for defining a potential owner of a task, described in the Create the Tasks section SAP AG 35

36 2009 SAP AG 36

37 2. Create Lanes 1) Expand Swimlanes from Palette. 2) Choose Lane and click the name area of the pool in the modeling surface. The new lane is created. 3) Select the lane on the left and in the Properties view open the General tab page. Enter Purchaser in the Name field. 4) Select the lane on the right and in the Properties view open the General tab page. Enter Manager in the Name field. 5) (Optional) If you have not assigned potential owners for all the tasks you created, you can do that on a lane level. You have to assign Peter Pure to the Purchaser lane and Michael Meier to the Manager lane. To do that, select the respective lane and assign the potential owner to it following the steps described in the Create the Task section. The potential owner of the lane becomes potential owner of all the tasks in the lane SAP AG 37

38 2009 SAP AG 38

39 3. Create Human and Automated Activities 1) Create the Human Activities a) In the Project Explorer view, expand Tasks. b) Drag all tasks to the appropriate lane in the modeling surface. Human activities are created with the respective task assigned to them SAP AG 39

40 2) Create the Automated Activity a) Drag & drop the interface HelloWorldWebService to the process diagram between the Purchase Selection human activity and the Sum Price Calculation mapping activity as shown in the screenshot above SAP AG 40

41 An automated activity is created. b) In the Properties view of this automated activity, choose Interface. c) Select GetQuote from the Operation dropdown menu. d) Enter the name of the logical destination SO. e) Select the Use logical destination radio button and enter SO in the Logical Destination field SAP AG 41

42 4. Create the Data Object 1) Expand Artifacts from Palette. 2) Choose Data Object and click the modeling surface. The data object appears in the place you clicked. 3) In the Properties view, open the General tab page and enter DO_Purchase in the Name field. 4) On the Data Type tab page, select Context - from the dropdown menu. 5. Create the Gateway 1) Expand Gateways from Palette. 2) Choose Exclusive Choice and click in the Purchaser lane between GetQuote automated activity and Purchase Notification human activity. The gateway appears in the place you clicked. 6. Create the Mapping Activity 1) Expand Activities from Palette. 2) Choose Mapping and click in the Purchaser lane between GetQuote automated activity and the gateway. The mapping activity appears in the place you clicked. 3) In the Properties view open the General tab page and enter Total Value Calculation in the Name field. 4) Choose File Save and save the process SAP AG 42

43 7. Create Connections You have an option to create connections between the objects in the process with a speed button. 1) Point your cursor at the start event. The speed buttons appear around the start event. 2) Choose the connection speed button, shaped as an arrow and drag the connection to the Purchase Selection human activity. The connection between the start event and the human activity is created. 3) Create all the necessary connections as shown in the graphic in the beginning of the document. To do that, follow the above steps. 4) Select the outgoing connection from the gateway to the Purchase Approval human activity and open the General tab page in the Properties view. Enter Total Value > 1000 in the Name field. 5) On the Condition tab page, enter DO_Purchase/Purchase/SumPrice > SAP AG 43

44 6) Select the outgoing connection from the gateway to the Purchase Notification human activity and open the General tab page in the Properties view. Enter Total Value <= 1000 in the Name field. 7) On the Condition tab page, enter DO_Purchase/Purchase/SumPrice <= ) Select the gateway and in the Properties view open the Condition Evaluation tab page. Select the checkbox in the Default Gate field for the Total Value <= 1000 condition to make this alternative the default one SAP AG 44

45 Define Data Mappings Use You define data mappings to show how data used as input and output by the activities and the events in your process is transformed. You define the necessary data mappings in the Purchase Process according to the following procedure. Procedure Defining Input Mapping 1. Select a human or automated activity in the process. 2. In the Properties view, open the Input Mapping tab page. 3. In the Process Context field, choose a node. 4. Map the node to a node in the Inputs field using drag and drop. You can map a process context node to more than one input nodes. You can also map more than one process context nodes to an input node. You define how this mapping is done with an expression. Defining Output Mapping 1. Select a human or automated activity in the process. 2. In the Properties view, open the Output Mapping tab page. 3. In the Outputs field, choose a node. 4. Map the output node to a node in the Process Context field using drag and drop. You can map an output node to more than one process context node. You can also map more than one output node to a process context element. You define how this mapping is done with an expression. Creating Expressions 1. Double-click the function icon on the mapping line between the source and the target node. The expression editor opens. 2. Enter the expression in the expression editor. Alternatively, expand the Rules and Functions node in the expression editor and drag a function to the editing area of the expression editor SAP AG 45

46 Creating expressions example: explicit cast mapping DateTime to String: Double click 2009 SAP AG 46

47 When you define data mappings, you can use the auto mapping option. To do that, you select a source node and drag it to the target node with the secondary mouse button. Release the button and choose Map automatically from the context menu that appears. All possible mappings are created automatically SAP AG 47

48 Define Data Mappings in the Purchase Process The following pictures show the data mappings you need to define in the Purchasing Process in their appropriate order. 1. Purchase Selection human activity 1) No input mapping 2) Define output mapping as shown in the picture SAP AG 48

49 2. getquote automated activity 1) Define input mapping as shown in the picture SAP AG 49

50 2) Define output mapping as shown in the picture SAP AG 50

51 3. Total Value Calculation mapping activity 1) Define mapping as shown in the picture. 2) Double-click the function icon on the mapping line and enter the expression in the expression editor SAP AG 51

52 4. Purchase Approval human activity 1) Define input mapping as shown in the picture. 2) Define output mapping as shown in the picture SAP AG 52

53 5. Purchase Notification human activity 1) Define input mapping as shown in the picture. 2) No Output Mapping. Choose File Save and save the process SAP AG 53

54 Executing the Process Build and Deploy the Process 1. Open the Development Infrastructure perspective. 2. In the Component Browser view, expand the GLX-TUTORIAL[demo.sap.com] SC. 3. Open the context menu of the glx/tutorial/pm DC and choose Build. 4. Next, choose the Select All pushbutton and then the Ok pushbutton. After the process build is complete, you get a status report. 5. Open the context menu of the glx/tutorial/pm DC and choose Deploy. 6. Next, choose the Select All pushbutton and then the Ok pushbutton. After the process deployment is complete, you get a status report. 7. Log on to the AS Java server as Administrator. Start and Execute the Process Use You start your processes in the NetWeaver Administrator in order for the specific tasks to appear in the task lists of the users, to whom specific tasks are assigned. You get central access to all tasks and processes relevant to you in the process desk. To perform a task, which is assigned to you as a processor, you just need to click the subject of the task listed in the UWL. Procedure 1. Start the SAP NetWeaver Administrator with and log on as Administrator. 2. Navigate to Configuration Management Processes and Tasks Process Repository. A list of all deployed processes is displayed SAP AG 54

55 3. In the Component (Vendor) list, choose galaxy~tutorial~pm (test.sap.com). The latest active version of the process is automatically selected in the Component Versions of the Component list. 4. In the Processes, Tasks and Rules of the Component table, choose Stock Purchase. Choose the Start Process pushbutton SAP AG 55

56 5. On the BPM Process Start screen, choose the Start Process pushbutton. When the process is successfully initiated, you get a message in a lower part of the screen. 6. Launch the NetWeaver portal with and log on as purchaser. 7. Open the Universal Worklist tab page in order to see all the tasks relevant to Peter Pure. To refresh the task list, open the context menu of the View icon and choose Refresh. 8. Click the subject of the task Purchase Selection SAP AG 56

57 9. On the next screen, enter the number of stocks you want to purchase. Then, from the drop down menu select the type of stocks you want to purchase and choose the Ok pushbutton. If the total value of the purchase is greater than 1000, the task Purchase Approval appears in the task list of the manager. To view or execute the task, log on as manager. After the task is executed, the task Purchase Notification appears in the task list of the purchaser. To complete the task, log on as purchaser and refresh the view SAP AG 57

58 Monitor the Process Use Monitoring process instances and tasks is an integral part of the NetWeaver Administrator environment. You can view detailed information for the process or task such as the status, the time started and the processor. As an Administrator you can also manage the process or task by suspending, resuming or cancelling it. Procedure 1. Open the NetWeaver Administrator with and navigate to Operation Management Processes and Tasks. 2. Choose Manage Processes and select from the drop down list All Running Process Instances. 3. Expand the Actions drop down menu. You can do the following: Suspend a running process Resume a running process Cancel a running process 2009 SAP AG 58

59 NOTE You can monitor and manage tasks in the same way as process instances SAP AG 59

60 Analysis of Potential Problems Problem 1 Symptoms The process cannot be deployed in the Developer Studio. An error message Deploy Exception is displayed. Solution 1. In the Developer Studio, open the Process Composer perspective. 2. Expand the tree glx/tutorial/pm Connectivity Service Groups. 3. Open the context menu of www_xignite_com and choose Delete. 4. Repeat Step 3 for all remaining Service Groups. 5. Deploy the process SAP AG 60

61 2009 SAP AG 61

62 Problem 2 Symptoms You have started the process and the task assigned to you is present in the tasks list (to check the list with all tasks, open the NetWeaver Administrator and navigate to Operation Management Processes and Tasks Manage Tasks). However, there is no Universal Worklist (UWL) tab page in the portal and the users cannot view or execute the tasks assigned to them. Solution 1. Launch the NetWeaver portal with and log on as Administrator. 2. Navigate to Content Administration Portal Content. 3. In the context menu of Every User Core Rome choose Open and Role. 4. In the Role Content table, select Overview and choose the Edit pushbutton SAP AG 62

63 5. In the left-hand side of the screen, expand the tree Portal Content Content provided by SAP End User Contents Standard Portal Users -> iviews com.sap.netweaver.bc.uwl.iviews. 6. Open the context menu of Universal Worklist and choose Add iview to Workset SAP AG 63

64 7. Copy the iview to the Every User Core Role workset and choose the Save pushbutton SAP AG 64

65 References SAP NetWeaver Business Process Management Knowledge Center Business Process Management page in SDN Business Process Modeling page in SDN SAP Library for SAP NetWeaver Composition Environment 7.1 EHP 1 Developer s Guide: Modeling Processes with Process Composer 2009 SAP AG 65

66 Copyright 2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, System i, System i5, System p, System p5, System x, System z, System z9, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. Any software coding and/or code lines/strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent SAP AG 66