best grammar app

Implementing your first process in Intalio (Beginner)

Submitted by intalio on Wed, 2011-10-05 18:31
intalio.com
  1. Define how our process will be exposed to the external world
  2. Define the XML schemas for the message data
  3. Integrating two operations from an existing web service

 

Step 5: Create the interface

Let's begin by defining how our process is started, meaning the interface to the process. An interface is represented by a participant that is calling the process. One process can have multiple interfaces, but in this tutorial we'll only use one: the BPMS Console, a standard basic interface used to manage all your processes.

To define an interface, add a new Pool in the diagram (from the Palette, in the Basic BPMN Shapes section) and name it "Client". However, the new pool we have just created will not represent a process that will execute. It is used to represent how the process will be called by the outside world, from other processes, external web service calls, or in our case a human user via the BPMS Console. So, once the pool is created, you will set it to non-executable. Right-click on the new pool, and in the popup menu choose "Set pool non executable".

 

In the non-executable Client pool, add a new Task named "Console Invocation". Use the Message Connection shape (similar to the Flow Connector shape) to connect the "Console Invocation" task to the "Receive Request" shape in your other pool. Use a second Message Connection to connect the "Send Response" shape back to the "Console Invocation" task. Compare your diagram to the picture below (please note that we've organized the pools and tasks differently for simplicity as we continue building the process).

 

Step 6: Define the message schemas

Defining an interface includes defining the messages, to answer the questions "what data does my process need to begin?" and "what data is my process going to send back?". We will answer those questions by using XML Schema elements to define our message content.

It's time to include our first file in the project, an XML schema named GetTime.xsd. This is available in the completed GetTime example which you should have downloaded already. Simply unzip the GetTime example, and drag-and-drop the GetTime.xsd file from there into the Process Explorer in Designer. Make sure it lands in the GetTime folder itself, and not the "build" folder within.

Now in your Process Explorer, you can unfold GetTime.xsd like a folder, to see all the XML elements that can be used to define the structure of each message. Drag the "ns:TimeRequest" node and drop it on the first process message as illustrated below:

 

Choose Set schema element 'TimeRequest' as the content of the message from the popup menu, and you'll see a new icon on the message link illustrating that the schema is defining the message contents. Do the same thing with "ns:TimeResponse" and the second process message.

Tip:If you have lots of messages and have forgotten which schemas define them, you can right-click the message connection and choose Navigate > Show attached Schema element and it will be selected in your Process Explorer.

Step 7: Integrate the web service operations

Intalio|Designer features a full WSDL Visual Browser that displays the structure and operations of a WSDL document graphically. Double-click any WSDL in the Process Explorer to see this view. In addition, you can expand each WSDL from your Process Explorer to access its services and operations. You can also access the messages included in the operations and even the schema that defines the data structure of the operations. You don't need to know any technical details about WSDLs to easily include them in your processes.


Intalio
Intalio delivers private cloud computing solutions that can be deployed on demand or on premises.
best grammar app

About BPMGeek

BPMGeek is an initiative to collaborate and communicate with the growing Business process management community out there. The goal is to help developers connect with experts, ask questions, post their learning and get understanding of BPM Concepts. Often tool specific knowledge of niche areas end up developers perplexed and confused - especially when there are very less number of resources available. We will be coming up several several new features. Have a look at our Roadmap here

BPMGeek is an independent entity not associated with any Product. All BPM product professionals are invited to contribute. The Logos and Names used across the site belong to their respective owners. The viewpoints mentioned by Individual contributors are their own. BPMgeek cannot be held liable for any issues arising out of it.


BPMgeek is promoting the Nounshoun English Grammar App - developed by Constellation Software.