Install Quickr 8.5 for WPS - Part 3 (HTTP and LDAP)

Now I will install HTTP server to access Quickr over port 80/443 and configure LDAP (Domino LDAP)

I will use Apache HTTP server from OS installation media

• My CD is mounted under  /media/RHEL_5.8\ x86_64\ DVD/ folder.
• Navigate into the folder #cd /media/RHEL_5.8\ x86_64\ DVD/Server and install httpd rpm
• #rpm -Uvh  httpd-2.2.3-63.el5.x86_64.rpm
• After installation run #service httpd start
• Test port 80 - type your server IP in to browser. You should get apache welcome page 
• No it is time to install WAS plug-in which is used for communication betwen WAS and HTTP server
• Navigate to Quicker Installation Media IL-7.
• #cd /opt/install/IL-7/q850_extras/plugin
• #./install
• Installation wizard will be opened in a graphic mode
• Click NEXT
• Accept license NEXT
• System prerequisites check failed ... do not worry click NEXT
• See notes about this error http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=rhel5cert&uid=swg21260689&loc=en_US&cs=utf-8&lang=en
• Select Apache Web Server V2 and click NEXT
• Select local option
• /opt/IBM/Quickr/Plugins click NEXT
• /opt/IBM/Quickr/AppServer and click NEXT
• /etc/httpd/conf/httpd.conf and port 80 - click NEXT
• leave webserver1 and click NEXT
• Leave plugin-cfg.xml in default ... NEXT
• Check summary and click NEXT, NEXT
• Install will be finished with status: Partial Success. We must configure WAS to use  HTTP server only.
• Install FP for plugin http://www-01.ibm.com/support/docview.wss?uid=swg24031962
• Configure HTTP server in WAS console
• Go to https://<IP>:10041/admin and login
• Navigate to Servers>Web Servers and click NEW
• Step 1 - fill name, type, hostname and os. Click NEXT
• Step 2 - Click NEXT
• Step 3 - Set port 80 and /opt/IBM/Quickr/Plugins and select All. Click NEXT
• Step 4 - click FINISH
• After server is created, click SAVE link abow Web Servers table
• Edit httpd.conf as and chage last 2 lines to have module version ap22 and not ap20
• LoadModule was_ap22_module /opt/IBM/Quickr/Plugins/bin/64bits/mod_was_ap22_http.so
• WebSpherePluginConfig /opt/IBM/Quickr/Plugins/config/webserver1/plugin-cfg.xml
• #service httpd start
• Enable SSL
• install  #rpm -Uvh distcache-1.4.5-14.1.x86_64.rpm
• install  #rpm -Uvh mod_ssl-2.2.3-63.el5.x86_64.rpm
• Edit /etc/httpd/conf/ssl.conf and find line <VirtualHost _default_:443> and add under
•  RewriteEngine On
•  RewriteRule ^/$ /places/login [R]
• Edit /etc/httpd/conf/httpd.conf add this lines on the end of the file

AllowEncodedSlashes On

NameVirtualHost *:443
NameVirtualHost *:80

<VirtualHost *:80>
        ServerName examlpe.ibm.com
        ErrorLog logs/examlpe.ibm.com-error_log
        CustomLog logs/examlpe.ibm.com-access_log common
        RewriteEngine On
        RewriteCond %{HTTPS} off
        RewriteRule (.*) https://%{HTTP_HOST}/places/login
</VirtualHost>

LoadModule was_ap22_module /opt/IBM/Quickr/Plugins/bin/64bits/mod_was_ap22_http.so
WebSpherePluginConfig /opt/IBM/Quickr/Plugins/config/webserver1/plugin-cfg.xml

• Configure Domino LDAP
• goto # cd /opt/IBM/Quickr/wp_profile/PortalServer/wizard
• start graphic wizard #./configwizard.sh
• you will need only actual was admin account, LDAP bind account, hostname of LDAP, LDAP type is Domino 7 even we have 8.5.2.
• I configured LDAP as federated. All other options could be  left in defaults.
• Restart WebSphere_Portal

Install Quickr 8.5 for WPS - Part 2

In this post, I would like to show you how to update Quickr installation before we will configure it.

Most important link for this part is:

Update strategy for IBM Lotus Quickr 8.5 for WebSphere Portal
http://www-01.ibm.com/support/docview.wss?uid=swg21434121

In my case, I am installing on CentOS, I had a problem to run an updateinstaller for WebSphere SW.
The problem is, that install.sh script check OS version from /etc/redhat-release file.
So there are two options how to go around:

• Change redhat-release file to contain a valid RHEL release information 
• Red Hat Enterprise Linux Server release 5.8 (Tikanga)

or

• Change the install script ... comment out line where version variable is set and add new one and set it to value 5. 

After this I was able to run ./install of WebSphere update installer.

Keep in mind, you must add password for wasadmin and portaladmin in to wkplc.properties file!

During installation of Portal FP I get an error because this file has no execute
So after I started installation a changed file as follow. It is important to change it after installer is started

Run commands in this order
./updatePortal.sh -install -installDir "/opt/IBM/Quickr/PortalServer/" -fixpack -fixpackDir "/opt/IBM/Quickr/PortalServer/update/fixpacks/" -fixpackID WP_PTF_6106

& in new terminal run this to change access:


# ls -al /opt/IBM/Quickr/PortalServer/version/actions/PUIAction.sh
-rw-r--r-- 1 root root 1457 Nov 29 16:07 /opt/IBM/Quickr/PortalServer/version/actions/PUIAction.sh

# chmod +x /opt/IBM/Quickr/PortalServer/version/actions/PUIAction.sh


 # ls -al /opt/IBM/Quickr/PortalServer/version/actions/PUIAction.sh
-rwxr-xr-x 1 root root 1457 Nov 29 16:11 /opt/IBM/Quickr/PortalServer/version/actions/PUIAction.sh

! The same thing I did during Quickr CF8 ... because there was exactly the same problem.


After portal FP installation, there is a error every time you run a portalupdateinstaller or a WPVersionInfo.sh.
There is a typo in this files:
/opt/IBM/Quickr/PortalServer/version/prereq.wcm.webdav.component
/opt/IBM/Quickr/PortalServer/wcm/prereq.wcm.fp615/version/prereq.wcm.webdav.component

build-version="Build CF51 51.0.4"prereq.wcm.webdav"
Correct one is as a follow:
build-version="Build CF51 51.0.4" name="prereq.wcm.webdav"

After two day of work it is done ... BLUE HELL?!

Install Quickr 8.5 for WPS - Part 1

Useful links - Quickr 8.5  for WebSphere Portal on CentOS 64bit

First some useful links:

• Download document: http://www-01.ibm.com/support/docview.wss?uid=swg24026635
• Product Documentation: http://www-10.lotus.com/ldd/lqwiki.nsf/xpViewCategories.xsp?lookupName=Lotus%20Quickr%208.5%20for%20WebSphere%20Portal%20documentation

