Welcome to my blog

· I have extensively worked on the following technologies/Implementation projects

· Oracle EBS R12, 11.5.10.2, 11.5.9

o Oracle Applications DBA (AD)

o Oracle Financials

o Order Management

· Oracle Retail Suite V12, V13

o Retail Merchandizing system RMS

o Invoice matching ReIM

o Retail Integration Bus RIB

o Retail price manager RPM

o Store Inventory Manager SIM

o Retail Demand Forecasting RDF

o Retail data warehousing RDW

o Oracle Internet Directory OID

· Oracle SOA Suite

o BPEL process manager

o Enterprise Service Bus

· Oracle Hyperion Suite

o Shared services OSS

o Workspace

o Planning

o Essbase

o Enterprise performance management EPM

o Financial reporting, Web analysis

· Enterprise Batch Scheduler Uc4 Appworx

· Oracle Business intelligence Suite

o Answers

o Interactive dashboards

o BI publisher

· I am responsible for several Implementations that use the following Oracle middleware products

· Oracle Weblogic Fusion Middleware web application

· Oracle Weblogic Forms and Reports Server

· Oracle Weblogic SOA Suite

o BPEL process manager

o Oracle Service Bus

o Oracle B2B server

· Oracle Business intelligence Suite

o BI publisher

o Oracle Discoverer 10g

· Enterprise Batch Scheduler Active Batch

· Oracle Internet Directory OID

· Oracle Connection Manager

· Several Custom applications deployed in Oracle 10g Application servers


My interest is to make this an arena to share my experiences.

Friday, November 13, 2015

oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener Class not Found

Resolving the Exception

"oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener Class not Found"  

  On re-start of a new install of OID11g on weblogic, the following error was seen:

'oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener' Class not Found 

This strongly indicates an issue with the exception in Weblogic environment. Also the deployments show remain in 'Prepared' state.

The error can be fixed with setting the nodemanager property to use the weblogic startup script by changing the parameter "StartScriptEnabled=true"

This will include correct the environment during startup.

The deployments will also be activated effectively on startup.


Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)