Recently, I have installed the Oracle SOA Suite 10.1.3.1 on my Win XP laptop. Amazingly, the installation went well and the whole suite was installed in less then 15 minutes…so far so good. I have chosen for an advanced installation on my Oracle Express installation, so the suite is installed in a separate OC4J container named oc4j_soa.
I also installed JDeveloper 10.1.3.2 on my laptop to build and deploy bpel processes with. JDeveloper uses Ant to deploy bpel processes. You can right-click your bpel project and choose the deploy option to deploy the process to your BPEL Process Manager (BPM) installation or you can use the build.xml file in project directly.
JDeveloper uses standard property settings (e.g oc4j instance and port settings) for deployement. The standard settings assume for example that the BPM is installed in the home oc4j instance. These settings plays an important role in deploying the jsp task forms generated in JDeveloper for a human task. Because I have a different SOA suite environment, I needed to change these default settings to successfully deploy my process including the jsp task forms. The reason why I wrap this fact in a posting is because I have to find out myself which files are responsible for the bpel Ant settings. There are two places where you can change the default bpel ant properties:
- build.properties file in your project. This file is used when you want to override the default settings on project scope
- ant-orabpel.properties file located in \bpel\utilities. The default settings are stored in this file. So make changes here when you want to change settings globally
Please make sure that you use the deploy target from the build.xml to use the changed settings in the build.properties file. When you use the deploy actions from the project options menu (rigth-click on project root node) the settings are ignored. I think it uses in that situation a default build file instead the build file from the project.
February 17th, 2007 at 08:41:55
[...] Original post by Tom Hofte [...]
May 24th, 2007 at 14:47:03
hi
i did changes in ant-orabpel.properties. But then also If I run Ant file – build.xml JDev takes
localhost:9700. Is this hardcoded some where in JDev.?
But build.properties hepls to override these.
May 24th, 2007 at 15:14:40
Yes, change the build.properties file..
You can also run ant in debug mode to see which properties are used..
Succes and let me know if things work
June 1st, 2007 at 13:55:13
hi Tom,
thanks.I worked. Now as far as I am using JDev to run build.xm It runs successfully. But I want to run this build.xml file from the simple command propmt.In that case It gives error like:
“Couldn’t find validateTask definition.”
This means ant is not able to find jar or class for this custom task. But the line
in build.xml file includes the file which will update the classpath for BPEL PM custom ant tasks.
This line is not throwing error so it means file is gettin imported.
So I am not getting whts worng…??
Any suggestion for this..??? Try to run build.xml from normal command prompt..Let me knw.
thanks
/mishit
June 6th, 2007 at 10:35:23
Hi Mishit,
Do the following changes in the build.xml file to run it from command prompt.
Add bpel.home property to point to your /bpel directory
Then comment the following lines
Alternatively you can set the BPEL_HOME environment variable to point to your /bpel directory. In this case no change is required to the build.xml.
Riyaz
June 6th, 2007 at 10:39:54
Hi Mishit,
Do the following changes in the build.xml file to run it from command prompt.
Add bpel.home property to point to your OracleSOAHOME’s bpel directory and comment the lines in the build.xml for setting the bpel.home property. These lines check if BPEL_HOME env property is available and if not sets bpel.home to point to JDev’s bpel directory.
Alternatively you can set the BPEL_HOME environment variable to point to your /bpel directory. In this case no change is required to the build.xml.
Riyaz
June 13th, 2007 at 15:09:34
Hi,
I stuck up with an issue related to Ant and build.xml. I created a BPEL project in JDeveloper 10.1.3.2.0 that has a jar as dependency. I added this jar as a library via project properties. Now when I try to deploy the project by “Run Ant” command on build.xml, it deploy the project but doesn’t include the dependency jar file in BPEL suitcase jar.
I wonder that when I deploy the project by JDeveloper, it properly add the dependency jar in BPEL suitcase jar.
Iam not able to find out why this happens.
March 2nd, 2009 at 09:22:08
I have created a customized build.xml file using .
I have also deployed the process through ANT.
But I am not able to open it up in the console. WSDL doesn’t contain ws-addressing thats why I am not able to open it up in console.
Could anybody tell me why this is happening?
How ws-addressing is done by server while process depolyement?
This is very urgent to me,