12.2 oacore managed server starts in ADMIN mode - java.lang.ClassNotFoundException

Issue:

EBS 12.2 Application services are bounced as part of regular maintenance. During startup oacore_server1 Managed server started in ADMIN mode rather than RUNNING mode.

Below are the errors found in oacore_server1.log file.

Caused By: java.lang.ClassNotFoundException: oracle.apps.bne.integrator.document.ooxml.BneCreateDocumentService

Solution:

web.xml has some how updated with incorrect values for servlet class.

At Line 341 of file

$FMW_HOME/Oracle_EBS-app1/applications/oacore/html/WEB-INF/web.xml Below is the found value:

<servlet-class>oracle.apps.bne.integrator.document.ooxml.BneCreateDocumentService</servlet-class>

Update the value with below change:

<servlet-class>oracle.apps.fnd.txk.util.TXKSubstituteProductServlet</servlet-class>

Save changes and bounce oacore_server1 managed server.

EBS 12.2 Unable to start up the managed server oacore_server1 - after clone

Unable to Start OACORE Services during clone on RUN Filesystem

Recently we did a clone and as part of execution of adcfgclone.pl in run Filesystem, I responded to adcfgclone.pl to start Application Filesystems. But I observed the start of Managed servers failed and below is the output from one of oacore services.

Successfully Connected to Node Manager.

The Node Manager is already up.
Starting server oacore_server1 ...
Error Starting server oacore_server1: weblogic.nodemanager.NMException: Exception while starting server 'oacore_server1'

ERROR: Unable to start up the managed server oacore_server1

05/20/15-00:20:43 :: admanagedsrvctl.sh: exiting with status 1

This information is not sufficient to identify the cause of the issue and I had go through the oacore log files under $EBS_DOMAIN_HOME/servers/oacore_server1/logs

9ee0eb174c5acfd:2fe0c70b:14d72092155:-8000-0000000000000eda> <1432203790547> <BEA-100028> <Could not deserialize session data.
oracle.apps.fnd.common.PoolException: Exception creating new Poolable object.
        at oracle.apps.fnd.common.Pool.createObject(Pool.java:1289)
..
 <<WLS Kernel>> <> <> <1432099154476> <BEA-149205> <Failed to initialize the application 'EBSDataSource' due to error weblogic.application.ModuleException: .
..
java.lang.NoClassDefFoundError: Could not initialize class oracle.apps.fnd.common.WebAppsContext
        at oracle.apps.fnd.security.AppsServletFilter.init(AppsServletFilter.java:148)
..
<Could not load user defined filter in web.xml: oracle.apps.jtf.cabo.interceptor.JTFWrapperFilter.
java.lang.NullPointerException
..

..
..

Caused By: weblogic.common.resourcepool.ResourceSystemException:
 Could not connect to 'oracle.jdbc.OracleDriver'.

 The returned message is: ORA-01017: invalid username/password; logon denied

 It is likely that the login or password is not valid.
 It is also possible that something else is invalid in the configuration or that the database is not available.




Then this gave clear information which says that the apps password provided during adcfgclone.pl is noot being accepted even though the password provided is correct.

Later it is observed that Apps Password is changed as part of execution of adcfgclone.pl on DBTier and theis new password change is somehow not reflected when Managed servers are created during execution of rapidclone on Apps Tier.

Now this is fixed manually by performing below steps.

As ADMIN Server is up and runnning,

Login to EBS Weblogic console -> Perform Lock & Edit -> Under Domain Structure -> Services -> Datasources -> Select "EBSDataSource"

Navigate to Configuration -> Connection pool  -> Update with new password in password fields.

Then Save changes.

Perform the above steps of other Datasource OAADatasource.

Now Activate the changes in Control Center.

This should resolve the issue. Bring up the managed servers from Console or using command line.

SSL for Weblogic Server

Hi,

Below are the high level steps of configuring Weblogic admin server and managed servers with SSL.

1) Create a keystore
2) Generate Certificate Request file using keytool
3) Export keystore file and upload to CA authority
4) Upload the Digital certificates obtained by Trusted CA to Key store
5) Login Weblogic console and go to configuration page of admin server
6) Enable SSL port under General, Modify Keystore details with Cutsom keystores and and keystore password
7) Update the same keystore under SSL Tab.
8) Save the changes and activate.
9) Shutdown admin server and restart it

After restart you should be able to launch Console with https (SSL Enabled).

The detailed primer of this activity will be published soon.. Wait for the updates