Ramkumar Menon's Blog tag:blogs.oracle.com,2008:/rammenon//86 2008-07-02T19:04:15Z Principal Consultant Movable Type Enterprise 1.52-en-voltron-r47459-20070213 An attempt on 8 Queens Problem tag:blogs.oracle.com,2008:/rammenon//86.5127 2008-07-01T07:07:29Z 2008-07-02T19:04:15Z I was trying out a different approach to 8-Queen's problem. I visualized each cell [that has a coordinate from (0,0) to (7,7) as a single number 10x + y. So you would have sort of an octal number set from... Ramkumar Menon I was trying out a different approach to 8-Queen's problem. I visualized each cell [that has a coordinate from (0,0) to (7,7) as a single number 10x + y. So you would have sort of an octal number set from 0 to 77. Each column would be 0-7, 10-17, 20-27 etc and so on till 70-77.
Each row would be 0-70, 1 to 71 etc, in increments of 10.

7 17 27 37 47 57 67 77
6 16 26 36 46 56 66 76
5 15 25 35 45 55 65 75
4 14 24 34 44 54 64 74
3 13 23 33 43 53 63 73
2 12 22 32 42 52 62 72
1 11 21 31 41 51 61 71
0 10 20 30 40 50 60 70

The solution was a recursive function that takes in a current column index [ranging from 0 to 7], and computing the matching lists of size 8, after applying an exclusion rule.

The exclusion rule is interesting.
For an item with value, lets say 43, the exclusion rule would test the row-wise, columnwise and diagonal collisions through a simple modulo-checking logic. The code is given below. Note that the code has not been subjected to any review, including self-review, though it generates the required 92 distinct permutations as the 8Q solution demands.

package equeen;

import java.io.FileWriter;

import java.util.ArrayList;
import java.util.List;
import java.util.Stack;

public class EightQueens {

public boolean computeMatches(int rowIndex, List matchedList) throws Exception{
if(matchedList.size() == 8) {
printToFile(matchedList);
}
boolean matched = false;
for(int i = 10*rowIndex ; i <= 10*rowIndex + 7 ; i++) {
int cellValue = i;
boolean isExcluded = computeExclusionRule(cellValue, matchedList);
if(!isExcluded) {
matched = true;
matchedList.add(cellValue);
if(computeMatches(rowIndex+1,matchedList)) matched = !matched;
}
}

if(!matched && matchedList.size() > 0) {
matchedList.remove(matchedList.size() - 1);
return true;

}
else return false;
}

private boolean computeExclusionRule(int value, List matchedList) {
for(int i = 0 ; i < matchedList.size() ; i++) {
int prevNumber = Integer.parseInt("" + matchedList.get(i));
int diff = (value - prevNumber);
if((diff % 9 == 0 && (prevNumber % 10 > value % 10)) ||
(diff % 10 == 0) ||
(diff % 11 == 0 && (prevNumber % 10 < value % 10))) {
return true;
}
}
return false;
}

public static void main(String[] args) throws Exception {
EightQueens q = new EightQueens();
List emptyList = new ArrayList();
int ZEROTHCOLUMN_INDEX = 0;
long t = System.currentTimeMillis();
q.computeMatches(ZEROTHCOLUMN_INDEX,emptyList);
System.err.println("Number of ms for execution - " + (System.currentTimeMillis() - t));
}

private static FileWriter fw = null;
private static void printToFile(List matchedList) throws Exception {
if(fw == null) {
fw = new FileWriter("d:\\temp\\results.log");
}
String str = "";
for(int i = 0 ; i < matchedList.size() ; i++) {
int itemValue = Integer.parseInt("" + matchedList.get(i));
str += getCoords(itemValue) + " ";

}
fw.write(str + "\r\n");
fw.flush();
}
private static String getCoords(int cellValue) {
int x = cellValue/10;
int y = cellValue % 10;
return "(" + x + "," + y + ")";
}

}

]]> Invoking an EJB Session Bean from a BPEL Process tag:blogs.oracle.com,2008:/rammenon//86.2637 2008-05-16T23:30:07Z 2008-07-02T19:05:09Z EJB session beans can be invoked from a BPEL process through WSIF. Oracle BPEL PM ships with a WSIF provider for invoking EJBs. For demonstrating this, lets create a new EJB session bean. The session bean shall have one single... Ramkumar Menon

EJB session beans can be invoked from a BPEL process through WSIF. Oracle BPEL PM ships with a WSIF provider for invoking EJBs.

For demonstrating this, lets create a new EJB session bean. The session bean shall have one single business method namely "greetUser" that takes in a string argument userName, and returns a string value "Hello &lt;USERNAME>".

Step 1: Creating the HelloWorld Session Bean.


  1. Create a new BPEL empty process project.
  2. Open up the New Gallery and choose to create a new EJB session bean.



  3. Choose the option for creating EJB 2.1 session bean. Give the Bean the name"HelloWorld", accept the remaining defaults and finish the wizard.
  4. Double click on the EJB in the Applications Navigator to bring up the EJB Module Editor". Specify the new business method in the "Methods" tab. Type in the parameter name and type manually in the text editor



  5. CLick ok to accept the changes. Click on the "orion-ejb-jar.xml" in the Applications Navigator. Here you need to provide the JNDI locaiton of the session bean. For this, add a "location" attribute on the &lt;SESSION-DEPLOYMENT>to provide the JNDI "ejb/session/HelloWorld".



    view plaincopy to clipboardprint?


    1. &lt;?xml version = '1.0' encoding = 'windows-1252'?>  
    2. &lt;orion-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  
    3.   xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-ejb-jar-10_0.xsd"  
    4.     schema-major-version="10" schema-minor-version="0">  
    5.     &lt;enterprise-beans>  
    6.         &lt;session-deployment name="HelloWorld" location="ejb/session/HelloWorld"/>  
    7.     &lt;/enterprise-beans>  
    8. &lt;/orion-ejb-jar>

  6. Your bean is now ready for deployment. Build the project and deploy to an OC4J container.

