Uninstall WebSphere Portal

 

+
Search Tips   |   Advanced Search

 

1. Prepare to uninstall
2. Uninstall WebSphere Portal using the GUI
3. Uninstall with the console interface
4. Uninstall with a response file
5. Uninstall manually

 

Prepare to uninstall

1. Optional. Make a backup of WebSphere Portal configuration using xmlaccess.

   The following data is not saved by an XML configuration export and will be deleted if you remove the database:

   • User attributes that are stored in the database and not in LDAP
   • Credential data that is stored in the default vault implementation
   • Data that is used by the Document Manager

2. We can uninstall WebSphere Portal with WAS security enabled, or we can choose to disable security before uninstalling.

3. Decide whether to keep database information.

   If you are using a database other than IBM Cloudscape and you want to preserve the WebSphere Portal information in the database, we can leave the database as it is before uninstalling.

   To uninstall WebSphere Portal completely, we can remove the databases and database tables before uninstalling.

   If you choose to keep the database information, you will not be able to use it with subsequent installations of WebSphere Portal, although we can still access the information through the database software.

   To remove the WebSphere Portal information from the database:

   1. Stop WebSphere Portal.

   2. cd portal_server_root/config

   3. Remove the database tables.

      Some tables may remain in the DB2 database after the commands are run. These tables will be removed when the database itself is removed. See drop-database-tables-domain-jcr

      • To remove all database tables...

            ./WPSconfig.sh drop-database-tables-all \
                           -Drelease.DbPassword=password \
                           -Dcustomization.DbPassword=password \
                           -Dcommunity.DbPassword=password \
                           -Djcr.DbPassword=password \
                           -Dwmm.DbPassword=password \
                           -Dfeedback.DbPassword=password \
                           -Dlikeminds.DbPassword=password 

      • To remove individual domain tables,...

            WPSconfig.sh drop-database-tables-domain-release \
                         -Drelease.DbPassword=password 
            WPSconfig.sh drop-database-tables-domain-community \
                         -Dcommunity.DbPassword=password 
            WPSconfig.sh drop-database-tables-domain-customization \
                         -Dcustomization.DbPassword=password 
            WPSconfig.sh drop-database-tables-domain-wmm \
                         -Dwmm.DbPassword=password 
            WPSconfig.sh drop-database-tables-domain-feedback \
                         -Dfeedback.DbPassword=password 
            WPSconfig.sh drop-database-tables-domain-likeminds \
                         -Dlikeminds.DbPassword=password 
            WPSconfig.sh drop-database-tables-domain-jcr \
                         -Djcr.DbPassword=password 
            WPSconfig.sh remove-wcm-persistence-tables \
                         -Djcr.DbPassword=password 

      • Remove the databases by doing one of the following steps:
        • If you are running DB2 on a local machine,...

              ./WPSconfig.sh drop-database-wps \
                             -Drelease.DbPassword=password \
                             -Dcustomization.DbPassword=password \
                             -Dcommunity.DbPassword=password \
                             -Djcr.DbPassword=password 
              ./WPSconfig.sh drop-wmm-db \
                             -Dwmm.DbPassword=password 

        • If you are running DB2 on a remote machine or if you are running a different database program, use the utilities that are provided with the database software to remove the databases manually.

      • On DB2, uninstalling WebSphere Portal or Portal Personalization will not remove a tablespace that may have been created during the install. This is because the installer does not guarantee that it created this tablespace and therefore cannot guarantee that there are no other tables from the database in this tablespace. You may manually remove the tablespace by running the command:

        drop tablespace lmtablespace

   If you choose to leave the database information unchanged, we can always delete the WebSphere Portal databases and database tables later using the database software.

4. Remove references to the IBM Workplace Collaboration Services shared library...
   1. Start the WAS administrative server

   2. Run...

      cd portal_server_root/config
      ./WPSconfig.sh action-remove-lwp-shared-library -DPortalAdminPwd=password

5. Stop the WAS admin server and the WebSphere Portal application server.

