Installing ibm docs on a single server

UKLUG 2012 – Cardiff, Wales
Roberto Boccadoro
ELD Engineering
roberto.boccadoro@eldeng.it
ICON UK 2015
Installing IBM Connections Docs in a
single server configuration
Martti Garden
IBM Germany
martti.garden@de.ibm.com
September 2012

About me
Joined Lotus in 1994, we were selling cc:Mail then, Notes was V3 and was
sold as development platform.
Bought by IBM, remained there since Sept. 2012 in Technical Sales.
Actually working as IT Specialist / IT architect for ELD Engineering; we’re
not technically a Business Partner but we work for Business Partners
helping them in proposing and deploying solutions for their customers.
I have worked with almost all the products Lotus/IBM has created in the
collaboration space, my actual focus is mostly IBM Connections, IBM
Sametime, IBM Docs, Quickr migration to Connections.
Outside work, I am a husband and father of 4 (2 humans, 2 cats) and an
amateur astronomer.

About me
Joined IBM in 1997 as a student and was happy to see the introduction of
Lotus Notes 4.5 in 1998.
Since 2000 I am working as a Technical Sales with side steps into Sales
and Services.
I have worked with mobile solutions from IBM (IBM Mobile Connect,
WebSphere Everyplace Access, WebSphere Everyplace Server,
WebSphere Everyplace Connection Manager) and the Lotus portfolio with
strong focus on Social Solutions (IBM Connections, IBM Docs and IBM
Verse).
Outside work I am … What’s outside work?!? ;-)

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 productivity.
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.

Architecture (medium to large)
*
**
*Also: Oracle,
soon: MS SQL
**Also: CIFS

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.

Shared storage
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 Connections
Docs.
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.

Why a single server install makes sense
IBM says it is useful only for demos / POCs
Here in Europe there are thousands of SMB customers with a
few hundreds of users, if not less, with a relatively small IT
infrastructure; also WAS is powerful enough to serve hundreds
of users on a single instance.
For this kind of deployment a single server installation is
definitely a viable solution.

Two options
You can install Docs on the same server
where there is IBM Connections, assuming
you have a powerful machine
Or….
You can install Docs in a separate server
and federate it with the Deployment
Manager of IBM Connections

Installation

First we need to create two shares for IBM Docs. We create them in C:IBM and name
them DocsShare and ViewerShare.

Create Docs db
Download the install package from Passport: IBM Connections Docs V1.0.7 for Windows and Linux
Multilingual (CN30NML ), is a file named CNNCTNS_DOCS_1.0.7_WINLNX_ML.zip.zip
Unzip it, you’ll see this
Go in the “native” directory, you’ll see this

Unzip “DocsApp_1.0.7.zip”, you’ll see this
Open a DB2 Command Window - Administrator

In the newly opened window navigate to the newly created directory
../DocsInstallPack/native/DocsApp_1.0.7/setupDB in a db2cmd on the DB server
and execute the createdb.bat .
You need to be patient, it may appear that nothing happens for a few minutes.
Some minutes later you should see all commands have been completed
successfully. Now run the updateDBSchema.bat command.

When finished you’ll see this
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 appGrants.sql.

Replace all occurrences of DOCSUSER with LCUSER and save the document.

Now go back to the DB2 command line processor and run the following command:
db2 -td@ -f appGrants.sql

Install Python 2.7.x
IBM Docs 1.0.7 needs Python for the installation, therefore we will need to provide it. Make sure to
select “Add python.exe to Path”, as it is per default unselected!

Disable User Account Control (UAC)
As the Docs installer will install parts (or all depending on you topology) of IBM Connections Docs
remotely, Windows User Account Control will need to be turned of. The installation will fail with errors
about remote jobs if this step is missed! Remember to reboot all servers after changing this setting.
UAC can be enabled again after the installation.

Install Docs 1.0.7
IBM Docs 1.0.7 comes with a new graphical installer based on IBM Installation Manager; much easier
than previous versions.
Make sure Connections is running and start Installation Manager.

and go to ../DocsInstallPackage/repository.config and click Open
Click on File / Preferences
Click on Add Repository
Click on Browse..

Now click OK.
In the next screen click OK again.

Now we click on Install.
Select IBM Connections Docs and click Next

Accept the license terms.

The default directory is fine so click Next.

Now you can choose which product you want to integrate Docs with.
Deselect the Docs Proxy Server, as it is only needed, when you have more than one Docs Server.
Click Next.

On the information panel click Next.

Now enter the wasadmin and corresponding password and click on browse.

Go to C:IBMWebSphereAppServerProfilesAppSrv01 and click OK.

Now click 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 (optionally)
the
Web server to webserver1 (or in this example Conn5Node01) by first selecting the nodename and then
the “>>” button at the proper application.

Now we need to scroll down and 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 the credentials in all instances. Then click Validate.

We have selected CCM integration so on the next screen enter the following values:
http://yourservername/fncmis
http://yourservername/dm
the administrative username of Filenet
http://yourservername/communities

We have no chat installed, so we just click Next.

On the DB2 Panel enter the values and then click Next:
Database server: yourservername
User Name: lcuser
Password: yourpassword
Database product: DB2
Database name : CONCORD
JDBC driver Library path : C:IBMSQLLIBjava
Port 50000

The following panel may be a bit confusing when installing everything locally. Fill it out as follows and
click Next:
Switch NFS to CIFS for both Docs and Viewer. For each of the two folder settings use the same ones:
C:IBMDocsShare and C:IBMViewerShare

Now select the path 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 Docs component and click Next.

On the next Panel we don’t need to do anything and can click Next.

Now we need to provide the directories for the Extension and Daemon installation.
For the Extension directory browse to C:IBMConnectionsdatasharedprovisionwebresources .
The Daemon should be installed in C:IBMConnectionsdatashared .
Click Next.

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 do the 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. In our example we choose No for both. Click Next.

Click Next on the configuration file overview panel.

Now you click on Install and grab a coffee or a beer (maybe two) .

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:

Now there is only one last thing to do so that from the next reboot on the two black windows should not
appear anymore.
Go to the Windows Task Scheduler:
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.

We do the same with the sym_monitor: Double click it…
Change it to run whether the user is logged on or not and select Do not store password. Also select
hidden and then OK.

Installing ibm docs on a single server

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Installing ibm docs on a single server

Similaire à Installing ibm docs on a single server (20)

Plus de Roberto Boccadoro

Plus de Roberto Boccadoro (9)

Dernier

Dernier (20)

Installing ibm docs on a single server