BrowserMetrix Version 2.0 Build Transaction Trace Analyzer Version 4.0 PL1 Build OPNET Authentication Service Version 1.

Transcription

1 1 Release Overview 1 Release Overview This section summarizes changes in the Version 2.x releases of the Transaction Trace Warehouse. Summary of Changes in Version 2.1 Versions of Related Components Version 2.1 of Transaction Trace Warehouse coincides with these versions of related components: AppInternals Xpert Version 8.5, Build 79 Note that Transaction Trace Warehouse Version 2.1 is required for transaction traces generated by Version 8.5 of JIDA and the dotnet data adapters. Transaction Trace Warehouse Version 2.1 can handle traces from earlier versions of the data adapters, but Version 2.0 will not work with Version 8.5 transaction traces. BrowserMetrix Version 2.0 Build 1035 Transaction Trace Analyzer Version 4.0 PL1 Build OPNET Authentication Service Version 1.0 OPNET Dashboards Version 2.0.W PL0 Build 8328 Integration with AppInternals Xpert BrowserMetrix A new component for AppInternals Xpert, BrowserMetrix, monitors end-user experience (EUE) for web applications, including cloud environments and mobile users. (BrowserMetrix Version 1.0 was previously available as an independent software-as-a-service offering called AppResponse Xpert SAAS.) Administrators configure web-based applications by adding JavaScript to Web pages they want to monitor. The script provides data to BrowserMetrix about response time, traffic, geography, platform type, and other measurements. BrowserMetrix is tightly integrated with this release of Transaction Trace Warehouse. When BrowserMetrix is configured to connect to Transaction Trace Warehouse (and both BrowserMetrix and Transaction Trace Warehouse use the same OPNET Authentication Service), users can see both BrowserMetrix and Transaction Trace Warehouse details in data views. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 Release Notes-1-1

2 1 Release Overview For example, the Transaction Details window in Transaction Trace Warehouse displays front-end details from BrowserMetrix. Users click in the chart to switch to BMX and see more front-end details: Users can also click the Front-End View link in Transaction Trace Warehouse to switch to the BrowserMetrix user interface: Release Notes-1-2 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

3 1 Release Overview Similarly, in the BrowserMetrix user interface, links switch to Transaction Trace Warehouse. Combined Installer for Transaction Trace Warehouse, BrowserMetrix, and OPNET Authentication Service Transaction Trace Warehouse is now distributed and installed as part of a new component installer that also installs BrowserMetrix and the OPNET Authentication Service. The component installer prompts users for the components they want to install. The OPNET Authentication Service is a required component for Transaction Trace Warehouse Version 2.1. It replaces the OPNET AAM server used by earlier versions of Transaction Trace Warehouse. See Migrating to OPNET Authentication Service for upgrade considerations. Link To and From Source Code to Related Transactions With additional configuration, users can link from source code in Visual Studio or Eclipse to related transactions in the Transaction Trace Warehouse. Similarly, they can open Visual Studio or Eclipse from the Transaction Details window in thetransaction Trace Warehouse. Once an administrator enables it, a download icon appears in the Top Calls tab of the Transaction Details window: OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 Release Notes-1-3

4 1 Release Overview In addition, users can link from source code to metric data in AppInternals Xpert desktop console and transaction data in Transaction Trace Analyzer. See the documentation supplement Linking Between Source Code and AppInternals Xpert Data included in these release notes for details. Other Changes Display Labels Change for ADO, JDBC, and Generic Categories The display labels in pie charts and tables changed as follows: ADO is now Database (ADO) JDBC is now Database (JDBC) Generic is now Application code Note that the search criteria values remain as ado, jdbc, and generic. Share this Search Preserves Search Settings in a URL There is a new Share this search icon next to the xx Matching Transactions label in the results area of the search screen. Click the icon to open a new browser tab or window with a URL that can be copied and sent to others. The URL preserves all search settings including the time range, search criteria, zoom range, and Refine Results settings. Users with Transaction Trace Warehouse accounts can browse to the URL and see the exact same results. Release Notes-1-4 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

5 Update Search Changes Search to Reflect Zoom and Refine Results Settings 1 Release Overview There is a new Update search icon next to the xx Matching Transactions label in the results area of the search screen. Click the icon to: Update the search time range based on the zoom selection Update the search criteria to query based on Refine Results settings Submit the search with these new criteria New Remote Calls Tab in Transaction Details Window A new tab in the Transaction Details window shows details of calls made by transactions that are not otherwise visible in the transaction map or other tabs (or in Transaction Trace Analyzer). This tab shows remote calls that are not already shown in the Outbound URLs tab or in the transaction map as remote calls to databases. Note that these remote calls do not appear in the transaction map. Property to Add Download to Transaction Trace Analyzer Icon in Search Results The file harvester.properties in the directory <installdir>\jboss\5.1.0\server\harvester\deploy\harvester\harvester.ear\ has a new property, show_txn_download_column. Set this property value to true to add a download icon to the Search screen results table. Users click the icon to open the selected transaction in Transaction Trace Analyzer. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 Release Notes-1-5

6 1 Release Overview Changing this property does not require restarting Transaction Trace Warehouse. Users must refresh their browsers or log out and in again. Note that changes to these settings are not preserved on upgrades. Property Settings Control Default Search Time Range and Number of Transactions Returned The file harvester.properties in the directory <installdir>\jboss\5.1.0\server\harvester\deploy\harvester\harvester.ear\ has the following properties that are new or have changed behavior: default_search_time_period_in_minutes specifies a shorter time range than the default of 60 minutes. The property is not new, but its behavior is changed so that values greater than 60 are ignored. default_max_search_results is a new property that specifies that searches will return fewer results than the default of 10,000 transactions. Values greater than 10,000 are ignored. Changes to these properties do not require restarting Transaction Trace Warehouse. Users must refresh their browsers or log out and in again. Note that changes to these settings are not preserved on upgrades. Documentation The documentation available from the support page has been updated with changes in Transaction Trace Warehouse Version 2.1: However, the documentation created by the Version 2.1 installation has not been updated. Help links in the user interface will not be up to date. Summary of Changes in Version 2.0 Enhanced Analysis Without Transaction Trace Analyzer The biggest change for this release is the new Transaction Details window that displays details about cross-tier transactions within the Transaction Trace Warehouse Web user interface. Previously, users had to download a transaction to Transaction Trace Analyzer to see a stitched view of cross-tier transactions that Transaction Trace Warehouse detected. Release Notes-1-6 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

