Wednesday 19 February 2014

Design, Deploy and Configure IBM Connections 4.5 with CCM and update it to CR2 (without cognos)




The following article list the installation of IBM Connections 4.5 with CCM and Update it to CR2. If you want reporting, analysis, score carding, and monitoring of events and metrics you can install Cognos BI and Transformation Server. The information below is gathered from different IBM Info center links and IBM redbook and presented in a simple to follow step by step procedure.
For up to date information check IBM Connections 4.5 system requirements and all other links mentioned in article.




Index:

  1. Notes and Important Links.
  2. Required Part Numbers and Fixes.
  3. Create Databases on DB2 Servers.
  4. Install Tivoli Directory Integrator and applying FP6.
  5. Edit the required Java Parameters and Updated path variable and files for TDI.
  6. Populate the PEOPLEDB aka Profiles database.
  7. Install WAS ND 8.0.0.0 and updated to FP5.
  8. Create DMGR and Federated Application Server Profile.
  9. Install 6 important interim fix packs on WAS ND 8.0.0.5.
  10. Federate the LDAP Repository.
  11. Install IBM Connections 4.5.0.0 with Connections Content Manager.
  12. Sync Nodes with DMGR and Set JVM Heap Size for IC Server.
  13. Setup the Homepage Administrator.
  14. Grant access to Global Metrics and Community Metrics.
  15. Update FileNet Content Platform Engine to FP2.
  16. Update FileNet Collaboration Services to FP 1.
  17. Update FileNet Content Platform Engine Client to FP2.
  18. Install Cumulative Refresh Pack 2 on IBM Connections 4.5 with CCM.
  19. Update the matrix database schema with CR2 SQL scripts.
  20. Clear WAS OSGI and Java Class Cache.
  21. Start the IC 4.5 and teste all apps for issues and finalize the deployment. (homepage, profiles, activities, blogs, communities, bookmarks, wiki, forums, files, metrics).


1.     Note and Important Links.

The following article below list the installation of IBM Connections 4.5 with CCM and Update to CR2. If you want reporting, analysis, score carding, and monitoring of events and metrics you can install Cognos BI and Transformation Server.

For system requirements and up to the minute information on IBM Connections 4.5 please visit: http://www-01.ibm.com/support/docview.wss?uid=swg27037782
Update strategy for IBM Connections 4.5:
http://www-01.ibm.com/support/docview.wss?uid=swg21637542

2.     Required Part Numbers and Fixes.

a.      IBM Connections V4.5 for Windows Multilingual (CIHC5ML)
b.      IBM Connections v4.5 Wizards for Windows Multilingual. (CIHC8ML).
c.      Tivoli Directory Integrator TDI_7.1.0.
d.      TDI FP 6 (7.1.0-TIV-TDI-FP0006.zip).
e.      IBM FileNet Content Engine V5.2 Windows Multilingual (CIQ57ML)
f.       IBM FileNet Content Engine Client V5.2 Windows English (CIQ5FEN)
g.      IBM FileNet Collaboration Services V2.0 Windows Multilingual (CIG7ZML)
h.      IBM DB2 UDB 9.7 OR above.
i.       IBM Data Server Runtime Client 9.7 for Windows® on AMD64 and Intel® EM64T systems (x64) Multilingual (CZ1A6ML).
j.       Websphere Application Server Network Deployment 8.0.0.0.
(CZM9KML, CZM9LML, CZM9MML, CZVG4ML, CZT7LML)
k.      WAS FP 5 required (Part1 and Part2).

WAS ND fixes required on WAS ND 8.0.0.5.
l.       PM62615: MESSAGES BUILD UP ON WEBSPHERE APPLICATION SERVER V7.0 SERVICE INTEGRATION BUS TOPICSPACE
Fix Central iFix for PM62615
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Application+Server&release=8.0.0.5&platform=All&function=aparId&apars=PM62615

m.    PM71430: SIB messages stuck and queue growing for 8+ hours (large scale deployments)
Fix Central iFix for PM71430
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Application+Server&release=8.0.0.5&platform=All&function=aparId&apars=PM71430


