Thursday, March 27, 2014

java.lang.ClassNotFoundException: oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener

While deploying Oracle ADF application sometimes we may receive the following exception
at weblogic.application.internal.flow.BaseLifecycleFlow$
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(
at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(
at weblogic.application.internal.BaseDeployment$
at weblogic.application.utils.StateMachineDriver.nextState(
at weblogic.application.internal.BaseDeployment.prepare(
at weblogic.application.internal.EarDeployment.prepare(
at weblogic.application.internal.DeploymentStateChecker.prepare(
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(
Caused By: java.lang.ClassNotFoundException: oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(
at weblogic.utils.classloaders.GenericClassLoader.findClass(
at java.lang.ClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(
at weblogic.utils.classloaders.GenericClassLoader.loadClass(
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(

The issue is due to  missing ADF web Run-time libraries in the war file.This can be resolved by adding the ADF web Runtime libraries into the war file.

If you are deploying through JDeveloper then follow the below steps.

Add the ADF Web Runtime to the project libraries.

Include the ADF Web Runtime library as part of the war. 
    Project Properties-->Edit the deployment profile.
    Select the ADF Web Runtime library as part of WEB-INF/lib contributors.

Getting the Audit Detail of a BPEL instance in JAVA - Oracle SOA Suite 11g

In Oracle SOA Suite 11g,the audit trail of the BPEL is stored in the table AUDIT_TRAIL.If the size of the payload crossed the threshold size configured in the EM console then the details are stored in the AUDIT_DETAILS table.

The payload in the AUDIT_DETAILS table is in compressed binary form, you can use the below approach to get the actual payload.

import java.sql.*;
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;
public class GetPayload {
    public static Connection getConnection() throws Exception {
        Context ctx = null;
        Hashtable ht = new Hashtable();
        ht.put(Context.PROVIDER_URL, "t3://:8000");
        ctx = new InitialContext(ht);
        javax.sql.DataSource ds =(javax.sql.DataSource)ctx.lookup("jdbc/SOADataSource");
        return ds.getConnection();

    public static String getPayload() {

        Statement stmt = null;
        Connection connection = null;
        ResultSet rs = null;
        String query="select  UTL_COMPRESS.LZ_UNCOMPRESS(b.bin) DOC from audit_details b where cikey='5148077' and rownum<2";
        String payload = "";
        try {
            connection = getConnection();
            stmt = connection.createStatement();
            rs = stmt.executeQuery(query);
            while ( {                    
                Blob blob=rs.getBlob("DOC");
                byte[] sdata = blob.getBytes(1, (int) blob.length());;
                payload = new String(sdata);             
        } catch (Exception e) {
        } finally {
            try {
                if (rs != null)
                if (stmt != null)
                if (connection != null)
            } catch (Exception e) {

        return payload;


Wednesday, March 26, 2014

Recovering the composites to JDeveloper from MDS - Oracle SOA Suite 11g

Sometimes there is a possibility the latest code changes of the deployed composite in JDeveloper might have lost in other hand some cases we will not be having the implementation code for the deployed composites.

These scenarios the Oracle SOA Suite composite artifacts can be exported from MDS through em console and the same can be converted to design time artifact in JDeveloper.

This post will explain the steps to recover the composite to JDeveloper from MDS.

Login to Em console, right click on the particular composite and click on Export

Select the appropriate options as shown and click on Export

Click on Save File and save the jar file to local system.

In the JDeveloper, Go to File -> import -> select SOA Archive into SOA Project.

Enter the Application Name and Project Name accordingly.

Browse and select the exported composite artifact.

The composite will be created in JDeveloper.

Tuesday, March 18, 2014

Not able to save the projects into the JWS file(Application) in JDeveloper

I was facing a issue while saving the project to the application JWS file and getting "Unable to save GettingPayload.jws".

Receiving the following exception in the JDeveloper console.
at oracle.ide.marshal.xml.StructureIO.loadUsingSAX(
at oracle.ide.marshal.xml.StructureIO.loadImpl(
at oracle.ide.marshal.xml.StructureIO.loadImpl(
at oracle.ide.marshal.xml.HashStructureIO.load(
at oracle.ideimpl.extension.RoleManagerImpl.getRolePreferences(
at oracle.ideimpl.extension.ExtensionManagerImpl.runRoleSelectionDialog(
at oracle.ideimpl.extension.ExtensionManagerImpl.initialize(
at javax.ide.Service.getService(
at javax.ide.extension.ExtensionRegistry.getExtensionRegistry(
at oracle.ide.ExtensionRegistry.getExtensionRegistry(
at oracle.ide.IdeCore.startupImpl(
at oracle.ide.Ide.startup(

While restating the JDeveloper,  i could not able to see the projects listed under the corresponding applications, i have to manually add them to the application.

After analyzing for a while found out that the issue might be due to the corrected preference files kept in the following location <<USER_HOME>>\AppData\Roaming\JDeveloper\<<system folder>>

To resolve the issue delete the <<system folder >> from the above location and restart the JDeveloper.
While restarting the JDeveloper will prompt you to importing the preferences, select No there(unfortunately you will be loosing all the resource connections created)

Load all the applications and projects manually. Now you will be able to save the projects to the application - JWS file.

Not able to connect to Remote Oracle SOA Suite Server through JDeveloper – Oracle SOA Suite

Sometimes we could have faced the issue to establish the connection to remote Oracle SOA Suite Server through JDeveloper; this might be due to different reasons. Below are some of the basic steps to resolve the connection issue.

Verify whether the Weblogic Server’s user name, password, IP Address, Port and the domain name are entered in the connection wizard properly.

Make sure the option “Always use SSL” in the connection wizard has not been set.

Make sure the option “Use HTTP Proxy Server” in the JDeveloper has not been set. Disable the proxy settings: Tools -> Preferences -> Web Browser and Proxy -> Uncheck 'Use HTTP Proxy Server' option.

Make sure the connectivity via the particular port is available to the remote server by using telnet.

(Connection Success)

Restart JDeveloper and Test the connection again.

If the JDeveloper is installed by admin user with admin privileges, then we do not have privilege on some folders. We have to run JDeveloper as administrator (Right Click -> Run as Admin) to connect to server.

Wednesday, March 12, 2014 [Deployer:149014]Target 'wlsbJMSServer' is not defined.

Sometimes we may receive the following exception when trying to deploy a web application from JDeveloper to weblogic server.

[02:44:09 PM] ----  Deployment started.  ----
[02:44:09 PM] Target platform is  (Weblogic 10.3).
[02:44:12 PM] Retrieving existing application information
[02:44:12 PM] Running dependency analysis...
[02:44:12 PM] Building...
[02:44:17 PM] ****  One or more compilation errors prevented deployment from continuing.
[02:44:17 PM] ****  Please correct all compilation errors before deploying.
[02:44:17 PM] ####  Deployment incomplete.  ####
[02:44:17 PM] ****  One or more compilation errors prevented deployment from continuing. (oracle.adfdt.common.deploy.impl.AdfLibraryBuildDeployer)
[02:45:08 PM] ----  Deployment started.  ----
[02:45:08 PM] Target platform is  (Weblogic 10.3).
[02:45:09 PM] Retrieving existing application information
[02:45:09 PM] Running dependency analysis...
[02:45:09 PM] Building...
[02:45:10 PM] Deploying profile...
[02:45:11 PM] Wrote Web Application Module to C:\JDeveloper\mywork\GettingPayload\GetPayloadWeb\deploy\GetPayloadWeb.war
[02:45:11 PM] Deploying Application...
[02:45:24 PM] Weblogic Server Exception: [Deployer:149014]Target 'wlsbJMSServer' is not defined.
[02:45:24 PM]   See server logs or server console for more details.
[02:45:24 PM] [Deployer:149014]Target 'wlsbJMSServer' is not defined.
[02:45:24 PM] ####  Deployment incomplete.  ####
[02:45:24 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)

The issue is due to wlsbJMSServer target is not defined in weblogic server.

We can avoid this error and continue with the deployment by selecting the option as Deploy to selected instances in the domain and selecting the particular server or cluster instead of selecting the option as Deploy to all instances in the domain from the JDeveloper deployment wizard.

This is a temporary solution to continue with the deployment but we have to correct the Target issue.

Wednesday, March 5, 2014

Wildcard SSL HostnameVerifier in Weblogic Server

Before WLS release 10.3.5, weblogic  servers's hostname verification code did not supports the wildcard certificate by default we have to create a custom hostname verification code to handle this scenario but from WLS release 10.3.5, weblogic servers  hostname verification code  by default supports the wildcard certificates.

Wildcard SSL Certificates work the same way as a regular SSL Certificate, allowing you to secure the connection between the client and server( but a single Wildcard SSL Certificate covers any and all of the sub-domains of the main domain(*

Configuring Wildcard SSL HostnameVerifier:

  • Launch WLS console
  • Click on Environment -> Servers and click on the server
  • Then go to SSL tab
  • Lock & Edit
  • Scroll down and expand advanced section
  • Change Hostname verification entry to Custom Hostname Verifier
  • Enter Below in Custom Hostname verifier ""

  • Make sure the option Use JSSE SSL is selected.

  • Restart the weblogic server.

Contact Form


Email *

Message *