This system serves as the basis for the applications shared by the cluster members. The installation process installs Lotus® Quickr™, federates the node to the deployment manager, and creates the cluster with the primary node as the first cluster member.
- Make sure that the system on which you are installing meets the supported hardware and software requirements for the product
- The user ID used during installation must have administrator authority
- If you are using a firewall on the system where you are installing, disable the firewall while you perform the installation. If you do not disable the firewall and the installation program detects it, a warning message displays during the installation
- Ensure that the ulimit for your operating system is set to 40000
- Between the installation of the primary and secondary nodes, there is the option of performing a database transfer to a remote database server. Detailed instructions begin with the topic Transferring to DB2. A database transfer can also be performed after secondary nodes have already been added to the cluster.
- Create a <qkr_install_root>/wp_profile/PlaceCenterCollections directory on one of the cluster servers to contain a places catalog index. Make sure the directory has enough space for your deployment; 1 GB is usually enough. The primary node must have write-access to the directory, and all other nodes must have read-access. In Step 12 in this topic, specify this as the location of Shared Resources for PlaceCenter Collections. For more information on configuring places catalogs for clusters, see the topic Configuring places catalog for clusters.
- To configure a clustered environment for search user must create a shared directory called jcr/search on a server in the network and make sure that each node in the cluster has network access to the directory. For more information about configuring search in clusters, see the topic Configuring search for Lotus Quickr content in clusters.
- Start the installation program.
Select the language for the installation and click OK. The welcome page is displayed.
- Use the Setup disc
If you have the Setup disc, insert it into the CD drive, and then use the ./install.sh command from the root directory of the CD.
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.
- Access the downloaded product code
If you downloaded the product code, extract all of the downloaded files and run the ./install.sh command from the root directory of the product download.
Remember: Be sure to conform to the conventions of your operating system when specifying directory locations, file names, and so on.
If you want to view the information center for Lotus Quickr, click Launch Information Center to open it in a browser. Otherwise, click Next to continue.
Select I accept both the IBM and the non-IBM terms. Click Next.
Select Enterprise Cluster, and click Next.
Select the database management system system. If DB2 is selected, a new instance of DB2 will be installed on the machine where the installation is run. After the initial installation, you can transfer to a remote DB2 instance, see Transferring to a remote DB2 database. If Oracle is selected, ensure that there's an existing instance of Oracle already configured. Enter the following information is required to connect to your existing Oracle instance and initialize it for use with Lotus Quickr:
Specify the directory where you want to install Lotus Quickr, and click Next. If the directory that you specify does not exist, it is created.
Select Primary Node and click Next.
Specify the following server information and click Next:
- Host Name: indicates the name of the host where Oracle is installed.
- Port Number: the port on the Oracle machine (default: 1521).
- DBA User: indicates the Oracle DBA account user id (default: system).
- DBA Password: indicates the Oracle DBA account password.
- DB Name: indicates the database name (SID) of the Oracle instance.
- JDBC Driver Path: indicates the location of the Oracle JDBC library (ojdbc14.jar).
Specify the server information for the deployment manager system, and enter the name you want to use for the cluster.
- Specify the name that you want to use to identify this node in the cell. Typically, this value is the same as the host name for the computer. Note that the node name must be unique among other node names in the same cell.
- The fully qualified host name of the computer that is running the server.
Enter the user ID and password to access Lotus Quickr and its supporting infrastructure services with administrator authority. Do not use spaces in either the user ID or the password, and ensure that the password is at least five characters in length. Click Next.
Ensure that the deployment manager is running while you are performing the Lotus Quickr installation or the installation fails.
- The default value for the deployment manager port number is 8879. If you used a different port number when you installed the deployment manager, use that port number here instead.
- When specifying the cluster to be created, do not use spaces or special characters.
- Before continuing verify that the system clock of the primary node is synchronized with the system clock of the deployment manager. The system clocks must be within five minutes of each other or the node federation fails.
Enter the location of the Shared Resources for PlaceCenter Collections. This is a shared folder that you created on one of the servers in your cluster called \\\\ServerName\\PlaceCenter\\Collections. The shared network folder does not need to be on one of the servers in the cluster, but it does need to be accessible from all nodes in the cluster. The Universal Naming Convention (UNC) format, \\\\\\\\your_server\\\\your_share\\\\jcr\\\\search, is the required input format. For example: \\\\\\\\hostname.example.com\\\\share\\\\jcr\\\\search.
- To streamline the installation process, the installation program uses this user ID and password to configure Lotus Quickr and all of its related services. This does not mean a single user ID and password are used, but rather that the same user ID and password are used in several places to configure required services. If you do not want to continue using this user ID and password for Lotus Quickr and its related services, you can change these values after installation. This user ID and password are also used to enable security on the deployment manager.
- The installation uses this user ID, with the password that you enter on this panel, to configure DB2 and create an account on the local system. If you prefer to use an existing user ID or do not want to use this user ID for your database, you can change the database user ID and password after installation by using the configuration wizard included with the product.
- Lotus Quickr provides a fully secured environment immediately upon installation, and the strength of that security starts with the password that you select during installation. Avoid a password that is the same as the user ID, and create a strong password by making it lengthy, combining letters and numbers (both uppercase and lowercase), and avoiding spaces or words found in a dictionary.
Because this password is used to create an account on the local system, make sure that the password that you enter conforms to any character and length policies that are used by your organization.
When entering the user ID and password, you can use characters a-z, A-Z, period (.), hyphen (-), and underscore (_). You can also use DBCS characters in the user ID, though not in the password. See Special characters in user IDs and passwords
for more information about acceptable special characters.
Select whether you want to run Lotus Quickr as services, and click Next.
Verify the components to be installed, and click Next.
To use a locally mapped drive for the shared resources location, one must first install it using the UNC format.
After the installation is complete, use one of the following methods to update the location value:
- Using WebSphere® Application Server administration console
Update the wp_profile\\ConfigEngine\\properties\\wkplc_comp.properties file
- Click Resource environment providers -> PlacecntrPropertiesService -> Custom properties -> defaultCollectionsFolder.
- update the value of defaultCollectionsFolder to point to the locally mapped drive
- Click Save.
- Restart the server(s).CC
- Change the value of the property placecntr.collections.storage.path to point to the locally mapped drive.
- Run the following ConfigEngine command, where xxx is the Lotus Quickr administrator password:
ConfigEngine.bat action-set-collections-path -DWasPassword=xxx
- Restart the server(s).CC
After the installation is underway, use the progress indicators and the process monitoring facilities of your operating system to monitor the overall progress of the installation.
When the installation is complete, a confirmation page is displayed.
Verify that the cluster has been created and that the Lotus Quickr server is running as a cluster member.
Before you click Finish
, note the following information.
- The fully qualified URL to access Lotus Quickr is displayed, with the port number on which Lotus Quickr receives requests. Make a note of the URL, particularly the port number specified in the URL.
- The First Steps utility provides an easy way to log in to Lotus Quickr or access the product documentation. If you want to start First Steps automatically after you close the installation program, ensure that Launch First Steps is selected.
- If you already know that you want to configure Lotus Quickr to use a different database or an LDAP directory, select Launch Advanced Configuration Wizard to continue with that configuration after you close the installation program.
Verify that Lotus Quickr can launch. Open a browser window and enter in the URL mentioned at the end of the Lotus Quickr installation.
Optional: Between the installation of the primary and secondary nodes, there is the option of performing a database transfer to a remote database server. Detailed instructions begin with the topic Transferring to DB2. A database transfer may also be performed after secondary nodes have already been added to the cluster.
- Log in to the administrative console for the deployment manager.
- Click Servers -> Clusters, and verify that the cluster you created is displayed.
- Click the cluster name, click Cluster members, and verify that the Lotus Quickr application server is displayed. CC
Note: Remember that WebSphere_Portal is not a cluster member, only the Lotus Quickr server is a cluster member.
Parent topic: Installing a cluster on AIX systems: qp85