n.      PM85834: Potential security exposure in WebSphere Application Server
Fix Central ifix for PM85834
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Application+Server&release=8.0.0.5&platform=All&function=aparId&apars=PM85834


o.     PM83196: OAuth TAI throwing 403 exception instead of 401 response
Fix Central iFix for PM83196
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Application+Server&release=8.0.0.5&platform=All&function=aparId&apars=PM83196


p.      PM76920: Nullpointerexception in the Trust Association Manager
Fix Central iFix for PM76920
http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Application+Server&release=All&platform=All&function=fixId&fixids=8.0.0.5-WS-WAS-IFPM76920&includeRequisites=1&includeSupersedes=0&downloadMethod=http


q.      PM94437: Minimize the number of threads that wait on the LDAP context pool creation after LDAP failure.
Fix Central iFix for PM94437
http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Application+Server&release=All&platform=All&function=fixId&fixids=8.0.0.5-WS-WAS-IFPM94437&includeRequisites=1&includeSupersedes=0&downloadMethod=http



3.     Create Databases on DB2 Servers.

1.                Create user LCUSER / Passw0rd on Databse machine.
2.                Login with db2 admin user which has administrative rights on DB2 Machine.
3.                Extract [IBM Connections v4.5 Wizards for Windows Multilingual. (CIHC8ML)] In a directory and run dbwizard.bat file with run as admin rights. Or manually execute the scripts below.
4.                Create Metrics and Cognos DBs if required.


HOMEPAGE
1.  db2 -tvf C:\RC_Backup\connections.sql\homepage\db2\createDb.sql
1b. db2 -tvf C:\RC_Backup\connections.sql\homepage\db2\appGrants.sql
1c. db2 -tvf C:\RC_Backup\connections.sql\homepage\db2\initData.sql
1d. db2 -tvf C:\RC_Backup\connections.sql\homepage\db2\reorg.sql
1e. db2 -tvf C:\RC_Backup\connections.sql\homepage\db2\updateStats.sql
PEOPLEDB
2. db2 -tvf C:\RC_Backup\connections.sql\profiles\db2\createDb.sql
2b.db2 -tvf C:\RC_Backup\connections.sql\profiles\db2\appGrants.sql

OPNACT
3. db2 -td@ -vf C:\RC_Backup\connections.sql\activities\db2\createDb.sql
3b.db2 -td@ -vf C:\RC_Backup\connections.sql\activities\db2\appGrants.sql

SNCOMM
4. db2 -td@ -vf C:\RC_Backup\connections.sql\communities\db2\createDb.sql
4b.db2 -td@ -vf C:\RC_Backup\connections.sql\communities\db2\appGrants.sql

BLOGS
5. db2 -td@ -vf C:\RC_Backup\connections.sql\blogs\db2\createDb.sql
5b.db2 -td@ -vf C:\RC_Backup\connections.sql\blogs\db2\appGrants.sql

FILES
6. db2 -td@ -vf C:\RC_Backup\connections.sql\files\db2\createDb.sql
6b.db2 -td@ -vf  C:\RC_Backup\connections.sql\files\db2\appGrants.sql

FORUM
7. db2 -td@ -vf C:\RC_Backup\connections.sql\forum\db2\createDb.sql
7b.db2 -td@ -vf  C:\RC_Backup\connections.sql\forum\db2\appGrants.sql

Mobile
8. db2 -td@ -vf  C:\RC_Backup\connections.sql\mobile\db2\createDb.sql
8b.db2 -td@ -vf  C:\RC_Backup\connections.sql\mobile\db2\appGrants.sql

WIKIS
9. db2 -td@ -vf C:\RC_Backup\connections.sql\wikis\db2\createDb.sql
9b.db2 -td@ -vf C:\RC_Backup\connections.sql\wikis\db2\appGrants.sql

DOGEAR
10. db2 -td@ -vf C:\RC_Backup\connections.sql\dogear\db2\createDb.sql
10b. db2 -td@ -vf C:\RC_Backup\connections.sql\dogear\db2\appGrants.sql