Step 2: Build the BPEL Process




  1. Create a new BPEL Process project.
  2. Create a new WSDL document in the project directory and name it HelloWorldEJB.wsdl.
  3. Add the bindings section that allow the process to invoke the EJB through WSIF. The salient portion of the bindings section is the jndiProviderURL. For an Application Server install, use the opmn ormi jndi provider URL. For standalone installations,use plain ormi provider URLs. The ejbName in the provider URL is the ejbName value in the ejb-jar.xml that was created as a part of the EJB session bean creation.





      view plaincopy to clipboardprint?


      1. &lt;?xml version="1.0" ?>  
      2. &lt;definitions targetNamespace="http://samples.otn.com/"  
      3.              xmlns:tns="http://samples.otn.com/"  
      4.              xmlns:xsd="http://www.w3.org/2001/XMLSchema"  
      5.              xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/"  
      6.              xmlns:ejb="http://schemas.xmlsoap.org/wsdl/ejb/"  
      7.              xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"  
      8.              xmlns="http://schemas.xmlsoap.org/wsdl/">  
      9.   &lt;!-- message declns -->  
      10.   &lt;message name="HelloWorldRequestMessage">  
      11.     &lt;part name="userName" type="xsd:string"/>  
      12.   &lt;/message>  
      13.   &lt;message name="HelloWorldResponseMessage">  
      14.     &lt;part name="message" type="xsd:string"/>  
      15.   &lt;/message>  
      16.   &lt;!-- port type declns -->  
      17.   &lt;portType name="HelloWorldPT">  
      18.     &lt;operation name="greetUser">  
      19.       &lt;input name="HelloWorldRequest" message="tns:HelloWorldRequestMessage"/>  
      20.       &lt;output name="HelloWorldResponse"  
      21.               message="tns:HelloWorldResponseMessage"/>  
      22.     &lt;/operation>  
      23.   &lt;/portType>  
      24.   &lt;!-- binding declns -->  
      25.   &lt;binding name="EJBBinding" type="tns:HelloWorldPT">  
      26.     &lt;ejb:binding/>  
      27.     &lt;format:typeMapping encoding="Java" style="Java">  
      28.       &lt;format:typeMap typeName="xsd:string" formatType="java.lang.String"/>  
      29.     &lt;/format:typeMapping>  
      30.     &lt;operation name="greetUser">  
      31.       &lt;ejb:operation methodName="greetUser" parameterOrder="userName"  
      32.                      interface="remote" returnPart="message"/>  
      33.       &lt;input name="HelloWorldRequest"/>  
      34.       &lt;output name="HelloWorldResponse"/>  
      35.     &lt;/operation>  
      36.   &lt;/binding>  
      37.   
      38.   &lt;!-- service decln -->  
      39.   &lt;service name="HelloWorldService">  
      40.     &lt;port name="EJBPort" binding="tns:EJBBinding">  
      41.       &lt;!-- Put vendor-specific deployment information here -->  
      42.       &lt;ejb:address className="helloworldbean.HelloWorldHome"  
      43.            jndiName="ejb/session/HelloWorld"  
      44.            initialContextFactory="com.evermind.server.rmi.RMIInitialContextFactory"  
      45.    jndiProviderURL="opmn:ormi://serverHost:opmnRequestPort:oc4jInstanceName/ejbName"/>  
      46.     &lt;/port>  
      47.   &lt;/service>  
      48.   
      49.   &lt;plnk:partnerLinkType name="HelloWorldService">  
      50.     &lt;plnk:role name="HelloWorldServiceProvider">  
      51.       &lt;plnk:portType name="tns:HelloWorldPT"/>  
      52.     &lt;/plnk:role>  
      53.   &lt;/plnk:partnerLinkType>  
      54. &lt;/definitions>  
      55.       

    1. Create a partnerlink for the WSDL that you just created and an invoke activity that can be used to invoke the plnk.
    2. Provide the username/password for connecting to the OC4J Instance that hosts the EJB within the bpel.xml deployment descriptor. This is typically the oc4jadmin user.



      view plaincopy to clipboardprint?


      1.   
      2. &lt;?xml version = '1.0' encoding = 'UTF-8'?>  
      3. &lt;BPELSuitcase>  
      4.    &lt;BPELProcess id="HelloWorldBPELClient" src="HelloWorldBPELClient.bpel">  
      5.       &lt;partnerLinkBindings>  
      6.          &lt;partnerLinkBinding name="client">  
      7.             &lt;property name="wsdlLocation">HelloWorldBPELClient.wsdl&lt;/property>  
      8.          &lt;/partnerLinkBinding>  
      9.          &lt;partnerLinkBinding name="HelloWorld_plt">  
      10.             &lt;property name="wsdlLocation">HelloWorldEJB.wsdl&lt;/property>  
      11.             &lt;property name="java.naming.security.principal">oc4jadmin&lt;/property>  
      12.             &lt;property name="java.naming.security.credentials">welcome1&lt;/property>  
      13.          &lt;/partnerLinkBinding>  
      14.       &lt;/partnerLinkBindings>  
      15.    &lt;/BPELProcess>
      16. &lt;/BPELSuitcase>

    3. Copy the EJB compiled classes from the EJB project created earlier into the $ORACLE_HOME/bpel/system/classes directory and restart the BPEL runtime. These classes are required for BPEL to get a hold on the home interface of the EJB to create an invoke the business method.
    4. Deploy the BPEL Process and see the results for yourself

    The demo EJB and BPEL Client project can be downloaded from this link.

]]> Interesting XSLT Recipe - Computing line totals tag:blogs.oracle.com,2008:/rammenon//86.2638 2008-05-08T05:03:53Z 2008-07-02T19:06:19Z Ramkumar Menon You might have run into a requirement where you need to compute the total value of all items in a purchase order. Consider the PO XML shown below.



