Home
Administering Connections 6 CR6
Welcome to the HCL Connections 6 CR6 documentation. HCL Connections is social networking software designed for the workplace. Its features help you to establish dynamic networks that connect you to the people and information you need to achieve your business goals.
Administering
Run administration and maintenance tasks to keep your environment up-to-date. For example, learn how to customize your deployment or how to use the wsadmin utility to edit configuration files. You can also schedule tasks, maintain application databases, moderate content, or manage users and their roles.
Administering Libraries
A Library provides the services of an Enterprise Content Management (ECM) system to Communities. To enable the use of Libraries, you must make some configuration changes to Connections and to each ECM system that you plan to use.
Configuring the FileNet® deployment used by Libraries
FileNet® Content Platform Engine and FileNet Collaboration Services are initially deployed and configured as part of the Connections Content Manager installation.
Managing anonymous access for a FileNet® deployment
IBM® Connections requires anonymous access to be set in FileNet® for public communities unless external users are part of a community, in which case anonymous access needs to be disabled.

Administering Connections 6 CR6
Welcome to the HCL Connections 6 CR6 documentation. HCL Connections is social networking software designed for the workplace. Its features help you to establish dynamic networks that connect you to the people and information you need to achieve your business goals.
- What's new in HCL Connections 6
  Find out about features that are new or updated in this release of HCL Connections.
- Product overview
  Learn how to deploy, customize, and administer the IBM Connections social networking product.
- Planning
  Before installing HCL Connections™, study the system requirements, deployment options, and documentation conventions.
- Installing
  To install IBM® Connections, you need to follow a detailed series of procedures.
- Migrating and updating
  Migrate IBM® Connections and its supporting software to the latest release and then update the installation with the latest interim fixes or Cumulative Refresh (CR).