I downloaded following installation packages: 

CZHX4ML	IBM Lotus Quickr 8.5 for WebSphere Portal Install (Setup) ML Optional: Required if installing optional product IBM Lotus Quickr 8.5
CZHY0ML	IBM Lotus Quickr 8.5 for WebSphere Portal - WP 1 of 3 (A-3, IL-3, W-3, ZL-3) ML Optional: Required if installing optional product IBM Lotus Quickr 8.5
CZHY1ML	IBM Lotus Quickr 8.5 for WebSphere Portal - WP 2 of 3 (A-4, IL-4, W-4, ZL-4) ML Optional: Required if installing optional product IBM Lotus Quickr 8.5
CZHY2ML	IBM Lotus Quickr 8.5 for WebSphere Portal - WP 3 of 3 (A-5, IL-5, W-5, ZL-5) ML Optional: Required if installing optional product IBM Lotus Quickr 8.5
CZHY3ML	IBM Lotus Quickr Connectors 8.5 Multiplatform Multilingual (A-6, IL-6, W-6, ZL-6) Optional: Required if installing optional product IBM Lotus Quickr 8.5. Required for installation on all platforms but supported only on Windows
CZHY6ML	IBM Lotus Quickr 8.5 for WebSphere Portal - WebSphere Application Server Network Deployment for Linux 64-bit (IL-1) Multilingual Optional: Required if installing optional product IBM Lotus Quickr 8.5
CZHY7ML	IBM Lotus Quickr 8.5 for WebSphere Portal - DB2 Enterprise Server Edition for Linux 64-bit (IL-2) ML Optional: Required if installing optional product IBM Lotus Quickr 8.5
CZHY8ML	IBM Lotus Quickr 8.5 for WebSphere Portal WAS Extras Linux 64-bit (IL-7) ML Optional: Required if installing optional product IBM Lotus Quickr 8.5

• Installation scenario is standalone server (all-in-one) 
• My configuration is: 
• 5GB RAM
• 100HDD
• 2 CPU
• VMware platform
• CentOS release 5.8 (Final) 64bit / it is not supported by IBM ... but who care? (May be only IBM support will)
• Domino as LDAP / already installed on different server

OS installation and Quickr pre-installation tasks

1. Install OS with gui (Gnome/KDE) make your own choose and
2. disable SELinux + Firewall during installation process.
3. Log in as root and install vmware tools (if you are on vmware platform)
4. You will need a libstdc++.so.5 to install DB2 so run as root 
1. #yum install compat-libstdc++-33
5. Update your OS installation - run as root:
1. #yum update
6. change limits - run as root
1. #ulimit -n 40000
2. #vim /etc/security/limits.conf
1. add line  "*                -       nofile          40000"
2. and save the file by ESC + :x
7. Try to ping your FQDN ... if its not resolve rout name edit /etc/hosts file and add line with your IP and your FQDN 
1. Note: Use #ifconfig command to find your IP
8. Create installation folder structure to prevent installer asking for installation CDs
1. #mkdir -p /opt/install/IL-Setup
2. #mkdir /opt/install/IL-1
3. repeat  command 2. to create IL-2 to IL-7
4. Extract each installation package into the correct folder you just created.
1. Note: See the table on the top of this page 
2. Use #unzip <filename.zip> to extract each package
3. Note: To install zip/unzip run #yum install unzip

Run quicker Installer

1. Run as root user
1. # cd /opt/install/IL-Setup/
2. # ./install.sh -console
1. I am running installer in text mode so adding parameter -console
3. Installer will be started in console mode. Here is what I select during installation
1. English
2. Accept Licence
3. Single Server
4. DB2
5. /opt/IBM/Quickr
6. quickernode
7. my FQDN
8. quikradm
9. my password

-------------------------------------------------------------------------------

IBM Lotus Quickr is ready to install.

To change any settings, choose Back. If you are satisfied with the settings

choose Next to begin copying files.

Products to install:

IBM Lotus Quickr 8.5 installation location:

/opt/IBM/Quickr

Installation details:

Host name: extranet.mydomain.com

Node name:  quickernode

User ID: quikradm

IBM Lotus Quickr 8.5 profile location:

/opt/IBM/Quickr/wp_profile

Total size on disk: 8 GB

If installer failed and you will run installer again, you must first delete all lines from /root/vpd.properties and delete all from /opt/IBM. Do it only if you do NOT have installed any other IBM SW on the server.

-------------------------------------------------------------------------------
Installation was successful.

IBM Lotus Quickr is now installed on your computer. Installation and
configuration details can be found in /opt/IBM/Quickr/PortalServer/log.

The IBM Lotus Quickr page is now available at
http://extranet.praha1.cz:10040/lotus/quickr.

Installation details:

IBM Lotus Quickr 8.5 installation location:

/opt/IBM/Quickr

Host name: extranet.praha1.cz

Node name:  quickrnode

User ID: quikradm

IBM Lotus Quickr 8.5 profile location:

/opt/IBM/Quickr/wp_profile

Total size on disk: 8 GB

Startup Script for IHS on RHEL

Today I'm going to show you how to setup IHS to run after boot/reboot on RHEL.

• First you need to know what is your default runtime level. To determinate default level see your inittab file:
• [root@ic ~]# less /etc/inittab
• find line start with id:< some number >:initdefault:
• In my case I have level 3 as default:
• id:3:initdefault:
• As root, create a new file ihs in  /etc/init.d/
• [root@ic ~]# vim /etc/init.d/ihs 

#!/bin/bash

# SERVICENAME should match this filename

SERVICENAME=$(basename $0)

LOCKFILE="/var/lock/subsys/${SERVICENAME}"

APACHECTL=/opt/IBM/HTTPServer/bin/apachectl

# The next lines are for chkconfig on RedHat systems.

# chkconfig: 2345 98 02

# description: Starts and stops IHS 

case "$1" in

  start)

    touch $LOCKFILE 

    ;;

  stop)

    rm -f $LOCKFILE

    ;;

  *)

    echo "Usage: $0 {start|stop|status|restart}"

    exit 1

    ;;

esac

$APACHECTL "$@"

• Save file and add executable mark to be able to run the script:
• [root@ic ~]# chmod u+x /etc/init.d/ihs
• Now add new service and set up if to run on level 3
• [root@ic ~]# chkconfig --add ihs
• [root@ic ~]# chkconfig --level 3 ihs on

IBM Connection 3.0.1.1 update to CR1

See my notes from installing Cumulative Refreshe 1  (CR1)

I did not make any changes in themes or other LC files so I do not need to backup them, before installation.

IBM page with CR1: http://www-304.ibm.com/support/docview.wss?uid=swg21595154&myns=swglotus&mynp=OCSSYGQH&mync=E