METRICS
db2 -td@ -vf C:\RC_Backup\connections.sql\metrics\db2\createDb.sql
db2 -td@ -vf C:\RC_Backup\connections.sql\metrics\db2\appGrants.sql
COGNOS
db2 -td@ -vf C:\RC_Backup\connections.sql\cognos\db2\createDb.sql
db2 -td@ -vf C:\RC_Backup\connections.sql\cognos\db2\appGrants.sql

4.     Install Tivoli Directory Integrator and applying fix pack 6.

On DB2 Server:
1. Run the launchpad.exe from C:\RC_Backup\Tivoli Directory Integrator 7.1.
2. Run the IBM Tivoli Directory Integrator 7.1 Installer.
3. Select Language, EULA and the directory path, that is C:\IBM\TDI\V7.1 and click next.
4. Select Typical, click next.

5. Used Default ports as follow:
      Server port = 1099
      System Store Port = 1527
      REST API Port = 1098
      System Queue Ports = 41001

6. Ports used by ISC, confirm and click next.
      13100 http
      13101    https
      13104    Action Manager API Port.
     
7. Register the TDI Server as service, if you want the service to run automatically.

8. Click Next and Install.

9. Click finish when done. Uncheck the start configuration editor.

10. Go to: C:\IBM\TDI\V7.1\bin> and run the following command below, make sure the TDI-7.1-FP0006.zip is placed at the location defined.

C:\IBM\TDI\V7.1\bin>applyUpdates -update "C:\RC_Backup\Tivoli Directory Integrator\ 7.1\7.1.0-TIV-TDI-FP0006\TDI-7.1-FP0006.zip"


5.     Edit the required Java Parameters and Updated path variable and files for TDI.

On DB2 Server:
1. Copy the db2jcc.jar and db2jcc_license_cu.jar files from C:\Program Files\IBM\SQLLIB\java\
and pasted to C:\RC_Backup\Tivoli Directory Integrator 7.1\7.1.0-TIV-TDI-FP0006

2. Edit ibmdisrv.bat in C:\IBM\TDI\V7.1\ as below.

Before Change:

"%TDI_JAVA_PROGRAM%"  -classpath "%TDI_HOME_DIR%\IDILoader.jar" %ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %*

After Change:

"%TDI_JAVA_PROGRAM%" -Xms256M -Xmx1024M -Xnojit -classpath "%TDI_HOME_DIR%\IDILoader.jar" %ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %*

6.     Populate the PEOPLEDB aka Profiles database.

On DB2 Server:
1. Extract IBM_Connections_4.5_wizards_win.exe self-extract executable in [C:\IBM\TDI\V7.1\Wizards\] location.
2. Run C:\IBM\TDI\V7.1\Wizards\populationWizard.bat as Administrator.
3. Click Next and give install path that is C:\IBM\TDI\V7.1\ and hit next.
4. Select DB2 Universal Database(TM) and click next.

5. Give
Hostname  = DBbox (192.168.1.72)
Port                            = 50001
Database Name      = PEOPLEDB
JDBC driver library path = C:\Program Files\IBM\SQLLIB\java
User ID (Account used to write to database) = LCUSER
Password = Passw0rd
Click next.

6. LDAP SERVER NAME = Adbox.rcds.com
LDAP SERVER PORT = 192.168.1.213

7. BIND Distinguished name (DN) = CN=portaladmin-qa,OU=qa,OU=portal,DC=rcds,DC=com
BIND Password:                     = Q@Adm1NpW$

8. LDAP user Search Base = OU=qa,OU=portal,DC=rcds,DC=com
LDAP user search filter = (&(sAMAccountName=*)(objectclass=user))

9. Click next and map ldap fileds to profiles db fields. Click next.

10. Check the summary and click finish.

7.     Install WAS ND 8.0.0.0 and updated to FP5.

On IBM Connections 4.5 Server:

Install the IBM Installation Manager

