Saturday, November 23, 2013

WebCenter Content - Admin Applets Error

Applicable to 11g PS5:

Recently when I tried to access WebCenter Content Server Admin Applets, I got following error.

Unable to start the application ConfigMan. Failed to initialize. Runtime error: access denied
("java.util.PropertyPermission" "user.timezone" "write")

Admin applets are not opening due to browser java plugin update to version 1.7.0_45.

Download and Install latest MLR patch for your Oracle WebCenter Content version from Oracle Support. Refer to Oracle Support Document#1592799.1 for more details.

If you are facing the issue even after applying the patch, clear the cache on the browser and try again.

Thursday, November 21, 2013

Weblogic Startup Error : command not found

If you get following error message while starting Weblogic Admin server (or) Manager servers using (or), create a file under security folder of each server.

<Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:weblogic
-bash: weblogic: command not found

1. Go to <DOMAIN_HOME>/servers/<ServerName>/security directory(If security folder is not available, create a folder)
2. create a file named
Unix: vi

3 Add username & password to the file and save it.

4. Try executing scripts 
nohup ./ &
nohup ./ ManagedServer1 &

5. Once server started, the file content will be encrypted.

WC Spaces Startup Error: Cannot open Web producer connection

Applicable to 11g PS5:

If you are facing following error message in log files during WebCenter Spaces managed server start up, check whether WebCenter Portlet managed server is already up and running.

<Error> <oracle.portlet.client> <WCS-40144> <Import of producer /oracle/adf/portlet/export/oracle/adf/portlet/wc-WebClipping_51f3fd31-8a45-406c-ba3d-81757d93f702 failed. The failure has been stored for possible retry.
oracle.portlet.client.container.PortletConnectionException: Cannot open Web producer connection.
        at oracle.portlet.client.techimpl.web.WebClientImpl.registerProducer(

To avoid this error, make sure that you have started Collaboration, Portlet, Utilities managed servers before starting Spaces managed server.

Monday, November 18, 2013

ORA-01005: null password given

Applicable to 11g PS5(

When we try to access ADF application (developed using database objects), it throws following error even though the data source connection created in weblogic server has no issues.

>>oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection

>>java.sql.SQLException: ORA-01005: null password given; logon denied

To resolve this error, add to EXTRA_JAVA_PROPERTIES entry in the file located in <MW_HOME>/user_projects/domains/<domain>/bin and restart the server.

ADF Managed Server Issue - java.lang.ClassNotFoundException

Applicable to 11g PS5(

After installing ADF runtime libraries on top of  Weblogic 10.3.6 base installation, extend the Weblogic domain to contain Admin Server and Managed Server (to deploy ADF applications).

Login to EM console --> Go to Weblogic Domain --> <Domain> --> Click on ADF Managed Server

To complete the ADF installation on Managed server, click on Apply JRF(Java Required Files) Template button.

The server must be restarted to for this operation to complete.

Create a simple ADF application and try to deploy it to ADF managed server. The managed server will throw following error.

<WebLogicServer> <BEA-000286> <Failed to invoke startup class "JRF Startup Class", java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup

<Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1384433391426' for task '0'. Error is: ' '
Caused By: java.lang.ClassNotFoundException: oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener

Given class not found exceptions occurs when ADF libraries classpath did not set properly.

To avoid this error, file needs to be updated as mentioned below.

1. Stop ADF managed server and node manager
2. Open file located under <WLS_HOME>\wlserver_10.3\common\nodemanager directory

3. Set StartScriptEnabled to 'true'. This property will enable to start ADF managed server with start up parameters configured in start up scripts.
4. Restart the node manager and start the ADF managed server from Console.