This is a summary for my own use, about installation of Connections 4.5. It's a quick reference documentation, and contains command lines and important points.
This may or may not be understandable from your point of view. I you are beginning at Connections, I suggest that you start with Zero to Hero Guide or Connections Wiki
RAA = Run As Administrator
CLAA = Command Line As Administrator
Server B
- For each server, create the administrative user directly on the server (not on the AD domain), add him to Administrators and the group that allow them to use windows at a distance. Log in with this user.
- RAA - Install DB2 without a response file. Do not start SSH server automatically. No notifications.
- Create LCUSER and add him to DB2USERS group.
- CLAA - add licence for DB2, if you have one
- CLAA - Configure Unicode
- CLAA - Database creation wizard : Run dbwizard.bat then stop and start db2
- RAA - Install TDI. Do not specify working directory
- CLAA - Install TDI FP7
- Modifiy runtime memory of C:\IBM\TDI\V7.1\ibmdisrv.bat
- CLAA - Launch population wizard. Just fill the DN of LDAP Bind User. LDAP user search base is empty. "CountryCode" might be set to "null"
- Have a cognos administrative account in LDAP
- Install DSClient
- Install WAS 8 and FP5
- Create a typical Application Server profile
- Update with ifpm62615 and ifpm71430
- Get CognosConfig and copy it on the ServerB. Get db2jcc.jar and db2jcc_license_cu.jar from C:\IBM\SQLLIB\java and put them into C:\Sources\CognosConfig\BI-Customization\JDBC
- Modifiy cognos-setup.properties accordingly to your environnement. (Cognos node name : YOURSERVERNode01, installation directories : C:\IBM\CognosBI, C:\IBM\CognosTF and C:\IBM\CognosTF\PowerCubes)
- CLAA - Launch cognos-setup.bat
- CLAA - Launch cognos-configure.bat
- Stop Cognos server and (CLAA) Federate node to ServerA. Then from Dmgr console (serverA) full resynchronize. Start Cognos server.
- Validate Cognos Server
Annex : command lines
4.
db2licm -l
db2licm -a db2ese_o.lic
5.
db2set DB2CODEPAGE=1208
db2start
db2set
8.
c:\IBM\TDI\V7.1\bin\applyUpdates.bat -update TDI-7.1-FP0007.zip
c:\IBM\TDI\V7.1\bin\applyUpdates.bat -queryreg
9.
"%TDI_JAVA_PROGRAM%" -Xms256M -Xmx1024M -Xnojit -classpath "%TDI_HOME_DIR%\IDILoader.jar" %ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %*
12.
db2 catalog tcpip node db2node remote serverB.domain.com server 50000
db2 catalog database COGNOS as COGNOS at node db2node
db2 catalog database METRICS as METRICS at node db2node
20.
In C:\IBM\WebSphere\AppServer\profiles\AppSrv01\properties\soap.client.props set :
com.ibm.SOAP.requestTimeout=600
C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin> addnode serverA.domain.com 8879 -includeapps -username wasadmin -password passw0rd
21.
Processes : BIBusTKServerMain, BmtMDProviderMain, cgsLauncher
http://serverB.domain.com:9081/cognos/servlet
http://serverB.domain.com:9081/cognos/servlet/dispatch
Server A
- RAA - Install Installation Manager (I use 1.6.2, 32bits)
- Install WAS 8 and FP 5
- Create a typical Cell profile
- Update with ifpm62615 and ifpm71430
- At this point I usually have to install Visual C++ runtime library and reboot, else I would get an error at next stage
- Install IBM HTTP Server 8.0.0.5 for WAS, Websphere Plugin 8.0.0.5 for WAS and Websphere Customization Toolbox 8.0.0.5 (consists of 3 repository, Webphere Supplements, FP5 for Supplements and FP5 for the Toolbox)
- Launch web server plugin configuration tool :
- add IHS_Location at C:\IBM\Websphere\Plugins
- Create a webserver plugin configuration, with ihsadmin for user ID
- Install IBM HTTP Administration as a service
- unique server web name : connections and not webserver1
- local installation
- AppSrv01 profile
- Put shortcuts (Dmgr stop/start, Node stop/start, Administrative console) on the desktop
- Start Dmgr and setup Federated Repositories ("Distinguished name of a base entry that uniquely identifies" should be set to "root" with a Domino LDAP). Set as current.
- Enable Application Security. Configure SSO. Log out, restart Dmgr, check groups and users.
- Get db2jcc4.jar and db2jcc_license_cu.jar from C:\IBM\SQLLIB\java in ServerB and put them in C:\IBM\SQLLIB\java
- Install Connections (cluster name : CL, server name : connections_server). Stop everything, start nodes, full resynchronize the nodes. Stop everything, start everything, Connections last.
- Connections is working!
10.
No comments:
Post a Comment