Required Installation Files
1. 32-Bit version of Domino 8.5* Quickr is not supported on a 64-bit installation of Domino
2. Quickr 8.2
Extract Domino installation file. Once the Domino installation has been extracted you will have an aix directory in the current working directory (CWD) .
Located within the aix folder at .../aix/domino is the installation script named “install”. To run this script you must be the root user on the system. Execute the install script by typing “./install” and pressing enter.
We will be doing this installation via the console and therefore will accept the default setting of [Yes] by pressing the “Enter” key.
The installation will start.
You will be prompted to continue the default setting of  is correct so we simply need to press the “Enter” key.
The Software License Agreement will be begin to be displayed. Press the “Enter” key to begin displaying the license agreement.
Enter a “1” and press the “Enter” key to accept the license agreement.
After accepting the license agreement you will be asked if you want to install the data directory only. Since we are doing a single partition installation for simplicity leave the selection at  and press the “Enter” key.
Next you will be prompted for the Domino installation directory path. You can use any file system location with sufficient size for the installation. In this case a custom path (/quickr82/quickrwiki) was specified instead of accepting the default path. Immediately following the Domino installation path prompt you will be prompted again regarding whether or not this installation is for a domino partitioned server. We selected [No] which is the default.
Next you will be prompted for the data directory installation path. To keep the server configuration simple we are specifying the same directory as Domino installation path. The server will then have 2 directories under this location
Next you will prompted to enter the OS level user name of the user who will be used to start the Domino server and who will own the files in the data directory. For simplicity we accept the default of [notes] user. * Note this user should exist prior to the installation. The user's name does NOT need to be "notes"
Next you will be prompted to enter the OS level group name that the "notes" user is a member of. Again we accept the default which is the [notes] group. * Note this group should exist prior to the installation. The group name does NOT need to be "notes".
Next you will be prompted if you want to create a softlink. We accept the default value of  or no by pressing the “Enter” key to continue.
Next we are prompted on how server setup should be started. Previously I have had issues with local and remote settings. Manual has worked more consistently in the past. Keep default setting of manual and press the “Enter” key to continue.
We are now prompted for the type of Domino installation. Quickr requires that we use Domino Enterprise server which is the default selection. Press the “Enter” key to accept the default setting.
You are next presented with a review of the configuration options you have selected. Unless you notice an error we will be simply press the “Enter” key to continue.
Next you will be presented with more installation information. Accept the current settings unless you notice an error by pressing “Enter” key.
After installation completes you will be presented with a successful installation message. Press the “Enter” key to accept the  in the dialog.
The Domino server is now installed but must be setup. To setup the Domino server we will use the remote server setup utitlity.
Domino Configuration via remote server setup utility
To remotely setup a Domino AIX server the server must be started in “listen mode.” Since we selected during the installation of the Domino server a “manual” start we must issue the command from the data directory as the appropriate OS level user. In our case “notes”.
On the client machine which has the remote server setup utility installed we start the utility and then enter the ip address of the server and then we should see the screen displayed below. Click next to continue.
We are prompted to select the server type. For simplicity we are doing a stand alone installation so we simply need to click next to accept the default setting.
Next we need to specify the server name. The server title is optional. Click next to continue
Next we need to either point to a existing administrator id or create a new one. Since this is a a new stand alone server installation we are going to create a new administrator account. We are saving a copy of the administrator id to the data directory.
We are now displayed the current enabled ports and host name. The host name field will normally be populated with the Fully Qualified Internet Host Name of the physical server we are installing on. The host name field can be customized to use any valid DNS name.
We choose to accept the default security settings. However, selections chosen should be representative of what your organization has specified for other Domino installations so that security settings are homogeneous on all servers.
We are next displayed the location where the server, cert, and admin ids will be created on the Domino server. We are also provided the option to save a local copy of these ids on the client machine. We selected to make copies on the client machine to make remote administration easier.
We are next displayed the configuration options we have chosen. At this point if you notice an error or misconfiguration you can click back and change the configuration. We clicked setup since no misconfiguration was noted.
Next we provided a message stating that Domino setup is complete and an additional dialog for stopping the setup listener. We stopped the listener and clicked finish to complete the Domino server configuration.
After Domino configuration and the server listener has been stopped. We recommend starting the Domino server and allowing the server process to stabilize and ensure the HTTP Server task successfully starts. The reason we do this is in an effort to isolate where installation issues may have occurred. Instead of installing both Domino and Quickr and then starting the server. If we receive errors or lack the functionality we know that it occurred during the initial configuration and/or installation of the Domino server. The Domino server is started by being the appropriate user (notes) and issue the following command from the data directory /quickr82/quickrwiki/lotus/bin/server. The path specified to the server binary will be dependent on the your environment's installation path.
We recommend updating the Domino server document with the Domino Servlet Manager setting at this time because administrators tend to forget this step. However, the update can be made at anytime the Domino server is running through the Administration client. For this setting to take effect the HTTP task must be restarted. We will be stopping the server after making this change to continue installing Quickr 8.2. On the next server start the Domino Servlet Manager setting will take effect. The server document should be updated at the following location.
- Internet Protocols → Domino Web Engine Tab → Java Servlets section to
“Domino Servlet Manager”
Quit the Domino server
Quickr 8.2 Installation
Extract the Quickr8.2 installation file
Change directory to the server directory. Execute the installation script called “install” by issuing the following command as the Root user “./install”.
You will presented the following screen press the “Tab” key to continue.
Enter a 1 to accept the license agreement.
Press the “Enter” key to modify the default path provided and enter the location to the “lotus” directory. In our example the path is /quickr82/quickwiki/lotus
Accept the new path we specified by clicking the “Tab” key.
Enter the path of the data directory by pressing the “Enter” key, specifying the path location, and pressing the “Tab” key to accept the new path
The next screen provides options for the installation type of Quickr. We are installing the full product and we need to change the setting from [Yes] to [No]. Press the space bar to change to [No] and press the “Tab” key to accept the setting
On the next screen the installer should have detected the name of the notes user specified during the Domino installation and have it as the choice. If the installer is displaying the incorrect user then change to the correct user. In our case the correct user was specified by the installer so we just need to accept by pressing the “Tab” key.
On the next screen the installer should have detected the group of the notes user that was specified during Domino installation and have it as the choice (in our installation both the user and group are called notes). If the installer is displaying the incorrect group then change to the correct group. In our case the correct group was specified by the installer so we just need to accept by press the “Tab” key.
The next screen prompts for the name of the administrator of the Quickr server. This is a user name that should NOT exist in the user directory the Quickr server will be connecting to. This user's role is to be able to access and administer the Quickr server, via the web, when there is no connection to a directory. This applies regardless if the Quickr server will be connecting to the Names.nsf that is on the local Domino server. We specified the user name of “Quickr Admin” by pressing the “Enter” key, typing in the name, press the “Enter” key again, and to accept the name press the “Tab” key.
The next screen prompts for the password to be used for the administrator account we just created. To change from nothing press the “Enter” key, type in the password , press the“Enter” key again, and then press the “Tab” key to accept the password entered. . We used the word “password”. However, in a production environment the password should confirm to security conventions of your organization.
The next screen explains that we will be reviewing the configuration and to press the “Tab” key to continue.
We are now displayed the type of install, installation paths, OS level user name, and OS level group name. Since the configuration is correct we simply need to press the “Tab” key to proceed. In the event you notice an error press the “ESC” or escape key to re-configure the installation settings for the Quickr server.
The Quickr installer will now check for the appropriate OS fixes/apars on the AIX server. Since no list appears we have all the correct OS Level patches and the installation begins.
If the installation completed successfully you should see successful installation message. The server is now ready to start.
We start the Quickr server by starting the Domino server we installed Quickr on as the appropriate OS level user. Once the Domino server starts we want to verify that “Lotus Quickr Services loaded” successfully is displayed on the console as well as the HTTP Server task being started.
The Quickr server should now be accessible via a web browser. We will login with the Quickr Admin that was specified during the Quickr installation and set the user directory by clicking Site Administration → User Directory → Change Directory and clicking the drop down window and selecting the appropriate directory type. For simplicity we chose “Domino Server” and clicked next.
When you have a successful connection to the directory you should see a status message indicating so. The message will be dependent on the directory type and whether or not credentials need to be specified or not. Users that exist in the Names.nsf and have their internet password set in their person document should now be able to access the Quickr server via the web.