Tech Mastery: Deep Dives into AEM, Cloud Technologies, AI Innovations, and Advanced Marketing Strate

Welcome to Tech Mastery, your expert source for insights into technology and digital strategy. Explore topics like Adobe Experience Manager, AWS, Azure, generative AI, and advanced marketing strategies. Delve into MACH architecture, Jamstack, modern software practices, DevOps, and SEO. Our blog is ideal for tech professionals and enthusiasts eager to stay ahead in digital innovations, from Content Management to Digital Asset Management and beyond.

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

weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:184)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:112)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:175)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:281)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.lang.ClassNotFoundException: oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:249)
at

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.

Steps to resolve the issue

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

In Oracle SOA Suite 11g and Oracle SOA Suite 12c,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.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");

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 (rs.next()) {

Blob blob=rs.getBlob("DOC");

byte[] sdata = blob.getBytes(1, (int) blob.length());;

payload = new String(sdata);

}

} catch (Exception e) {

e.printStackTrace();

} finally {

try {

if (rs != null)

rs.close();

if (stmt != null)

stmt.close();

if (connection != null)

connection.close();

} catch (Exception e) {

}

return payload;

}

Wednesday, March 26, 2014

Recovering the composites to JDeveloper from MDS - Oracle SOA Suite

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.

Steps to recover the composite from MDS

Select the appropriate options as shown and click on Export

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.

java.io.IOException
at oracle.ide.marshal.xml.StructureIO.loadUsingSAX(StructureIO.java:251)
at oracle.ide.marshal.xml.StructureIO.loadImpl(StructureIO.java:167)
at oracle.ide.marshal.xml.StructureIO.loadImpl(StructureIO.java:156)
at oracle.ide.marshal.xml.HashStructureIO.load(HashStructureIO.java:46)
at oracle.ideimpl.extension.RoleManagerImpl.getRolePreferences(RoleManagerImpl.java:80)
at oracle.ideimpl.extension.ExtensionManagerImpl.runRoleSelectionDialog(ExtensionManagerImpl.java:1112)
at oracle.ideimpl.extension.ExtensionManagerImpl.initialize(ExtensionManagerImpl.java:943)
at javax.ide.Service.getService(Service.java:68)
at javax.ide.extension.ExtensionRegistry.getExtensionRegistry(ExtensionRegistry.java:400)
at oracle.ide.ExtensionRegistry.getExtensionRegistry(ExtensionRegistry.java:191)
at oracle.ide.IdeCore.startupImpl(IdeCore.java:1384)
at oracle.ide.Ide.startup(Ide.java:703)

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.

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.