a.      Starting with WebSphere 8.0 the System is installed using the IBM Installation Manager.
b.      For IBM Connections 4.5 we use the IBM Installation Manager release 1.5.3. Navigate to the C:\RC_Backupl\WAS_ND_8.0\IM directory. Then right click the install.exe file and select Run as Administrator.
c.      Click Next to continue.
d.      Select I accept the terms in the license agreement. Then click Next to continue.
e.      Remove Program Files/ part in the path. Then click Next to continue.
f.       Click Install to start the installation.
g.      The IBM Installation Manager is installing.
h.      The IBM Installation Manager is installed. Click Restart Installation Manager.
i.       Install the IBM WebSphere Application Server
j.       Add the repositories. Click File > Preferences....
k.      Click Add Repository....
l.       Click Browse....
m.    Navigate to the C:\RC_Backup\WAS_ND_8.0\WAS directory and select the repository.config file. Then click Open.
n.      Click OK to continue.
o.     Click again Add Repository....
p.      Click Browse....
q.      Navigate to the C:\Install\WAS_ND_8.0\WAS_FP5 directory and select the repository.config file. Then click Open.
r.       Click OK to continue.
s.      Click OK to continue.
t.       Now click Install.
u.      Check both check boxes. Then click next to continue.
v.      Select I accept the terms in the license agreement. Then click next to continue.
w.    Remove the Program Files/ part in the path. Then click next to continue.
x.      Again remove the Program Files\ part in the path. Then click Next to continue.
y.      Then click Next to continue.
z.      Click Next to continue.
aa.   Click Install to start the installation.
bb.   Click Finish now. The Profile Management Tool starts automatically.

8.     Create DMGR and Federated Application Server Profile.

a)      Open Profile Mgmt Tool.
b)      Click Create button on right.
c)      Select Cell (DMGR and Federated App Server). Click Next.
d)      Select Typical Profile Creation click next.
e)      Give username = wasadmin password= Passw0rd and click next.
f)       Verify the details and click create.
g)      Uncheck launch first steps and click finish.
h)      Close the PMT.

9.     Install 6 important interim fix packs on WAS ND 8.0.0.5.

a.      Open IBM Installation Manager and Click File and then Preferences....
b.      Un-check the WAS and WAS_FP5 repositories. Then click Add Repository....
c.      Click browse and Navigate to the directory C:\RC_Backup\WAS 8\8.0.0-ws-wasnd-ifpm71430 and select the repository.config file. Then click Open.
d.      Click add repository, browse and Navigate to the directory C:\RC_Backup\WAS 8\8.0.0.5-ws-wasnd-ifpm62615 and select the repository.config file. Then click Open.
e.      Use this same procedure for remaining 4 fixes and add them in repository.
f.       Click oki and then click Update and hit next.
g.      Select Group package that is WAS ND 8 and hit next.
h.      Select both fixes and click next.
i.       Click update to continue.
j.       Click finish when done.

10.  Federated the LDAP Repository.

1. Open Console.
https://CCMBox.rcds.com:9043/ibm/console/logon.jsp
wasadmin / Passw0rd
2. Goto Security --> Global Security.
3. Make sure Federated Repository is selected, click on Configure infront of Federated Repository.
4. Click on Add New Realm.
5. Key in the Repository Name = QAOu_Ldap.
6. Key in the Ldap Server, port.
6a. Select appropriate directory server (TDS or AD).
LDAP SERVER NAME = Adbox.rcds.com
LDAP SERVER PORT = 192.168.1.213
Port = 389
7. Key in the Bind Username and password.
CN=portaladmin-qa,OU=qa,OU=portal,DC=rcds,DC=com / Q@Adm1NpW$
8. Edit person entity and type (OU=qa,OU=portal,DC=rcds,DC=com) in Search Filter to set the directory to look in users for QA only.
9. Click Save and enter the Distinguished name of a base entry that uniquely identifies this set of entries in the realm (OU=qa,OU=portal,DC=rcds,DC=com) and enter the Distinguished name of a base entry in this repository: (OU=qa,OU=portal,DC=rcds,DC=com).
10. Save the master config. Now click set as default infront of federated repository.
11. Click Apply and Ok and save to master config.
12. Log off and login again. Click Manage Users and check if users are listed.
13. If users are not listed then there is some configuration mistake.
14. Done you are all set, federated repository is now configured.

11.  Install IBM Connections 4.5.0.0 with Connections Content Manager.

