From jbosstools-commits at lists.jboss.org Tue May 25 11:27:34 2010
Content-Type: multipart/mixed; boundary="===============0933363944957474746=="
MIME-Version: 1.0
From: jbosstools-commits at lists.jboss.org
To: jbosstools-commits at lists.jboss.org
Subject: [jbosstools-commits] JBoss Tools SVN: r22310 - in
trunk/bpel/docs/reference/en-US: modules and 1 other directory.
Date: Tue, 25 May 2010 11:27:34 -0400
Message-ID: <201005251527.o4PFRYkM019203@svn01.web.mwc.hst.phx2.redhat.com>
--===============0933363944957474746==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: ochikvina
Date: 2010-05-25 11:27:33 -0400 (Tue, 25 May 2010)
New Revision: 22310
Added:
trunk/bpel/docs/reference/en-US/images/bpel_task_1.png
trunk/bpel/docs/reference/en-US/images/bpel_task_2.png
trunk/bpel/docs/reference/en-US/images/bpel_task_3.png
trunk/bpel/docs/reference/en-US/modules/summary.xml
trunk/bpel/docs/reference/en-US/modules/tasks.xml
Log:
https://jira.jboss.org/browse/TOOLSDOC-48 - Updated BPEL guide.Corrected=
all found incorrect places.
Added: trunk/bpel/docs/reference/en-US/images/bpel_task_1.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
(Binary files differ)
Property changes on: trunk/bpel/docs/reference/en-US/images/bpel_task_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/bpel/docs/reference/en-US/images/bpel_task_2.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
(Binary files differ)
Property changes on: trunk/bpel/docs/reference/en-US/images/bpel_task_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/bpel/docs/reference/en-US/images/bpel_task_3.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
(Binary files differ)
Property changes on: trunk/bpel/docs/reference/en-US/images/bpel_task_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/bpel/docs/reference/en-US/modules/summary.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/bpel/docs/reference/en-US/modules/summary.xml =
(rev 0)
+++ trunk/bpel/docs/reference/en-US/modules/summary.xml 2010-05-25 15:27:33=
UTC (rev 22310)
@@ -0,0 +1,21 @@
+
+
+
+ Summary
+ 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 a=
nd configure BPEL process and =
+ deployment descriptor files. =
+ If you have questions or suggestions concerned both the documentat=
ion and tools behavior,
+ you are welcome to JBoss Tools Users forum.
+ Please, use Jira to report bugs and requests on documentation.
+ =
+
+ Other relevant resources on the topic
+ All JBoss Developer Studio/JBoss Tools release documentation=
you can find at
+ http://docs.jboss.o=
rg/tools in the corresponding release directory.
+ =
+ The latest documentation builds are available at http://download.jbos=
s.org/jbosstools/nightly-docs.
+
+
+
Added: trunk/bpel/docs/reference/en-US/modules/tasks.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/bpel/docs/reference/en-US/modules/tasks.xml =
(rev 0)
+++ trunk/bpel/docs/reference/en-US/modules/tasks.xml 2010-05-25 15:27:33 U=
TC (rev 22310)
@@ -0,0 +1,444 @@
+
+
+ Tasks
+
+ Creating and editing a BPEL project
+ In the chapter we describe the necessary steps to create a n=
ew BPEL project and edit the BPEL files.
+ You can get the source of the example from
+ riftsaw/samples/quickstart/hello_world.
+ 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 re=
sponse.
+ First of all, you should create a BPEL project.
+ =
+
+
+ Creating a BPEL project
+ Create the project by selecting =
+ New > Project... > BPEL 2.0 > BPEL Pro=
ject from the menu bar.
+ Then click the Next button. =
+
+
+ New BPEL Project
+
+
+
+
+
+
+ On this page of the New BPEL Project Wizard enter a project name in the Project Name
+ field,e.g enter HelloWorld.
+ =
+
+ New BPEL Project Wizard
+
+
+
+
+
+
+ Click the Finish button.
+ So you have created the BPEL project named Hello=
World.
+ Its structure is like this:
+
+ The BPEL Project structure
+
+
+
+
+
+
+
+
+ Creating a BPEL process
+ Now you should create a BPEL process. You can create it =
by selecting =
+ New > Others... > BPEL 2.0 > New BPEL =
Process File.
+
+
+ New BPEL Process File
+
+
+
+
+
+
+ Click the Next button. Enter the fo=
llowing information:
+
+ =
+ Fields and values
+ =
+
+
+
+
+ Field
+ Value
+ =
+
+ =
+ =
+
+ BPEL Process Name
+ enter a process name. For example=
, HelloWorld. =
+ =
+
+ Namespace
+ enter or select a namespace for t=
he BPEL process. =
+ =
+
+ Template
+ 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 ou=
r case you should
+ select Synchronous BPEL Process<=
/property>. =
+ =
+ =
+ =
+
+
+ =
+
+ New BPEL Process File Wizard
+
+
+
+
+
+
+ Click the Next button. On the secon=
d page make sure that the folder HelloWorld/bpelContent is selected.
+ Click Finish.
+
+
+ All of your files that are used in your BPEL project=
must be under the bpelContent folder. Only in this ca=
se =
+ these files can be deployed to JBoss server.
+
+
+ =
+ Up to now, you have got a simple BPEL process as on the =
screen below.
+
+ A simple BPEL Process File
+
+
+
+
+
+
+ The next step, you can do is to edit the BPEL process fi=
le and then deploy it to JBoss server.
+
+
+ Editing a BPEL process file
+ If the Properties view and Palette view are not=
opened, you can open the views by right-clicking the BPEL editor and selec=
ting =
+ Show in Properties, Show Pa=
lette in Palette view. Then you should have the view like this: =
+
+
+ The BPEL editor view
+
+
+
+
+
+ =
+ In the Palette view, you can drag a BPEL element to the BPEL editor and drop it in the pl=
ace you want. =
+ In the Properties view, you can get the information about every element of the BPEL proce=
ss.
+ In the BPEL editor select any element you want,and then
+ the element's properties will be shown in the Properties v=
iew.The table below describes the tabs of the Properties view: =
+
+
+ =
+ Tabs of the Property view
+ =
+
+
+
+
+ Tab
+ Description
+ =
+
+ =
+ =
+
+ Description
+ Shows the descriptive information=
about the element,e.g. Name of the element. =
+ =
+
+ Details
+ Shows the detailed and important =
information about the element.
+ It is the most important section of an ele=
ment.
+ Most of the properties of an element are s=
et in this section. =
+ =
+
+ Join Behavior
+ Shows the Join Failure<=
/property> property of the element. =
+ =
+
+ Documentation
+ Shows the documentation=
sub-element of an element. =
+ =
+
+ Other
+ Every BPEL element has its own se=
ctions: Correlation section, Message Exchange section, and so on. We will
+ introduce them while using them. =
+ =
+ =
+
+
+ In order to see how a simple BPEL process works in actio=
n, you should do some steps as below: =
+
+
+ Modify two variables of the process:
+
+ Click on the details tab of the input =
variable,
+ select Browse....
+ Then choose string primitive =
from the list.
+
+ Edit variable in process file
+
+
+
+
+
+ =
+
+
+ Select xsd as a namespa=
ce in the popup menu.
+
+
+ =
+
+
+ Add an Assign element betwe=
en the receiveInput element and replyOutput<=
/property> element.
+
+
+ Click the Assign element in=
the BPEL editor in order to get the properties information of it in the Pr=
operties view. =
+
+
+
+ Set its name in the Description tab as assignHelloMesg.
+ In the Details section of P=
roperties view,
+ you should click the New butt=
on to add a copy sub-element to the element. =
+ Assign "Variable to Variable"(input:string to outp=
ut). At this time, an "initializer" popup dialog appea=
rs. Click on the Yes button in the dialog.
+
+
+ Add Assign to the proc=
ess
+
+
+
+
+
+ =
+ Then you should click New o=
nce more and select Expression to Variable
+ (assign concat($input,' World')) to <=
property>result:string.
+
+ Add Expression assign =
to the process
+
+
+
+
+
+ =
+
+
+
+ =
+
+ Adding Service to WSDL file
+
+
+ =
+
+ Open the file "HelloWorldArtifacts.wsd=
l" in the "HelloWorld" project by double-cl=
icking the file. Right-click the WSDL editor and select =
+ Add Service. A new service sh=
ould appear in the editor. Name it HelloWorldProcessService. It has the Port =
+ named NewPort. Select it, rig=
ht-click on it and rename it to HelloWorldProcessPort =
in the Properties =
+ view.
+
+
+ Add Service to the WSD=
L file
+
+
+
+
+
+ =
+
+
+ Right-click somewhere in the whitespace of the W=
SDL editor and select =
+ Add Binding. A new Binding co=
mponent will appear in the editor. Name it HelloWorldSOAPBinding<=
/property>. Select it, in the =
+ General tab of the Properties view and select HelloWorld as a port type in the PortType. Then click on the =
+ Generate Binding Content... b=
utton to open the Binding Wizard. In the wizard, sele=
ct SOAP =
+ as the Protocol. Finally, cli=
ck the Finish button to close the wizard.
+
+
+ Add a Binding to the W=
SDL file
+
+
+
+
+
+ =
+
+
+ Click the HelloWorldProcessPort property in the General section of the Properties view, select HelloWorldSOAPBinding in
+ the Binding combobox. In the =
Address field input http://localhost:8080/bpel/processes/Hell=
oWorld?wsdl.
+
+
+ Add the HelloWorldSOAPBinding to the HelloWorldProcessPort
+
+
+
+
+
+ =
+ =
+ You should also change some servic=
e part configurations.
+ To do this,click part element in the WSDL editor,
+ then put the following data in the Properties view=
. =
+
+
+ Configuration of service part
+
+
+
+
+
+ =
+
+
+ =
+ Now you have finished creating a simple BPEL process.As =
a next step, you can deploy the BPEL project to JBoss BPEL Runtime. =
=
+ =
+ =
+ =
+
+
+ Deploy a JBoss BPEL project to JBoss BPEL Runtime
+
+ Creating a bpel-deploy.xml file
+ If you want to deploy a BPEL project to JBoss BPEL Runti=
me, you should create a bpel-deploy.xml file. =
+ JBoss tools can help you to create it:
+
+
+
+ Create the bpel-deploy.xml by selecting =
+ New > Other... > BPEL 2.0 > Ap=
ache ODE Deployment Descriptor. Click the N=
ext button. =
+
+
+ New BPEL Deploy file
+
+
+
+
+
+ =
+
+
+ On the next wizard page you should enter the fol=
lowing information:
+ BPEL Project: Click the Browse... button to select the BPEL=
project in your workspace which you want to deploy to the runtime.
+ Please note, that you should select the =
bpelContent folder in your new BPEL project as a value of BPEL Project field because the bpel-deploy.xml should be cre=
ated in this place.
+
+ File name: The default value is bpel-deploy.xml. Please, don't change it.
+ Click on Finish button to c=
lose the wizard and a new bpel-deploy.xml file will be created.
+
+ New BPEL Deploy file Wizard
+
+
+
+
+
+ =
+
+
+ Double-click the bpel-deploy.xml file to open it=
in ODE Descriptor Deployment Editor.
+ In the Inbound Interfaces sec=
tion, click the =
+ Associated Port column and se=
lect HelloWorldProcessPort
+ in the dropdown box.The Related Service<=
/property> and Binding Used =
+ columns should be automatically filled in. Save t=
he bpel-deploy.xml.
+
+
+ bpel-deploy.xml file editor
+
+
+
+
+
+ =
+ =
+
+
+
+ Creating JBoss BPEL Server
+ Suppose you have installed the JBoss BPEL Runt=
ime-RiftSaw as it was described before, now you can create a server for JBoss BPEL runtime.
+
+
+ Open the Servers view by se=
lecting =
+ Windows > Show View > Other...=
> Server > Servers.
+ =
+
+
+ Right-click the Servers view and select =
+ New > Server to open the New Server Wizard: =
+
+
+ New Server Wizard
+
+
+
+
+
+ =
+
+
+ Select JBoss AS 5.1 as a se=
rver type.
+
+ Please note, that only JBoss As 5.1 or highe=
r version supports BPEL.
+
+
+
+ =
+ Click the Next button. On t=
he next page, you should input your JBoss As=
location. Then click the Next button and
+ you will get the page like this: =
+
+
+ Add resource to the server
+
+
+
+
+
+ =
+
+
+ Select HelloWorld, then cli=
ck the Add button to add the project to the server.
+ Then click on the Finish butt=
on.
+
+ Start the server by right-clicking on the server=
and selecting the Start item. =
+ =
+
+ The started server
+
+
+
+
+
+ =
+ If some aspects of server creation is not clear,=
please, read JBoss Server Manager Reference Guide for more details.
+
+
+ You can enter the link http://localhost:8080/bpel/processes.html=
ulink> to the browser to get the deployed processes. =
+
+ The BPEL console
+
+
+
+
+
+ =
+ =
+ =
+ If there's anything we didn't cover or you can't figure =
out, please feel free to visit our JBoss Tools Users Forum to ask questions.
+ There we are also waiting for your suggestions and comment=
s. =
+
+
+
--===============0933363944957474746==--