InstallPortal with WAS security temporarily disabled

 

---

 

Before you begin

1. Prepare the operating system

2. Choose an installation source

3. Plan for WebSphere Portal

Figure 1. WebSphere Portal with default components installed

 

Install WebSphere Portal

Although WebSphere Portal can be installed while WebSphere Application Server security is enabled, there is some required configuration for WebSphere Portal that cannot be automatically performed when security is active. The instructions in this section describe how to install WebSphere Application Server by temporarily disabling WebSphere Application Server security. If it is essential that security remain active at all times in your environment, you can install WebSphere Portal and perform the configuration manually by using the instructions in the section Install WebSphere Portal with security enabled.

Java 2 security note: WebSphere Portal does not support Java 2 security in WebSphere Application Server. If you are running WebSphere Application Server with Java 2 security, disable it before installing and running WebSphere Portal.

To install WebSphere Portal by temporarily disabling WebSphere Application Server security, follow these instructions.

Ensure that the installed WebSphere Application Server is at the supported level before continuing. Refer to Supported hardware and software for more information.

Linux installation note: If you install WebSphere Portal into a directory that does not have write permissions, the installation is not affected and proceeds normally. This is because the installation is performed with the root user, which always has full permissions over files.

1. Disable security using the WebSphere Application Server administrative console.

   If you start the WebSphere Portal installation program with WebSphere Application Server security enabled, the installation program will detect this and display a message. If this occurs, exit the installation program, disable security, and start the installation program again.

2. If you are installing on a machine with a firewall enabled, it is recommended that you disable the firewall before beginning installation. If you do not disable the firewall and the installation program detects it, a warning message displays during the installation.

3. Choose one of the following options to start the installation program:

   • Use the Setup disc

     If you have the Setup disc, perform the steps that are appropriate for your operating system:

     • UNIX: Insert the Setup disc, and then run the following command from the root directory of the CD:

       ./install.sh
       

       When installing with CD-ROM discs, ensure that you do not have an open shell in the CD directory. This can interfere with the installation when the installation program requires you to change discs.

     • Windows: Insert the Setup disc into the CD-ROM drive. The installation program automatically starts when you insert the Setup disc. If the autostart function is disabled, run the following command from the root directory of the CD:

       install.bat
       

   • Access the downloaded product code

     If you downloaded the product code, perform the steps that are appropriate for your operating system:

     • UNIX: Run the following command from the root directory of the CD:

       ./install.sh
       

     • Windows: Run the install.bat command from the <install_root> directory.

4. Select the language for the installation and click OK. The welcome panel is displayed.

   Although the screens here show a Windows 2000 installation, the screens that are displayed for other operating systems have a similar appearance. Be sure to conform to the conventions of your platform when specifying directory locations, file names, and so on.

5. If you want to view the WebSphere Portal Information Center, you can click Launch Information Center, and the Information Center will be opened in a browser. Otherwise, click Next to continue.

6. Select I accept the terms in the license agreement. Click Next.

   

   The installation program checks the machine for operating system and software prerequisites.

7. Select Custom, and click Next.

   

8. If you have one or more existing instances of WebSphere Application Server already installed, select the instance that you want to use from the list. If the installation program does not detect an instance of WebSphere Application Server but you know that it is present on the machine, you can enter the directory path to the WebSphere Application Server. Click Next.

   

9. If you are installing on an existing instance of WebSphere Application Server that is managed by a deployment manager, indicate whether this node is the primary node or a secondary node in the deployment manager cell. Select Primary node or Secondary node, and click Next.

   This panel is not displayed if you are installing on a stand-alone WebSphere Application Server.

   

10. Specify the directory where you want to install WebSphere Portal. If the directory that you specify does not exist, it will be created. If you are installing on Windows, do not include periods (.) in the installation path. Click Next.

    

11. Enter the user ID and password for the WebSphere Portal administrator. Do not use blanks in either the user ID or the password, and ensure that the password is at least five characters in length. This user ID is used to access WebSphere Portal with administrator authority after installation. Note that this user ID is only used to log in to WebSphere Portal and is not related to any user IDs that are used to access the operating system itself. If you intend to use a Lightweight Directory Access Protocol (LDAP) directory to manage your users, ensure that the administrator user ID that you specify here conforms to the recommendations that are specified in Special characters in user IDs and passwords. Click Next.

    administrative user panel" />