6. Locate and delete the portalinstall.lockfile:

   /tmp/portalinstall.lockfile

 

Uninstalling WebSphere Portal using the graphical uninstallation program

The uninstallation program provides you with the option of uninstalling WebSphere Portal only or uninstalling both WebSphere Portal and WAS.

If the WebSphere Portal directory remains after uninstalling, delete the directory manually.

Multiple uninstallations are not supported. You should only perform one uninstallation at a time.

If...

<install_dir>/AppServer/java/bin

is missing or corrupted, the WebSphere Portal uninstallation GUI can be launched using a locally installed Java JRE (if one is present). We can check for a Java installation by typing java -version at a command line. Navigate to...

PortalServer/uninstall/package

and execute...

java -jar uninstall.jar

This will launch the uninstall GUI. If the uninstall GUI is not launched, proceed to the manual removal steps for WebSphere Portal.

• If WebSphere Portal installed WAS, WebSphere Portal will offer to uninstall WAS. All profiles, including WebSphere Portal, will be removed if you select to uninstall WAS.

• If you installed WebSphere Portal with an existing WAS, the uninstallation program will simply remove WebSphere Portal and its components without affecting WAS.

However, if you installed WebSphere Portal with an existing WAS, the uninstallation program will simply remove WebSphere Portal and its components without affecting WAS.

1. Launch the uninstallation program by doing one of the following steps:
   • Windows only: Select WebSphere Portal from the Add/Remove Programs window in the Control Panel.

   • Run...

        cd portal_server_root/uninstall    ./uninstall.sh 

2. Select the language for the uninstallation, and click OK. The welcome panel is displayed.

3. Select the component to uninstall and click Next.

   WebSphere Application Server uninstall program purposely leaves behind its root registry key in the Windows registry.

4. Click Next to display the confirmation panel.

5. Click Next to begin the uninstallation process. When the uninstallation program finishes, the program displays a confirmation panel.

6. Click Finish to close the uninstallation program.

7. Restart the machine. This is of particular importance if you intend to install WebSphere Portal again on the same machine.

 

Uninstalling with the console interface

The WebSphere Portal uninstallation program also provides a console interface, which enables you to perform an interactive uninstallation from a command prompt. To launch the uninstallation program from the console interface, complete the following steps:

Multiple uninstallations are not supported. You should only perform one uninstallation at a time.

1. Change directory to the WebSphere Portal uninstall directory:
   • portal_server_root/uninstall

2. Enter the following command:

   ./uninstall.sh -console

The console interface presents the same content as the graphical uninstallation program, only in a textual form. Indicate the selections by entering a number corresponding to the choice and proceed through the uninstallation by pressing Enter. For example, to select the language that you want to use for the uninstallation, you would see output similar to the following example:

C:\WebSphere\PortalServer\uninstall>uninstall -console Licensed Materials - Property of IBM IBM WebSphere Portal 6.0 (C) Copyright IBM Corp. 2001, 2006 All Rights Reserved. ------------------------------------------------------------------------ Select a language to be used for this wizard. [ ] 1 - Czech [X] 2 - English [ ] 3 - French [ ] 4 - German [ ] 5 - Greek [ ] 6 - Hungarian [ ] 7 - Italian [ ] 8 - Japanese [ ] 9 - Korean [ ] 10 - Polish [ ] 11 - Portuguese [ ] 12 - Portuguese (Brazil) [ ] 13 - Russian [ ] 14 - Simplified Chinese [ ] 15 - Spanish [ ] 16 - Traditional Chinese [ ] 17 - Turkish To select an item enter its number, or 0 when you are finished: [0]

 

Uninstalling with a response file

WebSphere Portal can also be uninstalled from a command line through the use of a response file. When uninstalling with a response file, the uninstallation program can retrieve information from the response file that would otherwise be entered during the uninstallation. Uninstalling from a command line with a response file is well suited to situations where the use of a graphical uninstallation program is impractical or undesirable. To run the uninstallation program with a response file, enter the following command from the directory portal_server_root/uninstall:

