Designing processes - EMC Community Network
Designing processes - EMC Community Network Designing processes - EMC Community Network
Designing the Process at or right after the service invocation step. As a recommended best practice, as you build up your processes, particularly with web services integration activities, regularly test them with the debugger. Use the debugger every time you change the process to ensure the integrity of data that may have changed. Debugging custom methods with the process debugger If you are using custom methods in your workflows, you can debug them using the process debugger. To debug a custom method: 1. Launch Process Builder in debug mode. 2. Modify the shortcut to add debug options and enable debugging using the specified port. For example: -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n The complete shortcut may look similar to the following: C:\Program Files\Documentum\jreForPB\bin\java.exe" -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -Xms128m -Xmx256m -Dswing.aatext=true -cp ".;lib\bpm.jar;..\..\dctm.jar; C:\Documentum\config" WorkflowEditor -locale en_US 3. In your integrated development environment (IDE), add a new debug configuration to connect the host and port. 56 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Designing the Process 4. Place breakpoints in your code, run this debug configuration from your IDE, and begin debugging your process from Process Builder. Whenever an activity that uses your custom method is reached, you can debug through your custom method code. Note: To make the method code available to the process debugger, it must be a Class that is located in the appropriate directory structure or a JAR file located under \classes\custom folder in the Process Builder installation directory. Process design and Business Activity Monitor (BAM) BAM extracts information from executing processes, runs reports against this information, and provides a dashboard for viewing the reports. Plan to specify the monitoring configuration as you design your process in Process Builder. If you plan on using BAM, you must plan for: • Enabling reporting for BAM, page 58 • Reporting on data in an external database to BAM, page 59 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 57
- Page 5: Table of Contents Chapter 8 Cleanin
- Page 8 and 9: Preface 8 EMC Documentum xCelerated
- Page 10 and 11: Overview • Provides security and
- Page 12 and 13: Overview 12 EMC Documentum xCelerat
- Page 14 and 15: Product Overview Documentum ECM pla
- Page 16 and 17: Product Overview Process automation
- Page 18 and 19: Planning and Designing the Applicat
- Page 20 and 21: Planning and Designing the Applicat
- Page 22 and 23: Planning and Designing the Applicat
- Page 24 and 25: Planning and Designing the Applicat
- Page 26 and 27: Planning and Designing the Applicat
- Page 28 and 29: Planning and Designing the Applicat
- Page 30 and 31: Creating the Data Model submitter_a
- Page 32 and 33: Creating the Data Model should occu
- Page 34 and 35: Designing the Process Defining acti
- Page 36 and 37: Designing the Process The transitio
- Page 38 and 39: Designing the Process 2. Add a seco
- Page 40 and 41: Designing the Process The end resul
- Page 42 and 43: Designing the Process To copy all v
- Page 44 and 45: Designing the Process because the i
- Page 46 and 47: Designing the Process 3. On the Tim
- Page 48 and 49: Designing the Process 48 EMC Docume
- Page 50 and 51: Designing the Process Inter-process
- Page 52 and 53: Designing the Process In the HTTP I
- Page 54 and 55: Designing the Process For the child
- Page 58 and 59: Designing the Process Enabling repo
- Page 60 and 61: Designing the Process Performance a
- Page 62 and 63: Designing the Process 62 EMC Docume
- Page 64 and 65: Creating the User Interface mind th
- Page 66 and 67: Creating the User Interface Figure
- Page 68 and 69: Creating the User Interface 4. Sele
- Page 70 and 71: Creating the User Interface Figure
- Page 72 and 73: Creating the User Interface Figure
- Page 74 and 75: Creating the User Interface Figure
- Page 76 and 77: Creating the User Interface Adaptor
- Page 78 and 79: Creating the User Interface Figure
- Page 80 and 81: Creating the User Interface 5. Spec
- Page 82 and 83: Creating the User Interface 1. Open
- Page 84 and 85: Creating the User Interface 11. In
- Page 86 and 87: Creating the User Interface Working
- Page 88 and 89: Creating the User Interface 88 EMC
- Page 90 and 91: Monitoring Business Activity • pu
- Page 92 and 93: Monitoring Business Activity (PRS).
- Page 94 and 95: Monitoring Business Activity • Us
- Page 96 and 97: Performance and Scalability System
- Page 98 and 99: Performance and Scalability Factors
- Page 100 and 101: Performance and Scalability Skill-s
- Page 102 and 103: Performance and Scalability
- Page 104 and 105: Performance and Scalability If regi
<strong>Designing</strong> the Process<br />
4. Place breakpoints in your code, run this debug configuration from your IDE, and begin debugging<br />
your process from Process Builder.<br />
Whenever an activity that uses your custom method is reached, you can debug through your<br />
custom method code.<br />
Note: To make the method code available to the process debugger, it must be a Class that is<br />
located in the appropriate directory structure or a JAR file located under \classes\custom folder in<br />
the Process Builder installation directory.<br />
Process design and Business Activity Monitor<br />
(BAM)<br />
BAM extracts information from executing <strong>processes</strong>, runs reports against this information, and<br />
provides a dashboard for viewing the reports. Plan to specify the monitoring configuration as you<br />
design your process in Process Builder. If you plan on using BAM, you must plan for:<br />
• Enabling reporting for BAM, page 58<br />
• Reporting on data in an external database to BAM, page 59<br />
<strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 57
Change language