Follow these steps to finish installing the Communities feature.
1. In the Index file directory field, specify the file path to a local directory in which to store the index files used by Communities to perform full-text searches.
Alternatively, click Browse to navigate to a directory.
Do not share index file directories between different Communities servers. Make sure the directories you specify are large enough to hold the content. See the Hardware Requirements topic for details about disk space requirements for the features.
Click Next.
2. Optional: A page that states, "An existing Java security policy file on the WebSphere Application Server was found" is displayed if a security policy file exists on the WebSphere Application Server server process you are installing the Communities feature onto. As part of the installation process, the installer enables Java™ 2 security on the profile in which the feature is being installed. It then adds a Java virtual machine (JVM) custom property called java.security.auth.policy, which defines the location of this policy file, to the server process definition if no other policy file is defined for it. If a policy file already exists for the current server process, the installer does not change the value of the custom property to reference the new policy file. Instead, you must edit the existing policy file to set up the permissions for the Communities feature. Make a note of the directory in which the existing security policy file is stored, so you can edit it after the installation is complete, and then click Next.
3. When asked to enter the fully qualified domain name for the feature, in the HTTP URL field, type the Web address that users will type into a Web browser location bar to access the feature after it is installed. If you are using an HTTP server, do not specify a port number and remove the default port number provided by the installer. Select the Enable SSL server check box, and then type the Web address users will type into a Web browser location bar to access the feature over SSL into the HTTPS URL field. Click Next.
Note: Do not deselect the Enable HTTP server check box. Doing so could cause the features to be inaccessible from the navigation bar.
4. Review the Summary screen to make sure the values you entered on previous screens are correct. If you want to make a change, click Back to edit a value. If the values are correct, on the installation summary screen, click Install to begin the installation.
5. Click Finish.
6. Start the WebSphere® Application Server instance to which you installed the feature, such as server1, by typing the following commands:
- Linux:
cd opt/IBM/WebSphere/AppServer/profiles/<profile_name>/bin
startServer.sh <server_instance>
- Windows:
cd C:\IBM\WebSphere\AppServer\profiles\<profile_name>\bin
startServer.bat <server_instance>
Note: If the server fails to start, start it again by repeating the above commands. If it continues to fail, look at the error log to see if there is a problem with your set up. The error log file is stored in the following directory:
- Linux:
opt/IBM/WebSphere/AppServer/profiles/<profile_name>/logs/
<server_instance>/SystemOut.log
- Windows:
C:\IBM\WebSphere\AppServer\profiles\<profile_name>\logs\
<server_instance>\SystemOut.log
7. Open a Web browser and access the feature directly from the WebSphere Application Server by going to the Web address you specified for the Communities feature.
For example:
where <port_number> is the port number on the WebSphere Application Server that the feature is available from. This is usually:
- 9080 - Standard port number for the default server process, server1. This is probably the server process that you installed the feature on if you are installing each feature to its own profile.
- 9081-9085 - These are the port numbers that are usually assigned to features that are installed into a single profile. The first server process you create is assigned the port 9081, the next 9082, and each subsequent feature is assigned a port number incremented by one.
The serverindex.xml file stored in the node directory contains port assignment information.
See Mapping the features to the IBM HTTP Server for information about setting up a server that sits in front of the WebSphere Application Server and directs requests (which are not required to specify port numbers) to the appropriate features.
If the Communities login screen is displayed, you have successfully installed the Communities feature. If it is not, see the Troubleshooting section of this document.
8. Optional: If you plan to install additional features on the same system and want to be able to refer to the log file generated by the installer, copy the lcinstalllog.txt file from the following directory:
- Linux:
- Windows:
c:\Documents and Settings\<user_name>\Local Settings\temp\lcinstalllog.txt
into this directory:
- Linux:
/opt/IBM/WebSphere/LotusConnections/Communities/lcinstalllog.txt
- Windows:
c:\Program Files\IBM\WebSphere\AppServer\LotusConnections\Communities\lcinstalllog.txt
The lcinstalllog.txt log file stored in the temporary directory is overwritten by subsequent feature installations.
Much of the information you specify during the installation is stored in XML-based configuration files associated with the product. For information about making changes to those values, see the Administering Lotus Connections section of the Lotus Connections information center. For example, if you change HTTP servers, you can use a wsadmin command to change the service location settings defined in the configuration files for the feature.
Resources
Need support?
This wiki is designed to provide valuable information to help you, but it does not replace other technical support services. Refer the following resources for more information.
Parent topic: Installing a Lotus Connections feature
Related tasks
Installing a Lotus Connections feature
Mapping the features to the IBM HTTP Server
Related reference
Hardware requirements
Don't forget to Sign in to edit or comment on information. Learn how to