12. Verify the components to be installed and click Next. The installation program begins installing the selected components. Throughout the installation and configuration process, the installation program displays progress indicators for the different components.

    A full installation including WebSphere Application Server can take some time to complete. Use the progress indicators and the process monitoring facilities of your platform to monitor the overall progress of the installation.

13. When the installation is finished, the installation program displays a confirmation panel listing the components that have been installed. Note the following information before clicking Finish:

    • The port number that is used to access WebSphere Portal is displayed on the confirmation panel. Make a note of the port number for use in verifying the WebSphere Portal URL. This value is also stored in the WpsHostPort property in the <wp_root>/config/wpconfig.properties file.

    • Windows and Linux only: If you want to use the WebSphere Portal First Steps to access WebSphere Portal, ensure that Launch First Steps is selected. From First Steps you can access WebSphere Portal or read the WebSphere Portal documentation. If you are installing on aUNIXsystem, the Launch First Steps check box is not displayed.

14. Click Finish.

15. To verify that WebSphere Portal is running, open the following URL in a browser: http://<hostname.setgetweb.com>:<port_number>/wps/portal, where hostname.setgetweb.com is the fully qualified host name of the machine that is running WebSphere Portal and port_number is the port number that is displayed on the confirmation panel. For example, http://www.ibm.com:9081/wps/portal.

16. Configure WebSphere Portal to use WebSphere Application Server security, depending on the method you are using:

    • Configure WebSphere Portal for LDAP without realm support. This topic explains how to configure WebSphere Portal to use an LDAP user registry for security, without affecting the security settings that are defined in WebSphere Application Server.

    • Configure WebSphere Portal for LDAP with realm support. This topic explains how to configure WebSphere Portal to use an LDAP user registry for security, without affecting the security settings that are defined in WebSphere Application Server.

    • Configure a database user registry. This topic explains how to configure WebSphere Portal to use a database for security, without affecting the security settings that are defined in WebSphere Application Server.

    • Custom user registry. This topic explains how to configure WebSphere Portal to use a custom user registry for security, without affecting the security settings that are defined in WebSphere Application Server. You cannot use a custom user registry with the Cloudscape database.

    These topics also provide the necessary instructions to complete the WebSphere Portal installation.

17. If you installed WebSphere Portal on the primary node in a managed cell, ensure that you have deployed portlets by running the portlets configuration task. This task should have been run as part of your security configuration, as described in the previous step. Note that the portlets task should only be run after you have run the configuration task that sets up security, such as the secure-portal-ldap task that is used for LDAP support.

    It is not necessary to deploy portlets if you installed on a secondary node.

18. Enable WebSphere Application Server security again using the administrative console.

19. If the WebSphere Application Server where you installed WebSphere Portal is part of a cell managed by WebSphere Application Server Network Deployment, you can create a cluster of WebSphere Portal application servers. Refer to Clustering and WebSphere Portal for more information.

20. By default WebSphere Portal uses the internal HTTP transport within WebSphere Application Server to handle requests, but if you have an external Web server, such as IBM HTTP Server, you can configure WebSphere Portal to use the Web server. Refer to Configure your Web server for instructions.

 

Next steps

At this point, you can choose to explore the function that is provided with WebSphere Portal, or you can extend the WebSphere Portal environment by adding additional components for more advanced function:

• To explore WebSphere Portal, refer to First steps for information on WebSphere Portal that is installed and other important tasks, such as administering WebSphere Portal.

• To add a database with greater capability, such as DB2, refer to Database.

• To add a LDAP directory, refer to LDAP.

• To add collaboration function, such as Lotus Instant Messaging and Web Conferencing instant messaging, refer to Collaborative Services.

These are only a few of the options that are available to you. For a description of the range of components that WebSphere Portal can use to create a more rich environment, refer to Installation scenarios.

 

See also

• Configure your Web server

• WebSphere Portal

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.