What's new
Find out what's new and what's been updated.
IBM Connections 3.0.1
- If you are using an earlier version of the product, you can migrate from version 2.5 or upgrade from version 3.0. For more information, see the Migrating to IBM Connections 3.0.1 from version 2.5 and Update to IBM Connections 3.0.1 from version 3.0 topics.
- During the installation procedure, you can customize the names of your application servers.
IBM Connections 3
- Install a network deployment has been simplified and made more flexible. The dmgr (DM) component of WAS controls the addition of nodes and clusters to the deployment, thus eliminating several manual installation steps.
- Run the installation wizard on the DM with managed nodes rather than on unmanaged stand-alone nodes
- Install multiple nodes in a single installation procedure
- Add or remove nodes and clusters after installation without needing to unfederate nodes
- The installation wizard is replaced by the IBM Rational Installation Manager. This tool simplifies the installation and configuration of IBM Connections 3.0.
- A non-root user can install and update the product.
- A new checklist topic helps you to record important details of the installed environment.
- The stand-alone deployment option is no longer available with IBM Connections. Only a network deployment is possible with IBM Connections 3.0. This deployment option simplifies the installation and configuration of IBM Connections.
- The pilot deployment option is no longer provided with IBM Connections.
- Migrating from the IBM Lotus Connections 2.5 pilot deployment to IBM Connections 3 is not supported. You can migrate a pilot to the 2.5 production deployment and then migrate to IBM Connections 3.
- If the Profiles application is installed, the Profiles database is automatically selected as the user directory. There is no longer an option during installation to choose either the Profiles database or the LDAP directory as the user directory. You can still change the user directory after installation. The profiles.directory.service.extension.enabled parameter is enabled by default.
- The SPNEGO authentication mechanism is supported for Kerberos and IBM Tivoli Access Manager.
- Improved index management:
- Manage indexes across multiple nodes
- Configure temporary directories for indexes on each node
- Removed a node from the index management table when it is removed from a cluster
- Create scheduled tasks to back up the index
- Purge indexed content for individual applications instead of needing to delete and recreate the whole index
Parent topic
Installing
});