weblogic.management.ManagementException: [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: weblogic.management.ManagementException: [Deployer:149014]Target 'wlsbJMSServer' is not defined.

[02:45:24 PM] See server logs or server console for more details.

[02:45:24 PM] weblogic.management.ManagementException: [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(www.abc.com) but a single Wildcard SSL Certificate covers any and all of the sub-domains of the main domain(*.abc.com)

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 "weblogic.security.utils.SSLWLSWildcardHostnameVerifier"

Make sure the option Use JSSE SSL is selected.

Restart the weblogic server.

Tuesday, February 25, 2014

SOA-INFRA app is not starting up - Oracle SOA Suite 11g

SOA-INFRA app is not starting up - Oracle SOA Suite 11g:

When we restarted the soa server, the soa server came up properly except the SOA-INFRA app.
The status of the SOA-INFRA app in weblogic console is failed and also the SOA node in the em console is not displayed.

We could not able to find any particular error from log files including diagnostic log except schema mismatch error with some of the composites.It seems due to some reason the status of the soa-infra application is failed and the server is restarted without fixing the actual issue then even after fixing the issue and restarting the server the soa-infra app is not Active.

We have tried deleting the following folders from $DOMAIN_HOME/servers/AdminServer
data
temp
cache

Unfortunately even after deleting the above folders the SOA-INFRA app did not come up.

Tried starting the SOA-INFRA app manually from weblogic console, this time the SOA-INFRA app came up and we could able to see the SOA in em console.

Tuesday, January 28, 2014

ODL handler configuration through WLST script - Oracle SOA Suite

ODL handler configuration through WLST script - Oracle SOA Suite:

Oracle Fusion Middleware components write diagnostic log files in the Oracle Diagnostic Logging (ODL) format. Log file naming and the format of the contents of log files conforms to an Oracle standard. By default, the diagnostic messages are written in text format.

ODL provides the following benefits:

The capability to limit the total amount of diagnostic information saved. You can set the level of information saved and you can specify the maximum size of the log file and the log file directory.

When you reach the specified size, older segment files are removed and newer segment files are saved in chronological fashion.

Components can remain active, and do not need to be shutdown, when older diagnostic logging files are deleted.

The ODL configuration can be changed from EM console or WLST script.

Below is the WLST script help us to change the ODL handler setting.

Configureodlloghandlers.py

folderPath="/oracle/product/soa/11g/fmw/fmwlogs/SOACoreDomain"

domainAdminUserName = "weblogic"

domainAdminPassword = "welcome1"

connect(domainAdminUserName, domainAdminPassword, "t3://localhost:7001")

servers = adminHome.getMBeansByType('Server')

for s in servers:

edit()

startEdit()

serverName1 = s.getName()

path = '/Servers/' + serverName1

cd(path)

lh = listLogHandlers()

for l in lh:

lname = l.get('name')

odlfile = folderPath + '/logs/' + serverName1 + '/' + serverName1 + '-' + lname + '-diagnostic.log'

print 'Diagnostic path===>',odlfile

configureLogHandler(target=serverName1,name=lname, path=odlfile)

save()

activate()

The other details like maxFileSize,rotationFrequency and retentionPeriod etc can also be changed through configureLogHandler method.

Executing the script:

$MIDDLEWARE_HOME/Oracle_SOA/common/bin/wlst.sh Configureodlloghandlers.py

Tuesday, January 14, 2014

Polling the Message from WebSphere MQ using MQ Transport in OSB

OSB MQ transport help us to post/receive message from the WebSphere MQ. The MQ transport can be configured to poll the queue for the new messages.

This blog explains how to configure the OSB Proxy Service to poll the Queue for new messages.

Steps to configure the OSB Proxy Service to poll the Queue for new messages

Create a OSB Project and Create a Resource of type MQ Connection.

Provide the MQ Connection details like host name,port number,Queue Manager Name, Channel Name and also provide Connection Pool Size, Connection Timeout and Connection Max Wait. Provide the Static Service Account if User Name/Password is required to connect to MQ and leave the Connection type as default value(tcp mode). Save the connection details.

Remote Java Client to Post the Message to IBM MQ

The below java code will help us to post the message to remote IBM MQ.

package mqclient;
import com.ibm.mq.jms.*;
import javax.jms.*;

public class MQJavaClient {

public static void main(String[] args)
{
try {
MQQueueConnectionFactory cf = new MQQueueConnectionFactory();
cf.setHostName("10.130.134.178");
cf.setPort(2022);
cf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP);
cf.setQueueManager("EAI1");
cf.setChannel("T_CRM_FUSION_CLIENT");

MQQueueConnection connection = (MQQueueConnection) cf.createQueueConnection();
MQQueueSession session = (MQQueueSession) connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
MQQueue queue = (MQQueue) session.createQueue("queue:///DUMMY_Q?targetClient=1");
MQQueueSender sender = (MQQueueSender) session.createSender(queue);

String message="<ns1:EmployeeRequest xmlns:ns1=\"http://xmlns.oracle.com/JEJBSample/EmployeeDetailService/EmployeeDetailService\">\n" +
"<ns1:empNo>987654</ns1:empNo>\n" +
"</ns1:EmployeeRequest>";

TextMessage textMessage = (TextMessage) session.createTextMessage(message);
connection.start();
sender.send(textMessage);

sender.close();
session.close();
connection.close();

}catch (Exception e) {
e.printStackTrace();

}
}
}

Jar Files Required:

com.ibm.mq.jar

com.ibm.mqjms.jar

javax.jms.jar

com.ibm.dhbcore.jar

javax.resource.jar

javax.transaction.jar

Friday, January 10, 2014

Initiating an OSB Service with Email

Email transport will help us to send/receive emails in OSB. Some cases we may required to initiate the external service based on the email in the user inbox.

The Proxy service polls the Mail Inbox for the new messages and invokes the Business service whenever there is a new message in the Inbox.The polling interval can be specified in the Proxy Service configuration.Here i will explain about invoking the service with the XML message received from the email body.

Invoking the service with the XML message received from the email body

Create a XSD message structure that will be used by Proxy Service to receive the message

<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified"
elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/JEJBSample/EmployeeDetailService/EmployeeDetailService"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="EmployeeRequest">
<complexType>
<sequence>
<element name="empNo" type="string"/>
</sequence>
</complexType>
</element>
</schema>

Create a OSB project and create a Business service that needs to be invoked based on the Email content - Here i am invoking a sample BPEL service with the same XSD structure as input.

Create a Service Account with Static username/password of email user.

Exposing a OSB Proxy Service as EJB through JEJB transport

The JEJB transport lets you pass Plain Old Java Objects (POJOs) through Oracle Service Bus.To a J2EE client, a JEJB proxy service looks like a stateless session bean. A JEJB proxy service, on receiving the method arguments, passes their XML representation in the pipeline $body variable. POJO arguments are represented as the XML fragment. This XML fragment contains the location of the actual POJO stored in the object repository within the pipeline.

For deployment, Oracle Service Bus automatically packages JEJB proxy services as enterprise archives (EARs) and deploys to weblogic server(OSB Server).

JEJB transport uses the Java Interface to expose as EJB.

Here i will explain exposing the proxy service as EJB and invoking the same through java client by passing/receiving the java objects and invoking the business service by passing/receiving the XML(Java utility methods will be used to convert Java to XML and XML to Java).The BPEL service invoked will receive the empno and and return back the employee details.

Steps to expose the proxy service as EJB

Create a Java interface that will receive/return the Employee object .

package jejbsample;
public interface EmployeeDetails {

Employee getEmployeeDetails(Employee emp);
}

package jejbsample;

import java.io.Serializable;

public class Employee implements Serializable{

private String empName;

private String empNo;

private String empDept;

private String empLoc;

public Employee() {

super();

}

public void setEmpName(String empName) {

this.empName = empName;

}

public String getEmpName() {

return empName;

}

public void setEmpNo(String empNo) {

this.empNo = empNo;

}

public String getEmpNo() {

return empNo;

}

public void setEmpDept(String empDept) {

this.empDept = empDept;

}

public String getEmpDept() {

return empDept;

}

public void setEmpLoc(String empLoc) {

this.empLoc = empLoc;

}

public String getEmpLoc() {

return empLoc;

}

Create a Utility class that will convert the Java to XML and XML to Java.

package javaxmlconverter;

import java.io.InputStream;

import javax.xml.parsers.*;

import jejbsample.Employee;

import org.apache.xmlbeans.*;

import org.w3c.dom.*;

public class JavaXMLConverter {

public JavaXMLConverter() {

super();

}

public static String getEmpRequestXML(Employee emp) {

return emp.getEmpNo();

}

public static Employee getEmpResponseJava(XmlObject xml) throws Exception{

Employee emp = new Employee();

DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();

InputStream inputStream = xml.newInputStream();

DocumentBuilder db = dbf.newDocumentBuilder();

Document doc = db.parse(inputStream);

String empName=null ;

String empNo=null;

String empDept=null;

String empLoc=null;

NodeList nList = doc.getElementsByTagName("EmployeeResponse");

for (int temp = 0; temp < nList.getLength(); temp++) {

Node nNode = nList.item(temp);

if (nNode.getNodeType() == Node.ELEMENT_NODE) {

Element eElement = (Element)nNode;

empName =eElement.getElementsByTagName("empName").item(0).getTextContent();

empNo =eElement.getElementsByTagName("empNo").item(0).getTextContent();

empDept =eElement.getElementsByTagName("empDept").item(0).getTextContent();

empLoc =eElement.getElementsByTagName("empLoc").item(0).getTextContent();

}

emp.setEmpDept(empDept);

emp.setEmpName(empName);

emp.setEmpLoc(empLoc);

emp.setEmpNo(empNo);

return emp;

}

Custom Message Throttling and Interface Management – Oracle BPEL

This post explain the details on Custom Message Throttling and Interface Management – Oracle BPEL/Oracle SOA Suite 11g

Custom Message Throttling and Interface Management.pdf

Thursday, December 12, 2013

Approaches to integrate Oracle SOA Suite with SalesForce.com

This post explain the different Approaches to integrate Oracle SOA Suite with SalesForce.com.

Integrate Oracle SOA With SalesForce.pdf

Tuesday, December 10, 2013

Modifying the Request Headers of a OSB Business Service

Sometimes we may required to change the request header values eg. Content-Type and Accept etc for OSB Business Service request dynamically, this post will explain the steps to modify the header values for a Business Service request.

Steps to modify the header values for a Business Service request

Edit the Route to Business Service and Click on add Request Action

Dynamic endpoint configuration for OSB Business services

Sometimes we may required to change the OSB Business service endpoint dynamically.

Steps to change the Business Service endpoints dynamically

The following are the steps to change the Business Service endpoints dynamically.

Login to sbconsole and create the session.

Open the Proxy Service Message Flow.

Click on the RouteTo_BusinessService and click on Edit Route

Test the REST services using Chrome

This post will explain you how to test the REST services using chrome.

Steps to test the REST services using Chrome

Install the REST Console Extension to Chrome.

Open REST Console

Here, i am invoking the REST enabled salesforce login service with OAuth.

Provide the Request URI, Content-Type and Language.
Select the Content-Type of Content Headers as application/x-www-form-urlencoded and provide the request payload.We can also add Authorization, Attachment and Headers to the request.

Creating JCA Adapters with Abstract WSDL - Oracle OSB

Oracle OSB provides the option to create JCA adapters to connect to different resources through Proxy Services and Business Services.

The JCA adapter needs to be created through JDevelper, JDeveloper creats a Abstract WSDL and a JCA adapter file.

When creating Busines Service through eclipse, eclipse provides the option to generating the service by right clicking the JCA file.

But through OSB console, we will not be able to generate the Business Service with the Abstract WSDL(WSDL Web Service) because it will not have any binding or service defined.

If we are adding the binding/service to the abstract wsdl and creating the Business servive the following exception will be thrown

Weblogic Managed server status struck in STARTING

We faced the issue while starting the weblogic managed server, the status of the server struck in STARTING.

W could not able to find a valid error messages in the log files

Managed Server Log File:

<30-Oct-2013 11:13:29 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>

No logs are getting printed after this.

Node Manager Log File:

<30-Oct-2013 11:09:44> <INFO> <SOACoreDomain> <MS1> <Server failed during startup so will not be restarted>

<30-Oct-2013 11:09:44> <WARNING> <Exception while starting server 'MS1'>

java.io.IOException: Server failed to start up. See server output log for more details.

at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)

at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)

at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)

at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)

at weblogic.nodemanager.server.Handler.run(Handler.java:71)

at java.lang.Thread.run(Thread.java:662)

The root cause of this issue is somehow the ldap directory of the server got corrupted.

To resolve this issue:

Kill the managed server
Remove the ldap folder from the following location <<DOMAIN_HOME>>/servers/<<Managed Server>>, this file will be auto generated while restarting the server.
Restart the server

Pages