Administrator checklist

Database and file system backup

• Back up and restore data
• Gather DB2 database statistics daily

Tasks to schedule

1. Before recreating the search index, stop all scheduled tasks first.

   No tasks can run while the search index is being built. We do not have to do anything to create the initial search index because it runs automatically during the installation process. Wait for one of the default indexing tasks to run.

2. Re-create the index using one of the following procedures:

   Recreate the search index

   When using this method, users cannot use Search.

   Create a background index

   When using this method, users can continue to use Search.

3. Schedule the following tasks:

   • PowerCube refreshes for the Metrics application.

   • For user directory maintenance:

     • To keep the Profiles data in sync with the source from which you populated it, schedule the sync_all_dns script to run nightly.

       If we made any customizations to the population process, schedule your custom synchronization script to run nightly instead.

     • To keep information about managers up-to-date, run mark_managers.

Manage content

Consider enabling the following features:

• Moderation. Content that is added to Blogs, Forums, or Files in Communities must be reviewed by a moderator before it can be made public. Alternatively, we can allow people to add content freely, but enable others to flag content as inappropriate. See Moderation overview..

• To enable administrators to perform advanced tasks in all applications, Create a global administrator.

• Designate who can view and interact with server-level metrics . By default, community owners can view metrics only for their communities; users cannot view any metrics.

Integrate with other products

.Consider integrating the following features:

• Add IBM Sametime awareness, either through the Sametime client or server.

• We can add third-party applications to a list allowing them potential access to IBM Connections data using the OAuth protocol and the Connections API. Users decide whether to give these applications access to their IBM Connections data.

Security considerations

Consider configuring the following features:

• IBM Connections uses single sign-on to secure the transfer of user ID and password information. Users can switch to different applications without needing to authenticate again.

• By default, the Connections AJAX proxy is configured to allow cookies, headers or mime types, and all HTTP actions to be exchanged among the Connections applications. To change the traffic allowed from non-IBM Connections services, explicitly configure it.

Customize the product

Consider adding the following customizations:

• Start IBM Connections, and review the product user interface to determine which areas of the product to customize the user interface.

• We can also use an OAuth 2.0 consumer proxy to allow the Homepage component to surface gadgets in an OpenSocial container that can interact with an OAuth 2.0 protected service

Test the environment for production readiness

• If during product installation you specified directory paths to application data and resources that were different from the default paths, we must change your environment variables to reflect those changes. The application configuration files that define the behavior of the applications reference the directory paths using these environment variables.

• Make sure references to administrator IDs and passwords are correct.

• If the IHS is hosting multiple web servers, you might want to change the session cookie name of one of them to prevent the cookie from being lost when the user is redirected from one product to another.

Parent topic:
Administer common areas