12/24/09

BUILD SUCCESS

At last -
A Fresh installation of RedHat 5.2 on my laptop. Setting Hostname as surya.site.com, the installation went smooth.
Successfully installed WebSphere Portal Server 6.1.0 Express Edition on Linux.
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Completed install step: Finalizing Portal Server settings.
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.ReadPropertyAction, msg2, Read value: 10027 for property: WC_adminhost in file: /opt/IBM/WebSphere/Portal/PortalServer/package/tempportsWP.txt
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.installshield.wizardx.ascii.ModifyFile, msg2, Reading in ASCII file /opt/IBM/WebSphere/Portal/PortalServer/exp_inst/wp.config.firststeps/firststeps/launchpad/content/Work_with.properties.
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.installshield.wizardx.ascii.ModifyFile, msg2, /REPLACE TEXT: localhost:10027 ON LINE: 26/
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.installshield.wizardx.ascii.ModifyFile, msg2, anchor_launchAdm=< A href="javascript:void 0" name="test" onclick="viewPage(NO_DISKID, 'http://localhost:10027/ibm/console')">
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.Os400AsciiFileUpdate, msg2, Attempting to change file permissions to 777: /opt/IBM/WebSphere/Portal/PortalServer/exp_inst/wp.config.firststeps/firststeps/launchpad/content/Work_with.properties
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, fileName=/opt/IBM/WebSphere/Portal/AppServer/profiles/wp_profile/ConfigEngine/log/ConfigTrace.log
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, Search string not found
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.MsgLogAction, msg2, Entering MsgLogAction, action=LOG_INFO
(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.MsgLogAction, msg2, Sending message log: EJPIC0004I: The installation has completed successfully.

12/19/09

unix like commands in dos

are you looking for commands like tail, follow this url, http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displayLang=en download rktools.exe and enjoy the following commands -
* Acctinfo.dll (documented in Readme.htm)
* Adlb.exe: Active Directory Load Balancing Tool
* Admx.msi: ADM File Parser
* Atmarp.exe: Windows ATM ARP Server Information Tool
* Atmlane.exe: Windows ATM LAN Emulation Client Information
* Autoexnt.exe: AutoExNT Service
* Cdburn.exe: ISO CD-ROM Burner Tool
* Checkrepl.vbs: Check Replication
* Chklnks.exe: Link Check Wizard
* Chknic.exe: Network Interface Card Compliance Tool for Network Load Balancing
* Cleanspl.exe: Spooler Cleaner
* Clearmem.exe: Clear Memory
* Clusdiag.msi: Cluster Diagnostics and Verification Tool
* Clusfileport.dll: Cluster Print File Port
* Clusterrecovery.exe: Server Cluster Recovery Utility
* Cmdhere.inf: Command Here
* Cmgetcer.dll: Connection Manager Certificate Deployment Tool
* Compress.exe: Compress Files
* Confdisk.exe: Disk Configuration Tool
* Consume.exe: Memory Consumers Tool
* Creatfil.exe: Create File
* Csccmd.exe: Client-Side Caching Command-Line Options
* Custreasonedit.exe: Custom Reason Editor (documented in Readme.htm)
* Delprof.exe: User Profile Deletion Utility
* Dh.exe: Display Heap
* Diskraid.exe: RAID Configuration Tool
* Diskuse.exe: User Disk Usage Tool
* Dnsdiag.exe: SMTP DNS Diagnostic Tool (documented in Readme.htm)
* Dumpfsmos.cmd: Dump FSMO Roles
* Dvdburn.exe: ISO DVD Burner Tool
* Empty.exe: Free Working Set Tool
* Eventcombmt.exe: Check Replication
* Fcopy.exe: File Copy Utility for Message Queuing
* Frsflags.vbs
* Getcm.exe: Connection Manager Profile Update
* Gpmonitor.exe: Group Policy Monitor
* Gpotool.exe: Group Policy Objects
* Hlscan.exe: Hard Link Display Tool
* Ifilttst.exe: IFilter Test Suite
* Ifmember.exe: User Membership Tool
* Inetesc.adm: Internet Explorer Enhanced Security Configuration
* Iniman.exe: Initialization Files Manipulation Tool
* Instcm.exe: Install Connection Manager Profile
* Instsrv.exe: Service Installer
* Intfiltr.exe: Interrupt Affinity Tool
* Kerbtray.exe: Kerberos Tray
* Kernrate.exe: Kernel Profiling Tool
* Klist.exe: Kerberos List
* Krt.exe: Certification Authority Key Recovery
* Lbridge.cmd: L-Bridge
* Linkd.exe
* Linkspeed.exe: Link Speed
* List.exe: List Text File Tool
* Lockoutstatus.exe: Account Lockout Status (documented in Readme.htm)
* Logtime.exe
* Lsreport.exe: Terminal Services Licensing Reporter
* Lsview.exe: Terminal Services License Server Viewer
* Mcast.exe: Multicast Packet Tool
* Memmonitor.exe: Memory Monitor
* Memtriage.exe: Resource Leak Triage Tool
* Mibcc.exe: SNMP MIB Compiler
* Moveuser.exe: Move Users
* Mscep.dll: Certificate Services Add-on for Simple Certificate Enrollment Protocol
* Nlsinfo.exe: Locale Information Tool
* Now.exe: STDOUT Current Date and Time
* Ntimer.exe: Windows Program Timer
* Ntrights.exe
* Oh.exe: Open Handles
* Oleview.exe: OLE/COM Object Viewer
* Pathman.exe: Path Manager
* Permcopy.exe: Share Permissions Copy
* Perms.exe: User File Permissions Tool
* Pfmon.exe: Page Fault Monitor
* Pkiview.msc: PKI Health Tool
* Pmon.exe: Process Resource Monitor
* Printdriverinfo.exe: Drivers Source
* Prnadmin.dll: Printer Administration Objects
* Qgrep.exe
* Qtcp.exe: QoS Time Stamp
* Queryad.vbs: Query Active Directory
* Rassrvmon.exe: RAS Server Monitor
* Rcontrolad.exe: Active Directory Remote Control Add-On
* Regini.exe: Registry Change by Script
* Regview.exe (documented in Readme.htm)
* Remapkey.exe: Remap Windows Keyboard Layout
* Robocopy.exe: Robust File Copy Utility
* Rpccfg.exe: RPC Configuration Tool
* Rpcdump.exe
* Rpcping.exe
* RPing: RPC Connectivity Verification Tool
* Rqc.exe: Remote Access Quarantine Client
* Rqs.exe: Remote Access Quarantine Agent
* Setprinter.exe: Spooler Configuration Tool
* Showacls.exe
* Showperf.exe: Performance Data Block Dump Utility
* Showpriv.exe: Show Privilege
* Sleep.exe: Batch File Wait
* Sonar.exe: FRS Status Viewer
* Splinfo.exe: Print Spooler Information
* Srvany.exe: Applications as Services Utility
* Srvcheck.exe: Server Share Check
* Srvinfo.exe: Remote Server Information
* Srvmgr.exe: Server Manager
* Ssdformat.exe: System State Data Formatter
* Subinacl.exe
* Tail.exe
* Tcmon.exe: Traffic Control Monitor
* Timeit.exe (documented in Readme.htm)
* Timezone.exe: Daylight Saving Time Update Utility
* Tsctst.exe: Terminal Server Client License Dump Tool
* Tsscalling.exe: Terminal Services Scalability Planning Tools
* Uddicatschemeeditor.exe: UDDI Services Categorization Scheme Editor
* Uddiconfig.exe: UDDI Services Command-line Configuration Utility
* Uddidataexport.exe: UDDI Data Export Wizard
* Usrmgr.exe: User Manager for Domains
* Vadump.exe: Virtual Address Dump
* Vfi.exe: Visual File Information
* Volperf.exe: Shadow Copy Performance Counters
* Volrest.exe: Shadow Copies for Shared Folders Restore Tool
* Vrfydsk.exe: Verify Disk
* Winexit.scr: Windows Exit Screen Saver
* Winhttpcertcfg.exe: WinHTTP Certificate Configuration Tool
* Winhttptracecfg.exe: WinHTTP Tracing Facility Configuration Tool
* Winpolicies.exe: Policy Spy
* Wins.dll: WINS Replication Network Monitor Parser
* Wlbs_hb.dll & Wlbs_rc.dll: Windows Load Balancing Server Network Monitor Parsers

12/14/09

What you want to know about HTTP session persistence

Comment lines: Erik Burckart: What you want to know about HTTP session persistence -

Just the FAQs

In general, I get a lot of questions from various customers about HTTP session persistence. With Web 2.0 technologies taking off, more and more Web applications are being redesigned, and as they get changed, these same questions come up even more frequently. If you are involved in redesigning any Web applications for Web 2.0, here are answers to some of the questions you might soon be asking.

1. If I don’t need session persistence, can I turn it off?

Yes, you can configure session management to run with in-memory sessions, which is actually the default. You can still use HttpSessions in this mode, but if a failure occurs, the data stored in the HttpSessions will be lost.
.............read the remaining from this technical library article
Comment lines: Erik Burckart: What you want to know about HTTP session persistence

12/12/09

selinux blocks jvm

SELinux is preventing java from loading /software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so which requires text relocation.
Detailed DescriptionThe java application attempted to load /software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so which requires text relocation. This is a potential security problem. Most libraries do not need this permission. Libraries are sometimes coded incorrectly and request this permission. The SELinux Memory Protection Tests web page explains how to remove this requirement. You can configure SELinux temporarily to allow /software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so to use relocation as a workaround, until the library is fixed. Please file a bug report against this package.
Allowing Access
If you trust /software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so to run correctly, you can change the file context to textrel_shlib_t. "chcon -t textrel_shlib_t '/software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so'" You must also change the default file context files on the system in order to preserve them even on a full relabel. "semanage fcontext -a -t textrel_shlib_t '/software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so'"

12/11/09

VT-X/AMD-V acceleration error


When searched in the virtualbox discussion board, found this URL
http://forums.virtualbox.org/viewtopic.php?f=7&t=16951&start=0
What to do?
In the BIOS, enabled AMD-Virtualization.
error is gone

12/2/09

Phurnace Deliver onfiguration Viewer for WAS

The Phurnace Deliver Configuration Viewer for WebSphere

The Phurnace Deliver Configuration Viewer provides WebSphere customers with a graphical presentation of applications, configurations, servers, clusters, nodes, and domains of an application server environment. The view can be customized by scope, application, or individual component. Interrelations between the components are shown as connected lines, so at a glance, customers can determine if a configuration is associated with a particular server, cluster, or application.

Screenshots: http://phurnace.com/landing/configurationviewer

Recorded Demo: http://www.youtube.com/phurnacesoftware

11/28/09

hostname issues

I am still fighting with Portal Express installation. Now, I have changed my strategy and trying to install as silent with responsefile.

-silent
-G licenseAccepted="true"
-W setupTypePanel.selectedSetupTypeId="full"
-W globalInstall.location="/opt/IBM/WebSphere"
-W wasPanel.installChoice="install"

################################################################################
#
# EXISTING WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION
#
# Description: This is the value of the existing WebSphere Application Server
# if you selected to install on an existing instance.
#
# Be sure to follow the convention for specifying path information on your
# platform. For example,
#
# Windows: C:\WebSphere\AppServer
# AIX: /usr/WebSphere/AppServer
# Linux: /opt/WebSphere/AppServer
# Solaris: /opt/WebSphere/AppServer
# iSeries ND: /QIBM/ProdData/WebSphere/AppServer/V7/ND
# iSeries Base: /QIBM/ProdData/WebSphere/AppServer/V7/Base
################################################################################

# -W wasListPanel.existingWasLocation=""

################################################################################
#
# OPTIONAL:
# UNDETECTED WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION (NON-ISERIES)
#
# Description: Sometimes the Portal install program cannot detect an existing
# WebSphere Application Server(WAS). You cannot know this until install runtime
# when the silent install fails because the value of the above parameter
# wasListPanel.existingWasLocation cannot be validated.
#
# When this error occurs, and you are certain that there is a valid WAS at the
# location specified above, uncomment this parameter and enter the same value
# specified above.
#
# Be sure to follow the convention for specifying path information on your
# platform. For example,
#
# Windows: C:\WebSphere\AppServer
# AIX: /usr/WebSphere/AppServer
# Linux: /opt/WebSphere/AppServer
# Solaris: /opt/WebSphere/AppServer
#
################################################################################

# -W was.undetectedWas="/opt/IBM/WebSphere/AppServer"

and so on.
Now, as the responsefile expected, I have installed AppServer. I just wanted run and check, so called startServer.sh server1, to my surprise, it failed.
Stacktrace -
SystemErr R com.ibm.ws.exception.ConfigurationError:javax.naming.ConfigurationException: Cannot get canonical host name for server.

serverindex.xnl has hostname="null".
This is because -
Portal Server expected localhost.localdomain.com as hostname to localhost.localdomain.

I reverted /etc/hosts back to localhost.localdomain
and I have typed in hostname="localhost" in serverindex.xml.
Server started successfully.

Now, to kick start the PortalExpress, I am a kinda stuck, because, portal expects hostname as localhost.localdomain.com.
Portal cannot work with hostname as "localhost.localdomain.com", AppServer cannot run with host name *localhost.localdomain.com*. What a DEADLOCK!!!!!

11/26/09

build failed again

Well!! n-th run, build failed again with same message as posted here - http://javagongura.blogspot.com/2009/11/build-failed-on-line-3121.html

After this step. installation aborts.
Checked the App Server installation log, it was a successful installation.
Though its a failed installation, I tried to start the app server services.
I found some *amazing* things in startServer.log -
[11/25/09 22:31:28:005 EST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[11/25/09 22:31:28:157 EST] 0000000a AdminTool A ADMU0128I: Starting tool with the wp_profile profile
[11/25/09 22:31:28:159 EST] 0000000a AdminTool A ADMU3100I: Reading configuration for server: WebSphere_Portal
[11/25/09 22:31:32:605 EST] 0000000a WsServerLaunc E ADMU3002E: Exception attempting to process server WebSphere_Portal
[11/25/09 22:31:32:607 EST] 0000000a WsServerLaunc E ADMU3007E: Exception com.ibm.ws.process.exception.InvalidExecutableException: PROC0004E: Executable: [/opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java] does not appear to be a valid executable. Process could not be created.
at com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:159)
at com.ibm.ws.process.ProcessFactory.create(ProcessFactory.java:69)
at com.ibm.ws.management.launcher.ProcessLauncher.launch(ProcessLauncher.java:70)
at com.ibm.ws.management.launcher.LaunchCommand.launchProcess(LaunchCommand.java:246)
at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:309)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:264)
at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263)

