Uninstall options

Similar to install WebSphere Portal has provides you with three options for which method you want to use for unistalling portal.

• Graphical: The Graphical is default option that you get if you execute ./uninstall.sh or uninstall.bat command in the portal_server/uninstall director. It will open a Wizard and ask you couple of questions about what is user name and password of portal administrator and do you also want to uninstall websphere portal.


• Console: If your using a system where Graphical Uninstall/install is not supported then your second option is to use Console by executing ./uninstall.sh -console in this case portal will ask you same question as that of graphical unistall but on command console.


• Silent Install If your Operating system does not support Graphical UI then you can use the silent option. In this case you copy the uninstallresponse.txt file from the IL-Setup or W-Setup directory set appropriate properties and execute ./uninstall.sh -options <path_to_setup>/IL-Setup/unistallresponse.txt

The CentOS vmware that i use for experiments does not support Graphical UI so i had to uninstall using the silent option. This is how my uninstallresponse.txt looks like.

################################################################################
#
# Uninstall response file for IBM WebSphere Portal 6.1.0.1
#
# Follow the comments to use the response file and understand the various
# options. You must carefully complete or change the various values. If the
# values are not completed properly, the install may be unsuccessful.
#
# IMPORTANT: ALL VALUES MUST BE ENCLOSED IN DOUBLE QUOTES ( "" ).
#
# To use this file specify the command line option
# "-options path/to/uninstallresponse.txt". For example,
# uninstall.bat -options path\to\uninstallresponse.txt, or
# uninstall.sh -options path/to/uninstallresponse.txt
#
################################################################################


################################################################################
#
# UNINSTALLATION CHOICE
#
# Description: This line specifies that the uninstallation
# will be done in silent mode. If you wish to use this response
# response file in interactive mode, just comment out or delete
# this line.
#
################################################################################

-silent

################################################################################
#
# UNINSTALL WEBSPHERE APPLICATION CHOICE
#
# Description: This property enables you to leave the WebSphere
# Application Server installation on the machine when
# uninstalling WebSphere Portal.
#
# Legal values are: leave - leave WebSphere Application Server
# on the machine
#
# uninstall - uninstall WebSphere Application Server
#
# The uninstall option is available only if you installed the WebSphere
# Application Server using the WebSphere Portal installer.
#
################################################################################

-W uninstallWas.choice="uninstall"

################################################################################
#
# WEBSPHERE APPLICATION SERVER ADMINISTRATIVE USER AND PASSWORD
#
# Enter the user ID and password for the Websphere Application Server
# administrator for the profile you are removing. These properties are
# required when uninstalling with WebSphere security enabled.
#
################################################################################
-W wasIdPasswordUninstall.user="wasadmin"
-W wasIdPasswordUninstall.password="wasadmin"



Once you start the uninstall process it will display name of the log file where uninstall process is writing long in my case it is /tmp/wpuninstalllog.txt file. You can look inside this file in case of problems.

Both during the install and uninstall process the installer creates portalinstall.lock file to make sure that there is only one instance of installer/uninstaller program is running at a time. If your install or uninstall process is throwing other instance of installer already in progress check if this file is there in either /tmp folder in case of Linux or in C:\Documents and Settings\Administrator\Local Settings\Temp\portalinstall.lockfile folder in case of Windows. Delete this file manually and then start the install/uninstall program.

Portal Directory Structure

When you install portal it will create 3 directories AppServer, PortalServer and wp_profile. The AppServer directory is used for WAS 6.1.

This is how the PortalServer directory looks like. This directory is ready only.

 of C:\WebSphere\PortalServer
