Thursday, April 28, 2011

weblogic installation fail

Error message: A fatal error has occurred. This application will terminate.

User had downloaded a generic versoin of weblogic (64bit) which came as *.zip and had unzipped the file in linux to find a installer.jar file which she ran and received the error.

The generic file must be run the way it is ignoring the *.zip extension.
for 64 bit jvm ex: java -d64 -jar *
for 32 bit jvm ex: java -jar *
Provide full permissions to the file (chmod -r 777 *.zip)

Linux flavour template
$ java -d64<your temp dir> -jar wls1033_generic.jar -log=/tmp/wls.log

Windows template
d:\java -d64 -jar wls1034_generic.jar<your temp dir>

If you are unable to set the java try below:
/home/misc/jdk1.6.0_25/bin/java -jar wls1034_generic.jar -mode=console

Friday, April 22, 2011

weblogic nodemanager password change methods

Edit WLS config.xml and edit thelines:

Go to directory: domain_directory/config/nodemanager
Take a backupof file:
Find an entry hashed=uFiKcLvYU3x9r11u8tjZlRvwBr4\= and remove it
add credentials in simple text:

Log in to Admin Console and go to: DomainName -> Security tab-> General tab -> Advanced Options. Then change the property Credentials with the new password.

Also, in order to verify your changes you can connect to your Node Manager using the new credentials:
1 $ cd */oracle_common/common/bin
2 $
3 wls:/offline> nmConnect(domainName='robin_domain', username='User123', password='password123')
4 Connecting to Node Manager ...
5 Successfully Connected to Node Manager.
6 wls:/nm/test_domain> nmDisconnect()
7 Successfully disconnected from Node Manager.
8 wls:/offline> exit()

AuthenticationEnabled to “false” in the file to ignore what we are passing as part of user and password while connecting to the node manager. 

managed server not starting via nodemanager: ensure that the admin's ldap is copied over managed server's ldap. 

Thursday, April 21, 2011

11g OMS & Repository in unknow status after WLS silent install

Error message:
Caused by: java.lang.NoClassDefFoundError:
at oracle.sysman.util.jdk.URLUtil.getURL(
at oracle.sysman.emSDK.sec.auth.EMLoginServlet.authenticateUser(
at oracle.sysman.emSDK.sec.auth.EMLoginServlet.doPost(

Above error messages were thrown after grid control installation was done over WLS silent installation,

1. Stop the OMS.
2. Copy the $OMS_HOME/oui/jlib/http_client.jar to the */user_projects/domains/GCDomain/lib directory
3. Start the OMS
4. Access the console page.

Monday, April 4, 2011

Admin server not coming up

LDAP corruption: 
Admin server was not coming up and was terminating at acquiring license part in admin server log.

Renamed admin server folder and started the admin service, it came up but the user was unable to login.
So i restored ldapfiles folder from (user_projects\domains\base_domain\servers\AdminServer\data\ldap\backup) to  (user_projects\domains\base_domain\servers\AdminServer\data\ldap) and restarted and issue fixed.

Friday, April 1, 2011

Using virtual directory mapping in production mode

Its a facility in which you can place all your JPEG or video files in one location and many deployables can access it from that common location.
i implemented <virtual-directory-mapping> in my deployment and placed a text file in the virtual directory and am able to access the text file via a browser after deployment.
However whenever i make random changes to the text file, the changed values are not reflected in the browser page dynamically/immediately.
However when i tried this on my development domain it worked for me.I was able to see the changed values instantly after updating the text file. I changed the development domain to production mode and it still worked for me.
Later when I created a new domain in Production mode I was not able see the changes anymore.

Weblogic.xml (dev)
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="">

I did the following change to weblogic.xml and it works in prod mode aswell.

Weblogic.xml (Prod)
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="">