- Administering
  Run administration and maintenance tasks to keep your environment up-to-date. For example, learn how to customize your deployment or how to use the wsadmin utility to edit configuration files. You can also schedule tasks, maintain application databases, moderate content, or manage users and their roles.
  - Administering common areas
    Administer the common areas of IBM® Connections.
  - Administering Activities
    Configure Activities to best meet the needs of your environment.
  - Administering Blogs
    Administer site-wide settings for Blogs from either the Blogs user interface or via the wsadmin client.
  - Administering Bookmarks
    You configure and administer Bookmarks using scripts accessed using the wsadmin client. Changes to Bookmarks configuration settings require a restart of the Bookmarks server before they take effect. Changes made using administrative commands take effect immediately.
  - Administering Communities
    Configure and administer Communities using scripts accessed using the IBM® WebSphere® Application Server wsadmin client.
  - Administering Files
    You administer Files using the wsadmin client to specify properties in a configuration file, or run administrative commands.
  - Administering Forums
    Administer Forums by specifying properties in a configuration file or running administrative commands.
  - Administering the Home page
    You can administer site-wide settings for the Home page from the Home page administration user interface or using the wsadmin client.
  - Administering Libraries
    A Library provides the services of an Enterprise Content Management (ECM) system to Communities. To enable the use of Libraries, you must make some configuration changes to Connections and to each ECM system that you plan to use.
    - Library concepts and terminology
      Knowledge of FileNet® concepts can help with extension and customization of your deployment. Connections Content Manager uses the FileNet P8 Platform to store and retrieve documents in libraries.
    - Running Library administrative queries and commands
      Run administrative commands from the Administration Console for Content Platform Engine (ACCE) to query for and modify objects in the FileNet Content Platform Engine
    - Configuring CCM for newly added nodes
      You must perform several steps to get IBM® FileNet® working properly on a newly added node.
    - Creating and managing document types
      Define the document types that users can select when they add a file to a library.
    - Permissions and access management
      Files and folders can be shared within a Library. However, the Library itself cannot be shared, but you can set access on the Library in the edit mode of the Library widget. The Library owner can decide the permissions to be given to members of a community. Initially, files and folders inherit access settings from their parent.
    - Libraries and the Activity Stream
      A library sends events from documents in the library to the Activity Stream.
    - Finding identifiers for CCM libraries, folders, and documents
      Find identifiers of IBM Connections Content Manager libraries, folders, and documents from the IBM Connections web interface. You can then use the identifier in an administrative task or query.
    - Configuring the FileNet® deployment used by Libraries
      FileNet® Content Platform Engine and FileNet Collaboration Services are initially deployed and configured as part of the Connections Content Manager installation.
      - Configuring collaborative features in FileNet®
        You can set up and maintain FileNet® collaborative features using the Administration Console for Content Platform Engine (ACCE) on the FileNet system to create and administer an Object Store.
      - Reconfiguring FileNet® Collaboration Services to support changes to Connections Content Manager
        Use the IBM® Content Navigator Configuration and Deployment tool to reconfigure FileNet® Collaboration Services to support changes to IBM Connections Content Manager.
      - Generating Security identifiers to be used in configuration
        You need to generate Security Identifiers (SID) values for installing IBM® Connections Content Manager with a new FileNet® deployment or an existing FileNet deployment.
      - Managing anonymous access for a FileNet® deployment
        IBM® Connections requires anonymous access to be set in FileNet® for public communities unless external users are part of a community, in which case anonymous access needs to be disabled.
        Enabling anonymous access for a FileNet® deployment
        Disabling anonymous access
      - Setting an LDAP group to be domain administrator in addition to, or instead of, a specific user
        Select or create a group in LDAP to act as IBM® FileNet® domain or Object Store administrators or both, and add any desired user for this administrator role into this group. You should consult your LDAP documentation for complete information about LDAP groups. If a group is not granted administrator access and the administrative user is later deleted, it might be difficult to recover administrative access to FileNet, and functions including library creation and search indexing might not function.
      - Changing connectionsAdmin to be an LDAP user
        For an existing installation of IBM® Connections with IBM FileNet®, the connectionsAdmin user defined in your FileNet system must be available in the directory configuration of both FileNet and Connections. The easiest way to accomplish this is to change to the connections Admin user to be an LDAP user in a common directory. This procedure assumes that the connectionsAdmin user in Search and Communities (and all other applications) is already an LDAP user.
      - Optional: Changing the location on disk used to store library content
        If the system path used to access the shared content directory is changed for any reason, the IBM® FileNet® configuration needs to be updated.
    - Recreating the FileNet® domain and object store
      If you have a problem with running the ccmDomainTool automation tool to create the FileNet® P8 domain and Object Store, perform the following refresh steps and then rerun the tool.
    - Configuring Library widget options and defaults
      Configure the behavior of community Library widgets by checking out library-config.xml and editing it directly.
    - Configuring web resources and virus scan properties
      Web resources properties include for example, the Connections server and port for URLs. Virus scan properties include for example, the virus scanning server that is used to scan uploaded files for viruses. Create these configuration properties in the connections.xml file.
    - Administering thumbnails for library files
      IBM Connections™ configuration properties control how and when thumbnails are generated for Library files.
    - Enabling grid view for library files
      Use ccmMediaView flag to enable grid view in Connections Content Manager libraries and linked libraries.
    - Adding Linked Libraries
      Enable and configure linked libraries so that Community owners can add them.
    - Managing ECM and CCM connectivity in a library
      Manage Enterprise Content Management (ECM) and Connections Content Manager connectivity.
  - Administering Metrics for Cognos
    Administer metrics in IBM® Connections by modifying configuration settings, backing up data, and running commands to perform maintenance tasks.
  - Administering the News repository
    You administer the News repository using scripts accessed using the wsadmin client. Changes to News configuration settings require node synchronization and a restart of the Home page server before they take effect.
  - Administering Profiles
    Profiles provides two types of administrative capabilities: configuration settings and administrative commands. You change configuration settings and execute administrative commands by running scripts from the wsadmin command line.
  - Administering Search
    The Search service provides a point for performing full text and tag searches across all the deployed IBM® Connections applications. Search is a required application for all IBM Connections applications, and it must be running to prevent unexpected behaviors in the other applications.
  - Administering Wikis
    Configure and administer Wikis by using the wsadmin client to run administrative commands or by editing the configuration file directly.
  - Administering Component Pack for Connections
    Monitor the services for Component Pack for IBM Connections™ and troubleshoot issues.
- Customizing
  Customize IBM® Connections to fit your environment.
- Security
  IBM® Connections provides a flexible security infrastructure that supports an open, easily shareable data model.
- Mobile
  See the IBM Connections Mobile documentation for Connections Cloud and Connections on-premises.
- Developing
  Get information about how to use the APIs provided with IBM® Connections and how to use Connections Customizer to modify the Connections pages that are returned to users.
- Troubleshooting and support
  To isolate and resolve problems with your IBM® products, you can use the troubleshooting and support information. This information contains instructions for using the problem-determination resources that are provided with your IBM products, including HCL Connections™.

Managing anonymous access for a FileNet® deployment

IBM® Connections requires anonymous access to be set in FileNet® for public communities unless external users are part of a community, in which case anonymous access needs to be disabled.

About this task

Configuring an anonymous user is required if you want users to access Connections Content Manager without authenticating. The installation process also prompts for an anonymous user, and if you entered an anonymous user account during the installation, anonymous access is already configured. These steps might be used to enable or disable anonymous access after the installation. In some cases, such as when desktop single-sign is enabled, or when roles in the communities application are restricted to limit access to authenticated users, setting up anonymous access for FileNet® is optional. For more information, see Roles.

For more information, see Enabling anonymous access for a FileNet® deployment.

If you want to allow external users to participate in your Connections communities, then anonymous needs to be disabled for Connections Content Manager.

For more information, see Disabling anonymous access.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.