7 1 Release Overview Now, users click the view details icon in the Search screen results table. The Transaction Details window is faster and easier than using the Transaction Trace Analyzer. It displays a transaction map and a series of tabs: Users browse tabs to see additional detail about the cross-tier transactions: Summary: summary of slowest tiers and components, and a pie chart with active time spent in different transaction tiers: Delays: pie chart with active time spent by method calls, grouped by different criteria SQL: slowest SQL statements executed by calls in all transaction tiers Inbound URLs: slowest inbound URLs for transactions in all tiers Outbound URLs: slowest outbound URLs for transactions in all tiers Top Calls: slowest method calls across all transaction tiers Exceptions: most frequently occurring exceptions for method calls for all transaction tiers Performance Metrics: thumbnail graphs for several AppInternals Xpert metrics showing resource consumption by the.net CLR (Common Language Runtime) or Java Virtual Machine (JVM) processes for each transaction tier. (Time alignment of these graphs requires synchronization of the system times on each tier. See the documentation for more details.) OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 Release Notes-1-7

8 1 Release Overview Users click the Download icon in the upper right of the window to download the combined cross-tier transactions and open them in Transaction Trace Analyzer. Transaction Trace Analyzer still provides these features not available in the Transaction Details window: Hierarchical tree view of all instrumented method calls Sequence diagram showing the flow of transactions across tiers from start to end Python scripting interface to add custom capabilities Users click the Report icon in the upper right of the Transaction Details window to open a separate browser window or tab with the same details on a single page. Since the Transaction Trace Warehouse saves the data for these reports, users can copy the URL and share the same details with other users by sending them the URL. Other User Interface Changes When users log in, the Transaction Trace Warehouse automatically shows results (the slowest transactions in the last hour). Previously, users had to click Search to see results. Autocomplete improvements: The autocomplete feature in the Transaction Search screen no longer requires the first letter of a matching value. Once you provide a search field name and an operator, it displays all matching values: This makes it easy to browse for values of interest without knowing ahead of time what they might be. The maximum number of transactions a search can specify is 200,000 (increased from 100,000). Users can control the number of transactions in each page of the results table with the new Show drop-down setting above the results table. Previously, each page showed 10 transactions. Release Notes-1-8 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

9 1 Release Overview Users can add, remove, or rearrange columns in the results table by clicking the Customize Columns button above the results table. The Refine Results panel now includes Transaction Type as a criterion to limit the current search results. In the Details pane of the Transaction Search screen, the labels that launch the desktop console have changed: The Details pane now displays long URLs with better formatting. Other Changes Performance enhancements: Indexing transactions so they are available for searching in Transaction Trace Warehouse and the searches themselves are now faster. Improved detection of related cross-tier transactions ( stitching ). Logs for the Transaction Trace Warehouse silo processes by default now create new log files whenever a file exceeds 10 MB. The new max_log_size_mb setting in the silo.cfg file specifies this size. This is in addition to the existing behavior of creating new log files whenever a file is older than 7 days by default (specified by the existing log_rotate_interval setting). Also, the file names no longer include dates. Transaction traces now record the user name for the process that initiated the transactions. This allows searches in the Transaction Trace Warehouse to match the user name for.net "fat client" applications that do not have transaction-level user names. For such applicatiions, the Transaction Trace Warehouse displays this user value in the User column of the results table and in the Refine Results panel. Previously, such searches would not match on the process user name and the user interface showed 'n/a' as the User value. Re-indexing transactions: The executable for re-indexing transactions is in a different directory and its name depends on the version of Windows: For Windows Server 2008 (64 bit): <installdir>\bin\64\silo_store64.exe For Windows Server 2003 (64 bit): <installdir>\bin\64\silo_store_legacy_os64.exe For Windows Server 2008 (32 bit): <installdir>\bin\32\silo_store32.exe For Windows Server 2003 (32 bit): <installdir>\bin\32\silo_store_legacy_os32.exe OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 Release Notes-1-9

10 1 Release Overview Deprecated Features In the Transaction Trace Warehouse, administrators can create custom "transaction types" that match the transactiontype search field and that appear in the Transaction Type column of the search screen Results Table. As described in the Transaction Trace Warehouse online help, rules in the mapping_rules.cfg configuration file specify URL patterns as simple wildcard strings (the wildcard keyword) or regular expressions (the regex keyword). Support for regular expressions and the regex keyword is deprecated and will be removed in a future release. Rules that specify regex should be rewritten to use simple wildcard strings. Note that you can effectively supply multiple wildcard strings for a single transaction type by creating multiple rules with the same name. The Transaction Trace Warehouse uses the first pattern that matches the URL. For example: { "name" : "Server Pages", "wildcard" : "*.jsp" }, { "name" : "Server Pages", "wildcard" : "*.asp*" }, Upgrading from Earlier Versions The following sections describe specific upgrade considerations for different Transaction Trace Warehouse versions. Note Before upgrading, if the Windows Services utility is open, close it. If it is open, the installer may not be able to delete and create services. Upgrading to Version 2.1 Add TTWAdmin User Role After Upgrading From Earlier 2.1 Advanced Technology Release This note applies only to specific builds of the initial Transaction Trace Warehouse Version 2.1 Advanced Technology release. Identify installations that this note applies to as follows: Installer build 1035: The file name of the component installer executable used to install Transaction Trace Warehouse is AppInternals_Xpert_BrowserMetrix_TTW_Installer_v8.5_build_1035.exe Transaction Trace Warehouse build 1812: The version number shown at the bottom of screens in the Transaction Trace Warehouse Web user interface is Version: 2.1 Build Release Notes-1-10 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