view plaincopy to clipboardprint?


  1.   
  2. &lt;?xml version="1.0" encoding="UTF-8" ?>  
  3. &lt;po xmlns="http://www.example.org">  
  4.    &lt;Items>  
  5.       &lt;item>  
  6.          &lt;price>1&lt;/price>  
  7.          &lt;qty>2&lt;/qty>  
  8.       &lt;/item>  
  9.       &lt;item>  
  10.          &lt;price>3&lt;/price>  
  11.          &lt;qty>4&lt;/qty>  
  12.       &lt;/item>  
  13.       &lt;item>  
  14.          &lt;price>5&lt;/price>  
  15.          &lt;qty>6&lt;/qty>  
  16.       &lt;/item>  
  17.    &lt;/Items>  
  18. &lt;/po>  
You might want to compute the total value of all items in the purchase Order. For computing this, you would need to multiply the price and qty for each item, and add them up. In XSLT 1.0, I guess the way to do this would be to recursively invoke a template that computes the sum total. In XSLT 2.0, this can be done in a very elegant single expression.



view plaincopy to clipboardprint?


  1.   
  2.   &lt;xsl:variable name="itemVar" select="/tns:po/tns:Items/tns:item"/>                
  3.   &lt;xsl:template match="/">  
  4.     &lt;tns:poSummary>  
  5.       &lt;tns:totalValue>&lt;xsl:value-of select="sum(for $i in $itemVar return ($i/tns:price * $i/tns:qty))"/>&lt;/tns:totalValue>  
  6.     &lt;/tns:poSummary>  
  7.   &lt;/xsl:template>  
  8. &lt;/xsl:stylesheet>  

]]> Viewing Audits for Stale instances tag:blogs.oracle.com,2008:/rammenon//86.2639 2008-04-23T02:41:48Z 2008-07-02T19:07:41Z Ramkumar Menon

Wondering what to do if you wished to view the audit trail for stale instances?


Well, you could make use of the View Raw XML feature in the BPEL Console.


 


 

]]> Reusing code snippets in JDeveloper tag:blogs.oracle.com,2008:/rammenon//86.2640 2008-04-22T23:11:08Z 2008-07-02T19:10:41Z Here is one simple but useful thing that I've been too lazy to make use of, and had overlooked. JDeveloper's component palette has a page named "Code Snippets". You could actually add frequently re-used code snippets and save them into... Ramkumar Menon

Here is one simple but useful thing that I've been too lazy to make use of, and had overlooked.


JDeveloper's component palette has a page named "Code Snippets". You could actually add frequently re-used code snippets and save them into the "code snippets" section.



Once you click on "Add component", you can give the snippet a name, for e.g. "Assign WS-Addressing Headers" and copy the snippet from your source code  to the given text area.


You can now re-use the code snippet by dragging and dropping the component from the code snippet palette onto the source view of any file that you open in JDeveloper.


Similarly, you can also add your own Pages to the Component palette, to capture Snippets for diferent cateogies of code [for instnace, BPEL,XML, XSD, XSLT etc].



Now you can specify the Page Name and specify the type  - "snippet", "java" etc.


 


 



 


Now you can add new code snippets to the new Palette Page that you created.


 

]]> Obtaining the Execution Times of BPEL Processes over a period of time tag:blogs.oracle.com,2008:/rammenon//86.2641 2008-04-21T23:38:06Z 2008-07-02T19:13:04Z Here is a simple BPEL Query that will get you the statistics of execution times of all BPEL Process instances over a period of time. The stats include the number of invocations, minimum, maximum and average time of execution. view... Ramkumar Menon

Here is a simple BPEL Query that will get you the statistics of execution times of all BPEL Process instances over a period of time. The stats include the number of invocations, minimum, maximum and average time of execution.





view plaincopy to clipboardprint?


  1. SELECT process_id,count(*) as num_invocations,   
  2.   max(((EXTRACT(HOUR FROM MODIFY_DATE) - extract(hour from creation_date)) *3600 +   
  3.       (EXTRACT(MINUTE FROM MODIFY_DATE) - extract(MINUTE from creation_date)) *60 +   
  4.       (EXTRACT(SECOND FROM MODIFY_DATE) - extract(SECOND from creation_date))) *1000)   
  5.   as Max_Time ,   
  6.   
  7.   min(((EXTRACT(HOUR FROM MODIFY_DATE) - extract(hour from creation_date)) *3600 +   
  8.      (EXTRACT(MINUTE FROM MODIFY_DATE) - extract(MINUTE from creation_date)) *60 +   
  9.      (EXTRACT(SECOND FROM MODIFY_DATE) - extract(SECOND from creation_date))) *1000)   
  10.   as Min_Time ,   
  11.   
  12.   avg(((EXTRACT(HOUR FROM MODIFY_DATE) - extract(hour from creation_date)) *3600 +   
  13.      (EXTRACT(MINUTE FROM MODIFY_DATE) - extract(MINUTE from creation_date)) *60 +   
  14.      (EXTRACT(SECOND FROM MODIFY_DATE) - extract(SECOND from creation_date))) *1000)   
  15.   as Avg_Time   
  16.   
  17.   FROM CUBE_INSTANCE   
  18.     WHERE  
  19.       state &lt;> 9   
  20.         and  
  21.       creation_date > '09-APR-08 09.00.00.000000000 AM'  
  22.         and  
  23.       creation_date &lt; '09-APR-08 01.00.00.000000000 PM'  
  24.   
  25.       group by process_id order by process_id asc  

In this query, you need to replace the sample date and time values with the values that you wish to use and report. Here is another query that gives the execution times of all BPEL instances over the given time period.





view plaincopy to clipboardprint?


  1.   
  2. select bpel_process_name as process_id,   
  3.        instance_key as cikey,   
  4.        trunc(creation_date),   
  5.        eval_time as exec_time   
  6. from bpel_process_instances   
  7. where state &lt;> 9 and  
  8.       creation_date > '11-APR-08 09.00.00.000000000 AM' and  
  9.       creation_date &lt; '11-APR-08 05.00.00.420000000 PM'  
  10. order by process_id asc, exec_time desc  
  11.     

In this query, you need to replace the sample date and time values with the values that you wish to use and report. Note that the above query shall give you the execution times for a particular day. Take a look at the comments on this blog entry to see a modified example that uses the "day" as well to obtain stats that span across multiple days.

]]> Dynamically updating bpel.xml properties within your BPEL Process tag:blogs.oracle.com,2008:/rammenon//86.2642 2008-04-15T22:42:09Z 2008-07-02T19:59:45Z Ramkumar Menon