03/10/2009  07:18 AM    <DIR>          .
03/10/2009  07:18 AM    <DIR>          ..
02/27/2009  12:07 PM    <DIR>          ap
02/27/2009  12:07 PM    <DIR>          base
03/06/2009  08:59 AM    <DIR>          bin
02/27/2009  12:07 PM    <DIR>          bp
02/27/2009  12:07 PM    <DIR>          cmapi
03/10/2009  10:01 AM             7,072 CompositeApp.xml
02/27/2009  12:07 PM    <DIR>          doc
02/27/2009  12:08 PM    <DIR>          ext
02/27/2009  11:23 AM    <DIR>          firstSteps
03/12/2009  07:27 AM    <DIR>          installableApps
02/27/2009  12:08 PM    <DIR>          installer
02/27/2009  12:08 PM    <DIR>          jcr
02/27/2009  11:23 AM    <DIR>          license
02/27/2009  03:06 PM    <DIR>          log (Install Time logs only)
02/27/2009  12:08 PM    <DIR>          lwo
02/27/2009  12:08 PM    <DIR>          lwp04.infra
03/10/2009  10:01 AM             4,130 Mail.xml
02/27/2009  01:08 PM    <DIR>          migration
02/27/2009  12:24 PM    <DIR>          package
02/27/2009  12:08 PM    <DIR>          pcc.api
02/27/2009  12:08 PM    <DIR>          pcc.impl
02/27/2009  12:08 PM    <DIR>          prereq
02/27/2009  12:08 PM    <DIR>          prereqs.infra
02/27/2009  12:21 PM    <DIR>          pzn
02/27/2009  12:08 PM    <DIR>          pzn.ext
03/10/2009  07:18 AM    <DIR>          rational
02/27/2009  11:24 AM    <DIR>          reguninstall
02/27/2009  12:08 PM    <DIR>          search
02/27/2009  12:21 PM    <DIR>          shared
02/27/2009  12:08 PM    <DIR>          theme
03/10/2009  10:01 AM            90,115 theme.xml
02/27/2009  12:08 PM    <DIR>          ui
02/27/2009  11:23 AM    <DIR>          uninstall
03/06/2009  08:58 AM    <DIR>          version
02/27/2009  02:34 PM               273 wps.properties

Please note some important points

• The log folder contains only install time logs. Runtime logs are moved to profile directory


• Structure of shared lib is changed now shared/app directory has only few .jar fiels instead it has shared.app.jar which is empty .jar file. BUt if you look at the META-INF.MF of shared.app.jar it includes quite few .jar files
  

  
  Ant-Version: Apache Ant 1.6.5
  Created-By: 2.3 (IBM Corporation)
  Class-Path: ../../base/wp.resolver/wp.resolver.model.impl/shared/app/w
   p.resolver.model.impl.jar ../../lwp04.infra/sync.infra/syncmlbase/sha
   red/app/lotusworkplacelib/lwpSyncmlBase.jar ../../ext/common.ext/wpad
   apter/common/shared/app/lwp.portal.adapter.jar ../../base/wp.ai.rt.im
   pl/modification/shared/app/wp.ai.rt.impl.modification.jar ../../base/
   wp.resolver/wp.resolver.friendly.impl/shared/app/wp.resolver.friendly
   .impl.jar ../../base/wp.tpl.impl/shared/app/wp.tpl.impl.jar ../../bas
   e/wp.pe.api.standard/shared/app/wp.pe.api.standard.jar ../../base/wp.
   services.url/shared/app/wp.services.url.jar ../../cmapi/wp.contentapi
   .servlets.jcr.cm/shared/app/contentLib/wp.contentapi.servlets.jcr
  //Includes few more .jar files
  

  
  


• The shared/ext has very few .jar files and it contains shared.ext.jar file which is empty jar but it uses the META-INF.MF to add quite few .jar files to the class path.
  

  
  Manifest-Version: 1.0
  Ant-Version: Apache Ant 1.6.5
  Created-By: 2.3 (IBM Corporation)
  Class-Path: ../../prereqs.infra/prereq.eclipse/shared/ext/eclipse-runt
   ime.jar ../../prereqs.infra/prereq.eclipse/shared/ext/org.eclipse.cor
   e.resources_3.1.0.jar ../../prereqs.infra/prereq.eclipse/shared/ext/o
   rg.eclipse.osgi_3.1.0.jar ../../base/wp.base/shared/ext/wp.base.ext.j
   ar ../../base/wp.base/shared/ext/wp.jndi.jar ../../prereq/prereq.dhar
   ma/shared/ext/html-parser-1.4.4.jar ../../base/wp.collaborator/shared
   /ext/wp.collaborator.jar ../../base/wp.propertybroker.common/shared/e
   xt/wsdl4jpbext.jar ../../prereqs.infra/prereq.jdom_1.0/shared/ext/jdo
   m.jar
  

  
  


