Interesting! JDeveloper deploy to remote server uses HTTP POST

Question

The documentation clearly mentions that the bpelc ant task only deploys to local server using a file copy. I was wondering how JDeveloper is able to deploy to remote servers. Turns out is just does a HTTP POST of multipart/form-data to upload the BPEL suitcase jar file. Given below is the trace of the POST. Of course, it is all proprietary for now and is not documented. Maybe Oracle can wrap this as a custom ant task?
--Nizam
POST /integration/services/deploy/deployProcess.jsp HTTP/1.1
Host: bpel.server.com:9700
Connection: Keep-Alive, TE
TE: trailers, deflate, gzip, compress
User-Agent: RPT-HTTPClient/0.3-3
BPELDomain: default
BPELPassword: bpel
Accept-Language: en
Accept-Encoding: gzip, x-gzip, compress, x-compress
Content-type: multipart/form-data;boundary=*****
Content-length: 10690
Content-Disposition: form-data; name="upload";BPELDomain="default"; filename="E:\work\MyBPELWS\HelloWorld\output\bpel_HelloWorld_1.0.jar"
PK..
........3................META-INF/....PK..
........3...#............META-INF/MANIFEST.MFManifest-Version: 1.0
Process-GUID: MD5{9d2c0a4b850da042548cc6bdf1c04d68}
Created-By: 1.4.2_06 (Sun Microsystems Inc.)
Process-Id: HelloWorld
Timestamp: 1124360790893
Process-Class: BPEL
Implementation-Package: bpel.p0
Revision-Tag: 1.0
PK..
........3................BPEL-INF/PK..
........3.\.Z............bpel.xml<?xml version="1.0" encoding="UTF-8"?>
<BPELSuitcase guid="MD5{9d2c0a4b850da042548cc6bdf1c04d68}" timestamp="1124360790893" revision="1.0">
<BPELProcess process-impl="bpel.p0.BPEL_BIN" src="HelloWorld.bpel" id="HelloWorld">
<partnerLinkBindings>
<partnerLinkBinding name="client">
<property name="wsdlLocation">HelloWorld.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
</BPELProcess>
</BPELSuitcase>
PK..
........3[...5...5.......build.xml<?xml version="1.0" ?>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Run cxant on this file to build, package and deploy the
HelloWorld BPEL process
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<project name="HelloWorld" default="main" basedir=".">
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Name of the domain the generated BPEL suitcase will be deployed to
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<property name="deploy" value="default" />
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
What version number should be used to tag the generated BPEL archive?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<property name="rev" value="1.0" />
<target name="main">
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
the bpelc task compiles and package BPEL processes into versioned BPEL
archives (bpel_...jar). See the "Programming BPEL" guide for more
information on the options of this task.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<bpelc input="${basedir}/bpel.xml" rev="${rev}" deploy="${deploy}" />
</target>
</project>PK..
........3,.JaZ...Z.......graphics.xml<?xml version = '1.0' encoding = 'UTF-8'?>
<graphics>
<partnerlink_locations>
<partnerlink name="client" x="15" y="215" side="left"/>
</partnerlink_locations>
<diagram popupeditor="false" centerzoom="true" validateonload="true" confirmbeforedelete="true" SELECTED_PARTNERLINK_COLOR="0,0,153" SWIMLANE_BACKGROUND="255,255,225" SWIMLANE_DIVIDER_BACKGROUND="236,233,216" GRAPH_BACKGROUND="255,255,255" SELECTED_BORDER_BACKGROUND="204,255,204" CONNECTED_PARTNERLINK_COLOR="204,204,255" CONNECTABLE_PARTNERLINK_COLOR="0,0,255" UNCONNECTED_PARTNERLINK_COLOR="192,192,192"/>
</graphics>
PK..
........3O ..............HelloService.wsdl<definitions
targetNamespace="http://tempuri.org/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:s0="http://tempuri.org/"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
<import namespace="http://tempuri.org/" location="http://localhost/HelloEnglish/Service1.asmx?WSDL"/>
<plnk:partnerLinkType name="Service1Soap_PL">
<plnk:role name="Service1Soap_Role">
<plnk:portType name="s0:Service1Soap"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
PK..
........3.....
......HelloWorld.bpel<!--
// Oracle JDeveloper BPEL Designer
// Created: Fri Aug 05 00:05:52 IST 2005
// Author: nizam
// Purpose: Synchronous BPEL Process
-->
<process name="HelloWorld" targetNamespace="http://xmlns.oracle.com/HelloWorld" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:client="http://xmlns.oracle.com/HelloWorld" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"><!-- ================================================================= --><!-- PARTNERLINKS --><!-- List of services participating in this BPEL process --><!-- ================================================================= -->
<partnerLinks><!--
The 'client' role represents the requester of this service. It is
used for callback. The location and correlation information associated
with the client role are automatically set using WS-Addressing.
-->
<partnerLink name="client" partnerLinkType="client:HelloWorld" myRole="HelloWorldProvider"/>
</partnerLinks><!-- ================================================================= --><!-- VARIABLES --><!-- List of messages and XML documents used within this BPEL process --><!-- ================================================================= -->
<variables><!-- Reference to the message passed as input during initiation -->
<variable name="inputVariable" messageType="client:HelloWorldRequestMessage"/><!--
Reference to the message that will be returned to the requester
-->
<variable name="outputVariable" messageType="client:HelloWorldResponseMessage"/>
</variables><!-- ================================================================= --><!-- ORCHESTRATION LOGIC --><!-- Set of activities coordinating the flow of messages across the --><!-- services integrated within this business process --><!-- ================================================================= -->
<sequence name="main"><!-- Receive input from requestor.
Note: This maps to operation defined in HelloWorld.wsdl
-->
<receive name="receiveInput" partnerLink="client" portType="client:HelloWorld" operation="process" variable="inputVariable" createInstance="yes"/><!-- Generate reply to synchronous request -->
<assign name="Assign_1">
<copy>
<from expression="concat("v1.1: Hello ", bpws:getVariableData('inputVariable','payload','/client:HelloWorldProcessRequest/client:input'))"/>
<to variable="outputVariable" part="payload" query="/client:HelloWorldProcessResponse/client:result"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="client" portType="client:HelloWorld" operation="process" variable="outputVariable"/>
</sequence>
</process>PK..
........3.....
......HelloWorld.wsdl<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloWorld"
targetNamespace="http://xmlns.oracle.com/HelloWorld"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/HelloWorld"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
.<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.TYPE DEFINITION - List of services participating in this BPEL process
.The default output of the BPEL designer uses strings as input and
.output to the BPEL Process. But you can define or import any XML
.Schema type and us them as part of the message types.
.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
.<types>
..<schema attributeFormDefault="qualified"
...elementFormDefault="qualified"
...targetNamespace="http://xmlns.oracle.com/HelloWorld"
...xmlns="http://www.w3.org/2001/XMLSchema">
...<element name="HelloWorldProcessRequest">
....<complexType>
.....<sequence>
......<element name="input" type="string"/>
.....</sequence>
....</complexType>
...</element>
...<element name="HelloWorldProcessResponse">
....<complexType>
.....<sequence>
......<element name="result" type="string"/>
.....</sequence>
....</complexType>
...</element>
..</schema>
.</types>
.<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.MESSAGE TYPE DEFINITION - Definition of the message types used as
.part of the port type defintions
.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
.<message name="HelloWorldRequestMessage">
..<part name="payload" element="client:HelloWorldProcessRequest"/>
.</message>
.<message name="HelloWorldResponseMessage">
..<part name="payload" element="client:HelloWorldProcessResponse"/>
.</message>
.<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.PORT TYPE DEFINITION - A port type groups a set of operations into
.a logical service unit.
.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
.<!-- portType implemented by the HelloWorld BPEL process -->
.<portType name="HelloWorld">
..<operation name="process">
...<input message="client:HelloWorldRequestMessage" />
...<output message="client:HelloWorldResponseMessage"/>
..</operation>
.</portType>
.<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.PARTNER LINK TYPE DEFINITION
.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
.<plnk:partnerLinkType name="HelloWorld">
..<plnk:role name="HelloWorldProvider">
...<plnk:portType name="client:HelloWorld"/>
..</plnk:role>
.</plnk:partnerLinkType>
</definitions>
PK..
........3..............................META-INF/....PK..
........3...#......................+...META-INF/MANIFEST.MFPK..
........3..........................T...BPEL-INF/PK..
........3.\.Z......................{...bpel.xmlPK..
........3[...5...5.................i...build.xmlPK..
........3,.JaZ...Z.....................graphics.xmlPK..
........3O ........................I...HelloService.wsdlPK..
........3.....
....................HelloWorld.bpelPK..
........3.....
....................HelloWorld.wsdlPK...............&....
*****

Answer 1

If anyone is interested, I've created a custom ant taks to leverage this HTTP post for deploying the BPEL suitcase jar to remote servers. We didn't want to use FTP, as we'd have to change permissions on the files.
To do this, I've leveraged the oracle.tip.pc.infra.deploy.DeployRemote class. You just have to pass it the path the the jar, server url (http://host:port/deploy/deployProcess.jsp), domain, and password.
This seems to work fine for us.
-Mike