Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Uninstall Portal Express v6 on i5/OS
Overview
This section describes how to uninstall WebSphere Portal Express for i5/OS on a WAS profile.
WebSphere Portal Express provides uninstallation programs or tasks. You must have at least one fully installed WAS profile and WebSphere Portal Express fully installed on i5/OS in order to run these tasks.
These tasks must be run:
- locally on an i5/OS system
- sequentially
To uninstall, follow this procedure...
- Prepare to uninstall
- Uninstall the WAS profile and the WebSphere Portal Express installed on it
- Uninstall WebSphere Portal Express
- Uninstall WMQ Series Components
- Prepare to uninstall:
You can make a backup of the WebSphere Portal Express configuration using xmlaccess. The following data is not saved by an XML configuration export and will be deleted when 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
If you are running WebSphere Portal Express with security enabled, you can uninstall without affecting your security setting, or you can choose to disable security before uninstalling. To disable security before continuing uninstallation...
- Use a text editor to open each properties file, located in the UserData directory path...
portal_server_root/config- Ensure that the following properties have the appropriate values for your setup. The following properties must be updated to reflect your original settings before disabling security. If this is not done the administrator will not have administrative rights.For example, the WasUserid:
- The value must be lower case
- The default value after installation and before enabling security is: ReplaceWithYourWASUserID
- The recommended value when enabling security with LDAP is:
- IBM® Tivoli® Directory Server: uid=wpsbind,cn=users,dc=example,dc=com
- Custom User Registry (CUR): wpsbind
- The value change back to before disabling security is:
- Tivoli Directory Server: uid=wpsbind,cn=users,dc=example,dc=com
- Custom User Registry (CUR): wpsbind
Some values, shown here in italics, might need to be modified to your specific environment. See Configuration properties reference for a complete properties reference, including default values.
Section of wpconfig.properties file: WAS configuration properties
Property Value WasUserid The user ID for WAS security authentication. LDAP
For LDAP configuration this value should not contain spaces.
Make sure to type the value in lower case, regardless of the case used in the distinguished name (DN).
Recommendeds when using LDAP security:
- Custom User Registry (CUR): wpsbind
- Tivoli Directory Server: uid=wpsbind,cn=users,dc=example,dc=com
Default none
WasPassword The password for WAS security authentication. Recommended Set this value according to a environment.
Default none
Section of wpconfig.properties file: Portal configuration
Property Value PortalAdminId The fully qualified name of the WebSphere Portal Express administrator.
Before disabling security, this value should be set to the original value that is used when installing WebSphere Portal Express. Recommended uid=portaladminid,o=default organization
Default: none
PortalAdminPwd The password for the WebSphere Portal Express administrator, as defined in the PortalAdminId property.
Before disabling security, this value should be set to the original value that is used when installing WebSphere Portal Express. Recommended Set this value according to a environment.
Default: none
PortalAdminGroupId The group ID for the group to which the WebSphere Portal Express administrator belongs.
Before disabling security, this value should be set to the original value that is used when installing WebSphere Portal Express. Recommended cn=wpsadmins,o=default organization
Default: none
Section of wpconfig_dbdomain.properties file: Database properties
Depending on which database domain has to be configured, dbdomain may need to be replaced by:
- release
- customization
- community
- jcr (DB2 Content Manager Runtime Edition)
- wmm
- feedback
- likeminds
Property Value dbdomain.DbUser The user ID for the database administrator. Recommended Set this value according to a environment.
Default per database domain:
- db2admin
- Personalization and Feedback: wcmdbadm
- Likeminds: lmadmin
dbdomain.DbPassword The password for the database administrator.
Recommended: Set this value according to a environment.
Default ReplaceWithYourDbAdminPwd
- Perform this task only if you are using LDAP with a LookAside database. Set the LookAside property (in the LDAP properties section) to false.
- Save and close any properties file you edited.
- Open a command prompt and change to the UserData directory path:
portal_server_root/config- Enter the following command:
WPSconfig.sh -profileName wp_profile disable-security -DPortalAdminPwd=password -DDbPassword=passwordIf you choose to leave security enabled, you can always disable it later using the WAS administrative console.
- Remove references to the Workplace Collaboration Services shared library. Complete the following steps:
- Open a command prompt and change to the UserData directory path portal_server_root/config
- Ensure that the WAS administrative server is running.
- Enter the following command:
WPSconfig.sh -profileName wp_profile action-remove-lwp-shared-library -DPortalAdminPwd=password- Stop the WAS server if you are running with security enabled.
Follow the command that specifies the appropriate administrator user ID and password, which are needed with security enabled.
- Run the portal removal tool to remove:...
- DB2 for i5/OS database libraries for WebSphere Portal Express
- DB2 database's administrator user ID (wpdb2insx)
- WebSphere Portal Express server installed on the WAS profile
- WAS profile (wp_profilex) created by the portal installation program
This profile removal task must be run before continuing with the next step of fully uninstalling the WebSphere Portal Express server code.
First open an OS/400 command prompt and start the Qshell Interpreter by typing STRQSH.
Remove the database libraries and user ID, the portal code and profile...
- For WebSphere Portal Express installed on WAS Base or Express...
portal_server_root/uninstall/rmvwpprofile.sh -profileName wp_profile -username user -password password- For WebSphere Portal Express installed on WAS ND...
portal_server_root/uninstall/rmvwpprofile.sh -profileName wp_profile -wasfamily nd -username user -password password...where portal_server_root is the ProdData directory path.
If this removal task completes with success (without any errors), the message
INSTCONFSUCCESS...will be displayed, and the command will have removed an entire directory, for example...
/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/wp_profileAll files are removed, excepting the temp files, which includes the log files.
If this removal task completes with some errors, the message
INSTCONFPARTIALSUCCESSwill be displayed along with a log file name. Review the log file, correct the error situation, and rerun the removal task.
If you have more than one profile created, run this task for each profile you wish to remove. Click here to return to the beginning of this step.
If the profile (wp_profile) you just tried to delete still exists after running the removal task, you should manually delete the folder wp_profile for your WAS edition in the UserData portal_server_root directory path. Also, depending on the state of WAS, you might need to uninstall WAS manually.
Refer to the WAS documentation for details.
Proceed to uninstalling the WebSphere Portal Express server code.
- If this portal server code uninstall task is run without first removing the WAS profile in the previous step, the WebSphere Portal Express server is still viable. Don't run this task unless you have first removed the WAS profile. You can uninstall the WebSphere Portal Express server code interactively, in silent mode or with a response file.
Navigate to the ProdData directory path...
portal_server_root/uninstall/...and for an interactive uninstall type:
uninstall.sh...or run a silent uninstall with no further input required by typing this command instead...
uninstall.sh -silentor run an uninstall with a response file by typing this command, and the uninstallation program will retrieve information from the response file rather than requiring input during the uninstallation:
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.
The following parameter 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 Express 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.
If you want to use this response file but do not want to uninstall silently, comment the parameter out.
During an interactive uninstall follow the system prompts until the uninstall task is complete, indicating a selection by entering a number corresponding to your choice and then pressing Enter:
- At the first prompt choose a language. For example, to choose English type 0 (zero). Choose OK. The welcome panel is displayed.
- As the task proceeds, a prompt will ask you to type 1 (one) for Next.
- A final prompt will ask you to type 3 (three) for Finish.
- Uninstall WMQ Series Components
After uninstalling WebSphere Portal Express, MQ Series components may still be installed on your system. Do not uninstall these components if they are being used by other applications on your system.
Parent topic:
Install on i5/OS