K.1.Configure HTTP Server plugin with Connections

L. Additional HTTP Server config settings

L.1.Configure HTTP Server to compress some files

1. 
   Open httpd.conf (c:\IBM\HTTPServer\conf)
   

2. 
   Find the following entries in the configuration file:
   LoadModule headers_module modules/mod_headers.so
   LoadModule deflate_module modules/mod_deflate.so

   and uncomment them

   
   

3. 
   Add the following after all the LoadModule's

   #Only the specified MIME types will be compressed.

   AddOutputFilterByType DEFLATE application/atom+xml
   AddOutputFilterByType DEFLATE application/atomcat+xml
   AddOutputFilterByType DEFLATE application/javascript
   AddOutputFilterByType DEFLATE application/json
   AddOutputFilterByType DEFLATE application/octet-stream
   AddOutputFilterByType DEFLATE application/x-javascript
   AddOutputFilterByType DEFLATE application/xhtml+xml
   AddOutputFilterByType DEFLATE application/xml
   AddOutputFilterByType DEFLATE text/css
   AddOutputFilterByType DEFLATE text/html
   AddOutputFilterByType DEFLATE text/javascript
   AddOutputFilterByType DEFLATE text/plain
   AddOutputFilterByType DEFLATE text/xml
   AddOutputFilterByType DEFLATE text/xsl
   

4. 
   Add the following statement to specifically indicate that image files and binaries must not be compressed to prevent web browser hangs:

   # Ensures that images and executable binaries are not compressed

   
   SetEnvIfNoCase Request_URI \\.(?:gif|jpe?g|png|exe)$ no-gzip dont-vary
   

5. 
   Add the following statement to ensure that proxy servers do not modify the User Agent header needed by the previous statements:

   # Ensure that proxies do not deliver the wrong content

   
   Header append Vary User-Agent env=!dont-vary
   
6. 
   Add the following statement to ensure you can access the acce tool (admin client for FileNet)
   SetEnvIf Request_URI ^/acce(.*) no-gzip dont-vary
   

L.2.Configure Files and Wikis to download files

This is an optional step, but recommended in the infocenter. See the following section for details. http://www-01.ibm.com/support/knowledgecenter/SSYGQH_5.5.0/admin/install/t_install_post_files_downloads.dita

L.3.Configure Connections to use IHS to upload files

This is again an option step, but recommended in the infocenter. See the following section for details.

http://www-01.ibm.com/support/knowledgecenter/SSYGQH_5.5.0/admin/install/t_install_post_files_uploads.dita

M.Configure IBM Connections Content Manager Libraries

During the install of Connections Filenet was deployed on the system. Post install we need to configure the FileNet global configuration domain and objectstore. There are 2 scripts we will use to automatically create these.

M.1.Create Filenet Global Configuration Domain (GCD)

1. 
   If not running, start IBM Connections by running:
   ./startManager.sh from /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
   ./startNode.sh from /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

   Start Connections Clusters by running the following from /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

   
   ./startServer.sh InfraCluster_server1
   ./startServer.sh UtilCluster_server1
   ./startServer.sh AppsCluster_server1
   ./startServer.sh CCMCluster_server1
   ./startServer PushCluster_server1
   

2. 
   Run ./createGCD.sh from /opt/IBM/Connections/ccmDomainTool
   
3. 
   First it will ask you for the DMGR admin ID (localadmin for my environment), then the password
   
   

4. 
   Enter Y to regenerate the dminfo.properties file
   
   

5. 
   Next I added an administrator group from my ldap directory
   
   

6. 
   
   

M.2.Create FileNet ObjectStore

7. 
   Run ./ createObjectStore.sh from /opt/IBM/Connections/ccmDomainTool
   

8. 
   First enter the websphere admin username and password
   
   

9. 
   I chose Y to regenerate the dminfo.properties file
   
   

10. 
    Same as I did with the GCD, I set the administrator group from my ldap directory
    
    