• you will see quite few new directories like base, ui, ap, base, search. Each of these directories is used to group set of related jars. Ex. ui directory has .jars related to theme, tags, struts, property broker, wcl(widget component library). If you drill further you will notice that each of these .jar file has similar structures the shared/app would have .jar file the config folder would have configuration for that .jar the .html and .xml file would have i18n messages. The shared.app.jar has references to these .jar files
  
  

Portal installation default configuration

The portal server needs two things one is database to hold portal configuration such as page, portlet,.. information. In addition to this portal server also requires a User Repository

In order to simplify the installation portal server will install following default configuration

Portal Server:

When you install the Portal Server, installer will also install Apache Derby database and the portal related data will get stored in the Apache Derby database.

Virtual Member manager is used for storing the user information. With basic install the user repository would be stored on the local file system.

Portal Express:

When you install the Portal Express, installer will also install DB2 V9.1 database and the portal related data will get stored in this dedicated instance of DB2 V9.1 database.

Virtual Member manager is used for storing the user information. With basic install the user repository would be stored on the local file system.


Once the portal server is installed you can use the Configuration program to move the database from local to production quality database such as Oracle, DB2.

You can also move the User Repository from Local File System based repository to LDAP repository.

Portal Editions

The WebSphere Portal product family has following offerings.

• IBM WebSphere Portal Server software—provides foundational WebSphere Portal services and serves as the cornerstone of all WebSphere Portal offerings.
  


• IBM WebSphere Portal Enable software—includes all the features of WebSphere Portal Server software plus significant added content management and workflow functionality to support core business applications and processes.


• IBM WebSphere Portal Extend software—includes the capabilities of WebSphere Portal Enable software plus more robust collaboration and electronic forms capabilities.


• IBM WebSphere Portal Express software—provides a comprehensive set of out-of-the-box and ready-to-use portal,document management and collaboration features designed
  for small and midsize businesses and departments within larger organizations.


• IBM WebSphere Portal Enable for z/OS software—pairs the enterprise portal leadership of WebSphere Portal software with the hallmark reliability of the IBM z/OS® platform.

Empty Portal

Empty portal means that no portlets have been installed and no pages have been created on the portal. You must have empty portal if you want to move content from staging to production using the release builder/ xmlaccess combination.

In order for configuration transfer to work for the very first time the target server must be empty very first time. You will create full export of the source and import it on target, doing this will make sure that the unique id of the portlets, pages match between source and target. After initial migration whenever you want to move content from source to target you can take the difference and import it in target

You dont have an option to install empty portal instead your suppose to install Admin portal first configure it and then run the empty-portal config task. Configuring empty portal is not allowed so fully configure portal before configuring it.

You can empty both Portal Server and express edition.

You have the option to turn a full Portal installation into an empty portal by running the ‘empty-portal' task.

< wp_profile_root >/ ConfigEngine/ConfigEngine.sh empty-portal 

Important: When using virtual portals as production servers, you must create the virtual portals using the create-virtual-portal task; see Virtual portals reference for information. If you do not create the virtual portals using this task, the virtual portal instance is not empty and cannot be used to import a fresh release as a baseline.

Installation Options

When your installing Websphere Portal using the Wizard or console, the wizard will ask you, whether you want to install full portal or administrative portal. Administration is more common choice. Even if you are using silent install option you will have to set the setupTypePanel.selectedSetupTypeId value to indicate if it is full or administration install.

• Full: The full option includes all of the out-of-box portlets and administration portlet. Use this option only if you want to install some of the features such as COmposite applicationss, common mail portlets.
  
  
  
  • Full set of applications and features.
  
  
  • Targeted for evaluators, customers who are interested in the OOB apps.
  
  
  
  



• Administrations: If your setting up a development environment or your not planning to use the out of box features such as composite applications, common mails choose admin option. Once you install portal using admin option you can add components such as composite application afterwards when you need it. If you choose admin option the installer program will install all admin portlets and create WPS administration related pages it will also create welcome pages.
  
  
  
  • Minimal level of fully functional Portal.
  
  
  • Admin content, Welcome page, self-provisioning pages.
  
  
  • Better runtime performance (less apps).
  
  
  • Targeted for building stack solutions.
  
  
  
  

Important Note Please note that if your installing Portal Express edition then you dont have option of installing either full or admin portals. It always install full portal.