Fusion Development demo

Please view this demo for developing fusion applications declaratively using Jdeveloper 11g.

Read more...

Oracle Fusion Siebel Integration Demo

If you are interested to learn how to integrate to Siebel system using fusion middleware, you can view this demo.

Read more...

Calling BPEL from an ADF application

Susan Duncan has published a demo on how to call BPEL process from an ADF application.
Happy Learning !!!

Read more...

No BPEL Process Deployed Is Visible In BPEL Console On Container Restart

Symptoms
You have deployed one or more BPEL projects which runs successfully.
You restart the BPEL container and you do not see any previously deployed projects in BPEL Console.
The BPEL domain log has following error:

<2008-11-20 12:42:36,099>   
*****************************************************************************
Loading processes for BPEL domain "default" ...

08/11/20 12:42:36 java.lang.IncompatibleClassChangeError
08/11/20 12:42:36       at com.collaxa.cube.engine.deployment.DeploymentManager.loadAllProcesses(DeploymentManager.java:227)
08/11/20 12:42:36       at com.collaxa.cube.engine.CubeEngine.loadAllProcesses(CubeEngine.java:957)
08/11/20 12:42:36       at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:313)
08/11/20 12:42:36       at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:279)
08/11/20 12:42:36       at com.collaxa.cube.ejb.impl.ServerBean.loadProcesses(ServerBean.java:273)
08/11/20 12:42:36       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08/11/20 12:42:36       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
08/11/20 12:42:36       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
08/11/20 12:42:36       at java.lang.reflect.Method.invoke(Method.java:585)
08/11/20 12:42:36       at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
08/11/20 12:42:36       at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
08/11/20 12:42:36       at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
08/11/20 12:42:36       at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
08/11/20 12:42:36       at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
08/11/20 12:42:36       at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
08/11/20 12:42:36       at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
2008-11-20 12:42:36,102>    Failed to load processes for domain default

Changes
You apply any MLR patch to upgrade BPEL.

Cause
You have some classes in the classpath, whose class definition is not compatible with the currently executing method. This is likely if you have in the past applied any test patch provided by development under $ORACLE_HOME/bpel/system/classes directory. The class files placed in this directory overrides the same class in other location causing the incompatibility.

Solution
1.Stop the container running BPEL
2.Delete the classes under $ORACLE_HOME/bpel/system/classes
3.Start the BPEL container.

Read more...

BPEL Console isn't accesible if the BPEL domain name has mixed or upper case

Symptoms
When a BPEL domain is created using mixed or upper case in his name, the BPEL Console is inaccesible for the user.

Cause
The problem is caused because BPEL don't support the creation of domains using mixed or upper case in names. Since the domain names are used in the directory structure, and different Operating Systems handle case differently (Windows is case insensitive, while Unix and Linux are case sensitive), it is not possible to allow mixed or upper case names.

Some additional information about errors:

1.- Create two domains using capital letters, for example, 'DEV' and 'QA', then login to BPEL console,the following error occurs (Metalink Note 428317.1).

ERROR
OracleJSP: java.io.FileNotFoundException

2.- Created a new domain, with a domain name beginning with UPPERCASE letters.
When attempting to log into the BPEL Console the login failed and received the following error in the domain.log (Metalink Note 423058.1):

(Note the domain name searched is "dave" when the actual domain created was "DAVE")

<2007-04-10 13:52:58,453>    GOT CONNECTION 3 Autocommit = false
<2007-04-10 13:52:58,468>    CLOSE CONNECTION 2
<2007-04-10 13:53:14,890>    Error while invoking bean "finder": Cannot lookup BPEL domain.
The BPEL domain "dave" cannot be found; the domain may not have initialized properly.
Please verify that the BPEL domain loader has a valid set of initialization properties in the application properties file.

ORABPEL-02052

Cannot lookup BPEL domain.
The BPEL domain "dave" cannot be found; the domain may not have initialized properly.
Please verify that the BPEL domain loader has a valid set of initialization properties in the application properties file.

at com.collaxa.cube.engine.CubeEngineHolder.getStatus(CubeEngineHolder.java:41)
at com.collaxa.cube.engine.CubeEngineHolder.getEngine(CubeEngineHolder.java:52)

Solution
Create your domain using lower case.
It was determined that instead of trying to make a generic fix for all platforms, it would be much safer to pull patch 5851215, and require that all domains only be created in lower case.

Read more...

BPEL Process - Operation "Initiate" Does Not Appear In BPEL Console

Symptoms
When you upgrade or update MLR patchsets to SOA suite you might encounter this problem, where some of the already deployed BPEL processes may not show the "Initiate" operation in the Operation drop-down of the BPEL Console.

Cause
The cause for this issue could be due to the runtime WSDL files in the WSDL cache were corrupted during the upgrade.

Solution
Clear the WSDL cache.

Follow the steps below:
1. Stop the SOA server.
2. Navigate to \bpel\domains\<Domain>\tmp\
3. Delete all the .<Directories>. (There will be a dot in front of all these directories)
4. Start SOA Server.

You can also achieve the above from the BPEL console. Navigate to Administration tab --> Actions --> Press the "Clear WSDL Cache" button.

Read more...

BPEL Process Unable To Render HTML Or XML Form In Initiate Tab Of BPEL Console, When Using anySimpleType Element Type In Schema

Symptoms
You have a BPEL process that uses a schema with a element type anySimpleType. When you try to initiate the process from the BPEL console, the Initiate tab does not render the HTML or the XML input fields or form.

Solution
Apply Patch.8763870

Read more...