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 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.
Managing the Search index
The Search application uses a Lucene 3.0.3 index, supplemented by social facet information. The location of the Search index is mapped to an IBM® WebSphere® Application Server variable, SEARCH_INDEX_DIR. The value of this variable is set to CONNECTIONS_DATA_DIRECTORY/search/index by default.
The indexing process
The Search index is generated by retrieving information from each of the applications based on a schedule defined by the administrator. Search uses the IBM® WebSphere® Application Server scheduling service for creating and updating the Search index. The index must be deployed on each node running the Search enterprise application.
Manipulating the resume tokens for IBM® Connections services
Use administrative commands to manipulate the resume tokens in the Search index.

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.
  - 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.
    - Accessing the Search configuration environment
      You need to initialize the Search configuration environment to be able to run the SearchCellConfig and SearchService MBean commands.
    - Managing the Search index
      The Search application uses a Lucene 3.0.3 index, supplemented by social facet information. The location of the Search index is mapped to an IBM® WebSphere® Application Server variable, SEARCH_INDEX_DIR. The value of this variable is set to CONNECTIONS_DATA_DIRECTORY/search/index by default.
      - The indexing process
        The Search index is generated by retrieving information from each of the applications based on a schedule defined by the administrator. Search uses the IBM® WebSphere® Application Server scheduling service for creating and updating the Search index. The index must be deployed on each node running the Search enterprise application.
        Investigating file content search issues
        An overview of file content search issues.
        Search index directory structure
        Each IBM® Connections application has its own index directory. The Search index directory is defined by the WebSphere® Application Server variable SEARCH_INDEX_DIR.
        Adding a service to the search index
        Use administrative commands to update the Search index with data from a newly added service.
        Checking fault tolerance during the initial indexing process
        Review the serverStatus web page to determine whether any exceptions occurred while building an initial index.
        Manipulating the resume tokens for IBM® Connections services
        Use administrative commands to manipulate the resume tokens in the Search index.
      - Creating Search indexes
        Search indexing is automatically configured for IBM® Connections during installation.
      - Index settings
        Indexing is automatically configured in IBM® Connections. However, when setting up indexing for your environment, you might need to perform additional configuration tasks.
      - Verifying Search
        You can perform a number of steps to verify that Search index creation has completed successfully and the Search application is working as expected.
      - Adding a new component to an existing index
        Add new IBM® Connections components to the index that were not included when the index was built.
      - Configuring scheduled tasks
        The SearchService MBean is used to access a service that provides an administrative interface for adding scheduled task definitions to the Home page database.
      - Running one-off tasks
        The SearchService MBean provides commands that allow you to create an indexing optimize task that is scheduled to run once and only once, 30 seconds after being called.
      - Retrieving file content
        Use SearchService commands to perform file content retrieval tasks.
      - Purging content from the index
        Use the SearchService.deleteFeatureIndex command to purge content for a specific application from the Search index in a single-node environment.
      - Reindexing content
        Use the retryIndexing command when you want to reindex content that was not indexed successfully during initial or incremental indexing.
      - Reindexing content on a clustered IBM® Connections deployment
        When you reindex from scratch on a clustered IBM® Connections deployment, reindexing takes place in the background while the system continues to service requests of the existing index. When reindexing completes, you then switch to the new index. The update process includes ripple restart of Search nodes.
      - Deleting persisted seedlist data
        You can free up disk space by deleting persisted seedlists from your system using the SearchService.flushPersistedCrawlContent command.
      - Deleting the index
        Delete the index by deleting the contents of the directory specified by the IBM WebSphere® Application Server variable, SEARCH_INDEX_DIR.
      - Listing indexing nodes
        Use the SearchService.listIndexingNodes command when you need to check the names of the Search indexing nodes in your deployment. For example, if you want to remove an indexing node from the index management table, you can use this command to verify the name of the node that you want to remove.
      - Removing a node from the index management table
        When you are removing a node from a cluster, use the SearchService.removeIndexingNode wsadmin command to remove the node from the index management table.
      - Backup and restore
        Create a backup of the Search index and save it to a secure location so that it can be used to restore the index in the event of loss or corruption.
      - Configuring file attachment indexing settings
        Edit settings in the search-config.xml file to configure Search for file attachments.
      - Configuring the number of crawling threads
        Edit settings in the search-config.xml file to specify the maximum number of threads used when crawling. The maximum number of threads that you should specify is the number of applications that you have installed in your deployment.
      - Configuring the number of indexing threads
        Edit settings in the search-config.xml file to specify the maximum number of threads used when indexing.
      - Boosting search results by tag, title, or recency
        Influence the quality and ranking of search results by configuring a boost to the relevance score associated with specified fields in the index.
    - Managing the Search application
      You can perform the following tasks when managing the Search application.
    - Viewing and collecting Search metrics
      Enter a URL to view a standard set of metrics related to the Search application. You can also write internal search metrics to a file.
    - SearchCellConfig commands
      The SearchCellConfig commands are used to configure the location of the Search index and the IBM® LanguageWare® dictionaries used by Search, and to configure the file download and conversion service used when indexing file attachments.
    - SearchService commands
      The SearchService commands are used to create, retrieve, update, and delete scheduled task definitions for the indexing and optimization Search operations.
  - 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™.

Manipulating the resume tokens for IBM® Connections services

Use administrative commands to manipulate the resume tokens in the Search index.

Before you begin

To use administrative commands, you must use the wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin client.

Notes:

You must have an index in place because the commands manipulate the resume tokens in a valid index.
Do not run this command against a foreground index.

About this task

Use the Search application to update the resume tokens for components in an index. When this index is then used as the foreground index, crawling of the components resumes from the time and date that is specified in the updated resume tokens.

Procedure

To manipulate resume tokens, complete the following steps.

Use the following command to run one-off indexing tasks.

SearchService.updateResumeTokens(String components, String date, String indexLocation)

Updates the resume tokens in the index.

Note: You can run this command on background indexes only.

This command takes the following arguments:

components

The applications whose resume tokens are to be manipulated. The following values are valid:

activities
all_configured
blogs
calendar
communities
dogear
ecm_files
files
forums
people_finder
profiles
status_updates
wikis

Use all_configured instead of listing all indexable services when you want to manipulate the resume tokens.

date: The date the resume tokens are changed to; date is in the format MM-dd-yyyy HH:mm:ss:SSSZ.
For example: 08-01-2013 14:00:00:000-0000

indexLocation: The location that contains the index that has its resume tokens updated.
For example: /opt/IBM/Connections/data/search/index_backup
.

If the command works correctly and the resume tokens are updated, the value "1" is returned on the command line. If the resume tokens are not updated the value "0" is returned on the command line.

Note:

Examples:

SearchService.updateResumeTokens("all_configured","08-01-2013 14:00:00:000-0000", 
"/opt/IBM/Connections/data/search/index_backup") 
SearchService.updateResumeTokens("profiles, 
activities,blogs,communities,forums,files,dogear","08-01-2013 14:00:00:000-0000", 
"/opt/IBM/Connections/data/search/index_backup")

What to do next

Restore the updated index to all nodes in the cluster. For more information, see Restoring the Search index.

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.