./uninstall.sh -options path_to_file/response_filename

...where path_to_file is the full path to the response file containing the values that you want to use during the uninstallation and response_file_name is the name of the file. Note that quotation marks are required around a Windows file name only if there are spaces in the directory path or file name. An example: for each operating system follows:

./uninstall.sh -options /usr/WebSphere/PortalServer/uninstallresponse.txt

A sample response file (uninstallresponse.txt) file is located in the root directory of the setup CD.

Uninstall response file parameters The following parameters can be specified in the response file or directly on the command line when issuing the uninstallation command.

Parameter default	Description
-silent	SILENT UNINSTALLATION CHOICE Specify this parameter if you want to uninstall WebSphere Portal silently. When uninstalling silently, the uninstallation program will not display any graphical interface panels or solicit input from the user. Note that if a required parameter is not specified in this response file, an error message will be logged. To use this response file but do not want to uninstall silently, comment the parameter out.
-W uninstallWas.choice="leave" -W uninstallWas.choice="uninstall"	UNINSTALL WEBSPHERE APPLICATION SERVER Indicate whether you want to leave WebSphere Application Server installed on the machine when you are uninstalling WebSphere Portal. Values: leave - Leave WebSphere Application Server on the machine. uninstall - Uninstall WebSphere Application Server when you uninstall WebSphere Portal.
-W wasIDPasswordUninstall.user=" " -W wasIDPasswordUninstall.password=" "	WEBSPHERE APPLICATION SERVER ADMINISTRATIVE USER AND PASSWORD Enter the user ID and password for the WebSphere Application Server administrator

 

Uninstalling manually

In most cases, you should follow one of the preceding sets of instructions to uninstall WebSphere Portal. But, if the uninstallation program is not present, or if an aborted installation did not create a complete and functional uninstallation program, we can uninstall WebSphere Portal manually.

The following instructions provide steps for uninstalling WebSphere Portal manually. A reference to uninstalling WebSphere Application Server is provided. Verify that you follow all instructions for uninstalling WebSphere Application Server before continuing with the remainder of the steps in this section. To uninstall WebSphere Portal manually:

1. Delete the directory tree for WebSphere Portal (PortalServer). The following table shows the default location if it is not otherwise specified during installation:

   Operating system	Location
   AIX	/usr/IBM /WebSphere/PortalServer
   Linux	/opt/IBM /WebSphere/PortalServer
   Solaris	/opt/IBM /WebSphere/PortalServer
   Windows	C:\Program Files\IBM \WebSphere\PortalServer
   HP-UX	/opt/IBM /WebSphere/PortalServer

2. Uninstall WebSphere Application Server.

   Depending on the state of WAS, you might need to uninstall WAS manually.

3. Uninstall IBM WebSphere Process Server.

   Depending on the state of WebSphere Process Server, you might need to uninstall IBM WebSphere Process Server manually.

4. Edit the vpd.properties file to remove the lines that are related to portal.

   Do not delete or rename the vpd.properties file because the InstallShield for Multiplatforms program uses it for other products that it installs.

   To edit the file, perform the following steps:

   1. Locate the vpd.properties file.

      find / -name vpd.properties

   2. Remove all lines that contain the string that represents the portal installation location.

   3. Save the vpd.properties file and close it.

5. Edit $HOME/.WASRegistry and remove the lines that are related to portal.

   Do not delete or rename $HOME/.WASRegistry because the InstallShield for Multiplatforms program uses it for other products that it installs.

   Remove all lines that contain the string that represents the portal installation location.

