Launching TADDM in context without a GUID

TADDM certainly provides a cool way to be launched in a context, as documented at:

http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/index.jsp?topic=/com.ibm.taddm.doc_7.1/AdminGuide/r_cmdb_launchincontext.html

For example,

http://taddm_server:9430/cdm/servlet/LICServlet?guid=B435980E80FA39509EBFE294D70BA5C8

will launch TADDM Produce Console in the context of a GUID.

The problem arises when the launching application doesn't know the GUID.
I created a Java Server Page to bridge between such application and TADDM. It's available at:

http://docs.google.com/Doc?id=ddnnhc4w_307dffpq3gs

• Download the file as taddm_launcher.jsp
  
• Edit the line defining the TADDM_SERVER to your TADDM installation
  
• Copy the file to the TADDM Server to the directory /deploy-tomcat/cdm
• Point your browser to
  http://taddm_server:9430/cdm/taddm_launcher.jsp?name=computer_system_name
  replacing taddm_server and the computer_system_name accordingly

This work can certainly be expanded to launch other sections of TADDM and other kinds of resources (it works only with ComputerSystem objects).

The syntax of the Launch in Context URL can be found at:

TADDM Documentation

Extending TAMIT ASSETNUM attribute field length

Here is the procedure to extend the size of the attribute ASSETNUM in the ASSET MBO in TAMIT:

• Do a database backup
  
• Go To-> System Configuration -> Platform Configuration -> Database Configuration
• Object: ASSET
• Select ASSET
• Go to Attributes tab
• Select ASSETNUM
• Change the length to 32
• The attribute will be in Change mode
• Save it
• Go to List tab
• Select Action -> Managed Admin Mode
• Click Turn Admin Mode On
• Click Refresh Status until Admin Mode is ON
• Connect to TPAP DB
• db2 drop trigger multiassetloccip_u
• db2 drop trigger multiassetloccip_t
• Select Action -> Apply Configuration Changes
• Check Do you have a current backup?
• Click Start Configuring the Databsase
• Click Turn Admin Mode OFF
  

TDI class material

These are the links for the material used in the TDI class in Charlotte on Sep 18 - 20, 2008

Source CSV file: http://spreadsheets.google.com/pub?key=p4p_qEbMe9m6VL-TWV1NyQQ
Lab instructions: http://docs.google.com/Doc?id=ddnnhc4w_2793ph5zxcg
Presentation: http://docs.google.com/Presentation?id=ddnnhc4w_54f9tnwmd2

How to configure TADDM 7.1.1 to run BIRT reports

1. replace the reports.xml in dist/etc/cdm/xml
2. replace the dist/deploy-tomcat/cdm/WEB-INF/view/dm_newsummary_sidebar.jsp with the one here
3. untar birt-viewer.tar to dist/deploy-tomcat/
4. restart the server
5. Login to domain manager and you shd see the BIRT reports icon with a list of reports under the Analytics section

These files are available at: http://www.megaupload.com/?d=N1VTT5LT

Exporting data from TADDM

It's very simple to extract data from Tivoli Application Dependency Discovery Manager (TADDM), using Tivoli Directory Integrator (TDI) and the TADDM Connector, available at:

TADDM Connector at Tivoli OPAL

Using the TADDM Connector, you just specify the TADDM configuration information (host name, user, password, CI type), then drag and drop the fields into the desired Connector (for example, a CSV file, using the FileSystem Connector).

Setting the JDBC Transaction Isolation Level in TDI

As the JDBC Transaction Isolation needs to be set in the client side, I asked my Norwegian friends how to do it. As always, Eddie had the answer:

So you should have this option from TDI:

myJDBConnector.getConnector().getConnection().setTransactionIsolation( desiredLevel_int );


The Connection JavaDocs have this to say:

setTransactionIsolation
public void setTransactionIsolation(int level)
throws SQLException
Attempts to change the transaction isolation level for this Connection object to the one given. The constants defined in the interface Connection are the possible transaction isolation levels.
Note: If this method is called during a transaction, the result is implementation-defined.
Parameters:
level - one of the following Connection constants: Connection.TRANSACTION_READ_UNCOMMITTED, Connection.TRANSACTION_READ_COMMITTED, Connection.TRANSACTION_REPEATABLE_READ, or Connection.TRANSACTION_SERIALIZABLE. (Note that Connection.TRANSACTION_NONE cannot be used because it specifies that transactions are not supported.)

Throws:
SQLException - if a database access error occurs or the given parameter is not one of the Connection constants
See Also:
DatabaseMetaData.supportsTransactionIsolationLevel(int), getTransactionIsolation()

You will need to do this for each JDBC Connector with its own connection.

TDI class material

Here are the links for the TDI class:

Presentation: http://docs.google.com/Presentation?id=ddnnhc4w_19tsdmvbfk
Lab material: http://docs.google.com/Doc?id=ddnnhc4w_18fs4dpmcc