1. Run Launchpad.exe from RCBackup\IBM Connections folder.
2. Select Install IC and Check IBM Connections V4.5 and click next.
3. Select EULA and click Next.
4. Set Path for New Package Group = C:\IBM\Connections.
5. Scroll down and select IBM Connections Content Manager and click next.
6. Browse and Select WAS Install folder. C:\IBM\Websphere\AppServer
7. Select DMGR Profile = DMGR01
8. Hostname = CCMBox.rcds.com
9. Enter Username and password, wasadmin / Passw0rd.
10. Click Validate, (SSL Cert, DMGR Infor, Installed Apps are checked at this point).
11. Click New Deployment of CCM and Browse to Folder Where all the IBM CCM related executables are placed. C:\RCBackup and click validate.
12. Select Small in Topology Config, enter Cluster Name = SmallCL, Select Node CCMBoxNode1 and click next.

13. Because DB2 is on a Seperate Sever therefore we need to install the following client on (CCMBox.rcds.com) IBM Connections with CCM BOX.
IBM Data Server Runtime Client 9.7 for Windows® on AMD64 and Intel® EM64T systems (x64) Multilingual (CZ1A6ML).
(This will create the db2 java directory on the machine).
13. Enter the Configuration of DB2 Server.
Hostname = DBbox.rcds.com
Port = 50001
JDBC Driver Location = C:\Program Files\IBM\SQLLIB\java
Select the same userid / pass for all.
User ID = LCUSER
Password = Passw0rd
Click Next.
14. Leave Cognos for Later Setup if required.
15. Share Content Store = C:\IBM\Connections\data\shared
Local Content Store = C:\IBM\Connections\data\local
16. Disabled Mail Notifications. Will enable if required.
17. Verify all the packages and features and click install.
18. Click Finish when done.

12.  Sync Nodes with DMGR and Set JVM Heap Size for IC Server.

1. Goto run and type services.msc.
2. Locate IBM WAS 8.0 - CCMBoxCellManager01 Service Stop and then Start the Service.
3. Goto appserver profile C:\IBM\Websphere\AppServer\Profiles\AppSrv01\Bin and run startNode.bat.
4. Log in to the console https://CCMBox.rcds.com:9043/ibm/console/login.do?action=secure (Wasadmin / Passw0rd).
5. Click on System Administration and click on Nodes.
6. Select CCMBoxNode01 and click Full Resynchronize.
7. Wait and Check (C:\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps) for InstalledApps to get synchronized.
8. Now Click on Servers and Start [SmallCL_server1] as it hosts all the installaed applications.
9. Wait for the Java.exe process in taskmanager to reach 1.5 Gb.
10. now you can check the ibm connections at https://CCMBox.rcds.com:9444/homepage/login/
11. Log in to the console https://CCMBox.rcds.com:9043/ibm/console/login.do?action=secure (Wasadmin / Passw0rd).
12. Goto WAS Server and select SmallCL_server1 .
13. On the right side click Java and Process Management and then Process definition.
14. Click Java Virtual Machine
15. Check that the field Maximum Heap Size contains 2506 MB.
16. Apply and Ok the config.

13.  Setup the Homepage Administrator.

1.      In your Browser log in to the Integrated Solutions Console with your IBM WebSphere Application Server Administrator account and password.
2.      Click Applications -> Application Types - WebSphere Enterprise applications.
3.      Click the Homepage application.
4.      In the Detail Properties section, click Security roles to user/group mapping.
5.      Select the admin role and click Map Users....
6.      Enter a name or part of a name in the Search String field and click Search.
7.      Select one of the names in the Available view and click the button to add it to the selected view.
8.      The user name is now in the selected view. Click OK to continue.
9.      The user is now listed in the admin role in the apped Users column. Click OK to continue.
10.   Click Save to save the last configuration changes.
11.   If you now login with this administrative user ID to your connections server, you can see the Administration link on the left side.
12.   Here you can do some administrative configuration of the Homepage application.

14.  Grant access to Global Metrics and Community Metrics.

