TEPS 6.2 Client Java Upgrade

In order for clients to access to TEPS upgraded to ITM6.2 for the first time, they'll need to have the IBM JRE 1.5 installed on their system.

It's a very straightforward process, but if you need some guidance, the steps are outlined below.

1. Have client access TEPS via a browser session: http://<teps_server>:1920///cnp/kdh/lib/cnp.html
   

2. TEPS will detect the necessary JRE is not available and push down the ibm-java2.exe
   

   
   

3. Accept the installation and accept all the defaults EXCEPT in STEP #7
   

   
   

    
    

   
   

4. Next
   

   
   

    
    

5. Yeah yeah yeah… select 'Yes' for the EULA
   

   
   

    
    

6. Next
   

   
   

    
    

7. **IMPORTANT** Select 'NO' for SystemJVM
   

   
   

    
    

8. Confirm and select 'Next'
   

   
   

    
    

    
    

   
   

    
    

9. 'Next' again…
   

   
   

    
    

10. Select 'Finish'
    

    
    

     
     

11. You should see the "Java Compatible" Logo and progress bar in the browser
    

    
    

     
     

12. Select 'Always trust content…" or not, it really won't matter.
    

    
    

     
     

13. The Java plug-in settings are covered in another post, but you can click 'Help' here for more information
    

    
    

     
     

     
     

     
     

     
     

     
     

     
     

     
     

     
     

     
     

     
     

     
     

     
     

     
     

  

Parse Download Director dlmgr.pro

If you use the IBM Passport Advantage or PartnerWorld portal to download software, you no doubt want to have the filenames renamed to something more meaningful than the software part number. This script will rename files based on the parsed info in the dlmgr.pro file. Example

jdsmedia@deantp1 /cygdrive/c/DownloadDirector $ ls -1 

C1FT9EN.zip 

C1FU3EN.tar 

C1FU4EN.tar 

C473DIE.exe 

dlmgr.pro 

itmpatchagents.zip 

itmsup.zip 

jdsmedia@deantp1 /cygdrive/c/DownloadDirector $ /usr/local/bin/parse_ddpro.pl 

PWD is /cygdrive/c/DownloadDirector 

mv C1FU4EN.tar ITM_Version_6_1_Vol_6_Fixpack_7_Linux_Intel_C1FU4EN.tar 

mv C1FT9EN.zip ITM_Version_6_1_Vol_1_Fixpack_7_Windows_Plat_C1FT9EN.zip 

mv C1FU3EN.tar ITM_Version_6_1_Vol_7_Fixpack_7_Linux_Intel_P_C1FU3EN.tar

 

DOWNLOAD: parse_ddpro

 
 

Trackback: http://www.jdsmedia.net/miscellaneous/parse-download-director-dlmgrpro-2

Extract TAR files over SSH

Instead of copying a large tar file over ssh then extracting, take care of the whole process with one command:

cat <tarfile> | ssh –C user@remotehost "(cd <targetdirectory> && tar –xf -)"

This will stream the tarfile over a compressed ssl tunnel and the other side will only extract if the target directory exists. The "targetdirectory" piece I used as a good prevention to blowing files all over an undesired/unexpected location.

Trackback: http://www.jdsmedia.net/tivoli/tivoliscripts/extract-tar-files-over-ssh

Copyright of http://www.jdsmedia.net 2006-2008

Parse Download Director dlmgr.pro

If you use the IBM Passport Advantage portal to download software, you no doubt want to have the filenames renamed to something more meaningful than the software part number. This script will rename files based on the parsed info in the dlmgr.pro file. Example

jdsmedia@deantp1 /cygdrive/c/DownloadDirector $ ls -1

C1FT9EN.zip

C1FU3EN.tar

C1FU4EN.tar

C473DIE.exe

dlmgr.pro

itmpatchagents.zip

itmsup.zip

jdsmedia@deantp1 /cygdrive/c/DownloadDirector $ /usr/local/bin/parse_ddpro.pl

PWD is /cygdrive/c/DownloadDirector

mv C1FU4EN.tar ITM_Version_6_1_Vol_6_Fixpack_7_Linux_Intel_C1FU4EN.tar

mv C1FT9EN.zip ITM_Version_6_1_Vol_1_Fixpack_7_Windows_Plat_C1FT9EN.zip

mv C1FU3EN.tar ITM_Version_6_1_Vol_7_Fixpack_7_Linux_Intel_P_C1FU3EN.tar

DOWNLOAD: parse_ddpro

TEPS: migrate-export.bat does not export MS-SQL

Just discovered something which caused me some headache. The migrate-export.bat generates DB2 syntax statements by default, regardless if you're using MS SQL or not for TEPS. Go ahead and try to import the 'saveexport.sql' into your TEPS SQL db, it will cause some fun corruption. An APAR exists, but it still has not made it into ITM6.2.

APAR IZ21307

MIGRATE EXPORT/IMPORT SCRIPTS FAIL FOR MICROSOFT SQL SERVER

Problem Description:

The migrate-export.bat and migrate-import.bat scripts do not

work correctly when the TEPS database is Microsoft SQL Server.

The scripts incorrectly detect the database type to be DB2, and

insert SQL statements in the saveexport.sql file that are

invalid in SQL Server. Attempting to import the saveexport.sql

file into a TEPS using SQLServer will result in several SQL

errors and data will be missing from the TEPS database.

Circumvention:

Manually edit the migrate-export.bat script and change the errorlevel

checks at line 29 and 35 to 1 from 0.