Preparing to uninstall a single server on IBM i

Before uninstalling IBM® WebSphere® Portal, you must prepare your system; for example, adding passwords to the properties files and keeping or discarding database information.

1. Optional: Make a backup of the WebSphere Portal configuration using the XML Configuration Interface.
   Important: The following information is not backed up and is deleted if you delete the database:

   • User attributes that are stored in the database and not in the user registry
   • Credential data that is stored in the default vault implementation
2. Decide whether to keep your database as is to preserve WebSphere Portal information or complete the following steps to remove the information from the database:
   Note: If you choose to keep the database information, you cannot use it with subsequent WebSphere Portal installations although you can still access the information through your database software. Also, if you keep the information, you can always delete the WebSphere Portal databases and database tables later using your database software.
   1. Run the stopServer WebSphere_Portal -username admin_userid -password admin_password from the wp_profile_root/bin directory.
   2. Run the stopServer cw_profile -profileName cw_profile -username admin_userid -password admin_password from the AppServer_root/bin directory.
   3. Choose one of the following options to delete the database information:

      Table 1. Options to delete the database information.

      If your database is a...	Then complete the following steps:
      Local IBM DB2® for i	Run the ConfigEngine.sh remove-schema -DWasPassword=password -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password task from the wp_profile_root/ConfigEngine directory to remove all database tables.
      Remote IBM DB2 for i	Use a 5250 PC session to log on to the system where the remote database exists. Type wrklib prefix* on the command line to display a list of all libraries created for the remote database, where prefix is the prefix for your database name. Type 4 in the Opt field for each library name that you want to delete and then press Enter.

3. Verify that there are no other installations or uninstallations running.