Project Overview
Total Page：16
File Type：pdf, Size：1020Kb
Project Overview
This guide builds upon Part 1 of the sample Connections small deployment. In that guide, we installed the core Connections applications into a two-node WAS cluster with separate systems hosting the DB2 backend databases and the IHS web server.
In this guide, we will install a two-node cluster of Cognos BI Servers on the same systems running our core applications cluster. The Cognos Transformer component will reside with TDI and DB2 on the data node.
Before beginning this guide, you must have completed Part 1 of the deployment. Required installation files
Component IBM part numbers/Fix Central links File name
IBM Cognos Business CN1YPML bi_svr_64b_10.2.2_win_ml.tar.gz Intelligence Server 64- bit 10.2.2 Windows Multilingual
IBM Cognos Business CN1Z0ML bi_trfrm_10.2.2_win_ml.tar.gz Intelligence Transformer 10.2.2 Windows ML
*IBM Connections V5.5 5.5.0.0-IC-D1-CognosWizard- 5.5.0.0-IC-D1-CognosWizard- Cognos Wizard for LO87407-Windows LO87407-Windows.zip Windows Multilingual
*The Cognos Wizard part number CN80GML that is available on Passport Advantage should not be used. It is replaced in whole by the file in the table above. Chapter 1 – Pre-installation tasks 1.1 Chapter overview
Before installing and configuring the Cognos components, a few prerequisite configurations must be made to the sample environment. These are tasks similar to ones performed in Part 1 but are specific to the Cognos components we are configuring in this guide. 1.2 Create the power cube shared directory
About this task
Cognos Transformer builds datasets known as power cubes that are read by Cognos BI Server and form the basis of the statistics that are displayed in Connections Metrics. The power cubes must be available in a shared location that each Cognos BI Server node can access.
Procedure
1. Log into data.acme.com as the domain Administrator.
2. Right-click the Start button and click File Explorer.
3. Navigate to C:\IBM\Connections\data\shared.
4. Create the subdirectory C:\IBM\Connections\data\shared\cognos\powercubes. 1.3 Copy the JDBC driver to the Transformer node
About this task
The Cognos components require a JDBC driver to connect to the database server. The driver already exists for the Cognos BI nodes based on the core applications installed in Part 1, but it must be added for the Transformer node.
Procedure
1. Log into data.acme.com as the domain Administrator.
2. Create the directory C:\IBM\JDBC.
3. Navigate to C:\IBM\SQLLIB\java.
4. Copy db2jcc4.jar and db2jcc_license_cu.jar to C:\IBM\JDBC. 1.4 Create the application server profiles
About this task
The Cognos installer requires two pre-existing application server profiles. During Cognos installation, the profiles will be federated to the Connections cell, and new application servers will be created. The application servers created in this step are temporary and only required during Cognos installation. They can be deleted once installation is successfully completed.
Procedure
1. Log into ic1.acme.com as the domain Administrator.
2. Click Start -> Windows PowerShell.
3. Type cd C:\IBM\WebSphere\AppServer\bin and press Enter.
4. Type .\manageprofiles.bat -create -profileName cognos -profilePath C:\IBM\WebSphere\AppServer\profiles\cognos -templatePath C:\IBM\WebSphere\AppServer\profileTemplates\default -nodeName ic1_cognos01 -cellName ic1_cell02 -appServerNodeName ic1_TEMP_FOR_COGNOS -serverName ic1_TEMP_FOR_COGNOS -enableAdminSecurity true -adminUserName wasadmin -adminPassword
5. Confirm that you see the message "INSTCONFSUCCESS: Success: Profile cognos now exists" when the manageprofiles.bat command completes.
6. Log into ic2.acme.com as the domain Administrator.
7. Click Start -> Windows PowerShell.
8. Type cd C:\IBM\WebSphere\AppServer\bin and press Enter. 9. Type .\manageprofiles.bat -create -profileName cognos -profilePath C:\IBM\WebSphere\AppServer\profiles\cognos -templatePath C:\IBM\WebSphere\AppServer\profileTemplates\default -nodeName ic2_cognos01 -cellName ic2_cell02 -appServerNodeName ic2_TEMP_FOR_COGNOS -serverName ic2_TEMP_FOR_COGNOS -enableAdminSecurity true -adminUserName wasadmin -adminPassword
10. Confirm that you see the message "INSTCONFSUCCESS: Success: Profile cognos now exists" when the manageprofiles.bat command completes. Chapter 2 – Set up Cognos BI Server 2.1 Chapter overview
This chapter walks you through installing and configuring the two-node Cognos BI Server cluster. These servers will run on the same ic1.acme.com and ic2.acme.com systems that also run the core applications clusters.
During the installation tasks for the primary and secondary BI Servers, pay special attention to the requirement to disable any firewalls protecting the systems. The installation tasks attempt to connect to the new application servers, and this happens before the port numbers for the new servers are known to the admin. If these ports are blocked during the installation, the install will not complete and leave the servers in a broken state. 2.2 Install the primary BI Server
About this task
This task installs the primary BI Server node. Before beginning, make sure you have done the following:
Started the deployment manager on mgmt.acme.com
Started the DB2 server on data.acme.com
Disabled the firewall on ic1.acme.com
Procedure
1. Log into ic1.acme.com as the domain Administrator.
2. Open 5.5.0.0-IC-D1-CognosWizard-LO87407-Windows.zip and extract IBM_Cognos_Wizard_5.5_win.exe to a temporary directory. Open IBM_Cognos_Wizard_5.5_win.exe and extract the contents to C:\Temp\Install_Cognos_Wizard.
3. Open bi_svr_64b_10.2.2_win_ml.tar.gz and extract the contents of bi_svr_64b_10.2.2_win_ml.tar into C:\IBM\Temp\Install_Cognos_BI. Note: extract all files inside the .tar file to the indicated directory. Cognos components are distributed as gzip files, so you will need a decompression program capable of reading them.
4. If necessary, use the startServer command to start the ic1_TEMP_FOR_COGNOS application server.
5. Click Start -> Apps -> IBM Installation Manager.
6. Click File -> Preferences -> Repositories.
7. Click the Add Repository button and browse to C:\Temp\Install_Cognos_Wizard\IBM_Cognos_Install_Windows\CognosWizard.
8. Select repository.config and click Open. 9. Click OK twice.
10. Click Install.
11. Select Cognos Wizard and click Next.
12. Accept the license agreement and click Next.
13. On the package group panel, select Create a new package group and change the installation directory to C:\IBM\Cognos. Click Next.
14. On the features to install panel, select Primary BI Server. Click Next.
15. Make the following selections on the configuration panel:
a. Local Node Information:
i. Check both You must make sure... boxes.
ii. Installation location: C:\IBM\WebSphere\AppServer
iii. Local node profile: cognos
iv. Host Name: ic1.acme.com
v. Administrator user ID: wasadmin
vi. Administrator password:
vii. SOAP port number: Enter the value of SOAP_CONNECTOR_ADDRESS found in C:\IBM\WebSphere\AppServer\profiles\cognos\properties\portdef.props. For example, 8881.
viii. Deployment Manager Host Name: mgmt.acme.com
ix. Deployment Manager SOAP port number: Enter the value of SOAP_CONNECTOR_ADDRESS found in C:\IBM\WebSphere\AppServer\profiles\dmgr\properties\portdef.props on mgmt.acme.com. For example, 8879. x. Deployment Manager Administrator user ID: icadmin
xi. Deployment Manager Administrator password:
xii. Click the Validate button, confirm successful validation, and click OK.
xiii. Click Next. b. Cognos Topology Information:
i. Cluster name: ICCognosCluster
ii. Server name: ICCognosCluster_1
iii. Web context root: cognos
iv. Click Next. c. Cognos DB Information:
i. Database Type: DB2 Universal Database
ii. JDBC driver location: C:\IBM\JDBC
iii. Cognos Database Name: COGNOS
iv. Cognos Host Name: data.acme.com
v. Cognos Port: 50000
vi. Cognos User ID: LCUSER
vii. Cognos Password:
viii. Click Validate, confirm successful validation, and click OK.
ix. Click Next. d. Cognos BI Server Installers Location: i. Administrator user ID: icadmin
ii. Administrator password:
iii. BI Server Installer Location: C:\Temp\Install_Cognos_BI\winx64h\issetup.exe
iv. PowerCube Location: \\data.acme.com\shared\cognos\powercubes
v. Click Next.
e. Cognos LDAP Information:
i. Select Add both users and groups now.
ii. User names: icadmin
iii. Group names: icadmins
iv. Click Next.
16. Click Install.
17. Confirm successful installation and click Finish.
18. Re-enable the firewall on ic1.acme.com. 2.3 Configure firewall for primary BI node agent
About this task
The node agent uses a set of ports for its operations. This task configures the operating system firewall to open those ports to assure correct operation.
Procedure
1. Log into mgmt.acme.com as the domain Administrator.
2. Click Start -> Apps -> IBM WebSphere -> Administrative console.
3. Log into the administrative console as the icadmin user.
4. Navigate to System administration -> Node agents.
5. Click the nodeagent link for ic1_cognos01.
6. Click the plus sign next to Ports to expand the list of ports. Make a note of all ports listed.
7. Log into ic1.acme.com as the domain Administrator.
8. Click Start -> Administrative Tools and open Windows Firewall with Advanced Security.
9. Click Inbound Rules and then click New Rule in the right-most column.
10. Select Port and click Next.
11. Choose TCP and Specific local ports.
12. In the Specific local ports field, enter all port numbers from the list shown in the administration console from Step 6.
13. Click Next. 14. Choose Allow the connection and click Next.
15. Select all profiles and click Next.
16. Enter a name for the rule and click Finish. For example, ICCognos Node Agent - TCP.
17. Click Inbound Rules and then click New Rule in the right-most column.
18. Select Port and click Next.
19. Choose UDP and Specific local ports.
20. In the Specific local port field, enter all port numbers from the list shown in the administration console from Step 6.
21. Click Next.
22. Choose Allow the connection and click Next.
23. Select all profiles and click Next.
24. Enter a name for the rule and click Finish. For example, ICCognos Node Agent - UDP. 2.4 Configure firewall for primary BI application server
About this task
The application server uses a set of ports for its operations. This task configures the operating system firewall to open those ports to assure correct operation.
Procedure
1. Log into mgmt.acme.com as the domain Administrator.
2. Click Start -> Apps -> IBM WebSphere -> Administrative console.
3. Log into the administrative console as the icadmin user.
4. Navigate to Servers -> Server Types -> WebSphere application servers.
5. Click ICCognosCluster_1.
6. Click the plus sign next to Ports to expand the list of ports. Note: leave this list on the screen for reference in a later step.
7. Log into ic1.acme.com as the domain Administrator.
8. Click Start -> Administrative Tools -> Windows Firewall with Advanced Security.
9. Click Inbound Rules and then click New Rule in the right-most column.
10. Select Port and click Next.
11. Choose TCP and Specific local ports.
12. In the Specific local ports field, enter all port numbers from the list shown in the administration console from Step 6.
13. Click Next. 14. Choose Allow the connection and click Next.
15. Select all profiles and click Next.
16. Enter a name for the rule and click Finish. For example, ICCognosCluster_1 - TCP.
17. Click Inbound Rules and then click New Rule in the right-most column.
18. Select Port and click Next.
19. Choose UDP and Specific local ports.
20. In the Specific local ports field, enter all port numbers from the list shown in the administration console from Step 6.
21. Click Next.
22. Choose Allow the connection and click Next.
23. Select all profiles and click Next.
24. Enter a name for the rule and click Finish. For example, ICCognosCluster_1 - UDP. 2.5 Install the secondary BI server
About this task
Before beginning this task, make sure you have done the following:
Started the deployment manager on mgmt.acme.com
Started the DB2 server on data.acme.com
Disabled the firewall on ic2.acme.com
Procedure
1. Log into ic2.acme.com as the domain Administrator.
2. Open 5.5.0.0-IC-D1-CognosWizard-LO87407-Windows.zip and extract IBM_Cognos_Wizard_5.5_win.exe to a temporary directory. Open IBM_Cognos_Wizard_5.5_win.exe and extract the contents to C:\Temp\Install_Cognos_Wizard.
3. Open bi_svr_64b_10.2.2_win_ml.tar.gz and extract the contents of bi_svr_64b_10.2.2_win_ml.tar into C:\IBM\Installs\Install_Cognos_BI. Note: extract all files inside the .tar file to the indicated directory. Cognos components are distributed as gzip files, so you will need a decompression program capable of reading them.
4. If necessary, use the startServer command to start the ic2_TEMP_FOR_COGNOS application server.
5. Click Start -> Apps -> IBM Installation Manager.
6. Click File -> Preferences -> Repositories.
7. Click the Add Repository button and browse to C:\Temp\Install_Cognos_Wizard\IBM_Cognos_Install_Windows\CognosWizard.
8. Select repository.config and click Open. 9. Click OK twice.
10. Click Install.
11. Select Cognos Wizard and click Next.
12. Accept the license agreement and click Next.
13. On the package group panel, select Create a new package group and change the installation directory to C:\IBM\Cognos. Click Next.
14. On the features to install panel, select Secondary BI Server. Click Next.
15. Make the following selections on the configuration panel:
a. Local Node Information:
i. Check both You must make sure... boxes.
ii. Installation location: C:\IBM\WebSphere\AppServer
iii. Local node profile: cognos
iv. Host Name: ic2.acme.com
v. Administrator user ID: wasadmin
vi. Administrator password:
vii. SOAP port number: Enter the value of SOAP_CONNECTOR_ADDRESS found in C:\IBM\WebSphere\AppServer\profiles\cognos\properties\portdef.props. For example, 8881.
viii. Deployment Manager Host Name: mgmt.acme.com
ix. Deployment Manager SOAP port number: Enter the value of SOAP_CONNECTOR_ADDRESS found in C:\IBM\WebSphere\AppServer\profiles\dmgr\properties\portdef.props on mgmt.acme.com. For example, 8879. x. Deployment Manager Administrator user ID: icadmin
xi. Deployment Manager Administrator password:
xii. Click the Validate button, confirm successful validation, and click OK.
xiii. Click Next. b. Cognos Topology Information:
i. Cluster name: ICCognosCluster
ii. Server name: ICCognosCluster_2
iii. Web context root: cognos
iv. Click Next. c. Cognos DB Information:
i. Database Type: DB2 Universal Database
ii. Cognos Database Name: COGNOS
iii. Cognos Host Name: data.acme.com
iv. Cognos Port: 50000
v. Cognos User ID: LCUSER
vi. Cognos Password:
vii. Click Validate, confirm successful validation, and click OK.
viii. Click Next. d. Cognos BI Server Installers Location:
i. Administrator user ID: icadmin ii. Administrator password:
iii. BI Server Installer Location: C:\Temp\Install_Cognos_BI\winx64h\issetup.exe
iv. PowerCube Location: \\data.acme.com\shared\cognos\powercubes
v. Click Next.
16. Click Install.
17. Confirm successful installation and click Finish.
18. Re-enable the firewall on ic2.acme.com. 2.6 Configure firewall for secondary BI node agent
About this task
The node agent uses a set of ports for its operations. This task configures the operating system firewall to open those ports to assure correct operation.
Procedure
1. Log into mgmt.acme.com as the domain Administrator.
2. Click Start -> Apps -> IBM WebSphere -> Administrative console.
3. Log into the administrative console as the icadmin user.
4. Navigate to System administration -> Node agents.
5. Click the nodeagent link for ic2_cognos01.
6. Click the plus sign next to Ports to expand the list of ports. Make a note of all ports listed.
7. Log into ic2.acme.com as the domain Administrator.
8. Click Start -> Administrative Tools and open Windows Firewall with Advanced Security.
9. Click Inbound Rules and then click New Rule in the right-most column.
10. Select Port and click Next.
11. Choose TCP and Specific local ports.
12. In the Specific local ports field, enter all port numbers from the list shown in the administration console from Step 6.
13. Click Next. 14. Choose Allow the connection and click Next.
15. Select all profiles and click Next.
16. Enter a name for the rule and click Finish. For example, ICCognos Node Agent - TCP.
17. Click Inbound Rules and then click New Rule in the right-most column.
18. Select Port and click Next.
19. Choose UDP and Specific local ports.
20. In the Specific local port field, enter all port numbers from the list shown in the administration console from Step 6.
21. Click Next.
22. Choose Allow the connection and click Next.
23. Select all profiles and click Next.
24. Enter a name for the rule and click Finish. For example, ICCognos Node Agent - UDP. 2.7 Configure firewall for secondary BI application server
About this task
The application server uses a set of ports for its operations. This task configures the operating system firewall to open those ports to assure correct operation.
Procedure
1. Log into mgmt.acme.com as the domain Administrator.
2. Click Start -> Apps -> IBM WebSphere -> Administrative console.
3. Log into the administrative console as the icadmin user.
4. Navigate to Servers -> Server Types -> WebSphere application servers.
5. Click ICCognosCluster_2.
6. Click the plus sign next to Ports to expand the list of ports. Note: leave this list on the screen for reference in a later step.
7. Log into ic2.acme.com as the domain Administrator.
8. Click Start -> Administrative Tools -> Windows Firewall with Advanced Security.
9. Click Inbound Rules and then click New Rule in the right-most column.
10. Select Port and click Next.
11. Choose TCP and Specific local ports.
12. In the Specific local ports field, enter all port numbers from the list shown in the administration console from Step 6.
13. Click Next. 14. Choose Allow the connection and click Next.
15. Select all profiles and click Next.
16. Enter a name for the rule and click Finish. For example, ICCognosCluster_2 - TCP.
17. Click Inbound Rules and then click New Rule in the right-most column.
18. Select Port and click Next.
19. Choose UDP and Specific local ports.
20. In the Specific local ports field, enter all port numbers from the list shown in the administration console from Step 6.
21. Click Next.
22. Choose Allow the connection and click Next.
23. Select all profiles and click Next.
24. Enter a name for the rule and click Finish. For example, ICCognosCluster_2 - UDP. 2.8 Update cogstartup.xml on the BI servers to support clustering
About this task
The cogstartup.xml file must be manually updated to support multiple Cognos BI servers.
Procedure
1. Log into ic1.acme.com as the domain Administrator.
2. Open C:\IBM\Cognos\CognosBI\configuration\cogstartup.xml in a text editor.
3. Search the file for name="contentManagers". Leave the text editor open for use in Step 7.
4. Log into ic2.acme.com as the domain Administrator.
5. Open C:\IBM\Cognos\CognosBI\configuration\cogstartup.xml in a text editor.
6. Search the file for name="contentManagers". Leave the text editor open for use in Step 7.
7. Update both cogstartup.xml files to contain the same content manager URIs in the same order. For example:
a.
b.
c.
d.
e.
f.
8. Save and close both cogstartup.xml files. 2.9 Configure BI servers to use the HTTP server
About this task
This task updates the Cognos BI Server configuration to point to the IHS server on ic.acme.com.
Procedure
1. Log into ic1.acme.com as the domain Administrator.
2. Launch C:\IBM\Cognos\CognosBI\bin64\cogconfigw.exe.
3. Navigate to Local Configuration -> Environment.
4. Change Gateway Settings -> Dispatcher URIs for gateway to http://ic.acme.com:80/cognos/servlet/dispatch/ext.
5. Change Other URI Settings -> Dispatcher URI for external applications to http://ic.acme.com:80/cognos/servlet/dispatch.
6. Click File -> Save and then click Close.
7. Close IBM Cognos Configuration and choose No when asked to start the IBM Cognos service.
8. Repeat Steps 1-7 on ic2.acme.com. 2.10 Configure web server to trust application server certificates
About this task
This task guides you through the process of adding the application server certificates to the web server's key store to enable secure communications.
Procedure
1. Log into mgmt.acme.com as the domain Administrator.
2. Click Start -> Apps -> IBM WebSphere -> Administrative console.
3. Log into the administrative console as the icadmin user.
4. Navigate to Security -> SSL certificate and key management -> Key stores and certificates.
5. In the list of key stores, locate the ones named NodeDefaultTrustStore. There will be one for ic1_cognos01 and one for ic2_cognos01.
6. Click the ic1_cognos01 NodeDefaultTrustStore link.
7. Click the Signer certificates link on the right.
8. Check the box next to the certificate with the root label. Note: this certificate should also have the node name listed as one of the OU components (ic1_cognos01 or ic2_cognos01).
9. Click the Extract button.
10. Enter the path to a temporary file in which to save the certificate. For example, C:\Temp\ic1_cognos01.crt or C:\Temp\ic2_cognos01.crt.
11. Leave the default setting for Data type and click OK.
12. Navigate back to Security -> SSL certificate and key management -> Key stores and certificates. 13. Repeat Steps 6-11 for the ic2_cognos01 NodeDefaultTrustStore link.
14. Navigate back to Security -> SSL certificate and key management -> Key stores and certificates.
15. Click the CMSKeyStore link.
16. Click the Signer certificates link on the right.
17. Click the Add button.
18. In the Alias field, enter the node name. For example, ic1_cognos01 or ic2_cognos01.
19. In the File name field, enter the path to the first node's certificate in the temporary file created in Step 10. For example, C:\Temp\ic1_cognos01.crt or C:\Temp\ic2_cognos01.crt.
20. Leave the Data type field set to the default.
21. Click OK and then Save.
22. Repeat Steps 17-21 for the second node's certificate.
23. Click Servers -> Server Types -> Web servers -> webserver1 -> Plug-in properties.
24. Click the Copy to Web server key store directory button.
25. Click OK and Save. 2.11 Map the Cognos application to the web server
About this task
This task maps the Cognos application to the web server and updates the Connections LotusConnections- config.xml file to generate URLs using the web server host name.
Procedure
1. Log into mgmt.acme.com as the domain Administrator.
2. Click Start -> Apps -> IBM WebSphere -> Administrative console.
3. Log into the administrative console as the icadmin user.
4. Navigate to Applications -> Application Types -> WebSphere enterprise applications.
5. Click the Cognos application.
6. Click Manage Modules.
7. Select the checkbox next to IBM Cognos and then select the ICCognosCluster and webserver1 entries in the Clusters and servers box at the top of the page. Click Apply, OK, and then Save.
8. Navigate to Servers -> Server Types -> Web servers.
9. Select the checkbox next to webserver1 and click the Generate Plug-in button.
10. Select the checkbox next to webserver1 and click the Propagate Plug-in button.
11. Use the LCConfigService.checkOutConfig wsadmin command to check out the LotusConnections- config.xml file.
12. Open the checked-out LotusConnections-config.xml and search for "cognos". 13. Modify the clusterName value to ICCognosCluster and set the href and ssl_href values to point to the web server. For example:
a.
b.
c.
d.
e.
f.
g.
14. Save LotusConnections-config.xml and use the LCConfigService.checkInConfig wsadmin command to check the file back in.
15. Sync the ic1_cognos01 and ic2_cognos01 nodes and then restart the ICCognosCluster_1 and ICCognosCluster_2 application servers.
16. Restart IHS on ic.acme.com. 2.12 Update BI server security
About this task
This task removes unrestricted Cognos administration access for all users, leaving only the Connections admin with administrator access.
Before performing this task ensure you have done the following:
Started the ICCoreCluster cluster
Started the ICCognosCluster cluster
Started the IHS server
Procedure
1. Access https://ic.acme.com/cognos/servlet/dispatch/ext in a browser. This should redirect to https://ic.acme.com/metrics/login. Login as icadmin.
2. After successful login, you should be redirected to IBM Cognos Connection. Click the Log On link in the page header.
3. Click Launch -> IBM Cognos Administration from the page header.
4. Click the Security -> Cognos.
5. Locate the IBMConnectionsMetricsAdmin role and click the More link to the far right of the page.
6. Click Set properties -> Members -> Add.
7. Toggle on the Show users in the list option and then click IBMConnections.
8. Select icadmin in the list of entries and click the Add button to add the user to the Selected entries list on the right side of the page. 9. Click OK twice to return to the Security -> Cognos page.
10. Locate the System Administrators role and click the More link to the far right of the page.
11. Click Set properties -> Members.
12. Select Everyone in the list of entries and click the Remove.
13. Click OK.
14. Log into ic1.acme.com as the domain Administrator.
15. Launch C:\IBM\Cognos\CognosBI\bin64\cogconfigw.exe.
16. Navigate to Local Configuration -> Security -> Authentication -> Cognos.
17. Set Allow anonymous access to False.
18. Click File -> Save and then click Close.
19. Close IBM Cognos Configuration and choose No when asked to start the IBM Cognos service.
20. Repeat Steps 14-19 on ic2.acme.com.
21. Restart the ICCognosCluster_1 and ICCognosCluster_2 application servers. Chapter 3 – Set up Cognos Transformer 3.1 Chapter overview
In this chapter we will install the Cognos Transformer component. Transformer is not cluster-aware, so installing two instances on the two Cognos BI Server nodes is of limited usefulness. While possible to have a standby node, this increases administrative overhead without much benefit. For our purposes, Transformer will be considered a single node service like TDI or the WAS deployment manager. 3.2 Install Transformer
About this task
This task walks you through installing Cognos Transformer. Note that the Transformer installation preconfigures the operating system scheduled tasks that build the power cubes. In most cases, the defaults are sufficient, but they can be changed if needed. If you want to test Metrics immediately after installation, simply launch the build-all.bat script in C:\IBM\Cognos\Transformer\metricsmodel.
Procedure
1. Log into data.acme.com as the domain Administrator.
2. Open 5.5.0.0-IC-D1-CognosWizard-LO87407-Windows.zip and extract IBM_Cognos_Wizard_5.5_win.exe to a temporary directory. Open IBM_Cognos_Wizard_5.5_win.exe and extract the contents to C:\Temp\Install_Cognos_Wizard.
3. Open bi_trfrm_10.2.2_win_ml.tar.gz and extract the contents of bi_trfrm_10.2.2_win_ml.tar into C:\IBM\Installs\Install_Cognos_Transformer. Note: extract all files inside the .tar file to the indicated directory. Cognos components are distributed as gzip files, so you will need a decompression program capable of reading them.
4. Click Start -> Apps -> IBM Installation Manager.
5. Click File -> Preferences -> Repositories.
6. Click the Add Repository button and browse to C:\Temp\Install_Cognos_Wizard\IBM_Cognos_Install_Windows\CognosWizard.
7. Select repository.config and click Open.
8. Click OK twice.
9. Click Install. 10. Select Cognos Wizard and click Next.
11. Accept the license agreement and click Next.
12. Enter C:\IBM\IMShared for the Shared Resources Directory and click Next.
13. On the package group panel, select Create a new package group and change the installation directory to C:\IBM\Cognos. Click Next.
14. On the features to install panel, select Cognos Transformer. Click Next.
15. Make the following selections on the configuration panel:
a. Database Type: DB2 Universal Database
b. JDBC driver location: C:\IBM\JDBC
c. Database Name: METRICS
d. Host Name: data.acme.com
e. Port: 50000
f. User ID: LCUSER
g. Password:
h. Metrics local database name: METRICS
i. Click the Validate button, confirm successful validation, and click OK and Next.
16. Make the following selections on the Cognos Transformer Installers panel:
a. Transformer Installer Location: C:\Temp\Install_Cognos_Transformer\win32\issetup.exe
b. BI server URI: http://ic.acme.com:80/cognos
c. Administrator user ID: icadmin
d. Administrator password:
f. Click the Validate button, confirm successful validation, and click OK and Next.
17. Click Install.
18. Confirm successful installation and click Finish.