Edit
Attach
P
rintable
r4 - 2013-11-25 - 15:48:29 - Main.dmmckinn
You are here:
TWiki
>
Deployment Web
>
DeploymentIntegrating
>
DeploymentIntegratingReporting
>
Db2V9RemoteCLMDataWarehouseConfiguration
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right"> ---+!! <font size=7>Rational Reporting for Development Intelligence (RRDI)</font> ---+!! <font size=5>How to setup a DB2 V9 remote CLM Data Warehouse on a reporting server location</font> %DKGRAY% Authors: Main.PhilippeChevalier <br> Build basis: Collaborative Lifecycle Management Solution (CLM) (Jazz Team Server (JTS), Rational Team Concert (RTC), Rational Quality Manager (RQM), Rational Requirements Composer (RRC)) 4.0.x. %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> <br> <font size=3>This topic describes the steps to catalog a remote CLM data warehouse database using DB2 V9 Client software.</font> <br> <br> ---++ 1. Select or verify the DB2 Client software package A possible interpretation of the following link leads to installing the DB2 32-bit Client version. Installing in 64-bit or 32-bit mode on a 64-bit OS http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m2/topic/com.ibm.rational.rrdi.admin.doc/topics/c_preinstall_OS_ovr.html If you attempt the installation on a 64-bit machine of the 32-bit DB2 client, it will result in failure. That is because the 32-bit package is not supported on a 64-bit implementation. The solution is to use the 64-bit client package for the DB2 client software, the package includes both 64 and 32 bit libraries. Recommended DB2 V9.7 Client software: IBM Data Server Runtime Client 9.7 for Linux on !AMD64 and Intel !EM64T systems (x64) English More details on the available DB2 packages can be found at this link: *Downloading IBM DB2 Version 9.7 for Linux, UNIX, and Windows*: http://www.ibm.com/support/docview.wss?uid=swg21378087 To install the package and setup the instance, review the following documentation: *Installing IBM Data Server Driver Package (Linux and UNIX)*: http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.dbclient.install.doc/doc/t0054799.html ---++ 2. Catalog the remote database node using a command on the server's client instance The following will define the communication channel to the remote DB2 server that services the CLM data warehouse database over TCP/IP. The command must be executed by the db2inst1 user which is associated to the db2inst1 default instance of DB2 Client Software. <verbatim> db2 CATALOG TCPIP NODE {node-name} REMOTE {server-name} SERVER {port-or-service-name} WHERE: {node-name} = The name you want to give to the node. {server-name} = The server IP or DNS. {port-or-service-name} = The port or services name defined on the original database instance. </verbatim> To identify the services name or port you can review the remote DB2 instance using the *get dbm cfg*, SVCENAME property and reviewing the /etc/services file or, speak to your physical DBA for details. Example of *get dbm cfg* (PICTURE) Example of "/etc/services file", see db2c_db2inst1 entry (PICTURE) Example with values and result: <verbatim> [db2inst1@repexample]$ db2 CATALOG TCPIP NODE DB2REPEX REMOTE db2repexam.ibm.com SERVER 50000 DB20000I The CATALOG TCPIP NODE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed. </verbatim> ---++ 3. Catalog the database instance of the CLM data warehouse using the report server client instance This will define the database name to use on the remote database node. The user constraints are the same as the catalog node section. <verbatim> db2 CATALOG DB {clm-dw-name} AS {clm-dw-name} AT NODE {local-node-name} WHERE: {clm-dw-name} = The name of the remote database {local-node-name} = The node we first catalog in this technote </verbatim> Example with values and result: <verbatim> [db2inst1@repexample]$ db2 CATALOG DB CLMDB AS CLMDB AT NODE DB2REPEX DB20000I The CATALOG DATABASE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed. </verbatim> ---++ 4. Test the catalogs Once the Node and the database have been cataloged, you can test the results using the following two commands: <a href="http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.cmd.doc/doc/r0001961.html?resultof=%22%64%62%32%22%20%22%6c%69%73%74%22%20%22%64%61%74%61%62%61%73%65%22%20%22%64%61%74%61%62%61%73%22%20" target="_blank">"list db directory"</a> which will list all databases cataloged on the current DB2 instance. <verbatim> [db2inst1@repexample]$ db2 list db directory System Database Directory Number of entries in the directory = 1 Database 1 entry: Database alias = CLMDB Database name = CLMDB Node name = DB2REPEX Database release level = d.00 Comment = Directory entry type = Remote Authentication = SERVER Catalog database partition number = -1 Alternate server hostname = Alternate server port number = </verbatim> and *connect to*, using the DB2 instance owner, which in the following example is db2inst1. <verbatim> [db2inst1@repexample bin]$ db2 connect to CLMDB user db2inst1 Enter current password for db2inst1: ******* Database Connection Information Database server = DB2/LINUXX8664 9.7.0 SQL authorization ID = DB2INST1 Local database alias = CLMDB [db2inst1@repexample]$ </verbatim> If both of these tests are returned without errors, you have a been successful in setting up the remote database. ---++ 5. Setting up the root user, for the DB2 Client environment to support RRDI setup and IBM Rational !WebSphere Profile In this example the assumption is that there is a default DB2 Client Instance and its name is db2inst1, and is owned by the OS user "db2inst1". The "root" user is the owner of the !WebSphere Java processes, and owns the RRDI Home directory. In the root home directory /root , create a Linux source file named *.RRDI_source*, insert the db2profile file absolute path, set the *<noautolink>DB2INSTANCE</noautolink>* environment variable, and assign it the instance name. <START ".RRDI_source"> # Configuration setup file for RRDI and db2 database on Linux # declare the instance the user will use for DB2 export !DB2INSTANCE=db2inst1 # set environment for db2 . /home/db2inst1/sqllib/db2profile <END> This file can be managed in different ways (loaded manually, or within a script that sets up the !WebSphere environment variables before starting the Java Virtual Machine). This example will use the "/root/.bash_profile", and insert the command *source .RRDI_source*. This will source the file to the environment every time the root user logs in. <br /><img alt="repexample.jpg" src="%ATTACHURL%/repexample.jpg" /> If the configuration is setup correctly, you can then execute the same steps indicated in point 4 of this technote with the "root" user. You should have positive results. ---+++++!! Related topics: [[http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.dbclient.install.doc/doc/t0054799.html][Manually configuring DB2 servers after installation]], [[DeploymentWebHome][Deployment web home]] ---+++++!! External links: * [[https://www.ibm.com][IBM]] ---+++++!! Questions and comments: %COMMENT{type="below" target="Db2V9RemoteCLMDataWarehouseConfigurationComments" button="Submit"}% %INCLUDE{"Db2V9RemoteCLMDataWarehouseConfigurationComments"}% <sticky></div></sticky>
Attachments
Attachments
Topic attachments
I
Attachment
Action
Size
Date
Who
Comment
jpg
repexample.jpg
manage
20.5 K
2013-11-25 - 15:43
UnknownUser
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r9
|
r6
<
r5
<
r4
<
r3
|
More topic actions...
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.