1. It is good idea to make a shapshot of your servers (I made snapshots for my DB and WAS server)
2. I started DB server and DMGR ... it must be started during installation
3. I used latest Update installer Download Update Installer 3.0.1.x-IC-Multi-UPDI-20120403 (downloaded from IBM FixCentral).
4. Ok, after you download Update Installer, delete or backup /opt/IBM/LotusConnections/updateInstaller and extract updateinstaller in  /opt/IBM/LotusConnections/ - it will make folder updateinstaller again. 
5. Download all (depends what parts of LC did you install) CR jar/zip files in to /opt/IBM/LotusConnections/updateInstaller/fixes. If there are any zip, extract them.
6. To run /opt/IBM/LotusConnections/updateInstaller/updateWizard.sh add execute permissnion on this file
1. [root@ic ~]# cd /opt/IBM/LotusConnections/updateInstaller
2. [root@ic updateInstaller]# chmod +x updateWizard.sh
3. Make sure you have xserver started - you will be able to run graphic installation wizard.
4. Setup was home path: [root@ic updateInstaller]# cd /opt/IBM/WebSphere/AppServer/bin
5. Run: [root@ic bin]#. ./setupCmdLine.sh
6. [root@ic updateInstaller]# cd -
7. [root@ic updateInstaller]# ./updateWizard.sh
7. Update Wizard for Lotus Connections 3.0.1.1 will be launched. 
1. Click NEXT
2. Select Install updates and make sure there is path in to folder with jar files sfom step 5.
3. Click NEXT, on Update Selection page, depends on your installation, select what you want to install (In my case wizard selected all). Click NEXT.
4. I selected "I have not made any changes to IBM Connections application files." >> OK
5. Fill in your DMGR admin account and password. Click NEXT and wait for Validation success >> Click OK
6. Click INSTALL and go with your dog for a walk ... it will take some time to install.
7. After successful update installation start all nodes and node agents and perform a full synchronization to push the update to all nodes. 

How to hide an required attribute in self-care portlet?

Our customer wants to hide all field except password field in self-care portlet. They do not use self-registration, but they only want to be able to change a user password from self-care portlet.

The solution is quite easy - you can disable fields in config mode of self-care portlet directly.
But how to disable/hide required fields from the portlet? They are inactive - so administrator can not disable them.

First you have to remove required attributes from store.puma_default.user.add.required.attributes properties.