There are different properties that you could actually update in your process descriptor. They are a) The Configuration properties b) The preference properties c) The partnerlink properties. These properties are illustrated below.





view plaincopy to clipboardprint?


  1. &lt;BPELSuitcase>  
  2.   &lt;BPELProcess id="UpdatePropertyProcess" src="UpdatePropertyProcess.bpel">  
  3.     &lt;partnerLinkBindings>  
  4.       &lt;partnerLinkBinding name="client">  
  5.         &lt;property name="wsdlLocation">  
  6.           UpdatePropertyProcess.wsdl   
  7.         &lt;/property>  
  8.         &lt;property name="partnerlinkProperty1">  
  9.           valueOfPartnerlinkProperty 1   
  10.         &lt;/property>  
  11.       &lt;/partnerLinkBinding>  
  12.     &lt;/partnerLinkBindings>  
  13.      &lt;preferences>  
  14.        &lt;property name="preferenceProperty1" encryption="plaintext">  
  15.          valueOfPreferenceProperty1   
  16.        &lt;/property>  
  17.      &lt;/preferences>  
  18.      &lt;configurations>  
  19.       &lt;property name="configProperty1" encryption="plaintext">  
  20.         valueOfConfigProperty1   
  21.       &lt;/property>  
  22.       &lt;/configurations>  
  23.    &lt;/BPELProcess>  
  24. &lt;/BPELSuitcase>  

To update these properties dynamically within the BPEL Process, you can use a Java embedding within the process, as shown below.





view plaincopy to clipboardprint?


  1.   
  2. try {   
  3.   getLocator().lookupProcess ("UpdatePropertyProcess").   
  4.                  getDescriptor ().   
  5.                   getConfigurations().   
  6.                     setPropertyValue ("configProperty1",   
  7.                      "newValueOfConfigPropertyValue1");   
  8.   getLocator().lookupProcess ("UpdatePropertyProcess").   
  9.                   getDescriptor ().   
  10.                    getPreferences().   
  11.                     setPropertyValue ("preferenceProperty1",   
  12.                       "newValueOfPreferenceProperty1" );   
  13.   getLocator().lookupProcess ("UpdatePropertyProcess").   
  14.                   getDescriptor ().   
  15.                    getPartnerLinkBindings().   
  16.                      getPartnerLinkBinding ("client").   
  17.                        setPropertyValue ("partnerlinkProperty1",   
  18.                        "newValueOfPartnerlinkProperty 1");   
  19.  }   
  20.  catch(Throwable ex) {   
  21.  }   
  22.    

Click here to download the Sample BPEL Process project.

]]> Recursively replacing a string in all files in a directory [Linux] tag:blogs.oracle.com,2008:/rammenon//86.2643 2008-04-14T22:05:19Z 2008-06-24T09:58:06Z Ramkumar Menon

My colleague provided me an extremely useful script that will replace a source string with a target string in all files in the current directory and its subdirectories.

find . -type f | xargs perl -pi~ -e 's/oldtext/newtext/g;'

Replace "oldtext" with the source string, and "newtext" with the target string.


During the replacement, all original files are backed up with a  "~" suffix.

]]> Reading only headers in an File/FTP Adapter and skipping the payload tag:blogs.oracle.com,2008:/rammenon//86.2644 2008-03-18T21:50:39Z 2008-06-24T09:58:07Z Ramkumar Menon

At times, you might have a requirement where you only need to read the file headers[file name and directory] and ignore the payload while using an inbound file/ftp adapter.


For this purpose, you need to add UseHeaders="true" on the &lt;jca:operation> in the adapter wsdl.


This ensures that the payload is skipped while reading the file.


Then you can follow the usual steps to read the headers [through the inputHeaderVariable on the receive activity to retrieve the headers.


 

]]> Stripping namespaces using XSLT tag:blogs.oracle.com,2008:/rammenon//86.2645 2008-03-07T03:18:37Z 2008-06-24T09:58:07Z A common question often asked is "I have a namespace qualified XML document - I need to remove all xmlns attributes from the same". Here is an XSLT that you can use to strip all namespaces from your document. view... Ramkumar Menon

A common question often asked is "I have a namespace qualified XML document -
I need to remove all xmlns attributes from the same".



Here is an XSLT that you can use to strip all namespaces from your document.





view plaincopy to clipboardprint?


  1. &lt;xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  
  2. exclude-result-prefixes="xsl">  
  3.   
  4.  &lt;xsl:template match="*">  
  5.     &lt;xsl:element name="{local-name()}">  
  6.       &lt;xsl:apply-templates select="@* | node()"/>  
  7.     &lt;/xsl:element>  
  8.   &lt;/xsl:template>  
  9.   &lt;xsl:template match="@* | text()">  
  10.     &lt;xsl:copy/>  
  11.   &lt;/xsl:template>  
  12. &lt;/xsl:stylesheet>

]]> XML is Ten! tag:blogs.oracle.com,2008:/rammenon//86.2646 2008-02-15T00:11:39Z 2008-06-24T09:58:07Z Ramkumar Menon XML 10th anniversary

]]> Scanning text files using java.util.Scanner tag:blogs.oracle.com,2007:/rammenon//86.2647 2007-12-20T02:44:37Z 2008-06-24T09:58:07Z Ramkumar Menon

I loved this tech-tip article from Sun.


http://java.sun.com/developer/JDCTechTips/2004/tt1201.html#1


 


 

]]> Miscellaneous Ant tasks for Managing the BPEL Server tag:blogs.oracle.com,2007:/rammenon//86.2648 2007-11-27T01:44:57Z 2008-07-02T20:02:22Z The serverAdmin ANT task This news item describes a simple ant task that I had come up named serverAdmin that allows you to Selectively undeploy BPEL Processes Selectively purge BPEL process instances. Cancel and Recover Invocation Messages Cancel and Recover... Ramkumar Menon The serverAdmin ANT task This news item describes a simple ant task that I had come up named serverAdmin that allows you to
  1. Selectively undeploy BPEL Processes
  2. Selectively purge BPEL process instances.
  3. Cancel and Recover Invocation Messages
  4. Cancel and Recover Callback Messages
  5. Get one or more domain configuration properties
  6. Set one or more domain configuration properties
  7. Fetch the latest domain log from the Server
  8. Create/delete a domain on the BPEL server

