The Transaction Display Generator uses a template display to determine which objects to use in the generated displays.  The template must contain at least five objects, which must be added in the correct order.  The table below describes how these objects will be used, and the descriptions are in the order that they should be added to the template. These objects will be used to create the generated displays.  The objects in the generated displays are arranged with a predetermined layout and are generated with data attachment and drill down targets automatically assigned based on the information in TRANSACTIONS.ini.  Any additional objects will be copied directly to the generated displays, but will not be used when calculating the layout.

To create a template for the Transaction Display Generator, use the Display Builder to add objects to a display and save it.  You must include an object for each of the following elements in your template display:
 

Name	Description
transaction start /end component	Each transaction starts with a message being sent from a component, the start component, and ends with a message being received by a component, the end component.  The first object in the template file must be the graphical object used to represent the start and end components for each transaction.  This object must contain the object property "valueString". In the start component, this property will be assigned the name of the third argument of the "startBusTransaction" line in TRANSACTIONS.ini. In the end component, it will be set to the fourth argument of the "startBusTransaction" line of TRANSACTIONS.ini.  For example, if the following line is in TRANSACTIONS.ini:  startBusTransaction 'New Service Order' Siebel RoadRunner nso The valueString in the start component will be set to "Siebel". The valueString in the end component will be set to "RoadRunner".
intermediate component	All components between the start component and the end components in a transaction are intermediate components.  The second object in the template must be the graphic object used to represent all of the intermediate components in the transaction.   This object will be replicated for all of intermediate components listed in the TRANSACTIONS.ini file. The generated data attachment for the intermediate components will show the name of the  interface as well as summary information for that interface, the count, the latency and the rate.   The object will drill down to "ic.rtv" and pass the name of the component to the drill down display as "$component".  This object must contain the object property "title".  The title will be assigned the interface name which is the third argument in the interface line of  TRANSACTIONS.ini.   For example, the title will be set to "Siebel" if the following line is in TRANSACTIONS.ini:  interface NSO_Siebel-Oracle-IM2 Siebel The object must also contain the object property "valueTable".  The interface summary information, the latency, the count, and the rate are assigned to this property.
title	Each generated display will have a title bar listing the name of the business transaction it is displaying.  The third object in the template must be the object you would like to use for the title bar.  The object selected for the title bar must contain the object property "valueString".
table	The fourth object in the template must be a table.  This table will be used in the generated displays to show summary information for each interface in the transaction.
link	In the generated displays, each component in the transaction will have a link connecting it to the next component in the transaction.  The link represents the message that is sent from one component to the next and will display the size of the message.  The last object in the template display must be the link to use in the generated displays.  The same link will be used for all components in the generated displays.