Install WebSphere Portal on i5/OS on the primary node

Install WebSphere Portal on i5/OS on the primary node

WebSphere Portal is installed as a single component, complete with an integrated database for storing information. This allows you to get WebSphere Portal up and running quickly for a proof of concept phase where you can immediately begin building and working with it. You can also expand your environment to include high availability failover, a more robust database, and LDAP-based authentication. Review the Supported hardware and software requirements for your operating system and ensure that all hardware and software matches the minimum product level before installing WebSphere Portal. Review Installation methods, options, and sources before installing to determine your installation source location and installation method.
To install WebSphere Portal and create a custom profile for the node that will be added to the cluster. If you already installed WebSphere Portal, you can skip to the last step to create the custom profile.

Type ping yourserver.yourcompany.com on a command line to verify that your fully qualified host name is properly configured.

Type ping localhost on a command line to verify that your network is properly configured.

Setup a static IP address on the server where you will install WebSphere Portal.

If you are installing with an existing WAS instance, ensure it is installed at the supported level and has the following features installed:

Besides ensuring that the existing WAS instance is at the supported level, you will also need to ensure that Apache Derby is installed at the supported level before installing WebSphere Portal. See WebSphere Portal detailed system requirements for supported levels.

Application Server
Administration

Scripted Administration
Administrative Console

Ant and Deployment Tools

Deploy Tool
Ant Utilities

Choose one of the following installation commands based on the installation method you want to use to install WebSphere Portal; see Installation Methods for more information:
Advance installation parameters: To customize your installation, you can add various parameters to your installation commands; for example, you can specify your port information. See Advanced installation parameters.
Restriction: When defining your installation path, the ONLY supported characters are ASCII letters [A-Z and a-z], numbers [0-9], slashes [/ or \, depending on your operating system], and the dash [-].

Option Description
GUI install400.batOptional attribute: WAS profiles and configurations are performed with the Classic 64-bit JVM by default. To install the portal profile with J9 32-bit JVM, add the -W enableClassicJVM.active=false attribute to your installation command.
Console mode remote install400.bat -console
Console mode local install.shOptional attribute: WAS profiles and configurations are performed with the Classic 64-bit JVM by default. To install the portal profile with J9 32-bit JVM, add the -W enableClassicJVM.active=false attribute to your installation command.
Silent install remote install400.bat -options "path_to_file\response_filename", where path_to_file is the full path to the response file and response_filename is the name of the file. A sample install response file (installresponse.txt) and a sample uninstall response file (uninstallresponse.txt) are located in the setup CD root directory.
Do not place the response file in a path that contains a space and do not put a space in the file name.
Silent install local install.sh -options "path_to_file/response_filename", where path_to_file is the full path to the response file and response_filename is the name of the file. A sample install response file (installresponse.txt) and a sample uninstall response file (uninstallresponse.txt) are located in the setup CD root directory.
Do not place the response file in a path that contains a space and do not put a space in the file name.

If the GUI or console mode installation program fails to detect ports for either WAS or WebSphere Portal, a warning message displays and the installer offers another chance to enter the values. If the silent installation fails to detect ports for either WAS or WebSphere Portal, the installer will exit.
Optional: After the WebSphere Portal installation completes successfully, run...
ConfigEngine.sh configure-express -DPortalAdminPwd=password -DWasPassword=password task, from profile_root/ConfigEngine, if you want to enable the sample IBM Lotus Web Content Management content, such as internet and intranet sample sites.
Restriction: Run...
configure-express
before configuring your database, user registry, context root, security, etc. If you ran any tasks other than the install task, do not run this task.

See http://publib.boulder.ibm.com/infocenter/wpexpdoc/v6r1m0/topic/com.ibm.wp.exp.doc/wcm/wcm_jumpstart_ovw.html for tutorials on how to use the sample content.
The sample content includes:

Creates a group called contentAuthors; members of this group are given privileges to create content in the sample Internet and intranet sites. Navigate to the Administration area and then click Access > Users and Groups.
Creates two new Web Content Management Libraries: "Internet Web Content 6.1.0" and "Intranet Web Content 6.1.0". Navigate to the Administration area and then click Portal Content > Web Content Libraries.
Adds a portlet filter and applies the filter to various portlets in the sample Internet and intranet sites. You can see the definition of the filter in the WAS Administration console and examining the custom resources under the Environment area.
Creates two new theme policies: InternetStyle and IntranetStyle. These styles are applied to sample Internet and intranet sites. Navigate to Theme Customizer and then select the style.
Creates several portlet clones of the Web Content Management rendering portlet. These portlet clones are used on sample Internet and intranet sites.
Creates two virtual portals with context roots of wps/portal/intranet and wps/portal/internet. These are the sample Internet and intranet sites. Go to http://yourserver:yourport/wps/portal/internet and http://yourserver:yourport/wps/portal/intranet to access them.
Creates several sample credential slots, including "Default slot for E-mail", "Default slot for Feeds", "Default slot for Miscellaneous", "Default slot for Web Clipping", and "Default slot for Web Content Management". Navigate to the Administration area and then click Access > Credential Vault > Manage System Vault Slots.
Modifies the portlet palette to include some new portlets. Click the Portlets link to see the portlet palette.

Optional: If you ran the configure-express task, the owner of the items in the Web content libraries containing the Internet and Intranet Site Template content will be listed as uid=xyzadmin,o=defaultWIMFileBasedRealm.
To update the owner information for these items to correspond to the portal administrator ID, complete the following steps:

Edit...
profile_root/PortalServer/wcm/shared/app/config/wcmservices/MemberFixerModule.properties

Add the following line to the file:

uid=xyzadmin,o=defaultWIMFileBasedRealm -> portal_admin_DN
Replace portal_admin_DN with the distinguished name of the portal administrator.
Save changes and close the file.

Run...
ConfigEngine.sh action-express-memberfixer -DPortalAdminPwd=password -DWasPassword=password task, located in profile_root/ConfigEngine.

If installed WebSphere Portal on an i5/OS v6.1 system, install the MF45016 fix; see Fix Central to access the fix.Set the following two cache properties under the WP_CacheManagerService resource environment provider in the admin console; see Set service configuration properties for information:

cacheglobal.softref=true
cacheglobal.lifetime=1200

Parent topic:
Prepare the primary node on i5/OS

Next topic:
Set up a remote database

Related concepts

Installation methods
IBM Support Assistant Lite for WebSphere Portal

Related reference

Advanced installation parameters

Option	Description
GUI	install400.batOptional attribute: WAS profiles and configurations are performed with the Classic 64-bit JVM by default. To install the portal profile with J9 32-bit JVM, add the -W enableClassicJVM.active=false attribute to your installation command.
Console mode remote	install400.bat -console
Console mode local	install.shOptional attribute: WAS profiles and configurations are performed with the Classic 64-bit JVM by default. To install the portal profile with J9 32-bit JVM, add the -W enableClassicJVM.active=false attribute to your installation command.
Silent install remote	install400.bat -options "path_to_file\response_filename", where path_to_file is the full path to the response file and response_filename is the name of the file. A sample install response file (installresponse.txt) and a sample uninstall response file (uninstallresponse.txt) are located in the setup CD root directory. Do not place the response file in a path that contains a space and do not put a space in the file name.
Silent install local	install.sh -options "path_to_file/response_filename", where path_to_file is the full path to the response file and response_filename is the name of the file. A sample install response file (installresponse.txt) and a sample uninstall response file (uninstallresponse.txt) are located in the setup CD root directory. Do not place the response file in a path that contains a space and do not put a space in the file name.