Setup and Usage

To setup this task, perform the following steps.
  1. Copy the admintasks.jar from http://blogs.oracle.com/ramkumarMenon/gems/admintasks.jar into $ORACLE_HOMEintegrationlib directory.
  2. Open up ant-orabpel.xml in $ORACLE_HOMEbpelutilities directory and paste the following piece of code into the file within the &lt;project> element. 
&lt;path id="admin.tasks.class.path">
      &lt;pathelement location="${bpel.home}/../lib/admintasks.jar"/>
  &lt;/path>
  &lt;property name="admin.tasks.class.path" refid="admin.tasks.class.path"/>
  &lt;taskdef name="serverAdmin" classname="com.collaxa.cube.ant.taskdefs.ServerAdmin">
    &lt;classpath>
      &lt;pathelement path="${admin.tasks.class.path}"/>
    &lt;/classpath>
  &lt;/taskdef>
Illustrative Command Syntax
      &lt;serverAdmin  providerURL="opmn:ormi://&lt;hostName>:&lt;opmnRequestPort>:&lt;oc4jInstanceName>/orabpel" userName="oc4jadmin" password="&lt;pwdforoc4jadmin>">
       &lt;createDomain domainName="testDomain"/>
       &lt;deleteDomain domainName="testDomain"/>
       &lt;manageDomain domain="default">
              &lt;undeployProcesses select="BPELProcess.*"  type="all" revision="all"/>
              &lt;undeployProcesses select="TestXPath"  type="retired" revision="all"/>
             &lt;undeployProcesses select="Sample.*" type="all" revision="2.0"/>
             &lt;undeployProcesses select="SampleProcess" type="active" revision="1.0"/>
         &lt;!--example dateTime format "yyyy-MM-dd'T'HH:mm:ss Z"   "1994-11-05T08:15:30 -0800-->
         &lt;!--example date format "yyyy-MM-dd"   "1994-11-05"-->
          &lt;purgeInstances select="TestXPath" type="all" fromDateTime="2007-10-29T11:21:03 -0800" toDateTime="2007-10-31T13:21:03 -0800"/>
          &lt;purgeInstances select="TestJMS" type="closed.stale" fromDateTime="2007-10-29T11:21:03 -0800" toDateTime="2007-10-31T13:21:03 -0800"/>
             &lt;getProperties propertyNames="dspMinThreads,dspMaxThreads,syncMaxWaitTime"/>
              &lt;setProperty name="dspMinThreads" value="5"/>
              &lt;cancelInvocations select="PurchaseOrderProcess" revision="1.0" fromDateTime="2007-11-05T17:45:56 -0800" toDateTime="2007-11-05T17:45:58 -0800"/>
              &lt;recoverInvocations select="OrderCreationProcess" revision="1.0" fromDateTime="2007-11-05T17:21:10 -0800" toDateTime="2007-11-05T17:21:15 -0800"/>
              &lt;cancelCallbacks select="OrderCreationProcess" revision="2.0" fromDate="2007-11-05" toDate="2007-11-06"/>
              &lt;recoverCallbacks select="OrdeUpdateProcess" revision="2.0" fromDate="2007-11-05" toDate="2007-11-06"/>
              &lt;printLog outFile="D:\\temp\\latest_domain.log" lineCount="2000"/>
          &lt;purgeInstances select="all" type="closed.stale" fromDate="2007-10-29" toDate="2007-10-31"/>
          &lt;purgeInstances fromDate="2007-10-29" toDate="2007-10-31"/>
          &lt;purgeInstances select="SampleProcess" type="closed.completed"  toDateTime="2007-10-31"/>
          &lt;purgeInstances select="SampleProcess2" fromDateTime="2007-10-29T11:21:03 -0800"/>
          &lt;purgeInstances select="TestXPath" type="closed.stale" fromDate="2007-10-29" />
         &lt;purgeInstances/>
        &lt;/manageDomain>
      &lt;/serverAdmin>

Short Description

UnDeployProcesses subtask:-
The select argument for "undeployProcesses" subtask accepts both exact process names, as well as java regex expressions. For instance, the above example shows undeployment for all processes whose name starts with the string "BPELProcess". All arguments are mandatory.If you wish to specify "all" values for one or more arguments, specify them in the format &lt;argName>="all". For instance, you can specify type="all" or revision="all" or select="all" to indicate selection of all process states, all revisions or all processes.
PurgeInstances subtask :-
If fromDateTime/fromDate is omitted, it purges every matching instance upto and including the "toDateTime/toDate". Note that in case you specify a date as opposed to a dateTime, the time is defaulted to the beginning of the date. [i.e. 12 AM] If the "toDateTime/toDate" is omitted, it purges every matching instance till the present. If both are specified, the task purges all matching instances including and between the given timespan. If both are omitted, the task purges all matching instances irrespective of the time. The dateTime has to be specified in the format given in the above example. The "type" attribute, if omitted, is equivalent to "all". The other values are
  1. closed.aborted
  2. closed.cancelled
  3. closed.completed
  4. closed.faulted
  5. closed.stale
  6. closed.pendingCancel
  7. initiated
  8. open.running
  9. open.faulted
  10. open.suspended
Each serverAdmin task can be used to administer a different BPEL runtime. Within each serverAdmin, you can provide multiple &lt;manageDomain> tasks, one for each domain to purge and undeploy processes and instances in each domain.
Print Log Subtask
Prints the domain log
SetProperty subtask
Sets a domain property. e.g. dspMaxThreads
GetProperties subtask
Gets the property values for the given set of domain properties.[comma separated]
Recovery/Cancellation/Deletion of Invocation or callback subtasks
Recovers, deletes or cancels invocations/callback. Arguments to this task are the processName, revision, the from/to date or dateTimes in the given format as specified in the example. [yyyy-MM-dd'T'HH:mm:ss Z or yyyy-MM-dd]
Create Domain subtask
Creates a domain with the given name.
Delete Domain subtask
Deletes the domain with the given name. Notes: Ensure that BPEL_HOME and ORACLE_HOME are properly set. &lt;p/> Sample Build File 
&lt;?xml version="1.0" encoding="iso-8859-1"?>
&lt;project name="ServerAdminBuild" default="deploy" basedir=".">
    &lt;!--=============================-->
    &lt;!-- Process deployment targets  -->
    &lt;!--=============================-->
    &lt;!-- Set bpel.home from developer prompt's environment variable BPEL_HOME -->
    &lt;condition property="bpel.home" value="${env.BPEL_HOME}">
        &lt;available file="${env.BPEL_HOME}/utilities/ant-orabpel.xml"/>
    &lt;/condition>
    &lt;!-- If bpel.home is not yet using env.BPEL_HOME, set it for JDev -->
    &lt;property name="bpel.home" value="${oracle.home}/integration/bpel"/>
    &lt;!-- First override from build.properties in process.dir, if available -->
    &lt;property file="${process.dir}/build.properties"/>
    &lt;!-- import custom ant tasks for the BPEL PM -->
    &lt;import file="${bpel.home}/utilities/ant-orabpel.xml"/>
    &lt;target name="adminTasks">
      &lt;serverAdmin  providerURL="opmn:ormi://server.host.com:6004:oc4j_soa/orabpel" userName="oc4jadmin" password="welcome1">
        &lt;manageDomain domain="default">
              &lt;undeployProcesses select="BPELProcess.*"  type="all" revision="all"/>
             &lt;getProperties propertyNames="dspMinThreads"/>
              &lt;setProperty name="dspMinThreads" value="5"/>
              &lt;cancelInvocations select="PurchaseOrderProcess" revision="1.0" fromDateTime="2007-11-05T17:45:56 -0800" toDateTime="2007-11-05T17:45:58 -0800"/>
              &lt;recoverlInvocations select="OrderCreationProcess" revision="1.0" fromDateTime="2007-11-05T17:21:10 -0800" toDateTime="2007-11-05T17:21:15 -0800"/>
              &lt;cancelCallbacks select="OrderCreationProcess" revision="2.0" fromDate="2007-11-05" toDate="2007-11-06"/>
              &lt;recoverCallbacks select="OrdeUpdateProcess" revision="2.0" fromDate="2007-11-05" toDate="2007-11-06"/>
              &lt;printLog outFile="D:\\temp\\latest_domain.log" lineCount="2000"/>
              &lt;undeployProcesses select="TestXPath"  type="retired" revision="all"/>
             &lt;undeployProcesses select="Sample.*" type="all" revision="2.0"/>
             &lt;undeployProcesses select="SampleProcess" type="active" revision="1.0"/>
         &lt;!--example dateTime format "yyyy-MM-dd'T'HH:mm:ss Z"   "1994-11-05T08:15:30 -0800-->
         &lt;!--example date format "yyyy-MM-dd"   "1994-11-05"-->
          &lt;purgeInstances select="TestXPath" type="all" fromDateTime="2007-10-29T11:21:03 -0800" toDateTime="2007-10-31T13:21:03 -0800"/>
          &lt;purgeInstances select="TestJMS" type="closed.stale" fromDateTime="2007-10-29T11:21:03 -0800" toDateTime="2007-10-31T13:21:03 -0800"/>
          &lt;purgeInstances select="all" type="closed.stale" fromDate="2007-10-29" toDate="2007-10-31"/>
          &lt;purgeInstances fromDate="2007-10-29" toDate="2007-10-31"/>
          &lt;purgeInstances select="SampleProcess" type="closed.completed"  toDateTime="2007-10-31"/>
          &lt;purgeInstances select="SampleProcess2" fromDateTime="2007-10-29T11:21:03 -0800"/>
          &lt;purgeInstances select="TestXPath" type="closed.stale" fromDate="2007-10-29" />
         &lt;purgeInstances/>
        &lt;/manageDomain>
      &lt;/serverAdmin>
    &lt;/target>
&lt;/project>
]]> <![CDATA[Customizing any BPEL Project Artifact using <customizeDocument>]]> tag:blogs.oracle.com,2007:/rammenon//86.2649 2007-11-22T22:20:25Z 2008-07-02T20:01:15Z Tokenization of artifacts in a BPEL Project This note describes a simple ant task that I had come up with that provides an easy and flexible method to enable migration of Process artifacts while deploying to multiple target environments. Problem... Ramkumar Menon

Tokenization of artifacts in a BPEL Project


This note describes a simple ant task that I had come up with that provides an easy and flexible method to enable migration of Process artifacts while deploying to multiple target environments.


Problem Statement


Most often, the BPEL process projects that you develop contain XSDs and WSDLs that fall into one or more of the following categories.
a) The artifacts themselves are hosted on a dedicated server for the specific environment. [For instance, in the OHS htdocs within the development server] The artifacts are referred from the project using absolute URLs, containing the host, port, and other server specific information.
b) The artifacts include or import other artifacts that are hosted on a dedicated server for the specific environment.
c) The WSDL contains a JNDI location that changes for each environment.
d) The WSDL defines inline schemas that contain imported remote XSDs that again are hosted on the dedicated development server.
If your process exhibits one or more of the above characteristics, then more often that not, you will encounter the challenge of automating the migration of these artifacts at deployment time, especially when you have a medium to large number of projects, and/or if you have multiple target environments to deploy to.
There are multiple approaches that are in prevelance today to tackle this.
a) The laborious error-prone way of manually replacing the URLs/JNDI names for the new environments.
b) Usage of &lt;customize> and &lt;customizeWSDL> ant tasks.


But what will be really useful is a generic customization infrastructure that enables users to tokenize any arbitrary XML based artifact within the BPEL Project that includes, but is not limited to
a) The BPEL file
b) The WSDL file(s)
c) XSDs
d) XSLT
e) Toplink Mappings
The list goes on.


Overview


The above issues are addressed through a new customization ant task, namely customizeDocument. This task is very similar in usage and behaviour to the existing customization tasks shipped with the product.
The task allows token replacements of contents of any element or attribute that can be reached through an XPath expression. The only limitation of the task is within the tokenization of Processing Instructions within your XML based documents. For instance, the Jdeveloper generated XSL Map file contains a PI indicating the URLs of the source and target XSDs for the map. These URLs cannot be tokenized using this task, nor is this supported through any of the existing customization task.



Setup and Usage


To setup this task, perform the following steps.
a) Copy the customtasks.jar available at http://blogs.oracle.com/ramkumarMenon/gems/customtasks.jar into $ORACLE_HOME\integration\lib directory.
b) Open up ant-orabpel.xml in $ORACLE_HOME\bpel\utilities directory and paste the following piece of code into the file within the &lt;project> element.



&lt;path id="custom.tasks.class.path">
    &lt;pathelement location="&lt;absolute path to location of customtasks.jar>"/>
 &lt;/path>
 
  &lt;property name="custom.tasks.class.path" refid="custom.tasks.class.path"/>


&lt;taskdef name="customizeDocument" classname="com.collaxa.cube.ant.taskdefs.customize.document.CustomizeDocument">
    &lt;classpath>
      &lt;pathelement path="${custom.tasks.class.path}"/>
    &lt;/classpath>
&lt;/taskdef> 


The usage of this task is best illustrated through a simple running example.


You have a BPEL process project named i??CreatePurchaseOrderi?? that you have deployed to the i??testi?? environment. After you have performed all the necessary tests, you wish to promote this process to the production environment.
The project contains amongst others, the process WSDL named CreatePurchaseOrderService.wsdl that imports the local Process Schema named PurchaseOrder.xsd.


The WSDL also imports another WSDL named GeneralPOHeader.wsdl that is a shared WSDL amongst multiple BPEL Processes. This WSDL is hosted on the OHS on the i??testi?? environment. The CreatePurchaseOrderService.wsdl also imports an XSD named Addressing.xsd that is again hosted on the OHS on the test environment.
Moreover, each environment is associated with a specific support group i?? that receives notification on faults and errors within processes deployed to that specific environment. The support team email is specified as a preference witihn the deployment descriptor of the BPEL process. [bpel.xml].


This is how a portion of CreatePurchaseOrderService.wsdl looks like.


&lt;?xml version = '1.0' encoding = 'UTF-8'?>
&lt;definitions name="PurchaseOrderService" targetNamespace="http://xmlns.oracle.com/PurchaseOrderService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:client="http://xmlns.oracle.com/PurchaseOrderService" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">


        &lt;import namespace="http://xmlns.po.com/general" location="http://testsoa.server.com:7780/services/GeneralPOHeader.wsdl" />


        &lt;types>
  &lt;schema xmlns="http://www.w3.org/2001/XMLSchema">
   &lt;import namespace="http://xmlns.oracle.com/CreatePurchaseOrderService" schemaLocation="CreatePurchaseOrder.xsd"/>
   &lt;import namespace="http://xmlns.po.com/addressing" schemaLocation="http://testsoa.server.com:7780/schemas/Addressing.xsd"/>
  &lt;/schema>
 &lt;/types>


         . . . . .       
&lt;/definitions>


And the following is a snippet of bpel.xml.


&lt;?xml version = '1.0' encoding = 'UTF-8'?>
&lt;BPELSuitcase>
   &lt;BPELProcess id="CreatePurchaseOrderService" src="CreatePurchaseOrderService.bpel">
      &lt;partnerLinkBindings>
         &lt;partnerLinkBinding name="client">
            &lt;property name="wsdlLocation">CreatePurchaseOrderService.wsdl&lt;/property>
         &lt;/partnerLinkBinding>
      &lt;/partnerLinkBindings>
      &lt;preferences>
         &lt;property name="supportEmail" encryption="plaintext">test_support_group@clientcompany.com&lt;/property>
      &lt;/preferences>
   &lt;/BPELProcess>
&lt;/BPELSuitcase>


Note the lines highlighted in blue. The intent is to migrate these URLs and preferences to the values applicable for production. The corresponding values in the prod environment are
a) http://prodsoa.server.com:9876/services/GeneralPOHeader.wsdl
b) http://prodsoa.server.com:9876/schemas/Addressing.xsd
c) prod_support_group@clientcompany.com


Note: Steps 1 through 3 are only one of the different ways to manage multiple environments. You could have alternative mechanisms to manage multi-server deployments.


Step 1: Define multiple copies of ant-orabpel.properties, one for each environment - lets say as ant-orabpel_dev.properties, ant-orabpel_test.properties and ant-orabpel_prod.properties. Specify env specific parameters in each of these files.
Step 2: Define the following properties in the ant-orabpel_test.properties.
a) service_host=testsoa.server.com
b) service_ port = 7780
c) support_group_email=test_support_group@clientcompany.com
Define the following properties in the ant-orabpel_prod.properties.
a) service_ host=prodsoa.server.com
b) service_ port = 9876
c) support_group_email=prod_support_group@clientcompany.com
Step 3: Open the build.xml. Change the following line within it.
             &lt;property file="${bpel.home}/utilities/ant-orabpel.properties"/>
             So that it looks like this.
             &lt;property file="${bpel.home}/utilities/ant-orabpel_${deploy_env}.properties"/>
This enables us to pass in a command line argument named deploy_env to the build script and have it import the appropriate ant-orabpel.properties.
For e.g., When you invoke the build for the test environment by typing in ant i??Ddeploy_env=test, the build.xml automatically imports the ant-orabpel_test.properties.


Step 4: Open up the compile target block. We will now define the customizations on the process WSDL and the bpel.xml.


&lt;target name="compile">
        &lt;bpelc input="${process.dir}/bpel/bpel.xml" out="${process.dir}/output"
               rev="${rev}" home="${bpel.home}">
        &lt;/bpelc>
    &lt;/target>


Before the bpelc node, add the customizeDocument task.


&lt;target name=i??compilei??>
   &lt;customizeDocument inFile=i??${process.dir}/bpel/CreatePurchaseOrderService.wsdli?? outFile=i??${process.dir}/bpel/CreatePurchaseOrderService.wsdli??>
&lt;/customizeDocument>
   . . . .
&lt;/target>
The above step indicates the intent to customize the CreatePurchaseOrderService.wsdl.
Next, we need to add the nested i??setTextContenti?? task that allows us to set the text of any attribute or element within the WSDL. Use the setTextContent task to specify the element or attribute to be updated, together with the value that it should be updated with.


&lt;target name=i??compilei??>
   &lt;customizeDocument inFile=i??${process.dir}/bpel/CreatePurchaseOrderService.wsdli?? outFile=i??${process.dir}/bpel/CreatePurchaseOrderService.wsdli??>
   &lt;setTextContent select=i??/wsdl:definitions/wsdl:import/@locationi?? textContent=i??http://${service_host}:${service_port}/services/GeneralPOHeader.wsdli??/>
&lt;/customizeDocument>
   . . . .
&lt;/target>


The i??selecti?? attribute on the customizeDocument indicates a qualified XPath expression that points to the node within the process WSDL that needs to be customized. In this example, it points to the location attribute of the WSDL import. The i??textContenti?? attribute will hold the text that will be set within the node. In this example, it points to the absolute URL of the imported WSDL. You can also specify the tokens in the URL i?? The build script will automatically subsitute them with the actual values when it is executed. For instance, if the build were executed with the i??Ddeploy_env=test or prod, the appropriate values of service_host and service_port will be substituted from the ant-orabpel_test/prod.properties.


Next, we shall customize the XSD import within the WSDL. For this, add one more setTextContent task within the customizeDocument task. The semantics of this is identical to the earlier step.


&lt;target name=i??compilei??>
   &lt;customizeDocument inFile=i??${process.dir}/bpel/CreatePurchaseOrderService.wsdli?? outFile=i??${process.dir}/bpel/CreatePurchaseOrderService.wsdli??>
   &lt;setTextContent select=i??/wsdl:definitions/wsdl:import/@locationi?? textContent=i??http://${service_host}:${service_port}/services/GeneralPOHeader.wsdli??/>
   &lt;setTextContent select=i??/wsdl:definitions/wsdl:types/xsd:schema/xsd:import/@schemaLocationi?? textContent=i??http://${service_host}:${service_port}/schemas/Addressing.xsdi??/>
&lt;/customizeDocument>


   . . . .
&lt;/target>


The definition of the customization for the WSDL and XSD is almost complete. The missing step is the namespace URI mappings for the prefixes used within the select expressions. In this case, there are two prefixes that need to be mapped to a namespace URI.
a) The i??xsdi?? namespace prefix
b)  The i??wsdli?? namespace prefix.
These prefixes are declared as properties within the same build file.
Declare two properties, one for each of the namespace URI, as below at the global level within the build.xml [i.e. as a child element of the &lt;project> element. The name of the properties should be  i??prefix.i?? Followed by the actual prefix. The value attribute contains the namespace URI for the prefix.


    &lt;property name="prefix.wsdl" value="http://schemas.xmlsoap.org/wsdl/"/>
    &lt;property name="prefix.xsd" value="http://www.w3.org/2001/XMLSchema"/>



Next, we specify the customization required for the bpel.xml.
Add another &lt;customizeDocument> task within the compile block. We need to add another one since we are customizing a different document.


&lt;project   i??..>
     . . . . .
     &lt;property name="prefix.wsdl" value="http://schemas.xmlsoap.org/wsdl/"/>
     &lt;property name="prefix.xsd" value="http://www.w3.org/2001/XMLSchema"/>


     &lt;target name=i??compilei??>
       &lt;customizeDocument inFile=i??${process.dir}/bpel/CreatePurchaseOrderService.wsdli?? outFile=i??${process.dir}/bpel/CreatePurchaseOrderService.wsdli??>
      &lt;setTextContent select=i??/wsdl:definitions/wsdl:import/@locationi?? textContent=i??http://${service_host}:${service_port}/services/GeneralPOHeader.wsdli??/>
     &lt;setTextContent select=i??/wsdl:definitions/wsdl:types/xsd:schema/xsd:import/@schemaLocationi?? textContent=i??http://${service_host}:${service_port}/schemas/Addressing.xsdi??/>
&lt;/customizeDocument>


   &lt;customizeDocument inFile=i??${process.dir}/bpel/bpel.xmli?? outFile=i??${process.dir}/bpel/bpel.xmli??>
     &lt;setTextContent select=i??/BPELSuitcase/BPELProcess/preferences/property[@name=i??supportEmail
i??]i?? textContent=i??${support_group_email}i??/>
&lt;/customizeDocument>
   . . . .
&lt;/target>


Note that the select expression used for this customization does not need any namespace prefixes. This is attributed to the fact that bpel.xml by itself is an unqualified document.


This completes the customization features provided by this task.


Note that the customizeDocument task can be used to customize any bpel process project artifact, although not illustrated in this document.

]]> Removing additional whitespaces in your Elements and Attributes tag:blogs.oracle.com,2007:/rammenon//86.2650 2007-11-15T06:30:27Z 2008-06-24T09:58:09Z In case your XML elements contain multiple whitespaces within the text, or leading and trailing the text, you could use normalize-space() function to remove the leading and trailing whitespaces, as well as to combine all adjacent intermediary whitespaces into one... Ramkumar Menon

In case your XML elements contain multiple whitespaces within the text, or leading and trailing the text, you could use normalize-space() function to remove the leading and trailing whitespaces, as well as to combine all adjacent intermediary whitespaces into one single whitespace.


For e.g


Input


&lt;input>   1sp 2sp  3sp   4sp     5sp     3sp   end&lt;/input>


XSLT


 &lt;ns1:result>
   &lt;xsl:value-of select="normalize-space(/input)"/>
&lt;/ns1:result>


Result


&lt;result>1sp 2sp 3sp 4sp 5sp 3sp end&lt;/result>

]]>