[jbosstools-commits] JBoss Tools SVN: r17271 - in trunk/bpel/docs/reference/en: images and 1 other directories.

Author: Grid.Qian Date: 2009-08-26 06:40:16 -0400 (Wed, 26 Aug 2009) New Revision: 17271 Added: trunk/bpel/docs/reference/en/images/ trunk/bpel/docs/reference/en/images/deploy_createdeploy_1.png trunk/bpel/docs/reference/en/images/deploy_createdeploy_2.png trunk/bpel/docs/reference/en/images/deploy_createdeploy_3.png trunk/bpel/docs/reference/en/images/deploy_createdeploy_4.png trunk/bpel/docs/reference/en/images/deploy_createdeploy_5.png trunk/bpel/docs/reference/en/images/deploy_createdeploy_6.png trunk/bpel/docs/reference/en/images/deploy_createdeploy_7.png trunk/bpel/docs/reference/en/images/detail_createprocess_1.png trunk/bpel/docs/reference/en/images/detail_createprocess_2.png trunk/bpel/docs/reference/en/images/detail_createprocess_3.png trunk/bpel/docs/reference/en/images/detail_createproject_1.png trunk/bpel/docs/reference/en/images/detail_createproject_2.png trunk/bpel/docs/reference/en/images/detail_createproject_3.png trunk/bpel/docs/reference/en/images/detail_editprocess_1.png trunk/bpel/docs/reference/en/images/detail_editprocess_2.png trunk/bpel/docs/reference/en/images/detail_editprocess_3.png trunk/bpel/docs/reference/en/images/detail_editprocess_4.png trunk/bpel/docs/reference/en/images/detail_editprocess_5.png trunk/bpel/docs/reference/en/modules/ trunk/bpel/docs/reference/en/modules/deploy.xml trunk/bpel/docs/reference/en/modules/detail.xml trunk/bpel/docs/reference/en/modules/install.xml trunk/bpel/docs/reference/en/modules/overview.xml Log: add the bpel document Added: trunk/bpel/docs/reference/en/images/deploy_createdeploy_1.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/deploy_createdeploy_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/deploy_createdeploy_2.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/deploy_createdeploy_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/deploy_createdeploy_3.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/deploy_createdeploy_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/deploy_createdeploy_4.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/deploy_createdeploy_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/deploy_createdeploy_5.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/deploy_createdeploy_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/deploy_createdeploy_6.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/deploy_createdeploy_6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/deploy_createdeploy_7.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/deploy_createdeploy_7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_createprocess_1.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_createprocess_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_createprocess_2.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_createprocess_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_createprocess_3.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_createprocess_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_createproject_1.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_createproject_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_createproject_2.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_createproject_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_createproject_3.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_createproject_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_editprocess_1.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_editprocess_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_editprocess_2.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_editprocess_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_editprocess_3.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_editprocess_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_editprocess_4.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_editprocess_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/images/detail_editprocess_5.png =================================================================== (Binary files differ) Property changes on: trunk/bpel/docs/reference/en/images/detail_editprocess_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/bpel/docs/reference/en/modules/deploy.xml =================================================================== --- trunk/bpel/docs/reference/en/modules/deploy.xml (rev 0) +++ trunk/bpel/docs/reference/en/modules/deploy.xml 2009-08-26 10:40:16 UTC (rev 17271) @@ -0,0 +1,120 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="deploy"> + <title>Deploy a JBoss BPEL project into JBoss BPEL Runtime</title> + <section id="createdeploy"> + <title>Creating a bpel-deploy.xml file</title> + <para>If you want to deploy a BPEL project into JBoss BPEL Runtime, you need to create a bpel-deploy.xml file. + Our 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>. + </para> + <figure> + <title>New BPEL Deploy file</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_1.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>BPEL Project: Click on the <property>Browse...</property> button to select a BPEL project in your workspace which you want to deploy into the runtime. + Please note that you should select the bpel folder under the BPEL project because the bpel-deploy.xml should be at this place. + </para> + <para>File name: The default value is bpel-deploy.xml. Please don't change it.</para> + <para>Click on <property>Finish</property> button to close the wizard.</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 on the bpel-deploy.xml file to open it. In the <property>Inbound Interface</property> section, click in the + <property>Associated Port</property> column for the <property>client</property> Parner link. Then select <property>HelloWorldProcessPort</property> + in the drop down box. Click in the other part of the eclipse, the <property>Related Service</property> and <property>Binding Used</property> + clumns should automatically be filled in. Save the bpel-deploy.xml. + </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 JBoss BPEL Runtime, <property>RiftSaw</property>, now we can create a server for the JBoss BPEL runtime</para> + <itemizedlist> + <listitem> + <para>Open the <property>Servers view</property> by selecting + <emphasis><property>Windows > Show View > Other... > Server > Servers</property></emphasis>. + </para> + </listitem> + <listitem> + <para>In the Servers view, right-click and select + <emphasis><property>New > Server</property></emphasis> to open a wizard: + </para> + <figure> + <title>New Server Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_4.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Server type: select <property>JBoss AS 5.1</property>. Please note that only JBoss As 5.1 or higher version support BPEL.</para> + <para>Click on the <property>Next</property> button. On the next page, you can input your JBoss As location. Then click on the <property>Next</property> button. + you can get the page like this: + </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 on the <property>Add > </property> button to add the project to the server. + Then click on <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> + </listitem> + <listitem> + <para>You can input the link <ulink url="http://localhost:8080/bpel/processes.html">http://localhost:8080/bpel/processes.html</ulink> in the browse to find the deployed processes.</para> + <figure> + <title>The BPEL console</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/deploy_createdeploy_7.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + + </section> +</chapter> \ No newline at end of file Added: trunk/bpel/docs/reference/en/modules/detail.xml =================================================================== --- trunk/bpel/docs/reference/en/modules/detail.xml (rev 0) +++ trunk/bpel/docs/reference/en/modules/detail.xml 2009-08-26 10:40:16 UTC (rev 17271) @@ -0,0 +1,201 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="detail"> + <title>Create and edit a BPEL project</title> + <para>In the chapter we provide you with the necessary steps to create a BPEL project and edit the BPEL files. + First you need to create a BPEL project. + </para> + <section id="createproject"> + <title>Creating a BPEL project</title> + <para>Create a Web project by selecting + <emphasis><property>New > Project... > BPEL 2.0 > BPEL Project</property></emphasis>. + </para> + <figure> + <title>New BPEL Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Enter the following information:</para> + <itemizedlist> + <listitem> + <para>Project Name: enter a project name</para> + </listitem> + </itemizedlist> + <figure> + <title>New BPEL Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createproject_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click on the <property>Finish</property> button. Now you have created a BPEL project named <property>HelloWorld</property>. It's structure is like this: </para> + <figure> + <title>A 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>Create a BPEL process by selecting + <emphasis><property>New > Others... > BPEL 2.0 > New BPEL Process File</property></emphasis>. + </para> + <figure> + <title>New BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click on the <property>Next</property> button. Enter the following information:</para> + <itemizedlist> + <listitem> + <para>BPEL Process Name: enter a project name</para> + </listitem> + <listitem> + <para>Namespace: enter or select a namespace for the BPEL process</para> + </listitem> + <listitem> + <para>Template: select a template for the BPEL process. When you select a template, below the raw, you will get the information for the template.</para> + </listitem> + </itemizedlist> + <figure> + <title>New BPEL Process File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click on the <property>Next</property> button. On the second page, make sure that the Fold <property>HelloWorld/bpel</property> is selected. + Clink on the <property>Finish</property> button. + </para> + <para>All of your files that are used in your BPEL project must be under the <property>bpel</property> folder. Only like this, + these files can be deployed into JBoss server. + </para> + <para>Up to now, you have get a simple BPEL process as below. Next step, you can edit the BPEL process and then deploy it into JBoss server. </para> + <figure> + <title>A simple BPEL Process File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_createprocess_3.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="editprocess"> + <title>Editing a BPEL process</title> + <para>If you don't get the Properties view and Palette view opened, you can right-click on the BPEL editor and select the + <property>Show in Properties</property>, <property>Show Palette in Palette view</property>. Then you can get the view like: + </para> + <figure> + <title>The BPEL editor view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>In the Palette view, you can drag a BPEL element into the BPEL editor and put it in the palace that you want.</para> + <para>In the Properties view, you can get the information for every element of the BPEL process. Select a element in the BPEL editor, + the element's properties will be shown in the Properties view: + </para> + <itemizedlist> + <listitem> + <para>Description section: Show the described information of the element. For example, <property>Name</property> of the element.</para> + </listitem> + <listitem> + <para>Details section: Show the detailed and important information of element. This is the most important section of a element. + Many properties of a element will be set in this section. + </para> + </listitem> + <listitem> + <para>Join Behavior section: Show the <property>Join Failure</property> property of the element.</para> + </listitem> + <listitem> + <para>Documentation section: Show the <property>documentation</property> sub-element of the element.</para> + </listitem> + <listitem> + <para>Others sections: Every BPEL element has itself sections, Correlation section, Message Exchange section, and so on. We will + introduce them when using them. + </para> + </listitem> + </itemizedlist> + <para>In order to show how a simple BPEL process work, we will do some steps as below: </para> + <itemizedlist> + <listitem> + <para>Add an <property>Assign</property> element between the <property>receiveInput</property> element and <property>replyOutput</property> element.</para> + </listitem> + <listitem> + <para>Select the <property>Assign</property> element in the BPEL editor, you can get the properties information of it in the Properties view. + </para> + </listitem> + <listitem> + <para>In the Details section, you can select <property>New</property> button to add a <property>copy</property> sub-element to the element. + Assign "input->payload->input" to "output->payload->result". At this time, an "initializer" popup dialog appears. Click on the <property>Yes</property> button. + </para> + <figure> + <title>Add an <property>Assign</property> to the process</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/detail_editprocess_2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Open the file "HelloWorldArtifacts.wsdl" in the "HelloWorld" project by double-clicking on it. Right-click in the WSDL editor and select + <property>Add Service</property>. A new service appears on the editor. Name it <property>HelloWorldProcessService</property>. It has a 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 a <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 appears on the editor. Name it <property>HelloWorldSOAPBinding</property>. Select it, in the + Properties view, General section, select <property>HelloWorld</property> port type in the <property>PortType</property>. Then click on the + <property>Generate Binding Content...</property> button to open a <property>Binding Wizard</property>. In the wizard, select the <property>SOAP</property> + as the <property>Protocol</property>. Finally, click on 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 on the <property>HelloWorldProcessPort</property>, in the Properties view, General section, select the <property>HelloWorldSOAPBinding</property> in + the <property>Binding</property> Combo. 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> + </itemizedlist> + <para>For now, you have finished the simple BPEL process. Next step, you can deploy the BPEL project into JBoss BPEL Runtime.</para> + + </section> +</chapter> Property changes on: trunk/bpel/docs/reference/en/modules/detail.xml ___________________________________________________________________ Name: svn:executable + * Added: trunk/bpel/docs/reference/en/modules/install.xml =================================================================== --- trunk/bpel/docs/reference/en/modules/install.xml (rev 0) +++ trunk/bpel/docs/reference/en/modules/install.xml 2009-08-26 10:40:16 UTC (rev 17271) @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="install"> + <title>Install the JBoss BPEL editor</title> + <section id="installeclipse"> + <title>Installing the JBoss BPEL editor</title> + <para>At first, you need an Eclipse(3.5). You can get it from <ulink url="http://www.eclipse.org/downloads/download.php?file=/technology/... Web Site. + </para> + <para>The JBoss BPEL editor is included in 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 only want to install the JBoss BPEL editor, you may install it from <ulink url="http://jboss.org/tools/download/dev.html">JBoss Tools</ulink> page. Please note that + only JBoss Tools 3.1 or higher version include the JBoss BPEL editor. + </para> + </section> + <section id="installRuntime"> + <title>Installing the JBoss BPEL Runtime</title> + <para>If you want to deploy a BPEL project to JBoss runtime, you need to download the JBoss BPEL Runtime by yourself. The JBoss BPEL Runtime + is named RiftSaw. You can get it from <ulink url="">JBoss RiftSaw</ulink> page. + </para> + </section> +</chapter> \ No newline at end of file Added: trunk/bpel/docs/reference/en/modules/overview.xml =================================================================== --- trunk/bpel/docs/reference/en/modules/overview.xml (rev 0) +++ trunk/bpel/docs/reference/en/modules/overview.xml 2009-08-26 10:40:16 UTC (rev 17271) @@ -0,0 +1,61 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<chapter id="overview"> + <title>JBoss BPEL editor project Overview</title> + + <para>JBoss BPEL editor project is a WS-BPEL 2.0 editor that give a way to create, edit, validate and deploy BPEL files into JBoss BPEL runtime. It is based on the Eclipse + <ulink url="http://www.eclipse.org/bpel/">BPEL</ulink> + project. </para> + + <para>It improves the Eclipse BPEL project in the following way: </para> + <itemizedlist> + <listitem> Tight integration with JBoss BPEL runtime. Add a new project type for the deployment to JBoss BPEL runtime</listitem> + <listitem> Support two ways to deploy: one is deploy a bpel project directly into JBoss BPEL runtime. The other is deploy bpel files in the JBoss ESB project into JBoss BPEL runtime. </listitem> + <listitem> Improve the BPEL validator and the Eclipse BPEL editor's quality. </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. Specifically, 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 editor project</title> + <para>For a start, we propose you to look through the table of 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 editor project supports the newest WS-BPEL 2.0 specifications. </para></entry> + </row> + <row> + <entry><para>Tight integration with JBoss BPEL runtime</para></entry> + <entry><para>There are two ways to deploy BPEL files into JBoss BPEL runtime. User can deploy a BPEL project as a whole and can deploy BPEL files in JBoss ESB project into JBoss BPEL runtime. </para></entry> + </row> + <row> + <entry><para>A BPEL file editor</para></entry> + <entry><para>User can use the editor freely to edit a BPEL file. </para></entry> + </row> + <row> + <entry><para>A BPEL file validator</para></entry> + <entry><para>The validator can give the error messages about BPEL files to user. </para></entry> + </row> + </tbody> + </tgroup> + </table> + +</section> + +</chapter> \ No newline at end of file Property changes on: trunk/bpel/docs/reference/en/modules/overview.xml ___________________________________________________________________ Name: svn:executable + *