RE: cq.ini KFW* entries for DB2 Warehouse.
| Newsgroups | gmane.comp.sysutils.tivoli.general,gmane.comp.sysutils.tivoli.tme10 |
|---|---|
| Message-ID | <EA5FD7F404DE694BB310D050B12764960D9AA049@WFS0127A.corp1.ad1.seb.net> |
Hi, I’m using a type4 driver. WHP is using it on the same box. I will try and run itmcmd manage despite port regulations….. /Gus From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: den 16 februari 2013 00:12 To: Discussion list for Tivoli product and Tivoli Ready products. Subject: RE: [TME10] cq.ini KFW* entries for DB2 Warehouse. Yeah, the username, password and TDW URL are all encrypted. Anyway, despite the fact that you're using a type 4 (aka "Universal") jdbc driver--and thus should NOT need any DB2 products installed on the TEPS--because the DB2 runtime client is free, just install it on the TEPS and catalog the remote TDW node and dbase and see if things magically work. Otherwise you *might* be using a type 2 driver which doesn't utilize the DRDA architecture that type 4 uses...which can be verified by issuing: com.ibm.db2.java.jcc.DB2Jcc -version ...assuming the db2jcc.jar is in your class path. On Feb 15, 2013 9:26 AM, <[email protected]<mailto:[email protected]>> wrote: Hi no I didnt replaced them with my interp. (-: But I think that the DB2 Warehouse connection from a linux TEPS uses the DB2 client. The doc says to catalog the remote Warehouse DB which does’nt, make sense if you are running JDBC. Besides I think that the example I took was from someone who moved from Oracle Warehouse to DB2. Oracle Warehouse is using JDBC for sure. And this case deletes the references to Oracle when configuring teps. But the thing that puzzles me is that itmcmd manage (which I cant run) has Warehouse references to jdbc driver jdbc url etc. for DB2. So I’m a bit confused now on what the Warehouse connection is really using. Therfore I asked for cq.ini ref’s. But I just found out that the reference in cq.ini is encrypted SIGH! /Gus From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Venkat Saranathan Sent: den 15 februari 2013 15:37 To: Discussion list for Tivoli product and Tivoli Ready products. Subject: Re: [TME10] cq.ini KFW* entries for DB2 Warehouse. Gus, You haven't tried adding them verbatim, have you? The value for <arch> should be "lx8263". Also, make sure that you are replacing the existing values (if available), not adding duplicating rows. You probably did the right way but just thought of checking that first. with warm regards, Venkat Saranathan Gulf Breeze Software. Visiting Pulse 2013? Stop by our booth in the Expo and ask your Tivoli questions. On Fri, Feb 15, 2013 at 6:33 AM, <[email protected]<mailto:[email protected]>> wrote: Hi all. When I installed my teps on RHEL a chose not to configure a TDWH. It runs on Derby as TEPS DB. Node and db is cataloged on the DB2 client installed on the box. Not sure if it is needed for TEPS->TDWH connection though, since it looks like below it is using JDBC? DB2 is at version 9.7 on a remote windows server. S&P + WHP is running fine and I can see data flowing to TDWH tables. When I go back and run itmcmd config –A cq I don’t get prompted for more than DB2, Database name, user and pwd Googled around a bit and found (http://www-01.ibm.com/support/docview.wss?uid=swg21394004) that I need: <arch>|WHCLASS| <arch> |WHDB2ATTR|KFWJDBCDRIVER=;KFWDSURL=;| <arch>|WHURL| In */.ConfigData/kcqenv Tried adding these empty rows to the file and reran config of teps. Same result no questions to add these. I can’t run X either due to port restrictions so itmcmd manage is not an option. Can someone share KFW_* cq.ini entries for a remote TDWH on DB2? /Gus _______________________________________________ TME10 mailing list [email protected]<mailto:[email protected]> Unsubscribe:[email protected]<mailto:Unsubscribe%[email protected]> _______________________________________________ TME10 mailing list [email protected]<mailto:[email protected]> Unsubscribe:[email protected]<mailto:Unsubscribe%[email protected]> _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected]