Tuesday, April 5, 2011

Base64 Code Snippets for OSB and BPEL

This post applies to SOA suite

I need to decode a base64 payload in my OSB proxy service. Here is a native solution that I came up with:

1. The java source:
//import org.apache.xerces.impl.dv.util.*;
import java.lang.reflect.Method;
import java.net.URL;
import java.net.URLClassLoader;

import java.util.*;
public class MyBase64
  public static String decode(String x)

 try {
 String path = "file:///"+System.getenv("ALSB_HOME") + "/../modules/com.bea.core.apache.xercesImpl_2.8.1.jar";
  URL[] urls = new URL[] { new URL(path) };
  ClassLoader loader = new URLClassLoader(urls);
  Class<?> cls = loader.loadClass("org.apache.xerces.impl.dv.util.Base64");
  Method theMethod = cls.getMethod("decode", String.class);

  return new String( (byte[])theMethod.invoke(null, x));
 catch(Exception e)
  return "decode failed";

  public static void main(String args[])

2. complie java source (you need to add C:\Oracle\Middleware\modules\com.bea.core.apache.xercesImpl_2.8.1.jar to your compiler classpath, your path maybe different)
3. jar it up
4. add jar to your osb project. (In your project, choose "Create Resource", select "JAR" under "Utility")
4. use in your java callout

Here is a BPEL snippet to encode base64

    <bpelx:exec name="base64EncodeTemp" version="1.5" language="java">
        String sTemp = (String)getVariableData("temp");   
        addAuditTrailEntry("Covert Temp to Byte Array  : \n" + sTemp);
        byte[] bTemp = new byte[sTemp.length() / 2]; 
        for (int i = 0; i < bTemp.length; i++) { 
          bTemp[i] = (byte) Integer.parseInt(sTemp.substring(i*2, (i*2)+2), 16); 
       sun.misc.BASE64Encoder encoder = new sun.misc.BASE64Encoder();   
       String encodedTemp = encoder.encodeBuffer(bTemp);   
       setVariableData("temp", encodedTemp);]]>

Monday, April 4, 2011

OSB complains JCA class cannot be found

Recently I experienced some problems with OSB complaining about JCA class cannot be found. My SOA suite version is
As I work on OSB JCA DB adapters, all of a sudden I see errors like the following:
Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.db.DBWriteInteractionSpec
Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.db.DBActivationSpec
This initially gives me the impression that someone touched the startup script that messed up the classpath. So I modified the startup script to hard code the jar files in the classpath. That didn’t really solve the problem.
After sifting through log files and comparing config.xml, I noticed that my OSB server is missing from the DB adapter deployment target list.

You can either edit your config.xml file to add it back in. Or go to weblogic console -> deployments  -> DbAdapter -> Targets and make sure “osb_server1” is checked.
I think there is a bug that can cause this to happen. I don’t have an exact way to reproduce it. As you work on OSB JCA adapter services, this error may creep up on you.