IBM Connections Docs
2.0 install guide
Roberto Boccadoro – ELD Engineering
Martti Garden - IBM
What is IBM Connections Docs ?
With IBM Docs, teams can simultaneously collaborate
on word processing, spreadsheet and presentation
documents inside and outside the firewall to improve
IBM Docs authors will be able to store and share
documents in IBM SmartCloud, IBM Connections on
premise or Filenet, co-edit documents in real time or
edit the most up-to-date version on the server
regardless if the editing session is concurrent,
asynchronous or individual... this greatly decreases the
management of multiple revisions from multiple authors
in team-based documents.
IBM Docs requires only a browser. There is no other
desktop software to install. Utilizing the web browser,
users will be able to easily create professional looking
documents and share them with others. IBM Docs is
designed to be simple yet powerful, allowing users to
get started quickly and easily.
Web-based collaborative editors for creating, sharing and collaboratively
authoring word processor documents, spreadsheets and presentations.
IBM Connections Docs components
• An IBM Connections Docs deployment consists of six components:
• Docs Editing server (document service)
This component provides the core logic for processing of the documents.
• Document Format Conversion server (conversion service)
This component performs document type transformations.
• Docs extension plug-in and daemon library
These components are the integration elements which enable IBM Connections users to open and edit a document
within the Connections Docs context.
• File Viewer server (viewer service)
The viewer service enables viewing of the latest published version of a document.
• File Viewer extension plug-in and daemon library
These components are the integration element which enable Connections users to view a document within the
Connections Docs context.
• Docs proxy
The proxy is used for session affinity in Connections Docs. Session affinity routes requests for the same document
from different clients to the same Docs server node.
Architecture (medium to large)
*Also suppports Oracle & MS SQL
**Also supports CIFS on Windows
• Connections Docs shared storage is used by each of the Connections Docs components to store
drafts or transfer files between servers. There are three shares that need to be configured for
• The Connections Docs and Conversion components share storage for the editing and publishing of
documents. This shared storage is supported for either NFSv3 or CIFS (SMB). This share is
referred to as DOCS DATA.
• The File Viewer and Conversion components share storage for the viewing of documents. If File
Viewer and Conversion are installed on the same server, this storage can be local. If they are
installed on different servers, this shared storage is supported for either NFSv3 or CIFS (SMB).
This share is referred to as VIEWER DATA.
• The File Viewer and Connections Files components share storage for the viewing of documents. If
File Viewer and Connections Files are installed on the same server, this storage can be local. If
they are installed on different servers, this shared storage is supported for either NFS or CIFS
(SMB). This share is referred to as the Connections Files Content Store.
Before the installation you will need to download the following
• IBM Connections Docs V2.0 (Partnumber CN7ZLML)
• IBM Connections Docs 2.0 iFix 001
• Python 2.7.x
It is assumed, that you already have IBM Connections 5.0 or 5.5
installed and have access to the Connections database server (this
guide will use DB2).
Since in this case it is a single server installation the IBM Installation
Manager of IBM Connections will be reused.
First we need to create two shares for IBM Docs. We create them in C:IBM
and name them DocsShare and ViewerShare.
Now we need to Install Python, use version 2.7.x and not 3.x. With
3.x the installation *will* fail.
Select to install for all users
The default installation path is fine, so accept and click next
Make sure “Add python.exe to Path” is selected! Click Next again.
The databases have been created with access rights to a user called
DocsUser. As we want to use the same user as we use with IBM
Connections, we need to grant access to lcuser. In the same folder edit
Replace all occurrences of DOCSUSER with LCUSER and save the
Now go back to the DB2 command line processor and run the
db2 –td@ -f appGrants.sql
You should see all command being run successfully.
Close the db2 Command Window
IBM Docs now comes with a new graphical installer based on IBM
Installation Manager. This will make the installation much easier for us.
Make sure that Connections is running
We now need to start the Installation Manager.
Click on File-Preferences
The default installation directory is fine so click Next.
As we have installed IBM Connections as CCM, meaning together with
Filenet select Connections and Content Manager.
Deselect the Editor Proxy, as it is only needed, when you have more than
one Docs Server. Click Next.
On the information panel, make sure to check User Account Control
Disabled and click Next.
Now enter the wasadmin and corresponding password and click on browse.
Go to C:IBMWebSphereAppServerProfilesAppSrv01
and click OK.
Click on Validate
You will get no confirmation pop up.
Once the Next button becomes available click it.
Now we need to map the Nodes to the Applications. Map all application
to the first node and the webserver by first selecting the nodename and
then the “>>” button at the proper application.
Click on Validate
Again you will get no notification popup when the validation is done.
Click on Next once it comes available.
Now we need to supply the local Admin username and password. This is necessary since it
is a remote deployment from the Deployment Manager. It just happens to be on the same
machine in our case. Enter Administrator and password in all instances. Then click Validate.
Click Next once it comes available.
On the next screen enter the following
We have no chat installed, so we just click Next.
In the following screen fill in the values for the database and click Next
The following panel is a bit confusing when installing everything locally. Fill it out as follows
and click Next:
Now it wants to know where to install the Conversion Server and how many
CPU cores to use. For the path choose C:IBMConversion and reduce the
cores to 2. The port should be fine.
Choose C:IBMDocs for the installation target for the Editor component
and click Next.
On the next Panel we don’t need to do anything and can click Next.
For the Extension directory browse to
The Daemon should be installed in C:IBMConnectionsdatashared .
Now we can choose whether the Web and Connections server should be
restarted during the installation.
This is useful when installing IBM Connections Docs in production
environments because it allows you to do the Docs installation at any time
and to restart of the production Connections environment in a specific
maintenance time frame. Of course setting both to No will also decrease
the installation time a lot, since the Connections Server do not get restarted
once with each feature installed.
Since time does not matter we choose Yes for both. Click Next.
Click Next on the configuration file overview panel.
Now you click on Install and grab a coffee or two (or even have
During the installation two black windows will pop up. This is expected (and
annoying, as they pop up every few minutes). These are the conversion
tasks running. At the end of the installation we will alter the Task Scheduler
to have them started hidden. So long just minimize them once they pop up.
In the end you should see the following screen:
Verifying the Docs installation
Log in to Connections at http://yourserver.com/homepage/login
Choose a filename and click Create
This tells us, that the Docs Editor works.
Now enter some data and then click on File / Publish Now.
Enter a description and click Publish.
This message shows you, that the version has been published. For this to
work the Conversion Server needs to be working properly, which we tested
and proved now.
Now upload a new file:
Click Browse and upload a file
Go in My Files and click the name of the file you uploaded
The file will be opened by the Viewer, click on the down arrow near the
Blue box on the right
Select Edit inDocs
The file will be opened in edit mode
This shows that the Viewer and the Editor of Connections Docs work
Now there is only one last thing to do: Change some settings in the Task
scheduled in the Task Scheduler
Go to the Windows Task Scheduler:
Click on Task Scheduler Library on the left, then double click on
the kill_timeout task
Change it to run whether the user is logged on or not and select
Do not store password. Also select hidden and then OK.
Do the same with the sym_monitor task
From the next reboot on the two black windows should not appear anymore.
I hope you were successful in installing everything!
If you have any comments please feel free to contact us!