Specifying the URL to launch TADDM views

To launch TADDM views in context from other Tivoli applications, you must specify a URL.

The URL format for launching in context is:
Protocol://TADDMHostname:TADDMPort/ContextRoot/?queryString
The following list describes the valid values for each variable in the URL format:
Protocol
The Web protocol to use. Valid values are http or https.
TADDMHostname
The host name for the TADDM server to which you are launching.
TADDMPort
The port number for the TADDM server to which you are launching. The default value is 9430.
ContextRoot
The following values are valid:
cdm/servlet/LICServlet
The relative path to the Java™ servlet that is deployed in the Apache Tomcat server for TADDM 7.3.0, and in the WAS Liberty Profile server for TADDM 7.3.0.1, and later, and later.
cdm/queryHomePage.do
The relative path to the Query Home Page, when launched from IBM® Tivoli Monitoring, using single sign-on, and specifying search text.
queryString
Contains name-value pair parameters that are delimited by separators. The format for a name-value pair is name=value. Use = to separate names and values, and use & to separate name-value pairs.
The following list describes the valid name-value pairs that can be used in the queryString variable:
view
Specifies that you want to display change history.

The only valid value is changehistory.

days_previous
Specifies the time period (the number of past days) for which to show the change history of a particular configuration item.

The valid value is a positive integer.

hoursback
Specifies the time period (the number of past hours) for which to show the change history of a particular configuration item.

The valid value is a positive integer.

guid
Specifies the Globally Unique Identifier (GUID) for a configuration item.

For the domain server and the synchronization server, Table 1 lists the valid values for the graph parameter and indicates whether the guid parameter is optional or required based on the respective graph value.

If the graph parameter is specified with any of the following values, the guid parameter is optional:
  • businessapplications
  • applicationinfrastructure
  • physicalinfrastructure
If the graph parameter is specified with any other type of topology graph, the guid parameter is required.
The valid value is a valid string representation of a GUID, as shown in the following example: 
BA2842345F693855A3165A4B5F0D8BDE

You should specify only one GUID for each URL request for launch in context.

graph
Specifies the type of topology graph to be launched.

If you also specify a configuration item by providing its GUID on the guid parameter, the requested configuration item is then selected, if it is found in the topology graph that is specified on this graph parameter.

For the domain server and the synchronization server, Table 1 lists the valid values for the graph parameter and indicates whether the guid parameter is optional or required based on the respective graph value.

Table 1. Valid graph values and their relationship to the guid parameter
  Valid value Is the guid parameter optional or required with this graph value?
Domain server businessapplications Optional
applicationinfrastructure Optional
physicalinfrastructure Optional
For custom collection objects:
  • ba_infrastructure
 Required
Synchronization server businessapplications Optional
physicalinfrastructure Optional
For custom collection objects:
  • ba_infrastructure
 Required
Note: The other graph types that were used in the previous TADDM releases to render particular grouping entities by GUID are deprecated. However, to ensure compatibility with older versions, if you specify an old graph type with a GUID, the request is redirected to the new topology type.
username
Specifies the user name used to log in to TADDM.
password
Specifies the password used to log in to TADDM.
launchsource
The only valid value is ITM. It is always used with the searchtext=search_term name-value pair.
The search is confined to the configuration items of type ComputerSystem and TMSAgent, listed in the $COLLATION_HOME/etc/cdm/xml/itm_query_components.xml configuration file.
From the Query Home Page results, for each configuration item listed, you can launch the following views:
  • Change History pane
  • Details pane
  • Data Management Portal, displaying the Details pane
searchtext
Specifies the search term. It is always used with the launchsource=ITM name-value pair.

Examples of how to specify the URL

The following examples show how to specify the URL to launch TADDM views:
URL for launching the Data Management Portal, without entering authorization information separately
http://home.taddm.com:9430/cdm/servlet/LICServlet?username=administrator
&password=adminpwd&guid=BA2842345F693855A3165A4B5F0D8BDE
If you are using a trusted connection, you must use only credentials as part of the URL for launching in context because the user name and password are not encrypted.
URL for launching the Query Home Page window for IBM Tivoli Monitoring when using single sign-on and searching for a configuration item that matches the search text
http://home.taddm.com:9430/cdm/queryHomePage.do?launchsource=itm&searchtext=127.0.0.1
URL for showing a topology of a custom collection indicated by the guid parameter
http://home.taddm.com:9430/cdm/servlet/LICServlet?username=administrator&password=adminpwd&graph=ba_infrastructure&guid=BA2842345F693855A3165A4B5F0D8BDE