Sun java System Webserver (iplanet) browser information in logs

Add below partameter in log format :

"%Req->headers.user-agent%"

you can find below Access logs after adding the above paramter server.xml or customlog format through console and following with restart

Chrome :
127.0.0.1 - [13/Aug/2012:15:25:26 +0000] "GET /webservicesm HTTP/1.1" 200 "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/

Mozila :
127.0.0.1 - [13/Aug/2012:15:26:02 +0000] "GET /webservicesm HTTP/1.1" 200 "Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20100101 Firefox/11.0"

Internet Explorer :
127.0.0.1 - [13/Aug/2012:15:26:24 +0000] "GET /webservicesm.html HTTP/1.1" 200 "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; BTRS129225)"

Configuring cache controls for static files in Sun Java System Web Server 7

Edit the obj.conf as mentioned below:
Add these below lines after AuthTrans and NameTrans
directive to set up 10 days of cache from current access time
if path="~"
ObjectType fn="set-variable" insert-srvhdrs="Expires:$(httpdate($time + 864000))"
ObjectType fn="set-cache-control" control="public,private,must-revalidate,max-age=$(httpdate($time + 864000))"
/if

Patches to be installed: [119963-20] on solaris to install Orcle IPlanet 7.0.9

ERROR : Orcle IPlanet 7.0.9 on solaris installation will Abort with the below error
Aborting the installation.
Jul 24, 2012 8:53:57 AM com.sun.web.installer.common.dialogs.CustomDirectorySelectionPanel isDisplayComplete
INFO: Installing Oracle iPlanet Web Server 7.0.9
Jul 24, 2012 8:53:58 AM com.sun.web.installer.web.dialogs.PatchDetectionListener displayWarning
INFO: The following patches need to be installed for the server installation to complete successfully.
Patches to be installed: [119963-20]

CAUSE:
showrev -p Prints only the revision information about patches
user@localhost1 ~ $ showrev -p | grep Patchid
Patch: 119963-08 Obsoletes: Requires: Incompatibles: Packages: SUNWlibC
the above information says SUNWlibC patches are not installed in the OS

SOLUTION:We need to install SUNWlibC Patch at Opertation system Level

http://docs.oracle.com/cd/E19146-01/821-1835/gduwe/index.html

WebLogic Managed Servers Fail During Startup with weblogic.store.io.file.StoreFile Exception

Aug 1, 2012 6:57:46 PM UTC Info Store localhost server <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> 1343847466261 BEA-280008 Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=$DOMAIN_HOME/servers//data/store/diagnostics/ requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
Aug 1, 2012 6:57:46 PM UTC Critical WebLogicServer localhost server main <> <> <> 1343847466271 BEA-000386 Server subsystem failed. Reason: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.store.io.file.StoreFile.close(StoreFile.java:432)
at weblogic.store.io.file.Heap.open(Heap.java:307)
at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:104)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:413)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:404)
at weblogic.store.xa.PersistentStoreManagerXA.createFileStore(PersistentStoreManagerXA.java:118)
at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:91)
at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:128)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

CAUSE:

The file $DOMAIN_HOME/servers/ServerName/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT is somehow corrupted.
The Archive component of the WebLogic Diagnostics Framework (WLDF) captures and persists all data events, log records, and metrics collected by WLDF from server instances and applications running on them and saves them into this file. So having this file corrupted, prevents the Server from writing the WLDF information, and hence it fails to start.

SOLUTION:

Backup and remove the WLS_DIAGNOSTICS000000.DAT file,then restart the server: a new file will be created automatically.
This should not affect the server performance. It will only cause the loss of the archived diagnostic information (which is likely already lost since the file is corrupt).