IBM BS029ML - WebSphere Portal Server Self Help Manual page 74

Empty install
The empty portal installation scenario installs WebSphere Portal without the installation and
deployment of default portlets and without the pages that are normally created with the typical
and custom installation scenarios.
The empty portal installation is most often used when a transfer of the entire configuration, for
example, from test environment to production environment is required.The XML configuration
interface will allow you to export content from a test environment, for example, and import the
content into a production environment.
The key point to remember in the empty portal installation is that the install program actually
does removal of all WebSphere Portal resources, as noted in Example 3-2.
Example 3-2 Empty Portal Install trace output
(Jul 31, 2007 3:39:45 PM), MultiPlatform.install, com.ibm.wps.install.ExternalCommandAction,
msg2, Beginning install step: Removing all Portal resources
(Jul 31, 2007 3:39:45 PM), MultiPlatform.install, com.ibm.wps.install.ExternalCommandAction,
msg2, Executing command: cmd /c ""C:\IBM\WebSphere\PortalServer\config\WPSconfig.bat"
action-empty-portal -DPortalAdminPwd=PASSWORD_REMOVED -DWasPassword=PASSWORD_REMOVED
-DLTPAPassword=PASSWORD_REMOVED -DskipWTP=true"
(Jul 31, 2007 3:39:45 PM), MultiPlatform.install, com.ibm.wps.install.ExternalCommandAction,
msg2, Working directory:
Upon completion of this task, you need to confirm the task completes with a BUILD
SUCESSFUL message, as noted in Example 3-3.
Example 3-3 Empty Portal Install trace output
BUILD SUCCESSFUL
(Jul 31, 2007 3:47:07 PM), MultiPlatform.install,
com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: Total time: 7 minutes 12
seconds
(Jul 31, 2007 3:47:08 PM), MultiPlatform.install, com.ibm.wps.install.ExternalCommandAction,
msg2, Return code = 0
(Jul 31, 2007 3:47:08 PM), MultiPlatform.install, com.ibm.wps.install.ExternalCommandAction,
msg2, Executing command: completed
(Jul 31, 2007 3:47:08 PM), MultiPlatform.install, com.ibm.wps.install.ExternalCommandAction,
msg2, Completed install step: Removing all Portal resources
Attention: After installing an empty portal, expect messages indicating that no content can
be displayed or that some components are not yet configured. Adding content into the
portal will prevent these messages from rendering.
Figure 3-1 on page 61 shows what the user should see when accessing the Portal Server
directly after completing an empty portal installation scenario.
60
IBM WebSphere Portal V6 Self Help Guide