1.  Log in to the IBM WebSphere® Integrated Solutions Console (ISC). 
2. Go to Resources >> Resource Environment >> Resource Environment Providers
3. Click on the link for WP PumaStoreService. Under "Additional properties" click on "custom properties"
4. Click on the link for "store.puma_default.user.add.required.attributes" 
5. Delete all from value field
6. Save and restart portal :( 
7. Then go again in to config mode and disable all remaining attributes.

Actualy some fields are disabled because they are required fields in PUMA (user management), and cannot be removed. To hide them, it is easiest way to edit JSP which render self-care form. I added only display: none css for sn attribute part of form.

Edit file
/opt/IBM/WebSphere/wp_profile/installedApps/Node01/PA_Selfcare_Port_App.ear/selfcare.war/WEB-INF/jsp/UserInformationFormInclude.jspf


    <tr style="display:none;">
        <td align="<%=bidiAlignRight%>">
            <% if (requiredUserAttributes.contains(SelfcareConstants.LAST_NAME_FIELD_ID)) { %> * <% } %>
        </td>
        <td align="<%=bidiAlignLeft%>" class="wpsEditText">
            <label for="<%= SelfcareConstants.LAST_NAME_FIELD_ID %>">
                <fmt:message key="selfcare.label.last_name"/>
              <% if (isRequiredAttr) { %><span style="display:none"><fmt:message key="selfcare.label.required_attr"/></span> <% } %>
            </label>
        </td>
    </tr>
    <tr style="display:none;">
        <td>&nbsp;</td>
        <td>
            <input <%=bidiDirAttr%>
                   class="wpsEditField" 
                   type="text" 
                   id="<%= SelfcareConstants.LAST_NAME_FIELD_ID %>" 
                   name="<%=SelfcareConstants.USER_ATTRIBUTE_PREFIX%><%= SelfcareConstants.LAST_NAME_FIELD_ID %>" 
                   value='<% escapeXmlWriter.write(sn);%>'
                   onkeyup="javascript:updateDisplayName();return;" >
        </td>
        <td class="wpsFieldErrorText">
        </td>
    </tr>

Delete temp folder

/opt/IBM/WebSphere/wp_profile/temp/Node01/WebSphere_Portal/PA_Selfcare_Port_App

 and reload page with self-care portlet

IBM Connections - CLFRW0493E: Unable to start the document indexing service

I found in IBM Connectios 3.0.1.1 log this error:


000014ef DocumentIndex E com.ibm.lotus.connections.search.service.files.impl.DocumentIndexingServiceImpl isEnvironmentValid CLFRW0493E: Unable to start the document indexing service, please ensure that the PATH environment variable has been set.

After some Googling, I found this post where author set up paths as follows:

export PATH=/opt/IBM/LotusConnections/data/search/stellent/dcs/oiexport:$PATH
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/LotusConnections/data/search/stellent/dcs/oiexport


Sinc I have only one node cluster I will use path containing shared folder:


export PATH=/opt/IBM/LotusConnections/data/shared/search/stellent/dcs/oiexport:$PATH
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/LotusConnections/data/shared/search/stellent/dcs/oiexport


So I edited /opt/IBM/WebSphere/AppServer/bin/setupCmdLine.sh and added this two lines on the end of the file. I stopped websphere/connections and servers OS too.

How to change notification e-mail sender address - IBM Connections

How to change notification e-mail sender address - IBM Connections

You must export notification-config.xml file and edit email information in it and import file in to configuration again.

• [root@ic bin]# cd ../profiles/Dmgr01/bin/
• [root@ic bin]# ./wsadmin.sh -lang jython
• wsadmin>execfile("connectionsConfig.py")
• wsadmin>LCConfigService.checkOutNotificationConfig("/root/","icCell01")
• change email in exported xml file ans import it again
• wsadmin>LCConfigService.checkInNotificationConfig("/root/","icCell01")
• wsadmin>synchAllNodes()
• wsadmin>quit

IBM Connections - Duplicate headers recivied from server error

There is bug when you using Chrome and try to download any file from IBM Connections 3.0.1:

Browser error:
Duplicate headers recivied from server


Problem is in not valid (RFC) header, which including a ","  but there should be a ";" 



Response.AddHeader("Content-Disposition", "attachment, filename=\"" + filename + "\"");
Response.AddHeader("Content-Disposition", "attachment; filename=\"" + filename + "\"");

Fast solution is to put directive command in to Apache/IHS httpd.conf file:

Header edit Content-Disposition ^(.*)creation-date=(.*);\smodification-date=(.*);$ "$1creation-date=\"$2\"; modification-date=\"$3\";"



Or install IBM Connections 3.0.1 FixPack 1

IBM Connections 3.0.1 and iPad/iPhone native application

Hi there,

After I installed IBM Lotus Connections, I tried to install  native application for iPad - IBM Connections 3.1.1. The installation was easy, I fill my connection server hostname, my user name and password, after this I got an error:

The URL <hostname> is not a valid IBM Connections Mobile server.

I sent a logs file from my iPad (click on Info icon under the login form and click Send Logs) You will get it by email.

In log I found root problem:
"Received response. HTTP response http://<hostname>/homepage/Configuration Status: 404 (not found)"

And the solution is:
install this FixPack and Interim Fix

refresh pack: 3.0.1.0-IC-Multi-UPDI-20120220 (61.41 MB)

refresh pack: 3.0.1.0-IC-Multi-Mobile-IFLO67638 (12.28 MB)

1. Stop a cluster from WAS integrated solition console or from a command line
2. [root@ic updateInstaller]# cd /opt/IBM/WebSphere/AppServer/bin/
3. [root@ic bin]# . ./setupCmdLine.sh
4. [root@ic bin]# cd /opt/IBM/LotusConnections/
5. [root@ic LotusConnections]# mv updateInstaller/ updateInstaller-old/
6. [root@ic LotusConnections]# mv /opt/install/FIX/3.0.1.0-IC-Multi-UPDI-20120220.zip .
7. [root@ic LotusConnections]# unzip 3.0.1.0-IC-Multi-UPDI-20120220.zip
8. [root@ic LotusConnections]# cd updateInstaller/
9. [root@ic updateInstaller]# cd fixes/
10. [root@ic fixes]# mv /opt/install/FIX/3.0.1.0-IC-Multi-Mobile-IFLO67638.zip .
11. [root@ic fixes]# unzip 3.0.1.0-IC-Multi-Mobile-IFLO67638.zip
12. [root@ic /]# cd /opt/install/FIX/updateInstaller/
13. [root@ic updateInstaller]# chmod +x update*
14. [root@ic updateInstaller]#./updateWizard.sh
15. Select option: Install Updates > click NEXT > select our fix > click NEXT > enter administrator user name and password > and continue to install it.
16. After resynchronize all nodes and the start cluster

IBM Connections 3.0.1 on RHEL - how to install - 9. Post-Installation Tasks

Post-Installation Tasks

Finally, we have installed IBM Lotus Connections product, but there are some more important post installation steps! Lets go to finish them!

1. Configure HTTP server
1. Open  http://ic.ys.cz:9060/admin and log in as wasadmin
2. [root@ic bin]# cd /opt/IBM/HTTPServer/bin/
3. start Administration server: [root@ic bin]# ./adminctl start
4. Create new node to manage http server with dmgr server ... navigate to System administration > Nodes > click Add Node 
1. select  Unmanaged node click NEXT
2. Name: webserver1node
3. HostName: <FQDN>
4. Platform Type: Linux > OK > SAVE
5. Go to create a new WebServer definition ... navigate to Servers > Server Types > Web servers > and click New
1. Select node: webserver1node
2. Server name: webserver1
3. Type: IBM HTTP Server
4. Click NEXT > NEXT
5. Port: 80
6. Web server installation root: /opt/IBM/HTTPServer
7. Plug-in installation root: /opt/IBM/HTTPServer/Plugins
8. Administration Server Port: 8008
9. Username: ihsadmin
10. Password: <yourpass>
11. Confirm password:  <yourpass>
12. Click NEXT
13. Click FINISH ans SAVE
6. Check webserver1 checkbox and click Start button - it should start the server. If not you can reset password:
1. Switch to the HTTPServer_installdir/bin directory on your machine.
2. Type the following command:
3. ./htpasswd -b ../conf/admin.passwd user password
4. where user and password are the user ID and password that you want to have administrative authority for IBM HTTP Server. 
7. Resynchronize all nodes.
8. Generate plug-in configuration file ... navigate again to the webservers (same as step 5).
1. Select webserver1 and click Generate Plug-in and them click Propagate Plug-in
2. Note: Make sure, you will see in a Message dialog box same path to plugin-cfg.xml as is in IHS httpd.conf (last line of the file) file saved in /opt/IBM/HTTPServer/conf/httpd.conf 
   
3. Restart webserver
9. Navigate to Servers > Web servers > webserver1 > Plug-in properties and click Copy to Web server key store directory
10. Setup HTTP over SSL with self signed certificate
1. [root@ic ~]# cd /opt/IBM/HTTPServer/
2. [root@ic ~]# mkdir  keyfiles
3. [root@ic ~]# cd bin
4. [root@ic bin]# ./ikeyman
5. In IBM Key Management click New
1. Key database type: CMS
2. File Name: webserver-key.kdb
3. Location: /opt/IBM/HTTPServer/keyfiles
4. Click OK
5. Enter your password and select Stash password to a file
6. Click OK
6. In IBM Key Management click Create a new self-signed certificate
1. Key Label: LC Self Signed
2. Version: X509 V3
3. Key Size: 1024
4. Signature Algorithm: SHA1WithRSA
5. Other options are optional (set them as you wish) 
6. Click OK and close ikeyman
7. Stop HTTP server and edit httpd.conf file
1. [root@ic bin]# cd ../conf/
2. backup file: [root@ic conf]# cp httpd.conf httpd.conf.bak
3. Edit file and add following lines to the bottom of the file:
   LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
   <IfModule mod_ibm_ssl.c>
     Listen 0.0.0.0:443
     <VirtualHost *:443>
       ServerName ic.ys.cz
       SSLEnable
     </VirtualHost>
   </IfModule>
   SSLDisable
   Keyfile "/opt/IBM/HTTPServer/keyfiles/webserver-key.kdb"
   SSLStashFile "/opt/IBM/HTTPServer/keyfiles/webserver-key.sth"
   
4. start HTTP server and test https url on port 80
1. [root@ic conf]# ../bin/apachectl -k start
2. Open browser and go to https://<yourhostname>
3. You should get info about certificate - it is not a trusted certificate (because it is self-signed certificate)
8. Add our cert among trusted ones in WAS Trust Store
1. Navigate in Security > SSL Certificate and Key Management > Key stores and certificates
2. Click on link  CellDefaultTrustStore
3. Click on link Signer certificates
4. Click Retrieve from port
1. Host: <IHS hostname>
2. Port: 443
3. Alias: webserver-ssl
4. And click Retrieve signer information
5. Check if it is correct
6. OK > SAVE
11. Update Connections URL to use SSL
1. [root@ic conf]# cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/
2. [root@ic bin]# ./wsadmin.sh -lang jython
3. wsadmin> execfile("../config/bin_lc_admin/connectionsConfig.py")
4. wsadmin> LCConfigService.checkOutConfig("/root/","icCell01")
• Note: Make sure that you have correct cell name in command
5. Edit exported file and delete all occurrences of port in href or ssl_href
1. I deleted all occurrences of  :9081 and :9444 in the file.
6. Run wsadmin> LCConfigService.checkInConfig()
7. Run wsadmin> synchAllNodes()
12. You no what? You are done! Congratulations!  now you can take a look in to documentation how to tuneup your Connections

IBM Connections 3.0.1 on RHEL - how to install - 8. Install Connections

Create IBM Connections DBs

Here we will prepare DB and populate profiles from LDAP
You will need:

• CZVR1ML  IBM Connections 3.0.1 wizards for Linux x86
• CZVQ0ML IBM Connections 3.0.1 for Linux x86
• CZVQ0ML  IBM_Connections301_LinAIX_CZVQ0ML.tar

1. On database server save these package
1. Create folder: [root@icdb ~]# cd /opt/install/
2. [root@icdb install]# mkdir LCWizards
3. [root@icdb install]# cd /opt/install/LCWizards
4. [root@icdb LCWizards ]# tar xvf IBM_Connection301_Wzd_zLinux_CZVR1ML.tar
2. Log-in as db2inst1 (in to graphic xserver)
1. [root@db2inst1 ~]# cd /opt/install/LCWizards/Wizards/
2. [root@db2inst1 ~]# ./dbWizard30.sh
1. Wizard is open click NEXT > select Create click NEXT > 
2. in Default installation location: /opt/ibm/db2/V9.7
3. in database instance: db2inst1 > NEXT
4. Select all > NEXT > CREATE > EXECUTE
5. All DBs should finished without no errors, is there any error, try to run the wizard again and select only DB where your error occurred. Note: In my installation I had some error during Bookmarks db creation, so I run wizard again only for Bookmarks DB with success.
3. We will populate Lotus Connections Profiles from the Domino LDAP directory in next steps:
1. As root user, go to 
2. [root@icdb ~]# /opt/install/LCWizards/Wizards
3. [root@icdb  Wizards]#./populationWizard.sh
4. Profile population wizard is launched
1. Click NEXT
2. Select DB2 Universal Database(TM)
3. In Profiles database properties set
1. Host name: icdb.ys.cz  - it is hostname of your db server
2. Port: 50000
3. Database name: PEOPLEDB
4. JDBC driver library path: /home/db2inst1/sqllib/java
5. User ID: db2inst1
6. Password: <db2inst1 password>
7. Click NEXT
4. In LDAP server connection
1. LDAP server name: <your ldap hostname>
2. LDAP server port: 389
3. Do not check Use SSL communication if it is not configured on LDAP
4. Click NEXT
5. LDAP autentication propertise
1. Bind distinguished name (DN): bind user  / do not put name in format CN=<name>,O=<org>,C=<country>
2. Enter bind password
3. Click NEXT
6. In Base distinguished name and filter for search  enter:
1. LDAP user search base: c<yourcompany>,o=cz
2. LDAP user search base: (&(uid=*)(objectclass=inetOrgPerson))
3. Click NEXT
7. In Profile database mapping leave all in default, or change mapping as you need. Click NEXT
8. In Optional database tasks  leave all in default, or change as you need.
1. select Yes to run the task
2. Click NEXT 
9. Click CONFIGURE
10. Summary could contain some errors ... to determinate what is going on see logs in /opt/install/LCWizards/Wizards/TDIPopulation/TDISOL/linux/logs/PopulateDBFromDNFile.log  or in ibmdi.log

In my case, I had 23 success, 116 duplicate records  (because I run it again - so db table already had users 116 entries), and there is  one failure record (after some investigation, I found there is a wrong value in my Domino filed named "Office Number"). 

I had this in my PopulateDBFromDNFile.log :

CLFRN0209W: WARNING: Validation failed for field officeName. Value is BlablalaSomethingLongerThan32Characters

WARNING: Validation failed for entry CN=Tomas Marny,ou=kotelna,o=ys,c=cz

The value is longer then created column for  officeName  in DB2 ... PROF_PHYSICAL_DELIVERY_OFFICE   is   VARCHAR   with Length 32

To show database description run as db2inst1 this command

• [root@db2inst1 ~]# db2
• db2 => connect to database peopledb
• db2 => describe table empinst.employee

Install IBM Lotus Connections

You should have done: 

• Installed and fixed DB2 server v9.7.0.2
• Installed TDI
• Installed WAS 7.0 with FP 19 and IHS and plugin too 
• WAS is configured with LDAP (federated repositories)
• Configured DB2 
• You must have already populated LDAP profiles to DB2 database
• It is good idea to make a backup of servers
• Now we will install Lotus Connections

1. Start dmgr and node agent
2. login to application server as root and 
1. [root@ic ~]# /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/startManager.sh 
2. [root@ic ~]# /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/startNode.sh
3. Try to ping your db server ... if you are unable to resolve db server hostname, add in to /etc/hosts a new line <ip od db server> <FQND> <hostname> and save file. Try again.
4. Copy JDBC drivers from db server to application server
1. [root@ic ~]# cd /opt/IBM/
2. [root@ic ~]# mkdir JDBC
3. [root@ic IBM]# cd JDBC/
4. [root@ic JDBC]# scp -r root@192.168.50.128:/home/db2inst1/sqllib/java/* .
5. Start Connection installer
1. On application server unpack installer package 
2. [root@ic CONN]# tar xvf IBM_Connections301_LinAIX_CZVQ0ML.tar
3. [root@ic CONN]# cd Lotus_Connections_Install/
4. [root@ic Lotus_Connections_Install]# ./launchpad.sh
5. In launchpad click Install Lotus Connection 3.0.1
1. Click Launch the Lotus Connection 3.0.1 install wizard
2. Ensure that Lotus Connection and  Installation Manager are selected
3. Click NEXT and click agree license > NEXT
4. Leave Install Packages in default (/opt/IBM/...) click NEXT > click NEXT
5. Install all Features click NEXT
6. Websphere applicatiopn server configuration 
• Click Browse and  select /opt/IBM/WebSphere/AppServer/
• Select Dmgr01
• Enter hostname of application server 
• Enter Administrator user ID: wasadmin
• Enter Administrator password: <your password>
• SOAP port number: 8879
• Click Validate > in Validation successful dialog Click OK
• Click NEXT
7. Topology Configuration
1. Select SmallDeployment - for production it is recommended to use Medium or Large Deployment
2. Write in to select list Cluster Name: LCCluster
3. In Node selection Select your node
4. Click NEXT
8. Database Configuration
1. Enter Database server hostname: <your db host name>
2. Port: 50000
3. Specify JDBC Driver to folder from previous step 4 (/opt/IBM/JDBC)
4. Specify users and  passwords for all DBs (we used db2inst1 user)
5. Click Validate > in Validation successful dialog Click OK
6. Click NEXT
9. Content Store Configuration
1. Leave in defaults and click Validate
10. Notification configurations
1. We will used our Domino as SMTP server too. Configure your SMTP and click NEXT
11. See summary and click INSTALL
1. You can watch detailed log:  /opt/IBM/LotusConnections/logs/
2. After about 30-60 min it should finished vith success and click FINISH
6. Go to  http://ic.ys.cz:9060/admin
1. Navigate to  System administration > Nodes > check icNode01 and click Full Resynchronize
1. to watch status  
2. [root@ic bin]# tail -f /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/SystemOut.log
7. Restart DMGR
1. [root@ic bin]# /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/stopNode.sh
2. [root@ic bin]# /opt/IBM/WebSphere/AppServer/bin/stopManager.sh
3. [root@ic bin]# /opt/IBM/WebSphere/AppServer/bin/startManager.sh
4. [root@ic bin]# /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/startNode.sh

Next post is about important post-installation tasks

IBM Connections 3.0.1 on RHEL - how to install - 7. Connect Domino LDAP

In our infrastructure, we already have Domino server installed, so here I am going to show how to configure Federated Repository (add Domino LDAP).

What you will need:

• You must know FQND or IP of your Domino server
• LDAP port 389 as standard
• If your LDAP need to authenticate to reed content, you mast know some account DN and password - this will be used as bind user to bind in to LDAP
• You should have installed WAS (see previous posts)

1. Show status of dmgr server 
1. [root@ic bin]# cd /opt/IBM/WebSphere/AppServer/bin/
2. [root@ic bin]# ./serverStatus.sh -all -user wasadmin -password Pass4conn
3. If it is not started already, run: 
1. [root@ic bin]# cd /opt/IBM/WebSphere/AppServer/bin/startManager.sh
4. Backup your  wimconfig.xml file before doing any changes in the federated repository configuration
1. [root@ic bin]# cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/icCell01/wim/config/
2. [root@ic config]# cp wimconfig.xml wimconfig.xml.bak
5. Open web browser and go to  http://<hostname>:9060/admin  
6. Login with administrator account wasadmin and your password
1. go to Security > Global security  and in User account repository click Configure... button
2. In Repositories in the realm table click Add Base entry to Realm...
3. Click Add Repository and fill
1. Repository identifier (enter MyLDAP)
2. Select Directory type: IBM Lotus Domino
3. Enter Primary host name of your domino server
4. If you need bind enter bind and password
5. In Login properties you can add more options to login, I added email so there is uid;mail in the field
6. Click OK  and enter in to field with label:  Specifies the Lightweight Directory Access Protocol (LDAP) distinguished name (DN) that uniquely identifies this set of entries in the realm root of your Domino LDAP ... I have o=ys,c=cz
7. Click OK and SAVE
4. Restart dmgr server:
1. [root@ic bin]# /opt/IBM/WebSphere/AppServer/bin/stopManager.sh -user wasadmin -password Pass4conn
2. [root@ic bin]# /opt/IBM/WebSphere/AppServer/bin/startManager.sh -user wasadmin -password Pass4conn
5. Login again in to web Integrated Solutions Console
1. Navigate in to Users and Groups > Manage Users
2. Click on Search button. If the expected set of users is returned then LDAP is configured correctly! Make the same for groups and be sure that members of groups are correct.
6. Setup SSO
1. Go to Security > Global security in Authentication expand Web and SIP security and click Single sign-on (SSO)
2. enter  .ys.cz ... so .<domain>.com  It must start with a dot and continue with domain
3. Check  Interoperability Mode
4. OK and SAVE
5. Go to Security > Global security and click on Enable application security 
6. OK and SAVE
7. Sync nodes
1. [root@ic bin]# cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
2. [root@ic bin]# ./syncNode.sh ic.ys.cz 8879 -username wasadmin -password <your password>

Ok now we will go to Populate Profiles from the LDAP into DB2 tables.

IBM Connections 3.0.1 on RHEL - how to install - 6. Fix WAS, IHS and Plug-in

Because IBM Connections needs to have specific WebSphere Application Server fix pack level (5 or 19), (as you can see in supported HW and SW document) we will install them in this post.

You will need following FixPacks

• UpdateInstaller - ftp://public.dhe.ibm.com/software/websphere/appserv/support/tools/UpdateInstaller/7.0.x/LinuxPPC64/7.0.0.21-WS-UPDI-LinuxPPC64.tar.gz
• JAVA SDK FP 19 - ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixpacks/was70/cumulative/cf70019/LinuxX64/7.0.0-WS-WASSDK-LinuxX64-FP0000019.pak
• WAS FP 19 - ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixpacks/was70/cumulative/cf70019/LinuxX64/7.0.0-WS-WAS-LinuxX64-FP0000019.pak
• IHS FP 19 - ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixpacks/was70/cumulative/cf70019/LinuxX64/7.0.0-WS-IHS-LinuxX64-FP0000019.pak
• Plug-in FP 19 - ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixpacks/was70/cumulative/cf70019/LinuxX64/7.0.0-WS-PLG-LinuxX64-FP0000019.pak

You can download all these parts from 7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux, and UpdateInstaller from http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24020446

1. Create new dir on your application server
1. [root@ic install]# mkdir WASFix/
2. Download all FPs running command for each:
3. [root@ic WASFix]# wget <url from above list>
4. After you will get all FPs, you shold see
5. [root@ic WASFix]# ls -al
   drwxr-xr-x 2 root root      4096 Apr  3 17:53 .
   drwxr-xr-x 7 root root      4096 Apr  3 17:38 ..
   -rw-r--r-- 1 root root 110619051 Apr  3 17:57 7.0.0.21-WS-UPDI-LinuxAMD64.tar.gz
   -rw-r--r-- 1 root root  26391437 Apr  3 17:44 7.0.0-WS-IHS-LinuxX64-FP0000019.pak
   -rw-r--r-- 1 root root  43223029 Apr  3 17:48 7.0.0-WS-PLG-LinuxX64-FP0000019.pak
   -rw-r--r-- 1 root root 701712259 Apr  3 18:52 7.0.0-WS-WAS-LinuxX64-FP0000019.pak
   -rw-r--r-- 1 root root  88257374 Apr  3 17:54 7.0.0-WS-WASSDK-LinuxX64-FP0000019.pak total 948444
   
   
6. Make sure, all app servers are shouldtown
1. To stop DMGR run:
2. [root@ic WASFix]#  /opt/IBM/WebSphere/AppServer/bin/stopManager.sh -user wasadmin -password <your password>
3. Make a new folder UPDI under the WASFix folder for extracting the Updateinstaller, and extract it:
4. [root@ic UPDI]# tar xvfz 7.0.0.21-WS-UPDI-LinuxAMD64.tar.gz
5. [root@ic UPDI]# cd UpdateInstaller
6. [root@ic UPDI]# ./install
1. Installation wizard is opend, click NEXT
2. Accept license and click NEXT
3. System prerequisites check should Passed > NEXT
4. Leave direcotry path in default (/opt/IBM/WebSphere/UpdateInstaller) > NEXT > NEXT to install
5. After Installation Complete with status Success > Click FINISH
6. The UpdateInstaller will be launched
7. [root@ic UPDI]# mkdir /opt/IBM/WebSphere/UpdateInstaller/maintenence
8. [root@ic UPDI]# cd ..
9. [root@ic WASFix]# mv 7.0.0-WS-* /opt/IBM/WebSphere/UpdateInstaller/maintenance/
10. Go back in to launched UpdateInstaller click NEXT
11. In Product Selection Select AppServer (opt/IBM/WebSphere/AppServer) and click NEXT
12. Select Install maintenence package and click NEXT
13. In Maintenence Package Directory Selection leave default (it should be  /opt/IBM/WebSphere/UpdateInstaller/maintenance/) click NEXT 
14. WASSDK and WAS package should be preselected, click NEXT
15. Do not select Verify my permissions and click NEXT, after a few minutes, our installation should finished with Success status:
    
16. Click RELAUNCH and install fixpacks for IHS and Plug-in - go over 11. to 15 but select in 11. IHS and then Plug-in. 

Actually I was little confused when I tried to install IHS and Plug-in fixpacks. First there is a mistake in IBM Connections 3.0.1 download document. Part Numbers are wrong for 64bit versions of Supplemental packages. Anyway I download the correct ones ... 64bit WAS Supplemental 1 and 2 are C1G36ML and  C1G37ML and not C1G33ML and C1G34ML. But after I installed IHS from 64bit package, command for determining installed version show 32bit again! You can run it as /opt/IBM/HTTPServer/bin/versionInfo.sh
I am afraid there is mistake in versioninfo.sh, because I successfully installed WASJDK, IHS and Plugin FixPack 19 x64 over this IHS and Plug-in also.

We've now finished the “pre-requisite” software install part - all the foundational software we need for Connections is now in place.

Go to next post to configure federated repository with Domino LDAP.

IBM Connections 3.0.1 on RHEL - how to install - 5. Tivoli Directory Integrator

A content of this post is about installing Tivoli Directory Integrator 7.0 which will be used in IBM Connections instalation.


You will need:
installation packages

• C1IF4ML IBM Tivoli Directory Integrator V7.0 for Linux IA-64​
• IBM Tivoli Directory Integrator 7.0 Fix Pack 5 - 7.0.0-TIV-TDI-FP0005 can be downloaded from ftp://dispsd-8.boulder.ibm.com/ecc/sar/CMA/TIA/00zbo/1/7.0.0-TIV-TDI-FP0005.zip, or from 

and already installed RHEL 5.4 server with graphic environment.

Documentation TDI 7.0
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_7.0/welcome.htm

Server FQDN: icdb.ys.cz

TDI installation + FixPack 5 installation

1. Log in as root and create TDI folder for installation package
1. [root@icdb ~]# mkdir /opt/install/TDI
2. [root@icdb ~]# chmod 777 /opt/install/TDI
3. Download or copy  C1IF4ML.tar  in to created folder TDI
4. [root@icdb TDI]# cd  /opt/install/TDI/
5. [root@icdb TDI]# tar xvf C1IF4ML.tar
6. [root@icdb TDI]# ./launchpad.sh
1. Launchpad window is opened 
2. Click to Install IBM Tivoly Directory Integrator in left menu
3. Click Tivoli Directory Integrator 7.0 installer
4. Select your preferred language
5. Click NEXT > NEXT > Accept license > NEXT
6. Leave installation directory in default
7. Select Typical installation > NEXT
8. Select Do not specify > NEXT
9. Leave ports in default
• HTTP: 13100
• HTTPS: 13101
• Action manager API: 13104
10. NEXT  > NEXT >
11. Summary will appear > INSTALL
12. Uncheck Start the Configuration Editor > FINISH
2. Apply TDI FixPack 5 - supported by IBM Lotus Connections 3.0.1
1. [root@icdb ~]# mkdir /opt/install/TDIFix
2. [root@icdb ~]# cd  /opt/install/TDIFix
3. [root@icdb TDIFix]# wget ftp://dispsd-8.boulder.ibm.com/ecc/sar/CMA/TIA/00zbo/1/7.0.0-TIV-TDI-FP0005.zip
4. [root@icdb TDIFix]# unzip 7.0.0-TIV-TDI-FP0005.zip
5. [root@icdb TDIFix]# cd 7.0.0-TIV-TDI-FP0005
6. [root@icdb 7.0.0-TIV-TDI-FP0005]# cp UpdateInstaller.jar
7. [root@icdb 7.0.0-TIV-TDI-FP0005]# cp UpdateInstaller.jar /opt/IBM/TDI/V7.0/maintenance/
• overwrite existing UpdateInstaller.jar
8. [root@icdb 7.0.0-TIV-TDI-FP0005]# cd /opt/IBM/TDI/V7.0/bin/
9. [root@icdb bin]# ./applyUpdates.sh -update /opt/install/TDIFix/7.0.0-TIV-TDI-FP0005/TDI-7.0-FP0005.zip
10. Check information about fixpack running command:
• [root@icdb bin]# ./applyUpdates.sh -queryreg

Output of the command should be similar

Information from .registry file in: /opt/IBM/TDI/V7.0

Edition: Identity

Level: 7.0.0.5

License: None

Fixes Applied

=-=-=-=-=-=-=

TDI-7.0-FP0005(7.0.0.0)

Components Installed

=-=-=-=-=-=-=-=-=-=

BASE

SERVER

   -TDI-7.0-FP0005

CE

   -TDI-7.0-FP0005

JAVADOCS

EXAMPLES

   -TDI-7.0-FP0005

EMBEDDED WEB PLATFORM

AMC

   Deferred: false

Ta daaa ...  you are done with TDI!

Next part is here: how to install Fix WAS, IHS and Plug-in

IBM Connections 3.0.1 on RHEL - how to install - 4. Database Server DB2

Now we will prepare our DB2 server for IBM Connections.


You will need:
installation packages

• CZ19NEN  IBM DB2 Enterprise Server Edition V9.7 for Linux x86-64​
• CZ381ML   DB2_ESE_Restricted_QS_Activation_97.zip
• v9.7fp2_linuxx64_universal_fixpack.tar.gz

and already installed RHEL 5.4 server with graphic environment.

FQDN: icdb.ys.cz

DB2 Installation pre-requisites 

1.  After standart installation disable SELinux and Firewall
2. Change hostname 
1. run command:  [root@icdb ~]# system-config-network 
2. and change hostname to icdb.ys.cz
3. Create installation directory
1. [root@ icdb   ~]# mkdir -p /opt/install/DB2
2. [root@ic ~]# chmod 777 -R /opt/install/
4. OPTIONAL - If you run in vmware infrastructure install vmware tools
1. Mount vmware tools image and install it
2. [root@icdb media]# mkdir -p /media/cdrom
3. [root@icdb media]# mount /dev/hdc /media/cdrom
4. [root@icdb install]# cd /opt/install/
5. [root@icdb install]# tar xvzf  /media/cdrom VMwareTools-8.3.7-341836.tar.gz
6. [root@icdb install]# cd vmware-tools-distrib/
7. [root@icdb vmware-tools-distrib]# ./vmware-install.pl
8. Leave all options in default during installation wizard and run  [root@ic vmware-tools-distrib]# reboot
5. Check installed libs and rpms   http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/r0008865.html Try to find all listed files like libpam.so.0 in /lib  or /usr/lib/ direcotry

Install DB2 Server

1. After download from, save tar in to /opt/install/DB2
2. extract tar.gz file 
1. [root@icdb media]# cd /opt/install/DB2
2. [root@icdb media]# tar xvfz DB2_ESE_Restricted_QS_Activation_97.zip
3.  Run install wizard (you must be in X or your putty must have in "Categorry> Connection> SSH> X11> checked Enable X11 forwarding" and you must running Xming server on your local Windows workstation)
1. [root@icdb ese]# ./db2setup
2. Go trough wizard as follow:
1. Introduction > NEXT
2. Software License Agreement > Accept > NEXT
3. Installation type > Typical > NEXT
4. Installation action > NEXT
5. Installation directory > we used /opt/IBM/db2/V9.7  > NEXT
6. SA MP > Check Do not instal SA MP > NEXT
7. DAS user> 
1. Username: dasusr1
2. Group name: dasadm1
3. Password: Pass4conn > NEXT
8. Instance setup > Choose Create a DB2 instance > NEXT
9. Partitioning option > Single partition instance > NEXT
10. Instance owning user > 
1. User name: db2inst1
2. Group name: db2iadm1
3. Password:  Pass4conn  > NEXT
11. Fenced user >
1. User name: db2fenc1
2. Group name: db2fadm1
3. Password:  Pass4conn > NEXT
12. Tools catalog > Choose Prepare the DB2 tools catalog > NEXY
13. Notification setup > Do not set up your DB2 server to send notifications at this time > NEXT
14. Summary > Make sure, that all is ok > FINISH
3. Setup path to root as db2inst1 has in .bashrc - to be able to run db commands as root
1. [root@icdb ~]# less /home/db2inst1/.bashrc
2. Copy following lines
3. # The following three lines have been added by UDB DB2.
   if [ -f /home/db2inst1/sqllib/db2profile ]; then
       . /home/db2inst1/sqllib/db2profile
   fi
4. and paste it in to a /root/.bashrc
5. [root@icdb ~]# vim /root/.bashrc
4. Reconfigure DB2 installation
6. Then configure TCPIP communications:
7. Edit /etc/services (as root), add to bottom of file:
8. db2inst1 50000/tcp
   DB2_d2binst1_2 60002/tcp
   DB2_db2inst1 60003/tcp
   DB2_db2inst1_1 60004/tcp
   DB2_db2inst1_2 60005/tcp
   DB2_db2inst1_END 60006/tcp
9. Setup DB2 communications (as db2inst1)
1. [root@icdb ~]# su - db2inst1
2. [db2inst1@icdb ~]# cd ~/sqllib
3. [db2inst1@icdb ~]# . ./db2profile
4. [db2inst1@icdb ~]# db2 update database manager configuration using svcename db2inst1
5. [db2inst1@icdb ~]# db2stop;db2start
6. [db2inst1@icdb ~]# db2 get database manager configuration
7. [db2inst1@icdb ~]# db2 db2set DB2COMM=tcpip
8. [db2inst1@icdb ~]# db2stop;db2star
9. [db2inst1@icdb ~]# telnet localhost 50000
10. [db2inst1@icdb ~]# exit
10. Also need to configure DB2 to start automatically, e.g.:
1. Edit /etc/rc.local as root, add the following:
   #START DB2 for LOTUS CONNECTIONS
   DB2LOG=/tmp/startDB2.out.`date +"%y%m%d"`
   su db2inst1 -c /home/db2inst1/sqllib/adm/db2start >> $DB2LOG 2>&1

DB2 FixPack Installation

1. Download from FixCentral
2. Untar v9.7fp2_linuxx64_server.tar.gz
3. [root@icdb install]# tar xvfz v9.7fp2_linuxx64_server.tar.gz
4. To stop all DB2 processes, perform the following steps:
5. Determine which instances are associated with the DB2 copy In our case only db2inst1. Issue the command:
1. [root@icdb ~]# su - db2inst1
2. [db2inst1@icdb ~]$ . $HOME/sqllib/db2profile
3. [db2inst1@icdb ~]$ db2 force applications all
4. [db2inst1@icdb ~]$ db2 terminate
5. [db2inst1@icdb ~]$ db2stop
6. [db2inst1@icdb ~]$ db2licd -end
7. [db2inst1@icdb ~]$ exit
6. If the DB2 Administration Server (DAS) belongs to the DB2 copy that you are updating, stop the DAS:
1. [root@icdb ~]# su - dasusr1
2. [dasusr1@icdb ~]$ . $HOME/das/dasprofile
3. [dasusr1@icdb ~]$ db2admin stop
4. [dasusr1@icdb ~]$ exit
5. [root@icdb server]# su - db2inst1
6. [ db2inst1@icdb ~]# $HOME/sqllib/bin/ipclean
7. [ db2inst1@icdb ~]# exit
7. Run fix pack installation
1. [root@icdb ~]# cd /opt/install/DB2Fix/universal
2. [root@icdb  universal]# ./installFixPack -b /opt/ibm/db2/V9.7/
3. Make sure, that installation finished with success and without any errors
4. Note: If you will need to install an ealrier fix pack over currently installed (and higher) use -f level parameter to force db level check. So, go to step 5. and 6. again and then run ./installFixPack -f level -b /opt/ibm/db2/V9.7

License your DB2 

1. Use IBM Passport Advantage web site to get license key or if you install it from a DVD media, you can find it on.
2. Find package by Part Number CZ381ML.
3. Download the part and extract the DB2_ESE_Restricted_QS_Activation_97.zip file in to folder  /opt/install/DB2lic/
4. Log into DB2 using an db2inst1 admin.
5. Open a command prompt, change to the directory where the license file is stored, and run the following command:
• [db2inst1@icdb ~]$ db2licm -a /opt/install/DB2lic/ese_o/db2/license/db2ese_o.lic
6. Verify that the license is registered by running the following command:
• [db2inst1@icdb ~]$ db2licm -l 
• If the license is correctly registered, the details of your DB2 installation are displayed.
7. Restart DB2.

Setup DB2 instance to run after reboot

• First you need to configure fault monitor to start during system (os) start:
• [root@icdb ~]# db2fmcu -u -p /opt/IBM/db2/bin/db2fmcd
• Now you can enable FMC to automatically start the instance when the system is booted. To enable this feature for instance DB2INST1, type the following command:
• [db2inst1@icdb ~]$ db2iauto -on db2inst1
• Try to reboot your server and check if db instance is running. You can use telnet to localhost on port 50000 or ps -ax | grep db2

In the next chapter we will install TDI on this server