Install WebSphere Portal
Before you begin
- Plan for WebSphere Portal
- Prepare the operating system
- Choose an installation source
- About the installation program
Installation options
- WebSphere Portal Quick Installation Scenario
- Install WebSphere Portal with an existing instance of WAS
- Install Websphere Portal into a cluster
- Install coexisting WebSphere Portal products on the same machine
- Install for development
- Advanced installation options
When running the WebSphere Process Server installation manually from CD *-2, users should run the install.bat or install.sh script instead of running the executable. This will automatically deselect WebSphere Process Server Samples and Javadocs from being installed. The WebSphere Process Server installation fails if you try to install these components.
Name limitations
Because Windows limits the maximum path length to 256 characters, the name of the WAR file must be less than approximately 21 characters. Installing a WAR file with a name that is more than 21 characters can result in longer pathnames which makes the files not accessible anymore resulting in FileNotFoundExceptions.
The Portal tries to truncate or rename long names before it deploys the WAR file into Application Server. However it cannot always circumvent the pathname to exceed the limit. To correct this error, modify the file name to be less than 21 characters. IBM recommends that you install WebSphere products into the root directory to keep the common part of pathname short. For example, install to...
c:\WebSphere...instead of...
c:\Program Files\WebSphere
Installation Notes
Set ulimit -n 10240 before installing on all Linux and UNIX platforms.
After installation, to determine the server ports, refer to the SystemOut.log file to determine the server port. In the WPS/log/SystemOut.log search for the entry similar to:
[3/14/06 18:55:16:031 CET] 0000000a TCPChannel A TCPC0001I: TCP Channel TCP_1 is listening on host * (IPv4) port 9074.[3/14/06 18:55:16:047 CET] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain WCInboundAdmin. The 'WCInboundAdmin' transport channel points to the admin console port
The port number is displayed on top of the channel name.
Next steps
- Explore WebSphere Portal
- Transfer data to another database with greater capability.
- Use an LDAP directory as the user registry
- Add collaboration function