IBM Application Delivery Intelligence 5.0.2 6Product overview 7Overview of IBM Application Delivery Intelligence 8Key benefits of using ADI 9What's new in ADI 5.0.2 11Terminology overview 13Tutorials 15Installing and setting up ADI 16Installing ADI and configuring JTS to be the foundation of ADI 17Setting up a project area to start applications to be analyzed 23Setting up Manual Builds for Code Coverage Analysis 30Defining a new application as an analysis collection 31Adding the code coverage files to the first build 36Viewing the code coverage analysis results of the first build 38Defining a new build and planning the next test cycle using Minimal Test to Run 40Adding new code coverage results to an existing build 44Setting up automated code coverage data collections 47Adding a Manual Builds data provider to collect code coverage data automatically 48Creating an analysis collection for a new application and setting up code coverage results forautomated data collection 52Exercising setting up a Manual Builds for code coverage analysis 56Setting up a Manual Builds data provider 57Setting up an analysis collection 61Analyzing code coverage 63Reviewing code coverage reports and dashboards 64Generating sample data 72End-to-end system performance root cause analysis 77Installation and setup 86Hardware and software requirements 87Security considerations 89Installing ADI by using web-based express setup 91Information required before the installation 92Starting up the server 93Configuring the server 94Setting up the ADI application 99Shutting down the server 100Installing ADI by using web-based custom setup 101Information required before the installation 102Creating databases 103Starting up the server 105Configuring the server 106Setting up ADI application 113Shutting down the server 114Installing ADI by using the repotools command 115Starting up the server 116Running the response file 117Setting up ADI application 118

Shutting down the server 120Installing ADI into an existing CLM installation 121Before you begin 122Procedures 123What to do next 127Migrating from a previous release 128Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1 ifix01 129Installing the new release into a new directory 130Backing up database files 131Copying key configuration and data files from the old to the new installation 133Migrating the JTS data 134Migrating the ADI application data 135Starting the server and waiting for additional migration to finish 136Migrating from ADI 1.0.1 to ADI 1.0.1 ifix01 137Installing the new release into a new directory 138Backing up database files 139Copying key configuration and data files from the old to the new installation 141Starting the server and waiting for additional migration to finish 143Migrating from ADI 1.0.1 or ADI 1.0.1 ifix01 to ADI 1.0.2 144Installing the new release into a new directory 145Backing up database files 146Copying key configuration and data files from the old to the new installation 148Starting the server and waiting for additional migration to finish 150Migrating from ADI 1.0.2 to ADI 5.0.2 151Installing the new release into a new directory 152Backing up database files 153Copying key configuration and data files from the old to the new installation 155Starting the server and waiting for additional migration to finish 157Importing the new license keys 158Setting role-permissions for project area members 159Administration 160Logging in to administer the server 161Administration tasks for user management 162Managing client access licenses 163Creating and managing users 164Creating and managing user accounts 165Creating and managing project areas 166Assigning role-based permissions to ADI users 168Users changing their password 170Backing up your data 171Server configuration settings 172Settings that determine the behavior of startup scripts 173Server settings that need to be defined in teamserver.properties before the server starts 175Server settings that can be defined at runtime in the /adi/admin user interface 178Generating sample data for evaluation 183Generating OMEGAMON for CICS data 184Generating Application Discovery data 185

Preparing external data sources 186Preparing code coverage results for COBOL and PL/I 187Preparing code coverage results for batch applications 188Generating code coverage results by using the IDz client 189Assumptions 190Procedures 191Generating code coverage results by using the headless collector running on ADI server 193Assumption 194Procedures 195Preparing code coverage results for CICS transactions by using the debug tool backend and IDzclient 196Assumptions 197Procedures 198Preparing code coverage results for COBOL and PL/I by using RTC 200Assumptions 201Procedures 202Preparing code coverage results for Java 208Preparing code coverage results by using the RAD 9.5 code coverage solutions 209Preparing code coverage results for Java by using the RAD client 210Assumptions 211Procedures 212Preparing code coverage results for Java by using RTC with RAD Quality Extensions 214Assumptions 215Procedures 216Preparing code coverage results by using the ADI code coverage generator 223Preparing code coverage results by using Apache Ant build scripts 224Assumptions 225Procedures 226Reference of properties in build.properties 228Next steps 231Preparing code coverage results by using Rational Team Concert Build and Apache Ant 232Assumptions 233Procedures 234Next steps 236Managing connections, data providers, and analysis collections 237Managing connections 238Adding connections 239Editing connections 240Deleting a connection 241Managing data providers 242Data providers 244Managing Manual Builds data providers 245Adding a Manual Builds data provider 246Adding a Manual Builds data provider to collect data manually 247Adding a Manual Builds data provider to collect data automatically 248Modifying the Manual Builds data providers 250Editing the Manual Builds data provider information 251

Adding a build to a Manual Builds data provider when collecting data manually 252Adding a build to a Manual Builds data provider when collecting data automatically 253Refreshing the code coverage results for automatically data collection 254Updating an existing build 255Deleting a build from the Manual Builds data provider 256Downloading the code coverage data associated with build 257Managing Rational Team Concert Builds data providers 259Adding a Rational Team Concert Builds data provider 260Modifying the Rational Team Concert Builds data provider 262Editing the Rational Team Concert Builds data provider information 263Refreshing the builds and code coverage data 264Viewing builds data of the Rational Team Concert Builds data provider 265Deleting a build from the Rational Team Concert data provider 266Downloading the code coverage data associated with build 267Managing OMEGAMON for CICS data providers 268Adding an OMEGAMON for CICS data provider 269Modifying the OMEGAMON for CICS data provider 271Editing the OMEGAMON for CICS data provider information 272Viewing OMEGAMON for CICS data collection logs 273Downloading the OMEGAMON for CICS data 274Managing Application Discovery data providers 275Adding an Application Discovery data provider 276Modifying the Application Discovery data provider 277Editing the Application Discovery data provider information 278Refreshing the data collected from Application Discovery server 279Viewing Application Discovery data collection logs 280Downloading the Application Discovery data 281Deleting a data provider 282Managing analysis collections 283Adding analysis collections 284Modifying analysis collections 286Deleting analysis collections 288Analyzing data 289Role-based dashboards and reports 290Analyzing and displaying code coverage results 293Code coverage reports and information 297Comparing the builds 306Filtering data in the Build Analysis view 307Filtering data in the File Analysis view 308Analyzing the Tests to Run 309Analyzing code coverage of FlowPoint level break-down 312Analyzing and displaying operational data from IBM OMEGAMON for CICS 313OMEGAMON for CICS related reports and information 315Analyzing transaction data 323Analyzing and displaying project data from Application Discovery 325Project data from Application Discovery reports and information 328Analyzing project data 338

Analyzing the Transaction Composition 339Analyzing transactions with the Transaction Composition graph 340Analyzing transactions with the Transaction Composition table 342Reviewing the top-ranked artifacts 343Comparing the projects 345Troubleshooting 346Providing feedback 349Accessibility features for ADI 350

-

-

-

-

-

-

-

-

-

-

-

IBM Application Delivery Intelligence 5.0.2 IBM® Application Delivery Intelligence (ADI) 5.0.2 online help offers instructions thatare designed to support development and test managers, testers and developers,and any other users who work with ADI.

Product overview From the product overview, you can learn the basic knowledge about IBMApplication Delivery Intelligence (ADI) 5.0.2, its key benefits, and its new features.Terminology overview You can find the technical terms and abbreviations that are used in ADI in theterminology overview.Tutorials Tutorials provide the step-by-step instructions with which you can explore the keycapabilities of ADI.Installation and setup You can install and set up ADI by using web-based express setup, by using web-based custom setup, or by using repotools command. You can also install ADI intoan existing IBM Rational® Collaborative Lifecycle Management (CLM) solution. Ifyou use a previous release of ADI and want to install a new version, you canmigrate all the data from the old version to the new one.Administration As a administrator for ADI, you can do administration tasks for user managementand back up your data. Preparing external data sources You can learn how to prepare code coverage results for batch applications,CICS®, COBOL, PL/I and Java™.Managing connections, data providers, and analysis collections To work with ADI, you need to know how to manage connections, data providers,and analysis collections.Analyzing data Before you can view the analysis data, ADI requires you to select your role to startthe analysis. After the role selection, three types of data analysis based ondifferent types of data providers are available: Development, Test, and Operations.The order of dashboards reports depends on the role you select. Troubleshooting Troubleshooting helps you identify and solve problems that occur while using ADI.Providing feedback You can provide feedback to ADI by sending an email, opening a ServiceRequest, or sending a Request For Enhancement (RFE).Accessibility features for ADI Accessibility features assist users who have a disability, such as restricted mobilityor limited vision, to use information technology content successfully.

6

-

-

-

Product overview From the product overview, you can learn the basic knowledge about IBM®Application Delivery Intelligence (ADI) 5.0.2, its key benefits, and its new features.

Overview of IBM Application Delivery Intelligence Throughout the DevOps lifecycle, a huge amount of data is produced, includingcode, requirements, designs, test artifacts, and operational information aboutapplications. ADI is a web-based tool that is built on the Jazz framework tofacilitate enterprise DevOps adoption and drive continuous improvement acrossthe lifecycle of product development, delivery, and maintenance. Key benefits of using ADI ADI's cognitive capabilities allow users to analyze the correlated runtimeperformance data, with static code quality data, as well as the testing details overtime. It pro-actively alerts users on early problem detection so that resources canbe shifted to the areas that need attention. By working with ADI, the typical users,such as testers and test managers, developers and development managers, canbenefit from ADI's functions to improve their DevOps process.What's new in ADI 5.0.2 The key new features of ADI 5.0.2 bring the integrated Cognitive DevOpsexperience that accelerates efficient application development and deployment.

Parent topic:IBM Application Delivery Intelligence 5.0.2

7

-

--

-

-

-

-

Overview of IBM Application Delivery Intelligence Throughout the DevOps lifecycle, a huge amount of data is produced, includingcode, requirements, designs, test artifacts, and operational information aboutapplications. ADI is a web-based tool that is built on the Jazz framework to facilitateenterprise DevOps adoption and drive continuous improvement across the lifecycleof product development, delivery, and maintenance.  The vision of ADI is to provide an insight dashboard with actionablerecommendations to enterprise development and test teams by:

Analyzing and visualizing historical trend information on application, usage, codecoverage, complexity, quality, and performanceProviding near real-time application and process health checksAnalyzing code coverage data and recommending tests to run to achieve bettertests and code coverageMonitoring previously hidden performance and resource data to make performanceissues exposed before production timeShowing the application inventory and quality trends to reduce development andmaintenance costsHighlighting the artifacts that are related to the performance concerned areas andproviding the call graph of the corresponding transaction that shows the artifactcomplexity metrics of risk assessment Making information accessible to stakeholders through a simple and intuitiveinterface

Parent topic:Product overview

8

--

-

--

-

-

--

--

--

Key benefits of using ADI ADI's cognitive capabilities allow users to analyze the correlated runtimeperformance data, with static code quality data, as well as the testing details overtime. It pro-actively alerts users on early problem detection so that resources can beshifted to the areas that need attention. By working with ADI, the typical users, suchas testers and test managers, developers and development managers, can benefitfrom ADI's functions to improve their DevOps process. Users from enterprise development and test teams can benefit from ADI throughfollowing ways. By using ADI code coverage function, testers can:

See the current and previous test coverage status in a single dashboard view.Determine the test coverage of a build and identify the modules that need moretesting for each build.Develop a test list that contains the minimum number of test cases to run for aregression for the next build.

By using ADI code coverage function, test managers can:

Receive recommendations for test case optimization.Identify testing coverage issues. With the help of test coverage trends to examineoverall release quality, test managers can act sooner in the development cycle.

By leveraging OMEGAMON for CICS data, developers can:

Be alerted about potential performance problems before the code goes intoproduction.See whether their code changes drive up response times including DB2 and fileI/O percentage wait time with the performance information of transactions that theyown and the associated trend data.

By monitoring the application inventory and quality trends, developers can also:

Visualize whether their codes are becoming easier to maintain. Identify unreachable codes to further simplify the code base.

By monitoring and comparing maintainability trends, development and testmanagers can:

Ensure accountability of outsourced projects and in-house projects alike. Enable quantifiable improvement objectives to be established by organization.

By correlating performance data from OMEGAMON for CICS and code quality datafrom Application Discovery, a developer can:

Pinpoint the artifacts directly related to the performance problem.Assess the risk of changing those artifacts based on when the code was changedand the maintenance indexes.

Parent topic:Product overview

9

10

-

-

-

-

-

-

-

-

What's new in ADI 5.0.2 The key new features of ADI 5.0.2 bring the integrated Cognitive DevOpsexperience that accelerates efficient application development and deployment. ADI 5.0.2 enables users to work smarter with data analysis by collecting, correlating,and analyzing data to optimize application delivery. You can foresee and reduce therisk of production failures by discovering multiple data through ADI, such astransaction response time including the DB2 and File I/O wait percentage time, CPUtime, usage frequency data from IBM® OMEGAMON® for CICS®, and codecoverage data from COBOL, PL/I, and Java™ environments. You can easily gatherapplication inventory, complexity, and quality metrics from Application Discovery(AD) 5.0.2 to manage improvements in application quality and maintainability for thelong haul. For more information about key new features for ADI 5.0.2, see the followingsections. Root cause analysis

Developers can identify peaks in slow response time of a specific transaction in agraph and then visually compare them to DB2 and File I/O wait time peaks todetermine whether the three metrics coincide to identify a problem.Developers can use the Transaction Composition Map of the transaction thatperform poorly to identify program artifacts that call in to the same data source(s)and changed recently then take corrective measures to resolve the problem.

Cognitive user guidance

ADI displays the key data points that adversely contribute to the worseningresponse time of transactions with the biggest impact.ADI provides insights from correlated OMEGAMON for CICS and ApplicationDiscovery data that identify previously undiscovered poor performing transactionsand problematic artifacts.ADI ranks results to evaluate risky program artifacts in a problematic transactionwith confidence and then helps developer to take corrective action to resolveproblems.

New user experience

User can select their role after logging in to ADI, and the role related informationappears on the top over the other available information.User can provide comments on the newly added send-feedback page.

Globalization

ADI 5.0.2 online help doc is available in 5 different languages: English, Japanese,German, French, and Spanish.

Parent topic:Product overview

11

12

--

----

--

--

-

-

-

---

--

--

-

Terminology overview You can find the technical terms and abbreviations that are used in ADI in theterminology overview. To view glossaries for other IBM® products, go towww.ibm.com/software/globalization/terminology.

analysis collectionAs an ADI concept, it defines a collection of artifacts for which the analysisinformation would be provided. Users can group same or disparate artifactsfrom different data providers and get the analysis visualization for the selectedcollection. For example, an analysis collection could be

Different service classes from OMEGAMON for CICS data providerAn Application Discovery projectA set of programs for which code coverage data is availableCombination of two or more of the above

Application Discovery (AD) project

A project in AD is a user (typically an admin role) defined grouping of programartifacts (source codes), dependencies (copy books or includes), build scripts(JCL) and so on, on which the static analysis is performed and analysis metricsare gathered.

buildThe process of creating an executable to identify the user activities that anapplication intend to address.For z Systems:

Only changed programs are built. If changes are made only in a sub program,only the subprogram is compiled and linked in with the UI module or mainprogram.A build can consist of only one module, depending on the size of theapplication and the changes that are going in.The test team tests the whole application, which includes all the programs thatconstitute an application.

For example, getting an insurance quote consists of:

A UI program to accept user input and display the insurance quote or errorsA main program that validates the user inputA sub program that is called by the main program to get or calculate theinsurance quote and return the value or error to the main program

All these programs, modules, or files need to be built together to verify theinsurance quote application tasks.

code coverageA measure of how much of code in a program or file is being executed as partof a test or test case. The result can contain coverage for one or moreprograms or files, depending on how the test is structured.

CICSPlexA CICSPlex is an environment in which multiple and interconnected CICSregions operate. A CICSPlex lets CICS and associated applications use the fullcapabilities of Parallel Sysplex architecture.

file / program

13

-

-----

--

--

--

--

--

--

A software artifact that contains the logic to perform one or more of theapplication's activities.Examples:

Updating a database recordCalculating the insurance quoteCalculating mortgage rateValidating UI fieldsQuerying the account balance

provider

Data source. An analysis collection can have multiple data providers that ideallycovering the DevOps entry points.Examples:

BuildPerformance

service class

IBM OMEGAMON® for CICS® allows users to define a service policy, that is, aset of categorized goals called service classes that define the targetedperformance throughput and which transactions the goal applies to. And userscan apply the service policy to the workload running in the environment. Adefault service policy and set of service classes is provided upon installation ofIBM Tivoli® OMEGAMON XE for CICS. Users can customize the defaultservice policy and service classes and also add additional service classes.

test / test caseA set of steps to verify a specific activity, a set of activities, or part of an activitythat the application is intended to support.For z Systems:

Tests are mostly manual tests.A test case might or might not contain a list of steps to go through.

Examples:

Running a transactionSubmitting a batch job or jobs with different set of inputs

Parent topic:IBM Application Delivery Intelligence 5.0.2

14

-

-

-

-

-

-

-

Tutorials Tutorials provide the step-by-step instructions with which you can explore the keycapabilities of ADI.

Installing and setting up ADI This tutorial guides you to install and set up ADI as an administrator.Setting up Manual Builds for Code Coverage Analysis In this tutorial, you play the role of Alvin, an ADI administrator who is also knownas Adi Admin, to create a Manual Builds data provider and an analysis collectionas requested by Tammy, a test manager. Tammy wants to use ADI for a newapplication. You perform the following activities to set up an analysis collection fora new application requested by Tammy.Setting up automated code coverage data collections This tutorial guides you through how to set up automated code coverage datacollections.Exercising setting up a Manual Builds for code coverage analysis This is a required exercise as prerequisite for the Analyzing code coveragetutorial. You need to perform the set up of a Manual Builds data provider and ananalysis collection to analyze code coverage for Perfect Calculator application.Analyzing code coverage This tutorial guides you through how to analyze code coverage results with theApplication Delivery Intelligence.Generating sample data In this tutorial, you perform the role of ADI admin, Alvin, to generate the sample forthe end-to-end root cause analysis tutorial using data generation functionality. End-to-end system performance root cause analysis In this tutorial, you perform the role of Marco, the development lead of the zMobileHealth Application, to perform root cause analysis of a performance defectreported from Trish, a tester.

Parent topic:IBM Application Delivery Intelligence 5.0.2

15

-

-

Installing and setting up ADI This tutorial guides you to install and set up ADI as an administrator.

Installing ADI and configuring JTS to be the foundation of ADI This sectionl guides you through the installation of ADI and steps to configureIBM® Jazz™ Team Server (JTS) as the foundation of ADI.Setting up a project area to start applications to be analyzed After you finish the Express setup for ADI, you need to create a project area foranalysis.

Parent topic:Tutorials

16

1.2.3.

4.

1.2.

3.4.

5.

A.

Installing ADI and configuring JTS to be thefoundation of ADI This section guides you through the installation of ADI and steps to configure IBM®Jazz™ Team Server (JTS) as the foundation of ADI. Before you begin the installation, you need to update the host file to understand thepublic URI you use for the setup. Complete the following steps to update the hostfile.

Go to Start > All Programs > Accessories and run Notepad as an administrator.Open the host file to edit from Windows > System32 > drivers > etc directory.Update the host file for the Localhost as the following.

Save the host file.

Complete the following steps to install ADI.

Unzip the ADI installer that you obtained.Browse to the location where you unzip the ADI installer and navigate to the\adi\server directory.Run server.startup.bat in a command window. Wait until the server starts up.Start the Mozilla® Firefox® browser and go tohttps://healthcare.example.com:9443/jts/setup.Allow the browser to connect to the website when a message warning that yourconnection is not secure appears.

Click Add Exception... to proceed to the next step.

17

B.

6.

7.A.

Add Security Exception pop-up window appears. Click the Confirm SecurityException button.

Jazz Team Server login page appears. Log in with ADMIN as user ID and ADMINas password (case sensitive).

Take the following steps when the JTS setup wizard appears.

On the Welcome page, select Express Setup and click Next. 18

B.1.

2.

On the Configure Public URI page, complete the following steps.

Step 1: Configure Public URI The default Public URI at this step is thehttps://healthcare.example.com:9443/jts that you've set in the previous step.You can also use the Localhost URI for evaluation purpose. However, forthe production server, you need to update the public URI to a valid one.When the Public URI is set, you are not able to modify it.

Step 2: Confirm Public URI Check to confirm that you understand that when the Public URI is set, itcannot be modified.

19

3.4.

C.

-----

D.E.

Click Test Connection to test the connection to the server.If the test is successful, click Next.

Fill in the following information and click Next on the Create AdministrativeUser page to create an administrator user for setting up ADI server in latersteps.

User ID: AdiAdminName: Adi AdminPassword: AdiAdminRe-type Password: AdiAdminE-mail Address: adiadmin@healthcare.com

Click Next to proceed. The Setup Progress page appears. Wait until the setup progress completes. Click Next.Note: Now you areswitched to AdiAdmin user.

20

F.

On the Assign License page, select the Activate Trial link next to the licenseof IBM Application Delivery Intelligence – User.

21

G.

H.

Client Access License Agreement dialogue box appears. Select to acceptthe terms in license agreement and then click Finish.

Click Finish to complete the Express setup.

Parent topic:Installing and setting up ADI

22

1.

2.

3.

---

A.----

-B.

C.-

Setting up a project area to start applications to beanalyzed After you finish the Express setup for ADI, you need to create a project area foranalysis. Complete the following steps to set up a project area.

Open your Firefox browser and navigate tohttps://healthcare.example.com:9443/jts/admin. The JTS Administration homepage appears.Select the Create Users link in the Manage Users section.

Take the following steps to create users.Note: In these tutorials, you need tocreate 3 users for use.

Marco, a developer leadTammy, a test managerTrish, a tester

Enter the following information in the form for creating a user.

User Name: MarcoUser ID: MarcoE-mail Address: marco@healthcare.comIn the Client Access Licenses section, select the checkbox in front of IBMApplication Delivery Integration – User.Click Save to create this user.

Select Users > Create User on the top menu to create another user.

Enter the following information on the form for creating a user.

User Name: Tammy

23

---

-D.E.

----

-4.

5.

6.

A.

B.----

User ID: TammyE-mail Address: tammy@healthcare.comIn the Client Access Licenses section, select the checkbox in front of IBMApplication Delivery Integration – User.Click Save to create this user.

Select Users > Create User on the top menu to create the third user.Enter the following information on the form for creating a user.

User Name: TrishUser ID: TrishE-mail Address: trish@healthcare.comIn the Client Access Licenses section, select the checkbox in front of IBMApplication Delivery Integration – User.Click Save to create this user.

Navigate your browser to ADI application fromhttps://healthcare.example.com:9443/adi/web address.Note: You may want todisable the pop-up blocker from this page before start. ADI application appears with the All Projects page. For the first time user, noproject is available. Click on the project area management link to set up the

project. The application navigates to the Application Administration - IBM ApplicationDelivery Intelligence (ADI) page. Take the following steps to create a projectarea. Click on Create Project Area on the upper right corner of the Active Project

Areas section. In the Create Project Area form, provide the following information.

Project Area Name: HealthCare4AllSummary: Health Care SystemsDescription: Project to store data to be analyzed for Health Care systems.Process: If it is not yet selected, select IBM Application DeliveryIntelligence Application Default Process.

24

C.1.2.

3.

4.

D.

1.

2.3.4.

In the Members section, assign members to the project area.

Click on the Add link on the upper right corner of the Members section.On the Select Users pop-up window, click Show All to see all activemembers.Multi-select Adi Admin, Marco, Tammy, and Trish from the Matching userslist.Click Add and Close.

In the Administrators section, assign users as administrators of the projectarea.

Click on the Add link on the upper right corner of the Administratorssection.On the Select Users pop-up window, type Ad on the search box.Select Adi Admin from the Matching users list.Click Add and Close.

25

E.

F.

G.

-

Click Save next to the project area name on the top to create the project area.Note: Upon saving the project area, a warning message appears showing thatsome new members were added without process roles. Those members willhave the permissions of the "Everyone" role. The role permissions will be setup later in the next 2 steps.

On the Send Team Invitations to New Members? pop-up window, selectCancel.Note: If you are running the production server and you have set up themail server, you can select the users which you would like to send teaminvitations to.

Go to the Members section to set up process roles for all members.Note:Process roles are set in order to control the access for different users. 3 rolesare available.

Data Provider Administrator: The administrator of this ADI project. Theadministrator has the ability to create, modify, and delete data providers and

26

-

-

1.

2.

3.

analysis collections.Analysis Collection Owner: The owner of an analysis collection. Theanalysis collection owners can make changes to memberships and modifysettings of analysis collection. They can create builds and upload coverageresults for Manual Builds data providers and Rational Team Concert Buildsdata providers. They can also request data collections for data providers anddelete an analysis collection. Analysis Collection Member: The member of an analysis collection. Theanalysis collection members can review all data in an analysis collection andits data providers. They can only modify the settings of the analysiscollection.

Hover over to the name of Marco, the Members menu appears in front ofthe name.Expand the Members menu and select Add Process Roles.

On the Add Roles pop-up window, select Analysis Collection Owner.

27

4.5.

H.

Click Add to add process role.Repeat steps 1 - 4 to add process role for Adi Admin, Tammy, and Trish.Assign the data Provider Administrator to Adi Admin, the Analysis CollectionOwner to Tammy, and the Analysis Collection Member to Trish.

Click Save on the upper right corner of window to save this project area. You have now finished the setup of project area for the HealthCare4All project. Youcan navigate to HealthCare4All project on the ADI Application by clicking on theHome icon on upper left corner of window and then select IBM ApplicationDelivery Intelligence (ADI) > HealthCare4All from the dropdown menu that

appears. The following screen is the Welcome page of ADI application. ADI requires you toselect a role before you can continue on the analysis. However, if you're a dataprovider administrator, you can perform the setup of Connections, Data Providers,and Analysis Collections without selecting any roles.

28

Parent topic:Installing and setting up ADI

29

-

-

-

-

-

-

Setting up Manual Builds for Code CoverageAnalysis In this tutorial, you play the role of Alvin, an ADI administrator who is also known asAdi Admin, to create a Manual Builds data provider and an analysis collection asrequested by Tammy, a test manager. Tammy wants to use ADI for a newapplication. You perform the following activities to set up an analysis collection for anew application requested by Tammy. Prerequisite Before you begin this tutorial, you need to complete the following task.

Installing and setting up ADI

Defining a new application as an analysis collection This section introduces you how to define a new application as an analysiscollection and set up the first build to store code coverage information.Adding the code coverage files to the first build In this section, you play the role of Tammy, the test manager, to add the codecoverage files for analysis to the first build that is created by Adi Admin in theprevious step.Viewing the code coverage analysis results of the first build You can view the analysis code coverage results of the first build you've set in theprevious section.Defining a new build and planing the next test cycle using Minimal Test to Run In this section, you will play the role as the test manager Tammy to add a newbuild and the tester Trish to plan the next test using Minimal Test to Run.Adding new code coverage results to an existing build In this section, you play the role of Tammy, the test manager, to add the new codecoverage files provided by Trish to the existing 2015Nov11Build build. In the casethat there are multiple testers, Tammy can merge the code coverage files andupload all the files to the 2015Nov11Build build for the code coverage analysis.

Parent topic:Tutorials

30

1.

2.

3.

4.

5.

6.

Defining a new application as an analysis collection This section introduces you how to define a new application as an analysiscollection and set up the first build to store code coverage information. Complete the following steps to define a new application as an analysis collection.

Navigate your browser tohttps://healthcare.example.com:9443/adi/web/projects/HealthCare4All.Log in with AdiAdmin as user ID and AdiAdmin as password in the role ofadministrator Alvin to create data providers.The Welcome page appears. As an administrator, you do not need to select anyrole on this page. The role selection is only required when you want to view theanalysis dashboards and reports.To add a new application, you need to start with adding a data provider. Data

Provider is a source of data being analyzed. Select the Data Providers icon () from the left menu to go to the Data Providers page.On the Data Provider page, a warning message appears that shows no dataprovider available in the system yet.

Click the Add icon ( ) next to the Data Providers header to add a new dataprovider. The Add Data Provider page loads with choices of available data

providers.

31

7.8.

----

-

-----

9.

Select the Manual Builds data provider.The form for creating the Manual Builds data provider appears. Fill in thefollowing information.

First BuildBuild Name: 2015Nov10BuildDate of Build: 10 November 2015Description: November 10, 2015 build for SAM application.

Code Coverage Files You don't need to upload the Code Coverage Files at this point. The CodeCoverage Files will be uploaded by Tammy, the test manager in the nextsection. Data Provider Details

Name: SAM Manual BuildDescription: Manual build for SAM applicationEnable headless collection support: Make sure that the box is unchecked.Select All Data for the number of days to keep data in the data warehouse.

Click the Add button to create this data provider. The Providers page appearswith the SAM Manual Builds data provider added.

32

10.

11.12.

13.

14.

Hover over the SAM Manual Builds data provider, you can see action icons on

the bottom right of the card. Click the Pencil icon ( ) to edit the Manual Builds data provider information.The Edit Data Provider page loads, you can use this page to edit the Nameand Description of the Manual Builds data provider.

Click Save to save changes or Cancel to cancel changes. Now you have created a data provider for SAM application. You will then createan analysis collection as application and associate the data provider withanalysis collection. Select the Analysis Collection icon ( ) from the left menu to go to theAnalysis Collections page. The Analysis Collections page loads with no

analysis collections.

33

15.

16.---

--

-17.

18.

Click the Add icon ( ) next to the Analysis Collections header to add ananalysis collection.The Add Analysis Collection form appears. Fill in the following information.

Name: SAM ApplicationDescription: This is analysis collection for SAM Application.Contributor List: Select Tammy as Owner and Trish as Member.Note: Bydefault the user who creates an analysis collection will be automatically addedas the owner of the analysis collection. Provider: Select SAM Manual Builds. The Code Coverage Data Provider Settings appears. For Code CoverageThreshold, slide the left slider to 50% and the right slider to 80%.

Click Add to add this analysis collection.

The Welcome page appears. Select the Analysis Collection icon ( ) from theleft menu to go to the Analysis Collections page. You should see the SAMApplication added.You have done the setup of Manual Builds data provider and analysis collection.Go to the User menu on the bottom left of the view and click on it.

34

19.

20.

Select Logout to log out from ADI. The login page appears. You are now loggedout from ADI. Next you will be logging in as Tammy, the test manager. Beforeyou can start viewing the Code Coverage analysis, you need to upload CodeCoverage files for analysis.The Analysis Collections page loads. You can see that the SAM Applicationanalysis collection is added to the system.

Now you as Tammy has created the SAM Application analysis collection andassociated the SAM Application with the SAM Manual Builds data provider. You cansee the Code Coverage analysis results of the 2015Nov10Build from the Analysispage. Parent topic:Setting up Manual Builds for Code Coverage Analysis

35

1.

2.

3.

4.

5.

6.

7.

8.

Adding the code coverage files to the first build In this section, you play the role of Tammy, the test manager, to add the codecoverage files for analysis to the first build that is created by Adi Admin in theprevious step. Complete the following steps to add the code coverage files to the first build.

Log in as Tammy, the test manager, with Tammy as user ID and Tammy aspassword.Select the HealthCare4All project.

The Welcome page appears. Select the Test role. Note: To view analysisresults, ADI requires you to specify your primary role. ADI uses the provided roleto organize dashboards and reports based on the role focus. For example, whenthe Test role is selected, the dashboard and reports that interest tester most willbe shown first. Select the Continue button. Analysis view displays with SAM application.However, the report shows No Data at this point because no code coverage filesare uploaded yet.

Select the Data Providers icon ( ) from the left menu to go to the DataProviders page.Hover over SAM Manual Builds data provider, you can see action icons on thebottom right of the card. Note: The set of action icons are different from what youhave seen in the previous section. This is because of the role permissions thatare assigned to this user. Tammy has an analysis collection owner rolepermission. As a result, she can not edit or delete a data provider. For moreinformation about role permissions, see Assigning role-based permissions toADI users.

Select the List Builds icon ( ). The page showing all the builds in the dataprovider appears. Currently only one build is available, that is, 2015Nov10Build.Select the Edit icon ( ) on the 2015Nov10Build row. The Edit Build form

appears.

36

9.

10.

11.12.13.

On the Edit Build form, click the Add icon ( ) next to Code Coverage Filesheader section.Select samt1.zip, samt2.zip, samt3.zip, samt4.zip, samt5.zip, samt6.zip,samt7.zip as Code Coverage Files.Note: Browse to the sample data folder.Open the installed ADI folder > adi > cobol-coverage > SAM App >November 10 2015. Multi-select sam1.zip, sam2.zip, sam3.zip, sam4.zip,sam5.zip, sam6.zip, sam7.zip files.

Click the Save button to save the changes. The confirm dialogue appears. Click the Ok button to confirm the files being uploaded.The page with list of builds appears. You then see the log message showing thedata is successfully added to the warehouse.

Now as Tammy you have added the code coverage files to the first build of the SAMApplication analysis collection. You are now able to see the Code Coverageanalysis results of the 2015Nov10Build from the Analysis page. Parent topic:Setting up Manual Builds for Code Coverage Analysis

37

1.2.

3.

4.

Viewing the code coverage analysis results of thefirst build You can view the analysis code coverage results of the first build you've set in theprevious section. Complete the following steps to view the code coverage analysis results of2015Nov10Build from the Analysis page.

Select the Analysis icon ( ) from the left menu to go to the Analysis page.On the Analysis page, you can see SAM Application card with the Code

Coverage report. The Code Coverage result shows that SAM Application has only 66% CodeCoverage. Select on the SAM Application name in order to view the analysis of SAMApplication.On the SAM Application page, you can see the analysis of 2015Nov10Build. Thefirst chart is the latest Code Coverage result of SAM Manual Builds showing 66%Code Coverage. Next to the Code Coverage report are the Code CoveragePercentage Trend and the Executable Lines Covered Trend. Since there is onlycode coverage data for one build, no trend chart shows. You also see no data onthe Biggest Coverage Drops for the same reason.

38

5.6.

7.

Select SAM Manual Build : 2015Nov10Build to view code coverage details.On the 2015Nov10Build page, you can see 2 files within this build: SAM1.cbl andSAM2.cbl. Observe that SAM2.cbl has quite low Code Coverage percentage. Thisbrings the overall Code Coverage of this build to the warning state.

Select the Expand icon ( ) in front of SAM2.cbl file to view detailed codecoverage analysis result of SAM2.cbl.

From the detailed code coverage analysis, you can see that only 31 of 77executable lines are tested. There are 3 test cases ran against SAM2.cbl. Youcan also see that ADI suggested SAMT3 test case as minimal tests to run. Thismeans that your test cases are not effective. SAMT1 and SAMT4 covered thesame executable lines as SAMT3.

Now you have gone through the Code Coverage analysis. Next, you will play therole of Tammy, the test manager to add a new build and Trish, the tester to use thecode coverage analysis results in ADI to plan the next test. Parent topic:Setting up Manual Builds for Code Coverage Analysis

39

1.

2.

3.-----

Defining a new build and planning the next testcycle using Minimal Test to Run In this section, you will play the role as the test manager Tammy to add a new buildand the tester Trish to plan the next test using Minimal Test to Run. The development team informs Tammy that the new build will be available fortesting. Tammy adds a new build to SAM Manual Build without Code Coverageresults and informs her team that the build is available for testing. Her team can thenuse the code coverage information in the ADI to get recommended test for this newbuild. Complete the following steps to complete this task.

Select the Data Providers icon ( ) from the left menu to go to the DataProviders page.Hover over the SAM Manual Build and click on the Add Build icon ( ).

In the Add Build form, fill in the following information.

Build Name: 2015Nov11BuildDate of Build: 11 November 2015Description: November 11, 2015 build for SAM ApplicationSelect Modified Files: SAM1.cblCode Coverage File: Do not enter anything at this point.

40

4.

5.

A.

B.

C.D.E.

6.

Click Add button to add the 2015Nov11Build.

You have now added a new build to SAM Manual Build. The test team can go tothe Analysis page and look at this build to get suggested list of Test to Runwhen they perform testing. Logout from Tammy and login as Trish, a tester, by using Trish as user ID andTrish as password.

Select the User icon ( ) from the left menu.

Select Logout. The Login page appears as a pop-up window.On the Login page, log in as Trish.On the All Projects page, select HealthCare4All.

Select the SAM Application on the Analysis page and select SAM ManualBuild : 2015Nov11Build on the SAM Application page.Note: You see no datain all reports. This is because you have not yet uploaded the code coverageresults for Nov 11, 2015 Build.

41

7.

On the 2015Nov11Build page, click the Expand icon ( ) on each file. Look atthe Historical Test To Run column. Trish, the tester, can take the entire list toperform the testing of the new build.

In some case, Trish, the tester, may not want to test the entire build but want totest only the changed files. Trish can also filter out the files without changes to

42

8.

9.

10.

11.

12.

get the list of test to run for updated files only. Click on the Option Menu icon ( ) on the right to open the Option Menu Panel.Select the Changed Files Only option.

Confirm the list of files that are updated on the Changed Files page by clickingApply Filter.Click on the Option Menu icon ( ) again to close the Option Menu Panel. Nowyou can only see the list of files that are updated in 2015Nov11Build. Trish cannow get the list of test files to test on the updated files. In this case, there is onlyone file updated, SAM1.cbl. The list of test files to test this file includes SAM1,SAM2, SAM3, SAM4, SAM5, SAM6, and SAM7.Log out from Trish.

Parent topic:Setting up Manual Builds for Code Coverage Analysis

43

1.2.

3.

4.5.

6.

7.

8.9.

Adding new code coverage results to an existingbuild In this section, you play the role of Tammy, the test manager, to add the new codecoverage files provided by Trish to the existing 2015Nov11Build build. In the casethat there are multiple testers, Tammy can merge the code coverage files andupload all the files to the 2015Nov11Build build for the code coverage analysis. Complete the following steps to add new code coverage results to an existing build.

Login as Tammy with Tammy as user ID and Tammy as password.On the All Projects page, select HealthCare4All. The Analysis page appears.

Select the Data Providers icon ( ) from the left menu to go to the DataProviders page.

Hover over the SAM Manual Build and click on the List Build icon ( ).From the list of builds, click the Edit icon ( ) on the 2015Nov11Build to edit

this build. On the Edit Build form, click the Add icon ( ) next to Code Coverage Filesheader.Select sam1.zip, sam2.zip, sam3.zip, sam4.zip, sam5.zip, sam6.zip,sam7.zip as Code Coverage Files.Note: Browse to the sample data folder.Open the installed ADI folder > adi > cobol-coverage > SAM App >November 11 2015. Multi-select sam1.zip, sam2.zip, sam3.zip, sam4.zip,sam5.zip, sam6.zip, and sam7.zip files.

Click Save to save the changes.On the pop-up dialog, click OK to confirm the changes. The page with the list ofall builds appears with the message showing that the test files are successfullyadded to the data warehouse.

44

10.

11.

12.

13.

Now you have successfully added new code coverage results to the existingapplication. You can view the results of the Code Coverage analysis by going tothe Analysis page. Select the Analysis icon ( ) from the left menu to go to the Analysis page.

Click on SAM Application to view SAM Application code coverage reports. Youcan see that code coverage of SAM Application is now updated to 74%. TheCode Coverage Percentage Trend and the Executable Lines Covered Trendsare now updated with the data for Nov 10 and Nov 11 builds. Note: From 2 builds, the total executable lines of 2 builds are the same but theexecutable lines hit are increased from 168 to 186. This is the reason that theoverall code coverage for SAM Application is increased.

Click on SAM Manual Build: 2015Nov11Build to view detailed code coverageanalysis of SAM Application as you did previously.Expand SAM1.cbl and SAM2.cbl to view detailed Code Coverage analysis forindividual file. You can see that there is one line update in SAM1.cbl andexecutable lines that are tested has increased for SAM2.cbl.

45

14. Click on SAM2.cbl. You can see code coverage analysis at the flow point levelfrom this view. You can see the level of code coverage for each flowpoint inmore detail. For example, MAIN is tested by 88%. This has increased 13% from

the previous run. Now you have explored how to add an application and upload the code coverageresults to ADI for analysis as a test manager. You have also played the role of atester performing the test for next build to get the list of recommended tests fortesting the next build. Parent topic:Setting up Manual Builds for Code Coverage Analysis

46

-

-

--

-

-

Setting up automated code coverage datacollections This tutorial guides you through how to set up automated code coverage datacollections. ADI supports various automation scenarios for code coverage data collection asbelow.

Automated code coverage data collection utilizing the headless code coveragecollector daemon program of RDz (IBM Rational Developer for z Systems, 9.5).ADI 1.0.1 ships the headless collector and allows debuggers and code coverageengines to send code coverage data directly over the network so that ADI cancollect the code coverage data automatically. Automated code coverage data collection from RTC (IBM Rational Team Concert6.0 or higher) Build results. ADI 1.0.1 supports connecting to RTC servers (6.0 orhigher) and accessing RTC Build results that have code coverage data attached.This capability allows you to download these coverage files and add themautomatically to ADI.

In this tutorial, you can explore one of the automation scenarios that ADI supports.That is, the automated code coverage data collection utilizing the headless codecoverage daemon program of RDz 9.5. You play the role as Tammy, the testmanager, to add a new application in order to perform the code coverage analysis.This task is similar to Setting up Manual Builds for Code Coverage Analysis.However, in this tutorial, when creating the data provider, Tammy enables theheadless collector for ADI to automatically collect the code coverage data. Prerequisites Before you begin this tutorial, you should complete the following activities.

Installing and setting up ADISetting up Manual Builds for Code Coverage Analysis

Adding a Manual Builds data provider to collect code coverage data automatically In this section, Tammy the test manager wants to start monitoring code coveragefor a new application called Health Care application. She wants the code coveragedata to be automatically collected by ADI. So she requests Alvin, the ADIadministrator, to create a new data provider to collect the data for her Health Careapplication.Creating an analysis collection for a new application and setting up code coverageresults for automated data collection In this section, you play the role as Tammy, the test manager, to load the codecoverage results to the location where ADI can collect data automatically andtrigger the Health Care Manual Builds data provider to collect the code coverageresults.

Parent topic:Tutorials

47

1.

2.

3.

4.

5.6.

A.1.2.3.

Adding a Manual Builds data provider to collectcode coverage data automatically In this section, Tammy the test manager wants to start monitoring code coverage fora new application called Health Care application. She wants the code coverage datato be automatically collected by ADI. So she requests Alvin, the ADI administrator,to create a new data provider to collect the data for her Health Care application. As Alvin, you need to complete the following steps to add a Manual Builds dataprovider to collect code coverage data automatically.

Navigate your browser tohttps://healthcare.example.com:9443/adi/web/projects/HealthCare4All.Log in with AdiAdmin as user ID and AdiAdmin as password for the ADIadministrator role.

Select the Data Providers icon ( ) from the left menu to open the DataProviders page to add a new data provider. The Data Provider page loads with1 Manual Builds data provider: SAM Manual Build.

Click the Add icon ( ) next to the Data Providers header to add a new provider.Add Data Provider page loads with the choices of available data providers.

Select the Manual Builds provider. Manual Builds creation form appears.Fill in the following information.

First Build Build Name: 2016Feb2BuildDate of Build: 2 February 2016Description: February 2, 2016 build for Health Care application.

48

B.

C.1.2.

3.4.

5.

7.

8.

Code Coverage Files You won't load any code coverage files at this moment. Data Provider Details

Name: Health Care Manual BuildsDescription: Manual build with automated data collection for HealthCare application.Select the Enable headless collection support check box.Select Manual from the Collection Trigger choices. This is to set how thecode coverage data is to be collected. It can be on demand by selectingManual or on schedule by selecting Automatic and specifying thecollection interval in hours. For the objective of demonstration in thistutorial, you do on demand collection in order to see the code coveragedata being loaded immediately.Select All Data in number of days you want to keep data in the datawarehouse. You can choose among All Data (to keep the data forever),90 Days, 120 Days, 180 Days, and 360 Days.

Click the Add button to add this provider. The Data Providers page appearswith the Health Care Manual Builds added as the first card.

Hover over the Health Care Manual Builds card. Select the List Builds icon (

) in order to view all the builds of this Manual Builds provider. List Builds 49

9.

10.

11.

12.

A.----

-

-

page appears with one build. Note: Code Coverage value indicating N/A at thispoint because ADI has not yet collected the code coverage data.

Select the Back icon ( ) next to the Builds header to return to the DataProviders page. Alvin has now finished creating the data provider with automated data collection.Next he will create an analysis collection, associate analysis collection with thisdata provider, and set up a build to collect code coverage data automatically foranalysis. Select the Analysis Collection icon ( ) from the left menu to open theAnalysis Collections page.The Analysis Collections page loads with 1 analysis collection: SAMApplication.Click the Add icon ( ) next to the Analysis Collections header to add ananalysis collection. The Add Analysis Collection form appears

Fill in the following information.Name: Health CareDescription: This is analysis collection for Health Care application.Contributor List: Select Tammy as Owner and Trish as Member.Provider: Select Health Care Manual Builds. The Code Coverage DataProvider Settings appears.For the Code Coverage Threshold, slide the left slider to 60% and the rightslider to 80%.

Click the Add button to add this analysis collection.

50

13.

14.

The Welcome page loads. You can select the Analysis Collection icon ( ) tosee that the Health Care analysis collection is added to the system as the first

card. Log out from ADI.

You have successfully created the Health Care analysis collection with the first buildand set it up in the way that it can automatically collect the code coverage files. Inthe next section, you will play the role of Tammy, the test manager, to load the codecoverage files into the location where ADI can collect them for analysis. In realpractices, the step to prepare and load the code coverage files into an ADI locationcan be done automatically depending on the programming languages and tools youare using to generate code coverage data. For more information, see Preparingexternal data sources. Parent topic:Setting up automated code coverage data collections

51

1.

2.

3.

4.

5.

Creating an analysis collection for a new applicationand setting up code coverage results for automateddata collection In this section, you play the role of Tammy, the test manager, to load the codecoverage results to the location where ADI can collect data automatically and triggerthe Health Care Manual Builds data provider to collect the code coverage results. As Tammy you need complete the following steps.

Log in with Tammy as user ID and Tammy as password for the test managerrole. The All Projects page appears.Click on the project of HealthCare4All. The Analysis page loads with twoanalysis collections: Health Care and SAM Application.Select the Analysis Collection icon ( ) from the left menu to open theAnalysis Collections page. The Analysis Collections page loads with 1analysis collection: SAM Application.Note: At this point, you as Tammy cannotreview the code coverage analysis results. You need to load the code coveragefiles into the ADI location and trigger ADI to collect code coverage data.

Select the Data Providers icon ( ) from the left menu to open the DataProviders page.Hover over the Health Care Manual Builds data provider and select the CopyStartup Key icon ( ) to copy the start up key to the clipboard.

52

6.

7.

8.

9.

10.

11.

Open the Notepad program and paste the startup key to the Notepad. You willsee the text similar to the following sample. Remember the provider ID. In thiscase the providerid is R5G8VW.

Browse to the sample data folder: Installed ADI folder > adi > cobol-coverage> HealthCare App > February 2 2016. Select all the zip files under February 22016 folder and copy them to the clipboard.Browse to the ADI location. Select adi > server > conf > adi > headless-CC-files.Open the folder that has the same name as providerid. From this example it isthe R5G8VW-files folder. Paste all the zip files you copied to this folder.

In your typical scenario, you want the code coverage results to be loaded intothis location automatically, which depends on the programming languages andtools you are using to generate code coverage data. For more information, seePreparing external data sources. Go back to the ADI application and hover over the Health Care Manual Buildscard. Select the refresh icon ( ) in order to trigger ADI to collect the codecoverage data. Data Collection window appears.

Click OK to start the data collection.

53

12.

13.

14.

Select the List Builds icon ( ) from the Health Care Manual Builds card. TheList Builds page appears with the list of builds. You can now see theinformation bar indicates that data is loaded to the warehouse. Code Coveragefor this build now shows that the percent code coverage of this build is 59%.

Select the Analysis icon ( ) from the left menu to open the Analysis page toview the code coverage analysis results. On the Analysis page, you can now see the Code Coverage results on theHealth Care analysis collection. You can select the Health Care analysiscollection to view the detail of Code Coverage analysis for Health Careapplication as in the Setting up Manual Builds for Code Coverage Analysis

tutorial.

You have now explored how to add a new Manual Builds data provider to collect thecode coverage data automatically. This scenario reduces the manual steps youhave to perform in order for ADI to perform analysis of code coverage data. Asmentioned in the beginning of Setting up automated code coverage data collections, ADI also includes the capability of automated code coverage data collection froman RTC build. Due to the lack of RTC hosted environment, you are not able toexplore this scenario in this tutorial for now. If you are interested in the ADIcapability of automated data collection from an RTC build and already have an RTCserver hosted with code coverage data, you can find more information in this onlinehelp in the Chapter of Managing connections, data providers, and analysiscollections. Parent topic:Setting up automated code coverage data collections

54

55

-

-

-

Exercising setting up a Manual Builds for codecoverage analysis This is a required exercise as prerequisite for the Analyzing code coverage tutorial.You need to perform the set up of a Manual Builds data provider and an analysiscollection to analyze code coverage for Perfect Calculator application. Before you begin this tutorial, you need to complete the following task.

Installing and setting up ADI

Setting up a Manual Builds data provider This section guides you how to set up a Manual Builds data provider for codecoverage analysis of Perfect Calculator application.Setting up an analysis collection This section guides you how to set up an analysis collection for code coverageanalysis of Perfect Calculator application.

Parent topic:Tutorials

56

1.

2.

3.

4.

5.

6.A.

1.2.3.

B.1.2.

3.

Setting up a Manual Builds data provider This section guides you how to set up a Manual Builds data provider for codecoverage analysis of Perfect Calculator application. Complete the following steps to set up a manual build provider for Perfect Calculatorapplication.

Navigate your browser tohttps://healthcare.example.com:9443/adi/web/projects/HealthCare4All. Log in ADI with AdiAdmin as user ID and AdiAdmin as password. TheWelcome page appears.

Select the Data Providers icon ( ) on the left menu to open the DataProviders page.Click the Add icon ( ) next to the Data Providers header to add a dataprovider.On the Add Data Provider form, select Manual Builds. The form for creatingthe Manual Builds data provider appears.

Fill in the following information.

First BuildBuild Name: 2015Nov10BuildDate of Build: 10 November 2015Description: November 10, 2015 build for Perfect Calculator application.

Code Coverage Files

Click the Add icon ( ) next to the Code Coverage Files header section.Browse to the installed folder > adi > cobol-coverage > Perfcalc App >November 10 2015 folder.Select all the zip files in the November 10 2015 folder. (Perfcalct1.zip,Perfcalct2.zip, Perfcalct3.zip, and Perfcalct4.zip)

57

4.

5.A.B.C.

D.

7.

8.

9.A.B.C.D.E.

1.

Click the Open button.

Data Provider Details

Name: Perfect Calculator Manual BuildsDescription: Manual builds for Perfect Calculator applicationEnable headless collection support: Make sure that the box isunchecked.Select All Data for number of days to keep data in the data warehouse.

Click the Add button to create this data provider. The Data Providers pageappears with the Perfect Calculator Manual Builds added.

Hover over the Perfect Calculator Manual Builds, click the Add Build icon ( ) toadd another build.On the Add Build form, fill in the following information.

Build Name: 2015Nov11BuildDate of Build: 11 November 2015Description: November 11, 2015 build for Perfect Calculator ApplicationSelect Modified Files: CLCTPCTB.cbl, PERFCALC.cblCode Coverage Files:

Click the Add icon ( ) next to the Code Coverage Files header section.58

2.

3.

4.F.

10.

11.A.B.C.D.E.

1.2.

3.

4.F.

12.

13.A.B.C.D.E.

1.2.

3.

4.F.

14.

15.A.B.C.D.E.

1.

Browse to the Installed ADI folder > adi > cobol-coverage > PerfcalcApp > November 11 2015 folder.Select all the zip files in the November 11 2015 folder. (Perfcalct1.zip,Perfcalct2.zip, Perfcalct3.zip and Perfcalct4.zip)Click the Open button.

Click the Add button to add this build.The page with the list of all builds appears. Click the Add icon ( ) next to thepage header to add another build.On the Add Build form, fill in the following information.

Build Name: 2015Nov12BuildDate of Build: 12 November 2015Description: November 12, 2015 build for Perfect Calculator Application.Select Modified Files: CLCTPCTB.cbl, PERFCALC.cblCode Coverage Files

Click the Add icon ( ) next to Code Coverage Files header section.Browse to the Installed ADI folder > adi > cobol-coverage > PerfcalcApp > November 13 2015 folder.Select all the zip files in the November 13 2015 folder. (Perfcalct1.zip,Perfcalct2.zip, Perfcalct3.zip, Perfcalct4.zip, Perfcalct5.zip andPerfcalct6.zip)Click the Open button.

Click the Add button to add this build.The page with the list of all builds appears. Click the Add icon ( ) next to thepage header to add another build.On the Add Build form, fill in the following information.

Build Name: 2015Nov13BuildDate of Build: 13 November 2015Description: November 13, 2015 build for Perfect Calculator Application.Select Modified Files: CLCTPCTB.cbl,PERFCALC.cbl.Code Coverage Files:

Click the Add icon ( ) next to the Code Coverage Files header section.Browse to the Installed ADI folder > adi > cobol-coverage > PerfcalcApp > November 13 2015 folder.Select all the zip files in the November 13 2015 folder. (Perfcalct1.zip,Perfcalct2.zip, Perfcalct3.zip, Perfcalct4.zip, Perfcalct5.zip andPerfcalct6.zip)Click the Open button.

Click the Add button to add this build.The page with the list of all builds appears. Click the Add icon ( ) next to thepage header to add another build.On the Add Build form, fill in the following information.

Build Name: 2015Nov17BuildDate of Build: 17 November 2015Description: November 17, 2015 build for Perfect Calculator Application.Select Modified Files: CLCTPCTB.cbl, PERFCALC.cbl.Code Coverage Files:

Click the Add icon ( ) next to the Code Coverage Files header section.

59

2.

3.

4.F.

16.

17.

Browse to the Installed ADI folder > adi > cobol-coverage > PerfcalcApp > November 17 2015 folder.Select all the zip files in the November 17 2015 folder. (Perfcalct1.zip,Perfcalct2.zip, Perfcalct3.zip, Perfcalct4.zip, Perfcalct5.zip andPerfcalct6.zip)Click the Open button.

Click the Add button to add this build.After adding all the builds, you should see 5 builds in the Builds page as below.

Click the Back icon ( ) on the page header to go back to the Data Providerspage. You should see the Perfect Calculator Manual Builds added.

You have now finished setting up of the Perfect Calculator Manual Builds dataprovider. Next you will set up an analysis collection for the Perfect Calculatorapplication. Parent topic:Exercising setting up a Manual Builds for code coverage analysis

60

1.

2.

3.A.B.

C.

D.E.

Setting up an analysis collection This section guides you how to set up an analysis collection for code coverageanalysis of Perfect Calculator application. Complete the following steps to set up an analysis collection for Perfect Calculatorapplication.

Select the Analysis Collection icon ( ) from the left menu to open the AnalysisCollections page.On the Analysis Collections page, click the Add icon ( ) next to the AnalysisCollections header to add an analysis collection. The Add Analysis Collectionform appears. On the Add Analysis Collection form, fill in the following information.

Name: Perfect CalculatorDescription: This is an analysis collection for Perfect CalculatorApplication.Contributor List: Select Tammy as Owner and Trish as Member.Note: Bydefault, the user who is creating an analysis collection will be automaticallyadded as the owner of the analysis collection. Provider: Select Perfect Calculator Manual Builds. The Code Coverage Data Provider Settings appears. For Code CoverageThreshold: slide the left slider to 50% and the right slider to 80%.

61

F.4.

Click the Add button to add this analysis collection.The Welcome page loads. Select the Analysis Collection icon ( ) from the leftmenu to go back to the Analysis Collections page. You should see the Perfect

Calculator added.

You have completed the setup of the Perfect Calculator analysis collection. You arenow ready to analyze code coverage data for Perfect Calculator application. Formore information, see Analyzing code coverage. Parent topic:Exercising setting up a Manual Builds for code coverage analysis

62

---

---

-

Analyzing code coverage This tutorial guides you through how to analyze code coverage results with theApplication Delivery Intelligence. In this tutorial, you as Tammy, the test manager examines the code coverageanalysis reports and dashboard provided in the ADI by performing the followingactivities.

Reviewing the Analysis page to see overall application code coverage statusDeep driving to code coverage of application that having problemComparing code coverage status of current build and previous build to identify theproblem

Prerequisite Before you begin this tutorial, you need to perform the following activities.

Installing and setting up ADISetting up Manual Builds for Code Coverage AnalysisExercising setting up a Manual Builds for code coverage analysis

Reviewing code coverage reports and dashboards This section guides you how to review code coverage reports and dashboards asTammy, the test manager.

Parent topic:Tutorials

63

1.

2.

3.

4.

Reviewing code coverage reports and dashboards This section guides you how to review code coverage reports and dashboards asTammy, the test manager. Complete the following steps to examine the code coverage reports anddashboards.

Navigate your browser tohttps://healthcare.example.com:9443/adi/web/projects/HealthCare4All.Log in with Tammy as user ID and Tammy as password. The Analysis pageloads with the reports for all analysis collections available in the HealthCare4Allproject. For this tutorial, you will see the code coverage report for PerfectCalculator and SAM Application.

Observe that both applications have the Aggregated Code Coverage over 70%but Perfect Calculator is in warning state while SAM Application is in normalstate. The code coverage report is a roll-up percentage of code coverage fromall builds within one analysis collection. ADI allows users to define the codecoverage threshold for an analysis collection to customize based on the qualitylevel that application required. For example in this lab, the code coverage for Perfect Calculator which is lowerthan 80% will be shown in yellow to indicate the warning status and the codecoverage which is lower than 50% will be shown in red to indicate that it is not inacceptable number. For the SAM Application, the Aggregated CodeCoverage which is lower than 70% will be shown in yellow. This threshold values can be set when you create analysis collection. SeeSetting up Manual Builds for Code Coverage Analysis how to set up thethreshold values. Select the Perfect Calculator card to deep drive to code coverage reports ofPerfect Calculator analysis collection.

64

5.

6.

7.

The build analysis view is loaded. Currently there is only one build, PerfectCalculator Manual Build for the Perfect Calculator analysis collection. Thereports showing are the code coverage reports of the latest build of PerfectCalculator Manual Build. The first report shows that the Perfect Calculator has 75% Code Coveragewhich is in the warning area. Looking at the next report, the Code CoveragePercentage Trend is starting to go down from Nov 12. On the next report, thenumber of total executable lines in the next report is going up from 64 to 76 on11/13/2015 and then to 87 on 11/17/2015. However, the executable lines hitremains quite stable. There seems to be some code coverage issue with the last2 builds of the Perfect Calculator Manual Build. The Coverage Changed vs Unchanged Code report indicates that there isfifteen executable lines changed within a build and none of them have beentested. This means the changed code has not been tested properly.

Click on Perfect Calculator Manual Build: 2015Nov17Build card to drill downfurther.The files analysis view appears with the code coverage detail for all files within2015Nov17Build. On the top row of this view, you can see the summary of thebuild: Date of Build, Last Coverage Date Update, the percentage of CodeCoverage and the percentage of Exec. Lines Changes. The Exec. Lines Changes is percent executable lines being changed with in abuild calculated from number of total executable lines within a build and numberof lines updated within a build. The executable lines represent number ofexecutable lines for a source file or program. The executable line is defined asthe line of code that the compiler marks as executable. For COBOL, theexecutable line may not directly correspond to the exact source line, as COBOL

65

8.

9.

10.

11.

12.

is not debugged using source but rather the expanded source.

Below the top row, you can view the detail of file level code coverage. For eachfile, you can see name of the file, the code coverage percentage of the file, thepercentage of code coverage being changed, the number of executable lineschanged, the Change Percentage, the number of Historical Tests hitting the file,the number of Minimal Tests, and warning status. You can notice thatCLCTPCTB.cbl status is in warning and the percentage of code coveragechange goes down by 18%.Click on the Expand icon ( ) to expand more detail analysis of CLCTPCTB.cbl.The expand section shows number of total executable lines, number ofexecutable line hit, executable lines added, updated and deleted, list of historicaltests to run and list of minimal tests to run. You can notice that 11 executablelines are added and 4 lines are updated. This indicates that may be the addedlines did not get tested causing the code coverage goes down by 18%.

Click on the CLCTPCTB.cbl. The flow point analysis view appears. Similar tothe file analysis view, this view shows the code coverage detail for all flow pointwithin a file. You can notice that COMBINE-AND-WRITE has 15 executablelines changed from 16 executable lines but the code coverage shows 0%.Click on the Expand icon ( ) in font of the COMBINE-AND-WRITE name. Youcan see that there is 11 executable lines added and 4 lines updated but none ofthe executable lines are tested. This confirms your observation in the previous

step. Click the Back icon ( ) in font of the CLCTPCTB.cbl to go back to the

2015Nov17Build page. 66

13.

14.

15.

16.

Click the dropdown list next to the name of the build and select2015Nov13Build to go to the build on Nov 13, 2015.

On the page for 2015Nov13Build, you can observe that CLCTPCTB.cbl statusis also in warning for this build and the percentage of code coverage changegoes down by 36%. 10 executable lines are added. There is still an issue withcode coverage for this build as well.

Click the dropdown list next to the name of the build and select2015Nov12Build to go to build on Nov 12, 2015.On the page for 2015Nov12Build, the code coverage for overall build indicates100% code coverage. This build has been fully tested. The issues seem to bearisen starting in 2015Nov13Build. Tammy wants to compare the builds to getthe better understanding of what has changed.

67

17.18.

19.

20.21.

Click on the Option Menu icon ( ) on the right to open the Option Menu panel.Select the Compare Builds option.

By default 2015Nov12Build is preselected, select 2015Nov13Build and2015Nov17Build. Click Compare button to compare three builds.

Click on the Option Menu icon ( ) again to close the Option Menu Panel.On the Compare Build view, you can compare the detail of three builds in oneview. This view helps confirm that your observation earlier that fileCLCTPCTB.cbl has brought the code coverage percentage of the entire builddown from 100% to 86% and 75%. The cause could be that the executable linesthat are added to the CLCTPCTB.clb in the past 2 builds have not properlytested.

68

22.

23.24.

At this point, you can see how Tammy as a test manager use ADI to review thecode coverage reports and use the reports to analyze the potential issues withtesting. This would help the testing team to guarantee the level of testing. You can also view the code coverage by test file. Click on the Option Menu icon( ) to open the Option Menu Panel. Select the View by Tests option.

Click on the Option Menu icon ( ) again to close the Option Menu Panel.On the Test view, you can view the effectiveness of each test and files that aretested.

69

25.

26.

27.

Switch the build to 2015Nov13Build by clicking the build list next to2015Nov12Build header.You can notice that on 2015Nov13Build, PERFECT3, PERFECT4, andPERFECT1 are dropped significantly. Expand all three files. You can see that allthree files test CLCTPCTB.cbl file meaning we have lines added to the file butthere is no tests covered the lines added. Also there is no new test added to thisbuild. This confirms your observation previously that the reason the percentcode coverage dropped from previous build because there is no test coveringthe newly added lines.

Tammy is now satisfied with her investigation on code coverage issue forPerfect Calculator application. She communicates the results to her team andasked Trish to update the tests to cover the executable lines that are added. Shealso suggested her team to use ADI to always check the code coverage reports

70

---

--

to ensure that the application is fully tested. Now you have explored how you can use the test analysis results of the latest buildto investigate the testing issues of your build. Typically you can use theseinformation to perform the following analysis.

Determine if the coverage has improved from the previous builds.Determine if the changed files were indeed covered during the testing.Compare the results of the current build with one or more older builds to seedifferences between coverage results of these builds.Determine how much the set of files that have actually changed from build to build.Review the trends of changes and coverage over time to determine the quality ofthe tests performed.

Parent topic:Analyzing code coverage

71

-

1.

2.

3.

4.

5.

6.

Generating sample data In this tutorial, you perform the role of ADI admin, Alvin, to generate the sample forthe end-to-end root cause analysis tutorial using data generation functionality. The data generation functionality of ADI is useful when you do not have access tothe instance of the OMEGAMON for CICS or Application Discovery. You can usethe sample data that ADI generates to see how the data being analyzed. After thedata is generated, you can create and set up an analysis collection for users to viewthe analysis results.Note: To make the sample data show effectively in the end-to-end root cause analysis tutorial which you will perform later, you need to generateOMEGAMON for CICS data and Application Discovery data continuously. Prerequisite Before you begin this tutorial, you need to perform the following activities.

Installing and setting up ADI Complete the following steps to generate sample data.

Navigate your browser to ADI administration page athttps://healthcare.example.com:9443/adi/admin.Log in as Alvin, the ADI administrator, with AdiAdmin as user ID and AdiAdminas password. The ADI administration page appears. On the top menu of ADI administration page, select ADI Data Generation.

The ADI Data Generation page loads with choices of data to be generated:OMEGAMON for CICS or Application Discovery. Select OMEGAMON forCICS card to generate system performance sample data for OMEGAMON forCICS.Note: You need to be an administrator for Jazz Team Server and ADI togenerate the sample data.

The Data Generation Settings form appears. Leave all the fields as defaultvalues. For more information, see Generating sample data for evaluation.Click Generate button. The message indicating that the data generation will takesome time to generate data appears.

72

7.

8.

9.

10.

11.

Select the Application Discovery card to generate system performance sampledata for IBM Application Discovery.

The Data Generation Settings form appears. Leave all the fields as defaultvalues. For more information, see Generating sample data for evaluation.Click Generate button. The message indicating that the data generation will takesome time to generate data appears.

Navigate to the ADI page to check that the data is generated successfully.Expand the Home menu and select HealthCare4All under IBM Application

Delivery Intelligence (ADI). The browser navigates to ADI application and the Analysis view appears. Youcan see that there is no data to be analyzed yet because you have not yetdefined any analysis collections. Typically to add a new analysis collection, you start with creating a connection toa server storing data to be analyzed and then specifying data source as a dataprovider. One analysis collection can have multiple data providers. However forthis tutorial, you use the sample data for evaluation instead of connecting to theOMEGAMON for CICS server. So you don’t need to create any connections ordata providers. Select the Connections icon ( ) from the left menu to open the Connectionspage. You can see that there are two generated connections available on this

page.

73

12.

13.

14.

15.

16.

17.---

-

Hover over either one of the connections and select Edit icon ( ) to view

connection information. After viewing the information, click Cancel button and do not update anything onthe Edit Connection form.

Select the Providers icon ( ) from the left menu to open the Data Providerspage. Similar to connections, you can see two data providers created from ADIdata generation: Generated OMEGAMON Provider and GeneratedApplication Discovery Provider. You can see that there are two connections and two data providers generated.Next you will create an analysis collection for zMobile Health Application andassociate it with data providers for analysis. Select the Analysis Collections icon ( ) from the left menu to open theAnalysis Collections page. The Analysis Collections page loads without anyanalysis collections just yet.

Click the Add icon ( ) next to the Analysis Collections header to add ananalysis collection. The Add Analysis Collections form appears.Fill in the following information to create a new analysis collection.

Name: zMobile Health ApplicationDescription: This is an analysis collection for zMobile Health application..Contributors: Select Marco as an owner and Trish as a member.Note: Bydefault the user who is creating this analysis collection will be assigned asowner. Providers: Select Generated OMEGAMON Provider and GeneratedApplication Discovery Provider. The data provider settings forms for eachproviders appear.

74

--

--

----

-

Fill in the following information in the data provider settings forms.

OMEGAMON for CICS Data Provider SettingsSelect HTRANS service class.Timeframe to view dashboards's metrics: leave as default value which is

Last Day.

Application Discovery Data provider SettingsSelect the zMobile project.Unreachable Code Threshold: Leave as default value.Maintainability Index Threshold: Move the lower slider to 50% and leavethe upper slider at 85%.Cyclomatic Complexity Threshold: Leave as default value.

75

-18.

Click Add button to create this analysis collection.

The Welcome page appears. Select the Analysis Collections icon ( ) from theleft menu to go back to the Analysis Collections page. You can now see thatzMobile Health Application is created.

You are now ready to perform the end-to-end analysis of performance issues. Thenext tutorial you play the role as Marco, a development manager, to analyze thepotential cause of performance issues for this zMobile Health application. Parent topic:Tutorials

76

1.

2.3.

4.

-

-

End-to-end system performance root cause analysis In this tutorial, you play the role of Marco, the development lead of the zMobileHealth Application, to perform root cause analysis of a performance defect reportedfrom Trish, a tester. Trish is a test lead in testing the response time of the Inquire Patient feature of thezMobile Health Application. During the testing Trish found that in the latestdevelopment build, the response time of the Inquire Patient feature increased to 2minutes from less than a second in the previous build. She reported it to you, thedevelopment lead Marco. And you as Marco investigate the issues by consultingdashboards and reports in ADI. You as Marco need to complete the following steps to perform the end-to-endsystem performance root cause analysis.

Navigate your browser tohttps://healthcare.example.com:9443/adi/web/projects/HealthCare4All. Log in to ADI with Marco as user ID and Marco as password.The Welcome page loads. Select the Development role and click Continue.The Analysis page appears. Note: ADI requires you to select your role beforeyou can start viewing dashboards and reports. The role you select is used toorganize the showing dashboards and reports. This is to help users see thedashboards and reports that in their focus area first. You can see the dashboard that summarizes the overall status of zMobile HealthApplication. The dashboard contains reports from 2 data providers whichassociated with this analysis collection.

An OMEGAMON for CICS data provider that monitors performance of thezMobile Health Application CICS TransactionsAn Application Discovery data provider that collects Static analysis data aboutTransactions and Programs in the zMobile Health Application

With reports from multiple providers in one analysis collection, you can correlatedifferent data from different sources.

77

5.

You as Marco right away notice the problem that Trish reported. The averageresponse time of zMobile Health Application is almost 7 second. It is higher thanthe service level agreement for your company. Click on the zMobile Health Applications name. The detail analysis of programand transactions within zMobile project displays along with the performancereports of HTRANS. HTRANS is a service class in OMEGAMON for CICS data provider. Serviceclass is a concept that OMEGAMON uses to allow grouping of relatedtransactions together. If no service class is defined, OMEGAMON for CICSwould define a default service class.

78

6.

7.

Scroll down to HTRANS (Generated OMEGAMON for CICS data provider :HTRANS) to start your investigation on the performance issue that Trishreported. Besides the average response time that is in the red zone, you noticethat on the Transactions with Performance and Reliability Issues table,HCP1 transaction that is run by the *Inquire Patient* feature is flagged asexceeding the goal response time threshold by more than 400%. Averageexecution count of HCP1 is also much higher than the other transactions. Thenyou think that this transaction probably causes the application to slow down.Note: Goal response time threshold is the setting in OMEGAMON for CICS toindicate the severity of response time that exceeds the standard service levelagreement the company requires. The different warning icons on theTransactions with Performance and Reliability Issues table indicatesdifferent levels of severity. For example, red warning icon indicates that theresponse time exceeds threshold by more than 400% or transparent red warningicon indicates that the response time exceeds by 400%. Click on the HCP1 transaction on the Transactions with Performance andReliability Issues table to view detail transaction analysis. You now see thehistory of the average response time comparing to Average DB2 and File I/Owait time of response time, average CPU time, and execution count. On the header of the report, the maximum number of the execution count, CPUtime, and response time for a given timeframe display on this view. From the chart, you notice that the average response time is constantly high forthe past 3 days from 2 sec. to 26 sec. The same pattern occurs to DB2 waittime. DB2 wait time goes up from about 30% to over 70% which is higher thanthe suggested level 50% that is indicated by the red line on the Average DB2and File I/O Wait Time of Response Time. You notice that the execution is always at about almost 200 which means thistransaction has been executed frequently. You suspect that there probably aresome changes to the program within this transaction 3 days ago.

79

8.

9.

Hover over the chart on the area where the response time exceeds the thresholdand the average DB2 time is high. You can see response time value and percentDB2 wait time value.

Click on the area where a warning icon shows on top.Note: A warning iconindicates the maximum point of the response time. Performance data dialoguebox appears. It shows the performance data at the point you selected.

80

10.11.

12.

13.

Click OK to do further analysis.The Transaction Composition view loads. Transaction Composition analysis isthe analysis of key program and transaction metrics collected from ApplicationDiscovery. This view shows Transaction Composition graph which is theconnected graph of all artifacts (transactions, programs, and database tables)calling in a transaction. The arrow direction represents the calling direction. Younotice the warning icons on top of the artifacts. The blue warning icon indicatesthat there could be some changes to the artifacts because there is change toartifact metrics. The red warning icon indicates that the artifact is risky to modify.The Transaction Risk Areas dialog box on top of the chart explains themeaning of blue and red icons with the threshold setting for key metrics.

Click X on top right of the Transaction Risk Areas dialog to close the dialogbox.You can now see the full view of Transaction Composition graph. Notice that thegraph is expandable. This is because when you navigate to the transactioncomposition analysis from clicking at the areas where there is performanceissue, ADI is analyzing the cause of the issues and showing only the potentialartifacts that could cause issues. For example, in this case, ADI analyzed thatthe issues could be due to DB2 wait time. It displays all the artifacts thatconnected to DB table.

81

14.

15.

16.

17.18.

19.

Click the Risk Areas icon ( ) on the upper right the view. The TransactionRisk Areas dialog displays with the warning icons on the TransactionComposition graph. Observe the blue warning icon on HCIPDB01. This means that there could besome changes made to HCIPDB01 in the past week.Close the Transaction Risk Areas dialog and click on HCIPDB01 box. The keymetrics collected from Application Discovery for this artifact displayed. You cansee that the Maintainability Index is in red area but it is not your concern at this

point. Click X on top of the artifact information window to close the dialog window.On the top menu, you as Marco change the Date back 4 days to navigate to thetransaction composition graph four days ago and the metrics value collected

before the performance issues occur. The Transaction Composition graph loads. Click on HCIPDB01 box. You noticethat the number of active statements was changed. There is one line of ActiveStatements added to HCIPDB01.

Now you as Marco conclude that the HCIPDB01 should be the area of concern.You discuss with Jane, the developer. You two investigate further into the codeand find that there is extra Join which contributes to the excessive wait time.

82

20.

21.

-

-

-

22.

Before making modification, you and Jane go back to ADI. On the TransactionComposition graph view, you change the view to show the latest snapshot dateby selecting the last date on the Date drop down list on top of the view.

Click the Table icon ( ) to show the Transaction Composition table.

The Transaction Composition table shows the list of all program artifacts within atransaction. The table is sorted based on the analysis of high risk to modify. Therank of risk to modify is calculated based on combination of the following criteria:

Whether the artifact is in risk areas: Risk areas are based on the thresholdssetting.Whether the artifact is an outlier: Outlier artifacts are analyzed based on theoutlier detection algorithm leveraging mahalanobis distance of each artifact tothe center of the distribution. Artifacts with large mahalanobis distances meanthat they are outlier or abnormal because they are very far away frommajorities.Metrics values sorting: Given the same risk area and outlier status, artifacts arefinally sorted by the values of Maintainability Index, Unreachable Code, andCyclomatic Complexity.

On the Transaction Composition table, you and Jane notice that HCIPDB01 is atmedium risk to modify. Another program HCAZERRS is at high risk. Hencemaking another changes would not make much impact to the zMobile HealthApplication.

83

23.

24.

You can click on the Risk Areas icon ( ) to update the threshold settings andsee the effect of the changes. For example, move the lower slider ofMaintainability Index threshold to 40%. You now see that the warning icons ofthe programs with Maintainability Index higher than 40% are changed from redwarning icons to transparent red warning icons.

Click the Graph View icon ( ) on the top right menu to go back to theTransaction Composition graph view.Click on the box with 6 Artifacts text on Transaction Composition graph view toexpand the graph to show all artifacts.

You two notice that HCIPDB01 has dependency with HCAZERRS which hashigh risk to modify. After fixing the SQL problem, Jane also tests both modulescarefully to make sure it would not cause any regressions. In the next build, Trish reports that the problem with the “Inquire Patient” featureis fixed and it again takes only 2 seconds to respond.

You have seen how you can correlate performance data from OMEGAMON forCICS and static analysis data from Application Discovery to perform the root cause

84

analysis of the performance issues. ADI facilities you to identify the potentialprograms that cause the issues without going through the entire artifacts withintransactions. With Application Discovery data, it also recommends the Risk Areaswhere you need to take extra careful when you modify them. You can see thedependency of artifacts to ensure that there would be no regressions in the futurebuilds. Parent topic:Tutorials

85

-

-

-

-

-

-

-

Installation and setup You can install and set up ADI by using web-based express setup, by using web-based custom setup, or by using repotools command. You can also install ADI intoan existing IBM® Rational® Collaborative Lifecycle Management (CLM) solution. Ifyou use a previous release of ADI and want to install a new version, you canmigrate all the data from the old version to the new one.

Hardware and software requirements Before installation, verify that your hardware and software meets the minimumrequirements for installing and using ADI application.Security considerations You can take actions to ensure your secure installation, customize securitysettings, and set up user access controls. You can also ensure that you knowabout any security limitations that you might encounter with this application.Installing ADI by using web-based express setup The express setup is a simplified version of wizard setup. When you install and setup ADI by using this express setup, you use the Derby database by default andyou're not allowed to use any other databases. It is recommended that you use thisexpress setup in a demonstration or product trial but not for production.Installing ADI by using web-based custom setup When you install ADI by using web-based custom setup, you can set up themajority of the installation options. If you want to use DB2® database, you shoulduse this method.Installing ADI by using the repotools command When you install and set up the ADI application by using the repotools command,it sets up the Derby database by default. In this case, you cannot use any otherdata bases. You can use a repotools command to play back setup options with apre-packed response file which enables you to set up everything from thecommand shell. The information that you provide by using repotools command isthe same as for the web-based express setup.Installing ADI into an existing CLM installation You can find a roadmap for co-installing ADI with an existing IBM RationalCollaborative Lifecycle Management (CLM) solution, such as an existing Jazz™Team Server (JTS) and Rational Team Concert (RTC).Migrating from a previous release If you use a previous release of ADI and want to migrate all of its data, you mustfollow the migration steps described in this section instead of the other installationscenarios.

Parent topic:IBM Application Delivery Intelligence 5.0.2

86

----

-

---

---

-

----

-

-

Hardware and software requirements Before installation, verify that your hardware and software meets the minimumrequirements for installing and using ADI application. A 64-bit operating system (Windows or Linux) and a minimum of 8 GB servermemory provide the best environment for running the Jazz™ Team Server (JTS). A complete list of system requirement is as follows. Operating systems

Red Hat Enterprise Linux (RHEL) Server 6, x86-64Red Hat Enterprise Linux (RHEL) Server 7, x86-64Windows Server 2008 R2 Standard / Enterprise Edition, x86-64Windows Server 2012 R2 Standard / Datacenter Edition, x86-64

Application server

Embedded WebSphere® Application Server (Liberty Profile 8.5.5) Database

Embedded Apache Derby 10.10 (limited to 10 end users)DB2® Advanced Enterprise Server Edition, 10.5 and future fix packsDB2 Advanced Workgroup Server Edition, 10.5 and future fix packs

Browser

Microsoft Internet Explorer, 11 and future fix packsMozilla Firefox ESR, 52 and future fix packsGoogle Chrome, 58 or higher version

For a complete list of system requirements for any particular versions, see JTSonline help or the System requirements section on the Jazz.net Deployment wiki.For ADI installation requirements on the Linux system, see Planing to install onLinux systems and ensure that your hardware and software meets all therequirements. A list of software versions supported by ADI is as follows. Code coverage analysis

IBM® Rational® Developer for z Systems (RDz) 9.5.1 and IBM Developer for zSystems (IDz) 14.0.0Rational Team Concert™ (RTC) 6.0 and higherCOBOL 4.x and higherPL/I 4.2 and higherIBM Debug Tool for z/OS® 13.1 and higher

OMEGAMON for CICS data provider

IBM Tivoli® OMEGAMON® XE for CICS® on z/OS 5.3.0Note: It is required toconfigure ITM TEPS REST API in OMEGAMON for CICS to be data provider forADI. For more information, see OMEGAMON for CICS Knowledge Center.

Application Discovery data provider

IBM Application Discovery 5.0

87

Parent topic:Installation and setup

88

-

-

-

Security considerations You can take actions to ensure your secure installation, customize security settings,and set up user access controls. You can also ensure that you know about anysecurity limitations that you might encounter with this application. Enabling security during the installation process Application Delivery Intelligence only support HTTPS connection. You shouldalways use Secure Sockets Layer (SSL) HTTPS connections to browse to theapplication from browser. SSL encrypts all data that is passed over an HTTPSconnection. During installation, ADI security is enabled by default and all security isprovided through the Jazz Team Server. Enabling secure communication between multipleapplications ADI supports HTTP/HTTPS connections for all data provider connections. ADI is built on the Jazz Team Server and its users authentication and usersmanagement mechanism is provided via the Jazz Team Server. The Jazz TeamServer manages an LDAP connection . For more information, see Configure anLDAP or an LDAP/SDBM connection with the WebSphere Liberty server. Ports, protocols, and services The default port for ADI is 9443. If you do not want to use the default port numbers,see Changing the port numbers for the application server. Customizing your security settings After the installation, you need to configure a certificate authority that is signed orself-signed certificate for your application server. You need to send instructions toyour end users about how to import this certificate to avoid warnings of errors intheir browsers.

For instruction about configuring the certificates, see this topic in the Jazz onlinehelp: Configuring security certificates.For instructions about configuring the certificate, you can follow the sameinstructions as described in Configuring security certificates for Report Builderservers.For instructions about how to configure a browser for such self-signed certificates,follow the instructions in Importing certificates and configuring browsers for ReportBuilder reports.

You're required to specify an administrative user ID during ADI installation andsetup. You can use the Jazz Team Server administration pages to change user IDsand passwords. Setting up user roles and access ADI requires an user ID and password to access ADI services. For more informationabout creating and managing user accounts, see Creating and managing users. With the administrator permissions, you can manage users by using the Jazz TeamServer administration or ADI administration pages. When a project area is created,users can be designated as members of that project and be assigned rolepermissions. Only members of project area can have access to that project area.

89

The permission to perform the operations within the project area is controlled by therole permissions assigned to the users. For more information about permissions foreach role, see Assigning role-based permissions to ADI users. Privacy policy considerations This software offering does not use cookies or other technologies to collectpersonally identifiable information. Parent topic:Installation and setup

90

-

-

-

-

-

Installing ADI by using web-based express setup The express setup is a simplified version of wizard setup. When you install and setup ADI by using this express setup, you use the Derby database by default andyou're not allowed to use any other databases. It is recommended that you use thisexpress setup in a demonstration or product trial but not for production. For more information about the express setup, see Jazz online help.

Information required before the installation You need to get the necessary information before you install ADI application byusing the web-based express setup.Starting up the server To install ADI by using web-based express setup, you need to start up the serverfirst. Unzip the ADI installer package and run commands for the start. Configuring the server After you start the server, you need to configure the public URI and set up youradministrative user. This topic describes how you configure the server when youinstall ADI by using web-based express setup.Setting up the ADI application This topic describes how you set up the ADI after you install ADI by using theweb-based express setup.Shutting down the server After you finish the installation and setup, you can shut down the server.

Parent topic:Installation and setup

91

--

--

Information required before the installation You need to get the necessary information before you install ADI application byusing the web-based express setup. The following information is required before the installation:

A fully qualified host nameA public URI

Important: A fully qualified host name is the host name along with the DNS domainreference of the machine on which the Jazz™ Team Server (JTS) is installed.

An example of a fully qualified host name is clmwb.example.com.Examples of an invalidfully qualified host name include localhost and an IPaddress.

For more information about how to plan the server URI, see Planning your URIs Parent topic:Installing ADI by using web-based express setup

92

1.2.

3.

Starting up the server To install ADI by using web-based express setup, you need to start up the serverfirst. Unzip the ADI installer package and run commands for the start. Note: You need to disable the pop-up blocker and add security exceptions beforeyou start the installation. You need to take the following steps to start up the server.

Unzip the ADI installer package.Open terminal/command prompt and navigate to the unzipped-adi-installer/adi/server directory by running the following command.cd /unzipped-adi-installer/adi/server In the current directory, start the server by running the following command.server.startup

Parent topic:Installing ADI by using web-based express setup

93

1.

2.

Configuring the server After you start the server, you need to configure the public URI and set up youradministrative user. This topic describes how you configure the server when youinstall ADI by using web-based express setup. To configure the server, take the following steps:

Open a web browser, go to https://fully qualified hostname:9443/jts/setup, and logon using ADMIN as user ID and ADMIN as password.

On the welcome page, select Express Setup and click Next.

94

3.-

--

-

On the Configure Public URI page:

Provide a public URI root that is of the form https://fully qualified hostname:9443/jts/. For example, you can providehttps://insurance.example.com:9443/jts/ . Note: The repository might have analternative host name through which it can be publicly accessed. When thisproperty is set, this URL is used as the basis of absolute URIs that are madeavailable outside of the client and server. When the URI is set, it cannot bemodified. Check the box to confirm that when the public URI is set it cannot be modified.Click Test Connection to test the connection to the server. If the test issuccessful, click Next.For more information about URIs, see Planning URIs.

95

4.-

-

On the Create Administrative User page:

Provide information for the administrative user. This is an administrative usersfor both JTS and ADI application. The ADMIN user account will be automaticallydisabled after this step. You are required to use this administrative user forfuture setup. For more information, see User management. Click Next.

96

5.

6.

On the Setup Progress page, wait until the wizard finishes configuring theinstallation, and click Next.

On the Assign Licenses page, click Activate Trial and accept the terms of thelicense. After you activate the trial, a license will be automatically assigned to the

97

7.

administrator you created previously.

Click the Finish button to access the Jazz Team Server Administration pagewhere you can perform administrative tasks such as managing the server, users,and licenses. For more information, see Administering Rational solution forCollaborative Lifecycle Management servers.

Parent topic:Installing ADI by using web-based express setup

98

1.

2.

3.

4.

A.

B.C.

D.

E.F.

5.

6.7.

Setting up the ADI application This topic describes how you set up the ADI after you install ADI by using the web-based express setup. Before you begin, ensure that the pop-up blocker is disabled for https://fully qualifiedhostname:9443/adi/web page. To set up the ADI application, take the following steps:

Browse to https://fully qualified hostname:9443/adi/web to open the ADIapplication.Log on with the administrative user name and password that you created duringthe server configuration. ADI application appears with the All projects page. For the first time user, thereis no project area. Click the project area management link to set up a project

area. The application navigates to the Application Administration - IBM ApplicationDelivery Intelligence (ADI) page. Use this page to create a project area.

Click the Create Project Area link on the top right corner.

Provide a Name, Summary, and Description for the project area.Select IBM Application Delivery Intelligence Application Default Processas process if it is not yet selected.Assign or create users as members of the project area. For more information,see Creating and managing users. Assign or create users as administrators for the project area.Click Save next to the project area name on the top to create the project area.

Note: After you save the project area, a message appears warning you about themembers added without roles. You can ignore this warning message becausecurrently no role to members is available. On the upper left corner of window, click the Home icon to open the drop-downmenu and select IBM Application Delivery Intelligence (ADI) . My Projects andAll Projects appear.Click All projects. The project area you previously created appears. Click the project area to open it in your browser and then bookmark the page ofyour project area as the ADI home page.

Parent topic:Installing ADI by using web-based express setup

99

1.

2.

Shutting down the server After you finish the installation and setup, you can shut down the server. To shut down the server, complete the following steps:

Open terminal/command prompt and navigate to the unzipped-adi-installer/adi/server directory by running the following command:cd /unzipped-adi-installer/adi/server In the current directory, shut down the server by running the following command:server.shutdown

Parent topic:Installing ADI by using web-based express setup

100

-

-

-

-

-

-

Installing ADI by using web-based custom setup When you install ADI by using web-based custom setup, you can set up the majorityof the installation options. If you want to use DB2® database, you should use thismethod. The custom setup is recommended for production environments. The wizard guidesyou through setting up your database, configuring email settings, configuring theuser registry, and registering applications. The wizard detects and prompts you toset up the applications you installed. For more information about the custom setup method, see Jazz online help.

Information required before the installation You need to get the necessary information before you install ADI by using web-based custom setup.Creating databases You need to create databases before you set up application. Starting up the server To install ADI by using web-based custom setup, you need to start up the serverfirst. Unzip the ADI installer package and run commands for the start. Configuring the server After you start the server, you need to configure the public URI and set up youradministrative user. This topic describes how you configure the server when youinstall ADI by using web-based custom setup.Setting up ADI application This topic describes how you set up the IBM Application Delivery Intelligence(ADI) application by using web-based custom setup.Shutting down the server After you finish the installation and setup, you can shut down the server.

Parent topic:Installation and setup

101

--

--

Information required before the installation You need to get the necessary information before you install ADI by using web-based custom setup. The following information is required before the installation:

A fully qualified host nameA public URI

Important: A fully qualified host name is the host name along with the DNS domainreference of the machine on which the Jazz™ Team Server is installed.

An example of a fully qualified host name is clmwb.example.com.Examples of an invalid fully qualified host name include localhost and an IPaddress.

For more information about how to plan the server URI, see Planning your URIs Parent topic:Installing ADI by using web-based custom setup

102

Creating databases You need to create databases before you set up application. If you are running against a database other than the default Derby database, whichis included in the installation, you need to create a database before you set up theapplication. Currently, ADI supports only DB2® database. For more informationabout setting up the database, see Jazz online help. To set up the ADI application, you need to create three databases for Jazz™ TeamServer, ADI, and Data Warehouse (DW). Use the parameters that are provided inSetting up the database for Jazz Team Server and Data Warehouse. Use the sameparameter values that are used for Jazz Team Server when you create database forthe ADI application. Derby database By default, the builds use the Derby database included in the installation, so you donot need to create any database. This option is only available when you install ADIby using the web-based express setup installation. DB2 database Review Prerequisites and make sure that your DB2 database meets therequirements before you continue. Before you create the DB2 databases for ADI, you must set theDB2_COMPATIBILITY_VECTOR registry variable with the following commands.Otherwise, ADI will not be able to perform paged queries correctly and will showerror messages in various UI pages. db2set DB2_COMPATIBILITY_VECTOR=MYSdb2stop

db2start Then, you can create the required databases by using the following DB2commands: db2 create database JTS using codeset UTF-8 territory en PAGESIZE 16384db2 create database ADI using codeset UTF-8 territory en PAGESIZE 16384

db2 create database DW using codeset UTF-8 territory en PAGESIZE 16384 Optional: Data Warehouse that is used for raw data storage can be large. If you planto perform massive DB2 update transactions on the DW, it is recommended toincrease the default sizes of DW transaction logs. You can use the followingcommands to increase the primary and secondary log sizes.db2 get db cfg for DWdb2 update db cfg for DW using LOGPRIMARY 64

db2 update db cfg for DW using LOGSECOND 192 Note: The total number of primary logs plus secondary logs cannot exceed 256. It isalso recommended to set larger secondary log sizes since they are constantlycleared by DB2. For more information about DB2 installation, see IBM® DB2 10.5 for Linux, Unix andWindows documentation. Parent topic:Installing ADI by using web-based custom setup

103

104

1.2.

3.

Starting up the server To install ADI by using web-based custom setup, you need to start up the serverfirst. Unzip the ADI installer package and run commands for the start. You need to take the following steps to start up the server.

Unzip the ADI installer package.Open terminal/command prompt and navigate to the unzipped-adi-installer/adi/server directory by running the following command:cd /unzipped-adi-installer/adi/server In the current directory, start the server by running the following command:server.startup

Parent topic:Installing ADI by using web-based custom setup

105

1.

2.

Configuring the server After you start the server, you need to configure the public URI and set up youradministrative user. This topic describes how you configure the server when youinstall ADI by using web-based custom setup. To configure the server, take the following steps:

Open a web browser, go to https://localhost:9443/jts/setup, and log on usingADMIN as user ID and ADMIN as password.

On the welcome page, select the Custom Setup option to customize the setup,and click Next.

106

3.

4.A.

B.C.

On the Introduction page, click Next to get started with the setup wizard.

On the Configure Public URI page:

Provide a Public URI in the format of https://fully qualified hostname:9443/jts/. For example, https://example.com:9443/jts/.Check to confirm that when the Public URI is set it cannot be modified.Click Test Connection to test the connection to the server. If the test issuccessful, click Next.

Note: For more information about URIs, see Planning URIs.

107

5.

A.

B.1.

2.

C.

D.

On the Configure Database page, provide information to set up a connection tothe Jazz™ Team Server database.

Select the database vendor and connection type. ADI currently supports onlyDB2® as a database vendor and JDBC as a connection type.Configure the database connection properties.

Insert the password of the JDBC database, that is, the password of yourDB2 database.Provide the JDBC location in the following format.//server where your DB2 isinstalled:50000/JTS:user=Your DB2 user;password={password};

Click the Test Connection. You receive a message that the database existsbut is not configured to contain Jazz.Click the Create Tables, and wait several minutes for the commandprocessing. When the processing is complete, click Next.

108

6.

7.

On the Enable E-mail Notification page, disable email notifications and clickNext.Note: There is no email notification capabilities in the current version ofADI.

On the Register Applications page, the wizard detects the applications thatwere installed along with the Jazz Team Server. When the wizard detects theapplication, click Register Applications, and then click Next.

109

8.-

--

9.

-

--

On the Create Administrative User page:

Choose one of the options for your user registry. Jazz Team Server relies on auser registry to provide basic information about users and groups. For moreinformation, see User management. Currently, ADI supports only IBM®WebSphere® Application Server Liberty Core. You can manage WebSphere®Liberty server users by using the default basic user registry or LightweightDirectory Access Protocol (LDAP). If you need more information to create anLDAP connection, refer to this guide.

Click Activate Trial and accept the terms of the license.Click Next.

On the Configure Data Warehouse page, provide information to set up aconnection to the Date Warehouse database. If you use Derby database, you donot need to change the default values, and you are not prompted to createdatabase tables.

Select the database vendor and connection type. ADI currently supports onlyDB2 as a database vendor and JDBC as a connection type.Insert the password of your DB2 database.Provide the JDBC location in the following format.//server where your DB2 is installed:50000/DW:user=Your DB2 user;password={password};

110

-

-

10.

-

--

Click Test Connection. You receive a message that the database exists but it'snot configured to contain the data warehouse.Click the Create Tables, and wait several minutes for the commandprocessing. When the processing is complete, click Next.

On the Configure Data Warehouse page, provide information to set up aconnection to the ADI Database. If you uses the Derby database, you do notneed to change the default values, and you are not prompted to create databasetables.

Select the database vendor and connection type. ADI currently supports onlyDB2 as a database vendor and JDBC as a connection type.Insert the password of your DB2 database.Provide the JDBC location in the following format.//server where your DB2 is installed:50000/ADI:user=Your DB2 user;password={password};

111

-

-

--

11.

---

12.

-13.

Click Test Connection. You receive a message that the database exists, but itis not configured to contain Jazz.Click Create Tables, and wait several minutes for the command to finish. Whenthe command finishes, click Next.On the Finalize Application page, click Finalize Application Setup. When it finishes, click Next.

On the Configure Data Warehouse page, the wizard remembers theconfiguration.

Provide the DB2 password that you use for the DW database.Click Test Connection.Ignore the warning that you receive and click Next.

On the Finalize Lifecycle Project Administration Setup page, click FinalizeApplication Setup.

When it finishes, click Next.On the Summary page, view the summary of all your configurations. ClickFinish to access the Jazz Team Server Administration page where you canperform administration tasks such as managing the server, users, and licenses.For more information, see Administering Rational solution for CollaborativeLifecycle Management servers.

Parent topic:Installing ADI by using web-based custom setup

112

1.

2.

3.

4.

A.

B.C.

D.

E.F.

5.

6.7.

Setting up ADI application This topic describes how you set up the IBM Application Delivery Intelligence (ADI)application by using web-based custom setup. Before you begin, ensure that the pop-up blocker is disabled for https://fully qualifiedhostname:9443/adi/web page. To set up ADI application, take the following steps:

Browse to https://fully qualified hostname:9443/adi/web to open the ADIapplication.Log on with the administrative user name and password that you created duringthe server configuration. ADI application appears with the All projects page. For the first time user, thereis no project area. Click the project area management link to set up a project

area. The application navigates to the Application Administration - IBM ApplicationDelivery Intelligence (ADI) page. Use this page to create a project area.

Click the Create Project Area link on the top right corner.

Provide a Name, Summary, and Description for the project area.Select IBM Application Delivery Intelligence Application Default Processas process if it is not yet selected.Assign or create users as members of the project area. For more information,see Creating and managing users. Assign or create users as administrators for the project area.Click Save next to the project area name on the top to create the project area.

Note: After you save the project area, a message appears warning you about themembers added without roles. You can ignore this warning message becausecurrently no role to members is available. On the upper left corner of window, click the Home icon to open the drop-downmenu and select IBM Application Delivery Intelligence (ADI) . My Projects andAll Projects appear.Click All projects. The project area you previously created appears. Click the project area to open it in your browser and then bookmark the page ofyour project area as the ADI home page.

Parent topic:Installing ADI by using web-based custom setup

113

1.

2.

Shutting down the server After you finish the installation and setup, you can shut down the server. To shut down the server, complete the following steps:

Open terminal/command prompt and navigate to the unzipped-adi-installer/adi/server directory by running the following command:cd /unzipped-adi-installer/adi/server In the current directory, shut down the server by running the following command:server.shutdown

Parent topic:Installing ADI by using web-based custom setup

114

-

-

-

-

Installing ADI by using the repotools command When you install and set up the ADI application by using the repotools command, itsets up the Derby database by default. In this case, you cannot use any other databases. You can use a repotools command to play back setup options with a pre-packed response file which enables you to set up everything from the commandshell. The information that you provide by using repotools command is the same asfor the web-based express setup.

Starting up the server To install ADI by using repotools command, you need to start up the server first.Unzip the ADI installer package and run commands for the start. Running the response file You need to run the response file before you can successfully install ADI by usingrepotools command.Setting up ADI application This topic describes how you set up the IBM Application Delivery Intelligence(ADI) application after you install ADI by using the repotools command.Shutting down the server After you finish the installation and setup, you can shut down the server.

Parent topic:Installation and setup

115

1.2.

3.

Starting up the server To install ADI by using repotools command, you need to start up the server first.Unzip the ADI installer package and run commands for the start. You need to take the following steps to start up the server.

Unzip the ADI installer package.Open terminal/command prompt and navigate to the unzipped-adi-installer/adi/server directory by running the following command:cd /unzipped-adi-installer/adi/server In the current directory, start the server by running the following command:server.startup

Parent topic:Installing ADI by using the repotools command

116

1.

2.

3.

4.-

-

-5.

Running the response file You need to run the response file before you can successfully install ADI by usingrepotools command. To run the response file, take the following steps:

Use a command shell to change the directory to unzipped-adi-installer/serverdirectory where you can find the response file.Run the following command:repotools-jts -setup repositoryURL=https://server-address:9443/jtsadminUserID=ADMIN

adminPassword=ADMIN parametersFile=./adi-response.properties prompt=missing Note: Replace the server-address with a fully qualified server machine name. To see the default values setting in the response file, you can find it in /unzipped-adi-installer/adi/server/adi-response.properties.During the setup, you are prompted to provide the following information.

The repository URL from above again. It might theoretically be different if youare using aliases or proxies.The user name, password, and email address of the admin user you want tocreate.The license. Select licence 2.

When you complete, the command line shows a message to indicate thesuccessful installation.

Parent topic:Installing ADI by using the repotools command

117

1.

2.

3.

4.

A.

B.C.

D.

E.F.

5.

6.7.

Setting up ADI application This topic describes how you set up the IBM Application Delivery Intelligence (ADI)application after you install ADI by using the repotools command. Before you begin, ensure that the pop-up blocker is disabled for https://fully qualifiedhostname:9443/adi/web page. To set up the ADI application, take the following steps:

Browse to https://fully qualified hostname:9443/adi/web to open the ADIapplication.Log on with the administrative user name and password that you created duringthe server configuration. ADI application appears with the All projects page. For the first time user, thereis no project area. Click the project area management link to set up a project

area. The application navigates to the Application Administration - IBM ApplicationDelivery Intelligence (ADI) page. Use this page to create a project area.

Click the Create Project Area link on the top right corner.

Provide a Name, Summary, and Description for the project area.Select IBM Application Delivery Intelligence Application Default Processas process if it is not yet selected.Assign or create users as member of the project area. For more information,see Creating and managing users. Assign or create users as administrators for the project area.Click Save next to the project area name on the top to create the project area.

Note: After you save the project area, a message appears warning you about themembers added without roles. You can ignore this warning message becausecurrently no role to members is available. On the upper left corner of window, click the Home icon to open the drop-downmenu and select IBM Application Delivery Intelligence (ADI) . My Projects andAll Projects appear.Click All projects. The project area you previously created appears. Click the project area to open it in your browser and then bookmark the page ofyour project area as the ADI home page.

Parent topic:Installing ADI by using the repotools command

118

119

1.

2.

Shutting down the server After you finish the installation and setup, you can shut down the server. To shut down the server, complete the following steps:

Open terminal/command prompt and navigate to the unzipped-adi-installer/adi/server directory by running the following command:cd /unzipped-adi-installer/adi/server In the current directory, shut down the server by running the following command:server.shutdown

Parent topic:Installing ADI by using the repotools command

120

-

-

-

Installing ADI into an existing CLM installation You can find a roadmap for co-installing ADI with an existing IBM® Rational®Collaborative Lifecycle Management (CLM) solution, such as an existing Jazz™Team Server (JTS) and Rational Team Concert (RTC).

Before you begin Check out prerequisites before you install ADI into an existing CLM installation.Procedures After you verify the prerequisites, you can complete steps to install ADI into anexisting CLM installation. What to do next After you install ADI into an existing CLM, you can find the next steps to performmore operations.

Parent topic:Installation and setup

121

-

-

-

-

Before you begin Check out prerequisites before you install ADI into an existing CLM installation.

ADI is implemented as a Jazz™ application so it can be co-installed in the sameway as any other Jazz application, such as RTC or Doors Next Generation. For theJazz Deployment guidelines and the proposed deployment topologies, see JazzDeployment Guide.Decide on the topology that you want to implement. The main decision is to co-install on the same server machine as the JTS or to install it on a separate servermachine. The following instructions cover both scenarios.The versions of the CLM solution and ADI must match. ADI 5.0.2 can be co-installed only with CLM 6.0.2 or later version.These instructions work only for a new installation of ADI. If you use a stand-aloneversion of ADI, you cannot currently move that into the configuration as describedin the Procedures. Because the ADI application must remain with the JTS forwhich it was originally installed. However, those instructions work with an existinginstallation of CLM and a fresh install when the versions match as listed previously.Another possibility is to install CLM applications such as RTC into an existing ADIinstallation, that is, the JTS provided with ADI. In that case, review the CLM onlinehelp instructions about adding CLM applications to an existing JTS for moreinformation.

Parent topic:Installing ADI into an existing CLM installation

122

1.

-

2.-

1.

2.

3.

Procedures After you verify the prerequisites, you can complete steps to install ADI into anexisting CLM installation. Installing CLM

Use Installation Manager to install CLM 6.0.2 or a later version. If you installedand set up CLM (perhaps it is a CLM already in use), jump ahead to followingsection of "Install the ADI application".

For details, see Installing the Rational solution for Collaborative LifecycleManagement by using IBM Installation Manager in the CLM Online help.

Run the setup for CLM installation. For information on installing CLM, see CLM Interactive Installation Guide.

Installing the ADI application You can install ADI together with JTS installed on the same server machine and inthe same installation directory. In this case, ADI runs on the same Libertyapplication server as CLM and has the same base URL as the JTS and the otherlocally running applications. As an alternative that offers more scalability, you caninstall ADI on a different server machine. In this case, ADI has a different base URLthan the JTS. Other CLM applications will then most likely also be running on adifferent server. For details and how you can use a proxy server to unify URLs, seethe CLM Online help and Deployment Guides mentioned previously. Setting up a database If you use DB2® for your CLM databases, then you need to create the ADI databasein the existing DB2. You do not need to create JTS and DW database since theywere created during the CLM's setup. For more information, see Installing ADI byusing web-based custom Setup. Alternative 1: Installing ADI together with the JTS Prerequisite: Assumption is that the CLM server is set up and fully functional. Theinstallation machine has at least the JTS setup and zero or more applications suchas RTC. The CLM installation directory is referred to as clm_install.

Stop the CLM server with the following commands.cd clm_install/JazzTeamServer/serverserver.shutdown Extract the ADI distribution in a temporary directory referred to as adi_unzipbelow.Merge some of the ADI installation files into the JTS installation by copying (only)the following files and directories from the adi_unzip directory into thecorresponding clm_install directory.Table 1. Files and directories involved inmerging ADI installation into JTS installation

Copy from adi_unzip/adi/ Toclm_install/JazzTeamServer/

cobol-coverage (copy the entire folder intoJazzTeamServer folder)

license/adi license/java-coverage (copy the entire folder into

JazzTeamServer folder)

123

4.

5.

1.

2.

Note: If you are installing CLM and ADI at the same time and have not set it upyet, then the clm_install/server/liberty/servers directory does not exist, yet. In thatcase copy the files to clm_install/server/liberty/clmServerTemplate. Also, for thefollowing step use the template path for editing the file. All template files will becopied to liberty/server/clm the first time the server starts. Open the file clm_install/server/liberty/servers/clm/conf/application.xml in a texteditor. Add the following lines at the end, but before this line: </server><application

type="war" id="adi" name="adi" location="${server.config.dir}/apps/adi.war"></application>

<application type="war" id="adihelp" name="adihelp"

location="${server.config.dir}/apps/adihelp.war"></application> Start the CLM server again. Continue with the step of "Registering ADI with JTS".

Alternative 2: Installing ADI on another server machine After you install ADI, you still need to register it with the JTS. If you install CLM andADI fresh together at the same time, then the registration step will be part of theregular jts/setup. In the following, it is assumed that CLM was already set up andyou are adding ADI to that setup after the fact. Prerequisite: Assumption is that the CLM server is set up and fully functional. It isrunning on a different machine than where you want to install ADI. For thisinstallation option, you don't need to shut down the JTS server.

Extract the ADI distribution into the directory where you want it installed (forexample, /opt/ibm/adi on Linux or C:\ibm\adi on Windows). The location will bereferred to as adi_unzip below.Execute this command to deploy the Liberty server inside the installationdirectory:cd adi_unzip/adi/server

repotools/adi repostoolsserver/conf/adi server/conf/server/headless-CC server/server/liberty/clmServerTemplate/apps/adi.war

server/liberty/servers/clm/apps/

server/liberty/clmServerTemplate/apps/adihelp.war

server/liberty/servers/clm/apps/

server/liberty/clmServerTemplate/apps/adi.war.zip

server/liberty/servers/clm/apps/

server/liberty/clmServerTemplate/apps/adihelp.war.zip

server/liberty/servers/clm/apps/

server/codecov.shutdown.* server/server/codecov.startup.* server/server/repotools-adi.* server/server/server.shutdown.* server/ (replacing the existing

file; do file merge to be sure)server/server.startup.* server/ (replacing the existing

file; do file merge to be sure)swidtag/ibm.com_IBM_Application_Delivery_Intelligence-5.0.2.swidtag

swidtag/

124

3.

---

4.

5.

1.

2.

3.A.

B.

4.5.

6.

7.

8.A.

B.

server.startup -create Delete the following files and directories in adi_unzip/adi to remove the JTS fromthis installation so that you can use the existing JTS running on that othermachine:

/server/conf/jts/server/liberty/servers/clm/apps/clm*/server/liberty/servers/clm/apps/jts*

Start the ADI server with the following commands.cd unzipped-adi-installer/serverserver.startup Continue with the following step of "Registering ADI with JTS".

Registering ADI with JTS

As a Jazz™ administrator, navigate to the JTS home page either through theHome menu of any application or by going to the URL: https://server:port/jts/admin.Click the Server tab and select the Registered Application menu. A list ofapplications that are already registered with this JTS appears, among which ADIhasn't included yet.Determine the root services URL for your ADI application:

In case that you co-installed ADI on the same server machine and directory asyou do with JTS, the URLs will have the same machine name and port as theJTS URL. For example, if your JTS URL is https://server.sample.org:9443/jtsthen the ADI root services URL will be https://server.sample.org:9443/adi/scr.In case you installed ADI on another machine, then the URL will be based onthat other machine's hostname. For example, the JTS URL could behttps://server01.sample.org:9443/jts then the ADI root services URL could behttps://server02.sample.org:9443/adi/scr.

In the Registered Application admin page, click Add.Under Discovery URL, fill in the URL you specified in Step 3 and click Tab onyour keyboard. The dialog immediately tells you that it is verifying the URL youtype, which can take a moment. If the verification succeeds, the dialog updates. Ifyou received an error message, you most likely typed the URL wrong or youinstalled ADI on another machine.Fill in the application name, for example, /adi to be consistent with the other apps.Fill in a Consumer Secret twice to confirm the password that applications use toauthenticate their communications with each other. Keep all other fields assuggested by the dialog.Click Finish. When the dialog closes, you see a green status message at the top.Click Application Setup Wizard in that message to continue. This leads you tothe page https://server:port/adi/customSetup.Walk through the setup wizard as instructed.

If you configured a DB2 database for ADI then specify its details in theConfigure Database step.In the Configure Data Warehouse step, you must configure the samewarehouse database as the JTS. If you do not have the connection details andpassword, you must contact the JTS administrator who set it up. Because ADI

125

will work only when you configure the warehouse correctly. Parent topic:Installing ADI into an existing CLM installation

126

What to do next After you install ADI into an existing CLM, you can find the next steps to performmore operations. After you set up the application, you can follow the steps for creating a project areaas described in Creating and managing users and assign your existing CLM userbase as ADI users of that project area. You must also install and assign ADI ClientAccess Licenses to all your users as described in Managing Client Access Licenses. Parent topic:Installing ADI into an existing CLM installation

127

----

Migrating from a previous release If you use a previous release of ADI and want to migrate all of its data, you mustfollow the migration steps described in this section instead of the other installationscenarios. Note: The following instructions assume that you had either installed ADI 1.0.0 orADI 1.0.1 or ADI 1.0.1 ifix01 or ADI 1.0.2 in the following locations. If you installed indifferent locations, you can substitute the path when necessary.Linux: /opt/ibm/adi/ Windows: C:\IBM\adi\

Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1 ifix01 Migrating from ADI 1.0.1 to ADI 1.0.1 ifix01 Migrating from ADI 1.0.1 or ADI 1.0.1 ifix01 to ADI 1.0.2 Migrating from ADI 1.0.2 to ADI 5.0.2

Parent topic:Installation and setup

128

-

-

-

-

-

-

Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1ifix01

Installing the new release into a new directory You install every new release into a new installation directory parallel to the oldversion's installation. You do not install releases on top of each other to upgrade.Backing up database files If you use an enterprise database, such as DB2®, you can make backups of yourdata to be able to repeat the migration in case of errors. In case of Derby, you copyyour databases to the new location.Copying key configuration and data files from the old to the new installation You run various commands to copy configuration files from the old to the newlocation. In some cases, you make updates to the files to accommodate newsettings.Migrating the JTS data You execute an interactive command that allows you to migrate the JTSconfiguration files, the data repository, and the warehouse.Migrating the ADI application data You execute a command that updates the data repository storing ADI data.Starting the server and waiting for additional migration to finish After all the files are migrated, you can start the server. It executes additionalmigration tasks that the admin user can review for success.

Parent topic:Migrating from a previous release

129

1.

2.

3.

Installing the new release into a new directory You install every new release into a new installation directory parallel to the oldversion's installation. You do not install releases on top of each other to upgrade. Take the following steps to install the new release of ADI into a new directory.

Stop the current release of ADI using the following commands.Linux: cd /opt/ibm/adi/server

./server.shutdown Windows: cd \IBM\adi\server

server.shutdown Rename the installation directory to make sure that you can identify where theprevious version is installed.Linux: cd /opt/ibm

mv adi adi100 Windows: cd \IBM

ren adi adi100 Download the new release of ADI and extract it into the same location as you didwith the old release. Rename the new release in the same way. For example,rename it to adi101. Then you have the adi100 and adi101 next to each other inthe same installation location.

Parent topic:Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1 ifix01

130

--

1.

2.

3.

Backing up database files If you use an enterprise database, such as DB2®, you can make backups of yourdata to be able to repeat the migration in case of errors. In case of Derby, you copyyour databases to the new location. If you are using DB2, make sure that you follow the instructions of Backing up yourdata to back up your three databases: JTS, ADI, DW. If you are using Derby, no backup is required as you will have copies of thesedatabases in your adi100 installation directory. You must copy them to the newinstallation location with the following steps.Notes:

Make sure you adjust the path to your installation directory if necessary. Do not perform those steps if you are using DB2.

Create the liberty application directory to copy the files to.Linux: cd /opt/ibm/adi101/server

./server.startup -create Windows: cd \IBM\adi101\server

server.startup -create Delete the default Derby databases to replace them with the databases from theold release:Linux: rm -rf /opt/ibm/adi101/server/conf/jts/derby/repositoryDB

rm -rf /opt/ibm/adi101/server/conf/adi/derby/repositoryDB Windows: rd /s/q \IBM\adi101\server\conf\jts\derby\repositoryDB

rd /s/q \IBM\adi101\server\conf\adi\derby\repositoryDB Copy the Derby databases from the previous release to the new release. Note:The second command points to a path inside the liberty application severdirectory. That is where the Derby warehouse is located currently because of adefect in JTS 6.0.1 and 6.0.2. Linux: cp -R /opt/ibm/adi100/server/conf/jts/derby/repositoryDB

/opt/ibm/adi101/server/conf/jts/derby/repositoryDB

cp -R /opt/ibm/adi100/server/liberty/servers/clm/conf/jts

/opt/ibm/adi101/server/liberty/servers/clm/conf/jts

cp -R /opt/ibm/adi100/server/conf/adi/derby/repositoryDB

/opt/ibm/adi101/server/conf/adi/derby/repositoryDB Windows: xcopy /s/i \IBM\adi100\server\conf\jts\derby\repositoryDB \IBM\adi101\server\conf\jts\derby\repositoryDB

xcopy /s/i

\IBM\adi100\server\liberty\servers\clm\conf\jts\derby\warehouseDB\IBM\adi101\server\liberty\servers\clm\c

onf\jts\derby\warehouseDB\

xcopy /s/i \IBM\adi100\server\conf\adi\derby\repositoryDB \IBM\adi101\server\conf\adi\derby\repositoryDB

131

Parent topic:Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1 ifix01

132

1.

2.

3.

Copying key configuration and data files from theold to the new installation You run various commands to copy configuration files from the old to the newlocation. In some cases, you make updates to the files to accommodate newsettings. You need to copy key configuration files from the old installation location to the new.

Copy RDF index files.Linux: cp -R /opt/ibm/adi100/server/conf/adi/indices /opt/ibm/adi101/server/conf/adi/ Windows: xcopy /s/i \IBM\adi100\server\conf\adi\indices \IBM\adi101\server\conf\adi\indices Copy the uploaded code coverage files.Linux: cp -R /opt/ibm/adi100/server/conf/adi/coverageFileStorage

/opt/ibm/adi101/server/conf/adi/coverageFileStorage Windows: xcopy /s/i \IBM\adi100\server\conf\adi\coverageFileStorage

\IBM\adi101\server\conf\adi\coverageFileStorage Copy the ADI application's setting file.Linux: cp /opt/ibm/adi100/server/conf/adi/teamserver.properties /opt/ibm/adi101/server/conf/adi/ Windows: copy /y \IBM\adi100\server\conf\adi\teamserver.properties \IBM\adi101\server\conf\adi\

Parent topic:Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1 ifix01

133

Migrating the JTS data You execute an interactive command that allows you to migrate the JTSconfiguration files, the data repository, and the warehouse. Now you can execute a command that migrates your JTS, its repository, andwarehouse databases to the latest version. Linux: cd /opt/ibm/adi101/server

upgrade/jts/jts_upgrade.sh -oldJTSHome /opt/ibm/adi100/server/conf -noPrompt -noStepPrompt -noEditor Windows: cd \IBM\adi101\server

upgrade\jts\jts_upgrade.bat -oldJTSHome C:\IBM\adi100\server\conf -noPrompt -noStepPrompt -noEditor If you configured your server with nondefault options or want more control over allthe steps this migration script perform, see the Jazz™ Online help. Parent topic:Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1 ifix01

134

Migrating the ADI application data You execute a command that updates the data repository storing ADI data. Finally, you can migrate the ADI application's repository database: Linux: cd /opt/ibm/adi101/server

./repotools-adi.sh -addTables noPrompt Windows: cd \IBM\adi101\server

repotools-adi.bat -addTables noPrompt The server now has all the data of the previous server. However, you might still wantto add other configuration options, such as renewing server certificates etc. Formore details, see the Jazz™ Online Help . Parent topic:Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1 ifix01

135

1.

2.

3.

4.

5.

Starting the server and waiting for additionalmigration to finish After all the files are migrated, you can start the server. It executes additionalmigration tasks that the admin user can review for success. When you start the server, it executes more migration operations automatically. Anadministrator can review the progress of these operations in the log files that getgenerated on the server machine.

Start the new ADI server.Linux: cd /opt/ibm/adi101/server

./server.startup Windows: cd \IBM\adi101\server

server.startup Use a browser to navigate to the applications main page: https://servername:9443/adi/webObserve the progress of the migration in the log file located inadi101/server/logs/adi.log. For example, you can observe it by opening it in a texteditor and frequently reloading it or using the tail command on Linux.Wait for these two lines to be shown in the log.CRIDA0059I The DIMEZ warehouse schemavalidation has completed. andCRIDA0052I Completed checking the ADI data migration status. Also review previous lines shown for status messages and warnings about themigration. If there are errors, review the error message to understand the natureof the problem. You can also start over by redoing the steps described in thisguide with a new fresh installation. Contact technical support to get help with anymigration error messages.When the migration is shown as successful in the log, you can notify your usersthat the new server is available for use.

Parent topic:Migrating from ADI 1.0 to ADI 1.0.1 or ADI 1.0.1 ifix01

136

-

-

-

-

Migrating from ADI 1.0.1 to ADI 1.0.1 ifix01

Installing the new release into a new directory You install every new release into a new installation directory parallel to the oldversion's installation. You do not install releases on top of each other to upgrade.Backing up database files If you use an enterprise database, such as DB2®, you can make backups of yourdata to be able to repeat the migration in case of errors. In case of Derby, you copyyour databases to the new location.Copying key configuration and data files from the old to the new installation You run various commands to copy configuration files from the old to the newlocation. In some cases, you make updates to the files to accommodate newsettings.Starting the server and waiting for additional migration to finish After all the files are migrated, you can start the server. It executes additionalmigration tasks that the admin user can review for success.

Parent topic:Migrating from a previous release

137

1.

2.

3.

Installing the new release into a new directory You install every new release into a new installation directory parallel to the oldversion's installation. You do not install releases on top of each other to upgrade. Take the following steps to install the new release of ADI into a new directory.

Stop the current release of ADI using the following commands.Linux: cd /opt/ibm/adi/server

./server.shutdown Windows: cd \IBM\adi\server

server.shutdown Rename the installation directory to make sure that you can identify where theprevious version is installed.Linux: cd /opt/ibm

mv adi adi101 Windows: cd \IBM

ren adi adi101 Download the new release of ADI and extract it into the same location as you didwith the old release. Rename the new release in the same way. For example,rename it to adi1011. Then you have the adi101 and adi1011 next to each otherin the same installation location.

Parent topic:Migrating from ADI 1.0.1 to ADI 1.0.1 ifix01

138

--

1.

2.

3.

Backing up database files If you use an enterprise database, such as DB2®, you can make backups of yourdata to be able to repeat the migration in case of errors. In case of Derby, you copyyour databases to the new location. If you are using DB2, make sure that you follow the instructions of Backing up yourdata to back up your three databases: JTS, ADI, DW. If you are using Derby, no backup is required as you will have copies of thesedatabases in your adi101 installation directory. You must copy them to the newinstallation location with the following steps.Notes:

Make sure you adjust the path to your installation directory if necessary. Do not perform these steps if you are using DB2.

Create the Liberty application directory to copy the files to.Linux: cd /opt/ibm/adi1011/server

./server.startup -create Windows: cd \IBM\adi1011\server

server.startup -create Delete the default Derby databases to replace them with the databases from theold release:Linux: rm -rf /opt/ibm/adi1011/server/conf/jts/derby/repositoryDB

rm -rf /opt/ibm/adi1011/server/conf/adi/derby/repositoryDB Windows: rd /s/q \IBM\adi1011\server\conf\jts\derby\repositoryDB

rd /s/q \IBM\adi1011\server\conf\adi\derby\repositoryDB Copy the Derby databases from the previous release to the new release. Note:The second command points to a path inside the liberty application severdirectory. That is where the Derby warehouse is located currently because of adefect in JTS 6.0.1 and 6.0.2. Linux: cp -R /opt/ibm/adi101/server/conf/jts/derby/repositoryDB

/opt/ibm/adi1011/server/conf/jts/derby/repositoryDB

cp -R /opt/ibm/adi101/server/liberty/servers/clm/conf/jts

/opt/ibm/adi1011/server/liberty/servers/clm/conf/jts

cp -R /opt/ibm/adi101/server/conf/adi/derby/repositoryDB

/opt/ibm/adi1011/server/conf/adi/derby/repositoryDB Windows: xcopy /s/i \IBM\adi101\server\conf\jts\derby\repositoryDB \IBM\adi1011\server\conf\jts\derby\repositoryDB

xcopy /s/i

\IBM\adi101\server\liberty\servers\clm\conf\jts\derby\warehouseDB\IBM\adi1011\server\liberty\servers\clm\

conf\jts\derby\warehouseDB\

xcopy /s/i \IBM\adi101\server\conf\adi\derby\repositoryDB \IBM\adi1011\server\conf\adi\derby\repositoryDB

139

Parent topic:Migrating from ADI 1.0.1 to ADI 1.0.1 ifix01

140

1.

2.

3.

4.

5.

6.

Copying key configuration and data files from theold to the new installation You run various commands to copy configuration files from the old to the newlocation. In some cases, you make updates to the files to accommodate newsettings. You need to copy key configuration files from the old installation location to the new.

Copy RDF index files for ADI.Linux: cp -R /opt/ibm/adi101/server/conf/adi/indices /opt/ibm/adi1011/server/conf/adi/ Windows: xcopy /s/i \IBM\adi101\server\conf\adi\indices \IBM\adi1011\server\conf\adi\indices Copy the uploaded code coverage files for ADI.Linux: cp -R /opt/ibm/adi101/server/conf/adi/coverageFileStorage

/opt/ibm/adi1011/server/conf/adi/coverageFileStorage Windows: xcopy /s/i \IBM\adi101\server\conf\adi\coverageFileStorage

\IBM\adi1011\server\conf\adi\coverageFileStorage Copy the ADI application's setting file. If a prompt to overwrite the existing filesoccurs, confirm it. Linux: cp /opt/ibm/adi101/server/conf/adi/teamserver.properties /opt/ibm/adi1011/server/conf/adi/ Windows: copy /y \IBM\adi101\server\conf\adi\teamserver.properties \IBM\adi1011\server\conf\adi\ Copy the RDF index for JTS. Linux: cp -R /opt/ibm/adi101/server/conf/jts/indices /opt/ibm/adi1011/server/conf/jts/ Windows: xcopy /s/i \IBM\adi101\server\conf\jts\indices \IBM\adi1011\server\conf\jts\indices Copy the JTS settings file. If a prompt to overwrite the existing files occurs,confirm it. Linux: cp /opt/ibm/adi101/server/conf/jts/teamserver.properties /opt/ibm/adi1011/server/conf/jts/ Windows: copy /y \IBM\adi101\server\conf\jts\teamserver.properties \IBM\adi1011\server\conf\jts\ Create the Liberty application directory to copy files to.Note:If you are usingDerby, you can skip the following step as you've executed it in the previous stepBacking up database files. If you are using DB2, you need to complete the following step.

141

7.

Linux: cd /opt/ibm/adi1011/server

./server.startup -create Windows: cd \IBM\adi1011\server

server.startup -create Copy Liberty setting files. If a prompt to overwrite the existing files occurs, confirmit. Linux: cp /opt/ibm/adi101/server/liberty/servers/clm/server.xml /opt/ibm/adi1011/server/liberty/servers/clm/

cp /opt/ibm/adi101/server/liberty/servers/clm/conf/*.xml /opt/ibm/adi1011/server/liberty/servers/clm/conf Windows: copy /y \IBM\adi101\server\liberty\servers\clm\server.xml \IBM\adi1011\server\liberty\servers\clm\

copy /y \IBM\adi101\server\liberty\servers\clm\conf\*.xml \IBM\adi1011\server\liberty\servers\clm\conf\ Parent topic:Migrating from ADI 1.0.1 to ADI 1.0.1 ifix01

142

1.

2.

3.

4.

5.

Starting the server and waiting for additionalmigration to finish After all the files are migrated, you can start the server. It executes additionalmigration tasks that the admin user can review for success. When you start the server, it executes more migration operations automatically. Anadministrator can review the progress of these operations in the log files that getgenerated on the server machine.

Start the new ADI server.Linux: cd /opt/ibm/adi1011/server

./server.startup Windows: cd \IBM\adi1011\server

server.startup Use a browser to navigate to the applications main page: https://servername:9443/adi/webObserve the progress of the migration in the log file located inadi101/server/logs/adi.log. For example, you can observe it by opening it in a texteditor and frequently reloading it or using the tail command on Linux.Wait for these two lines to be shown in the log.CRIDA0059I The DIMEZ warehouse schemavalidation has completed. andCRIDA0052I Completed checking the ADI data migration status. Also review previous lines shown for status messages and warnings about themigration. If there are errors, review the error message to understand the natureof the problem. You can also start over by redoing the steps described in thisguide with a new fresh installation. Contact technical support to get help with anymigration error messages.When the migration is shown as successful in the log, you can notify your usersthat the new server is available for use.

Parent topic:Migrating from ADI 1.0.1 to ADI 1.0.1 ifix01

143

-

-

-

-

Migrating from ADI 1.0.1 or ADI 1.0.1 ifix01 to ADI1.0.2

Installing the new release into a new directory You install every new release into a new installation directory parallel to the oldversion's installation. You do not install releases on top of each other to upgrade.Backing up database files If you use an enterprise database, such as DB2®, you can make backups of yourdata to be able to repeat the migration in case of errors. In case of Derby, you copyyour databases to the new location.Copying key configuration and data files from the old to the new installation You run various commands to copy configuration files from the old to the newlocation. In some cases, you make updates to the files to accommodate newsettings.Starting the server and waiting for additional migration to finish After all the files are migrated, you can start the server. It executes additionalmigration tasks that the admin user can review for success.

Parent topic:Migrating from a previous release

144

1.

2.

3.

Installing the new release into a new directory You install every new release into a new installation directory parallel to the oldversion's installation. You do not install releases on top of each other to upgrade. Take the following steps to install the new release of ADI into a new directory.

Stop the current release of ADI using the following commands.Linux: cd /opt/ibm/adi/server

./server.shutdown Windows: cd \IBM\adi\server

server.shutdown Rename the installation directory to make sure that you can identify where theprevious version is installed.Linux: cd /opt/ibm

mv adi adi101 Windows: cd \IBM

ren adi adi101 Download the new release of ADI and extract it into the same location as you didwith the old release. Rename the new release in the same way. For example,rename it to adi102. Then you have the adi101 and adi102 next to each other inthe same installation location.

Parent topic:Migrating from ADI 1.0.1 or ADI 1.0.1 ifix01 to ADI 1.0.2

145

--

1.

2.

3.

Backing up database files If you use an enterprise database, such as DB2®, you can make backups of yourdata to be able to repeat the migration in case of errors. In case of Derby, you copyyour databases to the new location. If you are using DB2, make sure that you follow the instructions of Backing up yourdata to back up your three databases: JTS, ADI, DW. If you are using Derby, no backup is required as you will have copies of thesedatabases in your adi101 installation directory. You must copy them to the newinstallation location with the following steps.Notes:

Make sure you adjust the path to your installation directory if necessary. Do not perform these steps if you are using DB2.

Create the Liberty application directory to copy the files to.Linux: cd /opt/ibm/adi102/server

./server.startup -create Windows: cd \IBM\adi102\server

server.startup -create Delete the default Derby databases to replace them with the databases from theold release:Linux: rm -rf /opt/ibm/adi102/server/conf/jts/derby/repositoryDB

rm -rf /opt/ibm/adi102/server/conf/adi/derby/repositoryDB Windows: rd /s/q \IBM\adi102\server\conf\jts\derby\repositoryDB

rd /s/q \IBM\adi102\server\conf\adi\derby\repositoryDB Copy the Derby databases from the previous release to the new release. Note:The second command points to a path inside the liberty application severdirectory. That is where the Derby warehouse is located currently because of adefect in JTS 6.0.1 and 6.0.2. Linux: cp -R /opt/ibm/adi101/server/conf/jts/derby/repositoryDB

/opt/ibm/adi102/server/conf/jts/derby/repositoryDB

cp -R /opt/ibm/adi101/server/liberty/servers/clm/conf/jts

/opt/ibm/adi102/server/liberty/servers/clm/conf/jts

cp -R /opt/ibm/adi101/server/conf/adi/derby/repositoryDB

/opt/ibm/adi102/server/conf/adi/derby/repositoryDB Windows: xcopy /s/i \IBM\adi101\server\conf\jts\derby\repositoryDB \IBM\adi102\server\conf\jts\derby\repositoryDB

xcopy /s/i

\IBM\adi101\server\liberty\servers\clm\conf\jts\derby\warehouseDB\IBM\adi102\server\liberty\servers\clm\c

onf\jts\derby\warehouseDB\

xcopy /s/i \IBM\adi101\server\conf\adi\derby\repositoryDB \IBM\adi102\server\conf\adi\derby\repositoryDB

146

Parent topic:Migrating from ADI 1.0.1 or ADI 1.0.1 ifix01 to ADI 1.0.2

147

1.

2.

3.

4.

5.

6.

Copying key configuration and data files from theold to the new installation You run various commands to copy configuration files from the old to the newlocation. In some cases, you make updates to the files to accommodate newsettings. You need to copy key configuration files from the old installation location to the new.

Copy RDF index files for ADI. Linux: cp -R /opt/ibm/adi101/server/conf/adi/indices /opt/ibm/adi102/server/conf/adi/ Windows: xcopy /s/i \IBM\adi101\server\conf\adi\indices \IBM\adi102\server\conf\adi\indices Copy the uploaded code coverage files for ADI. Linux: cp -R /opt/ibm/adi101/server/conf/adi/coverageFileStorage

/opt/ibm/adi102/server/conf/adi/coverageFileStorage Windows: xcopy /s/i \IBM\adi101\server\conf\adi\coverageFileStorage

\IBM\adi102\server\conf\adi\coverageFileStorage Copy the ADI application's setting file. If a prompt to overwrite the existing filesoccurs, confirm it. Linux: cp /opt/ibm/adi101/server/conf/adi/teamserver.properties /opt/ibm/adi102/server/conf/adi/ Windows: copy /y \IBM\adi101\server\conf\adi\teamserver.properties \IBM\adi102\server\conf\adi\ Copy the RDF index for JTS. Linux: cp -R /opt/ibm/adi101/server/conf/jts/indices /opt/ibm/adi102/server/conf/jts/ Windows: xcopy /s/i \IBM\adi101\server\conf\jts\indices \IBM\adi102\server\conf\jts\indices Copy the JTS settings file. If a prompt to overwrite the existing files occurs,confirm it. Linux: cp /opt/ibm/adi101/server/conf/jts/teamserver.properties /opt/ibm/adi102/server/conf/jts/ Windows: copy /y \IBM\adi101\server\conf\jts\teamserver.properties \IBM\adi102\server\conf\jts\ Create the Liberty application directory to copy files to.Note:If you are usingDerby, you can skip the following step as you've executed it in the previous stepBacking up database files.

148

7.

If you are using DB2, you need to complete the following step. Linux: cd /opt/ibm/adi102/server

./server.startup -create Windows: cd \IBM\adi102\server

server.startup -create Copy Liberty setting files. If a prompt to overwrite the existing files occurs, confirmit. Linux: cp /opt/ibm/adi101/server/liberty/servers/clm/server.xml /opt/ibm/adi102/server/liberty/servers/clm/

cp /opt/ibm/adi101/server/liberty/servers/clm/conf/*.xml /opt/ibm/adi102/server/liberty/servers/clm/conf Windows: copy /y \IBM\adi101\server\liberty\servers\clm\server.xml \IBM\adi102\server\liberty\servers\clm\

copy /y \IBM\adi101\server\liberty\servers\clm\conf\*.xml \IBM\adi102\server\liberty\servers\clm\conf\ Parent topic:Migrating from ADI 1.0.1 or ADI 1.0.1 ifix01 to ADI 1.0.2

149

1.

2.

3.

4.

5.

Starting the server and waiting for additionalmigration to finish After all the files are migrated, you can start the server. It executes additionalmigration tasks that the admin user can review for success. When you start the server, it executes more migration operations automatically. Anadministrator can review the progress of these operations in the log files that getgenerated on the server machine.

Start the new ADI server. Linux: cd /opt/ibm/adi102/server

./server.startup Windows: cd \IBM\adi102\server

server.startup Use a browser to navigate to the applications main page: https://fully qualifiedhostname:9443/adi/webObserve the progress of the migration in the log file located inadi102/server/logs/adi.log. For example, you can observe it by opening it in a texteditor and frequently reloading it or using the tail command on Linux.Wait for these two lines to be shown in the log.CRIDA0059I The DIMEZ warehouse schemavalidation has completed. andCRIDA0052I Completed checking the ADI data migration status. Also review previous lines shown for status messages and warnings about themigration. If there are errors, review the error message to understand the natureof the problem. You can also start over by redoing the steps described in thisguide with a new fresh installation. Contact technical support to get help with anymigration error messages.When the migration is shown as successful in the log, you can notify your usersthat the new server is available for use.

Parent topic:Migrating from ADI 1.0.1 or ADI 1.0.1 ifix01 to ADI 1.0.2

150

-

-

-

-

-

-

Migrating from ADI 1.0.2 to ADI 5.0.2

Installing the new release into a new directory You install every new release into a new installation directory parallel to the oldversion's installation. You do not install releases on top of each other to upgrade.Backing up database files If you use an enterprise database, such as DB2®, you can make backups of yourdata to be able to repeat the migration in case of errors. In case of Derby, you copyyour databases to the new location.Copying key configuration and data files from the old to the new installation You run various commands to copy configuration files from the old to the newlocation. In some cases, you make updates to the files to accommodate newsettings.Starting the server and waiting for additional migration to finish After all the files are migrated, you can start the server. It executes additionalmigration tasks that the admin user can review for success.Importing the new license keys ADI 5.0.2 release provides all new license keys. The 1.0.x license keys won't workwith ADI 5.0.2. Therefore, when installing ADI 5.0.2, you must download the newlicense keys and import it to replace the existing license keys. Setting role-permissions for project area members ADI 5.0.2 leverages role-based permissions capabilities from Jazz Team Server inorder to set users permissions to perform operations in ADI. 3 role permissions forADI 5.0.2 are available: Data Provider Administrator, Data Collection Owner, andData Collection Member. You need to set these roles to the members of yourproject areas in order to have the permissions to continue using ADI.

Parent topic:Migrating from a previous release

151

1.

2.

3.

Installing the new release into a new directory You install every new release into a new installation directory parallel to the oldversion's installation. You do not install releases on top of each other to upgrade. Take the following steps to install the new release of ADI into a new directory.

Stop the current release of ADI using the following commands.Linux: cd /opt/ibm/adi/server

./server.shutdown Windows: cd \IBM\adi\server

server.shutdown Rename the installation directory to make sure that you can identify where theprevious version is installed. Linux: cd /opt/ibm

mv adi adi102 Windows: cd \IBM

ren adi adi102 Download the new release of ADI and extract it into the same location as you didwith the old release. Rename the new release in the same way. For example,rename it to adi502. Then you have the adi102 and adi502 next to each other inthe same installation location.

Parent topic:Migrating from ADI 1.0.2 to ADI 5.0.2

152

--

1.

2.

3.

Backing up database files If you use an enterprise database, such as DB2®, you can make backups of yourdata to be able to repeat the migration in case of errors. In case of Derby, you copyyour databases to the new location. If you are using DB2, make sure that you follow the instructions of Backing up yourdata to back up your three databases: JTS, ADI, DW. If you are using Derby, no backup is required as you will have copies of thesedatabases in your adi102 installation directory. You must copy them to the newinstallation location with the following steps.Notes:

Make sure you adjust the path to your installation directory if necessary. Do not perform these steps if you are using DB2.

Create the Liberty application directory to copy the files to .Linux: cd /opt/ibm/adi502/server

./server.startup -create Windows: cd \IBM\adi502\server

server.startup -create Delete the default Derby databases to replace them with the databases from theold release: Linux: rm -rf /opt/ibm/adi502/server/conf/jts/derby/repositoryDB

rm -rf /opt/ibm/adi502/server/conf/adi/derby/repositoryDB Windows: rd /s/q \IBM\adi502\server\conf\jts\derby\repositoryDB

rd /s/q \IBM\adi502\server\conf\adi\derby\repositoryDB Copy the Derby databases from the previous release to the new release. Note:The second command points to a path inside the liberty application severdirectory. That is where the Derby warehouse is located currently because of adefect in JTS 6.0.1 and 6.0.2. Linux: cp -R /opt/ibm/adi102/server/conf/jts/derby/repositoryDB

/opt/ibm/adi502/server/conf/jts/derby/repositoryDB

cp -R /opt/ibm/adi102/server/liberty/servers/clm/conf/jts

/opt/ibm/adi502/server/liberty/servers/clm/conf/jts

cp -R /opt/ibm/adi102/server/conf/adi/derby/repositoryDB

/opt/ibm/adi502/server/conf/adi/derby/repositoryDB Windows: xcopy /s/i \IBM\adi102\server\conf\jts\derby\repositoryDB \IBM\adi502\server\conf\jts\derby\repositoryDB

xcopy /s/i \IBM\adi102\server\liberty\servers\clm\conf\jts\derby\warehouseDB

\IBM\adi502\server\liberty\servers\clm\conf\jts\derby\warehouseDB\

xcopy /s/i \IBM\adi102\server\conf\adi\derby\repositoryDB \IBM\adi502\server\conf\adi\derby\repositoryDB 153

Parent topic:Migrating from ADI 1.0.2 to ADI 5.0.2

154

1.

2.

3.

4.

5.

6.

Copying key configuration and data files from theold to the new installation You run various commands to copy configuration files from the old to the newlocation. In some cases, you make updates to the files to accommodate newsettings. You need to copy key configuration files from the old installation location to the new.

Copy RDF index files for ADI. Linux: cp -R /opt/ibm/adi102/server/conf/adi/indices /opt/ibm/adi502/server/conf/adi/ Windows: xcopy /s/i \IBM\adi102\server\conf\adi\indices \IBM\adi502\server\conf\adi\indices Copy the uploaded code coverage files for ADI. Linux: cp -R /opt/ibm/adi102/server/conf/adi/coverageFileStorage

/opt/ibm/adi502/server/conf/adi/coverageFileStorage Windows: xcopy /s/i \IBM\adi102\server\conf\adi\coverageFileStorage

\IBM\adi502\server\conf\adi\coverageFileStorage Copy the ADI application's setting file. If a prompt to overwrite the existing filesoccurs, confirm it. Linux: cp /opt/ibm/adi102/server/conf/adi/teamserver.properties /opt/ibm/adi502/server/conf/adi/ Windows: copy /y \IBM\adi102\server\conf\adi\teamserver.properties \IBM\adi502\server\conf\adi\ Copy the RDF index for JTS. Linux: cp -R /opt/ibm/adi102/server/conf/jts/indices /opt/ibm/adi502/server/conf/jts/ Windows: xcopy /s/i \IBM\adi102\server\conf\jts\indices \IBM\adi502\server\conf\jts\indices Copy the JTS settings file. If a prompt to overwrite the existing files occurs,confirm it. Linux: cp /opt/ibm/adi102/server/conf/jts/teamserver.properties /opt/ibm/adi502/server/conf/jts/ Windows: copy /y \IBM\adi102\server\conf\jts\teamserver.properties \IBM\adi502\server\conf\jts\ Create the Liberty application directory to copy files to.Note:If you are usingDerby, you can skip the following step as you've executed it in the previous stepBacking up database files.

155

7.

If you are using DB2, you need to complete the following step. Linux: cd /opt/ibm/adi502/server

./server.startup -create Windows: cd \IBM\adi502\server

server.startup -create Copy Liberty setting files. If a prompt to overwrite the existing files occurs, confirmit. Linux: cp /opt/ibm/adi102/server/liberty/servers/clm/server.xml /opt/ibm/adi502/server/liberty/servers/clm/

cp /opt/ibm/adi102/server/liberty/servers/clm/conf/*.xml /opt/ibm/adi502/server/liberty/servers/clm/conf Windows: copy /y \IBM\adi102\server\liberty\servers\clm\server.xml \IBM\adi502\server\liberty\servers\clm\

copy /y \IBM\adi102\server\liberty\servers\clm\conf\*.xml \IBM\adi502\server\liberty\servers\clm\conf\ Parent topic:Migrating from ADI 1.0.2 to ADI 5.0.2

156

1.

2.

3.

4.

5.

Starting the server and waiting for additionalmigration to finish After all the files are migrated, you can start the server. It executes additionalmigration tasks that the admin user can review for success. When you start the server, it executes more migration operations automatically. Anadministrator can review the progress of these operations in the log files that getgenerated on the server machine.

Start the new ADI server. Linux: cd /opt/ibm/adi502/server

./server.startup Windows: cd \IBM\adi502\server

server.startup Use a browser to navigate to the applications main page: https://fully qualifiedhostname:9443/adi/webObserve the progress of the migration in the log file located inadi502/server/logs/adi.log. For example, you can observe it by opening it in a texteditor and frequently reloading it or using the tail command on Linux.Wait for these two lines to be shown in the log.CRIDA0059I The DIMEZ warehouse schemavalidation has completed. andCRIDA0052I Completed checking the ADI data migration status. Also review previous lines shown for status messages and warnings about themigration. If there are errors, review the error message to understand the natureof the problem. You can also start over by redoing the steps described in thisguide with a new fresh installation. Contact technical support to get help with anymigration error messages.When the migration is shown as successful in the log, you can notify your usersthat the new server is available for use.

Parent topic:Migrating from ADI 1.0.2 to ADI 5.0.2

157

1.2.

3.4.

Importing the new license keys ADI 5.0.2 release provides all new license keys. The 1.0.x license keys won't workwith ADI 5.0.2. Therefore, when installing ADI 5.0.2, you must download the newlicense keys and import it to replace the existing license keys. Complete the following steps to import the new license keys.

Open your browser and go to https://fully qualified hostname:9443/jts/admin.On the Jazz Team Server Administration page, select Server > License KeyManagement.Click Add.. in the Client Access License Types.Browse to the new license jar file to import.

Parent topic:Migrating from ADI 1.0.2 to ADI 5.0.2

158

Setting role-permissions for project area members ADI 5.0.2 leverages role-based permissions capabilities from Jazz Team Server inorder to set users permissions to perform operations in ADI. 3 role permissions forADI 5.0.2 are available: Data Provider Administrator, Data Collection Owner, andData Collection Member. You need to set these roles to the members of your projectareas in order to have the permissions to continue using ADI. For more information about the permissions for each role, see Assigning role-basedpermissions to ADI users. For more information about how to assign role permissionto a user, see Creating and managing users. Parent topic:Migrating from ADI 1.0.2 to ADI 5.0.2

159

-

-

-

-

-

Administration As a administrator for ADI, you can do administration tasks for user managementand back up your data.

Logging in to administer the server /jts/admin and /adi/admin are two admin pages available. One is for administeringthe Jazz™ Team Server (JTS), and the other is for the ADI application. Users canbe created and managed in either of them. Licenses need to be managed in thejts/admin.Administration tasks for user management For user management, you can manage client access licenses, create andmanage users, and change password.Backing up your data You can use the repotools command lines to back up your data.Server configuration settings Administrators can use various settings for controlling the ADI server. Generating sample data for evaluation For ADI 5.0.2, you can generate two types of sample data in order to evaluate theADI functionality, that is, OMEGAMON for CICS data and Application Discoverydata.

Parent topic:IBM Application Delivery Intelligence 5.0.2

160

1.2.

Logging in to administer the server /jts/admin and /adi/admin are two admin pages available. One is for administeringthe Jazz™ Team Server (JTS), and the other is for the ADI application. Users canbe created and managed in either of them. Licenses need to be managed in thejts/admin. The following example demonstrates the steps to log in to a JTS. For moreinformation, see Logging in to administer the server.

Go to https://localhost:9443/jts/admin.Log in with the administrative user name and password that you created duringthe Jazz Team Server setting up.

Parent topic:Administration

161

-

-

-

Administration tasks for user management For user management, you can manage client access licenses, create and manageusers, and change password.

Managing client access licenses You must have a valid client access license and install it first before you canaccess ADI.Creating and managing users Administrators need to create or import users, assign licenses to users, grantusers as members of project areas, and assign role-based permissions to users.Users changing their password If you are using the local user management facilities provided by ADI (and not, forexample, an LDAP server), users need to change their password in their userprofile.

Parent topic:Administration

162

Managing client access licenses You must have a valid client access license and install it first before you can accessADI. Administrators need to install and assign the access licenses to users in theadministrative web UI of that JTS (/jts/admin). ADI ships with trial licenses that the administrator can enable during setup or withinthat same administrative UI used for importing licenses. After or during the trialperiod, the administrator needs to import and configure purchased user accesslicense keys that replace the trial licenses with the purchased licenses to keep alluser assignments intact. ADI currently supports only user unlock client accesslicenses, that is, no floating or token licenses is supported. All the steps for importing and configuring the ADI end user licenses aredocumented in the Jazz™ Online help: Installing and managing client accesslicense keys. After you create users, complete the steps in Assigning client access licenses tousers. Parent topic:Administration tasks for user management

163

-----

-

-

-

Creating and managing users Administrators need to create or import users, assign licenses to users, grant usersas members of project areas, and assign role-based permissions to users. To add a user to ADI, you need to complete the following procedures.

Create a user or import it from an external user management service.Assign client access licenses to the new user.Create a project area or use an existing one.Assign the user to that project area.Assign role-based permissions to ADI users.

Creating and managing user accounts Currently ADI supports user management by the embedded Websphere LibertyProfile application server and LDAP user registries. Creating and managing project areas After you create users in the JTS and assign them client access licenses, the useraccounts will be replicated and made available to the ADI application. They willalso be visible in the ADI administrative Web UI (/adi/admin). Users can then beassigned by the administrator to one or more ADI project areas. Project areaspartition all data managed in ADI and provide access to user to that data. They canbe used to organize the content of different teams that do not want the others tohave access to their data. Assigning role-based permissions to ADI users ADI 5.0.2 leverages Jazz™ Team Server (JTS) role-based permissions in order tomanage operations that the users can perform within analysis collections.

Parent topic:Administration tasks for user management

164

---

-

-

-

Creating and managing user accounts Currently ADI supports user management by the embedded Websphere LibertyProfile application server and LDAP user registries. For configuring either option, see Installing ADI by using web-based custom setuppage for references. The Jazz Online Help describes all the details for creating new users locally inLiberty and how to import from LDAP. All these operations are performed in the JTSadministrative web UI (/jts/admin):

For the general overview to user management, see Managing users.For information about how to create users locally, see Creating users.For information about how to import users from LDAP if it was configured duringsetup: Importing users from an external user registry.For information about how to assign user client access licenses, see Assigningclient access licenses to users.For information about how to assign user roles and permissions, see Assigningroles to a member.For information about how to modify the user permissions, see Modifying role-based permissions.

Note: When you use a local user registry in Liberty and create new users, thepassword of this new user is the same as the user id specified. The new user canthen log on with that temporary password and use the user profile page to change it.For more details, see Users changing their password. Parent topic:Creating and managing users

165

-

-

-1.

2.3.4.5.6.

7.

8.

9.

-

-

-

-

-

Creating and managing project areas After you create users in the JTS and assign them client access licenses, the useraccounts will be replicated and made available to the ADI application. They will alsobe visible in the ADI administrative Web UI (/adi/admin). Users can then beassigned by the administrator to one or more ADI project areas. Project areaspartition all data managed in ADI and provide access to user to that data. They canbe used to organize the content of different teams that do not want the others tohave access to their data.

To learn more about project areas see the Jazz Online help: Project area.Note:The current release of ADI does not support all the capabilities described here. Inparticular we do not yet support Behavior and Timelines. After the setup, the administrator must create at least one ADI project area andassign each user to at least one of these project areas.

Procedures:To create a project area you need to navigate to the ADI Administrative WebUI located at this URL: https://fully qualified hostname:9443/adi/admin.Select Project Areas > Active Project Areas from the menu.Select the Create Project Area operation.Complete the form by providing at least a value for the Project Area Name.Select the default ADI Process.Click Add in the Members section to add one or more users as team members.Only the users who are listed here are able to access the data for this projectarea.Click Add in the Administrators section to add one or more administrativeusers as administrators of this project area. Only the administrators of theproject area can modify the information of the project area such as adding amember to the project area.Click Save to start the creation. Note: After you click Save, a warning aboutmissing user roles appears. Assign the user roles and permissions to each user. For more informationabout ADI role-based permissions, refer to the table of Assigning role-basedpermissions to ADI users.

To learn more about creating Project Areas, see the Jazz Online Help: Creating aproject area.

Once the project area is created users that are listed as members are able toaccess it from this URL: https://fully qualified hostname:9443/adi/web.At any time, the administrator can add more users to the project area. To learnmore about managing user for a project area, see the Jazz Online Help: Addingand modifying users as members of project areas.Notes:

Any other user that you add to the Administrators member section is able tofollow the previous steps to manage membership of that project area.Jazz Online Help also shares information about Team Areas. ADI also uses teamareas, but they should be created as part of the main ADI Web UI by creatinganalysis collections. Analysis collections map one-to-one to a Jazz Team Area.For more details, see Managing analysis collections.

166

Parent topic:Creating and managing users

167

Assigning role-based permissions to ADI users ADI 5.0.2 leverages Jazz™ Team Server (JTS) role-based permissions in order tomanage operations that the users can perform within analysis collections. The table below shows the list of user roles and permissions for ADI.Note: A usercan be assigned to more than one user roles. Table 1. User roles and permissions for ADI

User Roles ADI View OperationsData ProviderAdministrator

Connections Create, modify, anddelete connections.

Data Providers Create, modify, anddelete data providers

Analysis Collections Create, modify, anddelete analysiscollections.

Analysis View analysis reportsof analysis collectionsof which they aremembers.

Analysis CollectionOwner

Data Providers View data providersinformation andmodify part ofinformation. Such asadding new builds,uploading coverageresults, refreshingbuild data, deletingbuilds from anexisting ManualBuilds data provideror downloading datafrom data providers.

Analysis Collections Modify analysiscollections. Such asmaking changes tomemberships andsetting thresholds.

Analysis View analysis reportsof analysis collectionsof which they areowners.

Analysis CollectionMember

Data Providers View buildinformation, viewdata collection logs,and download datafrom data providers.

Analysis Collections View analysiscollections.

168

Parent topic:Creating and managing users

Analysis View analysis reportsof analysis collectionsof which they aremembers.

169

1.

2.

3.

4.

Users changing their password If you are using the local user management facilities provided by ADI (and not, forexample, an LDAP server), users need to change their password in their userprofile. ADI end users can use their account profile to manage their user accounts.Primarily, they can use this profile page to change their passwords in cases a localuser directory, that is, not an LDAP user directory, is used. Procedure:

To access your profile page from the ADI Web UI, select the small triangle in theleft navigation bar with the user icon.In the pop-up menu that opens, select My Profile. The Jazz Team Serveradministration page appears. Log in with your username and password if you arerequired to do so.To change your password, select the Change Password.. button on your profilepage.In case your server uses a third party user directory, such as LDAP, this buttonwill be disabled.

For more information about changing password, see Changing your password in theJazz™ Online Help. Parent topic:Administration tasks for user management

170

-

-

Backing up your data You can use the repotools command lines to back up your data. To back up your data, follow the instructions described on Backing up and restoringRational solution for Collaborative Lifecycle Management applications.

If you configured a Derby database, you can find all the process on Backing upand restoring the Derby database.If you configured a DB2® database, you can find all the process on Backing upand restoring other supported databases.

Note: You also need to back up the directory of adi-install-directory/server/conf/adi/coverageFileStorage that stores all the uploaded coveragecompressed files. Parent topic:Administration

171

-

-

-

Server configuration settings Administrators can use various settings for controlling the ADI server. This documentation only focuses on ADI-specific settings. For more informationabout the other options that are offered by the Jazz™ framework, see Jazz OnlineHelp .

Settings that determine the behavior of startup scripts You can learn about those startup scripts and how their behaviors are defined byvariables.Server settings that need to be defined in teamserver.properties before the serverstarts Before the server starts, you must set several settings that define the behaviorand storage locations of the ADI server. For example, the location of the databasesor the location of the code coverage resource files. Those settings are providedthrough a properties file in the installation location:adi/server/conf/adi/teamserver.properties.Server settings that can be defined at runtime in the /adi/admin user interface When you navigate to the /adi/admin pages of your application, you find anAdvanced Properties section. It defines variables that can change the ADIserver's runtime behavior.

Parent topic:Administration

172

Settings that determine the behavior of startupscripts You can learn about those startup scripts and how their behaviors are defined byvariables. The following table outlines the variables that define the behavior of those startupscripts. For example, they determine what processes should be started and onwhich port they operate.Table 1. Variables defined in startup scripts

Script File Name Property Name /Parameter Option

Default Value Description

adi/server/server.startup

HEADLESSCC / -noheadlesscc

true Determines if theheadless codecoverage daemonprocess should bestarted when theADI server starts.The default is true,that is, the daemonis always started. Change the defaultin the script or startADI with -noheadlesscc toprevent starting thecoverage daemon.Example:server.startup -noheadlesscc

adi/server/codecov.startup

CODECOV_PORT 8005 Defines the port onwhich the headlesscode coveragecollection daemonshould listen forincoming coveragedata.If you change thevalue, you alsoneed to change it inthecodecov.shutdownscript and theteamserver.properties variablecom.ibm.dimez.dashboard.coverageHeadlessCC.port. Formore details, seeServer settings thatneed to be definedinteamserver.properties before the serverstarts.

173

Parent topic:Server configuration settings

adi/server/codecov.shutdown

CODECOV_PORT 8005 Defines the port onwhich the headlesscode coveragecollection daemonlistens for incomingcoverage data.If you change thevalue, you alsoneed to change it inthe codecov.startupscript and theteamserver.properties variablecom.ibm.dimez.dashboard.coverageHeadlessCC.port. Formore details, seeServer settings thatneed to be definedinteamserver.properties before the serverstarts.

174

Server settings that need to be defined inteamserver.properties before the server starts Before the server starts, you must set several settings that define the behavior andstorage locations of the ADI server. For example, the location of the databases orthe location of the code coverage resource files. Those settings are providedthrough a properties file in the installation location:adi/server/conf/adi/teamserver.properties. Many settings have defaults. If you don't define them in the property file, thosesettings use the default values automatically. Therefore, if you want to change sucha setting and you do not see it in the current file on your server, add the propertywith that new value. Make sure that you always stop the server first before youmake any changes to the property file as some settings can also be set through theAdministrative UI. The following list provides the ADI-specific settings. For other settings in the file thatis defined by the Jazz™ framework that ADI uses, see Jazz Online Help.Table 1.Server settings that need to be defined in teamserver.properties before the serverstarts

Property Name Default Value Descriptioncom.ibm.dimez.dashboard.coverageFileStoragePath

adi/server/conf/adi/coverageFileStorage

The location in whichuploaded codecoverage files will bemanaged. You needto back up thelocation together withthe databases.If you change thisvalue after the initialsetup, make sure thatyou move alldirectories availablein the old location tothe new one to avoidbreaking ADI'sconsistency.

175

com.ibm.dimez.dashboard.coverageFileStorageCheckoutTimeout

60000 For two serverthreads try tocheckout the samecoverage filedirectory at the sametime for update, theproperty defines theamount of time thesecond threads waitsto receive a file lockuntil it throws atimeout exception. Ifyou see timeouterrors frequentlywhen you collectcoverage files,increase this value.

com.ibm.dimez.dashboard.coverageHeadlessCCFilesPath

adi/server/conf/adi/headless-CC-files

The base-directory inwhich the headlesscode coveragecollector demon isplacing codecoverage filesreceived by thecollector. Asubdirectory isavailable for everydata provider. ADIcollects files fromthere and move theminto thecoverageFileStoragelocation.If you change thisvalue, you currentlyhave to also changethe same path in asecond location: inadi/server/codecov.startup.[bat|sh] changethe value of thePROVIDERIDDIRvariable. Thisoperation configuresthe headlesscollection daemonprocess responsiblefor receivingcoverage data fromcoverage engine overthe net.

176

Parent topic:Server configuration settings

com.ibm.dimez.dashboard.coverageHeadlessCC.port

8005 The port of theheadless collectiondaemon processunder which codecoverage data can bereceived. This valueis only used forcreating the StartupKey examples in theADI UI.To change it, youmust also change thevalue of theCODECOV_PORTvariable inadi/server/codecov.startup.[bat|sh].

177

Server settings that can be defined at runtime in the/adi/admin user interface When you navigate to the /adi/admin pages of your application, you find anAdvanced Properties section. It defines variables that can change the ADI server'sruntime behavior. An example for a direct URL to the /adi/admin page ishttps://adi.example.com:9444/adi/admin#action=com.ibm.team.repository.admin.configureAdvanced.Table 1. Variables Defined in the /adi/admin Page

ADIComponentName

Task Name PropertyName

DefaultValue

Description

ADIWarehouseCollectionsand Access

com.ibm.dimez.dashboard.service.internal.DataCollectionService

DataCollectionDataProvider -IBM CodeCoverageData - HeapMemory

512M Defines themaximumheapmemory size(by usingthe -XmxJVMparameter)to bedefined forthe datacollectionjobs thatcollect codecoveragedata.Change thisvalue if yourdatacollectionsreport out ofmemoryerrors.

178

ADIWarehouseCollectionsand Access

com.ibm.dimez.dashboard.service.internal.DataCollectionService

DataCollectionDataProvider -OperationsData fromIBMOMEGAMON for CICS -HeapMemory

512M Defines themaximumheapmemory size(by usingthe -XmxJVMparameter)to bedefined forthe datacollectionjobs thatcollectoperationsdata fromIBM®OMEGAMON® forCICS®.Change thisvalue if yourdatacollectionsreport out ofmemoryerrors.

ADIWarehouseCollectionsand Access

com.ibm.dimez.dashboard.service.internal.DataCollectionService

DataCollectionDataProvider -StaticAnalysisData fromIBMApplicationDiscovery -HeapMemory

512M Defines themaximumheapmemory size(by usingthe -XmxJVMparameter)to bedefined forthe datacollectionjobs thatcollect staticanalysisdata fromIBMApplicationDiscovery.Change thisvalue if yourdatacollectionsreport out ofmemoryerrors.

179

ADIWarehouseCollectionsand Access

com.ibm.dimez.dashboard.service.internal.DataCollectionService

DataCollectionDataProvider -Data ScrubInterval(hours)

24 The timeinterval inhoursbetweenexecutionsof thescheduleddatascrubbingbackgroundtask.

ADIWarehouseCollectionsand Access

com.ibm.dimez.dashboard.service.internal.DimezAutoCollectionScheduleTask

ADI DataCollectionSchedulesTask FixedDelay(seconds)

900 The timeinterval inseconds atwhich ADIcheckswhether toperformanother datacollection ornot fromIBM CodeCoverage orIBMApplicationDiscoverydataproviders.By default,ADI checksevery fifteenminutes.EachscheduledIBM CodeCoverage orIBMApplicationDiscoverydataprovidercheckswhether thespecifiedamount oftime haspassed ornot. And ifyes, ADIruns a newcollection.

180

ADIWarehouseCollectionsand Access

com.ibm.dimez.dashboard.service.internal.OmDataAutoCollectionScheduleTask

ADIOperationsDataCollectionSchedulesTask FixedDelay(seconds)

300 The timeinterval inseconds atwhich ADIcheckswhether toperformanother datacollection ornot fromOMEGAMON for CICSdataprovider. Bydefault ADIchecksevery fiveminutes.EachscheduledOMEGAMON for CICSdataprovidercheckswhether thespecifiedamount oftime haspassed ornot. And ifyes, ADIruns a newcollection. Ifyou wantADI to checkmorefrequently,you canchange thevalue.However,currently,changingthe value isnotrecommended to ensurethat youcollect foreach 5-minute slot.However, ifyour IBM

181

Parent topic:Server configuration settings

OMEGAMON for CICSserver is notable toprovide all ofits datawithin a 5-minutetimeframe,you need toset thisvalue to alarger valuethat reflectsyour IBMOMEGAMON for CICSperformance.

182

-

-

Generating sample data for evaluation For ADI 5.0.2, you can generate two types of sample data in order to evaluate theADI functionality, that is, OMEGAMON for CICS data and Application Discoverydata.

Generating OMEGAMON for CICS data You can generate OMEGAMON for CICS data as sample data to evaluate the ADIfunctionality.Generating Application Discovery data You can generate Application Discovery data as sample data to evaluate the ADIfunctionality.

Parent topic:Administration

183

1.

2.

3.4.

5.

---

-

6.

Generating OMEGAMON for CICS data You can generate OMEGAMON for CICS data as sample data to evaluate the ADIfunctionality. Complete the following steps to generate OMEGAMON for CICS data.

Navigate your browser to ADI admin page https://<fully qulified hostname>:9443/adi/admin.Log on with Jazz administrator user ID and password. ApplicationAdministration page appears.Click ADI Data Generation to go to the data generation page.Select OMEGAMON for CICS card. The form of Data Generation Settings forOMEGAMON for CICS appears.Fill in the following information in Data Generation Settings. For moreinformation about terms, see Terminology overviewNote: For evaluation purpose,you can leave all the default values in the Data Generation Settings form. .

Plex: Name of a CICS plex that you want to generate data. Days: Number of days to create the data.Goal Response Time: Goal response time that you want to set as threshold inmicroseconds.Project Areas: Select the project area where you want the data generator tostore. By default, it is your current project area.

Click Generate to generate OMEGAMON for CICS data as sample. When thedata generation completes, the OMEGAMON for CICS data provider with sampledata appears in the list of data providers on the Providers page.

Parent topic:Generating sample data for evaluation

184

1.

2.

3.4.

5.

-

-

-

6.

Generating Application Discovery data You can generate Application Discovery data as sample data to evaluate the ADIfunctionality. Complete the following steps to generate Application Discovery data.

Navigate your browser to ADI admin page https://fully qulified hostname:9443/adi/admin.Log on with ADI administrator user ID and password. ApplicationAdministration page appears.Click ADI Data Generation to go to the data generation page.Select Application Discovery card. The form of Data Generation Settings forApplication Discovery appears.Fill in the following information in Data Generation Settings. For moreinformation about terms, see Terminology overview.Note: For evaluation purpose,you can leave all the default values in the Data Generation Settings form exceptthe data points. If you use Derby as database for evaluation, you may want toreduce number of data points to be generated.

Data Points: Number of data points that you want to generate. One data pointrepresents one data set that ADI collected from Application Discovery.Time Interval: Time interval in hours that you want to simulate the datacollection.Project Areas: Select project area where you want the data generator to store.By default, it is your current project area.

Click Generate to generate Application Discovery data as sample. When the datageneration completes, the Application Discovery data provider with sample dataappears in the list of data providers on the Providers page.

Parent topic:Generating sample data for evaluation

185

-

-

Preparing external data sources You can learn how to prepare code coverage results for batch applications, CICS®,COBOL, PL/I and Java™.

Preparing code coverage results for COBOL and PL/I You can learn how to prepare code coverage results for batch applications, CICS,COBOL, and PL/I.Preparing code coverage results for Java You can learn how to prepare code coverage results for Java.

Parent topic:IBM Application Delivery Intelligence 5.0.2

186

1.

2.

3.

4.

-

-

-

Preparing code coverage results for COBOL andPL/I You can learn how to prepare code coverage results for batch applications, CICS®,COBOL, and PL/I. There are four scenarios for ADI headless code coverage collection:

RDz v901x - no headless CC - client UI required. Integrated Debugger (DIRECT) and Debug Tool (TCPIP) are both supported. RDz v91x, v95x - headless on client (Windows, Linux) Integrated Debugger (DIRECT) and Debug Tool (TCPIP) are both supported. Headless on z/OS Debug Tool (TCPIP) only (not relevant for ADI). IBM Debug for z Systems v14 Headless on client (Windows, Linux) in Debug Tool Compatibility Mode (TCPIP) No headless in Standard Mode (DIRECT with UI running) Headless on z/OS, Debug Tool Compatibility Mode (TCPIP) only (not relevant forADI) IBM Developer for z Systems v14, IBM Developer for z Systems v14 EnterpriseEdition Headless on client (Windows, Linux) in Debug Tool Compatibility Mode (TCPIP) No headless in Standard Mode (DIRECT with UI running) Headless on z/OS, Debug Tool Compatibility Mode (TCPIP) only (not relevant forADI)

Preparing code coverage results for batch applications If you use IBM® Developer for z Systems (IDz), you can generate the codecoverage results for batch applications either by using the IDz client or by using theIDz headless mode.Preparing code coverage results for CICS transactions by using the debug toolbackend and IDz client By using the debug tool backend and IDz client, you can prepare code coverageresults for CICS transactions.Preparing code coverage results for COBOL and PL/I by using RTC You can generate code coverage results for COBOL and PL/I by using automatedbuilds provided by Rational Team Concert™ Enterprise Extensions (RTC EE).Also, you can connect ADI to this RTC EE server to collect the code coverage dataautomatically.

Parent topic:Preparing external data sources

187

-

-

Preparing code coverage results for batchapplications If you use IBM® Developer for z Systems (IDz), you can generate the codecoverage results for batch applications either by using the IDz client or by using theIDz headless mode.

Generating code coverage results by using the IDz client You can generate code coverage results by using the IDz client. Generating code coverage results by using the headless collector running on ADIserver You can generate code coverage results by using the headless collector runningon ADI server. Verify the assumptions before you perform this activity.

Parent topic:Preparing code coverage results for COBOL and PL/I

188

-

-

Generating code coverage results by using the IDzclient You can generate code coverage results by using the IDz client.

Assumptions Verify the assumptions before you prepare code coverage results by using IDzclient.Procedures After you verify the assumptions, you can complete steps to prepare codecoverage results for batch applications by using IDz client.

Parent topic:Preparing code coverage results for batch applications

189

--

-

-

Assumptions Verify the assumptions before you prepare code coverage results by using IDzclient.

The tester or developer uses the IDz client to run the test.The program or a set of programs, such as LIST, MAP, XREF, and SOURCE, forwhich the code coverage results are being gathered should be compiled fordebugging.The tester or developer starts the IDz with a new or existing workspace, defines aconnection to the remote system if necessary, and connects to the remote system.The JCL for testing the batch application resides in a set of data sets.

Parent topic:Generating code coverage results by using the IDz client

190

1.2.

3.

A.

B.C.

4.5.

---

6.

Procedures After you verify the assumptions, you can complete steps to prepare code coverageresults for batch applications by using IDz client.

Navigate to a JCL data set, for example, VENKATU.INS.QUOTE.JCL. Open a batch JCL member file to test the Insurance quote batch application,example: INSQTE1.jcl.Add a set of statements in the JCL RUN or GO step to execute the batch programin the code coverage mode, for example: //CEEOPTS DO * TEST(,,,DBM%VENKATU)

ENVAR("EQA_STARTUP_KEY=CC,,testid=INSQTE1")

/* Note:

The above set of statements are additional directives to run or execute thebatch program in code coverage mode. VENKATU is the user id, which is optional.EQA_STARTUP_KEY=CC indicates that the code coverage mode and thetestid parameter, INSQTE1, are to pass in the name of the test case or aunique ID to be associated with the generated code coverage results.

Save the JCL by right clicking in the Editor or the JCL member and click Submit.Click any of the buttons on the dialog that pops up after the submission:

Click Locate Job to go to the node where the job status can be viewed.Click Notify to update the status bar when the job finishes execution.Click OK to close the dialog.

Figure 1. Dialog showing the successful submission of the job

On successful execution, view the code coverage results from the current run inthe Code Coverage Report.Figure 2. Sample showing the Code coverage resultdisplayed in Code Coverage results view

191

7.

8.

9.

Right click the code coverage result and select Export.Figure 3. Sample showingthe Export menu in Code coverage results view

In the dialog that pops up, browse to the location on the file system to where theresult is exported to, and specify a name for the output file. This will create acompressed file with the code coverage results from the test run. Figure 4.Sample showing file system organization of code coverage results

Repeat steps 1 - 8 for running the other JCL scripts that are intended to test thesame build of the same application and export the code coverage results to thesame location. .

Parent topic:Generating code coverage results by using the IDz client

192

-

-

Generating code coverage results by using theheadless collector running on ADI server You can generate code coverage results by using the headless collector running onADI server. Verify the assumptions before you perform this activity.

Assumption Verify the assumption before you prepare code coverage results by using theheadless code coverage collector.Procedures After you verify the assumptions, you can complete steps to prepare codecoverage results by using the headless code coverage collector.

Parent topic:Preparing code coverage results for batch applications

193

Assumption Verify the assumption before you prepare code coverage results by using theheadless code coverage collector. The ADI server is started and running. As a part of the ADI startup, the headlesscode coverage collector daemon is started. Parent topic:Generating code coverage results by using the headless collectorrunning on ADI server

194

1.

2.

3.

4.

Procedures After you verify the assumptions, you can complete steps to prepare code coverageresults by using the headless code coverage collector.

Create the data provider by following the instructions described in Adding aManual Builds data provider to collect data automatically. When you created the data provider, select the clipboard icon ( ) to copy thestartup key sample as shown:

To see the startup key sample, click the pencil icon ( ):

Provide the previous sample snippet to the test team to be inserted into the JCL: Example://CEEOPTS DD *TEST(,,,TCPIP&<adi server tcpip address>%8005:*)

ENVAR("EQA_STARTUP_KEY=CC,,providerid=BGMT7L,testid=<your test-id>")

/* The IP address is the IP address of the ADI server machine where the codecoverage collector daemon is running. It can be the IP address or the DNS nameof the server. Submitting this JCL results in the code coverage for the test casewith test case id HDLS6 to be generated to the ADI server for automaticcollection. The providerid parameter ensures that the results are grouped to theappropriate data provider. Code coverage files are saved to the directory adi-server location \adi\conf\headless-CC-files\providerid-file\program_datetime_id.cczip. When you refresh the data provider, these codecoverage files are deleted.

Parent topic:Generating code coverage results by using the headless collectorrunning on ADI server

195

-

-

Preparing code coverage results for CICStransactions by using the debug tool backend andIDz client By using the debug tool backend and IDz client, you can prepare code coverageresults for CICS transactions.

Assumptions Verify the assumptions before you prepare code coverage results for CICStransactions by using the debug tool backend and IDz client.Procedures After you verify the assumptions, you can complete steps to prepare codecoverage results for CICS transactions.

Parent topic:Preparing code coverage results for COBOL and PL/I

196

Assumptions Verify the assumptions before you prepare code coverage results for CICStransactions by using the debug tool backend and IDz client. Parent topic:Preparing code coverage results for CICS transactions by using thedebug tool backend and IDz client

197

1.

2.

3.4.

Procedures After you verify the assumptions, you can complete steps to prepare code coverageresults for CICS transactions. Complete the following steps to generate code coverage results for CICStransactions by using Debug Tool backend and IDz client.

Create a DTCN profile to collect the code coverage results for a transaction.Figure 1. Screen showing the DTCN profile creation primary menu

Specify User Id, Session Type to be TCP, and IP Address pointing to the IDzinstance where the code coverage results would be displayed. Specify the port onwhich the debug daemon on the client runs. The default port is 8001. Press PF9and enter the following ENVAR("EQA_STARTUP_KEY=CC,,testid=seps4") asshown in Figure 2 below. Figure 2. Screen showing DTCN secondary menu to specify the Code coverageinvocation environment variable

The ENVAR is the directive to capture code coverage and the testid parameter isfor passing in the test case id. Press PF3 and then PF4 to save the profile. On the IDz client, click Window > Open Perspective > Debug to switch to thedebug perspective and check the daemon which is listening on the specified portas shown in Figure 3 below. The default port is 8001.Figure 3. Screen shotshowing the verification of debug daemon running

Run the transaction, for example, SEPS.Get the code coverage results in the IDz code coverage view.Figure 4. Screenshowing the Code Coverage result in the Code Coverage results view

198

5.

Right-click each of the results and export the results into a compressed file.

Parent topic:Preparing code coverage results for CICS transactions by using thedebug tool backend and IDz client

199

-

-

Preparing code coverage results for COBOL andPL/I by using RTC You can generate code coverage results for COBOL and PL/I by using automatedbuilds provided by Rational Team Concert™ Enterprise Extensions (RTC EE). Also,you can connect ADI to this RTC EE server to collect the code coverage dataautomatically. Take the following procedures to set up RTC builds to generate the coverage data.For details about how to configure ADI to connect to RTC and retrieve the data, seeAdding a Rational Team Concert builds provider.

Assumptions Verify the assumptions before you prepare code coverage for COBOL and PL/I byusing RTC.Procedures After you verify the assumptions, you can complete steps to prepare codecoverage for COBOL and PL/I by using RTC.

Parent topic:Preparing code coverage results for COBOL and PL/I

200

-

-

-

-

Assumptions Verify the assumptions before you prepare code coverage for COBOL and PL/I byusing RTC.

The development team uses RTC EE for z Systems Build component to build theirCOBOL and PL/I artifacts and run either automated or manual tests as part of thatbuild process. A set of build definitions are created for the COBOL and PL/I applications beingmanaged by RTC EE. For more information, see Setting up Enterprise Extensionbuilds.RDz provided Host Utilities (GI13-2864) that offers the headless Code coveragesupport, which is installed and configured on the z/OS® machine. For moreinformation, see Chapter 6 in IBM Rational Developer for z Systems: CofigurationGuide.The test team uses the RDz provided headless Code Coverage setup toautomatically generate code coverage results files when you run a build.

Parent topic:Preparing code coverage results for COBOL and PL/I by using RTC

201

1.

2.

3.

1.

2.

Procedures After you verify the assumptions, you can complete steps to prepare code coveragefor COBOL and PL/I by using RTC. Extend the existing build definition to submit a set of JCL that triggers a manual orautomated test after a successful build.

Use the Eclipse RTC client and select the project for which you would want to runthe tests and capture code coverage results as part of the build process. Make sure that you installed all the binaries required by the build engine, that is,the correct version of Ant or Maven that your build scripts would be using.In other RAD online help pages, there are steps for installing additional binarieson the build engine such as the Eclipse Birt libraries. This is not required for usewith ADI, as ADI provides its own presentation of the code coverage results anddoes not require the Birt-based processing of the data described there.

On your Eclipse RTC rich client. Create an Ant post build script

Start your Eclipse RTC rich client and select the project or application for whichyou want to run the tests and gather code coverage results as part of the Buildprocess. If no projects are loaded, follow the standard RTC flow to load theproject(s).Refer to the following postbuild.xml sample to create an Ant script. You can startwith the provided sample and modify as appropriate. <?xml version="1.0"encoding="UTF-8"?>

<!--====================================

This Ant script calls the code coverage headless script

using the properties defined in the build definition.

=====================================-->

<project name="Code Coverage" default="all" xmlns:jazz="antlib:com.ibm.team.enterprise.anttasks"

xmlns:ac="antlib:net.sf.antcontrib" >

<taskdef resource="net/sf/antcontrib/antcontrib.properties"/>

<description>

This Ant file is used to run the Code Review and Code Coverage

applications. It publishes the results to the RTC repository.

</description>

<taskdef classname="com.ibm.team.build.ant.task.ArtifactFilePublisherTask"

name="artifactFilePublisher"/>

<taskdef name="junitLogPublisher" classname="com.ibm.team.build.ant.task.JUnitLogPublisherTask" />

<taskdef name="nunitLogPublisher" classname="com.ibm.team.build.ant.task.NUnitLogPublisherTask" />

<target name="main">

<property name="temp.dir" value="${team.enterprise.scm.fetchDestination}/tmp"/>

<mkdir dir="${temp.dir}"/>

<property name="rexx.dir" value="${jcl.dir}"/>

<!-- Convert and add execute permission -->

<exec executable="iconv" output="${rexx.dir}/getJobRC.rexx"><arg line="-f UTF-8 -t IBM-1047202

${rexx.dir}/getJobRC.rexx"/></exec>

<chmod perm="755" file="${rexx.dir}/getJobRC.rexx"/>

<!-- Convert and add execute permission -->

<exec executable="iconv" output="${jcl.dir}/renameZipFile.sh">

<arg line="-f UTF-8 -t IBM-1047 ${jcl.dir}/renameZipFile.sh"/>

</exec>

<fixcrlf srcdir="${jcl.dir}" includes="renameZipFile.sh" cr="remove" />

<chmod perm="755" file="${jcl.dir}/renameZipFile.sh" verbose="true"/>

<ac:for list="${jcl.list}" param="jobname" >

<sequential>

<echo message="*** Job to be executed @{jobname}" />

<property name="job" value="@{jobname}" />

<echo message="job property = ${job}" />

<antcall target="startCodeCoverageDaemon" />

<!-- Wait until the debug daemons are available for running code coverage sessions -->

<waitfor maxwait="3" maxwaitunit="minute" checkevery="5000">

<and>

<socket server="${IP}" port="${CC.PORT_1}"/>

</and>

</waitfor>

<echo message="Submit ${job} job" />

<submitJCL src="&quot;//'${resourceTeamPrefix}.JCL(${job})'&quot;"/>

<!-- Stop the code coverage debug daemon that is listening -->

<exec executable="${RDZ_UTIL_BIN}/ccstop"

dir="${team.enterprise.scm.fetchDestination}" spawn="true">

<env key="JAVA_HOME" value="${JAVA_HOME}"/>

<arg line = "${CC.PORT_1}"/>

</exec>

<waitfor maxwait="3" maxwaitunit="minute" checkevery="5000">

<and>

<available

file="${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}/cc_done" />

</and>

</waitfor>

203

<delete

file="${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}/cc_done" />

<exec executable="${jcl.dir}/renameZipFile.sh" dir="${jcl.dir}">

<arg line = "${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}"/>

<arg line = "HospitalApplication-CC-${buildLabel}-${job}.cczip"/>

</exec>

<!-- Publish Code Coverage Results -->

<antcall target ="publishResults"/>

<var name="job" unset="true"/>

</sequential>

</ac:for>

</target>

<!--====================================

Start the daemon listener for code coverage. This task is run as

a daemon because the end of it will never be reached (gets stuck in the

exec task)

=====================================-->

<target name="startCodeCoverageDaemon">

<exec executable="${RDZ_UTIL_BIN}/ccstop" dir="${team.enterprise.scm.fetchDestination}"

spawn="true">

<env key="JAVA_HOME" value="${JAVA_HOME}"/>

<arg line = "${CC.PORT_1}"/>

</exec>

<waitfor maxwait="3" maxwaitunit="minute" checkevery="5000">

<and>

<available

file="${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}/cc_done" />

</and>

</waitfor>

<delete file="${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}/cc_done" />

<property environment="env"/>

204

<mkdir dir = "${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}"/>

<mkdir dir = "${team.enterprise.scm.fetchDestination}/cc_1/workspace"/>

<!-- Invoke the headless code coverage using the ccstart command, the required parms are

passed in via the arg line -->

<exec executable="${RDZ_UTIL_BIN}/ccstart" dir="${team.enterprise.scm.fetchDestination}"

spawn="true"> <env key="JAVA_HOME" value="${JAVA_HOME}"/> <arg line = "-

port=${CC.PORT_1}"/> <arg line = "-zipresult"/> <arg line = "-

output=${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}"/> <arg line = "-

prevresultpath=PREV"/> <arg line = "-reportformat=HTML"/> <arg line = "-

data ${team.enterprise.scm.fetchDestination}/cc_1/workspace"/> <arg line = "-

savesource"/> </exec>

<!-- Nothing else in this task can be reached! This task gets stuck in the exec because the

program is a daemon-->

<touch file="${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}/cc_done" />

</target>

<!-- Submits the JCL -->

<macrodef name="submitJCL"> <attribute name="src"/> <attribute

name="sleepInterval" default="5"/> <attribute name="ignoreRC" default="0"/>

<sequential> <antcall target="doJCLSubmission"> <param name="src"

value="@{src}"/> <param name="sleepInterval" value="@{sleepInterval}"/>

<param name="ignoreRC" value="@{ignoreRC}"/> </antcall> </sequential>

</macrodef>

<target name="doJCLSubmission">

<property name="output.file" value="${temp.dir}/getJobRC.out"/>

<property name="result.file" value="${temp.dir}/getJobRC.result"/>

<delete file="${result.file}"/>

<exec executable="submit" outputproperty="job.id"><arg line="-j ${src}"/></exec>

<echo message="Submitted JCL from ${src}. Job ID: ${job.id}"/>

<exec executable="${rexx.dir}/getJobRC.rexx" output="${output.file}" append="false">

<arg value="${job.id}"/>

<arg value="${result.file}"/>

<arg value="${sleepInterval}"/>

</exec>

<echo message="*** REXX output ***"/>

<exec executable="cat"><arg value="${output.file}"/></exec>

<echo message="*** End REXX output ***"/>

<exec executable="cat" outputproperty="job.maxRC">

<arg value="${result.file}"/>

</exec>

<fail message="Mac RC from ${src} was: ${job.maxRC}">

<condition>205

3.

4.

<and>

<not><equals arg1="${job.maxRC}" arg2="0"/></not>

<not><equals arg1="${job.maxRC}" arg2="${ignoreRC}"/></not>

<not>

<and>

<isset property="shouldIgnoreWarnings"/>

<or>

<equals arg1="${job.maxRC}" arg2="1"/>

<equals arg1="${job.maxRC}" arg2="4"/>

</or>

</and>

</not>

</and>

</condition>

</fail>

</target>

<!--====================================

Execute an additional artifactFilePublisher command to upload the coverage result zip file to that it

appears in the downloadable artifacts section of a build result, i.e. the Downloads section of a build

result editor in the RTC rich client. The extension of the file should be .cczip and .zip so that ADI

easily can find and download the file when communicating with the RTC server.

=====================================-->

<target name="publishResults"> <artifactFilePublisher

repositoryAddress="${repositoryAddress}" userId="${userId}" passwordFile =

"${passwordFile}" buildResultUUID="${buildResultUUID}"

filePath="${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}/HospitalApplication-CC-

${buildLabel}-${job}.cczip" label="${job} Code Coverage Results for batch

COBOL source for SaylesDemo - Hospital Application" verbose="YES">

</artifactFilePublisher> <delete

dir="${team.enterprise.scm.fetchDestination}/cc/results_${buildLabel}" /> </target>

<target name="all" depends="main"/>

</project> The {jcl.dir} and {jcl.list} parameters in the previous ANT script define the locationof the set of JCL to be submitted and the list of JCL to be submitted. Thisinformation is conveyed to the build definition by using the Properties tab of theBuild definition. See the following example.

Then specify the ANT script as a "post build script" as part of the RTC EE builddefinition. Select the associated build definition for the project from the WorkItems perspective, open the build definition, navigate to the z/OS® DependencyBuild tab, and add the location of the created ANT script as shown below:

206

5.

6.A.

B.

Now you can run your build. When you finish, verify in IDz Eclipse client byopening the build result editor that you have coverage results available in aCoverage tab. Check the Downloads tab that for a coverage .cczip file availablefor downloads. You are now ready to consume these build results with ADI.

For information about setting up an ADI data provider that connects to yourRTC server and build definition, see Adding a Rational Team Concert Buildsdata provider.For how to collect the coverage from the latest build available in ADI, seeRefreshing the builds and code coverage data.

Parent topic:Preparing code coverage results for COBOL and PL/I by using RTC

207

-

-

Preparing code coverage results for Java You can learn how to prepare code coverage results for Java™.

Preparing code coverage results by using the RAD 9.5 code coverage solutions You can choose to generate code coverage results either by using IBM®Rational® Application Developer (RAD) client or Rational Team Concert™ (RTC)with RAD Quality Extensions. Preparing code coverage results by using the ADI code coverage generator You can use the code coverage generator that ships with ADI to prepare codecoverage results for Java.

Parent topic:Preparing external data sources

208

-

-

Preparing code coverage results by using the RAD9.5 code coverage solutions You can choose to generate code coverage results either by using IBM® Rational®Application Developer (RAD) client or Rational Team Concert™ (RTC) with RADQuality Extensions.

Preparing code coverage results for Java by using the RAD client You can generate code coverage results for Java by using the IBM RationalApplication Developer for WebSphere® Software (RAD) version 9.5.0.1.Preparing code coverage results for Java by using RTC with RAD QualityExtensions You can generate code coverage results for Java by using automated builds thatare provided by Rational Team Concert (RTC) and connect ADI to this RTC serverto collect the code coverage data automatically.

Parent topic:Preparing code coverage results for Java

209

-

-

Preparing code coverage results for Java by usingthe RAD client You can generate code coverage results for Java™ by using the IBM® Rational®Application Developer for WebSphere® Software (RAD) version 9.5.0.1.

Assumptions Verify the assumptions before you prepare code coverage results by using RADclient.Procedures After you verify the assumptions, you can complete steps to prepare codecoverage results for Java by using RAD client.

Parent topic:Preparing code coverage results by using the RAD 9.5 code coveragesolutions

210

--

-

-

-

Assumptions Verify the assumptions before you prepare code coverage results by using RADclient.

The developer has written JUnit tests for his Java™ classes.The tester or developer uses the RAD environment to run individual JUnit testsmanually.The tester has the optional Code Coverage capability that is installed in their RADenvironment. And the tester uses the latest version 9.5.0.1 that provides theEnhance Code Coverage capability.The tester uses only the Enhanced Code Coverage Test Runner to receive JUnittest-specific coverage results and exports each result as it owns results file for ADI. The tester runs all tests for each of new build of his code base again.

Parent topic:Preparing code coverage results for Java by using the RAD client

211

1.

2.3.

-

-

4.5.

6.

A.

B.C.

7.8.9.

10.-

-

-

1.

Procedures After you verify the assumptions, you can complete steps to prepare code coverageresults for Java™ by using RAD client. In RAD:

Review the details for Determining Code Coverage in the RAD 9.5 online helpand familiarize yourself with the options available to generate code coverageresults.Set up a Java project in RAD with the code base of the current build under test.Follow the steps described in Configuring the JUnit test runner for enhancedcode coverage in the RAD 9.5 online help to enable the enhanced coveragerunner for a specific test.

Create a new Run Configuration for each test so that you can run each testindividually.You can decide on the granularity of the test that ADI will recognize by definingthe Run Configuration to compose of just one JUnit test class or even one testmethod; or even a whole set of test classes by grouping them into a JUnit testsuite and defining a Run Configuration for that suite.

Execute the Run Configuration created in Step 3.The code coverage results for the executed configuration will appear at the topof the Code Coverage Results view in RAD. See Accessing the code coverageresults view in the RAD online help.Right-click the new result and select Export... from the context menu. Also, seeImport and export results in the RAD online help for more information.

In the dialog, select Coverage Data and Project Baseline as the artifacts toexport.Specify a destination folder where to export.Click Finish.

Navigate to the destination folder specified in Step 6 in Windows Explorer.You see the two exported files.Select the two files and create a zip file (do not select the parent folder as the zipfile must not contain any folders).Rename the zip file to the name of your test.

This step is important as the name of the zip file will determine the name of thetest as it appears in ADI.If you ran this test before for an earlier build of your code base you must makesure that the name is exactly the same as before so that ADI can map the testand compare its current results against it earlier results.For example, if you ran a JUnit test called com.example.app1.ExampleTestthen you want to name the zip file com.example.app1.ExampleTest.zip andupload it with that name to ADI. When you create a new build of your codebase and rerun the test to find regression, your want to again export thecoverage results after the test completed, export the files and zip them andthen call the zip file exactly the same as before so that ADI can compare theresult of the first with the second test.

In ADI:

Log on to ADI.

212

2.

3.

4.

5.

If you did not do so already, create a new Data Provider for your Java project.See Adding a manual build provider to collect data manually for details.If you or another tester did not do so already, create a new Build that reflects yourcurrent code base under test. Note, that when multiple testers submit their resultsagainst the same build the assumption ADI makes is that they all used the exactsame code base. See Adding a build to a manual build provider when collectingdata manually for details.Open the build information page and add the exported, zipped, and renamedcode coverage files created in Steps 6 to 10. See Updating an existing build fordetails.Review the results for this build in the Analysis pages to confirm that the testswere correctly imported and that the coverage percentage is the same as seen inthe RAD Coverage Results view. See Code Coverage Reports and Informationfor details.

Parent topic:Preparing code coverage results for Java by using the RAD client

213

-

-

Preparing code coverage results for Java by usingRTC with RAD Quality Extensions You can generate code coverage results for Java™ by using automated builds thatare provided by Rational Team Concert™ (RTC) and connect ADI to this RTCserver to collect the code coverage data automatically.

Assumptions Verify the assumptions before you prepare code coverage results by using RTCwith RAD Quality Extensions.Procedures After you verify the assumptions, you can complete steps to prepare codecoverage results by using RTC with RAD Quality Extensions.

Parent topic:Preparing code coverage results by using the RAD 9.5 code coveragesolutions

214

-

-

-

Assumptions Verify the assumptions before you prepare code coverage results by using RTC withRAD Quality Extensions.

The development team uses RTC's Build component to build their Java™ projectand run JUnit tests as part of that build.The development team uses the RAD Code Coverage Extension for RTC toautomatically generate code coverage results files when running a build.The automated creation of code coverage files is limited to a coarse-graineddefinition of ADI test cases. In fact, the most common case is that the execution ofall JUnit tests during a build results into one code coverage file, which is mappedto only one test in ADI, that is, all JUnit tests executed map to one ADI test. Toachieve a lower level of granularity, you can break your build into smaller groups oftest execution. Each execution would generate a code coverage file that covers theJUnit test executed in that unit to be mapped to one ADI test case. And each groupresults into a separate ADI test.

Parent topic:Preparing code coverage results for Java by using RTC with RADQuality Extensions

215

1.

2.

3.

1.

2.

-

-

3.

A.

B.

4.

Procedures After you verify the assumptions, you can complete steps to prepare code coverageresults by using RTC with RAD Quality Extensions. On your RTC build engine machine:

Ensure that RAD Code Coverage Extensions are installed on the RTC buildengine. For more information, see Installing the Build System Toolkit in the Jazzonline help and Installing code quality extension for continuous integration forRational Team Concert builds feature using Installation Manager in the RADonline help.Also make sure that you installed all the binaries that are required by the buildengine, for example, the correct version of Ant or Maven that your build scriptswould be using.In other RAD online help pages (referenced below), there are steps for installingadditional binaries on the build engine such as the Eclipse Birt libraries. This isnot required for use with ADI, as ADI provides its own presentation of the codecoverage results and does not require the Birt-based processing of the datadescribed there.

On your Eclipse RTC rich client. Alternative 1: create an ANT build script

Start your Eclipse RTC rich client and follow the steps described in Configuring abuild definition in Rational Team Concert in the RAD online help for creating anew build definition that use Ant on the build engine.Follow Steps 1 to 3 and 5 of Creating an Ant build script to generate codecoverage statistics in remote build environments in the RAD online help to createan Ant script that compiles and tests your code.

It is recommended that you start with the sample Ant script provided in SampleAnt script (build.xml) files for remote build environments and update/refine thescript for your needs.Step 5 described in Publishing results to the Rational Team Concert server inthe RAD online help uses the filePublisher command to publish the coverageresult and baseline files to the RTC server so that special RTC client extensionsfor Eclipse that are shipping with RAD and Rational® Software Architect canshow the results in a special Eclipse UI of the rich client. For ADI, you need totype a second command described in the next step.

In the Ant script, you need to execute an additional artifactFilePublisher commandto upload the coverage result compressed file to that it appears in thedownloadable artifacts section of a build result, that is, the Downloads section ofa build result editor in the RTC rich client. It is strongly recommended that yourename the file before uploading for two reasons:

The name of the zip file determines the name of the test in ADI under whichthe coverage results will be listed.The extension of the file should be .cczip and .zip so that ADI can find anddownload the file when communicating with the RTC server. For more details,see Adding a Rational Team Concert Builds data provider.

Example for renaming and uploading the .cczip file:<move file="${resultsDir}\Coveragedata-${buildLabel}.zip"

tofile="${resultsDir}\Coveragedata-${buildLabel}.cczip" />216

5.

6.A.

B.

1.

2.

3.

<artifactFilePublisher buildResultUUID="${buildResultUUID}"

repositoryAddress="${repositoryAddress}" userId="${UserId}"

passwordFile="${PasswordFile}" verbose="true"

filePath="${resultsDir}\Coveragedata-${buildLabel}.cczip"

label="Code coverage data file for ADI." /> Now you can run your build. When you finish, verify in the RSA or RAD Eclipseclient by opening the build result editor that you have coverage results available ina Coverage tab. Check the Downloads tab for a coverage .cczip file available fordownloads. You are now ready to consume these build results with ADI.

For setting up an ADI data provider that connects to your RTC server and builddefinition, see Adding a Rational Team Concert Builds data providerFor how to collect the coverage from the latest build available in ADI, seeRefreshing the builds and code coverage data

Alternative 2: create one or more Maven build scripts As an alternative to Ant, you can also use Maven to run your JUnit tests and collectcode coverage data. The advantage of Maven is that, it organizes JUnit tests in thesame Eclipse projects as the code under test and you could create an individualcode coverage result easily for each project. Therefore, you can have a more fine-grained representation of tests in ADI, that is, one test for each Maven project.

To learn more about getting started with building with Maven, start from this topicon jazz.net: A Jazz-based Maven build. You can learn the main idea for workingwith RTC from Maven to call the same Ant commands using Maven's ability toexecute Ant commands.When you create your RTC Build Definition for Maven, the key thing is that youprovide all Ant properties to Maven as JVM arguments following a simple schemaas in this example (just an example and not all the variables you might need): -DbuildLabel=${buildLabel} -DrepositoryAddress=${repositoryAddress} -DbuildResultUUID=${buildResultUUID}

.... Tip: As the RTC Build Definition editor only provides a single line editor, it is betterif you maintain the list of variable declarations in a text editor of your choice andthen paste it into RTC when ready. It is recommended that you add in each Maven project's POM file a profile that isonly executed when running on a build engine to generate coverage data. In thisway, you can still run Maven builds in your IDE without the need to generate codecoverage data and update RTC build requests. For example, you can add aprofile as follows. <profiles> <profile>

<id>build-engine</id>

<activation>

<property>

<name>buildLabel</name>

</property>

</activation>

<build>

<plugins> 217

4.

-

-

This profile checks for the existence of the buildLabel variable, which is definedby the RTC build engine. Therefore, it would only be executed when you run on abuild engine and not during development when you run in your Eclipse IDE. The following example now is one possible end-to-end way of defining the Mavenprofile. You can define this profile in each of your POM file or if you use ahierarchical POM file in your base pom file.

The example uses the following variable that should be declared in the JVMvariable section of the Maven RTC Build Definition. For more detials of thesevariables listed, see last bullet point.-DbuildLabel=${buildLabel} -DBuild_System_HOME=${Build_System_HOME} -DrepositoryAddress=${repositoryAddress} -DUserId=${UserId} -

DPasswordFile=${PasswordFile} -DbuildResultUUID=${buildResultUUID} -Dllc-engine-plugin=${llc-engine-

plugin} -Declipse-jdt-core-plugin=${eclipse-jdt-core-plugin} -Declipse-equinox-common-plugin=${eclipse-

equinox-common-plugin} -Dllc-common-plugin=${llc-common-plugin} -Dllc-jvmti-library=${llc-jvmti-

library} You can see the comments inside the following sample example. They map tothe steps of the Ant sample script shown in the RAD Online help that wasreferenced previously.<profile> <id>build-engine</id>

<activation>

<property>

<name>buildLabel</name>

</property>

</activation>

<build>

<plugins>

<plugin>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-antrun-plugin</artifactId>

<version>1.8</version>

<executions>

<execution>

<id>code-analysis</id>

<phase>compile</phase>

<configuration>

<target>

<!-- Analyze compiled src code: Generating .probescript and

.baseline -->

<taskdef name="code-coverage-app-analyzer"

classname="com.ibm.rational.llc.engine.instrumentation.anttask.CoverageApplicationAnalyzerTask">

<classpath>

<fileset dir="${Build_System_HOME}/codecoverage">

<include name="${llc-engine-plugin}" />

<include name="plugins/${eclipse-jdt-core-plugin}"

/>

<include name="plugins/${eclipse-equinox-common-

plugin}" />

<include name="plugins/${llc-common-plugin}" />

</fileset>218

</classpath>

</taskdef>

<code-coverage-app-analyzer

projectDir="${project.basedir}/target"

probescript="${project.basedir}/${project.groupId}.${project.artifactId}.probescript"

baseline="${project.basedir}/${project.groupId}.${project.artifactId}.baseline" />

<taskdef name="startBuildActivity"

classname="com.ibm.team.build.ant.task.StartBuildActivityTask">

<classpath>

<fileset dir="${Build_System_HOME}/buildtoolkit">

<include name="*.jar" />

</fileset>

</classpath>

</taskdef>

<startBuildActivity buildResultUUID="${buildResultUUID}"

repositoryAddress="${repositoryAddress}" userId="${UserId}"

passwordFile="${PasswordFile}" verbose="true"

autoComplete="true"

label="Building and testing

${project.groupId}.${project.artifactId}." />

</target>

</configuration>

<goals>

<goal>run</goal>

</goals>

</execution>

<execution>

<id>publish-cc-file</id>

<phase>package</phase>

<configuration>

<target>

<zip

destfile="${project.basedir}/${project.groupId}.${project.artifactId}.zip"

basedir="${project.basedir}"

includes="${project.groupId}.${project.artifactId}.coveragedata"

encoding="UTF-8" />

<!-- Publish the code coverage results as RTC contributions -->

<taskdef name="filePublisher"

classname="com.ibm.team.build.ant.task.FilePublisherTask">

<classpath>

<fileset dir="${Build_System_HOME}/buildtoolkit">

<include name="*.jar" />

</fileset>

</classpath>

</taskdef>

<filePublisher buildResultUUID="${buildResultUUID}"

repositoryAddress="${repositoryAddress}" userId="${UserId}"

passwordFile="${PasswordFile}"219

contributionTypeId="com.ibm.rational.llc.build.coverage"

verbose="true"

filePath="${project.basedir}/${project.groupId}.${project.artifactId}.zip"

label="Coveragedata File for ${project.groupId}.${project.artifactId}"

failOnError="false" />

<zip

destfile="${project.basedir}/${project.groupId}.${project.artifactId}-baseline.zip"

basedir="${project.basedir}"

includes="${project.groupId}.${project.artifactId}.baseline"

encoding="UTF-8" />

<filePublisher buildResultUUID="${buildResultUUID}"

repositoryAddress="${repositoryAddress}" userId="${UserId}"

passwordFile="${PasswordFile}"

contributionTypeId="com.ibm.rational.llc.build.baseline"

verbose="true"

filePath="${project.basedir}/${project.groupId}.${project.artifactId}-baseline.zip"

label="Baseline file for ${project.groupId}.${project.artifactId}"

failOnError="false" />

<!-- Publish the code coverage results to the downloads -->

<move

file="${project.basedir}/${project.groupId}.${project.artifactId}.zip"

tofile="${project.basedir}/${project.groupId}.${project.artifactId}.cczip" />

<taskdef name="artifactFilePublisher"

classname="com.ibm.team.build.ant.task.ArtifactFilePublisherTask">

<classpath>

<fileset dir="${Build_System_HOME}/buildtoolkit">

<include name="*.jar" />

</fileset>

</classpath>

</taskdef>

<artifactFilePublisher buildResultUUID="${buildResultUUID}"

repositoryAddress="${repositoryAddress}" userId="${UserId}"

passwordFile="${PasswordFile}" verbose="true"

filePath="${project.basedir}/${project.groupId}.${project.artifactId}.cczip"

label="Code coverage data for ${project.groupId}.${project.artifactId}" />

</target>

</configuration>

<goals>

<goal>run</goal>

</goals>

</execution>

</executions>

</plugin>

<plugin>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-surefire-plugin</artifactId>220

-

-

-

-

-A.

<version>2.9</version>

<!-- Execute tests with code coverage: .coveragedata -->

<configuration>

<argLine>-

Dcoverage.out.file=${project.basedir}/${project.groupId}.${project.artifactId}.coveragedata

-Xbootclasspath/a:${Build_System_HOME}/codecoverage/${llc-engine-plugin}

-agentpath:${llc-jvmti-

library}=JPIAgent:server=standalone,file=;ProbekitAgent:ext-pk-BCILibraryName=BCIEngProbe,ext-pk-

probescript=${project.basedir}/${project.groupId}.${project.artifactId}.probescript</argLine>

</configuration>

</plugin>

</plugins>

</build>

</profile> You can see in the previous example that the code coverage file is uploaded asa .cczip with the same name as the Maven artifact name defined in this project.This ensures that ADI will load these results as a test with that name. If youprefer a different name, ensure that the .cczip file is named accordingly.If you are running multiple POM files of this build, you need to have a parentPOM that is executed by the Build Definition, which then defines each otherPOM as a module running each project's build and tests and upload the resultsfor each project using the artifact name. The last part of this sample script that defines the argLine for running a JUnittest is slightly more complicated as in the Ant example. Because the Antconfiguration of the RAD code coverage toolkit defines those in macros that arenot available to Maven. Therefore, you must define these variable either as partof the Build Definition or part of the Maven POM file. The values to be used foryour current version of the RAD coverage toolkit is available in this file on thebuild engine:<rtc-build-install-dir>/buildsystem/codecoverage/CodeCoverageProperties.xml You would copy each value from that file and define the variables listed in theexample. For defining the them as part of your RTC Build Definition, you wouldenter the variables and values in the Properties tab of the build definitions asshown in the following screen capture.

Now you can run your build. When you finish, verify in RSA or RAD Eclipseclient by opening the build result editor that you have coverage results availablein a Coverage tab. Check the Downloads tab for a coverage .cczip file availablefor downloads. You are now ready to consume these build results with ADI.

For setting up an ADI data provider that connects to your RTC server and221

B.build definition, see Adding a Rational Team Concert Builds data providerFor how to collect the coverage from the latest build available in ADI, seeRefreshing the builds and code coverage data

Parent topic:Preparing code coverage results for Java by using RTC with RADQuality Extensions

222

1.

2.

-

-

Preparing code coverage results by using the ADIcode coverage generator You can use the code coverage generator that ships with ADI to prepare codecoverage results for Java™. The ADI code coverage generator provides the following enhanced capabilities overthe IBM® Rational® Application Developer (RAD) 9.5 generator.

It includes the source code into the code coverage results, which allows ADI toanalyze and relate code changes to code coverage results.It generates test result on the JUnit test method level, which gives ADI a muchfiner granularity of the results for analysis and results presentation.

Preparing code coverage results by using Apache Ant build scripts By using an Apache Ant build script template that you can adopt for your ownJava projects, you can execute the code coverage generator that is shipped withADI to prepare code coverage results. Preparing code coverage results by using Rational Team Concert Build andApache Ant You can use the ADI Apache Ant build script template as part of your Ant orMaven build scripts that you execute from a build automation system. You canprepare code coverage results by using Rational Team Concert™ Build (RTCBuild) and Apache Ant.

Parent topic:Preparing code coverage results for Java

223

-

-

-

-

Preparing code coverage results by using ApacheAnt build scripts By using an Apache Ant build script template that you can adopt for your ownJava™ projects, you can execute the code coverage generator that is shipped withADI to prepare code coverage results.

Assumptions Verify the assumptions before you prepare code coverage results for Java byusing Apache Ant script.Procedures After you verify the assumptions, you can complete steps to prepare codecoverage results for Java by using Apache Ant script.Reference of properties in build.properties Find the complete reference of all the properties that you can modify inbuild.properties.Next steps After you generate the code coverage results, you can find the next steps toperform more operations.

Parent topic:Preparing code coverage results by using the ADI code coveragegenerator

224

-

-

Assumptions Verify the assumptions before you prepare code coverage results for Java™ byusing Apache Ant script.

Apache Ant, JUnit jar, and Hamcrest jar are available as part of the prerequisitesfor running code coverage results in headless mode by using Ant build scripts.The code coverage generator works on Windows and Linux platforms. And theJava Runtime Environment is limited to IBM® 64-bit Java 7 or 8 Runtime only.

Parent topic:Preparing code coverage results by using Apache Ant build scripts

225

1.

2.3.

4.

5.

6.

--

Procedures After you verify the assumptions, you can complete steps to prepare code coverageresults for Java™ by using Apache Ant script. Generating code coverage results Complete the following steps to generate code coverage results:

You can find the libraries and scripts that are provided in the ADI installationfolder under install-dir/adi/ as shown in the following example./adi/ java-coverage/

plugins/

com.ibm.rational.llc.engine_1.1.xxx.v2016xxxx_xx/

org.eclipse.hyades.probekit_4.5.xxx.v2015xxxxxx/

org.eclipse.tptp.javaprofiler

ccapi_4.0.0.2016xxxx_xxxx.jar

com.ibm.rational.llc.common_1.1.400.v2016xxxx_xxxx.jar

com.ibm.rational.llc.junitcc_1.0.0.v2016xxxx_xxxx.jar

org.eclipse.equinox.common_3.6.200.v2013xxxx-xxxx.jar

org.eclipse.jdt.core_3.10.2.v2015xxxx-xxxx.jar

build.properties

build.xml

CoverageToolkitTaskDefsForADI.xml

generatePropertyFileForADI.[bat|sh]

ReadMe.txt

VehicleExample.zip Copy those files to your build or development machine.Run generatePropertyFileForADI.bat for the Windows platform andgeneratePropertyFileForADI.sh for the Linux platform to generateCodeCoverageProperties64.properties file. You can find this properties file in thecopy of the java-coverage directory you created in Step 2. Specify properties for build.properties file, such as the location of Jars to run JUnittest, directories that contain source code, compiled class files, testcases to run,and storage location of code coverage results and so on. For a complete list of allthe properties, see Reference of properties in build.properties. Run build.xml in command line. For example, run cd to change the directory inwhich build.xml is located and execute: ant The generation of code coverage results initiates.Find the code coverage results in the specified result directory. The file with thecczip extension includes all complete code coverage results and source as shownin the following example. CCtest_2016xxxx_xxxxxx.cczip Unzip the zip file to find the following files:

/src/ - src directory contains all source filesccdata - ccdata file contains code coverage statistics data

Generating code coverage results for the Exampleapplication

226

1.2.3.

4.5.

6.

ADI includes a simple Java program with JUnit tests that you can use to quicklygenerate code coverage results for learning and experimentation. You can thenupload those results to ADI to review them in the application.

Copy the entire /adi/java-coverage directory to a new location.In the copied directory, find and unzip the sample "VehicleExample.zip".Open the file build.properties in an editor and modify it to configure the correctpath for homeDir and resultsDir corresponding to the current location (that is,where you copied the directory in Step 1).Execute generatePropertyFileForADI to set other location specific variables.Run ant to execute the build.xml which compiles the project and executes variousJUnit tests.Find the result files in the resultsDir location that you specified in Step 3.

Parent topic:Preparing code coverage results by using Apache Ant build scripts

227

Reference of properties in build.properties Find the complete reference of all the properties that you can modify inbuild.properties. Table 1. Reference of properties in build.properties

Attribute Description RequiredhomeDir Specify the location

or directory where thejava project islocated.

Yes

resultName Specify the name touse for result files.

Yes

resultsDir Specify the path ordirectory where youwould like to store allthe result files.

Yes

junitJar Specify the path ofJUnit jar.

Yes

hamcrestJar Specify the path ofHamcrest jar.

Yes

binDir Specify the paths ordirectories where tostore the compiledjava .class files thatyou would like toanalyze codecoveragestatistics.For multiplepaths/directories:Splitby ";" for theWindowsplatformSplit by ":" forthe Linux platform

Yes

inputDir Specify the paths ordirectories where tostore the java sourcefiles that you wouldlike to analyze codecoverage statistics.For multiplepaths/directories:Splitby ";" for theWindowsplatformSplit by ":" forthe Linux platform

Yes

228

testCase Specify the testcase/class that youwould like to run andget code coveragestatistics results splitby a space betweentest cases/classes formultiple testcases/classes.

Yes

junitPath Specify the classpathfor the JUnit classes.For multiplepaths/directories:Splitby ";" for WindowsplatformSplit by ":" forLinux platform

Yes

jvmargs Specify extra JVMarguments, split by aspace.

No. This is optional. Itcan be used forspecify extramemory. Forexample: jvmargs=-Xmx200m

methodLevelCapture Specify whether tocapture JUnit methodlevel or not.

No. The default valueis true. If it's not setyet or set to true, itcaptures the JUnitmethod level. If it isset to false, it doesn'tcapture JUnit methodlevel (captures onlyJUnit class level).

haltonfailure To stop the buildprocess if a test failsset on (errors areconsidered failuresas well).

No. The default valueis off.

229

Parent topic:Preparing code coverage results by using Apache Ant build scripts

excludefilter Specify the fullpackage name andclass that you wouldlike to exclude incollecting codecoverage data. Youcan also specify thepath where containsthe file that listedmultiple package andclass name thatwould like to exclude.For more detailsavailable at:https://www.ibm.com/support/knowledgecenter/SSQ2R2_14.0.0/com.ibm.rational.llc.ui.doc/topics/tgranularfiltersupp.html.

No. Default is empty.For multiple filters,each separated by aspace. For example:excludefilter=com.ibm.vehicles.tests.TestCarcom.ibm.vehicles.tests.TestCarImproved

includefilter Specify full packagename and class thatyou would like toinclude in collectingcode coverage dataor you can alsospecify the pathwhere contains thefile that listed multiplepackage and classname that would liketo include. For moredetails available at:https://www.ibm.com/support/knowledgecenter/SSQ2R2_14.0.0/com.ibm.rational.llc.ui.doc/topics/tgranularfiltersupp.html.

No. Default is empty.For multiple filters,each separated by aspace. For example: includefilter=com.ibm.vehicles.tests.TestCarcom.ibm.vehicles.tests.TestCarImproved

230

Next steps After you generate the code coverage results, you can find the next steps to performmore operations. After you generate the code coverage results, create a manual data provider in ADIwith a first build. Then add the cczip file of code coverage results that you generatedto that build to upload those results. For more information about how to create a manual data provider, see Adding amanual build provider to collect data manually and its peer sections. Parent topic:Preparing code coverage results by using Apache Ant build scripts

231

-

-

-

Preparing code coverage results by using RationalTeam Concert Build and Apache Ant You can use the ADI Apache Ant build script template as part of your Ant or Mavenbuild scripts that you execute from a build automation system. You can preparecode coverage results by using Rational Team Concert™ Build (RTC Build) andApache Ant. You can use the Apache Ant build script template that is described in the previoustopic as a starting point for the Apache Ant script for your build automation. You canalso call this ADI Apache Ant build script from a Maven or other build technologythat supports calling Apache Ant scripts. Another option is to reverse engineer thescript and implement it with another technology that you would like to use. It requiresthat you execute the JUnit Runner that is provided with ADI and used in the ApacheAnt build script example to execute all tests and make sure the JUnit Runner is notfrom a third-party. The following example assumes that you are using RationalTeam Concert with Apache Ant.

Assumptions Verify the assumptions before you prepare code coverage results for Java byusing RTC Build and Ant.Procedures After you verify the assumptions, you can complete steps to prepare codecoverage results for Java by using RTC Build and Ant.Next steps After you generate the code coverage results, you can find the next steps toperform more operations.

Parent topic:Preparing code coverage results by using the ADI code coveragegenerator

232

-

--

-

-

Assumptions Verify the assumptions before you prepare code coverage results for Java™ byusing RTC Build and Ant.

The development team uses RTC Build version 6.0 or later to build theirapplication.The development team uses Ant to execute its RTC builds.The RTC build engine is set up and configured already. For details, see theRational Team Concert Online Help. Make sure that you have write access to thebuild engine server machine and the RTC Build installation directory.ADI is installed as described in Installation and setup. You are granted with readaccess to the ADI server machine and the ADI installation directory.RTC Build and ADI could be installed on the same server machine or two differentones. Make sure that you are granted with permissions to copy some files fromADI to the RTC installation directories. For example, you need to have permissionsto execute SSH copy (scp) operations, to transfer files via FTP, or to copy filesthrough a USB stick.

Parent topic:Preparing code coverage results by using Rational Team ConcertBuild and Apache Ant

233

1.

2.

3.

-

4.

5.

6.7.

-

-

-

8.

9.

10.

-

-

Procedures After you verify the assumptions, you can complete steps to prepare code coverageresults for Java™ by using RTC Build and Ant. Complete the following steps to prepare the code coverage results by using RTCBuild and Apache Ant.

On the ADI server machine, find the ADI installation directory such as/opt/ibm/adi/.On the RTC server machine, find the RTC Build installation directory. Forexample, /opt/ibm/rtcbuild.Copy the entire directory /adi/java-coverage/ from the ADI installation directoryto RTC Build installation directory under the subdirectory rtcbuild/buildsystem.

The resulting directory would look like this: /opt/ibm/rtcbuild/buildsystem/java-coverage. Inside that directory, you find another directory that is called pluginsand other files. For details about the files included, see the previous topicGenerating code coverage results.

On the RTC Build engine, run cd to change directory to /buildsystem/java-coverage.Execute generatePropertyFileForADI.bat on Windows andgeneratePropertyFileForADI.sh on Linux to generate a new file calledCodeCoverageProperties64.xml.In RTC, create a Build Engine and Build Definition for your build.Create your RTC Build Ant build script.

If you are not familiar with RTC Build, you can check Tutorial in the TeamConcert Online Help for an introduction. For more information about the Antbuild script file itself, see Getting Started with Ant scripts and RTC Build AntTasks.If you do not have an Ant build script, copy the files /buildsystem/java-coverage/build.xml and build.properties to your development project. Thesefiles need to be delivered to the RTC source control management system sothat they can be found when you build your application.If you already have an Ant build script for your RTC Build, integrate thecontents of the /buildsystem/java-coverage/build.xml and build.properties.

Complete the build.xml to build your project and then use the gen-result target torun all JUnit tests and generate the code coverage files.Check Reference of properties in build.properties for more details aboutproperties to configure. Configure the resultsDir property that defines the path where the resulting codecoverage result file (.cczip) is written when JUnit tests get executed. This resultfile needs to be uploaded to RTC server so that they appear in the Downloadstab of the build results record, where ADI downloads them from. To achieve this,augment your build.xml file with additional Jazz™ Ant task calls that will uploadthe code coverage files to the RTC build result record.

The Rational Team Concert Online Help provides a reference for the Ant tasksavailable.The task to use for uploading the code coverage files is calledartifactFilePublisher.

234

-

-

-

11.

An example for such a call in your build.xml Ant script would be:<artifactFilePublisher buildResultUUID="${buildResultUUID}"

repositoryAddress="${repositoryAddress}" userId="${UserId}"

passwordFile="${PasswordFile}" verbose="true"

filePath="${resultsDir}/${resultFileName}"

label="Code coverage data for my project." /> A good place for this task execution in the build.xml is at the end of the gen-result target, after the line <antcall target="delete-result" />. You need to include the definition of those RTC tasks at the beginning of yourbuild.xml file. For example, run a statement such as <importfile="${buildToolkitLocation}/BuildToolkitTaskDefs.xml" />. The ${} you wouldset for your RTC Build Engine record is Build Toolkit Install/buildsystem/buildtoolkit.

Execute your RTC builds. The result should be build records that includegenerated cczip file with the code coverage results available in the Downloadsection.

Parent topic:Preparing code coverage results by using Rational Team ConcertBuild and Apache Ant

235

Next steps After you generate the code coverage results, you can find the next steps to performmore operations. In ADI, create a connection and an automated data provider that connects to yourRTC Build Engine and Build Definition to collect the coverage result cczip filesautomatically. For more details, see Managing connections, providers, andapplications. Parent topic:Preparing code coverage results by using Rational Team ConcertBuild and Apache Ant

236

-

-

-

Managing connections, data providers, and analysiscollections To work with ADI, you need to know how to manage connections, data providers,and analysis collections. For the terminology of data providers and analysis collections, see TerminologyOverview page.

Managing connections For a data provider that stores data on the server, you must manage connectionsassociated with the data provider in order to connect the server for data collection.Only the users with data provider administrator role can add, edit, and deleteconnections from the system. Managing data providers Manual Builds data providers, Rational Team Concert Builds data providers,OMEGAMON for CICS data providers, and Application Discovery data providersare four types of data source available for ADI 5.0.2. Only the users with analysiscollection administrator role can create, modify, and delete data providers fordifferent data sources.Managing analysis collections To perform data analysis, you can associate data providers with an analysiscollection in the Analysis Collections view. Only the users with analysis collectionadministrator role can add and delete analysis collections from the system. Theusers with analysis collection owner role can modify the analysis collection such asediting analysis collection information, adding members to an analysis collection,and setting threshold value for different data providers.

Parent topic:IBM Application Delivery Intelligence 5.0.2

237

-

-

-

Managing connections For a data provider that stores data on the server, you must manage connectionsassociated with the data provider in order to connect the server for data collection.Only the users with data provider administrator role can add, edit, and deleteconnections from the system. For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users.

Adding connections For a data provider that stores data on the server, before adding a data provider tothe system, you must make sure that you created at least one connection for thedata provider.Editing connections You can edit the information of connection after you create at least oneconnection.Deleting a connection You can delete a connection from the system. When you delete a connection, youcannot undo the deletion or restore the connection. You cannot delete aconnection when it is being used by data providers. Before you delete aconnection, you need to make sure that you deleted the data providers that use theconnection.

Parent topic:Managing connections, data providers, and analysis collections

238

1.

2.

3.-

---

---

-

4.5.

Adding connections For a data provider that stores data on the server, before adding a data provider tothe system, you must make sure that you created at least one connection for thedata provider. Go to the Connections page and create a connection to connect the data providerserver. Currently, ADI offers three types of connections, including IBM RationalTeam Concert, IBM OMEGAMON for CICS, and IBM Application Discovery.Note:You need a data provider administrator role permission in order to perform this task.For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users. Complete the following steps to create a connection.

Select the Connections icon ( ) on the left menu to go to the Connectionspage.Note: You can add a connection when you create the data provider. If youwant to add a connection as part of creating a data provider, go to step 3 toprovide connection information in the Add Connection form. Click the Add icon ( ) next to the Connections header. The Add Connectionpage appears. Provide the following information in the Add Connection form.

Connection type: Select type of connection you want to create. Currently, IBMRational Team Concert, IBM OMEGAMON for CICS, and IBM ApplicationDiscovery are three types of connections that ADI offers.Name: Provide a unique name of the connection.Description: Provide short description of the connection.Connection URL: Provide the URL address of the location you want to connectto. For IBM Rational Team Concert, you need to provide the address of rootservice. Examples of URL addresses for different data providers:

IBM Rational Team Concert - https://hostname:9443/jazzIBM OMEGAMON for CICS - http://hostname:15200IBM Application Discovery - http://hostname:9091

Username and Password: Provide username and password of the person whohas access to the server you want to connect to. If it is available, you can usethe username and password of function users.

Click Test to test the connection.If the connection is a success, click Add to create the connection.

Parent topic:Managing connections

239

1.

2.

3.4.

5.

Editing connections You can edit the information of connection after you create at least one connection. Note: You need a data provider administrator role permission in order to edit theconnection information. For more information about roles and permissions for ADI,see Assigning role-based permissions to ADI users. Complete the following steps to edit the connection information:

Select the Connections icon ( ) on the left menu to go to the Connectionspage.Note: You can edit a connection when you create the data provider. If youwant to edit a connection as part of creating a data provider, go to step 3 to edit aconnection. Hover over the connection card you want to edit and point to it. Action iconsappear on the right corner of the data provider card. You can search theconnection card by typing part of the connection name in the search box on thetop right corner. The connection cards with corresponding name appear.Select the Edit icon.Edit the information such as name, description. URL, username, and password orall the information. If you update connection URL, you are required to retest theconnection before saving the changes.Click Save to update the changes.

Parent topic:Managing connections

240

1.

2.

3.

4.

Deleting a connection You can delete a connection from the system. When you delete a connection, youcannot undo the deletion or restore the connection. You cannot delete a connectionwhen it is being used by data providers. Before you delete a connection, you needto make sure that you deleted the data providers that use the connection. Note: You need a data provider administrator role permission in order to delete aconnection. For more information about roles and permissions for ADI, seeAssigning role-based permissions to ADI users. Complete the following steps to delete a connection.

Select the Connections icon ( ) on the left menu to go to the Connectionspage.Note: You can delete a connection when you create the data provider. If youwant to delete a connection as part of creating a data provider, go to step 3 todelete a connection. Hover over the connection card you want to delete and point to it. Action iconsappear on the right corner of the data provider card. You can search theconnection card by typing part of the connection name in the search box on thetop right corner. The connection cards with corresponding name appear.Select the Delete icon. The dialogue box to confirm that the connection deletionappears.Click OK to confirm the deletion or Cancel to cancel the deletion.

Parent topic:Managing connections

241

-

-

-

-

-

-

Managing data providers Manual Builds data providers, Rational Team Concert Builds data providers,OMEGAMON for CICS data providers, and Application Discovery data providers arefour types of data source available for ADI 5.0.2. Only the users with analysiscollection administrator role can create, modify, and delete data providers fordifferent data sources. To manage data providers, you need to have specific role-permissions. For moreinformation about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users. Besides role-based permissions, there is an access control for an analysis collectionif users want to edit or delete analysis collection. The users need to be an owner ofthe analysis collection to edit and delete that analysis collection regardless of anyrole permissions the users have. As a member of the analysis collection, users canonly view the reports and dashboards of that analysis collection. To improve the efficiency and performance of data collection, ADI automaticallyscrubs historical data at certain intervals (for example, every 24 hours) in your datawarehouse. There are two aspects of data scrub configuration:

Specify the number of days that you want to keep data in the data warehouse foranalysis in the data provider setting. You need to have a data provideradministrator role permission to perform this task. Configure the interval time for the data scrub task to run automatically in the ADIadministration page. The default value is 24 hours for ADI to run the data scrubtask in the background every 24 hours. You need to be an ADI administrator toperform this task. For more information, see Server settings that can be defined atruntime in the /adi/admin user interface.

Data providers To get started with ADI, first you need to define the data providers to collect datafrom the data sources for analysis. Currently, ADI offers four types of dataproviders, that is, Manual Builds data providers, Rational Team Concert Buildsdata providers, OMEGAMON for CICS data providers, and Application Discoverydata providers. Only for Manual Builds data providers, you can create the dataprovider to collect data manually or automatically.Managing Manual Builds data providers You can add Manual Builds data providers and modify the Manual Builds dataprovider information on the Data Providers page. Among four types of providersavailable for ADI, only for Manual Builds data providers, you can specify the dataprovider to collect data manually or automatically. Managing Rational Team Concert Builds data providers You can add and modify Rational Team Concert Builds data providers on DataProviders page. Only the users with data provider administrator can add and editRational Team Concert Builds data provider. The users with analysis collectionowner role can refresh builds data. Any of the role permissions can view buildsdata, delete builds and export builds data. Managing OMEGAMON for CICS data providers You can add and modify OMEGAMON for CICS data providers on DataProviders page.

242

-

-

Managing Application Discovery data providers You can add and modify Application Discovery data providers on the DataProviders page.Deleting a data provider When you delete a data provider, you delete all the collected data and analyticsresults for the analysis collections that are associated with this data provider.

Parent topic:Managing connections, data providers, and analysis collections

243

Data providers To get started with ADI, first you need to define the data providers to collect datafrom the data sources for analysis. Currently, ADI offers four types of data providers,that is, Manual Builds data providers, Rational Team Concert Builds data providers,OMEGAMON for CICS data providers, and Application Discovery data providers.Only for Manual Builds data providers, you can create the data provider to collectdata manually or automatically. Manual Builds data providers You can define a Manual Builds data provider that is defined by a baseline of thecode that you run coverage tests against. You can run many tests against that buildand upload coverage result compressed files for a build in which each compressedfile represents the results of exactly one test. When you change your code or yourtests, you must create a new build for that data provider by using the Add Builddialog. The assumption is that all test that ran against a particular build used theexact same version of all the code files tested. For more information, see Preparingcode coverage results for batch applications. Rational Team Concert Builds data providers An Rational Team Concert Builds data provider connects to an RTC instance basedon one or more connections defined, queries the builds, and gathers any codecoverage data included in the RTC builds for the selected project area and builddefinition. As part of the data provider creation, you can specify a build tag or moreto match one or more tags for the RTC builds to identify the set of builds that youwant ADI to query and inspect for code coverage data. OMEGAMON for CICS data providers An OMEGAMON for CICS data provider connects to an IBM OMEGAMON® forCICS® instance based on one or more connections defined to collect theoperations-related data, including response time, CPU time, and usage frequencyfor CICS transactions running in a CICSPlex. As part of the data provider creation,you can choose one or more transaction service classes for which you want ADI togather and present the data. For more information on IBM OMEGAMON for CICS,see IBM Tivoli OMEGAMON XE for CICS on z/OS product page . Application Discovery data providers An Application Discovery data provider connects to an IBM Application Discovery(AD) server instance and collects the inventory, code complexity, and code qualitymetrics for the AD projects. As part of the data provider creation, you can select oneproject or a set of projects for which you want to perform analysis. For moreinformation on IBM Application Discovery, see IBM Application Discovery productpage. Parent topic:Managing data providers

244

-

-

Managing Manual Builds data providers You can add Manual Builds data providers and modify the Manual Builds dataprovider information on the Data Providers page. Among four types of providersavailable for ADI, only for Manual Builds data providers, you can specify the dataprovider to collect data manually or automatically. Only the users with the data provider administrator role permission can add and editManual Builds provider. The users with the analysis collection owner role permissioncan refresh the code coverage data for a build. Any of the role permissions can addbuilds, edit builds, modify the Code Coverage files for a build and download codecoverage data. For more information about roles and permissions for ADI, seeAssigning role-based permissions to ADI users.

Adding a Manual Builds data provider For Manual Builds data providers, you can create a Manual Builds data provider tocollect data manually or automatically. Modifying the Manual Builds data providers After you add a Manual Builds data provider, you can modify the Manual Buildsdata provider on Data Provider page. ADI prevents the provider update bymultiple users. The page rejects all but one of many parallel updates by multipleusers.

Parent topic:Managing data providers

245

-

-

Adding a Manual Builds data provider For Manual Builds data providers, you can create a Manual Builds data provider tocollect data manually or automatically.

Adding a Manual Builds data provider to collect data manually You can go to the Data Providers page and create a Manual Builds data providerto manually collect the data from the data sources for analysis.Adding a Manual Builds data provider to collect data automatically You can go to the Data Providers page and create a Manual Builds data providerto collect the data from the data sources for analysis. Manual Builds data providerscan collect data manually or automatically.

Parent topic:Managing Manual Builds data providers

246

1.

2.

3.4.

-

---

-

----

5.

Adding a Manual Builds data provider to collectdata manually You can go to the Data Providers page and create a Manual Builds data provider tomanually collect the data from the data sources for analysis. Note: You need a data provider administrator role permission in order to add aManual Builds data provider. For more information about roles and permissions forADI, see Assigning role-based permissions to ADI users. Complete the following steps to add a Manual Builds data provider for manual datacollection.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Click the Add icon next to the Data Providers header. The Add Data Providerpage appears.Select the Manual Builds icon.Provide the following information in the First Build, Code Coverage Files, andData Provider Details forms.

First Build form. Provide the information of the first build you have for codecoverage analysis. If you have more than one build, the later build can be addedto the data provider when you modify the Manual Builds data provider.

Build Name: Provide a unique name for the build.Date of Build: Specify the date and time when the build is created.Description: Provide a short description of the build.

Code Coverage Files form. Click the Add icon to browse to the code coverageresult files. Select one or more files of code coverage results for this build. Thelist of the selected code coverage files appears along with the name of userswho upload the file and the description. You can add a description to each of thefile. This is an optional step. You can skip this step if you do not have codecoverage results for this build. For more information about how to prepare thecode coverage results, see Preparing code coverage results for batchapplications and Preparing code coverage results for CICS transactions byusing the debug tool backend and IDz client .Data Provider Details form.

Name: Provide a unique name for the data provider you create.Description: Provide a short description of the data provider.Select the number of days you want to keep data in the data warehouse. Bydefault, the value is set to All Data. All the data is kept in the data warehouse.You can set the value to 90 days, 180 days, or 360 days. The data that is olderthan the selected value will be cleaned out.

Click Add to create the Manual Builds data provider. Parent topic:Adding a Manual Builds data provider

247

1.

2.

1.

2.

3.4.

-

---

--

----

--

-

5.

Adding a Manual Builds data provider to collectdata automatically You can go to the Data Providers page and create a Manual Builds data provider tocollect the data from the data sources for analysis. Manual Builds data providers cancollect data manually or automatically. Notes:

Before you can add a Manual Builds data provider to collect data automatically,you need to make sure that the code coverage results are stored in the headless-cc-file directory.You need a data provider administrator role permission in order to add a ManualBuilds data provider. For more information about roles and permissions for ADI,see Assigning role-based permissions to ADI users.

Complete the following steps to add a Manual Builds data provider for automateddata collection:

Select the Data Providers icon ( ) on the menu to go to the Data Providerspage.Click the Add icon next to the Data Providers header. The Add Data Providerpage appears.Select the Manual Builds icon.Provide the following information in the First Build, Code Coverage Files, andData Provider Details forms.

First Build form. Provide the information of the first build you have for codecoverage analysis. If you have more than one build, the later build can be addedto the data provider when you modify the Manual Builds data provider.

Build Name: Provide a unique name for the build.Date of Build: Specify the date and time when the build is created.Description: Provide a short description of the build.

Code Coverage Files form.For automated data collection, no zip files to be added here. For procedure toset up the automated data collection, see Generating code coverage results byusing the headless collector running on ADI server.

Data Provider Details form. Name: Provide a unique name for the data provider you create.Description: Provide a short description of the data provider.Enable headless collection support: Check to enable headless collectionsupport. A dropdown menu of Collection Trigger appears.

Select Manual to allow users to trigger the data collection manually.Select Automatic and fill in the collection interval in hours to schedule theinterval time for data collection.

Select the number of days you want to keep data in the data warehouse. Bydefault, the value is set to All Data. All the data is kept in the data warehouse.You can set the value to 90 days, 180 days, or 360 days. The data that is olderthan the selected value will be cleaned out.

Click Add to create the Manual Builds data provider.

248

-

-

There will be no code coverage data loaded to the build after the Manual Builds dataprovider is created.

If you have put the code coverage data into the headless-cc-file directory asdescribed in Preparing external data sources, you need to refresh the dataprovider in order to collect data from the headless-cc-file directory. For moreinformation, see Refreshing the code coverage results for automatically datacollection.If you have not put the code coverage data collection in the headless-cc-filedirectory, follow the steps described Preparing external data sources to put thecode coverage data collection in the headless-cc-file directory.

Parent topic:Adding a Manual Builds data provider

249

-

-

-

-

-

-

-

Modifying the Manual Builds data providers After you add a Manual Builds data provider, you can modify the Manual Builds dataprovider on Data Provider page. ADI prevents the provider update by multipleusers. The page rejects all but one of many parallel updates by multiple users. Only the users with data provider administrator role permission modify the ManualBuilds data provider. The users with analysis collection owner can add buildsinformation. Any of the role permissions can view, update and delete buildsinformation. For more information about roles and permissions for ADI, seeAssigning role-based permissions to ADI users.

Editing the Manual Builds data provider information You can edit name, description, or both of the data provider. Adding a build to a Manual Builds data provider when collecting data manually When a new build with code coverage results is available, you can add a build tothe existing Manual Builds data provider which collects data manually.Adding a build to a Manual Builds data provider when collecting data automatically When a new build with code coverage results is available, you can add a build tothe existing Manual Builds data provider which collects data automatically.Refreshing the code coverage results for automatically data collection When the code coverage results are available in headless-cc-file folder of ADI,you can manually refresh the data collection. Updating an existing build You can update an existing build by modifying the build information.Deleting a build from the Manual Builds data provider On the Data Providers page, you can remove a build from the Manual Builds dataprovider.Downloading the code coverage data associated with build You can download the code coverage data that is associated with build to a .csvfile or .json file to be used by external analytics tools.

Parent topic:Managing Manual Builds data providers

250

1.

2.

3.4.

5.

6.7.

Editing the Manual Builds data provider information You can edit name, description, or both of the data provider. Note: You need a data provider administrator role permission in order to edit thedata provider information. For more information about roles and permissions for ADI,see Assigning role-based permissions to ADI users. Complete the following steps to edit the data provider information:

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to edit and point to it. Actionicons appear on the right corner of the data provider card. You can search dataproviders by typing part of the data provider name in the search box on the topright corner.Select the Edit icon.Modify the data provider details, such as name, description, connection and soon.Enable or disable headless collection support to switch between automatic datacollection and manual data collection by selecting or clearing the headlesscollection support check box.Modify number of days you want to keep data in the data warehouse.Click Save to update the changes or click Cancel to quit editing.

Parent topic:Modifying the Manual Builds data providers

251

1.

2.

3.4.

----

--

-

5.

Adding a build to a Manual Builds data providerwhen collecting data manually When a new build with code coverage results is available, you can add a build to theexisting Manual Builds data provider which collects data manually. Note: You need either the data provider administrator role or analysis collectionowner role permission to perform this task. For more information about roles andpermissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to add a build to a Manual Builds data provider whichcollects data manually.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to add a build to and point to it.Action icons appear on the right corner of the data provider card. You can searchdata providers by typing part of the data provider name in the search box on thetop right corner.Select the Add Build icon.Provide build information to the Add Build form.

Build Name: Provide a unique name for the build.Date of Build: Specify the date and time when the build is created.Description: Provide a short description of the build.Select Modified Files: Add the files that are modified from the previous build.

Select the files that you want to add from the list on the left.Click the > icon to add the files to modified file list.

Code Coverage Files: Click Add icon to browse and select one or more zip filesof code coverage results created by testing this build. The list of the selectedcode coverage files appear along with the Filename and Description. You canadd a description to each of the file.

Click Add to associate the new build with the data provider. Note: If two users upload files at the same time to the same build, the upload isstrictly sequential. You can adjust this timeouts in/Users/everardo/Downloads/adi/server/conf/adi/teamserver.properties and the valueis coverageFileStorageCheckoutTimeout. Parent topic:Modifying the Manual Builds data providers

252

1.

2.

3.4.

----

--

-

5.

Adding a build to a Manual Builds data providerwhen collecting data automatically When a new build with code coverage results is available, you can add a build to theexisting Manual Builds data provider which collects data automatically. Note: You need either the data provider administrator role or analysis collectionowner role permission to perform this task. For more information about roles andpermissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to add a build to a data provider which collects dataautomatically.

Select the Data Providers icon ( ) on the menu to go to the Data Providerspage.Hover over the data provider card that you want to add a build to and point to it.Action icons appear on the right corner of the data provider card. You can searchdata providers by typing part of the data provider name in the search box on thetop right corner.Select the Add Build icon.Provide build information to the Add Build form.

Build Name: Provide a unique name for the build.Date of Build: Specify the date and time when the build is created.Description: Provide a short description of the build.Select Modified Files: Add the files that are modified from the previous build.

Select the files that you want to add from the list on the left.Click the > icon to add the files to modified file list.

Code Coverage Files: No code coverage zip files to be added here. You needto make sure that the code coverage results for a new build are stored in theheadless-CC-file directory for ADI to collect data automatically. See Generatingcode coverage results by using the headless collector running on ADI server formore information.

Click Add to associate the new build with the data provider. There will be no code coverage data loaded to the build after adding a build to anexisting Manual Builds data provider. Next step, you need to refresh the dataprovider in order to collect data from the headless-cc-file directory. For moreinformation, see Refreshing the builds and code coverage data. Parent topic:Modifying the Manual Builds data providers

253

1.

2.

3.4.

Refreshing the code coverage results forautomatically data collection When the code coverage results are available in headless-cc-file folder of ADI, youcan manually refresh the data collection. For more information how the code coverage results are prepared for automaticallydata collection, see Generating code coverage results by using the headlesscollector running on ADI server. Note: You need either the data provider administrator role or analysis collectionowner role permission to refresh the code coverage results for automatically datacollection. For more information about roles and permissions for ADI, see Assigningrole-based permissions to ADI users. Complete the following steps to refresh the code coverage results for collect codecoverage data from headless-cc-file folder.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to collect the code coverage dataand point to it. Action icons appear on the right corner of the data provider card.You can search data providers by typing part of the data provider name in thesearch box on the top right corner.Select the Refresh icon. Data Collection dialogue box appears.Click Ok to perform data collection or Cancel to cancel the operation.

Parent topic:Modifying the Manual Builds data providers

254

1.

2.

3.

4.5.

--

--

---

---

-

--

-

-6.

Updating an existing build You can update an existing build by modifying the build information. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to update an existing build associated with the dataprovider:

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to update existing buildinformation and point to it. Action icons appear on the right corner of the dataprovider card. You can search data providers by typing part of the data providername in the search box on the top right corner.Select the List Builds icon. A list of all builds associated with the data providercard appears.On the row which displays a build that you want to modify, click the Edit icon.Modify the build information. You can perform the following activities to modifybuild information.

Modify build name, date of build, and description.Add modified files.

Select the files that you want to add from the list on the left.Click > icon to add the files to the modified file list.

Remove modified files. Select the files that you want to remove from the modified file list on the right.Click < icon to remove the files from the modified file list.

Add extra code coverage files to the build. Click the Add icon to browse to the code coverage files. Select one or more code coverage results to associate the files with the build.When you add existing code coverage files, the files replace the files that youadded previously.The list of the selected code coverage files appear along with the name ofusers who upload the file and description. You can add description next toeach of the file.

Update comments for code coverage files.Delete a code coverage file from the build.

Mouse over the code coverage file you want to delete. The Delete iconappears on the right.Select the Delete icon to delete the code coverage file from the build.

Click Save to update the changes. Parent topic:Modifying the Manual Builds data providers

255

1.

2.

3.

4.

5.

Deleting a build from the Manual Builds dataprovider On the Data Providers page, you can remove a build from the Manual Builds dataprovider. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to delete a build from its associated Manual Buildsdata provider.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to delete a build from and point toit. Action icons appear on the right corner of the data provider card. You cansearch data providers by typing part of the data provider name in the search boxon the top right corner.Select the List Builds icon to list all builds associated with Manual Builds dataprovider. A list of all builds associated with the Manual Builds data provider cardappears.On the row which displays a build that you want to delete, click the Remove icon.The dialogue box to confirm that the build deletion appears. Click Ok to confirm the deletion or Cancel to cancel the deletion.

Parent topic:Modifying the Manual Builds data providers

256

1.

2.

3.

4.

-

-

-

-

-

-

--

-

5.

6.7.

Downloading the code coverage data associatedwith build You can download the code coverage data that is associated with build to a .csv fileor .json file to be used by external analytics tools. Note: Any of the role permissions ca perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to download the code coverage data to a .csv file or.JSON file.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to download the code coveragedata and point to it. Action icons appear on the right corner of the data providercard. You can search data providers by typing part of the data provider name inthe search box on the top right corner.Select the Download icon. The Download Data page appears with the downloadform.Specify the following information to scope the code coverage results to bedownloaded.

Date Range: Specify the start date and end date of the code coverage results tobe downloaded.Included Code Coverage Data: Specify the information to be downloaded byselecting the following options.

Build Definitions: Select this option to download code coverage data from allbuild definitions.Build Results: Select this option to include build results with the codecoverage data.Test Results: Select this option to include test results with the code coveragedata.File Test Results: Select this option to include file test results with the codecoverage data.

Export Details: Specify the file name and file format to be downloaded. File Name: Fill in the name of the file in which you want data to bedownloaded.File Download Type: Specify the type of file to be downloaded. 2 types offiles, .csv and .json are available. By default the data will be downloaded in.csv file.

Click Download to download or Cancel to cancel the download action. When youclick Download, the download box appears.Select the Save File option and click OK.Select Save to download the file.Note: The downloaded file contains multiple filesof the file type that you select.

Parent topic:Modifying the Manual Builds data providers

257

258

-

-

Managing Rational Team Concert Builds dataproviders You can add and modify Rational Team Concert Builds data providers on DataProviders page. Only the users with data provider administrator can add and editRational Team Concert Builds data provider. The users with analysis collectionowner role can refresh builds data. Any of the role permissions can view builds data,delete builds and export builds data. For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users.

Adding a Rational Team Concert Builds data provider Go to the Data Providers page and create a Rational Team Concert Builds dataprovider to collect the data from the Rational Team Concert for analysis. Modifying the Rational Team Concert Builds data provider After you add an Rational Team Concert Builds data provider, you can modify theRational Team Concert Builds data provider, edit the data provider information,refresh the build data, delete a build from an existing data provider, and downloadcode coverage data associated with build. ADI prevents the data provider updateby multiple users. The page rejects all but one of many parallel updates by multipleusers.

Parent topic:Managing data providers

259

1.

2.

3.4.

5.6.

7.

8.

9.

10.-

Adding a Rational Team Concert Builds dataprovider Go to the Data Providers page and create a Rational Team Concert Builds dataprovider to collect the data from the Rational Team Concert for analysis. Note: You need a data provider administrator role permission to add a RationalTeam Concert Builds data provider. For more information about roles andpermissions for ADI, see Assigning role-based permissions to ADI users. Assumptions You have setup your Rational Team Concert build engine and build definition asdocumented in Preparing code coverage results for Java using Rational TeamConcert with RAD Quality Extensions or Preparing code coverage results forCOBOL and PL/I by using RTC. Procedures Take the following steps to add an RTC builds data provider.

Select the Data Providers icon ( ) on the left menu to go to the DataProviders page.Click the Add icon next to the Data Providers header. The Add Data Providerpage appears.Select the Rational Team Concert Builds icon.Select the Connection to connect to RTC server where the data is stored. Youcan search for the connection by typing part of the connection name in thesearch box on the right corner of Connection section. If the connection to RTCserver has not yet created, you can click the Add icon next to the Connectionheader to add a connection. For more information, see Adding connections.Note: You can also edit connection information or delete connection from hereby hovering over the connection card that you want to edit or delete. Then selectthe Edit or Delete icon. Click Connect to fetch build and code coverage data from RTC server.When the Project Area appears, select Project Area you want the dataprovider to collect the data from the drop down list.Build Definitions associated with selected Project Area are displayed. Select aBuild Definition you want to perform code coverage analysis. You can searchfor the build definition by typing part of the build definition name in the Searchbox on the right corner of Build Definitions section.Optional, specify Build Tags to filter only the builds you want to analyze codecoverage. In other words, only builds that have one of the tags listed assignedwill be considered.By default all files available for Download in an RTC build result that end with.cczip will be downloaded and analyzed by ADI. If your build results do not use.cczip extensions or you want to define a custom filter for which files to downloadand use then you select the check box of Use alternative regular file nameexpression to override. When you select the box, a text field appears thatallows to specify a regular expression that follows the pattern language defined. Provide the following information in the Data Provider Details forms.

Name: Provide a unique name for the data provider you create.

260

--

-

11.

Description: Provide a short description of the data provider.Collection Trigger: Specify whether you want data to be collected manually orautomatically. If you choose to select data automatically, specify the intervaltime of data to be collected in hours.Specify number of days you want to keep the data in the data warehouse. Bydefault, the value is set to All Data. All the data is kept in the data warehouse.You can set the value to 90 days, 180 days, or 360 days. The data that is olderthan the selected value will be cleaned out.

Note: If the data collection fails due to memory issues, the administrator can setthe memory parameters to be used during data collection. For more information,see Server configuration settings. Click Add to create the Rational Team Concert Builds data provider.

Note: Once the project area and build definition is selected, you cannot modify them. Parent topic:Managing Rational Team Concert Builds data providers

261

-

-

-

-

-

Modifying the Rational Team Concert Builds dataprovider After you add an Rational Team Concert Builds data provider, you can modify theRational Team Concert Builds data provider, edit the data provider information,refresh the build data, delete a build from an existing data provider, and downloadcode coverage data associated with build. ADI prevents the data provider update bymultiple users. The page rejects all but one of many parallel updates by multipleusers. To edit or delete the Rational Team Concert builds provider, you need to have adata provider administrator role permission. To refresh the builds data, you need to have either a data provider administrator rolepermission or a analysis collection owner role permission. Any of the role permissions can view the builds data and download the codecoverage data. For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users.

Editing the Rational Team Concert Builds data provider information You can edit the Rational Team Concert Builds data provider information such asname, description, or update RTC settings including build tags and alternativeregular file name expression. Refreshing the builds and code coverage data You can refresh the data provider to manually retrieve more build data.Viewing builds data of the Rational Team Concert Builds data provider You can view the builds data and status of their data collection of the RationalTeam Concert Builds data provider.Deleting a build from the Rational Team Concert data provider For an existing Rational Team Concert Builds provider, you can remove a buildfrom the Rational Team Concert data provider.Downloading the code coverage data associated with build You can download the code coverage data that is associated with build to a .csvor .json file to be used by external analytics tools.

Parent topic:Managing Rational Team Concert Builds data providers

262

1.

2.

3.4.

--

5.

6.

Editing the Rational Team Concert Builds dataprovider information You can edit the Rational Team Concert Builds data provider information such asname, description, or update RTC settings including build tags and alternativeregular file name expression. Note: You need a data provider administrator role permissions to perform this task.For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users. Complete the following steps to edit the Rational Team Concert Builds data providerinformation:

Select the Data Providers icon ( ) on the left menu to go to Data Providerspage.Hover over the data provider card that you want to edit and point to it. Actionicons appear on the right corner of the data provider card. You can search dataproviders by typing part of the data provider name in the search box on the topright corner.Select the Edit icon.Modify one or all of the following RTC setting information.Note: The project areaand build definition cannot be modified once they are selected.

Build TagsAlternative regular file name expression to override

Modify the name, description, collection trigger, number of days you want to keepdata in the data warehouse or all information of the data provider.Note: TheConnection for the data provider cannot be modified. Click Save to update the changes or click Cancel to quit editing.

Parent topic:Modifying the Rational Team Concert Builds data provider

263

1.

2.

3.4.

Refreshing the builds and code coverage data You can refresh the data provider to manually retrieve more build data. The builds and code coverage data that is associated with the builds can berefreshed manually from the RTC server. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to refresh the builds and code coverage data.

Select the Data Providers icon ( ) on the menu to go to the Data Providerspage.Hover over the data provider card that you want to refresh the code coveragedata for the builds and point to it. Action icons appear on the right corner of thedata provider card. You can search data providers by typing part of the dataprovider name in the search box on the top right corner.Select the Refresh icon. Data Collection dialogue box appears.Click Ok to perform manual refresh or Cancel to cancel the operation.

Parent topic:Modifying the Rational Team Concert Builds data provider

264

1.

2.

3.

4.

Viewing builds data of the Rational Team ConcertBuilds data provider You can view the builds data and status of their data collection of the Rational TeamConcert Builds data provider. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Take the following steps to view builds data.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the Rational Team Concert Builds data provider card that you want toview the builds data and point to it. Action icons appear on the right corner of thedata provider card. You can search data providers by typing part of the dataprovider name in the search box on the top right corner.Select the List Builds icon. A list of all builds associated with the data providercard appears with code coverage information.Select the Check icon on the right side to view the log indicating the status of datacollection.Note: If the data collection fails due to memory issues, the administratorcan set the memory parameters to be used during data collection. For moreinformation, see Server settings that can be defined at runtime in the /adi/adminuser interface.

Parent topic:Modifying the Rational Team Concert Builds data provider

265

1.2.

3.

4.

5.

Deleting a build from the Rational Team Concertdata provider For an existing Rational Team Concert Builds provider, you can remove a build fromthe Rational Team Concert data provider. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to delete a build from its associated data provider.

Select the Data Providers icon ( ) to go to the Data Providers page.Hover to the Rational Team Concert Builds data provider card that you want todelete a build and point to it. Action icons appear on the right corner of the dataprovider card. You can search data providers by typing part of the data providername in the search box on the top right corner.Select the List Builds icon to list all builds associated with data provider. A list ofall builds associated with the data provider card appears.On the row that displays a build that you want to delete, click the Remove icon.The dialogue box to confirm that the build deletion appears.Click Ok to confirm the deletion or Cancel to cancel the deletion.

Parent topic:Modifying the Rational Team Concert Builds data provider

266

1.

2.

3.4.

-

-

-

-

-

-

---

5.

6.7.

Downloading the code coverage data associatedwith build You can download the code coverage data that is associated with build to a .csv or.json file to be used by external analytics tools. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to download the code coverage data to a .csv file or.json file.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over to the data provider card that you want to download the codecoverage results and point to it. Action icons appear on the right corner of thedata provider card. You can search data providers by typing part of the dataprovider name in the search box on the top right corner.Select the Download icon. Download Data page appears.Specify the following information to scope the code coverage results to bedownloaded.

Date Range: Specify the start date and end date of the code coverage results tobe downloaded.Included Data: Specify the information to be downloaded by selecting thefollowing options.

Build Definitions: Select this option to download code coverage data from allbuild definitions.Build Results: Select this option to include build results with the codecoverage data.Test Results: Select this option to include test results with the code coveragedata.File Test Results: Select this option to include file test results with the codecoverage data.

Export Details: Specify the name and the file format of the file to download.File Name: Specify the name of the file to download to.File Format: Specify the type of file to be downloaded. 2 types of files, CSVand JSON are available. By default the data will be downloaded in .csv file.

Click Download to export or Cancel to cancel the export option. When you clickDownload, the download box appears.Select the Save File option and click OK.Click Save to download the file.

Note: The downloaded file contains multiple files of the file type that you select. Parent topic:Modifying the Rational Team Concert Builds data provider

267

-

-

Managing OMEGAMON for CICS data providers You can add and modify OMEGAMON for CICS data providers on Data Providerspage. Only the users with data provider administrator can add and edit OMEGAMON forCICS data provider. Any of the role permissions can view data collection logs anddownload OMEGAMON for CICS data. For more information about roles andpermissions for ADI, see Assigning role-based permissions to ADI users.

Adding an OMEGAMON for CICS data provider Go to the Data Providers page and create an OMEGAMON for CICS dataprovider to collect data from the data sources for analysis. Before you can add anOMEGAMON for CICS data provider, you must create at least one connection thatconnects the data provider to OMEGAMON for CICS server.Modifying the OMEGAMON for CICS data provider After you add an OMEGAMON for CICS data provider, you can modify theOMEGAMON for CICS data provider information, view the data collection logs anddownload the OMEGAMON for CICS data. ADI prevents the data provider updateby multiple users. The page rejects all but one of many parallel updates by multipleusers.

Parent topic:Managing data providers

268

1.2.

3.4.

5.

6.

7.---

-

8.

Adding an OMEGAMON for CICS data provider Go to the Data Providers page and create an OMEGAMON for CICS data providerto collect data from the data sources for analysis. Before you can add anOMEGAMON for CICS data provider, you must create at least one connection thatconnects the data provider to OMEGAMON for CICS server. Note: You need a data provider administrator role permission in order to perform thistask. For more information about roles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to add an OMEGAMON for CICS data provider fordata collection.

Select the Data Providers icon ( ) on the menu to go to the Providers page.Click the Add icon next to the Providers header. The Add Provider pageappears.Select the OMEGAMON for CICS card.Select the Connection to connect OMEGAMON for CICS server where the datais stored. You can search for the connection by typing part of the connectionname in the search box on the right corner of Connection section. If theConnection to OMEGAMON for CICS server has not been created, you cancreate the connection by clicking the Add icon next to the Connection header. Formore information about how to create a connection, see Adding connections.Note: You can also edit connection information or delete connection from here byhovering over the connection card that you want to edit or delete. Then select theEdit or Delete icon. Click Connect to fetch data from OMEGAMON for CICS server. Provider andPlexes data appear.Select Provider and Plexes from which you want the data provider to collect thedata. You can search for the Plexes by typing part of the Plexes name in thesearch box on the right corner of Plexes section.Note: A plex can be used by onlyone OMEGAMON for CICS data provider. Provide the following information in the Data Provider Details section.

Name: Provide a unique name for the data provider you create.Description: Provide a short description of the data provider.Data collection: Specify whether you want data to be collected manually orautomatically. If you choose to select data automatically, specify the intervaltime of data to be collected in hours.Specify number of days you want to keep the data in the data warehouse. Bydefault, the value is set to All Data. All the data is kept in the data warehouse.You can set the value to 90 days, 180 days, or 360 days. The data that is olderthan the selected value will be cleaned out.

Note: If the data collection fails due to memory issues, the administrator can setthe memory parameters to be used during data collection. For more information,see Server settings that can be defined at runtime in the /adi/admin user interface. Click Add to create the OMEGAMON for CICS data provider.

Parent topic:Managing OMEGAMON for CICS data providers

269

270

-

-

-

Modifying the OMEGAMON for CICS data provider After you add an OMEGAMON for CICS data provider, you can modify theOMEGAMON for CICS data provider information, view the data collection logs anddownload the OMEGAMON for CICS data. ADI prevents the data provider updateby multiple users. The page rejects all but one of many parallel updates by multipleusers. Only the users with a data provider administrator role can edit the data providerinformation. Any of the role permissions can view the data collection logs forOMEGAMON for CICS data provider. For more information about roles andpermissions for ADI, see Assigning role-based permissions to ADI users.

Editing the OMEGAMON for CICS data provider information You can edit name, description, or both of the OMEGAMON for CICS dataprovider. Only the data provider details such as name, description, and datacollection and number of days to keep data in the data warehouse can be edited.ADI prevents the provider to be updated by multiple users. The page rejects all butone of many parallel updates by multiple users.Viewing OMEGAMON for CICS data collection logs You can view the status of OMEGAMON for CICS data collection.Downloading the OMEGAMON for CICS data You can download the OMEGAMON for CICS data to a .csv file or .json file to beused by external analytics tools.

Parent topic:Managing OMEGAMON for CICS data providers

271

1.

2.

3.4.

5.

Editing the OMEGAMON for CICS data providerinformation You can edit name, description, or both of the OMEGAMON for CICS data provider.Only the data provider details such as name, description, and data collection andnumber of days to keep data in the data warehouse can be edited. ADI prevents theprovider to be updated by multiple users. The page rejects all but one of manyparallel updates by multiple users. Note: You need a data provider administrator role permission in order to perform thistask. For more information about roles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to edit the OMEGAMON for CICS data providerinformation.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to edit and point to it. Actionicons appear on the right corner of the data provider card. You can search dataproviders by typing part of the data provider name in the search box on the topright corner.Select the Edit icon.Modify the name, description, data collection, or all information of the dataprovider details.Note: The Connection for the data provider cannot be modified. Click Save to update the changes or click Cancel to quit editing.

Parent topic:Modifying the OMEGAMON for CICS data provider

272

1.

2.

3.

4.

Viewing OMEGAMON for CICS data collection logs You can view the status of OMEGAMON for CICS data collection. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to view OMEGAMON for CICS data collection.

Select the Data Providers icon ( ) on the left menu to go to Data Providerspage.Hover over the data provider card that you want to view the data collection logsand point to it. Action icons appear on the right corner of the data provider card.You can search data providers by typing part of the data provider name in thesearch box on the top right corner.Select the List Logs icon. A list of collected date and time data appears. The logsare group by the hours when they are collected.Select the date and time you want to view the data collection logs. Logs of thedata collection status appear.Note: If the data collection fails due to memoryissues, the administrator can set the memory parameters to be used during datacollection. For more information, see Server settings that can be defined atruntime in the /adi/admin user interface.

Parent topic:Modifying the OMEGAMON for CICS data provider

273

1.

2.

3.4.

-

--

--

5.

6.7.

Downloading the OMEGAMON for CICS data You can download the OMEGAMON for CICS data to a .csv file or .json file to beused by external analytics tools. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to download the OMEGAMON for CICS data to a .csvfile or .json file.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to download the OMEGAMON forCICS data and point to it. Action icons appear on the right corner of the dataprovider card. You can search data providers by typing part of the data providername in the search box on the top right corner.Select the Download icon. The Download Data page appears.Specify the following information to scope the data to be downloaded.

Date Range: Specify the start date and end date of the code coverage results tobe exported.Included Data: Select the projects to be packaged in the download.Export Details:

File Name: Specify the name of the file to download to.File Format: Specify the type of file to be downloaded. 2 types of files, CSVand JSON are available. By default the data will be downloaded in .csv file.

Click Download to download or Cancel to cancel the export option. When youclick Download, the download box appears.Select the Save File option and click OK.Click Save to download the file.

Note: The downloaded file contains multiple files of the file type that you select. Parent topic:Modifying the OMEGAMON for CICS data provider

274

-

-

Managing Application Discovery data providers You can add and modify Application Discovery data providers on the DataProviders page. Only the users with data provider administrator can add and edit ApplicationDiscovery data provider. Any of the role permissions can refresh the ApplicationDiscovery data, view data collection logs and download Application Discovery data.For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users.

Adding an Application Discovery data provider Go to the Data Providers page and create an Application Discovery data providerto collect the data from the Application Discovery server for analysis. Modifying the Application Discovery data provider After you add an Application Discovery data provider, you can edit the dataprovider information, refresh the data, view the data collection logs and downloadApplication Discovery data. ADI prevents the data provider updates by multipleusers. The page rejects all but one of many parallel updates by multiple users.

Parent topic:Managing data providers

275

1.

2.

3.4.

5.---

-

6.

Adding an Application Discovery data provider Go to the Data Providers page and create an Application Discovery data providerto collect the data from the Application Discovery server for analysis. Note: You need a data provider administrator role permission in order to perform thistask. For more information about roles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to add an Application Discovery data provider for datacollection.

Select the Data Providers icon ( ) on the menu to go to the Data Providerspage.Click the Add icon next to the Data Providers header. The Add Provider pageappears.Select the Application Discovery card.Select the Connection to connect to AD server where the data is stored. You cansearch for the connection by typing part of the connection name in the search boxon the right corner of Connection section. If the Connection to AD server has notbeen created, you can create the connection by clicking the Add icon next to theConnection header. See Adding connections for more detail how to create aconnection.Note: You can also edit connection information or delete connectionfrom here by hovering over the connection card that you want to edit or delete.Then select the Edit or Delete icon. Provide the following information in the Provider Settings forms.

Name: Provide a unique name for the data provider you create.Description: Provide a short description of the data provider.Collection Trigger: Specify whether you want data to be collected manually orautomatically. If you choose to select data automatically, specify the intervaltime of data to be collected in hours.Specify number of days you want to keep the data in the data warehouse. Bydefault, the value is set to All Data. All the data is kept in the data warehouse.You can set the value to 90 days, 180 days, or 360 days. The data that is olderthan the selected value will be cleaned out.Note: If the data collection fails dueto memory issues, the administrator can set the memory parameters to be usedduring data collection. For more information, see Server settings that can bedefined at runtime in the /adi/admin user interface.

Click Add to create the Application Discovery data provider. Parent topic:Managing Application Discovery data providers

276

-

-

-

-

Modifying the Application Discovery data provider After you add an Application Discovery data provider, you can edit the data providerinformation, refresh the data, view the data collection logs and download ApplicationDiscovery data. ADI prevents the data provider updates by multiple users. The pagerejects all but one of many parallel updates by multiple users. Only the users with a data provider administrator role can edit the data providerinformation. Any of the role permissions can refresh the data and view the datacollection logs for Application Discovery data provider. For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users.

Editing the Application Discovery data provider information For an Application Discovery data provider, you can edit the data provider details,such as name, description, collection trigger, or number of days you want to keepthe data in the data warehouse.Refreshing the data collected from Application Discovery server You can refresh the Application Discovery data provider to manually retrieve moredata from AD server.Viewing Application Discovery data collection logs You can view the status of Application Discovery data collection.Downloading the Application Discovery data You can download the Application Discovery data to a .csv file or .json file to beused by external analytics tools.

Parent topic:Managing Application Discovery data providers

277

1.

2.

3.4.

5.

Editing the Application Discovery data providerinformation For an Application Discovery data provider, you can edit the data provider details,such as name, description, collection trigger, or number of days you want to keepthe data in the data warehouse. Complete the following steps to edit the Application Discovery data providerinformation.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to edit and point to it. Actionicons appear on the right corner of the data provider card. You can search dataproviders by typing part of the data provider name in the search box on the topright corner.Select the Edit icon.Modify the name, description, or collection trigger, number of days you want tokeep the data in the data warehouse or all information of the provider detailedinformation.Note: The Connection for the data provider cannot be modified. Click Save to update the changes or Cancel to quit editing.

Parent topic:Modifying the Application Discovery data provider

278

1.

2.

3.4.

Refreshing the data collected from ApplicationDiscovery server You can refresh the Application Discovery data provider to manually retrieve moredata from AD server. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to refresh the data from Application Discovery server.

Select the Data Providers icon ( ) on the menu to go to the Data Providerspage.Hover over the data provider card that you want to edit and point to it. Actionicons appear on the right corner of the data provider card. You can search dataproviders by typing part of the data provider name in the search box on the topright corner.Select the Refresh icon. Data Collection dialogue box appears.Click Ok to perform a manual refresh or Cancel to cancel the operation.

Parent topic:Modifying the Application Discovery data provider

279

1.

2.

3.

Viewing Application Discovery data collection logs You can view the status of Application Discovery data collection. Note: Any of the role permissions can perform this task. For more information aboutroles and permissions for ADI, see Assigning role-based permissions to ADI users. Complete the following steps to view Application Discovery data collection.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to edit and point to it. Actionicons appear on the right corner of the data provider card. You can search dataproviders by typing part of the data provider name in the search box on the topright corner.Select the List Logs icon. A list of the date and time data that are collectedappears.Note: If the data collection fails due to memory issues, the administratorcan set the memory parameters to be used during data collection. For moreinformation, see Server settings that can be defined at runtime in the /adi/adminuser interface.

Parent topic:Modifying the Application Discovery data provider

280

1.

2.

3.4.

-

--

--

5.

6.7.

Downloading the Application Discovery data You can download the Application Discovery data to a .csv file or .json file to beused by external analytics tools. Note: Any of the role permissions can perform this task. See ADI role-basedpermissions for more information. For more information about roles and permissionsfor ADI, see Assigning role-based permissions to ADI users. Complete the following steps to download the Application Discovery data to a csvfile or .json file.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to download the ApplicationDiscovery data and point to it. Action icons appear on the right corner of the dataprovider card. You can search data providers by typing part of the data providername in the search box on the top right corner.Select the Download icon. The Download Data page appears.Specify the following information to scope the data to be downloaded.

Date Range: Specify the start date and end date of the code coverage results tobe exported.Included Data: Select the projects to be packaged in the download.Export Details:

File Name: Specify the name of the file to download to.File Format: Specify the type of file to be downloaded. 2 types of files, CSVand JSON are available. By default the data will be downloaded in .csv file.

Click Download to download or Cancel to cancel the export option. When youclick Download, the download box appears.Select the Save File option and click OK.Click Save to download the file.

Note: The downloaded file contains multiple files of the file type that you select. Parent topic:Modifying the Application Discovery data provider

281

1.

2.

3.

4.

Deleting a data provider When you delete a data provider, you delete all the collected data and analyticsresults for the analysis collections that are associated with this data provider. Note: You need a data provider administrator role permission in order to perform thistask. For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users. Complete the following steps to delete a data provider.

Select the Data Providers icon ( ) on the left menu to go to the Data Providerspage.Hover over the data provider card that you want to delete and point to it. Actionicons appear on the right corner of the data provider card. You can search dataproviders by typing part of the data provider name in the search box on the topright corner.Select the Delete icon. The dialogue box to confirm the data provider deletionappears. Click OK to confirm the deletion or Cancel to cancel the deletion.

Parent topic:Managing data providers

282

-

-

-

Managing analysis collections To perform data analysis, you can associate data providers with an analysiscollection in the Analysis Collections view. Only the users with analysis collectionadministrator role can add and delete analysis collections from the system. Theusers with analysis collection owner role can modify the analysis collection such asediting analysis collection information, adding members to an analysis collection,and setting threshold value for different data providers. For more information about roles and permissions for ADI, see Assigning role-basedpermissions to ADI users. Besides the role-based permissions, there is access control for an analysiscollection if users want to modify or delete analysis collection. The users need to bean owner of the analysis collection to edit and delete that analysis collectionregardless of any role permissions the users have. As members of the analysiscollection, users can only view the reports and dashboards of that analysiscollection.

Adding analysis collections Before you add an analysis collection to the system, you must make sure that youcreated at least one data provider for the analysis collection.Modifying analysis collections You can modify the analysis collection information, update contributors, andupdate data providers of the analysis collection. Deleting analysis collections You can delete an analysis collection from the system. If you remove the analysiscollection, you cannot undo or restore the action. When you delete the analysiscollection, you don't delete the data providers associated with that analysiscollection.

Parent topic:Managing connections, data providers, and analysis collections

283

1.

2.

3.---

-

A.

B.C.

-

A.

B.C.

-

-

-

-

---

Adding analysis collections Before you add an analysis collection to the system, you must make sure that youcreated at least one data provider for the analysis collection. Note: Only the users with the analysis collection owner role permission can performthis task. For more information about roles and permissions for ADI, see Assigningrole-based permissions to ADI users. Complete the following steps to add an analysis collection.

Select the Analysis Collections icon ( ) from the left menu to go to AnalysisCollections page.Click Add icon next to the Analysis Collections header. Add AnalysisCollection page appears.Provide the following information to the form.

Name: The analysis collection name.Description: A brief description of the analysis collection.Contributors: Only the contributors of the analysis collection can modify, view,and analyze the analysis collection. You can find the list of all members that areassociated with the project area in the left box. For information about how to setup project area, see Installation and Set-up page.

Set owners of the analysis collection: An owner of the analysis collection canmodify and delete the analysis collection. By default the user who creates ananalysis collection will be assigned as an owner of that analysis collection.There can be more than one owner for an analysis collection.

Select one or more names of the analysis collection owners from the leftbox.Select the Owner role from the right box.Click > icon to add owners to the contributor list.

Set members of the analysis collection: A member of the analysis collectioncan view and analyze analysis collection.

Select one or more names of the analysis collection members from the leftbox.Select Member role from the right box.Click > icon to add members to the contributor list.

Data Providers: The list of all data providers in the system appears. Select oneor more data providers you want to associate with the analysis collection.Data Providers Setting: Provide the following information for each of the dataprovider added.

Manual Builds Data Provider and Rational Team Concert Builds DataProvider

Code Coverage Threshold: Set the code coverage threshold for the codecoverage analysis by using the slide bar. Slide the left and right bars toindicate the lower and upper threshold level.

OMEGAMON for CICS Data ProviderSelect one or more service classes you want to perform analysis.Timeframe to view Dashboard's Metrics: Set the timeframe you want theanalysis report to display on the dashboard. There are 5 choices: Last Month, Last Week, Last Day, Last Hour, and Most Recent. ADI uses the selectedtimeframe to analyze and display the information on all the data analysisviews associated with OMEGAMON for CICS data providers. For example, if

284

---

-

-

4.

you select Last Week, ADI takes all the data collected during past week tocalculated the information that displays on the OMEGAMON for CICSanalysis views. The default timeframe is Last Day.

Application Discovery Data ProviderSelect one or more projects you want to perform analysis.Unreachable Code Threshold: Set the unreachable code threshold for theunreachable code analysis by using the slide bar. Slide the left and right barsto indicate the acceptable, poor and unacceptable level. For more informationof Unreachable Code metric, see Project data from Application Discoveryreports and information.Maintainability Index Threshold: Set the maintainability index threshold forthe maintainability index analysis by using the slide bar. Slide the left andright bars to indicate the acceptable, poor and unacceptable level. For moreinformation of maintainability index, see Project data from ApplicationDiscovery reports and information.Cyclomatic Complexity Threshold: Set the Cyclomatic Complexitythreshold for the complexity analysis by using the slide bar. Slide the rightand left bars to indicate the acceptable, poor and unacceptable level. Formore information of Cyclomatic Complexity metric, see Project data fromApplication Discovery reports and information.

Click Add to create an analysis collection or Cancel to cancel adding an analysiscollection.

Parent topic:Managing analysis collections

285

1.

2.

3.4.

-

-A.B.C.

-A.

B.-

A.

B.C.

-A.

B.-

--

--

-

-

---

--

Modifying analysis collections You can modify the analysis collection information, update contributors, and updatedata providers of the analysis collection. Note: You need to be assigned as an owner of the analysis collection to modify thatanalysis collection. Complete the following steps to modify analysis collections.

From the left menu, select the Analysis Collections icon ( ) to go to theAnalysis Collections page.Hover over the analysis collection card that you want to edit and point to it. Actionicons appear on the right corner of the analysis collection card. You can searchanalysis collections by typing part of the analysis collection name in the Searchbox on the top right corner.Select the Edit icon.Modify the analysis collection information. You can perform one or more of thefollowing activities.

Modify name, description, or both of the analysis collection from the Name andDescription field.Add owners of the analysis collection.

Select one or more names of the analysis collection owners from the left box.Select Owner role from the right box.Click > icon to add owners to the contributor list.

Remove owners of the analysis collection. Select one or more names of the analysis collection owners from the rightbox.Click < icon to remove owners from the contributor list.

Add members of the analysis collection. Select one or more names of the analysis collection members from the leftbox.Select Member role from the right box.Click > icon to add members to the contributor list.

Remove members of the analysis collection. Select one or more names of the analysis collection members from the rightbox.Click < icon to remove members from the contributor list.

Update the threshold.Slide the right and left bars to change the threshold level.

Update data providers. Select or deselect the data providers from the data provider list.

Update the data provider settings for each of the data provider.Manual Builds data provider and Rational Team Concert Builds dataprovider

Code Coverage Threshold: Slide the right and left bars to change thethreshold level.

OMEGAMON for CICS data providerSelect or deselect the service classes from the list.Timeframe to view Dashboard's Metrics: select the timeframe from the list.

Application Discovery data provider Select or deselect the projects from the list.

286

-

-

5.

Unreachable Code Threshold: Slide the right and left bars to change thethreshold level.Maintainability Index Threshold : Slide the right and left bars to change thethreshold level.

Click Save to update the changes being made. Parent topic:Managing analysis collections

287

1.2.

3.4.

Deleting analysis collections You can delete an analysis collection from the system. If you remove the analysiscollection, you cannot undo or restore the action. When you delete the analysiscollection, you don't delete the data providers associated with that analysiscollection. Note: You need to be assigned as an owner of the analysis collection to delete thatanalysis collection. Complete the following steps to delete an analysis collection.

Select the Analysis Collections icon ( ) to go to the Analysis Collections page.Hover over the analysis collection card that you want to delete and point to it.Action icons appear on the right corner of the collection card. You can searchanalysis collections by typing part of the analysis collection name in the searchbox on the top right corner.Select Delete icon. A confirmation message appears.Click Ok to delete the analysis collection or Cancel to cancel the delete action.

Parent topic:Managing analysis collections

288

-

-

-

-

Analyzing data Before you can view the analysis data, ADI requires you to select your role to startthe analysis. After the role selection, three types of data analysis based on differenttypes of data providers are available: Development, Test, and Operations. The orderof dashboards reports depends on the role you select. For more information, see Role-based dashboards and reports.

Role-based dashboards and reports Before you start analyzing the data, ADI requires you to select your role. Roleselection allows ADI to customize the order of dashboards and reports within adashboard based on the focus of a specific role, which helps you view the reportsin which you are most interested first. Three roles are available: Development,Test, and Operations. Analyzing and displaying code coverage results Code coverage results are analyzed and displayed in different views. You cannavigate through different views of code coverage analysis results for an analysiscollection. Analyzing and displaying operational data from IBM OMEGAMON for CICS Operational data from IBM OMEGAMON® for CICS® is analyzed and displayed indifferent views. You can navigate through different views of operational dataanalysis results for a collection.Analyzing and displaying project data from Application Discovery Application Discovery (AD) provides static analysis of projects. Project data suchas number of artifacts, maintainability index, and number of statements that arecollected from AD are analyzed and displayed in different views. You can navigatethrough different views of project inventory data analysis results for an analysiscollection.

Parent topic:IBM Application Delivery Intelligence 5.0.2

289

----

--

----

-

-----

-

---

----

Role-based dashboards and reports Before you start analyzing the data, ADI requires you to select your role. Roleselection allows ADI to customize the order of dashboards and reports within adashboard based on the focus of a specific role, which helps you view the reports inwhich you are most interested first. Three roles are available: Development, Test,and Operations. Development role This role is for people whose focus is on software implementation. You can find theorder of dashboards displayed and reports displayed within a dashboard for thedevelopment role in the following list.

For Analysis view: Application Discovery reportsCode Coverage analysis reportsOMEGAMON for CICS reports

For Analysis Collection view: Application Discovery dashboard: The order of the reports within theApplication Discovery dashboard is:

Unreachable Code TrendTotal and Active Statements TrendArtifact and Lines of Code BreakdownMaintainability Index vs Delivered Bugs

For report details, see Project data from Application Discovery reports andinformation.Code Coverage analysis dashboard: The order of the reports within the CodeCoverage dashboard is:

Coverage Changed vs Unchanged CodeBiggest Coverage DropsFiles with Lowest CoverageCode Coverage, Executable Lines Covered TrendCode Coverage Percentage Trend.

For report details, see Code coverage reports and information.OMEGAMON for CICS dashboard: The order of the reports within theOMEGAMON for CICS dashboard is:

Transactions with Performance and Reliability IssuesAverage Response TimeAverage CPU Time, Average Transactions

For report details, see OMEGAMON for CICS related reports and information. Test role This role is for people whose focus is on software testing. You can find the order ofdashboards and reports displayed within a dashboard for the test role in thefollowing list.

For Analysis view: Code Coverage analysis reportsOMEGAMON for CICS reportsApplication Discovery reports

290

--

-----

-

----

-

----

----

--

----

-

---

For Analysis Collection view:Code Coverage analysis dashboard: The order of the reports within the CodeCoverage dashboard is:

Coverage, Executable Lines Covered TrendCode Coverage Percentage TrendCoverage Changed vs Unchanged CodeBiggest Coverage DropsFiles with Lowest Coverage.

For report details, see Code coverage reports and information.OMEGAMON for CICS dashboard: The order of the reports within theOMEGAMON for CICS dashboard is:

Transactions with Performance and Reliability IssuesAverage Response TimeAverage CPU TimeAverage Transactions

For report details, see OMEGAMON for CICS related reports and information.Application Discovery dashboard: The order of the reports within theApplication Discovery dashboard is:

Maintainability Index vs Delivered BugsArtifact and Lines of Code BreakdownUnreachable Code TrendTotal and Active Statements Trend

For report details, see Project data from Application Discovery reports andinformation.

Operations role This role is for people whose focus in on monitoring the performance of theoperation server. You can find the order of dashboards and reports displayed withina dashboard for the operations role in the following list.

For Analysis view:OMEGAMON for CICS reportsApplication Discovery reportsCode Coverage analysis reports

For Analysis Collection view:OMEGAMON for CICS dashboard: The order of the reports within theOMEGAMON for CICS dashboard is:

Average Response TimeAverage CPU TimeAverage TransactionsTransactions with Performance and Reliability Issues

For report details, see OMEGAMON for CICS related reports and information.Application Discovery dashboard: The order of the reports within theApplication Discovery dashboard is:

Artifact and Lines of Code BreakdownUnreachable Code TrendTotal and Active Statements Trend

291

-

-

------

Maintainability Index vs Delivered Bugs For report details, see Project data from Application Discovery reports andinformation.Code Coverage analysis dashboard: The order of the reports within the CodeCoverage dashboard is:

Code CoverageExecutable Lines Covered TrendCode Coverage Percentage TrendCoverage Changed vs Unchanged CodeBiggest Coverage DropsFiles with Lowest Coverage

For report details, see Code coverage reports and information. Note: The dashboards and reports related to a data provider will only be displayedwhen you associate that type of data provider with the analysis collection beinganalyzed. For example, if you do not have OMEGAMON for CICS data providerassociated with an analysis collection being analyzed, the dashboards and reportsrelated to OMEGAMON for CICS data providers will not be displayed. Parent topic:Analyzing data

292

-

-

------

-

Analyzing and displaying code coverage results Code coverage results are analyzed and displayed in different views. You cannavigate through different views of code coverage analysis results for an analysiscollection. Before you start this task, you need to add at least one analysis collection with onedata provider to the system. For more information, see Managing connections, dataproviders, and analysis collections. Navigating through different views of code coverage results Code coverage results for an analysis collection can be analyzed and displayed inthese views: Analysis view, Collection Analysis view, Build Analysis view, andFile Analysis view.Note: An analysis collection is a logical grouping of programs orfiles. You can use an analysis collection to organize programs or files in the way thatis meaningful to you. For more information about analysis collections, see Terminology overview.

Analysis view.You can get to the Analysis view by selecting the Analysis icon () from the left menu. The first page of Analysis view is the view that shows all the analysis collectionswith their latest aggregated code coverage. The analysis collection code coverageis the code coverage percentage of the latest build of that analysis collection forwhich code coverage results are provided. For more information, see Codecoverage reports and information. Collection Analysis view.From the main page of Analysis view, select anyanalysis collection card to browse the Collection Analysis view. The Collection Analysis view displays all the data providers within that analysiscollection. For Manual Builds and Rational Team Concert Builds data providers,each data provider card displays the code coverage reports resulting from the codecoverage analysis of the latest build of that build data provider. The following sixreports are displayed. The order of reports that is displayed depends on your role.For more information, see Role-based dashboards and reports.

Code CoverageCode Coverage Percentage TrendExecutable Lines Covered TrendCoverage Changed vs Unchanged CodeBiggest Coverage DropsFiles with Lowest Coverage

For more information, see Code coverage reports and information. On the top of each analysis collection card, you can see the dual slider. You canuse this slide to navigate to different builds. Use the left slider to set the start buildand the right slider to set the end build. Based on the start and end builds youselect, the code coverage reports on this view will get updated. Build Analysis view.From the Collection Analysis view of any analysiscollection, click the title of the analysis collection to browse the Build Analysisview. By default, the build analysis view displays detailed information of the latest build.You can click the upside-down triangle icon next to the current build id to selectother builds available. The Build Analysis view is composed of Header andContent areas. The Header area displays the name of the build, the analysis collection name, and

293

-

-

--------

---

----

--

-

-

-

-

-

the data provider name. You can use the dropdown icon, which locates next to thename of the build, to view code coverage analysis for different builds. The Content area displays the build status information and code coverage detailsfor files or programs within that build.

Build status information. The top row of this view displays the overallinformation for a build: Date of Build, Last Coverage Date Update, CodeCoverage, and Executable Line Changes.Code coverage details. The table under the build status information displays thedetails of code coverage for files or programs within the build. You can examinethe following information.

Name of File or ProgramPercentage of Code CoveragePercentage of Coverage ChangeNumber of Executable Lines ChangedChange Percentage of Executable LinesNumber of Historical Tests to RunNumber of Minimal Tests to RunWarnings for Code Coverage Status of the File or Program

For each file, you can click the right-angled triangle icon to expand the row tosee more information about code coverage details.

Number of Executable LinesNumber of Total Executable LinesNumber of Executable Lines Hit

Number of Executable Lines ChangedNumber of Executable Lines AddedNumber of Executable Lines UpdatedNumber of Executable Lines Deleted

List of Historical Tests to RunList of Minimal Tests to Run

For detailed information about each code coverage reports or code coverage, seeCode coverage reports and information You can also click the toggle icon in the upper right corner of the view to switch todifferent views. The Actions menu appears with following options available.

View by Source Files. This is the default view that displays detail code coveragefor each source file within a build. View by Tests. This view displays detail code coverage for each test thatexecutes the code within a build.Compare Builds. With this view, you can select multiple builds to compare thecode coverage information. For more information, see Comparing the builds.

You can also use the Filter options provided in the Actions menu to filter theinformation that is displayed in the view. For more information, see Filtering data inthe Build Analysis view. File Analysis view.From the Build Analysis view, select the file name to navigateto the File Analysis view of that file. The view is composed of two areas: Header and Content areas.

The Header area displays the name of the file, the analysis collection name, and294

-

-

----

-

--------

---

----

--

-

-

-

the data provider name. You can click the upside-down triangle icon next to thename of the file to view code coverage analysis for different files. The Content area displays two groups of information: file status information andcode coverage detail for functions or methods within that file.

File status information: The top row of this view displays the overallinformation for a file.

Percentage of Code CoveragePercentage of Coverage ChangeExecutable Lines AddedExecutable Lines Deleted

Code coverage detail: The table under the file status information displays thedetail of code coverage for functions or method within the file.

Name of the Function or MethodPercentage of Code CoveragePercentage of Coverage ChangeNumber of Executable Lines ChangedChange Percentage of Executable LinesNumber of Historical Tests to RunNumber of Minimal Tests to RunWarnings for Code Coverage Status of the File or Program

For each function or method, you can click the right-angled triangle icon toexpand the row to see more code coverage detail information.

Number of Executable LinesNumber of Total Executable LinesNumber of Executable Lines Hit

Number of Executable Lines ChangedNumber of Executable Lines AddedNumber of Executable Lines UpdatedNumber of Executable Lines Deleted

List of Historical Tests to RunList of Minimal Tests to Run

For detail of each code coverage reports or code coverage information, see Codecoverage reports and information. You can also use the Filter options provided in the Actions menu to filter theinformation that is displayed in the view. For more information, see Filtering data inthe File Analysis view.

Code coverage reports and information You can find the details of reports and information that is displayed for the codecoverage analysis views.Comparing the builds You can compare builds to analyze code coverage results. To compare the builds,you need at least two builds with code coverage data. Filtering data in the Build Analysis view You can filter information in the Build Analysis view.

295

-

-

-

Filtering data in the File Analysis view You can filter information in the File Analysis view.Analyzing the Tests to Run You can use ADI for suggestions about which tests to run for a current build basedon the analysis of code coverage results from the previous build and informationabout changed files. Analyzing code coverage of FlowPoint level break-down ADI provides the detailed code coverage analysis of the FlowPoint level break-down for a file. FlowPoint level break-down refers to the function or method withina file.

Parent topic:Analyzing data

296

Code coverage reports and information You can find the details of reports and information that is displayed for the codecoverage analysis views. Code coverage reports Table 1. Code coverage reports

Reports Name Description Displayed LocationAggregated codecoverage

Code coverage percentageof the analysis collectionthat is calculated byaverage code coveragepercentage of all builddefinitions and all theirbuild data providers' mostrecent builds that havecoverage results.

Analysis view

Code coverage Code coverage percentageof the build calculated byaverage code coveragepercentage of all the filesor program within the mostrecent build.

Build Card in CollectionAnalysis View

Code CoveragePercentage Trend

Line charts that show thecode coverage percentagetrend of all builds.

Build Card in CollectionAnalysis View

Executable LinesCovered Trend

Line charts that show thenumber of executable lineshit vs total executable linesof a build over time.

Build Card in CollectionAnalysis View

Coverage Changed vsUnchanged Code

Stacked bar charts thatdisplay the comparison ofcode coverage forexecutable lines that arechanged and executablelines unchanged in thecurrent build. The stackedbar presents thepercentage executablelines that are hit vs not hitby the tests.

Build Card in CollectionAnalysis View

297

Note: The order of the reports displayed in Collection Analysis view depends onyour role. For more information, see Role-based dashboards and reports. Information displayed in Build Analysis Views Table 2. Information that is displayed in Build Analysis views

Biggest Coverage Drops Bar charts that display thetop 5 files that have thebiggest amount of codecoverage drop that iscompared to the last build.Any files that the codecoverage drops is over10% and the codecoverage is crossed thethreshold boundaries areconsidered as largeamount of code coveragedrop.

Build Card in CollectionAnalysis View

Files with LowestCoverage

Bar charts that displays thetop 5 source files that havethe lowest code coverage.

Build Card in CollectionAnalysis View

View Information DescriptionBuild DetailSummary

Date of Build The date and timethat the build iscreated.

  Last Coverage DataUpdate

The date and timethat the codecoverage informationis updated, that is,the last date when acoverage zip file wasadded.

  Code Coverage The code coveragepercentage of thebuild. It is calculatedby average codecoverage percentageof all the files orprogram within abuild.

  Exec. Line Changes The percentage ofexecutable linesbeing changed withina build. It iscalculated from thenumber of lines thatare updated within abuild and the numberof total executablelines within a build.

298

View by source files Name The name of thesource file orprogram within abuild.

  Code Coverage The code coveragepercentage of thesource file orprogram. SeeTerminologyOverview for moreinformation aboutcode coverage.

  Coverage Change The difference incode coverage that iscompared with theprevious build as apercentage.

  Executable LinesChanged

The number ofexecutable lines thatare updated from theprevious build andnumber of totalexecutable lines.

  Changes Percentage The percentage ofexecutable lineschanged.

  Historical Tests The number of testcases that test thesource file orprogram analyzedfrom all the previousbuilds as well as thecurrent build.

  Minimal Tests The number ofminimal list of teststhat achieve thehighest codecoverage percentageand it is sorted by theamount of codecoverage that isprovided.

299

  Warnings The code coveragestatus of individualfile or program. Twostatuses areavailable: red andyellow. Yellowindicates the poorcode coveragepercentage. Redindicates theinsufficient codecoverage percentage.Threshold of red andyellow status are setduring the analysiscollection creation.See Modifyinganalysis collectionsfor more detail.

Expansion Sectionof Source File

Executable Lines The number ofexecutable lines for asource file orprogram. Executableline is defined as theline of code that thecompiler marks asexecutable. ForCOBOL, theexecutable line mightnot directlycorrespond to theexact source line, asCOBOL is notdebugged usingsource but rather theexpanded source.

  Executable Lines -Total

The number of totalexecutable lines inthe source files.

  Executable Lines -Hit

The number ofexecutable lines thatis exercised by thetests.

  Executable Line -Changed

Executable lines thatare changed (eitheradded, updated ordeleted) in a functionor method from theprevious build.

  Executable Lines -Added

The number ofexecutable lines thatare added from theprevious build.

300

  Executable Lines -Updated

The number ofexecutable lines thatare updated from theprevious build.

  Executable Lines -Deleted

The number ofexecutable lines thatare deleted from theprevious build.

  Historical Tests toRun

The list of test casesthat test the sourcefile or programanalyzed from all theprevious builds aswell as the currentbuild.

  Minimal Tests to Run For each source file,the recommended listof minimal set of testcases to run toachieve the highestcode coveragepercentage. The listis sorted by the testfiles with the highertest coverage.

View by Tests Test The name of the test.See TerminologyOverview for thedefinition of test.

  Code Coverage The code coveragepercentage of the testthat is calculated bynumber of executablelines the testexercises and totalnumber of theexecutable lines ofthe source files thetest exercises.

  Executable LinesCovered

The number ofexecutable lines thetest exercises pertotal number of theexecutable lines ofthe source files thetest exercises.

301

  Flowpoints Covered The number offlowpoints that thetest exercises pertotal number offlowpoint of thesource files that thetest exercises.

  File Tested byCurrent Build

The number ofsource files that areexercised by the testthe current buildbeing analyzed.

  Historical FilesMissing

The number of filesthat the test did notexercise in the test ofthe current buildbeing analyzed butthey were exercisedin the previous testsof the previousbuilds.

  File Tested byPrevious Build

The list of source filesthat are exercised bythe test for allprevious builds.

Expansion Sectionof Test File

Start Time The sate and timethat the test was run.

  Files Tested byCurrent Build

The list of source filesexercised by the testfor the current buildbeing analyzed.

  Historical FilesMissing

The list of files thatthe test did notexercise in the test ofthe current buildbeing analyzed butthey were exercisedin the previous testsof the previousbuilds.

Compare Builds Name The name of thesource file orprogram within thebuilds.

  Build Name The name of the buildor build ID forautomated build.

  Language Programminglanguage of thesource file orprogram beinganalyzed.

302

Information Display in File Analysis View Table 3. Information that is display in File Analysis views

  <other columns> Same as the columnslisted previously for"View by SourceFiles".

View Information DescriptionFile Detail Summary Code Coverage Code coverage percentage

of a source file. SeeTerminology Overview forCode Coverage.

  Coverage Change Shows the difference incoverage of a source file inthe current build comparedto the same source file inthe previous build as apercentage.

  Executable Lines Changed The number of executablelines that are updated in asource file from theprevious build.

  Executable Lines Added The number of executablelines that are added to asource file from theprevious build.

  Executable Lines Deleted The number of executablelines that are deleted froma source file from theprevious build.

File Analysis Detail Name The name of a function ormethod within a source file.

  Code Coverage Code coverage percentageof a function or method.

  Coverage Change Shows the difference incoverage of a function ormethod in the current buildcompared to the samefunction or method in theprevious build as apercentage. For Java™, onthe package level you seethe rollup coveragechanges percentage for allmethods under thatpackage.

303

  Executable Lines Changed Shows number ofexecutable lines that areupdated in a function ormethod from the previousbuild and number of totalexecutable lines.

  Change Percentage The percentage ofexecutable lines that arechanged from the previousbuild.

  Historical Tests The number of test casesthat test a function ormethod analyzed from allthe previous builds as wellas the current build.

  Minimal Tests The number of minimal listof tests that achieve thesame amount of codecoverage and it is sortedby the amount of codecoverage that is provided.

  Warnings Code coverage status ofindividual function ormethod. Two statuses areavailable: red and yellow.Yellow indicates the poorcode coveragepercentage.Red indicatesthe insufficient codecoverage percentage.Threshold of red andyellow status are set duringthe analysis collectioncreation. See Modifyinganalysis collections formore detail.

Expansion section of FlowPoint

Executable Lines The number of executablelines for a function ormethod. Executable line isdefined as the line of codethat the compiler marks asexecutable. For COBOL,the executable line mightnot directly correspond tothe exact source line,because COBOL is notdebugged using source butrather the expandedsource.

  Executable Lines - Total The number of totalexecutable lines within afunction or method.

304

Parent topic:Analyzing and displaying code coverage results

  Executable Lines - Hit The number of executablelines that is exercised bythe tests.

  Executable Line Changed Executable lines that arechanged (either added,updated or deleted) in afunction or method fromthe previous build.

  Executable Lines - Added The number of executablelines that are added to afunction or method fromthe previous build.

  Executable Lines -Updated

The number of executablelines that are updated in afunction or method fromthe previous build.

  Executable Lines - Deleted The number of executablelines that are deleted in afunction or method fromthe previous build.

  Historical Tests to Run The list of test cases thattest a function or methodanalyzed from all theprevious builds and thecurrent build.

  Minimal Tests to Run A recommended list ofminimal set of test cases tobe run to achieve thehighest code coveragepercentage for eachfunction or method. The listis sorted by the test fileswith the higher testcoverage.

305

1.2.3.

4.5.6.

7.8.

Comparing the builds You can compare builds to analyze code coverage results. To compare the builds,you need at least two builds with code coverage data. Complete the following steps to compare builds:

Select the Analysis icon ( ) to go to the Analysis page.Select the analysis collection card of the builds that you want to compare.Click the name of the Manual Builds or Rational Team Concert Builds dataprovider with the latest build name to which the builds belong. The latest buildinformation is displayed in the Build Analysis view. Click to toggle the Actions menu in the upper right corner of the view.Select Compare Builds from the Actions menu.Select the check boxes of two or more builds to compare from the list. Themaximum number of builds that are allowed to be compared is 5.Click Compare to compare the builds. The Compare Builds view is displayed.For Java™ code coverage, you can click the expand icon to expand the packagesand view the detailed package comparison.

For more information that is displayed in the Compare Builds view, see Codecoverage reports and information. Parent topic:Analyzing and displaying code coverage results

306

1.2.3.

4.5.

-

-

--

-

-

-

6.7.

Filtering data in the Build Analysis view You can filter information in the Build Analysis view. Complete the following steps to filter the information:

Select the Analysis icon ( ) to go to the Analysis page.Select the analysis collection card that you want to view analysis information.Click the name of the Manual Builds or Rational Team Concert Builds dataprovider with the latest build name that you want to view analysis information. Thelatest build information is displayed in the Build Analysis view. Click to toggle the Actions menu in the upper right corner of the view.Under the Filter section, select one or more options to filter the informationdepending on your current situation.

Select the Changed Files Only check box to show only the changed files.Changed files refer to those files that are explicitly selected as Modified Fileson the Add Build page in the Providers section.

If you specify Modified Files in the Add or Edit Build dialog then this listpresents to you in a dialog. You can deselect files from that list if you want toreview only a subset of these files.If you specify no files for the build as modified, a warning message occurs.

Select the Hide Good Coverage Files check box to hide good code coveragefiles. You can hide the files whose code coverage are above the threshold inorder to show only files that have poor code coverage.Note: Code coveragethreshold is set when you add an analysis collection. For more information abouthow the threshold can be set, see Adding analysis collections. You can alsomodify the threshold settings by modifying analysis collections. For informationabout how the threshold can be updated, see Modifying analysis collections. Select the Hide Poor Coverage Files check box to hide poor code coveragefiles. You can hide the files whose code coverage are below the thresholds inorder to show only files that have good code coverage. Note: Code coveragethreshold is set when you add an analysis collection. For more information abouthow the threshold can be set, see Adding analysis collections. You can alsomodify the threshold settings by modifying analysis collections. For informationabout how the threshold can be updated, see Modifying analysis collections. Slide the bar of Filter Percentage Line Changes left or right to filter by thepercentage of line changes with a value range you specified. For example, youcan specify to show files that have at least 10% but not more than 80% of linesthat are changed.Slide the bar of Filter Coverage Percentage left or right to filter by the codecoverage percentage with a value range you specified.

If you want to clear filters, click Clear Filter to clear all the filter selections.Select the Actions menu icon again to hide the Actions menu.

Parent topic:Analyzing and displaying code coverage results

307

1.2.3.

4.

5.6.

-

-

-

-

7.8.

Filtering data in the File Analysis view You can filter information in the File Analysis view. Complete the following steps to filter the information:

Select the Analysis icon ( ) to go to the Analysis page.Select the analysis collection card that you want to view analysis information.Click the name of Manual Builds or Rational Team Concert Builds data providerwith the latest build name that you want to view analysis information. The latestbuild information is displayed in the Build Analysis view. Click the file or program name that you want to view analysis information. TheFile Analysis view appears. Click to toggle the Actions menu in the upper right corner of the view.Under the Filter section, choose one or more options below to filter the sourcesfiles.

Filter the sources files with the percentage line changes between the specifiedrange.

Slide the sliders to the specific range you want. The view displays only thesource files that the percentage line changes between the specified range.

.Filter the sources files with the code coverage percentage between the specifiedrange.

Slide the sliders to the specific range you want. The view displays only thesource files that the code coverage and lines changed between the specifiedrange.

If you want to clear filters, click Clear Filter to clear all the filter selections.Select the Actions icon again to hide the Actions menu panel.

Parent topic:Analyzing and displaying code coverage results

308

1.

2.3.

4.

5.

6.

7.

-

-

8.--

Analyzing the Tests to Run You can use ADI for suggestions about which tests to run for a current build basedon the analysis of code coverage results from the previous build and informationabout changed files. ADI lists the tests for a changed source file that exercised that source file in previousbuilds. You can use the list of Historical Tests to Run or Minimal Tests to Run tohelp you plan the testing of your latest build. For more information, see CodeCoverage Reports and Information. Before you begin this activity, you need to add at least one analysis collection andone data provider with code coverage results. Analyzing the tests to run based-on the Historical Tests toRun Follow the following steps to analyze test to run by using the list of Historical Teststo Run.

Add the latest build to the data provider. For information about how to add a buildto a data provider, see Managing Providers. Note: You do not add code coverageresult files at this step for your current build has no code coverage results yet.However, in this screen you need to select which files have been changed in thisbuild to let ADI know how to filter results in the following steps. Click the Analysis icon ( ) to go to the Analysis view.On the Analysis view, select the analysis collection card that the build belongs to.If the analysis collection has only one Manual Builds data provider, theAggregated Code Coverage report of this analysis collection shows no resultsbecause no code coverage results are associated with the build yet. However, ifearlier builds that had coverage results are available, the number of the mostrecent build with results is shown.On the Analysis Collection view, select the data provider that the build belongsto. No results of code coverage on the build cards are displayed because no codecoverage results are associated with the build yet. In contrast to the previousscreen, no earlier build results is shown here because it is a most-recent buildspecific view.The Build Analysis view appears with the information of latest build. You see noinformation that is related to executable lines changes nor code coverageinformation.For each of the file, click the right-angled triangle icon to expand more detailinformation of the file.View the Historical Tests to Run column on the right. This column displays thelist of tests that exercising a file from the previous build. You can use this list toconstruct the testing of your current build.

Take the list from all the source files if you want to perform the testing for allsource files in the build.Take the list from a single source file if you want to perform the testing for aspecific source file.

Get the list of test to run for modified files only. Click to toggle the Actions menu in the upper right corner of the view.In the Filter section of the Actions menu, check the Changed Files Only box tofilter out the files that are not changed in this build. All the files that you selectedas changed earlier in Step 1 are shown in the view.

309

-

-

-

1.2.

3.

4.

5.

-

-

6.--

-

-

-

You can clear some files that you want to exclude from the filter, that is, you canremove them from the recommended list of tests to run. Expand the detail section to view the list of Historical Tests to Run to get thelist of tests for the changed files from Historical Tests to Run. The view displaysonly the files that are modified in the latest build.Switch the view to View by Tests in the Actions menu to get the list of teststhat are recommended to run for these changed files.

After you run the test against the latest build, you must collect the code coverageresults from current build and add the code coverage result files to the latest build.For more information about how to add code coverage result files to an existingbuild, see Managing Providers. Analyzing the tests to run based on the Minimal Tests to Run Complete the following steps to analyze the tests to run by using the list of MinimalTest to Run.

Click the Analysis icon ( ) to go to Analysis view.On the Analysis view, select the analysis collection card that you want to doanalysis. On the Analysis Collection view, select the data provider of the build you wantto perform analysis. The information of latest build is displayed in the BuildAnalysis view.For each of the file, click the right-angled triangle icon to expand more detailinformation of the file.View the Minimal Tests to Run column. This column suggests the list of minimalset of tests to achieve the same amount of code coverage. You can use this list toconstruct the testing when perform regression testing to reduce amount of testeffort.

Take the list from all the source files if you want to perform the testing for allsource files in the build.Take the list from a single source file if you want to perform the testing for aspecific source file.

Get the list of tests to run for modified files only.Click to toggle the Actions menu in the upper right corner of the view.In the Filter section of the Actions menu, check the Changed Files Only box tofilter out the files that are not changed in this build. All the files that you selectedas changed earlier in Step 1 are shown in the view. You can clear some files that you want to exclude from the filter, that is, you canremove them from the recommended list of tests to run.Expand the detail section to view the list of Minimal Tests to Run to get therecommended list of tests for the changed files from Minimal Tests to Run. Thisview displays only the files that are modified in the latest build. Switch the view to View by Tests in the Actions menu to get the list of teststhat are recommended to run for those changed files.

Note: You can view only the list of minimal tests to run when code coverage reportsare against the current build.

310

Parent topic:Analyzing and displaying code coverage results

311

1.2.3.

4.

5.-----

6.

Analyzing code coverage of FlowPoint level break-down ADI provides the detailed code coverage analysis of the FlowPoint level break-downfor a file. FlowPoint level break-down refers to the function or method within a file. Complete the following steps to view the code coverage analysis of FlowPoint levelbreak-down. Before you perform this activity, you need to add at least one analysiscollection and one data provider with code coverage results.

Select the Analysis icon ( ) to go to the Analysis page.Select the analysis collection card that you want to view analysis information.Click the name of Manual Builds or Rational Team Concert Builds data providerwith the latest build name that you want to view analysis information. The latestbuild information is displayed in the Build Analysis view.Click the file or program name that you want to view the FlowPoint analysisinformation. The list of functions or methods within the file and the code coverageinformation is displayed in the File Analysis view.Expand the function or method row to see more detail information, for example:

The number of total executable linesThe number of executable lines hitThe number of executable lines changedA list of historical tests to runA list of minimal tests to run

For more information about the reports that are displayed in the File Analysisview, see Code Coverage Reports and Information.Click to toggle the Actions menu in the upper right corner of the view to filterfunctions or methods by range of code coverage. For more information about howto filter the functions and methods in the File Analysis view, see Filtering Data inthe File Analysis View.

Parent topic:Analyzing and displaying code coverage results

312

-

-

----

-

-

Analyzing and displaying operational data from IBMOMEGAMON for CICS Operational data from IBM® OMEGAMON® for CICS® is analyzed and displayed indifferent views. You can navigate through different views of operational dataanalysis results for a collection. Before you start this task, you need to add at least one connection with oneOMEGAMON for CICS data provider to the system. For more information, seeManaging connections, data providers, and analysis collections. Navigating through different views of OMEGAMON for CICSdata analysis Operational data from IBM OMEGAMON for CICS for a collection can be analyzedand displayed in these views: Analysis view, Collection Analysis view, andTransaction Analysis view.

Analysis view You can get to the Analysis view by selecting the Analysis icon ( ) from the leftmenu. The first page of Analysis view is the view that shows all the collections with itslatest data analysis results from their associated data provider. For the collectionsassociated with OMEGAMON for CICS data provider, an average response timegauge report displays on the card. For more information, see OMEGAMON forCICS related reports and information Collection Analysis view From the main page of Analysis view, select the name of a collection card that isassociated with OMEGAMON for CICS data provider to browse the CollectionAnalysis view. The Collection Analysis view displays all the service classes within thatcollection. Each service class card displays the operational data reports related tothe analysis of the latest operational data that is collected from the associatedOMEGAMON for CICS data provider. The following five reports are displayed. Theorder of reports that is displayed depends on your role. For more information, seeRole-based dashboards and reports.

Average transactionsAverage response timeAverage CPU timeTransaction with Performance and Reliability Issues

Note: The average value of the reports are calculated by using the timeframe youselect during the analysis collection creation. For example, if you select, LastMonth timeframe, the average response time report is calculated by using theresponse time of all transactions within the past month from the present time. For more information, see OMEGAMON for CICS related reports and information. Transaction Analysis view From the Collection Analysis view, you have three different ways to get toTransaction Analysis view report:

Select the name of a service classe to view all transactions under the serviceclass. Then select the name of the transaction you want to view the analysisresults.

313

-

-

-

-

Click on the transaction name under Transaction with Performance andReliability Issues report.

The Transaction Analysis view is composed of Header and Content areas. The Header area displays the name of service class the transaction belongs to,transaction name, maximum number of execution counts, maximum CPU time,maximum response time, and number of transactions exceeding goal responsetime. You can use the dropdown (v) icon, which locates next to the name of thetransaction, to view transaction analysis for different transactions. You can alsotype part of the transaction name on the Select Transaction text box to search fora transaction. The Content area display the history trends of average response time, averageDB2 and File I/O wait time of response time, average execution count, andaverage CPU time of that transaction. The charts can be view hourly, daily, orweekly. The default display timeline can be set when you create an OMEGAMONfor CICS analysis collection. For more information, see Adding analysis collections. For more information, see OMEGAMON for CICS related reports and information.

OMEGAMON for CICS related reports and information You can find the details of reports and information that is displayed forOMEGAMON for CICS data analysis.Analyzing transaction data ADI provides the detailed CICS transaction analysis within a service class.

Parent topic:Analyzing data

314

OMEGAMON for CICS related reports andinformation You can find the details of reports and information that is displayed for OMEGAMONfor CICS data analysis. For OMEGAMON for CICS data provider, two types of timeframe are available,including data collection interval timeframe and dashboard display timeframe. Data collection interval timeframe refers to the timeframe that the collection ofdata from IBM® OMEGAMON® for CICS® server runs every 5 minutes. Dashboard display timeframe refers to the default timeframe that the data displayson the dashboard. You can set the dashboard display timeframe during collectioncreation. Table 1. OMEGAMON for CICS data analysis reports

Reports Name Description Displayed Location

315

Average responsetime gauge

Gauge shows thestatus of the averageresponse time for allCICS transactionswithin the collectionthat exceed the goalresponse time that isset in the IBMOMEGAMON forCICS server. Theaverage responsetime is calculatedfrom the recenttransactions that arecollected fromOMEGAMON forCICS data provider.Red indicates that theaverage responsetime for all CICStransactions withinthe collectionexceeds the goalresponse time by400%Orange indicates thatthe average responsetime for all CICStransactions withinthe collectionexceeds the goalresponse time by 200- 400%Yellow indicates thatthe average responsetime for all CICStransactions withinthe collectionexceeds the goalresponse time by 100- 200%Blue indicates thatthe average responsetime for all CICStransactions withinthe collectionexceeds the goalresponse time lessthan 100%

Analysis view

316

Average transactions Average recenttransactions viewletshows number ofCICS transactionsthat are calculated bytaking number oftransactions for eachdata collection (every5 minutes) within theselected dashboarddisplay timeframeand averaging them.

Collection Analysisview

317

Average responsetime

Average responsetime that is calculatedby averaging theresponse time of allCICS transactions inthe collection that arecollected within thedashboard displaytimeframe. Thegauge shows thelevel where theaverage responsetime exceeds thegoal response time.Red indicates that theaverage responsetime for all CICStransactions withinthe collection thatexceed the goalresponse time by400%Orange indicates thatthe average responsetime for all CICStransactions withinthe collection thatexceed the goalresponse time by 200- 400%Yellow indicates thatthe average responsetime for all CICStransactions withinthe collection thatexceed the goalresponse time by 100- 200%Blue indicates thatthe average responsetime for all CICStransactions withinthe collection thatexceed the goalresponse time lessthan 100%

Collection Analysisview

318

Average CPU time Average CPU timethat is calculated byaveraging the CPUtime of all CICStransactions in thecollection that arecollected within thedashboard displaytimeframe.

Collection Analysisview

Top averageexecution count

Top averageexecution countdisplays the top tenlists of CICStransactions with thehighest averageexecution count.Average executioncount is calculated byaveraging theexecution count of allCICS transactions inthe collection that arecollected within thedashboard displaytimeframe.

Collection Analysisview

Transactions withPerformance andReliability Issues

Transactions withPerformance andReliability Issuesdisplays the tableview of alltransactions thatexceeding the goalresponse timethreshold that is setin the OMEGAMONfor CICS server. Thereport is sorted basedon the number ofaverage executioncounts to emphasizeon the transactionswith the potentiallybiggest impact on thetop.

Transaction Analysisview

319

Average responsetime trends

Average responsetime trends showhistory of averageresponse time of aCICS transactionover the dashboarddisplay settingtimeframe (forexample, hourly,daily, or weekly).

Transaction Analysisview

Average DB2 andFile I/O Wait Time ofResponse Timetrends

This chart displaystwo trend lines:average DB2 waittime of response timetrends and averagefile I/O wait time ofresponse time trends.Average DB2 waittime of response timetrends shows historyof percent DB2 waittime of the responsetime of a CICStransaction over thedashboard displaysetting timeframe(e.g. hourly, daily orweekly).Average file I/O waittime of response timetrends shows historyof percent file I/O waittime of the responsetime of a CICStransaction over thedashboard displaysetting timeframe(e.g. hourly, daily orweekly).

Transaction Analysisview

Average executioncount trends

Average executioncount trends showhistory of averageexecution count of aCICS transactionover the dashboarddisplay settingtimeframe (forexample, hourly,daily, or weekly).

Transaction Analysisview

320

Note: The display order of the reports in Collection Analysis view depends on yourrole. For more information, see Role-based dashboards and reports. Table 2. OMEGAMON for CICS data analysis information

Average CPU timetrends

Average CPU timetrends show historyof average CPU timeof a CICS transactionover the dashboarddisplay settingtimeframe (e.g.hourly, daily orweekly).

Transaction Analysisview

View Information DescriptionTransactionAnalysis view

Service Class The name of serviceclass the transactionbelongs to.

  Transaction Name The name of thetransaction that isanalyzed.

  Max Execution Count Maximum number ofexecution counts ofthe transaction that isanalyzed over theperiod of thedashboard displaytimeframe.

  Max CPU Time Maximum number ofCPU times in secondof the transaction thatis analyzed over theperiod of thedashboard displaytimeframe.

  Max Response Time Maximum number ofresponse times inminute of thetransaction that isanalyzed over theperiod of thedashboard displaytimeframe.

  TransactionExceeding GoalResponse Time

Number oftransactions that theresponse time isgoing over the goalresponse time set inIBM OMEGAMON forCICS server.

321

Parent topic:Analyzing and displaying operational data from IBM OMEGAMON forCICS

  Average Responsetime

Average responsetime in minute for alltransactions that arecollected from thelatest data collection.

  Average CPU time Average CPU time insecond for alltransactions that arecollected from thelatest data collection.

  Average executioncount

Average number ofexecution counts forall transactions thatare collected from thelatest data collection.

322

1.2.3.

4.A.

B.

5.

--------

6.7.

8.

9.

10.

-A.

B.

Analyzing transaction data ADI provides the detailed CICS transaction analysis within a service class. Complete the following steps to view the response time, CPU time or executioncount analysis of CICS transaction. Before you begin this activity, you need to addat least one collection with associated OMEGAMON for CICS data provider.

Select the Analysis icon ( ) to go to the Analysis page.Select the analysis collection card that you want to view analysis information.View the reports on the Collection Analysis view. The latest analysisinformation such as number of average transactions, average CPU time, andaverage response time are displayed.Go to the Transaction Analysis view by using one of the following steps.

Select the transaction name that you want to view the transaction analysisinformation from either Top Average Execution Count report orTransaction Exceeding Response Time Threshold report.Select the name of the service class that you want to view analysisinformation. The list of all CICS transactions within that service class displays.Then, select the transaction name that you want to view the transactionanalysis information.

The Transaction Analysis view displays with the following informationcalculating from the latest data that is collected within the default timeframe thatis set when you create the collection. For more information, see OMEGAMONfor CICS related reports and information.

Maximum execution countMaximum CPU timeMaximum response timeNumber of transactions exceeding goal response timeAverage response time and average response time trendsAverage DB2 and File I/O Wait Time of Response Time trendsAverage Execution count and average execution count trendsAverage CPU time and average CPU time trends

Hover over the trend line to view data on that trend line.Observe the warning icon on top of the average response time trends. The iconindicates the time where the maximum response time occurs.Observe the DB2 and File I/O wait time trends to see the area where the DB2 orFile I/O wait time is above the red line which is the acceptable value. Currently itis set to 50%.Select different timeframe, for example, Hourly, Daily or Weekly, on top of thetrend chart to zoom in or zoom out information.If you associated Application Discovery data provider with this analysiscollection, you can perform deep analysis of your performance issues based onthe Application Discovery metrics by performing one of the actions below.Note:The analysis can be done only when there are transactions with the same nameon both OMEGAMON for CICS and Application Discovery data.

Analyze the potential artifacts that are cause of the performance issues.Click on the area of the Average response time trends where you want to dodeep analysis. The dialogue box with Performance data appears.Click OK button to navigate to the Transaction Composition graph. TheTransaction Composition graph appears with artifacts that connect to either

323

--

DB2 or File I/O. This depends on if the potential cause is due to DB2 waittime or File I/O wait time. For example, if DB2 wait time is much above theacceptable value, the slow response time can be caused by the DB2 waittime. The Transaction Composition graph will display all the artifacts thatconnect to DB2 wait time.

Analyze all artifacts within the transaction:Clicking on the Transaction Composition button on the top right of theTransaction Analysis view. The Transaction Composition graph appears withall artifacts within the Transaction. For more information about how to analyzeTransaction Composition, see Analyzing the Transaction Composition.

Parent topic:Analyzing and displaying operational data from IBM OMEGAMON forCICS

324

-

-

----

-

-

Analyzing and displaying project data fromApplication Discovery Application Discovery (AD) provides static analysis of projects. Project data such asnumber of artifacts, maintainability index, and number of statements that arecollected from AD are analyzed and displayed in different views. You can navigatethrough different views of project inventory data analysis results for an analysiscollection. Before you start this task, you need to add at least one connection with oneApplication Discovery data provider to the system. For more information, seeManaging connections, data providers, and analysis collections. Navigating through different views of project data analysis Project inventory for a collection can be analyzed and displayed in these views:Analysis view, Collection Analysis view, and Compare Projects view.

Analysis view You can get to the Analysis view by selecting the Analysis icon ( ) from the leftmenu. The first page of Analysis view is the view that shows all the collections with itslatest data analysis results from their associated data provider. The reports on thisview are the high-level roll-up information in a collection. For the collectionsassociated with Application Discovery data provider, the view displaysMaintenance Status report on the card. For more information on the report, seeProject data from Application Discovery reports and information. Collection Analysis view From the main page of Analysis view, select the name of any collection cards thatare associated with Application Discovery data provider to browse the CollectionAnalysis view. The Collection Analysis view displays data analysis for all the projects you selectwhen you create a collection. Each project card displays the latest projectinventory information that is collected from AD data provider that is associated withit. The following four reports are displayed.

Artifact and Lines of Code BreakdownMaintainability Index versus Delivered BugsUnreachable Code TrendTotal and Active Statements Trend

For more information, see Project data from Application Discovery reports andinformation. The order of reports displayed depends on your role. For more information, seeRole-based dashboards and reports. Note: For Application Discovery data analysis, you can associate only one dataprovider with a collection. The Transaction Composition view displays the information of all artifacts withina transaction. It can be switched between the following 2 reports.

Transaction Composition graph You can navigate to the Transaction Composition graph from the CollectionAnalysis view by selecting the name of an Application Discovery data providerproject. When the page to select a transaction for analysis appears, select thetransaction you want to analyze. The Transaction Composition graph view

325

-

-

-

--

----

-

-

-

-

appears. For more information about the Transaction Composition graph, seeProject data from Application Discovery reports and information. For moreinformation about how to analyze Transaction Composition, see Analyzing theTransaction Composition. Transaction Composition table You can navigate to the Transaction Composition table view from theTransaction Composition graph view by selecting the Table View icon on thetop right of the view. For more information about the Transaction Compositiontable, see Project data from Application Discovery reports and information. Formore information about how to analyze Transaction Composition, see Analyzingthe Transaction Composition.

Compare Projects view From the Analysis view, take the following steps to go to the Compare Projectsview.

Hover over an analysis collection card. Select two or more compare check boxesunder maintenance status gauge for each project. Select Compare button on the top right corner of the card.The Compare Projects view displays on the next page.

The Compare Projects view displays comparison of the following information forall projects you select.

Maintainability IndexArtifactsSource Lines of CodeUnreachable Code

For more information, see Project data from Application Discovery reports andinformation and Comparing the projects.

Project data from Application Discovery reports and information You can find the details of reports and information that is displayed for ApplicationDiscovery data analysis.Analyzing project data ADI provides the detailed project data analysis such as project inventory, projectcomplexity, and quality.Analyzing the Transaction Composition The transactions within a project can be analyzed using the TransactionComposition. The Transaction Composition allows you to analyze potential riskareas of all the artifacts within a transaction based on relationships betweenartifacts and Application Discovery related metrics such as maintainability index,unreachable code, and cyclomatic complexity. Comparing the projects You can compare project data analysis between two or more projects within ananalysis collection.

Parent topic:Analyzing data

326

327

Project data from Application Discovery reports andinformation You can find the details of reports and information that is displayed for ApplicationDiscovery data analysis. Table 1. Data analysis reports for project data from Application Discovery

Reports Name Description Displayed LocationMaintenance Status The gauge

represents the overallmaintenance statusof an ApplicationDiscovery project.The status iscalculated based onthe MaintainabilityIndex (MI) andUnreachable Codethreshold setting inthe following table.The assumption isthat theMaintainability Indexmetric has doubleweight of theUnreachable Codemetric.

Analysis view

Artifact and Lines ofCode Breakdown

Artifact and Lines ofCode Breakdownreport displays totalnumber of artifactscomparing with totalnumber of lines ofcode breakdown bytype of artifacts.The total number ofartifacts calculated bythe number ofartifacts that areincluded in a project,where artifacts wouldbe entities such asprograms, screens,and classes.The total number oflines of code that iscalculated by thenumber of lines ofcode in a project foreach type of artifacts.

Collection Analysisview

328

Maintainability Indexversus DeliveredBugs

Maintainability Indexversus DeliveredBugs displays the linechart over timecomparingmaintainability indexand delivered bugs.MaintainabilityIndex(MI) is asoftware metric thatmeasures howmaintainable (easy tosupport or change)the source code is.This is calculatedbased on Lines ofCode, Cyclomaticcomplexity, andHalstead volume.The MI value is 0 -100. A higher valueindicates bettermaintainability.Cyclomaticcomplexity is anestimation ofcomplexity bymeasuring thenumber of decisionpoints within aprogram sourcecode, in which thecontrol flow cancontinue in more thanone way.Halstead volume isan estimation ofcomplexity measuresbased on number ofvariables, forexample, number ofoperands, andoperators forexpressions, programlength, vocabulary aswell as number ofdelivered bugs.Delivered Bugs is anestimated number oferrors. It correlateswith the overallcomplexity of thesoftware. For theproject level, it is

Collection Analysisview

329

calculated byaveraging thenumber of deliveredbugs for all type ofartifacts within aproject.For more information,see ComplexityReports inApplication Discovery.

Unreachable CodeTrend

Unreachable codetrend displays thepercentage ofstatements that arewithin routines thatcannot be reached bythe control flow out ofthe total number ofstatements over time.For more information,see Dead CodeReport in ApplicationDiscovery.

Collection Analysisview

Total and ActiveStatements Trend

Total and activestatements displaytrend lines comparingtotal number ofstatements and totalnumber of activestatements within aproject.Total number ofstatements that arecalculated from totalnumber of executablelines of all programwithin a project.Active number ofstatements that arecalculated from totalnumber of hit lines ofall program within aproject.

Collection Analysisview

330

Artifact Compositiongraph

Artifact Compositiongraph is theconnected graphshowing all artifacts(for example,program anddatabase table )within a transaction.The boxes representartifacts within atransaction. Thearrow lines representthe connectionbetween two artifacts.The arrow directionindicates the callingdirection betweenartifacts.

Artifact Compositionview

331

Artifact Compositiontable

Artifact Compositiontable shows the list ofall program artifactswithin a transaction.The table is sortedbased on the analysisof high risk to modify.The rank of risk tomodify is calculatedbased oncombination of thefollowingcriteria:Whether theartifact is in riskareas: Risk areas arebased on thethresholdssetting.Whether theartifact is an outlier:Outlier artifacts isanalyzed based onthe outlier detectionalgorithm leveragingmahalanobis distanceof each artifact to thecenter of thedistribution. Artifactswith largemahalanobisdistances mean theyare outlier orabnormal becausethey very far awayfrommajorities.Metricsvalues sorting:Given the same riskarea and outlierstatus, artifacts arefinally sorted by thevalues ofMaintainability Index,Unreachable Code,and CyclomaticComplexity.

Artifact Compositionview

Maintainability Indextrend

Trend line showsMaintainability Indexof source code in aproject over time.See ApplicationDiscovery dataanalysis informationfor detailed report.

Compare Projectsview

332

Note: The order of the reports displayed in the Collection Analysis view depends onyour role. For more information, see Role-based dashboards and reports. Table 2. Data analysis information for project data from Application Discovery

Artifacts trend Trend line showstotal number ofartifacts that areincluded in a projectover time. SeeApplication Discoverydata analysisinformation fordetailed report.

Compare Projectsview

Source lines of codetrend

Trend line showstotal number ofsource lines of codein a project over time.See ApplicationDiscovery dataanalysis informationfor detailed report.

Compare Projectsview

Unreachable codetrend

Trend line showspercentage ofunreachable code ina project over time.See ApplicationDiscovery dataanalysis informationfor detailed report.

Compare Projectsview

View Information DescriptionArtifactComposition tableview

Outlier Status Outlier Statusindicates whether theartifact is an outlier.Outlier artifacts isanalyzed based onthe outlier detectionalgorithm leveragingmahalanobis distanceof each artifact to thecenter of thedistribution. Artifactswith largemahalanobisdistances mean theyare outlier orabnormal becausethey very far awayfrom majorities.

  Artifact Type The program type ofthe artifact.

333

  Program Name The name of theartifact.

  Maintainability Index MaintainabilityIndex(MI) is asoftware metric thatmeasures howmaintainable ( easyto support or change) the source code is.This is calculatedbased on Lines ofCode, Cyclomaticcomplexity andHalstead volume.The higher the MI,the easier it is tomaintain the sourcecode.Cyclomaticcomplexity is anestimation ofcomplexity bymeasuring thenumber of decisionpoints within aprogram sourcecode, in which thecontrol flow cancontinue in more thanone way.Halstead volume isan estimation ofcomplexity measuresbased on number ofvariables, forexample, number ofoperands andoperators forexpressions, programlength as well asnumber of deliveredbugs.For more information,see MaintainabilityIndex Report inApplicationDiscovery.

334

  Unreachable Code The percentage ofstatements out of thetotal number ofstatements that arewithin routines andare unreachable bythe control flow. Formore information, seeDead Code Report inApplicationDiscovery.

  CyclomaticComplexity

Cyclomaticcomplexity is anestimation ofcomplexity bymeasuring thenumber of decisionpoints within aprogram sourcecode, in which thecontrol flow cancontinue in more thanone way. For moreinformation, seeCyclomatic Report.

  Number of IncomingReferences

The number of linkscalling in the artifact.

  Number of OutgoingReferences

The number of linkscalling out of theartifact.

335

Compare Projectsview

Maintainability Index MaintainabilityIndex(MI) is asoftware metric thatmeasures howmaintainable (easy tosupport or change)the source code is.This is calculatedbased on Lines ofCode, Cyclomaticcomplexity, andHalstead volume.The higher the MI,the easier to maintainthe source code.Cyclomaticcomplexity is anestimation ofcomplexity bymeasuring thenumber of decisionpoints within aprogram sourcecode, in which thecontrol flow cancontinue in more thanone way.Halstead volume isan estimation ofcomplexity measuresbased on number ofvariables, forexample, number ofoperands andoperators forexpressions, programlength as well asnumber of deliveredbugs.

  Artifacts The total number ofartifacts that arecalculated by thenumber of artifactsthat are included in aproject, whereartifacts would beentities such asprograms, screensand classes.

336

Parent topic:Analyzing and displaying project data from Application Discovery

  Source lines of code The total number oflines of codecalculated by thenumber of lines ofcode in a project foreach type of artifacts.

  Unreachable code The percentage ofstatements out of thetotal number ofstatements that arewithin routines andare unreachable bythe control flow.

337

1.2.3.

----

Analyzing project data ADI provides the detailed project data analysis such as project inventory, projectcomplexity, and quality. Complete the following steps to view the analysis of project inventory, complexity,and quality. Before you begin this activity, you need to add at least one analysiscollection with associated Application Discovery data provider. For more informationabout how to add an analysis collection associated with Application Discovery, seeAdding analysis collections.

Select the Analysis icon ( ) to go to the Analysis page.Select the name of the collection card that you want to view analysis information.The Collection Analysis view displays with the following information calculatingfrom the latest data that is collected from Application Discovery data provider. Fordetailed report information, see Project data from Application Discovery reportsand information.

Artifact and lines of code breakdownMaintainability index versus delivered bugsUnreachable code trend Total and active statements trend

Note: The order of reports displayed depends on your role. For more information,see Role-based dashboards and reports.

For next step, you can perform the Transaction Composition analysis of atransaction within a project by navigate to Transaction Composition function. Formore information, see Analyzing the Transaction Composition. Parent topic:Analyzing and displaying project data from Application Discovery

338

1.2.

3.

4.

5.

6.

7.

8.

9.

---

Analyzing the Transaction Composition The transactions within a project can be analyzed using the TransactionComposition. The Transaction Composition allows you to analyze potential riskareas of all the artifacts within a transaction based on relationships between artifactsand Application Discovery related metrics such as maintainability index,unreachable code, and cyclomatic complexity. The Transaction Composition is displayed in two views: the TransactionComposition graph and the Transaction Composition table. You can switch betweenthe two views after you navigate to the Transaction Composition function. Forinformation about Transaction Composition graph and Transaction Compositiontable, see Project data from Application Discovery reports and information. Complete the following steps to navigate to analyze the Transaction Composition.Note: If you navigate to the Transaction Composition function from the transactionanalysis view of OMEGAMON for CICS data provider, you can go directly to step 5.

Select the Analysis icon ( ) to go to the Analysis page.Select the name of the analysis collection card that you want to view analysisinformation.The Collection Analysis view appears. Select the name of Application Discoverydata provider project.The page to select transaction for analysis appears. Select the transaction youwant to analyze.The Transaction Composition graph appears. You can perform multiple actions tohelp analyze the Transaction Composition. For more information, see Analyzingtransactions with the Transaction Composition graph.Select the Table icon ( ) on the top right of the view to switch to TransactionComposition table.The Transaction Composition table appears. You can perform multiple actions tohelp analyze the Transaction Composition. For more information, see Analyzingtransactions with the Transaction Composition table.Review the top-ranked artifacts on the table first as they are the potentially riskierones to modify. For more information, see Reviewing the top-ranked artifacts.Select the Graph icon ( ) on the top right of the view to switch back to theTransaction Composition graph.

Analyzing transactions with the Transaction Composition graph Analyzing transactions with the Transaction Composition table Reviewing the top-ranked artifacts

Parent topic:Analyzing and displaying project data from Application Discovery

339

1.

2.3.4.5.

--

-------

---

1.2.

--

Analyzing transactions with the TransactionComposition graph You can perform the following actions to help analyze the transactions via theTransaction Composition graph. Risk Areas analysis Risk areas are the indications of potential artifacts that could be risky. Risk areasare indicated by either blue warning icons or red warning icons. A blue warning iconindicates the artifacts that have Application Discovery metrics changes that canindicate potential source changes in the past week. A red icon indicates the value ofMaintainability Index, Unreachable Code, or Cyclomatic Complexity is above orbelow the related threshold setting. Complete the following steps to make a Risk Areas analysis.

Click the Risk Areas icon ( ) on the top header. The dialogue box explainingthe risk areas and threshold setting appears.Blue warning icons and red warning icons appears on the artifact boxes.Slide the threshold sliders to adjust the threshold values.The warning icons update based on the adjusted threshold values.Click X on the top right of the dialogue box to close the Risk Areas dialogue box.

Viewing program metrics You can view all the metrics related to each program by clicking the artifact box. Thedialogue box with program metrics appears with the following information.

The type of program and the program nameMetrics

Maintainability IndexUnreachable CodeActive StatementsSource Lines of CodeCyclomatic ComplexityDelivered BugsTotal Statements

Program Reference Info Number of incoming referencesNumber of outgoing references

Filtering artifacts The artifacts can be filtered based on 2 criteria: filter artifacts that are connected toDB2 and filter artifacts that are connected to File I/O. Complete the following steps to filter artifacts.

On the top header, drop the Filters dropdown list.On the dropdown list, check either of the following choices or both.

Select DB2 to display only the artifacts which are connected to DB2.Select FILE I/O to display only the artifacts which are connected to File I/O.

340

3. Click the Expand All icon ( ) on the top header to clear all the filters. Changing snapshot date By default the Transaction Composition graph is displayed based on the latest datacollected from the Application Discovery server. You can view the TransactionComposition graph from different snapshots by selecting a different date from theDate dropdown list on the top header. Navigating through other projects and regions A transaction may be associated with other projects and regions. You can view theTransaction Composition graph of these other projects and regions by selecting aproject or a region from the Project dropdown list or the Region dropdown list onthe top header. Navigating through other transactions There may be other transactions within a project and a region. You can view theTransaction Composition graph of other transactions by selecting a transaction fromthe Transaction dropdown list on the top header. Parent topic:Analyzing the Transaction Composition

341

1.

2.3.4.

Analyzing transactions with the TransactionComposition table You can perform the following actions to help analyze transactions via theTransaction Composition table. Risk Areas analysis Risk areas are the indications of artifacts that could be potentially risky. Risk areasare indicated by either the blue warning icons or the red warning icons. A bluewarning icon indicates the artifacts that have Application Discovery metrics changesthat can indicate potential source changes in the past week. A red icon indicates thevalue of Maintainability Index, Unreachable Code, or Cyclomatic Complexity isabove or below the related threshold setting. Complete the following steps to make Risk Areas analysis.

Click the Risk Areas icon ( ) on the top header. The dialogue box explainingthe risk areas and threshold setting appears.Slide the threshold sliders to adjust the threshold values.The warning icons update based on the adjusted threshold values.Click X on the top right of the dialogue box to close the Risk Areas dialogue box.

Changing snapshot date By default the Transaction Composition graph is displayed based on the latest datacollected from Application Discovery server. You can view the TransactionComposition table from different snapshots by selecting a different date from theDate dropdown list on the top header. Navigating through other projects and regions A transaction may be associated with other projects and regions. You can view theTransaction Composition table of these other projects and regions by selecting aproject or a region from the Project dropdown list or the Region dropdown list onthe top header. Navigating through other transactions There may be other transactions within a project and a region. You can view theTransaction Composition table of other transactions by selecting a transaction fromthe Transaction dropdown list on the top header. Parent topic:Analyzing the Transaction Composition

342

1.2.3.

-

-

Reviewing the top-ranked artifacts It is recommended that you review the top-ranked artifacts on the table for analysis.This top-ranked artifacts indicate the higher risk if there are changes to theseartifacts. The top-ranked artifacts are ranked comprehensively based on three factors:

Risk areas analysis.Outlier analysis status.Static metrics sorting

The basic idea of this ranking algorithm can be illustrated in the following figure. Forsimplicity, a two-dimensional graph is shown with the x-axis representsMaintainability Index (MI) and the y-axis represents Unreachable Code (UC). Eachsolid circle on the graph represents a program artifact with two metrics: MI and UC.

The red rectangle shown on the graph is a risk area. It is defined by a horizontalline (UC > 25%) and a vertical line (MI < 10), artifacts within the risk area (colorlabeled as red) are heuristically riskier than those outside the risk area (colorlabeled as blue). As such, checking whether a program artifact is in the risk area isthe first factor to calculate the ranking. From the graph, you can also see that there are two red artifacts and four blueartifacts having much larger distances from the center compared to the others.Such distance is measured by Mahalanobis Distance, which is a commonly-useddistance measurement between a data point and a distribution, introduced by P. C.Mahalanobis in 1936. These two artifacts can be considered as bad outliers asthey are within risk area and far away from the others. The four blue artifacts canbe considered as good outliers as they are outside the risk area and far away fromthe others. Thus, checking whether an artifact is a bad outlier is the second factorin calculating the rank. Note: ADI may generate false positives, that is, markinggood outliers as bad outliers. It usually happens when you defined impropermetrics threshold settings for risk area analysis. It is recommended that you usethe default threshold settings or ask domain experts for advice.

343

- The last ranking factor is metrics sorting. ADI sorts artifacts by their metric valuesfollowing this order: Maintainability Index, Unreachable Code, CyclomaticComplexity, Number Of Incoming References, and Number Of OutgoingReferences.

Parent topic:Analyzing the Transaction Composition

344

1.2.

3.4.5.

----

Comparing the projects You can compare project data analysis between two or more projects within ananalysis collection. To compare projects, you need to select at least 2 projects to be analyzed when youcreate a collection associated with the Application Discovery data provider. Formore information about how to add a collection associated with ApplicationDiscovery, see Adding analysis collections. Complete the following steps to compare projects data.

Select the Analysis icon ( ) to go to the Analysis page.Hover over a collection card and then select two or more compare check boxesunder maintainability status gauge for each project. Click Compare on the top right corner of the card.The Compare Projects view displays on the next page.View the following reports for comparison.

Maintainability IndexArtifactsSource Lines of CodeUnreachable Code

For more information, see Project data from Application Discovery reports andinformation. Parent topic:Analyzing and displaying project data from Application Discovery

345

-

-

-

-1.

Troubleshooting Troubleshooting helps you identify and solve problems that occur while using ADI. Limited platform support This application is built by using the Jazz infrastructure. However, ADI doesn'tsupport all the platforms that are currently listed as supported for Jazz™. For moreinformation about the supported environment for ADI, see Hardware and softwarerequirements. Requirements on the pop-up blocker configuration Currently, when you need to authenticate, the ADI log-on dialog pops up. Therefore,the browser that you are using must be configured to allow all the pop-up windowsfrom the ADI server machine. In other words, you do not need to disable your pop-blocker, but you must configure it to allow the pop-up window from the ADI server.You can typically accomplish it in the browser's preferences settings by specifyingan exception. Another method is to let the browser block the first initial pop-upwindow and then click the configuration banner or button that is displayed to informyou that a pop-up window was blocked. You need to select the option to allow pop-ups from this site in the future and then reload the page to make the pop-up log-onwindow appear. Requirements on a self-signed certificate and browserconfigurations for the application server shipping with ADI After the installation, you need to configure a certificate authority that is a signed orself-signed certificate for your application server. You need to send instructions toyour end users about how to import this certificate to avoid warnings of errors intheir browsers.

For instruction about configuring the certificates, see the Jazz online help:Configuring security certificates.For information about how to configure the certificate, you can follow the sameinstructions as described in Configuring security certificates for Report Builderservers.For information about how to configure a browser for such self-signed certificates,follow the instructions in Importing certificates and configuring browsers for ReportBuilder reports.

Icon display error on ADI browser page ADI uses a custom font to display all of its icons and browser settings might preventthe custom font from being downloaded. In that case, when you browse ADI, the UImight be filled with strange characters and numbers that don't make sense.Therefore, you need to make sure that your browser preferences are set to allowpages to choose their own fonts. This icon display error occurs in browser ofMicrosoft Internet Explorer 11 and Mozilla Firefox. To verify that your browser is configured to download the custom font, make surethat the following settings are correct:

For Microsoft Internet Explorer 11:Select Tools > Internet options.

346

2.3.

4.

5.6.

-1.2.3.4.

---

1.

On the General tab, click Accessibility. The Accessibility window appears.Clear the checkbox before Ignore font styles specified on webpages andpress OK.If the font is still not displayed correctly in the browser page, go to the Securitytab of Internet Options and select the zone that you are using for ADI.Click Custom level.... In the Security Settings window, verify that under the Downloads section, Fontdownload is set to Enable (or Prompt, assuming you have turned off the pop-upblocking).

For Mozilla Firefox:Select Tools>Options.Select Content in the left navigation area. In the Fonts & Colors section, click Advanced.... On the Fonts window, verify that the checkbox for Allow pages to choosetheir own fonts, instead of my selections above is selected and then pressOK.

SQL error (SQLCODE = -964) on massive data updatetransactions for DB2 When you perform massive DB2® update transactions, for example, deleting a dataprovider with 200,000 entries, you might observe SQL error with error code -964.The possible cause for the error is that your DB2 log setting is wrong or toorestrictive. To solve this issue, you need to increase the size of your transactionlogs. You can refer to the following sample statements to increase log size,supposing the name of your DB2 data warehouse is "DW".

db2 get db cfg for DWdb2 update db cfg for DW using LOGPRIMARY 64db2 update db cfg for DW using LOGSECOND 192

Note: The total number of primary logs plus secondary logs cannot exceed 256. It isrecommended to set larger secondary log size since they are constantly cleared byDB2. Migration error (Error 503: CRJAZ1173W) when migratingfrom ADI 1.0.1 or ADI 1.0.1 ifix01 to ADI 1.0.2 When you complete the migration steps, start the new server, and navigate to theapplications main page: https://servername:9443/adi/web, you might hit the followingerror. Error 503: CRJAZ1173W The com.ibm.team.repository.service.internal.ILogoutRestService service is not

available. This error is caused by services trying to access Jazz Team Server (JTS) rootservices too early in the application. This means that JTS is not fully started and theroot services that are required for authentication are not yet available. To fix the error, you should try the following steps:

Open a browser and navigate to the JTS admin page: https://servername:9443/jts/admin to ensure that Jazz Team Server is fully started.

347

2.

3.

4.

5.

1.

2.

-

--

-

If you can successfully access the JTS admin page, you can retry accessing theapplications main page: https://servername:9443/adi/web.Review the progress of migration tasks in the log file located inadi102/server/logs/adi.log to verify that your data is migrated successfully. Confirm that these two lines are shown in the log.CRIDA0059I The DIMEZ warehouse schemavalidation has completed. andCRIDA0052I Completed checking the ADI data migration status. If you find errors in the log, review the error message to understand the nature ofthe problem. Contact technical support to get further help with any migration errormessages.

Application log files Application logs contain important information about the JTS server and ADI serverapplications. Consult the application logs when you encounter errors in theapplication. If there is an error ID associated with the error message, theadministrator can search for that ID in the application logs to ensure the appropriatemessage is being investigated. IBM Support may request log levels be adjusted forADI application. Perform the following steps to adjust the log levels.

Browse to Installed_ADI_folder > adi > server > conf > adi and editlog4j.properties files.Go to the line 17 on the log4j.properties and switch the log level from WARN toINFO.

Other key log files are available to collect to aid the troubleshooting. The key logfiles are:

Log file for ADI application:Installed_ADI_folder\adi\server\liberty\servers\clm\logs\adi.logLog file for JTS: Installed_ADI_folder\adi\server\liberty\servers\clm\logs\jts.logLog file for ADI data collection: Installed_ADI_folder\adi\server\conf\adi\logs\adi-collections.logLog file to check which patches have been applied:Installed_ADI_folder\adi\server\liberty\servers\clm\logs\adi-patch.log

Troubleshooting tip For more troubleshooting information on ADI, you can check the Q&As on dWAnswers page. Parent topic:IBM Application Delivery Intelligence 5.0.2

348

1.2.3.4.

1.2.3.

1.2.3.

Providing feedback You can provide feedback to ADI by sending an email, opening a Service Request,or sending a Request For Enhancement (RFE). Sending an email Complete the following steps to send an email to ADI.

Log in to ADI with your user ID and password.On the main menu located on the left panel, click on the Help Menu.Select Send Email in the sub menu panel.Your default email program is opened with the default recipient and subject.

Opening a Service Request In the case that you have problems or issues and need ADI support, you can open aService Request. You need to have an IBM ID and password to open a ServiceRequest. You can register your IBM ID at IBM site. Complete the following steps to open a Service Request to ADI.

Login to ADI with your user ID and password.On the main menu located on the left panel, click on the Help Menu.Select Open Service Request in the sub menu panel. You will be redirected tothe Service Request submission page on IBM site.

Sending a Request For Enhancement (RFE) In the case that you want to request or suggest for an enhancement of ADIcapabilities, you can submit a Request For Enhancement. You need to have an IBMID and password to open a request. You can register IBM ID at IBM site. Complete the following steps to open a Service Request to ADI.

Login to ADI with your user ID and password.On the main menu located on the left panel, click on the Help Menu.Select Open Service Request in the sub menu panel. You will be redirected tothe Service Request submission page on IBM site.

Parent topic:IBM Application Delivery Intelligence 5.0.2

349

--

Accessibility features for ADI Accessibility features assist users who have a disability, such as restricted mobilityor limited vision, to use information technology content successfully. Accessibility features ADI includes the following major accessibility features:

Keyboard-only operationOperations that use a screen reader

ADI uses the latest W3C Standard, WAI-ARIA 1.0 (http://www.w3.org/TR/wai-aria/),to ensure compliance to US Section 508(http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards), and Web Content Accessibility Guidelines (WCAG) 2.0(http://www.w3.org/TR/WCAG20/). To take advantage of accessibility features, usethe latest release of your screen reader in combination with the latest web browserthat is supported by this product. The ADI online product documentation in IBM® Knowledge Center is enabled foraccessibility. The accessibility features of IBM Knowledge Center are described athttps://www.ibm.com/support/knowledgecenter/en/about/releasenotes.html#accessibility. Keyboard navigation This product uses standard navigation keys. ADI uses Tab and Return as the keyboard shortcuts. To enable keyboard navigation on Apple Mac OS X for your browser, click SystemPreferences > Keyboard > Shortcuts, and select the All controls radio box at thebottom of the dialog. Related accessibility information In addition to standard IBM help desk and support websites, IBM has established aTTY telephone service for use by deaf or hard of hearing customers to access salesand support services: TTY service 800-IBM-3383 (800-426-3383) (within North America) IBM and accessibility For more information about the commitment that IBM has to accessibility, see IBMAccessibility(www.ibm.com/able). Parent topic:IBM Application Delivery Intelligence 5.0.2

350