1. Log on to IBM Console.
2. Go to applications, websphere enterprise apps.
3. Open common app and click on security rules to user/group mapping.
4. Select the metrics-report-run role and click Map Special Subjects.
5. Select All Authenticated in Application's Realm.
6. Click ok and save the master config.
7. Perform the same steps for metrics applciation.
8. Full sync the nodes.

15.  Update FileNet Content Platform Engine to FP2.

0. STOP Application Server.
1. Install CPE first, Extract 5.2.0.2-P8CPE-WIN-FP002.zip and run 5.2.0.2-P8CPE-WIN-FP002.exe
2. Click next, on components select Content Platform Engine Server only. click next.
3. Install directory will be deducted as = c:\ibm\connections\ccm\contentengine click next.
4. Set url used in wcmapiconfig.properties file http://CCMBox.rcds.com:9081/wsi/FNCEWS40MTOM/ click next.
5. Read the config and click next for installation. it will take approx 1750 MB diskspace.
6. Click finish when done do not run the configuraiton manager in last.
7. To verify check ce_version.info at C:\IBM\Connections\addons\ccm\ContentEngine path.
8. Now goto Websphere Enterprise Application section in WAS console and Uninstall FileNetEngine App.
9. Stop nodeagent / node and dmgr.
10. Delete the filnetengine ear folder from C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\CCMBoxNode01\SmallCL_server1
11. Start node agent / node and dmgr.
12. Now goto C:\IBM\Connections\addons\ccm\ContentEngine\tools\configure and run configmgr.exe.
12a. Click file menu and click upgrade profile.
13. Click next, put userid / password and hostname of WAS.
13a. Wasadmin / Passw0rd / CCMBox.rcds.com
14. Click Finish and Verify setting before pressing OK.
15. Click ok and then close the welcome screen on back.
16. Double Click on the task "Configure Bootstrap and Text Extraction"
17. Make sure the Bootstrap operations shows "Upgrade”. Verify the path in the field "Bootstrapped EAR file". Click "Save”.
18. Once Saved, click Run Task
19. Now double click on Deploy Application
20. Verify the path in the field "Bootstrapped EAR file" . Click "Save" .
21. Once Saved, click Run Task
22. Once you see "Finished running Deploy Application" you can close the Configuration Manager
23. Check the nodeagent log file in C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent for
AppBinaryProc I ADMA7021I: Distribution of application FileNetEngine completed successfully.

Skiiping Step: 1.4.1. Add FileNetEngine back to the HTTP server
http://www-01.ibm.com/support/docview.wss?uid=swg21655425

16.  Update FileNet Collaboration Services to FP 1.

1. First uninstall the current FNCS Application.
2. Open a browser to the Integrated Solutions Console and login
3. Go to Applications - Application Types - WebSphere enterprise applications, Select FNCS and click Uninstall
4. Monitor the SystemOut.log on the nodeagent (C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\nodeagent) for
ADMA7021I: Distribution of application FNCS completed successfully.
5. Stop Connections node, nodeagent and dmgr by running:
             a. Stop Connections node: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopserver.bat SmallCL_server1 -username localadmin -password password
             b. Stop nodeagent: c:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopNode.bat -username wasadmin -password Passw0rd
             c. Stop DMGR: c:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\stopManager.bat -username wasadmin -password Passw0rd
6. Delete temp directories on all nodes by removing the FNCS folder in C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\CCMBoxNode01\SmallCL_server1
7. If it exists delete the FNCS.ear folder from C:\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\SmallCL_server1

Uninstall FNCS application binaries
1. Run C:\IBM\Connections\addons\ccm\FNCS\uninstall\fncs-uninstall.exe
2. Backup the C:\IBM\Connections\addons/ccm/FNCS/CE_API directory.
3. Backup the C:\IBM\Connections\addons/ccm/FNCS/configmanager/profiles/fncs-sitePrefs.properties file.
4. Delete the C:\IBM\Connections\addons/ccm/FNCS directory.

Install FileNet Collaboration Services (FNCS)

Files needed for this section:
FileNet Collaboration Services (FNCS) IF1 (e.g. 2.0.0.1-FNCS-IF001-WIN)

