Bpel deployment fails for all processes that have revision other than 1.0.

Question

Using: Release *10.1.3.3.1*
Hello All,
Bpel deployment fails for all processes that have revision other than *1.0*.
We have been attempting to deploy several BPEL projects via ANT script to a target environment and are encountering failures to deploy for every project which isn’t a (revision 1.0). We are getting the following error whenever we try to deploy a process with a revision other than 1.0:
D:\TJ_AutoDeploy\BPEL_AutoDeploy_BETA\build.xml:65: BPEL archive doesnt exist in directory "{0}"
     at com.collaxa.cube.ant.taskdefs.DeployRemote.getJarFile(DeployRemote.java:254)
     at com.collaxa.cube.ant.taskdefs.DeployRemote.deployProcess(DeployRemote.java:409)
     at com.collaxa.cube.ant.taskdefs.DeployRemote.execute(DeployRemote.java:211)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
     at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
     at org.apache.tools.ant.Main.runBuild(Main.java:668)
     at org.apache.tools.ant.Main.startAnt(Main.java:187)
     at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
     at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
The structure of our automated deployment script is as follows:
First, a batch script calls (Jdeveloper_BPEL_Prompt.bat) in order to set all necessary environment variables i.e. ORACLE_HOME, BPEL_HOME, ANT_HOME, etc for ant.
Next, the script lists every .jar file within the directory to an .ini file called BPEL_List.ini. Furthermore, BPEL_DIR, ADMIN_USER and ADMIN_PSWD variables are set and initialized respectively to:
-     “.” – point to directory where script is running from because all the BPEL processes are located here
-     “oc4jadmin”
-     “*********” (whatever the password for out environment is)
We’ve developed a method to have the script prompt the user to select the target environment to deploy to. Once the user selects the appropriate environment, the script goes through the BPEL_List.ini files and a loop tells it that for every BPEL process listed:
DO ant
-Dprocess.name=%%b
-Drev= !Rev!
-Dpath=%BPEL_DIR%
-Ddomain=default
-Dadmin.user=%ADMIN_USER%
-Dadmin.password=%ADMIN_PWD%
-Dhttp.hostname=%HOST%
-Dhttp.port=%PORT%
-Dverbose=true
(What’s happening is that the variables in the batch file are being passed on to the ANT script where *%%b* is the process name, !rev! is revision #, and so on…)
The loop goes through each line in the BPEL_List.ini and tokenizes the BPEL process into 3 parts *(%%a, %%b, and %%c)* but we only extract 2 parts: *%%b* (process name) and *%%c* which becomes !Rev! (revision number).
Example:
Sample BPEL process:
bpel_ThisIsProcess1_1.0.jar
bpel_ThisIsProcess2_SOAv2.19.0.001B.jar
After tokenizing:
%%a     %%b     %%c
bpel     ThisIsProcess1     1.0.jar
bpel     ThisIsProcess2     SOAv2.19.0.001B.jar
*!Rev!* and not *%%c* because *%%c* will return whatever the revision number is + the “.jar” file extension as illustrated above. So to circumvent this, we parse *%%c* so that the last 4 characters are stripped. Such is done like this:
set RevN=%%c
set RevN=!RevN:~0,-4!
Hence, the usage of !Rev!.
Below is a screenshot post of the ANT build.xml that goes with our script:
<!--<?xml version="1.0"?>-->
<!--BUILD.XML-->
<project name="bpel.deploy" default="deployProcess" basedir=".">
     <!--
     This ant build file was generated by JDev to deploy the BPEL process.
     DONOT EDIT THIS JDEV GENERATED FILE. Any customization should be done
     in default target in user created pre-build.xml or post-build.xml
     -->
     <property name="process.dir" value="${basedir}" />
          <!-- Set BPEL process name -->
          <!--
          <xmlproperty file="${process.dir}/bpel/bpel.xml"/>
          <property name="process.name" value="${BPELSuitcase.BPELProcess(id)}"/>
          <property name="rev" value="${BPELSuitcase(rev)}"/>
          -->
     <property environment="env"/>
     <!-- Set bpel.home from developer prompt's environment variable BPEL_HOME -->
          <condition property="bpel.home" value="${env.BPEL_HOME}">
               <available file="${env.BPEL_HOME}/utilities/ant-orabpel.xml" />
          </condition>
     <!-- show that both bpel and oracle.home are located (TESTING purposes ONLY) -->
     <!-- <echo>HERE:${env.BPEL_HOME} ${env.ORACLE_HOME}</echo> -->
     <!-- END TESTING -->
     <!--If bpel.home is not yet using env.BPEL_HOME, set it for JDev -->
     <property name="oracle.home" value="${env.ORACLE_HOME}" />
     <property name="bpel.home" value="${oracle.home}/bpel" />
     <!--First override from build.properties in process.dir, if available-->
     <property file="${process.dir}/build.properties"/>
     <!--import custom ant tasks for the BPEL PM-->
     <import file="${bpel.home}/utilities/ant-orabpel.xml" />
     <!--Use deployment related default properties-->
     <property file="${bpel.home}/utilities/ant-orabpel.properties" />
     <!-- *************************************************************************************** -->
     <target name="deployProcess">
          <tstamp>
               <format property="timestamp" pattern="MM-dd-yyyy HH:mm:ss" />
          </tstamp>
          <!-- WRITE TO LOG FILE #tjas -->
          <record name="build_verbose.log" loglevel="verbose" append="true" />
          <record name="build_debug.log" loglevel="debug" append="true" />
          <echo></echo>
          <echo>####################################################################</echo>
          <echo>BPEL_AutoDeploy initiated @ ${timestamp}</echo>
          <echo>--------------------------------------------------------------------</echo>
          <echo>Deploying ${process.name} on ${http.hostname} port ${http.port} </echo>
          <echo>--------------------------------------------------------------------</echo>
          <deployProcess
               user="${admin.user}"
               password="${admin.password}"
               domain="${domain}"
               process="${process.name}"
               rev="${rev}"
               dir="${process.dir}/${path}"
               hostname="${http.hostname}"
               httpport="${http.port}"
               verbose="${verbose}" />
          <sleep seconds="30" />
          <!--<echo message="${process.name} deployment logged to ${build_verbose.log}"/>
          <echo message="${process.name} deployment logged to ${build.log}"/> -->
     </target>
     <!-- *************************************************************************************** -->
</project>
SUMMARY OF ISSUE AT HAND:
~ Every bpel process w/ 1.0 revision deploys with no problems
~ At first I would get an invalid character error most likely due to the “!” preceding “Rev”, but then I decided to set rev=”false” in the build.xml file. That didn’t work quite well. In another attempt, I decided to leave the –Drev= attribute within the batch script blank. That still led to 1.0s going through. My next thought was deploying something other than a 1.0, such as 1.2 or 2.0 and that’s when I realized that if it wasn’t a 1.0, it refused to go through.
QUESTIONS:
1.     IS THERE A WAY TO HAVE ANT LOOK INTO THE BPEL PROCESS AND PULL THE REVISION ID?
2.     WHAT ARE WE DOING WRONG? ARE WE MISSING ANYTHING?
3.     DID WE GO TOO FAR? MEANING, IS THERE A MUCH EASIER WAY WE OVERLOOKED/FORGOT/OR DON’T KNOW ABOUT THAT EXISTS?
Edited by: 793292 on Jul 28, 2011 12:38 PM

Answer 1

Only thing i can think of is instead of using a MAC ACL , u cud jus use the default class
Policy Map Test
class class-default
police 56000 8000 exceed-action drop
Class Map match-any class-default (id 0)
Match any
You would be saving a MAC-ACL ;-).