O v e r vi ew
In this exercise, Kevin Parker will first import the modified BPMN model from Marc Allen.
Kevin will then add missing technical details to the process by reusing existing webMethods components.
Finally, he will change Abstract Task types to technical Task types (like Service Tasks or User Tasks) and refine the conditional transitions.
S t ep s
1. To save memory on your VM, close ARIS Business Architect.
2. In the Windows Services Control Panel start the Software AG Integration Server.
Note: This action may take a few minutes to complete.
3. Use the Integration Server (IS) Administration console:
a) To connect to the Integration Server Administration console, open a web browser and enter the URL http://localhost:5555 or use the shortcut labeled Integration Server in the browser’s bookmarks toolbar.
If the Integration Server started successfully, you’ll get prompted for authentication.
Provide Administrator |manage as user credentials.
Note: It takes a few minutes for the Integration Server to startup; therefore refresh the web page until you are asked to enter the User Name and Password.
b) In the IS console click on Packages -> Management to see the list of available IS packages.
c) Supporting assets for the Employ Worker process are provided in the existing (but disabled) IS package M2EProcessesSupport. Click on the link labeled No in column Enabled to activate this package in the Integration Server.
Confirm with OK. You should get the message:
d) Logoff from IS Administration Console and close the browser tab.
4. Start Software AG Designer (if not active).
5. In Designer, ensure you are in the Process Development perspective. Open the Package Navigator view and right-click server named Default. Choose Connect to Server.
After connecting, expand Default and ensure IS package M2EProcessesSupport is displayed in the tree view of IS assets.
6. Additionally, import a CAF project that contains the User Task UI implementation.
a) In Designer’s Solution view, right-click Default Solution – Tasks and select Import… . In the wizard, select Software AG - >Existing CAF projects into Workspace and click Next.
b) On the next panel browse for the archive file
<workshop-dir>\Student\Exercise 6\Resources\M2ETasks.zip and click Finish.
7. Now Kevin Parker will re-import the updated BPMN model from ARIS:
a) In Designer’s ARIS Tasks view, click the refresh icon.
b) A new M2E task named ‘Import updated process: Employ Worker’ should be displayed.
Right-click on the task and select Import.
c) In the import wizard, select the existing project M2EProcesses and click OK to allow overwriting of the existing BPMN process model Employ Worker. Click Finish and then Yes to All.
d) Briefly inspect and close the import report.
8. Performing the M2E task ‘Import updated process’ from the ARIS Tasks view in Designer causes a state transition of the process to ‘In development’, sends out e-mails to the process engineer(s), and produces new M2E tasks to become available for process developer(s) and process engineer(s).
a) Use Mozilla Thunderbird to look for new e-mails sent to process engineer Marc Allen.
9. Use Designer to re-open process Employ Worker from the Solutions view.
Verify that all changes made by Marc Allen in the last exercise have been transferred.
10. With the process loaded into the editor, ensure you are working in the Process Developer mode of the Process Development perspective.
11. Perform the following technical enhancements:
a) Drag IS service m2EProcessesSupport.services:assignOffice from the left-hand Package Navigator view on top of the Abstract Task Activity Assign Office in the process editor. As a result, the Abstract Task is automatically converted into a Service Task Activity of type IS service and all technical webMethods properties have been set properly.
b) In the same way assign the following IS services to the corresponding Abstract Task Activity:
i) m2EProcessesSupport.services:requestComputer -> Request Computer ii) m2EProcessesSupport.services:scheduleNewHireTraining ->
Schedule New Hire Training
c) From the Package Navigator view, drag the IS Web service connector
m2EProcessesSupport.services.webservices.calculateSalaryWS_.connectors:
calculateSalaryWSProvider_PortType_calculateSalary on top of the Abstract Task Activity Calculate Salary in the process editor. As a result, the Abstract Task is automatically converted into a Service Task Activity of type Web service and all technical webMethods properties have been set properly.
d) In the Solutions view, navigate to Default Solution -> Tasks -> M2ETasks and drag the User Task implementation ReviewEmployeeData on top of the User Task Activity Review Employee Data in the process editor.
Select the User Task Activity Review Employee Data in the editor and open the Inputs/Outputs tab in the Properties view. If you do not see Inputs/Outputs defined, click the Refresh icon . This will load the Input/Output definitions.
e) In the process editor, select the transition from Gateway Split to Gateway Join. In the Condition tab of the Properties view, set Transition Type to If Condition and then click the Add icon to create a new row in the table of conditions. In the first table row, open the drop down within column Field Name and select the business data field Employee/ComputerType. In column Operator select = and enter the value None in column Comparison Value/Field.
f) Select the transition from Gateway Split to Abstract Task Notify Computer Center.
In the Condition tab of the Properties view, select Transition Type Default.
g) From a technical point of view, Abstract Task Signal Employee Acceptance has to be implemented in two BPMN nodes. A first node to create the Signal data, and a second node to send the signal out:
i) Remove the transition between Abstract Task Signal Employee Acceptance and End Terminate Event Employee Acceptance signaled.
ii) Use the Palette to insert an Intermediate Signal Event between Signal Employee Acceptance and Event Employee Acceptance.
Select the new Signal Event in the process editor. In the related Properties view, rename the Signal Event to Signal Employee Acceptance on the General tab.
On the Implementation tab of the Properties view, change the Event type to Throw Event and browse for the Document type
m2EProcessesSupport.docs:EmployeeAcceptance to be thrown.
iii) Select Abstract Task Signal Employee Acceptance in the process editor and rename it in its Properties view to Create Employee Acceptance.
iv) Drag IS service m2EProcessesSupport.services:createEmployeeAcceptance from the Package Navigator view on top of the Abstract Task Activity Create Employee Acceptance in the process editor. As a result, the Abstract Task is automatically converted into a Service Task Activity of type IS service and all technical
webMethods properties have been set properly.
v) Add a transition from Service Task Activity Create Employee Acceptance to the Intermediate Signal Event Signal Employee Acceptance.
vi) Add another transition from Intermediate Signal Event Signal Employee Acceptance to the End Terminate Event Employee Acceptance signaled.
Your technical BPMN process model should now look like this:
h) To configure the message types to be received by the Start Message Events perform the following steps:
i) From the Package Navigator view, drag the IS document type
m2EProcessesSupport.docs:Employee onto the Start Message Event Employee received.
ii) Drag the IS document type m2EProcessesSupport.docs:EmployeeContract onto the Start Message Event Employee Contract signed.
i) Save and close your process model in Designer.