How to get a BPEL process running with ServiceMix JBI Container and Fivesight's
PXE :
===
1) The first step is to create a BPEL process with the corresponding WSDL files.
Examples bundled with PXE can serve as a quickstart.
2) Remove any concrete bindings in the WSDL Files (
binding and service XML tags). Indeed, the endpoints are JBI proxies, so the
SOAP over HTTP bindings are useless here. PXE and ServiceMix will take care of
registering ports as JBI Service endopints.
3) Compile your BPEL process and WSDL files
let's say the main WSDL file describing the process is in the
MissionPlanningProcess.wsdl (this file must import the other WSDL files that
are
used :
REM add the resources to PXE's Resources Repository MissionPlanning.rr
rradd -wsdl file:MissionPlanningProcess.wsdl MissionPlanning.rr
REM compile the BPEL
bpelc -rr MissionPlanning.rr -wsdl file:MissionPlanningProcess.wsdl
file:MissionPlanning.bpel
4) Create a pxe-system.xml file that describes how to bind the BPEL process to
actual JBI endpoints. (PXE's deployment descriptor)
Let's say that the MissionPlanning process provides 3 portTypes :
proc:ProcessPT, proc:CallbackPT, resp:ResponderPT.
We want to expose 2 services :
ProcessSVC that exposes the proc:processPT and proc:CallbackPT porttypes
and
ResponderSVC that exposes the resp:ResponderPT portType.
(same names as the Async example bundled with PXE)
the corresponding pxe-system.xml file would be :
http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.fivesight.com/pxe/system-descriptor/
http://www.fivesight.com/pxe/system-descriptor/"
wsdlUri="file:MissionPlanningProcess.wsdl"
xmlns="http://www.fivesight.com/pxe/system-descriptor/"
xmlns:proc="uri:concordia.ciise.weather.process"
xmlns:resp="uri:concordia.ciise.weather.responder">
Trackback: http://tb.blog.youkuaiyun.com/TrackBack.aspx?PostId=486262
本文档详细介绍了如何使用Fivesight的PXE工具和服务混合(JBI)容器来部署并运行BPEL流程。主要步骤包括创建BPEL流程及对应的WSDL文件,移除具体绑定,编译流程文件,并通过pxe-system.xml文件定义服务端点。
103

被折叠的 条评论
为什么被折叠?