1. Run C:\downloads\ic45CR2\FileNet\FNCS\2.0.0.1-FNCS-IF001-WIN.exe
2. Update the Installation directory to C:\IBM\Connections\addons\ccm\FNCS and click Next.
3. Copy the CE_API directory you backed up earlier to the C:\IBM\Connections\addons/ccm/FNCS directory
4. Copy the fncs-sitePrefs.properties file you backed earlier to the C:\IBM\Connections\addons/ccm/FNCS/configmanager/profiles directory.
5. Finally verify that C:\IBM\Connections\addons\ccm\FNCS\properties\fncs-sitePrefs.properties has the following properties:
AnonymousAccessEnabled=true
EnablePropertySheetTemplateMinMax=true

Otherwise, add them to the file.

17.  Update FileNet Content Platform Engine Client to FP2.

Upgrade Content Platform Engine Client CEClient interactively
Start all Connections by running the following commands:
Start DMGR: C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\startManager.bat
Start nodeagent: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startNode.bat
Start Connections node: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startserver.bat SmallCL_server1

1. Run C:\RC_Backup\FileNet\5.2.0.2-P8CPE-CLIENT-WIN-FP002\5.2.0.1-P8CE-CLIENT-WIN-FP001.exe
2. Click next.
3. The next page asks for the host name and port of the Content Platform Engine Server:
4. CCMBox.rcds.com:9081
5. Select "IBM FileNet Services for Lotus Quickr" In my install, this was already selected and no changes had to be made:
6. Set the common files directory C:\IBM\Connections\addons\ccm\Common Files
7. Select Next, verify settings and click install.


Important notes:
1. Each time you update FNCS, you will need to reinstall the CCM authentication filter into FNCS. To reinstall the authentication filter, please follow Install  FNCS authentication filter steps in this topic: Configuring FileNet Collaboration Services for the Connections Content Manager.
2. For additional FileNet information, refer to the IBM FileNet P8 Platform Documentation.

Configure FileNet Collaboration Services
Make sure Connections is running.
1. Run C:\IBM\Connections\addons\ccm\FNCS\configmanager\configwizard.bat
2. The next screen asks for the Content Platform Engine URL.
                              a. iiop://CCMBox.rcds.com:2811/FileNet/Engine
                              b. Object Store: ICObjectStore
3. Next Give the WAS Version and path:
                              a. 8.5
                              b. C:\IBM\WebSphere\AppServer
4. Userid / password of local admin.
                              wasadmin / Passw0rd
5. Verification of Connectivity.
6. Web Client Applicaiton = None.
7. IBM Connection URL : http://CCMBox.rcds.com:9081
8. App Server Profile: DMGR01 , wasadmin , Passw0rd.
9. Application Server cluster.
10. SmallCL.
11. WAS Enterprise App Name = FNCS
12. Click next, verify settings and click Done.
13. When finish restart app server, nodeagent and dmgr.

Validate FNCS was upgraded correctly

14. To Verify open http://CCMBox.rcds.com:9081/dm/ in browser.
Add Anonymous user back to FNCS RunAs role
NEED TO DISCUSS:
15. goto Enterprise Applications > FNCS and click (user RunAs roles).
16. Select the Anonymous role and enter the username and password of the LDAP user designated for the anonymous access role.
17. Click Apply, OK and save configuration.

Install FNCS authentication filter

1. Go to Applications - Application Types - WebSphere Enterprise Applications.
2. Select FNCS and Click Update.
3. For Application update options, select the Replace, add, or delete multiple files option
4. Select local file system if running the browser on the Deployment Manager node or remote if on another machine and then locate the auth_filter_patch.zip file in the C:/IBM/Connections/ccm/ccm/ccm/auth_filter_patch/auth_filter_patch.zip directory.
5. Click Next and OK to update the application.

FileNet is now upgraded to the necessary level for CR2 and you can proceed to apply the Connections CR.

18.  Install Cumulative Refresh Pack 2 on IBM Connections 4.5 with CCM.

In this step, we will install CR2. Please review the Update strategy for IBM Connections 4.5 document for the CR fix list, and links to download the installation packages from Fix Central.
http://www-01.ibm.com/support/docview.wss?uid=swg21637542