6. Remove entries that are related to WebSphere Portal from the native registry for the operating system. Use the native registry tool for the operating system to remove the following entries.

   • Windows:

     1. Read the Windows help system for information about using the Windows Registry Editor.

        The following instructions provide steps for editing the Windows registry. Before you proceed, note that the computer may not function properly if an incorrect entry or deletion is made. If this happens, we can restore the registry. See the Windows Help system for more information.

     2. Click...

        Start > Run

        ...and then type regedit to start the Windows Registry Editor.

     3. Delete all entries under the following key:

        HKEY_LOCAL_MACHINE -> SOFTWARE -> IBM -> WebSphere Portal Server

     4. Remove a Windows service from the Services list and registry by typing sc delete <service_name> at a command prompt. We can find <service_name> by going to...

        Control Panel | Administration Tools | Services

        ...and viewing the properties of the IBM WebSphere services left behind.

   • AIX :
     1. Search for the two portal entries in the AIX registry:
        • #lslpp -l | grep IBM WPS

          If there are no matching entries when using this command, no further action is required for this entry. The resulting list of packages are in the following format:

          IBM WPScore 6.0.0.0 COMMITTED ISMP installed entry 

        • #lslpp -l | grep WebSphere PortalProduct If there are no matching entries when using this command, no further action is required for this entry. The resulting list of packages are in the following format:

          WebSphere PortalProduct 6.0.0.0 COMMITTED ISMP installed entry 

     2. Remove the portal entries:

        • #geninstall –u IBM WPScore 

        • #geninstall –u WebSphere PortalProduct 

   • Linux :
     1. Search for two portal entries
        • #rpm -qa | grep IBM WPS

          If there are no matching entries when using this command, no further action is required for this entry. The resulting list of packages are in the following format:

          IBM WPScore 6.0-0
          

        • #rpm -qa | grep WebSphere PortalProduct If there are no matching entries when using this command, no further action is required for this entry. The resulting list of packages are in the following format:

          WebSphere PortalProduct-6.0.-0
          

     2. Remove the portal entries:

        • #rpm –e IBM WPScore-6.0-0 
          

        • #rpm –e WebSphere PortalProduct-6.0-0
          

   • Solaris :
     1. Search for two portal entries in the Solaris registry:
        • #pkginfo | grep IBM WPS

          If there are no matching entries when using this command, no further action is required for this entry. The resulting list of packages are in the following format:

          application ISIBM WPSc WebSphere Portal Server Component 

        • #pkginfo | grep WebSphere PortalProduct If there are no matching entries when using this command, no further action is required for this entry. The resulting list of packages are in the following format:

          application WebSphere PortalProduct WebSphere Portal Server Product 

     2. Change to the directory where the package information is registered:

        #cd /var/sadm/pkg 

     3. Remove WebSphere Portal packages using the following command:

        #pkgrm ISIBM WPSc WebSphere PortalProduct 

   • HP-UX
     1. Use HP-UX System Administration Manager (SAM) to remove packages.
        1. Start the SAM utility and verify that the DISPLAY and TERM environment variables are set properly.

        2. Click Software management.

        3. Click View installed software.

        4. Look for WebSphere Portal entries in the SD list.

        5. Close the SD list.

        6. Click Remove local host software.
           1. Find the following packages and remove:
              • IBM WPS

              • Portal

              • IBM PZN

              • pzn

              • IBM FB

              • IBM LM

              • e44a44c17bc4df37f9e9a6e911e59b42-5.1-0

           2. Examples to find installed Portal packages:
              • HP-UX : swlist | grep IBM WPS

        7. Click the instances in the SD Remove List that you would like to remove.

        8. Click Actions > Mark for remove.

        9. Click Actions > Remove.

        10. Click OK in the Remove analysis dialog box.

        11. Click Logs to display real-time removal of selected packages.

        12. Click Done when all packages are removed.

        13. Exit SAM.

     2. Search for the packages to verify their removal.
        • Type swlist | grep package name to show packages for WebSphere Portal.

        • Package names for WebSphere Portal are:
          • IBM WPS

          • Portal

          • Portal

          • IBM PZN

          • pzn

          • IBM FB

          • IBM LM

          • e44a44c17bc4df37f9e9a6e911e59b42-5.1-0

 

Related information

• Install on Windows and UNIX

 

---