11 1 Release Overview If you have installed this build of Transaction Trace Warehouse, you must manually add a new role, TTWAdmin, using the OPNET Authentication Service Web user interface. This role was added after build 1812 and is required for users to access the Configure screen in the Transaction Trace Warehouse user interface. (Installing later builds creates the role automatically.) After upgrading, follow these steps to add the role and assign it to user accounts that you want to administer Transaction Trace Warehouse. 1) Open the OPNET Authentication Service Web user interface. Log in to Transaction Trace Warehouse as the admin user (or any user that has the RootAdmin role) and click the Account link at the upper right. 2) The OPNET Authentication Service screen opens in a separate browser tab or window. Click the Roles tab and the Role Management subtab. Click the Add Role... button. 3) In the Add New Role dialog box, specify TTWAdmin in the Role Name field and click Save. 4) Click the Role Assignment subtab. Assign the new TTWAdmin role to users you want by selecting the user identifier and the TTWAdmin role (in the Available Roles area), clicking the > button, and clicking Save. Migration to User Roles From Earlier Versions Version 2.1 of Transaction Trace Warehouse recognizes the following user account roles managed by OPNET Authentication Service: Role RootAdmin TTWAdmin TTWAccess Authority Not directly used by Transaction Trace Warehouse. Required to log into OPNET Authentication Service and create accounts and grant roles to accounts. Accounts with only the RootAdmin role cannot log in to Transaction Trace Warehouse. Log in, view data, and access the Configure screen in Transaction Trace Warehouse. Log in and view data in Transaction Trace Warehouse. Earlier releases did not use OPNET Authentication Service. Instead, users were assigned the Admin privilege and enabled within Transaction Trace Warehouse. Upgrading from earlier versions migrates users to OPNET Authentication Service and the new roles as follows: Enabled users with the Admin privilege are assigned the TTWAdmin role but not the RootAdmin role. Enabled users without the Admin privilege are assigned the TTWAccess role. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 Release Notes-1-11

12 1 Release Overview Disabled users are not assigned any role. The admin user (the default user created by the installation) is handled as a special case: It is always assigned the RootAdmin role. If it is enabled at the time of the upgrade, it is also assigned the TTWAdmin role. If it is disabled at the time of the upgrade, it is not assigned the TTWAdmin role but is changed to Active in OPNET Authentication Service. This handling of the admin user insures that at least one Transaction Trace Warehouse user will be able to access OPNET Authentication Service and assign the TTWAdmin role to itself and the RootAdmin role to other users. In cases where the Transaction Trace Warehouse admin user was disabled at the time of the upgrade, be sure log in as admin, open OPNET Authentication Service (click the Account link at the upper right of the Transaction Trace Warehouse user interface), and assign the TTWAdmin role to admin or the RootAdmin role to at least one other user. Migrating to OPNET Authentication Service The new OPNET Authentication Service replaces the OPNET AAM server used by earlier versions of Transaction Trace Warehouse. OPNET Authentication Service is a shareable component for OPNET products that enables single sign-on and integration with LDAP/AD authentication servers. You must migrate to OPNET Authentication Service when you install Transaction Trace Warehouse Version 2.1. Depending on whether other OPNET products (such as OPNET Dashboards Version 1.0) that also use AAM are also installed, this migration may require manual steps. See Considerations for Migrating to OPNET Authentication Service for more details. The simplest case for upgrading is when there is an earlier version of Transaction Trace Warehouse installed and there are no other products (such as OPNET Dashboards Version 1.0) that also use AAM. You can use the component installer to install the Authentication Service on the same system and also upgrade Transaction Trace Warehouse. Release Notes-1-12 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