11. 
    Next enter the url used to access Connections (https://cpdocs2.swg.usma.ibm.com) NOTE: It must be the SSL url
    
    

12. 
    
    

13. 
    Restart Connections to pick up the changes.
    

N.Apply Connections 5.5 Recommended Day1 fixes

I'm applying the recommended day 1 fixes as of February 12, 2016. See the following technote for latest recommended updates:
http://www-01.ibm.com/support/docview.wss?uid=swg21972646
Software used in this step:
IBM Connections Day 1 fixes:
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=Collaboration%2BSolutions&product=ibm/Lotus/Lotus+Connections&release=5.5.0.0&platform=All&function=all

• 
  interim fix: 5.5.0.0-IC-Multi-IFLO87330
  
• 
  interim fix: 5.5.0.0-IC-News-IFLO87487
  
• 
  interim fix: 5.5.0.0-IC-Common-IFLO87469
  
• 
  refresh pack: 5.5.0.0-IC-Multi-UPDI-20151224
  

N.1.Install the Day1 ifixes

1. 
   Before getting started shut down the Connections nodes, I left the nodeagents running.
   

2. 
   Extract the refresh pack: 5.5.0.0-IC-Multi-UPDI-20151224,
   unzip 5.5.0.0-IC-Multi-UPDI-20151224.zip -d updateinstaller
   

3. 
   this will create an AIX-Linux and Windows directory. Under the AIX-Linux directory is UpdateInstaller.tar. Extract UpdateInstaller to /opt/IBM/Connections/updateInstaller

   tar -C /opt/IBM/Connections -xvf UpdateInstaller.tar

   
   

4. 
   Copy the ifix jar files to /opt/IBM/Connections/updateInstaller\fixes

   cp 5.5.0.0-IC-Common-IFLO87469.jar 5.5.0.0-IC-Multi-IFLO87330.jar 5.5.0.0-IC-News-IFLO87487-151224.jar /opt/IBM/Connections/updateInstaller/fixes/

   
   

5. 
   Follow the Steps in Appendix A to export the display to your desktop
   

6. 
   From /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/ run
   . ./setupCmdLine.sh
   NOTE: That's dot space dot forward slash
   
   

7. 
   Change directory to /opt/IBM/Connections/updateInstaller/ and run ./updateWizard.sh
   

8. 
   
   

9. 
   
   

10. 
    
    

11. 
    
    

12. 
    
    

13. 
    
    

14. 
    
    

15. 
    
    

16. 
    Delete the contents of /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp -
    NOTE: If this step is missed when you access connections again, you will see the theme from Connections 5.0
    

17. 
    Start Connections and it should be ready to use.
    
    
    

Appendix - helpful linux stuff

O.Redirecting Display from unix to local windows machine

Redirecting Display\GUI from Unix to Windows:

1. 
   Install a Xwindows client on your local PC and start a Xsession
   Cygwin and Xming are popular clients
   
2. 
   Telnet\SSH into Unix server and login as root
   
3. 
   Set the DISPLAY to your PC's IP and export the setting
   DISPLAY=:0 # DISPLAY=9.9.124.126:0
   export DISPLAY
   
4. 
   You may have to disable security using the following command
   xhost +
   
5. 
   Run following command in the Unix telnet\ssh session should result in a clock appearing on your local PC
   xclock
   

NOTE: May have to run yum install xorg-x11-apps-7.6-6.el6.x86_64.rpm to install xclock



Using Xming as your Xwindows client:

The "trick" with Xming is to FIRST start it via the XLaunch (icon or command), NOT the Xming command/icon. That's because XLaunch allows you to check "No Access Control" which tells Xming to allow other IP's in. Starting Xming with the Xming command, causes the default "only allow in local host" mode. I was confused by this and first started Xming via "Xming" and didn't understand the role of XLaunch.

1. If Xming is already running and on the task bar, click and "exist"

2. Start -> All Programs -> Xming -> XLaunch

3. Select display window option .. click Next

4. Select "Start no client" option.. click Next

5. Select "Clickboard" and "No Access Control" option.. click Next

** If "No Access Control" is not selected, the xsession connection will fail"

6. Click Finish

P.Disable password settings on the OS

http://www.cyberciti.biz/tips/setting-off-password-aging-expiration.html

Q.Configure DB2 to start automatically after system restart

On UNIX operating systems, to configure an instance to auto-start after each system restart, perform the following steps:

1. 
   As root run the following command:

   NOTE: dot space /home/db2inst1/sqllib/db2profile

   . /home/db2inst1/sqllib/db2profile
   
   
   

2. 
   Verify that the instance's startAtBoot global registry field value is set to 1 by checking the output of the following command:

   db2greg -getinstrec instancename=''

   
   
   

   NOTE: If the startAtBoot global registry field value is not set to 1, set the value to 1 by running the following command:

   
   

db2greg -updinstrec instancename=''!startatboot=1

3. 
   Enable the instance to auto-start after each system restart, by running the following command:
   db2iauto -on
   
   
   

4. 
   Run
   db2set -all
   
   
   Notice DB2AUTOSTART is set to YES
   

5. 
   Change /opt/ibm/db2/V10.1/bin and run

   ./db2fm -i db2inst1 -U

   
   ./db2fm -i db2inst1 -u **This one gave an error for some reason??**
   ./db2fm -i db2inst1 -f on
   
   
   

6. 
   Reboot
   
7. 
   Sign in a db2inst1 and check the state
   db2fm -s -S
   

Now when you restart the machine, DB2 should start automatically

To prevent an instance from auto-starting after each system restart, enter the following command:
db2iauto -off

R.Configure IBM HTTP Server to start automatically

http://www.ibm.com/developerworks/aix/tutorials/au-enterprisewebsvr/section5.html

Directory: developerworks -> community -> files
files -> Mobile Application Developer (Classroom) Career path description
community -> Getting Started with Maximo Anywhere 5 Document version 0
community -> Compiling and installing Apache and php on aix 1 Revision control
files -> Mobile Arcgis desktop Systems for the laptop and ruggized pc
community -> Georgia ibm power user Group Date/Time: Thursday, January 21, 2015, 3pm to 5pm Location: ibm corporation, Building A, Barfield Auditorium
community -> 6303 Barfield Road ne, Atlanta, ga 30328 Agenda: 3: 00-3: 10pm Meet and Greet
files -> 31st December 2012 Submitted to the faculty of computer science & engineering

Download 143.99 Kb.

Share with your friends: