This chapter discusses:
Section 2.2, "Preparing the Microsoft Windows Operating System"
Section 2.3, "Retrieving WebSphere Portal 7.0 Software from Oracle JD Edwards Update Center"
The following sections discuss the prerequisites for installing the Websphere portal server.
Before you install Portal v7.0, you must first install WebSphere Application Server 7.0 and the latest supported fix pack listed in the JD Edwards EnterpriseOne HTML Web Server Minimum Technical Requirements (MTRs). These MTRs are available on My Oracle Support in document ID 705409.1 and can be accessed at this link:
https://metalink3.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=705409.1
To install WebSphere Application Server 7.0, refer to Chapter 3: Installing and Configuring WebSphere Application Server 7.0 in the JD Edwards EnterpriseOne HTML Web Server Reference Guide for Microsoft Windows-Based Systems and WebSphere Application Server 7.0. This document is available on My Oracle Support in document ID 705495.1 and can be accessed at this link:
https://metalink3-dr.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=705495.1
If you are using same single physical machine for both the Portal and the HTML Server, you cannot install the JD Edwards EnterpriseOne HTML Web Server (also called JAS) to the same profile as that of Portal. By default, WebSphere Portal v7.0 creates a separate profile called wp_profile.
IBM product documentation for Portal v7.0:
http://www.ibm.com/developerworks/websphere/zones/portal/proddoc/index.html
IBM WebSphere Application Server 7.0 Info Center:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp
IBM Portal v7.0 Hardware and Software Requirements:
Use these steps to prepare your Microsoft Windows operating system for the installation of Portal 7.0 components:
Check that the system logon user ID you will use during installation has the following permissions and rights:
The user ID must already exist prior to installation.
The user ID must belong to the Administrators group.
Perform these steps to determine if a user account is a member of the Administrators group:
Click Start > Programs > Administrative Tools > Computer Management.
Expand Local Users and Groups and select Groups.
Open the Administrators group to see what members belong to it.
Add the user to the Administrators group if necessary.
Consider these recommendations when installing to avoid excessively long path names:
Specify short cell and node names; do not use names longer than 5 characters. For example, you might use scell instead of stonemillNode01cell.
Ensure there are no special characters in the node and/or cell names as they are known to cause problems during install.
Name WAR files with less than 21 characters. If necessary, modify the file name before installing.
Refer to the following tech note for additional information: WKSP0016E - 'Filename is too long error' in Microsoft Windows..
Note:
If you exceed the 259 maximum character length, you may receive one of these error messages during configuration or in the wpinstalllog.txt file: · The input line is too long. · The syntax of the command is incorrect. · The filename is too long.If you are installing on a server with a firewall enabled, disable the firewall before installing. If you do not disable the firewall and the installation program detects it, a warning message might be displayed during the installation.
To retrieve WebSphere Portal 7.0 Software from the Oracle JD Edwards Update Center:
Log on to EnterpriseOne Update Center:
Select “EnterpriseOne Technology Foundation” type.
Select the platform.
Select and download the following files for WebSphere Portal 7.0 installation (The files are based on platform type):
Name | Description |
---|---|
IBM_WPS_7.0_Install_Guide_Win_1-2.par | WebSphere Portal 7.0 Install and Quick Start Guide 1/2 |
IBM_WPS_7.0_Install_Guide_Win_2-2.par | WebSphere Portal 7.0 Install and Quick Start Guide 2/2 |
Note:
Uses the regular Microsoft Windows unzip command to extract the files.Unzip the .par files that you downloaded from the Update Center to a temporary location. When unzipped, they files will appear as follows:
wps70-windows.zip.001
wps70-windows.zip.002
Extracting WebSphere Portal 7.0 Software
To extract WebSphere Portal 7.0 Software:
Move both wps70-windows.zip* files to a “WPS70” folder.
Extract wps70-windows.zip.001 using the 7zip product.
The unzip process will process both files.
To begin the installation
From either the Setup CD or directory, you can use various methods to launch the installer, as shown in this table (it is recommended to use Graphical user interface for installation):
Installation Method | Command and Description |
---|---|
Graphical user interface | install |
Console mode | install -console |
Silent install | install -options "path_to_file\response_filename"
where path_to_file is the full path to the response file, and where 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 root directory of the Setup CD. Important: Do not place the response file in a path that contains a space and do not put a space in the file name. |
Note:
If the installation program does not detect a WebSphere Application Server instance that you know exists, exit the installation program and re-run it using command line options to specify the WebSphere Application Server instance location.For example:
install -W was.undetectedWas="\my\WAS\location"
Upon execution, by default the installer creates a separate profile called wp_profile. This profile is used to host the Portal contents. Therefore, you should not install Portal into an existing profile with other applications installed.
On the installation type screen, select IBM WebSphere Portal Extend. Click Next button.
Accept the license terms and Click the Next button.
Select Base as the install type and click Next button.
Select "To existing WebSphere application server installation" and click Next button.
The installer detects your WebSphere Application Server 7.0 installation. For example:
X:\IBM7\WebSphere\AppServer
On the WAS location screen, choose the WAS installation into which you want to install the Portal.
If you have multiple installations of WebSphere, the program may detect more than one WebSphere location.
With the desired location selected, click the Next button. This is the directory where the wp_profile and PortalServer directories will be created.
On the instance properties screen, complete these fields:
Field | Description |
---|---|
Node name | Enter a unique Node name for this installation of WebSphere Portal and Lotus Web Content Management.
The Node name is used to identify the server. Having a unique node name is important when configuring a federated, production environment. Do not use names that contain special characters (i.e _ underscore..etc.). |
Host name | Enter the fully-qualified Host name for this installation of WebSphere Portal and Lotus Web Content Management. The Host name must include the fully-qualified domain name (for example, hostname.example.com). Do not use a local host or a loopback address |
Click the Next button.
On the security screen for the administration user ID and password, WebSphere Portal enables security by default. It is not possible and/or recommended to disable security. Complete these fields:
Field | Description |
---|---|
Administrative User ID | Enter the user ID that you assign for the Portal administrator. For example:
wpsadmin This user is used for Stopping Services after the Portal installation is completed. It is not related to any user IDs used to access the operating system. |
Administrative Password | Enter the password for the Administrative User defined in the previous field. |
Confirm Password | Confirm the password you entered in the previous field. |
Select the checkbox to configure the WebSphere_Portal server to run as a windows service and Click the Next button.
On the summary screen, review your selections for the Portal installation.
Click the Next button to start the installation process.
As the installer begins, it creates a default portal profile called wp_profile.
When the installation completes, locate and open the wps.properties file from this directory:
X:\IBM\WebSphere\PortalServer
Verify the version= parameter in the wps.properties file specifies the updated Portal version: 7.0.0.0
After the installation completes successfully following screen will be displayed. Uncheck both the boxes and click Finish to complete the installation. Note the WebSphere Portal and Web Content Management and WebSphere Application Server URL's from the screen.
Accessing the WPS and WCM link brings up the following screen:
Clicking on Login brings up the login portlet. Login with the credentials provided during the installation (i.e with wpsadmin user credentials).
After successful login the Administrative page is displayed as shown above.
This completes the installation of WebSphere Portal 7.