13 1 Release Overview During the installation of the Authentication Service, the installer asks if there are AAM users to migrate and the directory with the AAM files to migrate. Supply the location of the aam.war directory (<installdir>\jboss\server\op_webapps\deploy\aam.war) and the installer will migrate existing AAM users to the Authentication Service: Upgrading to Version 2.0: Upgrades Must Not Override Existing Installation Directory Related Software Problem Reports (available at The Transaction Trace Warehouse installer allows you to change the installation directory. When upgrading an existing Version 1.0 or installation to Version 2.0, the installer detects the current installation location but still allows users to change it. If you change the installation directory when upgrading, the upgrade completes, but then users cannot log in to the Transaction Trace Warehouse user interface. If this occurs, you must remove both installations and install Transaction Trace Warehouse again. System Requirements For this reason, do not override the installation directory when you upgrade from Version 1.0 or to Version 2.0. See the System Requirements link on the AppInternals Xpert support page for the latest Transaction Trace Warehouse system requirements. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 Release Notes-1-13

14 1 Release Overview Note the following errors in the Transaction Trace Warehouse installation documentation regarding system requirements: The Transaction Trace Warehouse is only supported on 64-bit Windows platforms. 32-bit Windows systems are not supported. Transaction Trace Warehouse Web user interface does not support Microsoft Internet Explorer Version 7. Release Notes-1-14 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

15 Considerations for Migrating to OPNET Authentication Service The OPNET Authentication Service replaces the OPNET AAM server used by earlier versions of OPNET products, such as OPNET Dashboards Version 1.0 or Transaction Trace Warehouse Version 1.0 or 2.0. If you are upgrading either OPNET Dashboards or Transaction Trace Warehouse, those upgrades must also migrate from AAM to OPNET Authentication Service. Depending on which products are present, this may require assistance from OPNET technical support. Earlier Versions of Dashboards and Other OPNET Products If earlier versions of multiple products are installed, always upgrade OPNET Dashboards first. The Dashboards upgrade performs internal migration to Authentication Service that must occur before any other upgrade. Use the component installer to install the Authentication Service and upgrade Dashboards on the same system. The installer prompts for the location of AAM files and migrates them to the Authentication Service. This upgrade and migration does not require manual steps or assistance from OPNET technical support. The migration for the other products requires manual steps. Contact OPNET technical support for assistance. Earlier Version of Transaction Trace Warehouse Only If an earlier version of Transaction Trace Warehouse is installed, use the component installer to install the Authentication Service on the same system and upgrade Transaction Trace Warehouse. The installer prompts for the location of AAM files and migrates them from Authentication Service. This upgrade and migration does not require manual steps or assistance from OPNET technical support. Migrating AAM to an Authentication Service on Another System Products can specify an OPNET Authentication Service installed on a remote system. In this case, migration for earlier versions of products requires manual steps. Contact OPNET technical support for assistance. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.0 Release Notes-1-15

16 Release Notes-1-16 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.0

17 2 Known Problems and Problems Fixed 2 Known Problems and Problems Fixed Known Problems This section describes known problems and problems fixed for the Transaction Trace Warehouse. Close Windows Services Utility Before Installation Related Software Problem Reports (available at , The Transaction Trace Warehouse installer can encounter problems if the Windows Services utility is open when you install, upgrade, or delete an installation. If it is open, the installer may not be able to create or delete the two services (OPNET AppInternals Xpert Transaction Trace Warehouse <version> and OPNET AppInternals Xpert Transaction Trace Warehouse backend processes). For a new installation, the installer will complete but one or both of the required Windows services may not be created. For upgrades, one or both of the services may be marked for deletion and unusable. For deleted installations, one or both of the services may be marked for deletion but remain. To avoid these problems, be sure to close the Windows Services utility before running the installer. To recover from new and upgraded installations with missing or unusable services: 1) Reboot the system. 2) Delete the installation (from the Windows Start menu, run OPNET > AppInternals Xpert Transaction Trace Warehouse > Uninstall AppInternals Xpert Transaction Trace Warehouse). 3) Run the installer again. For deleted installations that leave services behind, reboot the system to remove them. Secure Communications Require that All SMPs Use the Same Trusted Certificate Related Software Problem Reports (available at OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 Release Notes-2-1

18 2 Known Problems and Problems Fixed As described in the Transaction Trace Warehouse configuration documentation, you can configure the Transaction Trace Warehouse with key and certificate files so that it can identify itself to a comparably-configured SMP and its DSAs. Problems Fixed in Version 2.0 Because of a problem, you cannot configure the Transaction Trace Warehouse to connect to multiple SMPs and their DSAs if they use different keys and certificates. Searches Could Cause Excessive Memory Consumption Related Software Problem Reports (available at Original Problem: In some cases, using the autocomplete feature in the Search screen consumed memory excessively. Specifically, the silo_query64 process consumed several gigabytes of memory. Resolution: This problem has been fixed. Potential JBoss Port Conflicts on Windows 2003 Systems Related Software Problem Reports (available at Original Problem: The Transaction Trace Warehouse uses the JBoss application server to host its Web user interface. Some ports required by JBoss fall into the default range of ephemeral ports defined on Windows 2003 systems. When another process was already allocated an ephemeral port that is also required by JBoss, the Transaction Trace Warehouse did not start. This problem could prevent the SMP and Transaction Trace Warehouse from running on the same Windows 2003 system, especially when the Transaction Trace Warehouse was installed after the SMP, and the SMP had been running for a long time Resolution: This problem has been fixed. The Transaction Trace Warehouse installation on Windows 2003 systems checks whether ports it requires are in use and assigns other ports if necessary. Release Notes-2-2 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

19 3 Linking Between Source Code and AppInternals Xpert Data 3 Linking Between Source Code and AppInternals Xpert Data In AppInternals Xpert consoles you can click on a transaction trace or metric to open the line of source code that defines the generic class.method that generated that transaction or metric when applicable. The capability, called LinkToSource, can link from: Transaction Trace Warehouse, at least Version 2.1 (to Windows IDEs only) Transaction Trace Analyzer, at least Version 4.0 (to Windows IDEs only) Likewise, in Visual Studio and Eclipse code, you can click on the name of a generic method or click inside the code for the method and link to traces on transactions that the.net or Java code generated, and display those transactions in Transaction Trace Warehouse. This capability is called LinkToTxn. (If the method did not generate any transactions, LinkToTxn does not find any.) In addition, you can click on the name of a generic method or click inside the code for the method and link to AppInternals Xpert metrics that the method generated, displaying in the Desktop Console. This capability is called LinkToMetric. (If the method did not generate any metrics, LinkToMetric does not find any.) These LinkToTxn and LinkToMetric capabilities can link from: Visual Studio Eclipse (from both Windows and UNIX IDEs) LinkToTxn and LinkToMetric can help you analyze your code by letting you go back and forth between the source code and the AppInternals Xpert performance data to examine selected class/method transactions that: Exceed a particular duration Generate an exception when executed The illustration in Figure 3-1 shows all ways that you can link between source code and AppInternals Xpert data. The red lines show the LinkTo options. Note You must place the cursor in either the name or body of the method before you right-click. TTW-Admin-3-1 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

20 3 Linking Between Source Code and AppInternals Xpert Data Figure 3-1 Ways You Can Link Between Source Code and AppInternals Xpert Data Metrics Servers/Systems Running AppInternals Xpert Components SMP Metrics Transaction Trace Warehouse Managed Nodes Traces Monitoring.NET or Java applications with dotnet JIDA Data Adapters Txn Traces LinkToSource LinkToTxn Transaction Trace Analyzer Desktop Console Developer Workstation Running AppInternals Xpert Components & Visual Studio or Eclipse LinkToSource LinkToMetric Cursor must be in either the name or body of the method Configuring dotnet and JIDA Data Adapters for LinkTo Capability For LinkToTxn to find the traces generated by a method in a particular section of your.net code in Visual Studio or of your Java code in Eclipse, the method where you placed the cursor must: Be a generic method Have class.method metrics explicitly enabled in the dotnet.config file of the dotnet data adapter using collect_generic commands Have class.method metrics explicitly enabled in the jida.config file of the JIDA data adapter using collect_generic commands OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-2

21 3 Linking Between Source Code and AppInternals Xpert Data If these conditions have not been met, LinkToTxn opens Transaction Trace Warehouse, but finds no transaction traces for the method. For information on configuring collection of traces and metrics from.net code, see the AppInternals Xpert Configuration Guide chapter on Configuring the dotnet Data Adapter. For information on configuring collection of traces and metrics from Java, see the chapter on Configuring JIDA. Compatible Development Environments The LinkToTxn and LinkToMetric capabilities of AppInternals Xpert are available as an add-in for multiple versions of Visual Studio and as a plug-in for Eclipse. Visual Studio with.net Framework The Visual Studio add-in is compatible with versions 2005, 2008, 2010, and 2012 and works with code programmed in any.net languages. On any machine where you will be running Visual Studio and interacting with any AppInternals Xpert consoles, you must: Download and install Transaction Trace Analyzer. The Transaction Trace Analyzer installer also installs a required Visual Studio navigation utility. To download this tool, refer to: Downloading and Installing Transaction Trace Analyzer from Web Site Download the Visual Studio add-in from the web site and install the add-in yourself. To download and install the Visual Studio add-in, refer to: Downloading Add-Ins and Plug-Ins for IDEs from Web Site Installing the Visual Studio Add-In Note If you are working in a Visual Studio Team Foundation Server environment, you need to map the team project before you attempt to link between AppInternals Xpert consoles and Visual Studio projects. You then open your projects or solutions in the copy of the Team Explorer that mapping generates. Eclipse with Java Features The Eclipse plug-in is compatible with supported brands of Eclipse, Helios (3.6) and greater, works with Java code only, and requires Java features or a Java Enterprise Environment (EE). TTW-Admin-3-3 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

22 3 Linking Between Source Code and AppInternals Xpert Data The plug-in runs on all operating systems supporting Eclipse, including all types of Windows and UNIX that AppInternals Xpert supports. On any machine where you will be running Eclipse and interacting with any AppInternals Xpert consoles, you must Download and install Transaction Trace Analyzer. The Transaction Trace Analyzer installer also installs a required Eclipse navigation utility. To download this tool, refer to: Downloading and Installing Transaction Trace Analyzer from Web Site Download this plug-in from the web site and install the plug-in yourself. To download and install the Eclipse plug-in, refer to: Downloading Add-Ins and Plug-Ins for IDEs from Web Site Installing the Eclipse Plug-In How Does Linking to Traces and Metrics Work? Once you install the add-in to Visual Studio or the plug-in to Eclipse, you can use LinkToTxn and LinkToMetric capabilities. When you right-click on a line of code, the add-in or plug-in takes the class and method from the code and puts it into a URL to send to the Transaction Trace Warehouse. So that the utility knows where to find the traces, it pops up a dialog box where you indicate the Transaction Trace Warehouse host name and the start and end times of the particular period in time. (You can also supply other optional parameters to the utility, including a particular managed node name to restrict the results to data from that node.) The utility combines the parameters to form a query and execute it in Transaction Trace Warehouse. You can then examine the traces that the line of code generated. How Does Linking to Source Code Work? How does LinkToSource work? To use LinkToSource capabilities, you install Transaction Trace Analyzer on the Visual Studio or Eclipse development machine. Installing Transaction Trace Analyzer also installs special Visual Studio and Eclipse navigation utilities that both Transaction Trace Analyzer and Transaction Trace Warehouse use to link to the source code. Each utility knows the particular development environment to search for the source of the trace or metric. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-4

23 3 Linking Between Source Code and AppInternals Xpert Data The utility turns on the LinkToSource capability that links from either Transaction Trace Analyzer or Transaction Trace Warehouse to Visual Studio or Windows-based Eclipse. How the Navigation Utility Searches Visual Studio Code If, for instance, you are linking to the source code in Visual Studio from a trace, the utility first searches the currently open project or solution for the definition of the class and method in the trace. The utility searches the hierarchy in this order: the workspace first, the project second, and the file last. If the utility cannot find the class and method definition in the open project or solution (or if you do not have one currently open), it opens and searches each of the most recently used projects/solutions one-by-one. When it opens a new project or solution, it prompts you on whether to continue or cancel the search. Finally, if the utility cannot find the class and method, it presents a dialog where you can enter the path to a solution or cancel. How the Navigation Utility Searches Eclipse Code If, for instance, you are linking to the source code in Eclipse from a trace, the utility searches the currently open code for the definition of the class and method in the trace. If the utility cannot find the class and method definition in the open program, it queries you for the path to a workspace and gives you the option to cancel. It searches the workspace you enter and continues to query you for the next workspace until you cancel. TTW-Admin-3-5 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

24 Configuring LinkToTxn and LinkToMetric 3 Linking Between Source Code and AppInternals Xpert Data You take the steps that follow to prepare to use LinkToTxn and LinkToMetric: Table 3-1 Software Installation Requirements for LinkToTxn and LinkToMetric From: Visual Studio Eclipse To: (Windows) (Windows) (Linux) Transaction Trace Warehouse Visual Studio add-in Eclipse plug-in Eclipse plug-in Desktop Console Visual Studio add-in Eclipse plug-in Eclipse plug-in Downloading Add-Ins and Plug-Ins for IDEs from Web Site The Visual Studio add-in and/or Eclipse plug-in that you require to link from Visual Studio and/or Eclipse to Transaction Trace Warehouse with LinkToTxn is available on the OPNET web site. To download the add-in and/or plug-in: Procedure On the machine where you have Visual Studio and/or Eclipse installed, click on the link below to open the support page of the web site: 2 At the top of the page under Latest Product Updates, click Advanced Technology Release: AppInternals Xpert When the AppInternals Xpert Version 8.5 Advanced Technology Release page appears, scroll down, look below Download, and find Development Environment Integration. You see links for an Eclipse plug-in and several Visual Studio add-ins (for different versions). Click the appropriate link and download the file. You must fill in the data for your user profile and certify the information is correct. 4 Once you have downloaded the file, copy it into a temp directory, and unzip it. 5 On Windows: Proceed with Installing the Visual Studio Add-In or Installing the Eclipse Plug-In. 6 On UNIX: Copy the Eclipse plug-in (com.opnet.ideintegration.eclipse.gts_1.0.0.jar) to the /bin directory under the <EclipseInstall> directory. End of Procedure 3-1 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-6

25 3 Linking Between Source Code and AppInternals Xpert Data Installing the Visual Studio Add-In The add-in files for integration between Visual Studio and AppInternals Xpert consoles are zipped into a single file: ideintegration.zip, unzipped into several ideintegration<####>.msi files (add-in installers) (use the one whose number matches your version of Visual Studio) To install the Visual Studio add-in and confirm the installation of LinkToTxn: Procedure If you have not already done so, download the Visual Studio add-in installer files from the web site (see Downloading Add-Ins and Plug-Ins for IDEs from Web Site) to the computer that has Visual Studio installed. 2 Unzip the ideintegration.zip file in a temp directory. 3 In the temp directory, choose the MSI add-in installer file with a <####> that matches your version of Visual Studio either 2005, 2008, 2010, or 2012 and copy the file. 4 Copy the add-in installer to the Users\<yourUserAccount>\Documents\Visual Studio ####\Addins directory. If the directory does not exist, create it and place the files in it. 5 Run the add-in installer on the command line (this example installs Version 2010): msiexec /i ideintegration2010.msi 6 In the installer, click Next until the installation completes, then click Finish. ideintegration<####>ttw appears in the Windows Control Panel Programs and Features list. 7 To confirm that the add-in is enabled, run Visual Studio and select Tools > Add-in Manager from the menu bar. 8 When the Add-in Manager appears, find OPNET TTW Navigator under Available Add-ins and select Startup and/or Command Line, depending on how you want to start the navigator, then click OK. Having it run on startup of Visual Studio is convenient. 9 To find traces or metrics that a line of code generated, proceed to Linking from Source Code to Traces or Metrics. End of Procedure 3-2 TTW-Admin-3-7 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

26 Installing the Eclipse Plug-In 3 Linking Between Source Code and AppInternals Xpert Data Two files are involved in integration between Eclipse and AppInternals Xpert consoles: com.opnet.ideintegration.eclipse.plugins.gts_1.0.0.jar (Eclipse IDE plug-in) eclipsemgr.jar (navigation utility) To install the Eclipse plug-in and confirm the installation of LinkToTxn: Procedure If you have not already done so, download the Eclipse plug-in.jar file from the web site (see Downloading Add-Ins and Plug-Ins for IDEs from Web Site) to the computer that has Eclipse installed. 2 In both UNIX and Windows, copy com.opnet.ideintegration.eclipse.plugins.gts_1.0.0.jar to the plugins directory under the <EclipseInstall> directory. 3 To find traces that a line of code generated, proceed to Linking from Source Code to Traces or Metrics. End of Procedure 3-3 Confirming Installation of TTW to IDE Eclipse Utility To install the Eclipse utility and confirm the installation of LinkToSource for Eclipse: Procedure If you have not already done so, download and install Version 4.0 of Transaction Trace Analyzer (see Downloading and Installing Transaction Trace Analyzer from Web Site). 2 In UNIX: Confirm that the eclipsemgr.jar is installed in the /bin directory. 3 In Windows: If you plan to link to the source code from Transaction Trace Warehouse or Transaction Trace Analyzer, confirm that the eclipsemgr.jar file is installed in the 32-bit bin directory under Transaction Trace Analyzer: <installdir>\opnet\tta\16.5.p\sys\pc_intel_win32\bin 4 To find the line of source code that generated particular transactions, proceed to Configuring LinkToSource. End of Procedure 3-4 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-8

27 3 Linking Between Source Code and AppInternals Xpert Data Linking from Source Code to Traces or Metrics When you are developing code in Visual Studio or Eclipse, you can inspect how long it takes to execute a method or determine whether that method has generated exceptions when executed both ways to improve your application performance. You reveal this information by linking from the line of source code to AppInternals Xpert traces or metrics that the code generated. Linking to Traces (with LinkToTxn) To link from the source code to traces: Procedure Open a project in Visual Studio or Eclipse that has generated traces or metrics. 2 Optional. Run the AppInternals Xpert console you want to work in and log in. 3 Right-click on a line of code. When the context menu opens, find AppInternals Xpert in the menu and drag to the right to see these additional menu options: Find Transactions... Find Transactions (Quick) Find Metrics... Find Metrics (Quick) 4 If it is your first time using LinkToTxn in this session or you want to find transactions on a different Transaction Trace Warehouse host or generated on a different managed node, select Find Transactions... from the context menu. If you have been using LinkToTxn earlier in the session and want to find transactions on the same Transaction Trace Warehouse host or generated on the same managed node, select Find Transaction (Quick) instead. TTW-Admin-3-9 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

28 3 Linking Between Source Code and AppInternals Xpert Data Figure 3-2 Additional Context Menu Options for Linking to Traces or Metrics AppIntermals Xpert menu options OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-10

29 3 Linking Between Source Code and AppInternals Xpert Data 5 The Configure Transaction Queries dialog box appears (see next figure), where you indicate the particular transactions to find by filling in the information. Figure 3-3 Configure Transaction Queries Dialog Box in Visual Studio If the server is running on an alternative port, enter the port number after its host name; for example: ttwhost:8808 Click here to change the units for the minimum transaction duration. 5.1 Transaction Trace Warehouse Host Name:port Enter the host name of the server where Transaction Trace Warehouse is installed. Required. You can also, optionally, add a colon followed by the port number if the product is using a non-standard port. Note If the Transaction Trace Warehouse server is running on an alternative port (any port other than the standard one), you must enter the port after the host name, with a colon between them: <hostname>:<port> 5.2 Start and End time Indicate date/time when the traces were generated. Required. 5.3 Under Optional parameters, you can set the Managed node name and the Minimum transaction duration. Click the drop-down menu to set the units for the duration to sec, ms, µs, or ns. 5.4 To restrict traces you are examining to those for transactions that generated exceptions, turn on the Only include transactions with exceptions checkbox. 5.5 To display the traces in their own tab inside the Visual Studio or Eclipse browser, turn on the Display results in Eclipse (or Visual Studio) browser checkbox. The login page appears first if you are not already logged in to Transaction Trace Warehouse or Transaction Trace Analyzer. You can resize the window for better visibility. 6 Click OK to see the LinkToTxn open the Transaction Trace Warehouse console and display the traces. Traces that the line of code generated appear highlighted in the list. TTW-Admin-3-11 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

30 3 Linking Between Source Code and AppInternals Xpert Data 7 If you have not logged in to the console for the session, its login window appears. Once you log in, you see the data. Figure 3-4 Transaction Trace Warehouse Login Page in Eclipse When you display Transaction Trace Warehouse in the Eclipse browser, you can easily move back and forth between the code and the transaction traces. Once you have logged in to Transaction Trace Warehouse, when you select the next line of code in Eclipse, you see the traces in Transaction Trace Warehouse immediately without having to log in again. 8 The next time you click on a line of code, you do not have to log in again. And if you are searching the same source, you can select Find Transactions (Quick) from the menu bar to skip the Configure Transaction Queries dialog box, and Transaction Trace Warehouse adheres to the prior settings. LinkToTxn forms a query, opens Transaction Trace Warehouse, and uses the query to find the class.method of the section of code where you placed your cursor. Because the query searches only for class.method, it does not find the method independent of the class. 9 Once LinkToTxn opens Transaction Trace Warehouse, however, you can modify the query for instance, you could remove the method, then search only on the class. This approach finds more transactions, because you can now find transactions from generic methods in that class that dotnet or JIDA data adapters collect automatically, in addition to those explicitly enabled in the dotnet.config or jida.config file. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-12

31 3 Linking Between Source Code and AppInternals Xpert Data Figure 3-5 Transaction Trace Warehouse Displaying Traces That the Source Code Generated End of Procedure 3-5 Linking to Metrics (with LinkToMetric) To link from the source code to metrics it generated: Procedure To find metrics, select Find Metrics from the context menu. 2 When the Configure Desktop Console Metric Queries dialog box appears (see next figure), you indicate the particular metrics to find by providing required information: TTW-Admin-3-13 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

32 3 Linking Between Source Code and AppInternals Xpert Data Figure 3-6 Configure Metric Queries (for Desktop Console) Dialog Box in Visual Studio These settings restrict the metrics found to those generated by Java on the devsystemjones host. 2.1 SMP Host Name Enter the host name of the SMP associated with the managed node monitoring the system. Required. 2.2 Start and End time Indicate range of date/time when the metrics were generated. Required. 2.3 Under Optional parameters, you can set the Application Host Name and the Component Name or leave them set to asterisk for one or both of these values. 3 Click OK to see LinkToMetric automatically both download and open the Desktop Console, then display the metrics in the Objects and Metrics table. The metrics found are highlighted in the console. 4 If you have not logged in to the console for the session, its login window appears. Once you log in, you see the metrics. End of Procedure 3-6 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-14

33 3 Linking Between Source Code and AppInternals Xpert Data Configuring LinkToSource When you have been viewing data on a generic method in any OPNET console, you can inspect the code by linking from the trace or metric to the line of source code that generated that trace or metric. On the machine running Visual Studio or Eclipse where you will be linking from Transaction Trace Warehouse or Transaction Trace Analyzer to the Visual Studio or Eclipse IDE, you must install Transaction Trace Analyzer to install navigation utilities that both OPNET products use to link to the source code. Each utility knows the particular development environment to search for the source of the trace or metric. If you do not already have Transaction Trace Analyzer, you can download it from the OPNET web site and install it as explained under Downloading and Installing Transaction Trace Analyzer from Web Site Once you have installed the utilities by installing Transaction Trace Analyzer, you do not need to take any extra configuration steps for Transaction Trace Analyzer to work with LinkToSource; however, you must take a few steps to configure Transaction Trace Warehouse to work with LinkToSource (see Configuring Transaction Trace Warehouse to Link to Source). Table 3-2 Software Installation and Property Setting Requirements for LinkToSource From: Transaction Trace Warehouse or Analyzer (Windows) To: Visual Studio Eclipse (Windows) Eclipse (Linux) Property set to True Utility from TTA Property set to True Utility from TTA Eclipse plug-in Property set to True Eclipse plug-in TTW-Admin-3-15 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

34 3 Linking Between Source Code and AppInternals Xpert Data Downloading and Installing Transaction Trace Analyzer from Web Site You must install Transaction Trace Analyzer to install navigation utilities that both Transaction Trace Analyzer and Transaction Trace Warehouse use to link to the source code. Transaction Trace Analyzer is available on the OPNET web site. To download the tool: Procedure On the machine where you have Visual Studio and/or Eclipse installed, click on the link below to open the support page of the web site: 2 At the top of the page under Latest Product Updates, click Advanced Technology Release: AppInternals Xpert When the AppInternals Xpert Version 8.5 Advanced Technology Release page appears, scroll down, look below Download, and find Transaction Trace Analyzer Build Click the Windows button and follow the instructions to download the.exe file. You must fill in the data for your user profile and certify the information is correct. 4 Once you have downloaded the file, double-click the.exe file to install the tool. End of Procedure 3-7 Confirming Installation of TTW to IDE Visual Studio Utility The utility files for integration between Visual Studio and AppInternals Xpert consoles were downloaded when you installed TTA: vsmanager.exe (navigation utility executable) vsmanager.exe.config (utility that identifies version of.net CLR runtime) To install the utilities and confirm the installation of LinkToSource: Procedure If you have not already done so, download and install Version 4.0 of Transaction Trace Analyzer (see Downloading and Installing Transaction Trace Analyzer from Web Site). 2 Confirm that the vsmanager.exe and vsmanager.exe.config files are installed in the 32-bit bin directory under Transaction Trace Analyzer: <installdir>\opnet\tta\16.5.p\sys\pc_intel_win32\bin OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-16

35 3 Linking Between Source Code and AppInternals Xpert Data 3 To find the line of source code that generated particular traces or metrics, proceed to Configuring LinkToSource. End of Procedure 3-8 Confirming Installation of TTW to IDE Eclipse Utility To install the Eclipse utility and confirm the installation of LinkToSource for Eclipse: Procedure If you have not already done so, download and install Version 4.0 of Transaction Trace Analyzer (see Downloading and Installing Transaction Trace Analyzer from Web Site). 2 For UNIX-based Eclipse: Confirm that the eclipsemgr.jar is installed in the /bin directory. 3 For Windows-based Eclipse: Confirm that the eclipsemgr.jar file is installed in the 32-bit bin directory under Transaction Trace Analyzer: <installdir>\opnet\tta\16.5.p\sys\pc_intel_win32\bin 4 To find the line of source code that generated particular transactions, proceed to Configuring LinkToSource. End of Procedure 3-9 Configuring Transaction Trace Warehouse to Link to Source You must configure Transaction Trace Warehouse to work with LinkToSource to turn on the display of the IDE Integration button (to appear in the Transaction Details under the Top Calls tab for a particular transaction). Procedure Turn on display of the IDE Integration button (to appear in the Transaction Details for a particular trace: 2 Find the harvester.properties file at the following path: C:\OPNET\JBoss\5.1.0\server\harvester\deploy\harvester\harvester.ear\ 3 Open the file and set the following property to true: show_ide_launch_button=true 4 Save and close the file. TTW-Admin-3-17 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

36 5 Refresh the browser view (press F5). End of Procedure Linking Between Source Code and AppInternals Xpert Data Linking from Transaction to Source Code Before you can Link to a transaction trace or metric to source code, you should first be sure you have configured the software as required. See Configuring LinkToSource for details. Linking from Transaction Trace Warehouse to Source Code (with LinkToSource) To see the IDE Integration button: Procedure Open the Transaction Details for a trace and click the Top Calls tab. 2 Look for the button to the left of the name in the Class column with a down arrow in it. When you hover over the button, it indicates that the button opens the source code in Eclipse or Visual Studio, as shown in Figure 3-7. Figure 3-7 IDE Integration Button in Transaction Details of Transaction Trace Warehouse 3 If you see the Opening launch.ttw2ide dialog box, click Browse and select either Visual Studio or Eclipse from the list of programs. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-18

37 3 Linking Between Source Code and AppInternals Xpert Data Figure 3-8 Opening launch.ttw2ide Dialog 4 When the IDE opens, you should see the cursor land on the line of code containing the definition of the method from the transaction whose Open Source button you clicked. 5 To prevent the Opening launch.ttw2ide dialog from interfering with the smooth transition between Transaction Trace Warehouse and the IDE, click the check box labeled Do this automatically for files like this from now on. In the future, the browser will open the IDE automatically. End of Procedure 3-11 Linking from Transaction Trace Analyzer to Source Code (with LinkToSource) To link from a trace to the source code that generated it: Procedure Run the AppInternals Xpert console you want to work in and log in. That console can be Transaction Trace Warehouse, Transaction Trace Analyzer, or the Desktop Console. 2 If you are looking for the source in Visual Studio code managed by a Microsoft Team Foundation Server, skip to step 4. 3 Although you are not required to have Visual Studio already running or have a solution open, if you would like, you can run Visual Studio before proceeding and open the code you believe contains the source. 4 If you are using Visual Studio with code managed by a Microsoft Team Foundation Server, check out the code to your local workstation. TTW-Admin-3-19 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

38 3 Linking Between Source Code and AppInternals Xpert Data Note AppInternals Xpert consoles do not search for source code in files on the Microsoft Team Foundation Server. 5 If you are looking for the source in an Eclipse project (in Windows), first run Eclipse and open any workspaces containing possible source projects, then open all projects that could possibly contain the source. The AppInternals Xpert console does not find Eclipse source code in closed projects, even if the project s workspace is open. Note If you close an Eclipse project after you have found source code in it, AppInternals Xpert consoles no longer look in that project for source code and do not open the project to search it. 6 In the AppInternals Xpert console, right-click on a the trace or metric whose source code you want to see and select Open Source in Visual Studio (or Eclipse) from the drop-down menu. Figure 3-9 shows using this menu in Transaction Trace Analyzer to open the Visual Studio solution containing the source code. Notice that after it opens the solution, LinkToSource automatically highlights the line of code defining the method. Figure 3-9 From Transaction Trace Analyzer, Opening Source in Visual Studio Visual Studio If Visual Studio is not running or is running but has no solution open, LinkToSource prompts you to browse to a particular solution and press OK, then searches that solution. If Visual Studio is running with an open solution, LinkToSource searches the currently open project/solution first. OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-20

39 3 Linking Between Source Code and AppInternals Xpert Data If LinkToSource cannot find the source containing the class/method from the trace or metric in the open solution, it then prompts you to select another project or solution (see the next figure) to search or to press cancel. It continues to prompt you for another solution or project until it finds the source code or you press Cancel to exit. If you have used LinkToSource before, and Visual Studio is not running or is running but has no solution open, the Please Select a Solution dialog box initially shows the path to the last solution you searched, unless you are using Visual Studio on a Microsoft Team Foundation Server and have not copied the code to your local system see the note below for details. Note If you are using Visual Studio on code managed by a Microsoft Team Foundation Server and have not checked out the code to your local workstation, LinkToSource does not find the solution automatically. If the trace is from a get_xxx or set_xxx method, like the get_city and set_city methods shown below, LinkToSource finds the source of those methods, just as it would any other method: public string City { get { return _city; } set { _city = value; } } Figure 3-10 Dialog Box Prompting for Visual Studio Solution Enter full path to Visual Studio solution or project file Eclipse If Eclipse is not running, LinkToSource prompts you to browse to a particular workspace containing the code you want it to search. LinkToSource then opens the code and searches it. If LinkToSource cannot find the source code in that program, it prompts you to enter the path to another workspace or cancel. It continues to prompt you for another workspace until either it finds the source code or you press Cancel to exit. TTW-Admin-3-21 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1

40 3 Linking Between Source Code and AppInternals Xpert Data If you have used LinkToSource before, and Eclipse is not running or is running but has no workspace open, the Please Select a Workspace dialog box initially shows the path to the last workspace you searched, unless the source code is on a server (see the note below). Figure 3-11 Dialog Box Prompting for Project Workspace and Eclipse Executable Enter path to the workspace for your project Enter full path to Eclipse executable file If you provide only the location of the Eclipse executable, Eclipse then prompts you for the workspace. If you provide only the workspace location, a popup reminds you that the path to the Eclipse executable is required. End of Procedure 3-12 OPNET AppInternals Xpert/Transaction Trace Warehouse/Version 2.1 TTW-Admin-3-22