- Adding a node to a cluster
Add a node to an existing cluster.
- Configuring a reverse caching proxy
Configure a reverse proxy that directs all traffic to your IBM® Connections deployment to a single server.
- JavaScript configuration
- Enabling locked domains
Assuming that you have completed the server setup previously described, to enable locked domains in IBM® Connections, specify an additional attribute in the LotusConnections-config.xml to ensure that only ConnectionsOpensocial application is mapped to the locked domain host.
- Configuring the custom ID attribute for users or groups
Configure IBM® Connections to use custom ID attributes to identify users and groups in the LDAP directory.
- Configuring External Collaboration
External Collaboration allows internal and external users to work together in your IBM® Connections deployment.
- Configuring Files to use an object store
Configure IBM Connections™ Files to seamlessly work with an external object store, providing scalability and data recovery for your deployment, while enabling faster access to files for users.
- Installing and deploying Connections Docs
To extend Connections to offer users a way to view documents, spreadsheets, and presentations within the Files application, install and set up Viewer from IBM Connections Docs.
- Deploying URL preview in an environment where anonymous access is disabled
To deploy URL preview optionally in an environment where anonymous access is disabled within IBM® Connections, you must define a system user as a proxy for the oEmbed/image proxy services so that it can perform HTTP requests.
- Enabling anonymous access for the Rich Content Widget component
Define a system user to impersonate HTTP read-only requests to the File AppData API for the Rich Content Widget component.
- Customizing browser cookie cleanup on user logout
You can manage and add to the list of browser cookies to be cleaned up on user logout.
- Configuring an NGINX server for long polling
If you deploy an NGINX proxy server to manage push notifications for IBM Connections™, you can configure it to use load balancing and thus provide a greater long poll interval.
- Setting up and configuring a WAS proxy server for long poll testing
HTTP long polling can be used to push updates to a web client. A connection is held open between the web client and the web server so that when the server has new information it can push it to the client. That connection is then closed. For IBM® Connections Social Cloud, a WebSphere® Application Server (WAS) proxy server must be used to test this function.
- Configuring notifications
Enable support for email notifications in IBM® Connections applications.