Compared with uninstalling WPS6.0, it is much easier to uninstall WPS6.1 silently on AIX.
IBM introduced more parameters for uninstall scripts. You can follow the steps
(1) stop All WPS6.1 processes.
(2) logon the WPS server with the user "root"
(3) go to the directory /IBM/WebSphere/ProcServer/uninstall.wbi
(4) run the following command:
./uninstall -OPT isUmbrellaUninstall="true" -OPT removeProfilesOnUninstall="true" -silent
the output should like this:
I Process Type: uninstall
I Install Type: nonOS400
I Install Mode: silentMode
I #Received OPT Properties
#Mon Feb 28 10:38:27 EST 2011
isUmbrellaUninstall=true
removeProfilesOnUninstall=true
INSTCONFPARTIALSUCCESS: The profiles no longer exist, but errors occurred. For more information, consult /IBM/WebSphere/ProcServer/logs/manageprofiles/deleteAll.log.
you may see some alerts, but when you check the log file, you will see the the profile already removed.
<logger>com.ibm.wsspi.profile.WSProfileCLI</logger>
<level>INFO</level>
<class>com.ibm.wsspi.profile.WSProfileCLI</class>
<method>invokeWSProfile</method>
<thread>11</thread>
<message>Returning with return code: INSTCONFSUCCESS</message>
</record>
and if you check the unistall log files at the directory /IBM/WebSphere/ProcServer/logs/uninstall, you will see uninstall is successful.
(Feb 28, 2011 10:49:00 AM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS
At the same time, on AIX, you can run "lslpp -l |grep -i websphere" to check if the WebSphere package already removed
(5) remove the WebSphere directories.
Monday, February 28, 2011
Saturday, February 26, 2011
WAS7 - Busines level Application can not be removed
In WAs7, IBM introduced the new concept BLA (business level application) which can include EAR, JAR or share libraries.
However, some times when you update a EAR file from console but failed, which cause the Enterprise Application was removed but BLA was still left. When you redeploy the same module, the module can not be deployed, and you will see the following error when you want to delete the existing BLA:
CWWMH0149E: Cannot delete business-level application "WebSphere:blaname=AppEAR" because it contains composition units. Delete all composition units which belong to the business-level application, and then delete the business-level application. Check log for details.
As a matter of fact, you already removed all composition units, and you can not see any composition units belong to this BLA from administrative console or even using wsadmin scripts.
Here is a way for how to remove the isolated BLA if BLA can not be removed without any composition units belonging to it.
1) stop the WebSphere Application Server.
2) backup the WebSphere profile configuration using "backupConfig.sh" command
3) go to directory <ProfileDir>/config/cells/<CellName>/blas
4) remove the directory of specified BLA
5) go to directory <ProfileDir>/config/cells/<CellName>/cus
6) remove the directory of specified BLA
7) go to directory <ProfileDir>config, remove temp directory
8) go to directory <ProfileDir>, remove wstemp and temp directory
9) restart the WebSphere Application Server
10) redeploy the module.
this is the way I solved this problem. I hope someone can provide the better way to solve this issue.
However, some times when you update a EAR file from console but failed, which cause the Enterprise Application was removed but BLA was still left. When you redeploy the same module, the module can not be deployed, and you will see the following error when you want to delete the existing BLA:
CWWMH0149E: Cannot delete business-level application "WebSphere:blaname=AppEAR" because it contains composition units. Delete all composition units which belong to the business-level application, and then delete the business-level application. Check log for details.
As a matter of fact, you already removed all composition units, and you can not see any composition units belong to this BLA from administrative console or even using wsadmin scripts.
Here is a way for how to remove the isolated BLA if BLA can not be removed without any composition units belonging to it.
1) stop the WebSphere Application Server.
2) backup the WebSphere profile configuration using "backupConfig.sh" command
3) go to directory <ProfileDir>/config/cells/<CellName>/blas
4) remove the directory of specified BLA
5) go to directory <ProfileDir>/config/cells/<CellName>/cus
6) remove the directory of specified BLA
7) go to directory <ProfileDir>config, remove temp directory
8) go to directory <ProfileDir>, remove wstemp and temp directory
9) restart the WebSphere Application Server
10) redeploy the module.
this is the way I solved this problem. I hope someone can provide the better way to solve this issue.
Monday, February 14, 2011
WPS--Clean the events in WPS CEI Database
The CEI Events in WPS CEI Database will be increasing with more and more business transactions were processed and will take a lot of hard disk.
Here is how to Clean the events in CEI Database.
1) run the command
wsadmin.sh -f eventbucket.jacl -change -serverName server1
this command will switch the event bucket from 0 to 1 or 1 to 0 depending on which one is current event bucket.
To check the current event, use the following command
wsadmin.sh -f eventbucket.jacl -status -serverName server1
2) log on to the database server (here the database is DB2), then issue the command with the db2 instance owner.
fastpurge.sh CEIDB db2instance1 password=password
(3) run reorg.sh to reorganize the database
reorg.sh CEIDB db2instance1 password=password
(4) run runstats.sh to run statistics on database
runstats.sh CEIDB db2instance1 password=password
Note:
1) when you run eventbucket.jacl in cluster environment, you may see the following errors:
WASX7017E: Exception received while running
file "$WAS_HOME/util/event/eventpurge.jacl"; exception
information: javax.management.InstanceNotFoundException: *:*)
this bug will be fixed in WPS7.0.0.17 (http://www-01.ibm.com/support/docview.wss?uid=swg1PM21539). However, you can ask IBM to provide the updated com.ibm.events.client.jar, and then you will run it like the following command
wsadmin.sh -f eventbucket.jacl -status -clusterName SupportCluster
2) fastpurge.sh, reorg.sh and runstats.sh can be found at the directory <profileDir>/dbscripts/CEI/DB2/CEIDB on stand-alone server, and can be found at the directory <profileDir>/databases/event/clusterName/dbscripts/db2 on cluster environment.
Here is how to Clean the events in CEI Database.
1) run the command
wsadmin.sh -f eventbucket.jacl -change -serverName server1
this command will switch the event bucket from 0 to 1 or 1 to 0 depending on which one is current event bucket.
To check the current event, use the following command
wsadmin.sh -f eventbucket.jacl -status -serverName server1
2) log on to the database server (here the database is DB2), then issue the command with the db2 instance owner.
fastpurge.sh CEIDB db2instance1 password=password
(3) run reorg.sh to reorganize the database
reorg.sh CEIDB db2instance1 password=password
(4) run runstats.sh to run statistics on database
runstats.sh CEIDB db2instance1 password=password
Note:
1) when you run eventbucket.jacl in cluster environment, you may see the following errors:
WASX7017E: Exception received while running
file "$WAS_HOME/util/event/eventpurge.jacl"; exception
information: javax.management.InstanceNotFoundException: *:*)
this bug will be fixed in WPS7.0.0.17 (http://www-01.ibm.com/support/docview.wss?uid=swg1PM21539). However, you can ask IBM to provide the updated com.ibm.events.client.jar, and then you will run it like the following command
wsadmin.sh -f eventbucket.jacl -status -clusterName SupportCluster
2) fastpurge.sh, reorg.sh and runstats.sh can be found at the directory <profileDir>/dbscripts/CEI/DB2/CEIDB on stand-alone server, and can be found at the directory <profileDir>/databases/event/clusterName/dbscripts/db2 on cluster environment.
Subscribe to:
Posts (Atom)