Deploying and Testing your first process in Intalio (Beginner)

Submitted by intalio on Wed, 2011-10-05 18:40
intalio.com

Contributed by Chandra Shekhar

 

 

 

 

 

Abstract

The aim of this document is to let you deploy and test your first process designed in 'Getting Started: Implementing your first process ' guide.
In this guide, you will be introduced to the following concepts:

  • Deployment
  • Execution

Please discuss the document directly in the forums.

Pre-requisities

Before you start digging in this document please make sure that both Designer and the runtime components are installed and running properly in your environment. The complete GetTime process is also required. You can find it in the in the library under 'Processes/Implemented Processes'

Validating and Deploying your process

Intalio|BPMS Designer will compile your process after each change indicating in real-time all the errors that are preventing the process from being deployed and executed. The list of problems is available in the problem view as well as directly on the process model.
Indeed each shape that is not correctly implemented (missing data elements, wrong mappings, invalid BPMN sequence...) is marked by a red cross so is the process in the Process Explorer.

Once your process is ready to be executed, simply click on the deployment bundle icon to open the deployment menudeploymenticon.jpg

 

The deployment menu allows you to choose the processes to deploy as well as their dependencies. Please note that when you select one process to deploy, the dependencies are automatically selected. You are free to select the dependencies that you want to deploy.
For instance it allows you to switch between the deployment of a test process that returns always the same data and the deployment of the real implemented process.

By default the process will be deployed on the same machine where Designer is running.
You can change the location of your process server by accessing Intalio|Designer preferences which will allow you to do remote deployment.

 

The different artifacts generated are:

  • the BPEL code corresponding to the process
  • the different WSDLs used by the process to represent its interactions with other participants (partner links)
  • the different WSDLs used to represent external services
  • the compiled BPEL code in Pi-Calculus
  • a Deployment descriptor specific to Intalio|Server
  • an SVG representation of the process used for dynamic process monitoring
  • The custom initialization of variables if applicable
  • The deployment descriptor for the forms

You will notice that Intalio|BPMS Designer allows you to deploy either the processes or the forms or both at the same time.
Intalio|BPMS Designer Deployment Wizard is the central wizard to deploy all the different files required to run a process.
You don't have to deal with multiple build environments and multiple XML files.
Intalio|BPMS Designer deploys them for you.

 

Starting the process in Intalio|BPMS Console

Let's connect to Intalio|BPMS Console to ensure that our process is deployed correctly.
Open a browser to http://localhost:8080/bpms-console and use the credentials 'admin/changeit' to log in.
Please note that you can open your browser directly from Intalio|BPMS Designer allowing you to do everything in one single tool.


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

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.