Author: bbrodt Date: 2010-07-13 20:52:09 -0400 (Tue, 13 Jul 2010) New Revision: 23395 Added: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_8.png trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_9.png trunk/bpel/docs/reference/en-US/images/detail_assign1.png trunk/bpel/docs/reference/en-US/images/detail_assign2.png trunk/bpel/docs/reference/en-US/images/detail_assign3.png trunk/bpel/docs/reference/en-US/images/detail_createprocess_2a.png trunk/bpel/docs/reference/en-US/images/details_createproject_1.png trunk/bpel/docs/reference/en-US/images/reference/bpel_ref_3a.png Modified: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_1.png trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_2.png trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_3.png trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_4.png trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_5.png trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_6.png trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_7.png trunk/bpel/docs/reference/en-US/images/detail_createprocess_1.png trunk/bpel/docs/reference/en-US/images/detail_createprocess_2.png trunk/bpel/docs/reference/en-US/images/detail_createprocess_3.png trunk/bpel/docs/reference/en-US/images/detail_createproject_1.png trunk/bpel/docs/reference/en-US/images/detail_createproject_2.png trunk/bpel/docs/reference/en-US/images/detail_editprocess_1.png trunk/bpel/docs/reference/en-US/images/detail_editprocess_2.png trunk/bpel/docs/reference/en-US/images/reference/bpel_ref_3.png trunk/bpel/docs/reference/en-US/images/reference/bpel_ref_4.png trunk/bpel/docs/reference/en-US/master.xml trunk/bpel/docs/reference/en-US/modules/install.xml trunk/bpel/docs/reference/en-US/modules/overview.xml trunk/bpel/docs/reference/en-US/modules/reference.xml trunk/bpel/docs/reference/en-US/modules/summary.xml trunk/bpel/docs/reference/en-US/modules/tasks.xml Log: Update BPEL User Guide https://jira.jboss.org/browse/TOOLSDOC-90 Modified: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_1.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_2.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_3.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_4.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_5.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_6.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_7.png =================================================================== (Binary files differ) Added: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_8.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_9.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en-US/images/deploy_createdeploy_9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en-US/images/detail_assign1.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en-US/images/detail_assign1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en-US/images/detail_assign2.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en-US/images/detail_assign2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en-US/images/detail_assign3.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en-US/images/detail_assign3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/bpel/docs/reference/en-US/images/detail_createprocess_1.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/detail_createprocess_2.png =================================================================== (Binary files differ) Added: trunk/bpel/docs/reference/en-US/images/detail_createprocess_2a.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en-US/images/detail_createprocess_2a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/bpel/docs/reference/en-US/images/detail_createprocess_3.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/detail_createproject_1.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/detail_createproject_2.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/detail_editprocess_1.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/images/detail_editprocess_2.png =================================================================== (Binary files differ) Added: trunk/bpel/docs/reference/en-US/images/details_createproject_1.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en-US/images/details_createproject_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/bpel/docs/reference/en-US/images/reference/bpel_ref_3.png =================================================================== (Binary files differ) Added: trunk/bpel/docs/reference/en-US/images/reference/bpel_ref_3a.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en-US/images/reference/bpel_ref_3a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/bpel/docs/reference/en-US/images/reference/bpel_ref_4.png =================================================================== (Binary files differ) Modified: trunk/bpel/docs/reference/en-US/master.xml =================================================================== --- trunk/bpel/docs/reference/en-US/master.xml 2010-07-14 00:02:21 UTC (rev 23394) +++ trunk/bpel/docs/reference/en-US/master.xml 2010-07-14 00:52:09 UTC (rev 23395) @@ -1,57 +1,56 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" -"http://www.docbook.org/xml/4.3/docbookx.dtd" - -[<!ENTITY overview SYSTEM "modules/overview.xml"> -<!ENTITY install SYSTEM "modules/install.xml"> -<!ENTITY detail SYSTEM "modules/detail.xml"> -<!ENTITY deploy SYSTEM "modules/deploy.xml"> -<!ENTITY reference SYSTEM "modules/reference.xml"> -<!ENTITY summary SYSTEM "modules/summary.xml"> -<!ENTITY tasks SYSTEM "modules/tasks.xml"> -]> - -<book> - - <bookinfo> - <title>JBoss BPEL User Guide</title> - - <corpauthor> - <inlinemediaobject> - <imageobject role="fo"> - <imagedata format="PNG" fileref="images/jbosstools_logo.png" /> - </imageobject> - <imageobject role="html"> - <imagedata/> - </imageobject> - </inlinemediaobject> - </corpauthor> - <author&gt;&lt;firstname&gt;Denny&lt;/firstname&gt;&lt;surname&gt;Xu&lt;/surname&gt;&lt;email&gt;dxu(a)redhat.com&lt;/email&gt;&lt;/author&gt; - <author&gt;&lt;firstname&gt;Grid&lt;/firstname&gt;&lt;surname&gt;Qian&lt;/surname&gt;&lt;email&gt;fqian(a)redhat.com&lt;/email&gt;&lt;/author&gt; - <copyright> - <year>2009</year> - <year>2010</year> - <holder>JBoss by Red Hat</holder> - </copyright> - <releaseinfo> - Version: 1.0.0.trunk - </releaseinfo> -<abstract> - <title/> - <para> - <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/bpel_ref_g... version</ulink> - </para> -</abstract> - - - </bookinfo> - - <toc/> - &overview; - &install; - &tasks; - <!-- &detail; - &deploy;--> - &reference; - &summary; -</book> +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" +"http://www.docbook.org/xml/4.3/docbookx.dtd" + +[<!ENTITY overview SYSTEM "modules/overview.xml"> +<!ENTITY install SYSTEM "modules/install.xml"> +<!ENTITY detail SYSTEM "modules/detail.xml"> +<!ENTITY deploy SYSTEM "modules/deploy.xml"> +<!ENTITY reference SYSTEM "modules/reference.xml"> +<!ENTITY summary SYSTEM "modules/summary.xml"> +<!ENTITY tasks SYSTEM "modules/tasks.xml"> +]> +<book> + <bookinfo> + <title>JBoss BPEL User Guide</title> + <corpauthor> + <inlinemediaobject> + <imageobject role="fo"> + <imagedata fileref="images/jbosstools_logo.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata/> + </imageobject> + </inlinemediaobject> + </corpauthor> + <author> + <firstname>Denny</firstname> + <surname>Xu</surname> + <email&gt;dxu(a)redhat.com&lt;/email&gt; + </author> + <author> + <firstname>Grid</firstname> + <surname>Qian</surname> + <email&gt;fqian(a)redhat.com&lt;/email&gt; + </author> + <author> + <firstname>Bob</firstname> + <surname>Brodt</surname> + <email&gt;bbrodt(a)redhat.com&lt;/email&gt; + </author> + <copyright> + <year>2009</year> + <year>2010</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo> Version: 1.0.0.trunk </releaseinfo> + <abstract> + <title/> + <para> + <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/bpel_ref_g... version</ulink> + </para> + </abstract> + </bookinfo> + <toc/> +&overview;&install;&tasks;<!-- &detail; + &deploy;-->&reference;&summary;</book> Modified: trunk/bpel/docs/reference/en-US/modules/install.xml =================================================================== --- trunk/bpel/docs/reference/en-US/modules/install.xml 2010-07-14 00:02:21 UTC (rev 23394) +++ trunk/bpel/docs/reference/en-US/modules/install.xml 2010-07-14 00:52:09 UTC (rev 23395) @@ -1,62 +1,59 @@ -<?xml version="1.0" encoding="ISO-8859-1"?> -<chapter id="install"> - <title>Installation JBoss BPEL Tools</title> - <section id="installeclipse"> - <title>Installation JBoss BPEL editor</title> - <para>At first, you need Eclipse 3.5. You can get it from <ulink url="http://www.eclipse.org/downloads/download.php?file=/technology/... Web Site</ulink>. - </para> - <para>The JBoss BPEL editor is included into JBoss Tools. - You have some methods to install JBoss Tools. - See <ulink url="http://www.jboss.org/tools/download/installation.html">... JBoss Tools</ulink> for more information.</para> - <para>If you want to install only the JBoss BPEL editor, you can install it from <ulink url="http://jboss.org/tools/download/dev.html">JBoss Tools</ulink> page separately. - Please, note, that only JBoss Tools 3.1 or higher version includes JBoss BPEL editor. - </para> - </section> - <section> - <title>Prerequisites</title> - <para>For installation and configuring BPEL engine into a JBossAS environment - you will need the following: </para> - <itemizedlist> - <listitem><para> JBossAS (version 5.1.0.GA or higher), - available from <ulink url="http://www.jboss.org/jbossas"> - http://www.jboss.org/jbossas</ulink>.</para></listitem> - <listitem><para>RiftSaw (version 2.0 or higher), available from <ulink url="http://www.jboss.org/riftsaw">http://www.jboss.org/rift... - <listitem><para>Ant, available from <ulink url="http://ant.apache.org">here</ulink>.</para></listitem> - </itemizedlist> - - </section> - <section id="installRuntime"> - <title>Installation JBoss BPEL Runtime</title> - <itemizedlist> - <listitem> - <para>Unpack the JBossAS installation archive into the required location. - </para> - </listitem> - <listitem> - <para>Unpack the RiftSaw distribution into the location - alongside the JBossAS installation:</para> - <itemizedlist> - <listitem> - <para>Edit the <property>install/deployment.properties</property> file to update - the JBossAS location settings. - </para> - </listitem> - <listitem> - <para>From the <property>install</property> folder, - run: <property>ant deploy -Ddatabase=hsql</property> - to deploy RiftSaw to JBossAS. - </para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para>Then in the - <property>${RiftSaw}/install</property> folder run the command: - <property>ant deploy -Ddatabase=hsql -Dws.stack=native -Dws.version=3.2.2.GA</property> - It will help you to download the web service stack, and then upgrade it for JBoss AS. - </para> - </listitem> - </itemizedlist> - - </section> +<?xml version='1.0' encoding='ISO-8859-1'?><chapter id="install"> + <title>Installating the JBoss BPEL Tools</title> + <section id="installeclipse"> + <title>BPEL Editor</title> + <para>The JBoss BPEL Editor and deployment framework are available in the community-supported distribution of JBoss Tools and are now also bundled into the commerically available JBoss Developer Studio (JBDS). As of this writing, the tools can be installed from the JBoss update site using either the Eclipse 3.5 Galileo or Eclipse 3.6 Helios releases. The Eclipse distributions can be downloaded from the <ulink url="http://eclipse.org/downloads/">Eclipse Web Site</ulink>. + </para> + <para>The JBoss BPEL Editor may also be installed as a stand-alone plug-in. See <ulink url="http://www.jboss.org/tools/download/installation.html">... JBoss Tools</ulink> for more information.</para> + </section> + <section> + <title>Prerequisites</title> + <para>For installation and configuring BPEL engine into a JBossAS environment + you will need the following: </para> + <itemizedlist> + <listitem> + <para> JBossAS (version 5.1.0.GA or higher), + available from <ulink url="http://www.jboss.org/jbossas"> http://www.jboss.org/jbossas</ulink>.</para> + </listitem> + <listitem> + <para>RiftSaw (version 2.0 or higher), available from <ulink url="http://www.jboss.org/riftsaw">http://www.jboss.org/rift... + </listitem> + <listitem> + <para>Ant, available from <ulink url="http://ant.apache.org">here</ulink>.</para> + </listitem> + </itemizedlist> + </section> + <section id="installRuntime"> + <title>BPEL (Riftsaw) Runtime</title> + <itemizedlist> + <listitem> + <para>Unpack the JBossAS installation archive into the required location. + </para> + </listitem> + <listitem> + <para>Unpack the RiftSaw distribution into the location + alongside the JBossAS installation:</para> + <itemizedlist> + <listitem> + <para>Edit the <property>install/deployment.properties</property> file to update + the JBossAS location settings. + </para> + </listitem> + <listitem> + <para>From the <property>install</property> folder, + run: <property>ant deploy -Ddatabase=hsql</property> + to deploy RiftSaw to JBossAS. + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para>Then in the + <property>${RiftSaw}/install</property> folder run the command: + <property>ant deploy -Ddatabase=hsql -Dws.stack=native -Dws.version=3.2.2.GA</property> + It will help you to download the web service stack, and then upgrade it for JBoss AS. + </para> + </listitem> + </itemizedlist> + </section> </chapter> \ No newline at end of file Modified: trunk/bpel/docs/reference/en-US/modules/overview.xml =================================================================== --- trunk/bpel/docs/reference/en-US/modules/overview.xml 2010-07-14 00:02:21 UTC (rev 23394) +++ trunk/bpel/docs/reference/en-US/modules/overview.xml 2010-07-14 00:52:09 UTC (rev 23395) @@ -1,67 +1,29 @@ -<?xml version="1.0" encoding="ISO-8859-1"?> -<chapter id="overview"> - <title>JBoss BPEL project Overview</title> - - <para>JBoss BPEL project is a WS-BPEL 2.0 project that gives a way to create, edit, validate and deploy BPEL files to JBoss BPEL runtime. It is based on Eclipse - <ulink url="http://www.eclipse.org/bpel/">BPEL - project </ulink>. </para> - - <para>It improves the Eclipse BPEL project in the following way: </para> - <itemizedlist> - <listitem><para> Implements close integration with JBoss BPEL runtime. Adds a new project type for the deployment to JBoss BPEL runtime.</para></listitem> - <listitem><para> Supports two ways of deployment: one way is to deploy a bpel project directly to JBoss BPEL runtime. The other way is to deploy bpel files in JBoss ESB project to JBoss BPEL runtime. </para></listitem> - <listitem><para> Improves the BPEL validator and increases Eclipse BPEL editor's quality. </para></listitem> - </itemizedlist> - - <para> - <ulink url="http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html&qu... 2.0</ulink> - stands for Web Service Business Process Execution Language. Like EAI, BPEL is an XML-based language, - but BPEL is more specific and targeted. A programmer uses BPEL to join sometimes - disparate functions into an integrated process, resulting in a seamless use of the Internet to - conduct business transactions ranging from simple money exchanges to complex calculations and - asset reallocation. - </para> - -<section> - <title>Key Features of JBoss BPEL project</title> - <para>Let's start with looking through the table of the main features of JBoss BPEL editor project: </para> - - <table> - - <title>Key Functionality for JBoss BPEL editor project</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="2*"/> - <colspec colnum="2" colwidth="4*"/> - <thead> - <row> - <entry>Feature</entry> - <entry>Benefit</entry> - - </row> - </thead> - <tbody> - <row> - <entry><para>WS-BPEL 2.0 support</para></entry> - <entry><para>JBoss BPEL project supports the newest WS-BPEL 2.0 specifications. </para></entry> - </row> - <row> - <entry><para>Close integration with JBoss BPEL runtime</para></entry> - <entry><para>There are two ways to deploy BPEL files to JBoss BPEL runtime. - The user can deploy a BPEL project as a whole and can deploy BPEL files in - JBoss ESB project to JBoss BPEL runtime. </para></entry> - </row> - <row> - <entry><para>BPEL file editor</para></entry> - <entry><para>The user can use the editor separately to edit a BPEL file. </para></entry> - </row> - <row> - <entry><para>BPEL file validator</para></entry> - <entry><para>The validator can give the error messages about BPEL files to the user. </para></entry> - </row> - </tbody> - </tgroup> - </table> - -</section> - +<?xml version='1.0' encoding='ISO-8859-1'?><chapter id="overview"> + <title>JBoss BPEL Tooling Overview</title> + <para>JBoss Tools now includes a BPEL (Business Process Execution Language) editor that is WS-BPEL 2.0 compliant.</para> + <para><footnote label="*"> + <para> + <ulink url="http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html&qu... 2.0</ulink> + stands for Web Service Business Process Execution Language. Like EAI, BPEL is an XML-based language, + but BPEL is more specific and targeted. Typically, BPEL is used to &quot;orchestrate&quot; or join disparate web services into an integrated process, resulting in a seamless use of the Internet to + conduct business transactions ranging from simple money exchanges to complex calculations and + asset reallocation.</para> + </footnote>The editor is based on the Eclipse + <ulink url="http://www.eclipse.org/bpel/">BPEL project </ulink> with some additional enhancements and numerous bug fixes. In addition, a deployment framework allows BPEL processes to be deployed to, and executed by the Riftsaw BPEL execution engine which + is based on the Apache ODE engine (version 1.3.4 as of this writing). Please refer to the <ulink url="http://jboss.org/riftsaw">Riftsaw website</ulink> for more information.</para> + <para>Here are just some of the new features of the JBoss Tools BPEL editor: </para> + <itemizedlist> + <listitem> + <para>Close integration with the Riftsaw BPEL runtime: a new Eclipse project type has been defined to allow simple, one-click deployment.</para> + </listitem> + <listitem> + <para>Increased reliability and language validation over the Eclipse BPEL project.</para> + </listitem> + <listitem> + <para>Enhanced &quot;New Process Wizard&quot; that generates a complete, ready-to-run process on a local server without additional WSDL configuration.</para> + </listitem> + <listitem> + <para>Improved BPEL Console for simple monitoring and control of BPEL processes.</para> + </listitem> + </itemizedlist> </chapter> \ No newline at end of file Modified: trunk/bpel/docs/reference/en-US/modules/reference.xml =================================================================== --- trunk/bpel/docs/reference/en-US/modules/reference.xml 2010-07-14 00:02:21 UTC (rev 23394) +++ trunk/bpel/docs/reference/en-US/modules/reference.xml 2010-07-14 00:52:09 UTC (rev 23395) @@ -1,386 +1,379 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="reference"> - <?dbhtml filename="reference.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Tools</keyword> - <keyword>BPEL</keyword> - <keyword>JBT</keyword> - </keywordset> - </chapterinfo> - <title>Reference</title> - <para>This chapter includes detailed reference information about all BPEL tools wizards and editors.</para> +<?xml version='1.0' encoding='UTF-8'?><chapter id="reference"> +<?dbhtml filename="reference.html"?> <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>BPEL</keyword> + <keyword>JBT</keyword> + </keywordset> + </chapterinfo> + <title>Reference</title> + <para>This chapter includes detailed reference information about all BPEL tools wizards and editors.</para> + <section> + <title>Wizards</title> <section> - <title>Wizards</title> - <section> - <title>New BPEL project Wizard</title> - <para>This wizard helps to create new BPEL project.It is available with clicking - <property>File->New->Other->BPEL project</property> in the menu bar.</para> - <figure> - <title>New BPEL Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>It consists of only one page:</para> - <itemizedlist> - <listitem><para>On the page you can adjust the name of the project and the directory where it will be created.</para> - <para>If "<property>Use default</property>" option is checked the output directory will be the workspace, + <title>New BPEL project Wizard</title> + <para>This wizard helps to create new BPEL project.It is available with clicking + <property>File-&gt;New-&gt;Other-&gt;BPEL project</property> in the menu bar.</para> + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>It consists of only one page:</para> + <itemizedlist> + <listitem> + <para>On the page you can adjust the name of the project and the directory where it will be created.</para> + <para>If &quot;<property>Use default</property>&quot; option is checked the output directory will be the workspace, othervise the user should specify it by himself using <property>Browse</property> button.</para> - <figure> - <title>New BPEL Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_2.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - </section> - <section> - <title>Apache ODE Deployment Descriptor Wizard</title> - <para>Using this wizard user can create ODE deployment descriptor (deploy.xml) and place it in the temporary directory.It is available with clicking - <property>File->New->Other->Apache ODE Deployment Descriptor Wizard</property> in the menu bar.</para> - <figure> - <title>New BPEL Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_2a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>On the page you can adjust the name of the deployment descriptor and - the directory where it will be created.Note,that you should use <property> - /PROJECT_NAME/bpelContent</property> directory as an output one.</para> - - </section> - <section> - <title>New BPEL Process file Wizard</title> - <para>Using <property>New BPEL Process file Wizard</property> + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + <section> + <title>Apache ODE Deployment Descriptor Wizard</title> + <para>Using this wizard user can create ODE deployment descriptor (deploy.xml) and place it in the temporary directory.It is available with clicking + <property>File-&gt;New-&gt;Other-&gt;Apache ODE Deployment Descriptor Wizard</property> in the menu bar.</para> + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_2a.png"/> + </imageobject> + </mediaobject> + </figure> + <para>On the page you can adjust the name of the deployment descriptor and + the directory where it will be created.Note,that you should use <property> /PROJECT_NAME/bpelContent</property> directory as an output one.</para> + </section> + <section> + <title>New BPEL Process file Wizard</title> + <para>Using <property>New BPEL Process file Wizard</property> user can create BPEL process file and WSDL file if it is necessary. The wizard includes several pages:</para> - <itemizedlist> - <listitem><para>The first page has the following options to set:</para> - <table> - <title>New BPEL Process file Wizard. First Page Options.</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" align="left" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - - <thead> - <row> - <entry>Option</entry> - <entry>Description</entry> - <entry>Default</entry> - </row> - </thead> - <tbody> - <row> - <entry>Name</entry> - <entry>Enter the process name.</entry> - <entry>no default value</entry> - </row> - - - <row> - <entry>Namespace</entry> - <entry>Enter the namespace url here</entry> - <entry>no default value</entry> - </row> - - <row> - <entry>Template</entry> - <entry>Select one of the provided templates: - <itemizedlist> - <listitem><para><emphasis>Asynchronous BPEL Process</emphasis> - + <itemizedlist> + <listitem> + <para>The first page has the following options to set:</para> + <table> + <title>New BPEL Process file Wizard. First Page Options.</title> + <tgroup cols="3"> + <colspec colnum="1" colwidth="1*" align="left"/> + <colspec colnum="2" colwidth="3*" align="left"/> + <colspec colnum="3" colwidth="1*" align="left"/> + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + <row> + <entry>Name</entry> + <entry>Enter the process name.</entry> + <entry>no default value</entry> + </row> + <row> + <entry>Namespace</entry> + <entry>Enter the namespace url here</entry> + <entry>no default value</entry> + </row> + <row> + <entry>Template</entry> + <entry>Select one of the provided templates: <itemizedlist> + <listitem> + <para><emphasis>Asynchronous BPEL Process</emphasis> - generates the basis of orchestration logic: receive and reply activities are included into the process;client WSDL is generated, service is defined in the <property>parentlink</property> of the process. The caller is notified asynchronously when the process completes. - </para></listitem> - <listitem><para><emphasis>Empty BPEL Process</emphasis> - list of services participating in this BPEL process together - with the one of messages used within the process is empty.There are no any orchestration logic.</para></listitem> - <listitem><para><emphasis>Synchronous BPEL Process</emphasis> - + </para> + </listitem> + <listitem> + <para><emphasis>Empty BPEL Process</emphasis> - list of services participating in this BPEL process together + with the one of messages used within the process is empty.There are no any orchestration logic.</para> + </listitem> + <listitem> + <para><emphasis>Synchronous BPEL Process</emphasis> - similar to Asynchronous BPEL Process template except the fact that here - the caller is notified synchronously when the process completes.</para></listitem> - </itemizedlist></entry> - <entry>Asynchronous BPEL Process</entry> - </row> - <row> - <entry>Abstract Process</entry> - <entry>Specifies the created process as an abstract one -partially - specified processes that are not intended to be executed.</entry> - <entry>unchecked</entry> - </row> - </tbody> - </tgroup> - </table> - <figure> - <title>New BPEL Process file Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_3.png"/> - </imageobject> - </mediaobject> - </figure> - - </listitem> - <listitem><para>On the second page the user should select the BPEL project + the caller is notified synchronously when the process completes.</para> + </listitem> + </itemizedlist></entry> + <entry>Asynchronous BPEL Process</entry> + </row> + <row> + <entry>Abstract Process</entry> + <entry>Specifies the created process as an abstract one -partially specified processes that are not intended to be executed.</entry> + <entry>unchecked</entry> + </row> + </tbody> + </tgroup> + </table> + <figure> + <title>New BPEL Process file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_3.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>The second page allows you to define the service endpoint and binding protocol:</para> + <figure> + <title>New BPEL Process file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_3a.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>The third page is used to select the BPEL project and folder where the process file will be created:</para> - <figure> - <title>New BPEL Process file Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_4.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - <note> - <para>Process files that are used in the BPEL project must be under the <property>bpelContent</property> folder. Only in this case - these files can be deployed to JBoss server. - </para> - </note> - </section> + <figure> + <title>New BPEL Process file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <note> + <para>Process files that are used in the BPEL project must be located in the <property>bpelContent</property> folder.</para> + </note> </section> + </section> + <section> + <title>Editors</title> <section> - <title>Editors</title> - <section> - <title>Business Process Editor</title> - <para>Business Process Editor is intended to facilitate the process of changing and + <title>Business Process Editor</title> + <para>Business Process Editor is intended to facilitate the process of changing and adding new logic to BPEL process file.You can open <emphasis>.bpel</emphasis> in this editor by right click the file in the project explorer and selecting - <property>Open With...->Business Process Editor</property> + <property>Open With...-&gt;Business Process Editor</property> </para> + <figure> + <title>Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_5.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The editor consists of two tabs:<property>Design</property> tab and <property>Source</property> tab.</para> + <section> + <title>Design tab</title> + <para>Design tab is the main part of Business Process Editor.It consists of 3 parts:</para> + <itemizedlist> + <listitem> + <para>Visual Pane:</para> <figure> - <title>Business Process Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_5.png"/> - </imageobject> - </mediaobject> + <title>Visual Pane of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_6.png"/> + </imageobject> + </mediaobject> </figure> - <para>The editor consists of two tabs:<property>Design</property> tab and <property>Source</property> tab.</para> - <section> - <title>Design tab</title> - <para>Design tab is the main part of Business Process Editor.It consists of 3 parts:</para> - <itemizedlist> - <listitem><para>Visual Pane:</para> - <figure> - <title>Visual Pane of Business Process Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_6.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The Visual Pane graphically displays the order in which the activities are executed.</para> - </listitem> - <listitem><para>Palette:</para> - <figure> - <title>Palette of Business Process Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_7.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The <property>Palette</property> represents different elements of the BPEL activities + <para>The Visual Pane graphically displays the order in which the activities are executed.</para> + </listitem> + <listitem> + <para>Palette:</para> + <figure> + <title>Palette of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_7.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The <property>Palette</property> represents different elements of the BPEL activities organized into functional categories. Using it the user can easily add new elements to the sequence activity. To do this,he should just click the required element and then drug and drop it to the place on the Visual Pane where it should be added.</para> - </listitem> - <listitem><para>Behavior Components View:</para> - <figure> - <title>Behavior Components View of Business Process Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_8.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Execution behavior components are grouped into the <property> - Behavior Components View</property>. + </listitem> + <listitem> + <para>Behavior Components View:</para> + <figure> + <title>Behavior Components View of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_8.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Execution behavior components are grouped into the <property> Behavior Components View</property>. The view is also fully syncronized with Properties view where you can customize all the properties of the component.</para> - <figure> - <title>Process Structure View of Business Process Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_9.png"/> - </imageobject> - </mediaobject> - </figure> - <para>To add an element to some component group click plus(<inlinemediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_10.png"/> - </imageobject> - </inlinemediaobject>) icon, + <figure> + <title>Process Structure View of Business Process Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_9.png"/> + </imageobject> + </mediaobject> + </figure> + <para>To add an element to some component group click plus(<inlinemediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_10.png"/> + </imageobject> + </inlinemediaobject>) icon, for its deleting you should click the element and - use its <property>Delete</property> option in the popup menu.</para> - </listitem> - - </itemizedlist> - - - </section> - <section> - <title>Source tab</title> - <para>Source tab can be used for editing BPEL process file directly. + use its <property>Delete</property> option in the popup menu.</para> + </listitem> + </itemizedlist> + </section> + <section> + <title>Source tab</title> + <para>Source tab can be used for editing BPEL process file directly. The validation of file structure is also available. </para> - <figure> - <title>Validation error in Source tab</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_11.png"/> - </imageobject> - </mediaobject> - </figure> - <para>If the user wants to disable/unable validation he can do it by following - <property>Window->Preferences->Validation</property>.</para> - <figure> - <title>Validation configuration</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_12.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - </section> - <section> - <title>ODE Deployment Descriptor Editor</title> - <para>To deploy your process in Ode you need to create a + <figure> + <title>Validation error in Source tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_11.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If the user wants to disable/unable validation he can do it by following + <property>Window-&gt;Preferences-&gt;Validation</property>.</para> + <figure> + <title>Validation configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_12.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section> + <title>ODE Deployment Descriptor Editor</title> + <para>To deploy your process in Ode you need to create a simple deployment descriptor with basic information and <property>ODE Deployment Descriptor Editor</property> facilitates the process of descriptor configuration. You can see how the descriptor file,opened in the editor looks like on the picture below: </para> - <figure> - <title>ODE Deployment Descriptor Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/reference/bpel_ref_13.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The table below describes the configuration options of the + <figure> + <title>ODE Deployment Descriptor Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/reference/bpel_ref_13.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The table below describes the configuration options of the ODE Deployment Descriptor Editor:</para> - <table> - <title>ODE Deployment Descriptor Editor.Options.</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" align="left" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - - <thead> - <row> - <entry>Section</entry> - <entry>Options</entry> - <entry>Description</entry> - </row> - </thead> - <tbody> - <row> - <entry morerows='1' valign='middle'><para> - General</para></entry> - - <entry>This process is</entry> - <entry>Select one of the provided options: - <itemizedlist> - <listitem> - <para><emphasis>activated</emphasis> + <table> + <title>ODE Deployment Descriptor Editor.Options.</title> + <tgroup cols="3"> + <colspec colnum="1" colwidth="1*" align="left"/> + <colspec colnum="2" colwidth="3*" align="left"/> + <colspec colnum="3" colwidth="1*" align="left"/> + <thead> + <row> + <entry>Section</entry> + <entry>Options</entry> + <entry>Description</entry> + </row> + </thead> + <tbody> + <row> + <entry morerows="1" valign="middle"> + <para> + General</para> + </entry> + <entry>This process is</entry> + <entry>Select one of the provided options: <itemizedlist> + <listitem> + <para><emphasis>activated</emphasis> </para> - </listitem> - <listitem> - <para><emphasis>deactivated</emphasis></para> - </listitem> - <listitem> - <para><emphasis>retired</emphasis> + </listitem> + <listitem> + <para><emphasis>deactivated</emphasis></para> + </listitem> + <listitem> + <para><emphasis>retired</emphasis> </para> - </listitem> - </itemizedlist></entry> - - </row> - <row><entry>Run this process in memory</entry> - <entry>for performance purposes, - you can define the process as being - executed only in-memory.</entry> - </row> - - <row> - <entry>Inbound Interfaces(Services)</entry> - <entry>Associated Port</entry> - <entry>Click Associated Port and the dropdown list with all available port names will appear. - Select the one you need ,other fields will be filled automatically. - This action configure the services - provided by the process and - bind each service to an endpoint - </entry> - - </row> - - <row> - <entry>Outbound Interfaces(Invokes)</entry> - <entry>Associated Port</entry> - <entry>Click Associated Port and the dropdown list with all available port names will appear. - Select the one you need, other fields will be filled automatically. - This action configure the services - invoked by the process</entry> - </row> - <row> - <entry>Process-level Monitoring Events</entry> - <entry> <itemizedlist> - <listitem><para> + </listitem> + </itemizedlist></entry> + </row> + <row> + <entry>Run this process in memory</entry> + <entry>for performance purposes, you can define the process as being executed only in-memory.</entry> + </row> + <row> + <entry>Inbound Interfaces(Services)</entry> + <entry>Associated Port</entry> + <entry>Click Associated Port and the dropdown list with all available port names will appear. Select the one you need ,other fields will be filled automatically. This action configure the services provided by the process and bind each service to an endpoint </entry> + </row> + <row> + <entry>Outbound Interfaces(Invokes)</entry> + <entry>Associated Port</entry> + <entry>Click Associated Port and the dropdown list with all available port names will appear. Select the one you need, other fields will be filled automatically. This action configure the services invoked by the process</entry> + </row> + <row> + <entry>Process-level Monitoring Events</entry> + <entry> + <itemizedlist> + <listitem> + <para> <emphasis>None</emphasis> - </para></listitem> - <listitem> - <para> + </para> + </listitem> + <listitem> + <para> <emphasis>All</emphasis> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <emphasis>Selected</emphasis>: </para> - <itemizedlist> - <listitem><para>Instance life cycle</para></listitem> - <listitem><para>Activity life cycle</para></listitem> - <listitem><para>Data handling</para></listitem> - <listitem><para>Scope handling</para></listitem> - <listitem><para>Correlation</para></listitem> - - </itemizedlist> - - </listitem> - </itemizedlist> - </entry> - <entry>Using ODE's deployment descriptor, it's also - possible to make events generation to - filtrate which ones get created. - All option just duplicates the default behaviour, - when nothing is specified in the deployment.</entry> - </row> - <row> - <entry>Scope-level Monitoring Events</entry> - <entry>Scope</entry> - <entry>This section makes it possible to - define filtering for each scope of your process. - </entry> - </row> - </tbody> - </tgroup> - </table> - </section> - + <itemizedlist> + <listitem> + <para>Instance life cycle</para> + </listitem> + <listitem> + <para>Activity life cycle</para> + </listitem> + <listitem> + <para>Data handling</para> + </listitem> + <listitem> + <para>Scope handling</para> + </listitem> + <listitem> + <para>Correlation</para> + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + </entry> + <entry>Using ODE&apos;s deployment descriptor, it&apos;s also possible to make events generation to filtrate which ones get created. All option just duplicates the default behaviour, when nothing is specified in the deployment.</entry> + </row> + <row> + <entry>Scope-level Monitoring Events</entry> + <entry>Scope</entry> + <entry>This section makes it possible to define filtering for each scope of your process. </entry> + </row> + </tbody> + </tgroup> + </table> </section> - - -</chapter> - + </section> +</chapter> \ No newline at end of file Modified: trunk/bpel/docs/reference/en-US/modules/summary.xml =================================================================== --- trunk/bpel/docs/reference/en-US/modules/summary.xml 2010-07-14 00:02:21 UTC (rev 23394) +++ trunk/bpel/docs/reference/en-US/modules/summary.xml 2010-07-14 00:52:09 UTC (rev 23395) @@ -1,21 +1,14 @@ -<?xml version="1.0" encoding="ISO-8859-1"?> -<chapter> - <?dbhtml filename="summary.html"?> - <title>Summary</title> - <para>In conclusion, with this document you know all the capabilities of BPEL Tools - and could easily start with them. - The chapters above walked you through the steps on how to create and configure BPEL process and - deployment descriptor files. - If you have questions or suggestions concerned both the documentation and tools behavior, - you are welcome to JBoss Tools Users forum. - Please, use Jira to report bugs and requests on documentation.</para> - - <section> - <title>Other relevant resources on the topic</title> - <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at +<?xml version='1.0' encoding='ISO-8859-1'?><chapter> +<?dbhtml filename="summary.html"?> <title>Summary</title> + <para>This document is just a very brief introduction to the JBoss BPEL tooling but it touches on many aspects of the associated tools and runtimes. A complete reference to the BPEL language and the Eclipse BPEL editor is available from various online resources, and is simply beyond the scope of this document.</para> + <para>If you have questions or suggestions concerning either the documentation or JBoss BPEL Tools, + please visit the JBoss Tools website. + Bug reports, feature requests and documentation enhancements should be submitted via the Jira bug tracking facility at this website.</para> + <section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at <ulink url="http://docs.jboss.org/tools">http://docs.jboss.org/tool... in the corresponding release directory. - </para> - <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http...;. </para> - - </section> -</chapter> + </para> + <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http...;. </para> + </section> +</chapter> \ No newline at end of file Modified: trunk/bpel/docs/reference/en-US/modules/tasks.xml =================================================================== --- trunk/bpel/docs/reference/en-US/modules/tasks.xml 2010-07-14 00:02:21 UTC (rev 23394) +++ trunk/bpel/docs/reference/en-US/modules/tasks.xml 2010-07-14 00:52:09 UTC (rev 23395) @@ -1,444 +1,477 @@ -<?xml version="1.0" encoding="ISO-8859-1"?> -<chapter id="tasks"> - <title>Tasks</title> - <section id="detail"> - <title>Creating and editing a BPEL project</title> - <para>In the chapter we describe the necessary steps to create a new BPEL project and edit the BPEL files. - You can get the source of the example from <property> - riftsaw/samples/quickstart/hello_world</property>. - Here and further in the guide we will create - a simple echo example, used to respond to a sent message with a - modified version of the request message being returned in a response. - First of all, you should create a BPEL project. +<?xml version='1.0' encoding='ISO-8859-1'?><chapter id="tasks"> + <title>Tasks</title> + <section id="detail"> + <title>Creating a BPEL Process</title> + <para>This chapter explains how to create a new BPEL project and BPEL process file. + You may either follow along with this document as we walk you through the procedure or, if you are the impatient type, you can simply import the &quot;Hello World&quot; project from the Riftsaw &quot;quick start&quot; examples. The sample project can be found in the + samples/quickstart/hello_world directory of the Riftsaw installation. </para> - <section id="createproject"> - <title>Creating a BPEL project</title> - <para>Create the project by selecting - <emphasis><property>New > Project... > BPEL 2.0 > BPEL Project</property></emphasis> from the menu bar. - Then click the <property>Next</property> button. + <para>In this example we will build a simple BPEL process that accepts a message containing a single string input element, concatenates it with the string &quot;Hello&quot;, and returns the result in the reply message which also consists of only a single string output element.</para> + <section id="createproject"> + <title>Creating the BPEL Project</title> + <para>Create the project by selecting + <emphasis> + <property>File &gt; New &gt; Project... </property> + </emphasis> from the menu bar which will display the Eclipse New Project Wizard. + Scroll down to the BPEL 2.0 category, select <emphasis role="italic">BPEL Project </emphasis>and click the <property>Next</property> button. </para> - <figure> - <title>New BPEL Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_createproject_1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>On this page of the <property>New BPEL Project Wizard</property> enter a project name in the <property>Project Name</property> + <figure> + <title>New BPEL Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>On this page of the <property>New BPEL Project Wizard</property> enter a project name in the <property>Project Name</property> field,e.g enter <property>HelloWorld</property>.</para> - - <figure> - <title>New BPEL Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_createproject_2.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Click the <property>Finish</property> button. + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Finish</property> button. So you have created the BPEL project named <property>HelloWorld</property>. - Its structure is like this: </para> - <figure> - <title>The BPEL Project structure</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_createproject_3.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section id="createprocess"> - <title>Creating a BPEL process</title> - <para>Now you should create a BPEL process. You can create it by selecting - <emphasis><property>New > Others... > BPEL 2.0 > New BPEL Process File</property></emphasis>. + Its structure looks like this: </para> + <figure> + <title>The BPEL Project structure</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_3.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="createprocess"> + <title>Creating the BPEL Process</title> + <para>The next step is to create a BPEL process. Select your newly created BPEL project and from the context (right-click) menu, select + <emphasis> + <property>New &gt; Other... </property> + </emphasis> and then <emphasis role="italic">BPEL 2.0 &gt; New BPEL Process File</emphasis> as shown below:</para> + <figure> + <title>New BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <property>Next</property> button. On the first page of the New BPEL Process Wizard, enter the following information:</para> + <table> + <title>Fields and values</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="2*" align="left"/> + <colspec colnum="2" colwidth="4*"/> + <thead> + <row> + <entry>Field</entry> + <entry>Value</entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>BPEL Process Name</para> + </entry> + <entry> + <para>enter a process name. For this example, <property>HelloWorld</property>.</para> + </entry> + </row> + <row> + <entry> + <para>Namespace</para> + </entry> + <entry> + <para>enter or select a namespace for the BPEL process.</para> + </entry> + </row> + <row> + <entry> + <para>Template</para> + </entry> + <entry> + <para>Select the desired template for the BPEL process. + The wizard can generate three different types processes from templates: Synchronous, Asynchronouse and Empty. For this example, select <property>Synchronous BPEL Process</property>.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <figure> + <title>New BPEL Process File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The next page allows you to define the process&apos; endpoint; enter the following information: </para> - <figure> - <title>New BPEL Process File</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_createprocess_1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Click the <property>Next</property> button. Enter the following information:</para> - <table> - - <title>Fields and values</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="2*"/> - <colspec colnum="2" colwidth="4*"/> - <thead> - <row> - <entry>Field</entry> - <entry>Value</entry> - - </row> - </thead> - <tbody> - <row> - <entry><para>BPEL Process Name</para></entry> - <entry><para>enter a process name. For example, <property>HelloWorld</property>.</para></entry> - </row> - <row> - <entry><para>Namespace</para></entry> - <entry><para>enter or select a namespace for the BPEL process.</para></entry> - </row> - <row> - <entry><para>Template</para></entry> - <entry><para>Select the necessary template for the BPEL process. - When you select the template, you will see the information - about the template below on the page.In our case you should - select <property>Synchronous BPEL Process</property>.</para></entry> - </row> - - </tbody> - </tgroup> - </table> - - <figure> - <title>New BPEL Process File Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_createprocess_2.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Click the <property>Next</property> button. On the second page make sure that the folder <property>HelloWorld/bpelContent</property> is selected. - Click <property>Finish</property>. - </para> - <note> - <para>All of your files that are used in your BPEL project must be under the <property>bpelContent</property> folder. Only in this case - these files can be deployed to JBoss server. + <table> + <title>Fields and values</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="2*" align="left"/> + <colspec colnum="2" colwidth="4*"/> + <thead> + <row> + <entry>Field</entry> + <entry>Value</entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Service Name</para> + </entry> + <entry> + <para>enter the name of the service which will be published by the JBoss Web Server. The default is the same as the process name, but this can be any name you choose. For this example, enter <property>HelloWorld</property>.</para> + </entry> + </row> + <row> + <entry> + <para>Port Name</para> + </entry> + <entry> + <para>enter or the Service Port name. Again, this can be any name desired, but the default is the name of the service suffixed with &quot;Port&quot;. </para> + </entry> + </row> + <row> + <entry> + <para>Service Address</para> + </entry> + <entry> + <para>enter the service URL. By default the wizard assumes that the process will be deployed to a local WS server and fills in the address &quot;localhost:8080&quot; (8080 is the default web service port).</para> + </entry> + </row> + <row> + <entry> + <para>Binding Protocol</para> + </entry> + <entry> + <para>select the service binding protocl; either &quot;HTTP&quot; or &quot;SOAP&quot; By default the wizard assumes that the process will be deployed to a local WS server and fills in the address &quot;localhost:8080&quot; (8080 is the default web service port).</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <figure> + <title>New BPEL Process File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_2a.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The last page selects the target project and directory for the new process. Click Finish to select the default location (i.e. your currently selected BPEL Project).</para> + <note> + <para>All BPEL artifacts (*.bpel, *.wsdl, *.xsd, etc.) must be contained in the <emphasis role="bold"> + <property>bpelContent</property> + </emphasis> folder. This is required for proper deployment to the JBoss server. </para> - </note> - - <para>Up to now, you have got a simple BPEL process as on the screen below.</para> - <figure> - <title>A simple BPEL Process File</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_createprocess_3.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The next step, you can do is to edit the BPEL process file and then deploy it to JBoss server. </para> - </section> - <section id="editprocess"> - <title>Editing a BPEL process file</title> - <para>If the <emphasis><property>Properties view</property></emphasis> and <emphasis><property>Palette view</property></emphasis> are not opened, you can open the views by right-clicking the BPEL editor and selecting - <property>Show in Properties</property>, <property>Show Palette in Palette view</property>. Then you should have the view like this: + </note> + <para>You should now have the BPEL Editor open with the HelloWorld process as shown below.</para> + <figure> + <title>A simple BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Notice that this process does not do much of anything; it simply contains a receive and a reply activity. The &quot;FIX_ME&quot; activity in the middle acts as a placeholder for you to insert all of your business logic. This is an &quot;empty&quot;, do-nothing activity and can be deleted.</para> + </section> + <section id="editprocess"> + <title>Editing a BPEL Process File</title> + <para>In this next step we will add some functionality to the HelloWorld process.</para> + <para>If the <emphasis> + <property>Properties view</property> + </emphasis> and <emphasis> + <property>Palette view</property> + </emphasis> are not already visible in your perspective, you can open the views by right-clicking the BPEL editor canvas and selecting <emphasis role="italic">Show in Properties</emphasis> and <emphasis role="italic">Show Palette in Palette view</emphasis>.</para> + <para>First, select the &quot;FIX_ME&quot; empty activity and press DEL to delete it - we won&apos;t be needing this. Now locate and click on the Assign activity in the Palette (this is located in the Actions drawer). The cursor changes to a &quot;drop cursor&quot; which will place the selected activity on the canvas when you click the left mouse button. Move the cursor between the receiveInput and replyOutput activities as shown below; note that an insert bar appears as you move the cursor up and down the sequence of activities, indicating the drop point for the new activity.</para> + <figure> + <title>The BPEL editor view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Now left-click to drop the new Assign activity in place. Your workspace should look something like the figure below:</para> + <figure> + <title/> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Select the <emphasis> + <property>Properties view</property> + </emphasis>, and within that, the Details tab as shown above.</para> + <para>The table below describes the tabs of the Properties view: </para> - <figure> - <title>The BPEL editor view</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_editprocess_1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>In the <emphasis><property>Palette view</property></emphasis>, you can drag a BPEL element to the BPEL editor and drop it in the place you want.</para> - <para>In the <emphasis><property>Properties view</property></emphasis>, you can get the information about every element of the BPEL process. - In the BPEL editor select any element you want,and then - the element's properties will be shown in the Properties view.The table below describes the tabs of the Properties view: - </para> - <table> - - <title>Tabs of the Property view</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="2*"/> - <colspec colnum="2" colwidth="4*"/> - <thead> - <row> - <entry>Tab</entry> - <entry>Description</entry> - - </row> - </thead> - <tbody> - <row> - <entry><para>Description</para></entry> - <entry><para>Shows the descriptive information about the element,e.g. <property>Name</property> of the element.</para></entry> - </row> - <row> - <entry><para>Details</para></entry> - <entry><para>Shows the detailed and important information about the element. + <table> + <title>Tabs of the Property view</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="2*" align="left"/> + <colspec colnum="2" colwidth="4*"/> + <thead> + <row> + <entry>Tab</entry> + <entry>Description</entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Description</para> + </entry> + <entry> + <para>Shows the descriptive information about the element,e.g. <property>Name</property> of the element.</para> + </entry> + </row> + <row> + <entry> + <para>Details</para> + </entry> + <entry> + <para>Shows the detailed and important information about the element. It is the most important section of an element. - Most of the properties of an element are set in this section.</para></entry> - </row> - <row> - <entry><para>Join Behavior</para></entry> - <entry><para>Shows the <property>Join Failure</property> property of the element.</para></entry> - </row> - <row> - <entry><para>Documentation</para></entry> - <entry><para>Shows the <property>documentation</property> sub-element of an element.</para></entry> - </row> - <row> - <entry><para>Other</para></entry> - <entry><para>Every BPEL element has its own sections: Correlation section, Message Exchange section, and so on. We will - introduce them while using them.</para></entry> - </row> - </tbody> - </tgroup> - </table> - <para>In order to see how a simple BPEL process works in action, you should do some steps as below: </para> - <itemizedlist> - <listitem> - <para>Modify two variables of the process:</para> - <itemizedlist> - <listitem><para>Click on the details tab of the input variable, - select <property>Browse...</property>. - Then choose <property>string</property> primitive from the list.</para> - <figure> - <title>Edit variable in <property>process</property> file</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpel_task_1.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Select <property>xsd</property> as a namespace in the popup menu.</para> - </listitem> - </itemizedlist> - - </listitem> - <listitem> - <para>Add an <property>Assign</property> element between the <property>receiveInput</property> element and <property>replyOutput</property> element.</para> - </listitem> - <listitem> - <para>Click the <property>Assign</property> element in the BPEL editor in order to get the properties information of it in the Properties view. - </para> - </listitem> - <listitem> - <para>Set its name in the <property>Description</property> tab as <property>assignHelloMesg</property>.</para> - <para>In the <property>Details</property> section of Properties view, - you should click the <property>New</property> button to add a <property>copy</property> sub-element to the element. - Assign "Variable to Variable"(input:string to output). At this time, an "<property>initializer</property>" popup dialog appears. Click on the <property>Yes</property> button in the dialog. - </para> - <figure> - <title>Add <property>Assign</property> to the process</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpel_task_3.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Then you should click <property>New</property> once more and select Expression to Variable - (assign <code>concat($input,' World'))</code> to <property>result:string</property>. </para> - <figure> - <title>Add <property>Expression assign</property> to the process</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpel_task_2.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - </section> - - <section id="wsdl"> - <title>Adding Service to WSDL file</title> - <para></para> - <itemizedlist> - - <listitem> - <para>Open the file "<property>HelloWorldArtifacts.wsdl</property>" in the "<property>HelloWorld</property>" project by double-clicking the file. Right-click the WSDL editor and select - <property>Add Service</property>. A new service should appear in the editor. Name it <property>HelloWorldProcessService</property>. It has the Port - named <property>NewPort</property>. Select it, right-click on it and rename it to <property>HelloWorldProcessPort</property> in the Properties - view. - </para> - <figure> - <title>Add <property>Service</property> to the WSDL file</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_editprocess_3.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Right-click somewhere in the whitespace of the WSDL editor and select - <property>Add Binding</property>. A new Binding component will appear in the editor. Name it <property>HelloWorldSOAPBinding</property>. Select it, in the - General tab of the Properties view and select <property>HelloWorld</property> as a port type in the <property>PortType</property>. Then click on the - <property>Generate Binding Content...</property> button to open the <property>Binding Wizard</property>. In the wizard, select <property>SOAP </property> - as the <property>Protocol</property>. Finally, click the <property>Finish</property> button to close the wizard. - </para> - <figure> - <title>Add a <property>Binding</property> to the WSDL file</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_editprocess_4.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Click the <property>HelloWorldProcessPort</property> property in the General section of the Properties view, select <property>HelloWorldSOAPBinding</property> in - the <property>Binding</property> combobox. In the <property>Address</property> field input <ulink url="http://localhost:8080/bpel/processes/HelloWorld?wsdl">http://localhost:8080/bpel/processes/HelloWorld?wsdl</ulink>. - </para> - <figure> - <title>Add the <property>HelloWorldSOAPBinding</property> to the <property>HelloWorldProcessPort</property></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_editprocess_5.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem><para>You should also change some service part configurations. - To do this,click part element in the WSDL editor, - then put the following data in the Properties view. - </para> - <figure> - <title>Configuration of service part</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/detail_editprocess_5.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - - <para>Now you have finished creating a simple BPEL process.As a next step, you can deploy the BPEL project to JBoss BPEL Runtime.</para> - - </section> - + Most of the properties of an element are set in this section.</para> + </entry> + </row> + <row> + <entry> + <para>Join Behavior</para> + </entry> + <entry> + <para>Shows the <property>Join Failure</property> property of the element.</para> + </entry> + </row> + <row> + <entry> + <para>Documentation</para> + </entry> + <entry> + <para>Shows the <property>documentation</property> sub-element of an element.</para> + </entry> + </row> + <row> + <entry> + <para>Other</para> + </entry> + <entry> + <para>Every BPEL element has its own sections: Correlation section, Message Exchange section, and so on. We will + introduce them while using them.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <para>The next step is to add the XPath expressions that will build our reply message. From the Details tab of the Property view for the Assign activity, click New. This will add an empty row to the Assignment activity:</para> + <figure> + <title/> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_assign1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>In the &quot;From:&quot; group, select Expression and use &quot;Same as Process&quot; for the Expression Language (the default). Then, type the following XPath expression in the edit box:</para> + <para><code>concat(&quot;Hello&quot;,$input.payload/tns:input)</code></para> + <para>As you type the expression, notice that the Expression Editor pops up a tooltip containing a list of known functions, variables and message parts that match the characters you just typed.</para> + <para><note> + <para>Currently the BPEL editor only supports XPath 1.0. Support for XPath 2.0 is planned as an enhancement for future versions.</para> + </note></para> + <para>Next, in the &quot;To:&quot; group, expand the &quot;output&quot; message, then the &quot;payload&quot; part and finally the &quot;result&quot; element in the message. This element is the target for the results of the concat() XPath function you entered in the &quot;From:&quot; group.</para> + <para>The Property view should now look like this:</para> + <figure> + <title/> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_assign2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>After you change focus by clicking anywhere outside of the &quot;To:&quot; item you have just selected, the BPEL editor will ask if you would like to initialize the output variable. </para> + <figure> + <title/> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_assign3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>This is generally a good idea because it initializes the structure of the output message and without it, the ODE BPEL engine will report a mysterious &quot;bpel:selectionFailure&quot; exception.</para> + <note> + <para>The changes made in the Properties view are not reflected in the BPEL Editor&apos;s main canvas until you change focus to the canvas. Because the Properties view is just a view, it does not understand keyboard shortcuts like CTRL-S to save the BPEL Editor. </para> + </note> </section> - <section id="deploy"> - <title>Deploy a JBoss BPEL project to JBoss BPEL Runtime</title> - <section id="createdeploy"> - <title>Creating a bpel-deploy.xml file</title> - <para>If you want to deploy a BPEL project to JBoss BPEL Runtime, you should create a bpel-deploy.xml file. - JBoss tools can help you to create it: - </para> - <itemizedlist> - <listitem> - <para>Create the bpel-deploy.xml by selecting - <emphasis><property>New > Other... > BPEL 2.0 > Apache ODE Deployment Descriptor</property></emphasis>. Click the <property>Next</property> button. - </para> - <figure> - <title>New BPEL Deploy file</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/deploy_createdeploy_1.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>On the next wizard page you should enter the following information:</para> - <para><emphasis><property>BPEL Project</property></emphasis>: Click the <property>Browse...</property> button to select the BPEL project in your workspace which you want to deploy to the runtime. + </section> + <section id="deploy"> + <title>Deploying a BPEL Project</title> + <section id="createdeploy"> + <title>Creating the Deployment File</title> + <para>The deployment framework requires a description file which defines the BPEL services and interface definitions that are to be installed in the BPEL runtime server. This description file is called bpel-deploy.xml and is created using the Eclipse New File wizard. +</para> + <itemizedlist> + <listitem> + <para>Select the BPEL project in which you wish to create the descriptor, then select + <emphasis> + <property>New &gt; Other... &gt; BPEL 2.0 &gt; Apache ODE Deployment Descriptor</property> + </emphasis>. </para> + <para><figure> + <title>New BPEL Deploy file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_1.png"/> + </imageobject> + </mediaobject> + </figure>. </para> + </listitem> + <listitem> + <para>On the next wizard page, enter the following information:</para> + <para><emphasis> + <property>BPEL Project</property> + </emphasis>: Click the <property>Browse...</property> button to select the BPEL project in your workspace which you want to deploy to the runtime. Please note, that you should select the <property>bpelContent</property> folder in your new BPEL project as a value of <property>BPEL Project</property> field because the bpel-deploy.xml should be created in this place. </para> - <para><emphasis><property>File name</property></emphasis>: The default value is bpel-deploy.xml. Please, don't change it.</para> - <para>Click on <property>Finish</property> button to close the wizard and a new bpel-deploy.xml file will be created.</para> - <figure> - <title>New BPEL Deploy file Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/deploy_createdeploy_2.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Double-click the bpel-deploy.xml file to open it in ODE Descriptor Deployment Editor. + <para><emphasis> + <property>File name</property> + </emphasis>: This field is read-only and can not be changed.</para> + <para>Click on <property>Finish</property> button to close the wizard and a new bpel-deploy.xml file will be created.</para> + <figure> + <title>New BPEL Deploy file Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Double-click the bpel-deploy.xml file to open it in ODE Descriptor Deployment Editor. In the <property>Inbound Interfaces</property> section, click the - <property>Associated Port</property> column and select <property>HelloWorldProcessPort</property> + <property>Associated Port</property> column and select <property>HelloWorldPort</property> in the dropdown box.The <property>Related Service</property> and <property>Binding Used</property> - columns should be automatically filled in. Save the <emphasis><property>bpel-deploy.xml</property></emphasis>. + columns should be automatically filled in. Save the <emphasis> + <property>bpel-deploy.xml</property> + </emphasis>. </para> - <figure> - <title>bpel-deploy.xml file editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/deploy_createdeploy_3.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - </section> - <section id="createruntime"> - <title>Creating JBoss BPEL Server</title> - <para>Suppose you have installed the <property>JBoss BPEL Runtime-RiftSaw</property> as it was described <link linkend="installRuntime">before</link>, now you can create a server for JBoss BPEL runtime.</para> - <itemizedlist> - <listitem> - <para>Open the <property>Servers</property> view by selecting - <emphasis><property>Windows > Show View > Other... > Server > Servers</property></emphasis>. - </para> - </listitem> - <listitem> - <para>Right-click the Servers view and select - <emphasis><property>New > Server</property></emphasis> to open the New Server Wizard: + <figure> + <title>bpel-deploy.xml file editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_3.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + </section> + <section id="createruntime"> + <title>Creating the Server Instance</title> + <para>Assuming you have installed the <property>JBoss BPEL Runtime (RiftSaw)</property> as described <link linkend="installRuntime">previously</link>, the next step is to create a Server Definition for it.</para> + <itemizedlist> + <listitem> + <para>Open the <property>Servers</property> view by selecting + <emphasis> + <property>Windows &gt; Show View &gt; Other... &gt; Server &gt; Servers</property> + </emphasis>. </para> - <figure> - <title>New Server Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/deploy_createdeploy_4.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Select <property>JBoss AS 5.1 </property>as a server type. </para> - <note> - <para>Please note, that only JBoss As 5.1 or higher version supports BPEL.</para> - </note> - </listitem> - <listitem> - - <para>Click the <property>Next</property> button. On the next page, you should input your <emphasis><property>JBoss As</property></emphasis> location. Then click the <property>Next</property> button and - you will get the page like this: + </listitem> + <listitem> + <para>Right-click the Servers view and select + <emphasis> + <property>New &gt; Server</property> + </emphasis> to open the New Server Wizard: </para> - <figure> - <title>Add resource to the server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/deploy_createdeploy_5.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Select <property>HelloWorld</property>, then click the <property>Add </property> button to add the project to the server. + <figure> + <title>New Server Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property>JBoss AS 5.1 </property>as a server type. </para> + <note> + <para>Please note, that only JBoss As 5.1 or higher version supports BPEL.</para> + </note> + </listitem> + <listitem> + <para>Click the <property>Next</property> button. On the next page, enter the file system directory where <emphasis> + <property>JBoss As</property> + </emphasis>was installed, then click the <property>Next</property> button. This will display the Server Deployment dialog as shown below: + </para> + <figure> + <title>Add resource to the server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select <property>HelloWorld</property>, then click the <property>Add </property> button to add the project to the server. Then click on the <property>Finish</property> button. </para> - <para>Start the server by right-clicking on the server and selecting the <property>Start</property> item. </para> - - <figure> - <title>The started server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/deploy_createdeploy_6.png"/> - </imageobject> - </mediaobject> - </figure> - <para>If some aspects of server creation is not clear, please, read <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/as/html_si... Server Manager Reference Guide</ulink> for more details.</para> - </listitem> - <listitem> - <para>You can enter the link <ulink url="http://localhost:8080/bpel/processes.html">http://localhost:8080/bpel/processes.html</ulink> to the browser to get the deployed processes.</para> - <figure> - <title>The BPEL console</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/deploy_createdeploy_7.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - <para>If there's anything we didn't cover or you can't figure out, please feel free to visit our <ulink - url="http://www.jboss.com/index.html?module=bb&amp;op=viewforum&... - >JBoss Tools Users Forum</ulink> to ask questions. - There we are also waiting for your suggestions and comments.</para> - </section> + <note> + <para>The Server Deployment (Add and Remove) dialog can also be displayed by right-clicking on the desired entry in the Servers view. + </para> + </note> + <para>Start the server by right-clicking on the JBoss server entry and selecting the <property>Start</property> item. </para> + <figure> + <title>Servers view after starting JBoss AS</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_6.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Please refer to the <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/as/html_si... Server Manager Reference Guide</ulink> for more information about server management.</para> + </listitem> + </itemizedlist> </section> -</chapter> + <section> + <title>Monitoring BPEL Processes</title> + <para>A BPEL process management and monitoring console is installed as part of the Riftsaw runtime. This console can be viewed using any standard internet browser by navigating to the JBoss AS server URL. By default, the BPEL console listens on port 8080 but this is configurable.</para> + <para>In our example we have installed the server on the local machine, so the BPEL console should be at <ulink url="http://localhost:8080/bpel-console">http://localhost:8080/bpel-console</ulink> . This will display the console&apos;s login screen. The default installation creates a single administrative user login +identified by &quot;admin&quot; and &quot;password&quot; (again, these are configurable - see the Riftsaw documentation for more information):</para> + <figure> + <title>The BPEL console login page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_7.png"/> + </imageobject> + </mediaobject> + </figure> + <para>After successful login, the console displays a list of active processes, and other detailed information:</para> + <figure> + <title>The BPEL processes page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_8.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Select the <emphasis role="bold">Runtime</emphasis> link at the bottom to display the deployed process versions. Note that it is possible to deploy multiple versions of the same process, but only one version can be the active one. To activate or deactivate (retire) a particular version, select it in the Deployment list, then click the <emphasis role="bold">Activate</emphasis> or <emphasis role="bold">Retire</emphasis> buttons at the bottom of the console.</para> + <figure> + <title>The BPEL deployments page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_9.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> +</chapter> \ No newline at end of file