This line in the above stack trace *Executable: [/opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java] does not appear to be a valid executable. Process could not be created.* amazed me.
Why startServer is trying to look for java in /opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java?

So, I have created folder structure like /opt/XYZWEBSPHEREXYZ/AppServer/java/bin/ and created a softlink to original appserver/java/bin/java.
But, its looking for remaining binaries in the same location.
So, need to create softlink for the entiar installation under /opt/XYZWEBSPHEREXYZ/AppServer/

Lets see...
BTW - Found a technote on this -
http://www-01.ibm.com/support/docview.wss?uid=swg21202564
The technote mentions that, because its a broken installation, you get such an error.

unzip

On linux (RHEL),
to unzip a zip file,
unzip file.zip
To unzip to a specific folder -
unzip file.zip -d /path-to-destination

11/24/09

BUILD FAILED on line 3121

(Nov 23, 2009 1:56:17 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: BUILD FAILED
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/exp_inst/wp.config/config/includes/wp.config_cfg.xml:46: The following error occurred while executing this line:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/AppServer/profiles/wp_profile/ConfigEngine/config/actions/db_cfg_mgr.xml:277: The following error occurred while executing this line:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/base/wp.db.impl/config/includes/wp.db.impl_cfg.xml:95: The following error occurred while executing this line:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/base/wp.db.impl/config/includes/wp.db.impl_cfg.xml:337: ERROR: Error during the execution of the sql files.
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: Total time: 38 seconds
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Return code = 1
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Executing command: completed
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Completed install step: Please wait while the WebSphere Portal Express database is initialized.
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, fileName=/software/IBM/WebSphere/PortalExpress/AppServer/profiles/wp_profile/ConfigEngine/log/ConfigTrace.log
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, Found text BUILD FAILED on line 3121
(Nov 23, 2009 1:57:06 PM), PortalExpress.install, com.ibm.wps.install.SwingPopUp, err, Logged message: EJPIC0017E: Portal installation failed. The Portal configuration step completed with errors. Please refer to the log file /software/IBM/WebSphere/PortalExpress/PortalServer/log/wpinstalllog.txt for additional information. The installer will now exit.
(Nov 23, 2009 1:57:06 PM), PortalExpress.install, com.ibm.wps.install.SwingPopUp, msg2, Exiting installer.
What to do?


Follow Up - http://www-01.ibm.com/support/docview.wss?uid=swg21291586

11/23/09

EJPIC0229E

My DB2Express installation on Linux is failing with the above error - EJPIC0229E: The DB2 Express installation step failed.

Just above to this log entry -
error while loading shared libraries: libstdc++.so.5: cannot pen shared object file: No such file or directory.


Follow up -
Found this technote http://www-01.ibm.com/support/docview.wss?rcss=faqtt_1Q09&uid=swg21297575


Follow up -
As mentioned in the above technote, I have downloaded and installed compat-libstdc++-33-3.2.3-61.i386.rpm. I got this from http://rpm.pbone.net/index.php3/stat/4/idpl/3416184/com/compat-libstdc++-33-3.2.3-61.i386.rpm.html_.
DB2Express successfully installed.

Now!! PortalExpress process get past Db2 hickup and installing WAS. Lets see what happens.

11/20/09

EJPIC0067E

I am installing PortalExpress v 6.1.0.0 on RHEL 5.2 on my laptop.

Some tips -
Run install.sh -console

You may encounter EJPIC0067E error.
EJPIC0067E: {0} requires a fully-qualified host name that is recognized by the DNS server. Short host names, loopback addresses, IP addresses and illegal characters such as blanks are not allowed. Enter the host name again.
Explanation: This installation requires a fully-qualified host name. Short host names, loopback addresses, and IP addresses are not allowed.
User Response: Enter the host name again.

To resolve this -
Just check the complete name of your box
uname -a
for me it is
localhost.localdomain
Now -
vi /etc/hosts as root
edit localhost.localdomain to localhost.localdomain.com

10/30/09

Profile Creation, New in 6.1

In 6.0 - To create a profile one can call AppServerPath/bin/ProfileCreator/pctSolaris.bin command or wasprofile.sh command.

Ex.,
./wasprofile.sh -create -profileName bladetcb6profile -profilePath /usr/IBM/WebSphere/AppServer/profiles/bladetcb6profile -templatePath /usr/WebSphere/AppServer -profileTemplates/default -nodeName bladetcb6node -cellName bladetcb6Cell -hostName bladetcb6.rtp.raleigh.ibm.com

Or you can kick this process thru firststeps.

In 6.1, wasprofile.sh command is available too but it is depricated. Instead you have manageprofil.sh command.
ex.,
manageprofiles.sh -create
-profileName shasti
-profilePath /shasti/WebSphere
-templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/dmgr
-cellName cell1
-hostName planetaix
-nodeName dmgr1

6.1.0.2 installer fails to create profile.

Issue -
WAS 6.1.0.2 installer fails to create profile.
log.txt -
Process, com.ibm.ws.install.ni.ismp.installtoolkitbridge.ISMPInstallToolkitBridgeForNIFramework, wrn, Config action failed: 97SInstallInvokeWSProfile - /software/IBM/WebSphere/AppServer/properties/version/nif/config/install/97SInstallInvokeWSProfile.ijc
Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: clearClassCache, percent complete: 25%
Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: os400fp, percent complete: 50%
Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: copyEmbedProductFile, percent complete: 75%
Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: runISCDeployRestore, percent complete: 100%
Process, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process is successful. Process type is: install
Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=2
Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFPARTIALSUCCESS

trace.txt -
INSTCONFPARTIALSUCCESS: Partially successful install of: zip:///software/tempinst/WAS/was.installconfig.pak
I Current install/uninstall process is successful. Process type is: install
I CWUPI0000I: EXITCODE=2
I INSTCONFPARTIALSUCCESS

Solution -
Install without creating a profile, apply latest fix packs and then create profile.

9/12/09

6.0 and 6.1 Co-exist topology

You have 6.0.xx installed on a machine. You wanted to install 6.1 on the same machine and migrate 6.0.xx to 6.1 later.
Now, You found that, your 6.1 installation going on smooth, but, you are amazed to see this message at the end of your log.txt
(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.installtoolkitbridge.ISMPInstallToolkitBridgeForNIFramework, wrn, Config action failed: 97SInstallInvokeWSProfile - /software/IBM/WebSphere61/AppServer/properties/version/nif/config/install/97SInstallInvokeWSProfile.ijc
(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: clearClassCache, percent complete: 25%
(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: os400fp, percent complete: 50%
(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: copyEmbedProductFile, percent complete: 75%
(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: runISCDeployRestore, percent complete: 100%
(Sep 11, 2009 4:04:37 PM), Process, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process is successful. Process type is: install
(Sep 11, 2009 4:04:37 PM), Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=2
(Sep 11, 2009 4:04:37 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFPARTIALSUCCESS


The reason for this is, since you already installed 6.0.xx, you have already used default ports. Now, for the new installation, you need to tell the installer not to look for default ports.

Explore the following technote -


http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=wrn%2c+Config+action+failed%3a+97SInstallInvokeWSProfile&uid=swg21261120&loc=en_US&cs=utf-8&lang=en

8/25/09

WAS Migration Step By Step

Here is the IBM WAS Tech Library Article on "A quick guide for migrating to WebSphere Application Server V6.1"

http://www.ibm.com/developerworks/websphere/library/techarticles/0608_chalmers/0608_chalmers.html

8/20/09

64 bit or 32 bit JVM?

How to know your WAS version is 32 bit or 64 bit?
This is a machine which has WAS 64 bit
$ ./java -d64 -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_06-erdist-20060404 20060511)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-erdist-20060404, mixed mode)
IBM Java ORB build orb50-20060511a (SR2)
XML build XSLT4J Java 2.7.4
XML build IBM JAXP 1.3.5
XML build XML4J 4.4.5

This is a machine which has WAS 32bit
$ ./java -d64 -version
execv(): No such file or directory
Error trying to exec /software/opt/IBM/WebSphere/AppServer/java/jre/bin/sparcv9/java.
Check if file exists and permissions are set correctly.
Failed to start a 64-bit JVM process from a 32-bit JVM.
Verify all necessary J2SE components have been installed.
(Solaris SPARC 64-bit components must be installed after 32-bit components.)

So acid Test is -
goto App Server javahome
/path/to/washome/java/jre/bin
./java -d64 -version

if it is 64 bit, it returns with version info.
otherwise returns with no such file or directory.

7/23/09

Collector Tool

Someone asked me how to run collector tool. IBM Doc says, run the tool not from APPSERVER_INST_PATH/bin, but run from working directory. What exactly is that?

The collector tool gathers information about your WebSphere Application Server installation and packages it in a Java archive (JAR) file that you can send to IBM Customer Support to assist in determining and analyzing your problem. Information in the JAR file includes logs, property files, configuration files, operating system and Java data, and the presence and level of each software prerequisite.

collector command - summary option

WebSphere Application Server products include an enhancement to the collector tool beginning with Version 5.0.2, known as the collector summary option.

The collector summary option helps you communicate with WebSphere Application Server technical staff at IBM Support. Run the collector tool with the -Summary option to produce a lightweight text file and console version of some of the information in the Java archive (JAR) file that the tool produces without the -Summary parameter. You can use the collector summary option to retrieve basic configuration and prerequisite software level information when starting a conversation with IBM Support.

The collector summary option produces version information for the WebSphere Application Server product and the operating system as well as other information. It stores the information in the Collector_Summary.txt file and writes it to the console. You can use the information to answer initial questions from IBM Support or you can send the Collector_Summary.txt file directly to IBM Support.

Collector tool collect key information including ffdc, configuration, logs, and so on and makes a jar file with all the information. So, depending on your configuration and all, jar file may occupy lot of space. So, IBM docs says that, create a folder out of appserver installation path.
Example,
mkdir /tmp/collector
cd /tmp/collector

Then run the script as needed
/appserver/instpath/profiles/profilename/bin/collector.sh
or
/appserver/instpath/profiles/profilename/bin/collector.sh -summery

Symbolic links

Sometimes, in the process of WebSphere, IHS Administration, it may require you to create symbolic links. This is the procedure.

ln is the command to create symbolic links.
$man ln
User Commands ln

NAME
ln - make hard or symbolic links to files

SYNOPSIS
/usr/bin/ln [-fns] source_file [target]

/usr/bin/ln [-fns] source_file... target

/usr/xpg4/bin/ln [-fs] source_file [target]

/usr/xpg4/bin/ln [-fs] source_file... target

DESCRIPTION
In the first synopsis form, the ln utility creates a new
directory entry (link) for the file specified by
source_file, at the destination path specified by target. If
target is not specified, the link is made in the current
directory. This first synopsis form is assumed when the
final operand does not name an existing directory; if more
than two operands are specified and the final is not an
existing directory, an error will result.

In the second synopsis form, the ln utility creates a new
directory entry for each file specified by a source_file
operand, at a destination path in the existing directory
named by target.
..............................


Example -
Developers wanted to have a look at SystemOut.log and SystemErr.log. They dont have uid on the box. So, I need to create a web link to this through HTTP Server.
I did like this.
I have created a document root called logs.
/logs
I created symbolic links to SystemOut.log and SystemErr.log like this
ln -s source destination
This creates a softlink *from* a file to a *file*
$ln -s /path/to/appserver/profiles/profilename/logs/servername/SystemOut.log SystemOut.log
$ln -s /path/to/appserver/profiles/profilename/logs/servername/SystemErr.log SystemErr.log
This created me two files SystemOut.log and SystemErr.log under /logs
if I ls -ltr on /logs, I get this list
SystemOut.log -> /path/to/appserver/profiles/profilename/logs/servername/SystemOut.log
SystemErr.log -> /path/to/appserver/profiles/profilename/logs/servername/SystemErr.log

Now, I have created a html file, say, index.html with hyperlinks like this -
Server Logs
< A HREF="SystemOut.log">SystemOut< / A>< br />
< A HREF="SystemErr.log">SystemErr< / A>

7/14/09

Enable Trace in Plugin-cfg.xml

WebServer Plugin writes a log, by default its named as http-plugin.log, by default placed under PLUGIN_HOME/logs/
Plugin writes Error messages into this log. The attribute which deals with this is
< Log > in the plugin-cfg.xml
Ex.,
< Log LogLevel="Error" Name="/usr/IBM/WebSphere/Plugins/logs/http_plugin.log" / >

According to above line all Error messages will be written into http-plugin.log.

How to enable trace in the plugin-cfg.xml? if that is the question, do like this -

< Log LogLevel="Trace" Name="/usr/IBM/WebSphere/Plugins/logs/http_plugin.log" / >

From the InfoCenter -
Plug-in Problem Determination Steps
The plug-in provides very readable tracing which can be beneficial in helping to figure out the problem. By setting the LogLevel attribute in the config/plugin-cfg.xml file to Trace, you can follow the request processing to see what is going wrong.
Note: If you are using a Veritas File System with large file support enabled, file sizes up to two terabytes are allowed. In this case, if you set the LogLevel attribute in the plugin-cfg.xml file to LogLevel=Trace, then the http_plugin.log file might grow quickly and consume all available space on your file system. Therefore, you should set the value of the LogLevel attribute to ERROR or DEBUG to prevent high CPU utilization.
At a high level, complete these steps.
The plug-in gets a request.
The plug-in checks the routes defined in the plugin-cfg.xml file.
It finds the server group.
It finds the server.
It picks the transport protocol, HTTP or HTTPS.
It sends the request.
It reads the response.
It writes it back to the client.


Here is the URL for Web server plug-in troubleshooting tips

Multiple Authentication Bypass Vulnerabilities within IBM WAS

Multiple Authentication Bypass Vulnerabilities within IBM WebSphere Application Server

OVERVIEW:
Two vulnerabilities in IBM WebSphere Application Server have recently been made public. IBM WebSphere Application Server is a software application server that uses web technologies and can be implemented on many common operating systems. Both vulnerabilities may allow malicious users to bypass authentication required to access a service running on the vulnerable server. Successful exploitation may allow attackers to gain unauthorized access to the service, which may lead to other attacks.

SYSTEMS AFFECTED:
The vulnerability identified by IBM in PK72138 (Bugtraq ID 35594):
* IBM WebSphere Application Server 7.0 1
* IBM WebSphere Application Server 6.1 23
* IBM WebSphere Application Server 6.1 22
* IBM WebSphere Application Server 6.1 21
* IBM WebSphere Application Server 6.1 20
* IBM WebSphere Application Server 6.1 19
* IBM WebSphere Application Server 6.1 18
* IBM WebSphere Application Server 6.1 17
* IBM WebSphere Application Server 6.1 15
* IBM WebSphere Application Server 6.1 13
* IBM WebSphere Application Server 6.1 12
* IBM WebSphere Application Server 6.1 10
* IBM WebSphere Application Server 6.1 .9
* IBM WebSphere Application Server 6.1 .7
* IBM WebSphere Application Server 6.1 .6
* IBM WebSphere Application Server 6.1 .5
* IBM WebSphere Application Server 6.1 .3
* IBM WebSphere Application Server 6.1 .2
* IBM WebSphere Application Server 6.1 .14
* IBM WebSphere Application Server 6.1 .1
* IBM WebSphere Application Server 6.1
* IBM WebSphere Application Server 6.1
* IBM WebSphere Application Server 6.1
* IBM WebSphere Application Server 6.1
* IBM WebSphere Application Server 6.1
* IBM WebSphere Application Server 6.1
* IBM WebSphere Application Server 7.0

The vulnerability identified by IBM in PK75992 (Bugtraq ID 35610):
* IBM WebSphere Application Server 7.0 1
* IBM WebSphere Application Server 6.1 21
* IBM WebSphere Application Server 6.1 19
* IBM WebSphere Application Server 6.1 17
* IBM WebSphere Application Server 6.1 15
* IBM WebSphere Application Server 6.0.2 31
* IBM WebSphere Application Server 6.0.2 29
* IBM WebSphere Application Server 6.0.2 27
* IBM WebSphere Application Server 6.0.2 .25
* IBM WebSphere Application Server 7.0

RISK:
Government:
* Large and medium government entities: High
* Small government entities: High

Businesses:
* Large and medium business entities: High
* Small business entities: High

Home users: N/A

DESCRIPTION:
IBM has confirmed the existence of two vulnerabilities that may allow a remote attacker to bypass application server authentication. Exploiting these vulnerabilities could allow an attacker to access restricted services, which may then lead to other attacks. Both vulnerabilities are associated with WS-Security, which is the security implementation within the Java API for XML Web Services (JAX-WS).
The first vulnerability discovered within WS-Security, referenced and addressed by IBM in PK72138, can only be exploited when the security policy is implemented at the 'Operational Level'. When this policy is established, WS-Security does not properly handle inbound requests that lack a SOAPAction or WS-Addressing Action. An attacker can craft a malicious inbound request to exploit this vulnerability. Successful exploitation may allow attackers to bypass certain security restrictions, which may then lead to other attacks.
The second vulnerability, referenced and addressed by IBM in PK75992, arises in the way WS-Security validates the 'UsernameToken' object. It is possible for WS-Security to incorrectly validate these tokens, allowing a malicious user to bypass the authentication process. This may allow a malicious user to conduct further attacks.

RECOMMENDATIONS:
We recommend the following actions be taken:
* Apply appropriate patches provided by IBM to vulnerable systems immediately after appropriate testing.
* Deploy network intrusion detection systems to monitor network traffic for malicious activity.

REFERENCES:

IBM:
http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&dc=D600&uid=swg21367223&loc=en_US&cs=UTF-8&lang=en&rss=ct180WebSphere

Security Focus:
http://www.securityfocus.com/bid/35594
http://www.securityfocus.com/bid/35610

CVE:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0903

6/29/09

Applet Security -

When an app is accessed through https, if there is no trust between app server and browser jre, client jvm may spit SSL HandShake Error. Error may go like this -
Error Occured during session initialization: Error SSL connecting to server:9446:javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Its very simple to solve this. One needs to import client certificate into jre/lib/security/cacerts which is the trust store of the JVM.
example -
"C:\Program Files\Java\jre1.5.0_11\bin\keytool" -import -trustcacerts -keystore "C:\Program Files\Java\jre1.5.0_11\lib\security\cacerts" -storepass changeit -noprompt -alias ALIAS_NAME -file "\CERTIFICATE_NAME"

6/22/09

10000

I am happy to announce that this blog crossed 10000 hits.

Thanks to all for viewing my blog on webshpere.

Please mail me if u have any questions or for any info or any suggestions.

admin.websphere@gmail.com

6/17/09

While using df

Solaris
df -h is the command to display available disk free space in bytes
e.g.,
$df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d84 3.9G 136M 3.8G 4% /var
swap 6.6G 992K 6.6G 1% /tmp
/dev/md/dsk/d101 20G 7.8G 12G 41% /software

Equivalent df in AIX
df -g

AIX df command

df Command

Purpose

Reports information about space on file systems. This document describes the AIX df command as well as the System V version of df.

Syntax

df [ [ -P ] | [ -I | -M | -i | -t | -v ] ] [ -k ] [ -m ] [ -g ] [ -s ] [FileSystem ... | File... ]

Description

The df command displays information about total space and available space on a file system. The FileSystem parameter specifies the name of the device on which the file system resides, the directory on which the file system is mounted, or the relative path name of a file system. The File parameter specifies a file or a directory that is not a mount point. If the File parameter is specified, the df command displays information for the file system on which the file or directory resides. If you do not specify the FileSystem or File parameter, the df command displays information for all currently mounted file systems. File system statistics are displayed in units of 512-byte blocks by default.

The df command gets file system space statistics from the statfs system call. However, specifying the -s flag gets the statistics from the virtual file system (VFS) specific file system helper. If you do not specify arguments with the -s flag and the helper fails to get the statistics, the statfs system call statistics are used. Under certain exceptional conditions, such as when a file system is being modified while the df command is running, the statistics displayed by the df command might not be accurate.

Note:
Some remote file systems, such as the Network File System (NFS), do not provide all the information that the df command needs. The df command prints blanks for statistics that the server does not provide.

The df command does not fully support NFSv4 filesystems. Use the nfs4cl command to extract block and space information.

Flags

-g Displays statistics in units of GB blocks. The output values for the file system statistics would be in floating point numbers as value of each unit in bytes is significantly high.
-i Displays the number of used inodes and the percentage of inodes in use for the file system. This output is the default when the specified file system is mounted.
-I Displays information on the total number of blocks, the used space, the free space, the percentage of used space, and the mount point for the file system.
-k Displays statistics in units of 1024-byte blocks.
-m Displays statistics in units of MB blocks. The output values for the file system statistics would be in floating point numbers as value of each unit in bytes is significantly high.
-M Displays the mount point information for the file system in the second column.
-P Displays information on the file system in POSIX portable format.

When the -P flag is specified, the header line appears similar to:

Filesystem 512-blocks Used Available Capacity Mounted on\n

If the -k, -m or -g flag is specified in addition to the -P flag, the column heading 512-blocks is replaced by the respective units, depending on which of these flags is used with the -P flag.

File system statistics are displayed on one line in the following order:

FileSystem, TotalSpace, UsedSpace, FreeSpace, UsedPercentage, MountPoint

-s Displays statistics on unmounted JFS or Enhanced JFS file systems by the command line arguments. If there are no arguments specified, the -s flag has no effect. If the file systems specified by the argument are currently mounted or an argument is a file, the -s flag has no effect for that particular argument. To collect statistics on unmounted file systems, an argument must be a JFS or Enhanced JFS file system mount point or device, the file system must be listed in /etc/filesystems, and the user must have read access to the device.
-t Includes figures for total allocated space in the output.
-v Displays all information for the specified file system.

The values of the output parameters with the flags -m and -g would be rounded off to nearest second decimal digit. If all or any two of the -k, -m and -g flags are specified, the last one specified takes effect.

Exit Status

This command returns the following exit values:

0 Successful completion.
>0 An error occurred.

Examples

  1. To display information about all mounted file systems, enter:
    df

    If your system has the /, /usr, /site, and /usr/venus file systems mounted, the output from the df command resembles the following:

    Filesystem 512-blocks Free   %Used   Iused  %Iused  Mounted on
    /dev/hd0 19368 9976 48% 4714 5% /
    /dev/hd1 24212 4808 80% 5031 19% /usr
    /dev/hd2 9744 9352 4% 1900 4% /site
    /dev/hd3 3868 3856 0% 986 0% /usr/venus
  2. To display information about /test file system in 1024-byte blocks, enter:
    df -k /test
    Filesystem    1024 blocks    Free    %Used   Iused  %Iused  Mounted on
    /dev/lv11 16384 15824 4% 18 1% /tmp/ravi1
    This displays the file system statistics in 1024-byte disk blocks.
  3. To display information about /test file system in MB blocks, enter:
    df -m /test
    Filesystem    MB blocks    Free    %Used    Iused  %Iused  Mounted on
    /dev/lv11 16.00 15.46 4% 18 1% /tmp/ravi1
    This displays file system statistics in MB disk blocks rounded off to nearest 2nd decimal digit.
  4. To display information about the /test file system in GB blocks, enter:
    df -g /test
    Filesystem    GB blocks   Free     %Used    Iused  %Iused  Mounted on
    /dev/lv11 0.02 0.02 0% 18 1% /tmp/ravi1
    This displays file system statistics in GB disk blocks rounded off to nearest 2nd decimal digit.
  5. To display available space on the file system in which your current directory resides, enter:
    cd/
    df .

    The output from this command resembles the following:

    Device   512-blocks  free   %used   iused   %iused  Mounted on
    /dev/hd4 19368 9976 48% 4714 5% /

Files

/etc/filesystems Lists the known file systems and defines their characteristics.
/etc/vfs Contains descriptions of virtual file system types.

Solaris df, du, ls commands

Solaris df command

New df, du, and ls Options

The df, du, and ls commands have a new h option for displaying disk usage and file or file system sizes that are easy to understand.

The default form of the df command displays file system size in blocks (512 bytes). The df output, in kilobytes, follows:

$ df -k / /usr
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 192056 94788 78063 55% /
/dev/dsk/c0t0d0s6 1982988 829966 1093533 44% /usr

The same file system sizes displayed in powers of 1024 follows:

$ df -h / /usr
Filesystem size used avail capacity Mounted on
/dev/dsk/c0t0d0s0 188M 93M 76M 55% /
/dev/dsk/c0t0d0s6 1.9G 811M 1.0G 44% /usr

The default form of the du command displays disk space in blocks (512 bytes). The du output, in blocks, follows:

% du -s k*
100 kadmin
98 kadmin.local
98 kdb5_util
90 keyserv
10 killall

The same disk space displayed in powers of 1024 follows:

% du -h k*
50K kadmin
49K kadmin.local
49K kdb5_util
45K keyserv
5K killall

The default form of the ls -l command displays file size in bytes. Use the ls -lh command to display file size in powers of 1024:

% ls -lh k
-r-xr-xr-x 1 root bin 49K Nov 30 03:32 kadmin
-r-xr-xr-x 1 root bin 49K Nov 30 03:32 kadmin.local
-r-xr-xr-x 1 root bin 49K Nov 30 03:32 kdb5_util
-r-xr-xr-x 1 root sys 44K Nov 25 04:37 keyserv
-r-xr-xr-x 1 root bin 4.3K Nov 25 04:36 killall

6/10/09

AIX Command Tips

Displaying top CPU_consuming processes:
#ps aux | head -1; ps aux | sort -rn +2 | head -10
Displaying top 10 memory-consuming processes:
#ps aux | head -1; ps aux | sort -rn +3 | head
Displaying process in order of being penalized:
#ps -eakl | head -1; ps -eakl | sort -rn +5
Displaying process in order of priority:
#ps -eakl | sort -n +6 | head
Displaying process in order of nice value
#ps -eakl | sort -n +7
Displaying the process in order of time
#ps vx | head -1;ps vx | grep -v PID | sort -rn +3 | head -10
Displaying the process in order of real memory use
#ps vx | head -1; ps vx | grep -v PID | sort -rn +6 | head -10
Displaying the process in order of I/O
#ps vx | head -1; ps vx | grep -v PID | sort -rn +4 | head -10
Displaying WLM classes
#ps -a -o pid, user, class, pcpu, pmem, args
Determinimg process ID of wait processes:
#ps vg | head -1; ps vg | grep -w wait
Wait process bound to CPU
#ps -mo THREAD -p
Cpu usage with priority levels
#topas -P

#svmon -Put 10 will give the memory mapping for the
top ten memory consuming processes.

#top


Remember, some commands needs you to be root. So, you switch to su to root.
Two important things here -
1. from ur profile, if u say
$su root
takes you to root with current shell. Means that, though u r root, u still carry ur .profile and ur env variables.
2. if u want to have root's env variables -
su - root or
su root
after getting into root
. ./.profile

AIX commands

Found some AIX commands thru google. Thought to share here. Enjoy :)
1. Useful commands
Note All AIX commands reference can be found under
http //www.austin.ibm.com/doc_link/en_US/a_doc_lib/aixgen/wbinfnav/CmdsRefTop.htm
1.1 Memory
bootinfo –r shows how much RAM does my machine has (as root)
lsattr –E –l sys0 –a realmem shows how much RAM does my machine have (as non root)
rmss -c 512
rmss -r sets the memory size to 512 MB
resets the memory size to the original one
1.2 Devices

lsattr -El en0 displays en0 driver params
lsattr -El ent0 displays ent0 HW params
lsattr -El rmt0 displays tape params
lscfg -vp -l rmt0 (all information about a tape drive)
lsattr -El sys0 displays system type, firmware, etc driver params
lscfg –v lists all system HW config (NVRAM)
lsdev –Csscsi list all scsi devices
lsdev –Cspci list all pci devices
lsparent –Ck scsi list all scsi adapters
lsdevfc list fiberchannel devices
cfgmgr Configures devices
lsdev -Ccdisk Shows all disks
lsdev -Cctape Shows all tapes
cfgmgr -v -l device –v Specifies verbose output. The cfgmgr command writes information about what it is doing to standard output.
cfgmgr -v -l device Name Specifies the named device to configure along with its children.
If you only turned on a disk tower at e.g. scsi2 cfgmgr -v -l scsi2 will only configure this with detailed output.
lsdisp To check which graphic adapter is installed.
lscfg -vp -l mga0 (all information about a adapter)
lscfg -vp -l hdisk0 | grep Machine gives info about the disk manufacture type
lsslot -c pci For 6F1 only !!!! Lists all slots ,voltage,boards,etc !!!!
bootlist -m normal cd0 rmt0 hdisk0 Changes the default bootlist
lsmcode -c display the system firmware level and service processor
lsmcode -r -d scraid0 display the adapter microcode levels for a RAID adapter scraid0
lsmcode -A display the microcode level for all supported devices


1.3 System info

/usr/bin/uname -m Get machine ID
/usr/bin/uname -M Get platform type
oslevel Displays current AIX level
oslevel -r Displays current AIX maintenance level
oslevel -g List filesets at levels later than maintenance level !!!
lsps -a Paging space settings.
lscfg -vp -l proc0 (1,2,3) (all information about a processor[s])
lscfg -vp -l mem0 |pg (all information about memory modules installed)
env ulimit Environment setings - show user ulimit
bootinfo –s hdisk0 Displays disk size
lsattr -El sys0 -a systemid Determines the system serial number
lscfg –vp|grep ROM|grep -v CD Determines the system Firmware level
1.4 System issues

TERM=vt100 -If you execute a command/application and it responds with msg
‘ The type of your terminal is unknown to the system’,run those commands (In ‘ksh’)
set term=vt100 -Same (In tcsh’)
rcp -rp /dataVolumes/brisque1.1.0/jobs/flower.job sciroot@ripro3:/dataVolumes/ripro3.3.0/jobs/ -Copying a file from one Unix machine (Brisque) to another (Server) the assumption is that both machines know each other’s names (in hosts file)
dd if=/dev/fd0 of=/temp/diskimage bs=4096 -Duplicate a diskette copy from diskette to hard drive
dd if=/temp/diskimage of=/dev/fd0 bs=4096 -copy diskette image onto diskette
/usr/lpp/X11/bin/xset -display unix 0 s off -Kill display timeout
lsfs -v jfs -List of Filesystem items.
lsfs -q -v jfs -you can see also the parameter of a filesystem and thus see if e.g. /backup was or is a big_filesystem_enabled one.
Important for the 2GB File limit.
lsuser –f root Shows all user parameters (max .file size,etc)
sysdumpdev -L Check last system dump status
sysdumpdev -l Check system dump device settings
lslpp -f Upd_Timna_DTM.obj List contents of the package
1.5 Networking

ksh
for ENT in ` lsdev –Cs pci|grep ent | awk '{ print $1 }'|cut –c 1,2,4 `;do
mktcpip –S $ENT
done
exit -Shows all interfaces IP config+mask+router+DNS !
host timna1 displays station default IP address – works ONLY in DNS environment
ifconfig en0 displays en0 driver params
netstat -i displays network interfaces setting
mktcpip -S en0 #host:addr:mask:_rawname:nameserv:domain:gateway:type:start
syslab18:192.9.100.1:255.255.255.0:en0:10.4.2.12:csil.creoscitex.com:10.4.30.1:N/A:no
GREAT TCPIP info in one command !!!
showmount –e displays all exported volumes
showmount -a show who's got my filesystemsses mounted over IP !
lssrc –g tcpip displays all IP oriented processes status
entstat -drt ent0 |grep –i error display any communication errors on etn0
entstat -r Resets all the statistics back to their initial values.
arp -a shows a local arp cache
cd /usr/local/es/;res restarts appletalk
netstat -ptcp shows IP statistics
netstat -pudp shows UDP statistics
netstat -c
-s
-m client only;
server only
NFS mount
netstat -I en0 10 Trace en0 every 10 seconds
netstat -rn Display routing info with IP address (10.4.27.182)
netstat -in Shows the state of all configured interfaces
netstat -r Display routing info with full hostnames (timna2.csil.creoscitex)
nfsstat –z ;to reset NFS stats without reboot
cat /etc/resolv.conf Check DNS settings
stopsrc –g NFS To stop NFS services on a client
startsrc –g NFS To start NFS services on a client
traceroute 149.115.39.1 Trace all hobs (interconnections=routers) to the destination IP
netpmon -o netpmon.out
trcstop Traces all network processes activity into a logfile. Must be preceede by a trcstop command !
nslookup hostname Shows the DNS server name and address
ping -R -c 1 bnc2 Ping with displaying the routing info
namerslv -s | grep domain | awk '{ print $2 }' Displays a fully qualified domain name of a host
rup Shows the status of a remote host on the local network
nmonnfs Traces all NFS processes activity
mount hostname:/filesystem /mount-point Mount an NFS filesystem
mknfsexp -d /directory Creates an NFS export directory
mknfsmnt Creates an NFS mount directory
rmnfs Stops and un-configures NFS services
mknfs Configures and starts NFS services
exportfs -u (filesystem) Un-exports a filesystem
exportfs Lists all exported filesystems
exportfs -a Exports all fs's in /etc/exports file
1.6 Disks

synclvodm -vP svg3 synchronizes ODM and the disk VG info.
redefinevg svg3 Redfined VG definition in ODM
lqueryvg -p hdisk0 –Avt -reads logical volumes info from disk
bootinfo -s hdiskx Shows Megabytes available even if no volume group is assigned.
lspv -p hdiskx (PP's used, location on disk, mount point)
lscfg -vp -l hdiskx (all information about a disk/raid)
1.7 Filesystem

chfs -a size=+200000 /var increases /var FS by 100MB
du -sk /john shows directory used space in kb !!!!
mount all mounts all FS
umount /dataVolumes/rtest9.1.0 unmounts a FS
fuser -k /dev/cd0 Releases a CD that will not unmount !
fuser –c /dataVolumes/rtest9.1.0 -Find out which process_id lock the FS
istat Shows when the file was last created/modified/accessed !!!!
1.8 System monitoring

istat Shows create/modify/access file info
alog -o -t boot | more displays system boot log
w Lists login users and their programs.
who Identifies the users currently logged in
/usr/local/es/swho Identifies the Ethershare users currently logged in
last |more shows last logins
last –20 Shows recent 20 lines
last root Shows username ‘root’ login/logout record
last ftp Shows all FTP session in the record
mount shows all mounted filesystems (nfs+local)
ps -ef show all running processes
ps -ef |grep Scitex show all scitex running processes
du -ak /scitex|sort -n -r|head –10 -Display 10 biggest directories on the volume by size
find /scitex -xdev -size +2048 -ls|sort -rn +6|head –10 -to find 10 top files in the root (/) directory larger than 1 MB.”-xdev” helps searching ONLY in “/” !!!!!!!!!
history Last commands run on the system by this user
alog -ot boot Lists a log of all boot operations
grep TX /etc/environment Verify daylight settings
1.9 Performance issues

nmon a nice monitor - runs only on AIX5 and up
topas a nice monitor - runs only on AIX 4.3.3 and up
monitor -top 10 -s 2 monitors system 10 top processes with 2 seconds
iostat 2 displays disks activity every 2 seconds refresh interval
iostat –a 2 AIX5 ONLY !!!!
displays disks and ADAPTER !!!! activity every 2 seconds refresh interval
vmstat 2 ;monitors virtual memory statistics every 2 seconds (see appendix A)
sar –P ALL 2 2 Show all CPU’s activity on an SMP machine
svmon –i 2 Monitors real and virtual memory
ps auxw | sort –r +3 |head –10 -Shows top 10 memory usage by process
ps auxw | sort –r +2 |head –10 -Shows top 10 CPU usage by process
ps –auw | grep defunct Shows zombies processes (to kill – reboot or kill the parent)
filemon –O all –o filemon.out ; find / -name core ; trcstop Traces FS,LV,disks,files activityof a “find” command into a logfile (filemon.out). Must be preceded by a trcstop command.
tprof –x find / -name core ; trcstop Traces CPU activityof a “find” command Severall logfile are created. Must be preceded by a trcstop command.
tprof -ske -x "sleep 30" -Trace CPU activity for next 30 seconds.Results in file sleep.tprof

lvmstat –ev svg1
lvmstat –v svg1 2 AIX5 ONLY !!!!
enable gathering the VG statistics
Display VG logical volumes statistics every 2 seconds
1.10 Remote issues (working over the modem)

pdelay tty0; pdisable tty0 >/dev/null ;penable tty0
-Resets tty0
stty erase '^?' Makes bakespace to work
/scitex/version/utils/modem/kermit -l /dev/ttyx –c atdt {phone #} Use Unix to Dail-out (for any reason) ttyx is the serial port the cable is connected
/scitex/version/utils/modem/kermit -s /u/d0/ripro_messages -i Sends a file to a remote desktop in binary mode
/scitex/version/utils/modem/kermit –r
-Receives a file to from remote desktop
1.11 Browsing errlog with errpt

errpt -a -s 0604090601 -e 0605090901 browse the errlog in detail for all errors within a timeframe
errpt -a -N SYSPROC |more
errpt -a -N SYSPROC > /tmp/err.log Browse the errlog for the SYSPROC resource, can be into the file
errpt -j 5DFED6F1 -Browse the errlog by the identifier
errpt –A -AIX5 ONLY !!!! Shows less detailes then errpt -a
errpt –D -AIX5 ONLY !!!! eliminates double entries
1.12 Security issues

chmod -s Filename Remove Sticky Bit to a file or directory

chmod +r+w+x+t Filename Add Read+Write+Execute+Temp mode to a file or directory.
This is a ‘blanket’ change for all owner, user & group.
Numeric Access Modes
0 (---) - no access
1 (--x) - execute permissions; search permissions for directories
2 (-w-) - write access
3 (-wx) - execute/search permission and write access
4 (r--) - read access
5 (r-x) - execute/search permission and read access
6 (rw-) - read and write access
7 (rwx) - execute/search permission and read and write access
mkpasswd -f rebuild the /etc/passwd indexes in case of suspected corruption
1.13 Miscellaneous
ksh
find / -type f|xargs grep "10.4.27.181" 2> /dev/null
-Find all files containing my IP address
compress -c file > file.Z Compresses the files while keeps the original
whereis Returms full path of program

5/26/09

How to reload .profile

You made a change to your .profile. How to reload your .profile?
One way is, exit from the session, telnet or ssh again to that host. Another way is -
After you changing the .profile, save and quit. Then at the command prompt type in this
$. ./.profile

This reloads your .profile.

4/28/09

tar.Z file

How to extract a tar.Z file on unix box?
This is the way

zcat file.tar.Z | tar xvf -

3/27/09

uninstall fixpacks

Someone asked me how to troubleshoot fixpack uninstallation process.

Befroe going into that, read the following from UpdateInstaller README. You can find this under Update_Inst_Path/docs/raedme_updateinstaller.txt/pdf/html

3.0 Uninstalling maintenance packages

This topic describes how to use the Update Installer for WebSphere
Software to uninstall interim fixes, fix packs, and refresh packs. The
Update Installer for WebSphere Software is also known as the update
installer program, the updateInstaller program, and the Update
installation wizard.



Use the proper authorizations to successfully uninstall product updates.
Use the update installer program as the root user on a Linux or UNIX
platform, or as the administrator on a Windows platform.

The Update Installer wizard is an InstallShield for Multiplatforms
wizard that runs with either a graphical user interface or in silent
mode with a response file.

Important: See 4.3, "Known problems and workarounds for the update
command" for information about known problems and workarounds.

The following descriptions contain reference information about
uninstalling interim fixes, fix packs, and refresh packs on WebSphere
Application Server products:

Overview of the uninstall procedure
To uninstall a maintenance package:
1. Use the update installer to install the maintenance package,
which creates a backup file in the
app_server_root/properties/version/nif/backup directory. IBM
does not support user modifications to backup files.
2. Use the update installer program to remove the maintenance
package as described in this topic.

Viewing the fix level of the node
You can use the 5.0, "versionInfo command" in the
app_server_root/bin directory to display the exact fix and
version level of the product. However, do not use the
versionInfo command while installing or uninstalling a
maintenance package.

Do not launch multiple copies of the Update Installer wizard at one
time: Concurrent launches of the update installer program are not
supported. Performing more than one update at the same time can produce
unpredictable results, which might include a failed or faulty
installation.

Required information

The graphical interface requires the following information that you
must supply:

Table 4. Information required when uninstalling a maintenance package
+-----------------------+----------------------+----------------------+
| Field | Valid values | Description |
+-----------------------+----------------------+----------------------+
| File path of the | Identify the | The Update Installer |
| installation root | installation root | application defaults |
| directory of the | directory for one of | to the last-visited |
| WebSphere product and | the following | product location. |
| the Update Installer | products: | |
| | * IBM WebSphere | |
| | Application Server | |
| | * IBM WebSphere | |
| | Application Server - | |
| | Express | |
| | * Embedded version | |
| | of the IBM WebSphere | |
| | Application Server - | |
| | Express | |
| | * IBM WebSphere | |
| | Application Server | |
| | Network Deployment | |
| | * IBM WebSphere | |
| | Extended Deployment | |
| | * IBM Application | |
| | Client for WebSphere | |
| | Application Server | |
| | * IBM WebSphere | |
| | Business Integration | |
| | Server Foundation | |
| | * Web server | |
| | plug-ins for | |
| | WebSphere | |
| | Application Server | |
+-----------------------+----------------------+----------------------+
| File name of the | Select a maintenance | The default |
| maintenance package | package to uninstall | maintenance package |
| to uninstall. | from the | is the package with |
| | app_server_root/prop | the latest date |
| | erties/version/ | stamp and time stamp |
| | update/backup | in the |
| | directory. | app_server_root |
| | | /properties/version/ |
| | | update/backup |
| | | directory. |
+-----------------------+----------------------+----------------------+



The following procedure describes how to uninstall a maintenance
package.

1. Log on to the operating system.

[Linux] In addition, verify that the umask setting is 022. To verify
the umask setting, issue the following command:

umask

To set the umask setting to 022, issue the following command:

umask 022

2. Change directories to the updi_root directory.
3. [Windows] Use the Windows Services panel to stop all services for
WebSphere Application Server processes.
4. Stop all Java processes that use the IBM Software Developer Kit (SDK)
that the WebSphere Application Server product provides.

Before uninstalling interim fixes, fix packs, and refresh packs on a
machine, stop all Java processes on the machine that use the IBM SDK,
Java Technology Edition that WebSphere Application Server provides.



WebSphere Application Server processes include:
* Application server processes
* The nodeagent process on an application server node when the node
is federated into a deployment manager cell
* The dmgr process for the deployment manager server



Stop all Java processes if necessary. If you uninstall a maintenance
package while a WebSphere Application Server-related Java process
runs, IBM does not guarantee that the product can continue to run
successfully, or without error.

5. Use the update installer to uninstall the maintenance package.

Uninstall the interim fix on each application server node in a cell
before uninstalling the maintenance package from the deployment
manager node.



Issue one of the following commands to uninstall with the graphical
interface:

Table 5. Update installer commands for uninstalling with the graphical
interface
+--------------------------------+-------------+----------------------+
| Command example | Type of | Description |
| | installatio | |
| | n | |
+--------------------------------+-------------+----------------------+
| update.bat -W | Graphical | Initializes the |
| update.type="uninstall" | interface | maintenance package |
| | mode | field with the name |
| | | of the maintenance |
| | | package that was |
| | | most recently |
| | | installed. |
| | | Accept all of the |
| | | default values to |
| | | uninstall the |
| | | maintenance package |
| | | with the most recent |
| | | date stamp and time |
| | | stamp. |
+--------------------------------+-------------+----------------------+
| update.bat -W | Graphical | Overrides the |
| product.location="e: | interface | graphical interface |
| \IBM\WebSphere\AppServer" -W | mode | with the location of |
| update.type="uninstall" | | the WebSphere |
| | | software to update. |
| | | The default |
| | | maintenance package |
| | | to uninstall is the |
| | | most recently |
| | | installed |
| | | maintenance package |
| | | for that software. |
+--------------------------------+-------------+----------------------+
| update.bat -W | Graphical | Overrides the |
| backup.package="PQ20029.pak" | interface | maintenance package |
| -W update.type="uninstall" | mode | field with the name |
| | | of the maintenance |
| | | package to |
| | | uninstall. |
+--------------------------------+-------------+----------------------+
| update.bat -W | Graphical | Overrides the |
| product.location="e: | interface | location of the |
| \IBM\WebSphere\AppServer" -W | mode | WebSphere software |
| backup.package="PQ20029.pak" | | to update and the |
| -W update.type="uninstall" | | name of the |
| | | maintenance package |
| | | to uninstall. |
+--------------------------------+-------------+----------------------+
| update.bat -options | Graphical | Overrides all |
| "responsefiles/file_name" | interface | default values with |
| | mode with | values that you |
| | an options | specified in the |
| | file | options response |
| | | file. |
| | | If you omit either |
| | | value from the |
| | | response file, the |
| | | default maintenance |
| | | package is the |
| | | installed package |
| | | with the most recent |
| | | date stamp and time |
| | | stamp. The default |
| | | software is the |
| | | software installed |
| | | in the parent |
| | | directory. |
+--------------------------------+-------------+----------------------+



Issue the following command to use the silent interface:

Table 6. Update installer command for uninstalling in silent mode
+--------------------------------+-------------+----------------------+
| Command example | Type of | Description |
| | installatio | |
| | n | |
+--------------------------------+-------------+----------------------+
| update.bat -silent -options | Silent mode | Overrides all |
| "responsefiles/file_name" | with an | default values with |
| | options | values that you |
| | file | specified in the |
| | | options response |
| | | file. |
| | | Always use a |
| | | response file that |
| | | is based on the |
| | | response file under |
| | | updi_root/responsefi |
| | | les. |
+--------------------------------+-------------+----------------------+



This procedure results in uninstalling maintenance packages to update
WebSphere software.



After uninstalling maintenance packages, you can continue to use the
WebSphere software.

Rolling back changes to existing profiles: Some maintenance packages
for WebSphere Application Server products, such as Refresh Pack 2,
update existing profiles. If you roll back a maintenance package that
contains a profile update, also use any undo scripts provided with the
profile update script to roll back changes to the existing profiles.

The readme file for a maintenance package describes scripts that update
and scripts that roll back profile fix levels. For example, Refresh Pack
2 for WebSphere Application Server includes required service for the
JDBC resource provider templates in existing profiles. See the readme
for the profile update and undo scripts for the JDBC-related update for
more information.

Deleting profiles created by a service level that is now rolled back:
See Profiles remain at the Version 6.0.2 level after roll back for a
description of a limitation that requires profiles to be at the same
service level or at a lower service level that the WebSphere Application
Server product.

For example, suppose that you install Fix Pack 1 for Version 6.1
(Version 6.1.0.1), create a new profile, and then roll back Fix Pack 1.
You must delete the profile that you created at the Version 6.1.0.1
level to avoid possible problems.

3.1 uninstall.txt

The Update Installer for WebSphere Software can use an options response
file to uninstall maintenance packages from a command line interface.

The uninstall.txt file has one directive that identifies the backup file
for uninstalling a service update. Comments in the file describe how to
set the string value.

The Update Installer for WebSphere Software wizard reads the options
file to determine uninstall choices. The Update Installer uninstalls the
maintenance package in silent mode, instead of displaying a graphical
user interface.

3.1.1 Location of the response file

The sample options response file is named uninstall.txt. The file is in
the updi_root/responsefiles directory after you unzip the Update
Installer for WebSphere Software into the installation root directory of
the WebSphere software product.

3.1.2 Uninstalling silently

The options file supplies the values to the Update installer wizard when
uninstalling silently. The wizard reads the options file to determine
responses and does not display the graphical user interface.

The following command uses a copy of the options file named
myresponsefile.txt to provide uninstall option responses during a silent
uninstall:

./update.sh -options "responsefiles/myresponsefile.txt" -silent

If you do not use the -silent option, the wizard uses the response file
to provide initial values for the graphical interface:

./update.sh -options "responsefiles/myresponsefile.txt"

3.1.3 Response file user entry validation

In a silent uninstall, response file validation has been coded into the
uninstall process. If the validation does not pass, the failure is
recorded in the log files in the app_server_root/logs/update/tmp
directory.

Location of the maintenance package to be uninstalled


Default directive setting
-W backup.package=""

Valid setting
You must set this directive to the location of the
backup file. The backup file reverses the application
of the maintenance. For example, you might specify the
following location on a Linux system:
/opt/properties/version/nif/backup/maintenance_package_to_uninstall


Error identifiers:

* The maintenance package cannot be uninstalled.
Uninstalling the maintenance would break the
following superseding maintenance packages.
Uninstall the superseding maintenance packages
first: list_of_superseding_maintenance_packages
* This maintenance package cannot be uninstalled. The
following maintenance packages are dependent on the
package that you are attempting to uninstall:
list_of_dependent_maintenance_packages
* This maintenance package cannot be uninstalled. The
following maintenance packages are dependent on the
APARs you are attempting to uninstall:
list_of_dependent_maintenance_packages
* No installation backup packages are available for
uninstalling maintenance.


Product location


Although uninstalling maintenance from another product is
possible, always use the Update installer wizard from the
directory structure of the product that you are updating if
possible. Problems can occur when a mismatch between product
SDKs occurs, for example.



Do not use this directive unless absolutely necessary.



Default directive setting
-W
product.location="SPECIFY_PRODUCT_INSTALL_LOCATION_HERE"

Valid setting
You must set this directive to the installation root
directory of the alternate product. For example, you
might specify the following location on a Linux
system:
/opt/IBM/WebSphere/AppServer2


Error identifiers:

* The maintenance package cannot be uninstalled.
Uninstalling the maintenance would break the
following superseding maintenance packages.
Uninstall the superseding maintenance packages
first: list_of_superseding_maintenance_packages
* This maintenance package cannot be uninstalled. The
following maintenance packages are dependent on the
package that you are attempting to uninstall:
list_of_dependent_maintenance_packages
* This maintenance package cannot be uninstalled. The
following maintenance packages are dependent on the
APARs you are attempting to uninstall:
list_of_dependent_maintenance_packages
* No installation backup packages are available for
uninstalling maintenance.
*

3.1.4 Usage notes

* The file is not a read-only file.
* Edit this file directly with your flat file editor of choice, such as
Kate on SLES or WordPad on a Windows platform.
* The file must exist to perform a silent uninstall. The Update
installer wizard reads this file to determine uninstall parameters.
Provide the fully qualified file path to the backup file.
* Save the copy of the options file in the responsefiles directory for
best results.

3.1.5 Example uninstall.txt file

Edit the version of the file that is included in the Update Installer
for WebSphere Software ZIP file. The following example is not guaranteed
to be an accurate representation of the actual file.

################################################################################
#
# This is the silent install response file for uninstalling maintenance packages
# using the update installer.
#
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, *uncomment* and modify the parameters defined within.
#
# Use the following command line when running the wizard from the update
# installer directory:
#
# update -options responsefiles/uninstall.txt -silent
#
# Please enclose all values within a single pair of double quotes.
#
################################################################################


################################################################################
#
# Used to input the maintenance backup package filename to be uninstalled.
# This is the same filename as the package that was originally installed.
# A maintenance package can only be uninstalled if a backup package exists.
#
# ie. -W backup.package="PQ20029.pak"
#
# Note: If no package is specified, a default of the last installed maintenance
# package will be used.
#
#-W backup.package=""


################################################################################
#
# Used to modify the product install location that will be updated.
# This value should be left commented out if the Update Installer is
# being run from the recommended location
#
# ie. -W product.location="C:\Program Files\IBM\WebSphere\AppServer"
#
# Note: The product install location should always been specified, and it should
# always be the full path.
#
-W product.location=""



################################################################################
#
# Do not edit these values.
#
-W update.type="uninstall"

.....................................................................


So, according to documentation,
1. uninstall process requires you to log in as correct privileges.
2. you need to make sure that you are using correct UpdateInstaller.
3. in general, if the uninstallation fails, may mean that, installation is partial success.
4. check the dependencies.
5. you need to tail app_server_root/logs/update/maintenance_package.uninstall this log for any issues and act accordingly
6. Sometimes, this could be a reason -
(Sep 27, 2006 12:33:10 PM), UpdateInstaller, com.ibm.ws.install.ni.ismp.actions.PopulateTitleBarAction, msg1, IBM Update Installer for WebSphere Software V6.0.2.7
(Sep 27, 2006 12:33:11 PM), UpdateInstaller, com.ibm.ws.install.ni.ismp.actions.PopulateUninstallMaintenancePanelAction, err, CWUPI0024E: /software/IBM/WebSphere/AppServer/updateinstaller/maintenance/6.0.2-WS-WAS-SolarisSparc-FP0000005.pak is not a valid maintenance package or may be corrupted.
(Sep 27, 2006 12:33:11 PM), UpdateInstaller, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=1
(Sep 27, 2006 12:33:11 PM), UpdateInstaller, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFFAILED

In such cases, you can manually remove the pack and update corresponding maintenance files.