Close the Application Server (SmallCL_Server1) before performing this task.
Backup the existing update Installer directory (C:\IBM\Connections\updateInstaller)
Extract 4.5.0.0-IC-Multi-UPDI-20130909, and copy the updateInstaller directory to C:\IBM\Connections)
Extract 4.5.0.0-IC-Multi-CR02-LO76350 to C:\IBM\Connections\updateInstaller\fixes
1. Set WAS_HOME=C:\IBM\Websphere\AppServer
2. Update Operation Selection
3. C:\IBM\Connections\updateInstaller\fixes
4. Select all Updates that apply.
5. Press ok if asked for backup.
6. Key in was id and pass. wasadmin / Passw0rd.
7. After validation is successful, verify summary and click install.
8. Verify that all the application are installed successfully.
9. Look in the nodeagent's SystemOut.log for the following messages


ADMA7021I: Distribution of application Mobile completed successfully.
ADMA7021I: Distribution of application Forums completed successfully.
ADMA7021I: Distribution of application Activities completed successfully.
ADMA7021I: Distribution of application Profiles completed successfully.
ADMA7021I: Distribution of application News completed successfully.
ADMA7021I: Distribution of application Help completed successfully.
ADMA7021I: Distribution of application Moderation completed successfully.
ADMA7021I: Distribution of application Homepage completed successfully.
ADMA7021I: Distribution of application Blogs completed successfully.
ADMA7021I: Distribution of application WidgetContainer completed successfully.
ADMA7021I: Distribution of application Mobile Administration completed successfully.
ADMA7021I: Distribution of application Dogear completed successfully.
ADMA7021I: Distribution of application connectionsProxy completed successfully.
ADMA7021I: Distribution of application Metrics completed successfully.
ADMA7021I: Distribution of application Communities completed successfully.
ADMA7021I: Distribution of application Wikis completed successfully.
ADMA7021I: Distribution of application Search completed successfully.
ADMA7021I: Distribution of application Files completed successfully.
ADMA7021I: Distribution of application Common completed successfully.

10. Restart Connections.


Update CCM

1. Go to C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin and delete dminfo.properties
2. Run C:\IBM\Connections\addons\ccm\ccmDomainTool\ccmUpdate.bat.
3. Give password for the wasadmin user (Passw0rd).
4. Restart environment


19.  Update the matrix database schema with CR2 SQL scripts.

Updating the IBM Connections 4.5 databases to the required schema versions for Cumulative Refresh 2 (CR2)
http://www-01.ibm.com/support/docview.wss?uid=swg21655480

1. First logon to Db2 machine.
2. goto http://www-01.ibm.com/support/docview.wss?uid=swg21648864 and db2 scripts below and place them at c:\program files\ibm\sqllib\bin folder.
3. Then run the following db2 scripts below on db2 command prompt.
db2 -td@ -vf METRICS-db-upgrade-45-45CR2_DB2.sql
db2 -td@ -vf METRICS-db-reorg-45-45CR2_DB2.sql
db2 -td@ -vf METRICS-db-updateStats-45-45CR2_DB2.sql

20.  Clear WAS OSGI and Java Class Cache.

To clear the OSGi class cache:
    For UNIX platforms, run the following script in each profile:
    /profiles/profile_name/bin/osgiCfgInit.sh
    For Windows platforms, run the following script in each profile:
    \profiles\profile_name\bin\osgiCfgInit.bat

To clear the JVM's class cache (Windows, Linux and AIX only) :
    For UNIX platforms, run the following script:
    /bin/clearClassCache.sh
    For Windows platforms, run the following script:
    \bin\clearClassCache.bat
    And clear the following directory contents:
    \Local Settings\ApplicationData\javasharedresources\
    Where WinUsers_home is either C:\Documents and Settings\DefaultUser OR C:\Users depending on your current version of Windows.

21.  Start the IC 4.5 and test all apps for issues and finalize the deployment.
(Homepage, profiles, activities, blogs, communities, bookmarks, wiki, forums, files, metrics).
1.      Start the App Server, Node agent and DMGR.
2.      Login and check all the applications one by one.
Posted by at No comments:
Subscribe to: Posts (Atom)