CA Business Intelligence

(1)

N-Tier Implementation and Configuration

Guide

Release 3.2

(2)

This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

(3)

Contact CA

Contact CA Support

For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At

http://ca.com/support, you can access the following:

■ Online and telephone contact information for technical assistance and customer services

■ _{Information about user communities and forums} ■ Product and documentation downloads

■ CA Support policies and guidelines

■ _{Other helpful resources appropriate for your product}

Providing Feedback About Product Documentation

If you have comments or questions about CA product documentation, you can send a message to [email protected].

If you would like to provide feedback about CA product documentation, complete our short customer survey, which is available on the CA Support website at

(4)

(5)

Contents 5

Chapter 1: Introduction

9

Overview ... 9

Architecture ... 10

Chapter 2: Implementing CABI N-Tier Environment

11

Pre-requisites ... 11

CABI N-Tier Implementation ... 12

Create Users for CMS and Audit Databases in SQL Server ... 12

Create CMS_DSN and AUDIT_DSN ODBC Connections on Intelligence Tiers ... 14

Set up CABI Common File Share on Shared File Repository... 16

Install the First CABI Intelligence Tier ... 17

Install the CABI Web Application Tiers ... 23

Install the Second CABI Intelligence Tier ... 28

Install the CABI Processing Tier ... 33

Configure Servers in the CABI N-Tier Environment ... 38

Configure Input and Output File Repository Servers ... 41

Chapter 3: Configuring Additional Options for CABI

43

Configure CABI Tomcat for SSL (HTTPS) ... 43

Modify the Shortcuts to Use the New URL’s ... 45

Configure Applications to Use the New InfoView URL ... 45

Integrate CA Business Intelligence with LDAP ... 47

Integrate CA Business Intelligence with Tivoli Directory Server ... 52

Modify InfoView to Select Different Authentication Types ... 57

Install and Configure Apache Load Balancer for CABI Web Application Tiers ... 58

Pre-requisites ... 59

Install the Apache HTTP Server ... 61

Configure Apache HTTP Server ... 63

Configure CABI Web Tier ... 65

Chapter 4: Deploying CABI Reports of CA Products

67

Deploy CA Service Catalog Manager Reports ... 68

Verify the Report Deployment ... 70

Deploy CA Software Compliance Manager Reports ... 73

(6)

6 N-Tier Implementation and Configuration Guide

Deploy CA IT Client Manager Reports ... 76

Deploy CA Clarity Reports ... 82

Deploy CA Clarity on SQL Server Database ... 82

Deploy CA Clarity on Oracle Database ... 86

Perform Post-Installation Steps ... 88

Deploy CA Service Desk Manager Reports ... 89

Deploy CA Asset Portfolio Manager Reports (CA Services Provided Reports) ... 93

Deploy CA CAF to Enable CustomParams for Custom Prompt Pages ... 96

Verify the CAF Registration ... 99

Deploy CA Service Operations Insight (CA SOI) Reports ... 100

Install the CA SOI Reports ... 101

Perform Post-Installation Steps ... 104

Enable Custom Report Prompts Pages ... 106

Chapter 5: Integrating CA Products with CA Business Intelligence

109

Integrate CA Service Desk Manager with CABI ... 109

Configure Date Range Values and Join Parameters for the ODBC Connection... 112

Integrate CA Clarity with CABI ... 113

Integrate CA Service Catalog with CABI ... 114

Integrate CA Software Compliance Manager with CABI ... 115

Create a User in CABI and Assign Permissions ... 116

Assign Security to the CA SWCM Reports Folder ... 117

Integrate CA SWCM and CA Business Intelligence ... 120

Integrate CA Service Operations Insight with CABI ... 121

Configure Single Sign On for Reports ... 122

Configure Users to Access SOI Reports ... 124

Modify Security on SAM Reports Folder ... 125

Chapter 6: Validating the Solution

129

Validate the Server Intelligence Agent ... 130

Validate the File Repository Servers ... 132

Validate the Servers Status ... 134

Validate the CABI Universe DesignerTopic ... 136

Validate the InfoView and the Configuration Management Console ... 141

(7)

Contents 7

Appendix A: Configuring Reports and Universe Connections

145

Change ODBC and Universe Connection Settings ... 145

Change ODBC Connection ... 145

Change SDM ODBC Connection ... 148

Update the Universe Connection ... 148

Appendix B: Managing Passwords

153

Change Password for CA Clarity ... 153

Change Password for CA Service Operations Insight ... 153

Change Password for CA Software Compliance Manager ... 154

Appendix C: Troubleshooting

157

ODBC OpenAccess SDK Driver, Cannot Open File ... 157

Log in to CA Business Intelligence Fails When Installing ITCM Reports ... 160

CABI Installer Fails to Launch with Java Virtual Machine Error ... 161

Server Intelligence Agent Fails to Start on Intelligence Tiers ... 161

File Repository Server Settings Are Not Updated After Changing to CABI_SHARE Folder ... 162

Appendix D: Applying Business Objects XI Service Pack 5 Patch

163

Update the First Intelligence Tier (Primary CMS HOST) to Service Pack 5 ... 163

Update the Second Intelligence Tier to Service Pack 5 ... 166

Update the Processing Tiers to Service Pack 5 ... 169

Update the Web Tier to Service Pack 5 ... 171

Perform Post-Implementation Steps on Web Tiers after Updating to Service Pack 5 ... 173

(8)

(9)

Chapter 1: Introduction 9

Chapter 1: Introduction

Business Intelligence is an iterative user-centric process that includes accessing, exploring, and analyzing information, developing insights, and gaining an in-depth understanding. This process leads to improved and informed decision making.

An effective Business Intelligence architecture helps provide the following benefits:

■ _{Increase sales}

■ Deepen customer relationships

■ Build better products

■ _{Provide better services} ■ _{Streamline operations} ■ Reduce costs

■ Improves management and operational processes

CA Business Intelligence (CABI) provides performance and information management, reporting, and query analysis tools.

Note: CABI includes a license to create reports that are based on data from specific CA

Technologies solutions.

This section contains the following topics: Overview (see page 9)

Architecture (see page 10)

Overview

This guide provides detailed steps to implement CABI in a clustered environment (CABI N-tier).

This guide is intended for the CA product Administrators (or their equivalent) who are responsible for performing the following tasks:

■ Implementing CABI onsite on a clustered environment.

■ Deploying reports of various CA products on a shared CABI environment.

■ _{Integrating CABI with CA products.}

■ _{Configuring authentication and authorization in CABI.}

(10)

Architecture

The CABI N-tier architecture consists of six Business Objects servers and one database server. This configuration accommodates a large user population that needs access to the reporting functionality that CA Business Intelligence offers. This solution provides high availability and the solution is scalable.

Note: CABI N-tier requires a shared file repository location for the intelligence tiers. An

additional server is used to store the files that the Input and Output File repository servers use. As a best practice, store the share containing the repository files on a high available Storage Area Network (SAN) or Network Attached Storage (NAS). It also eliminates the need of an additional server.

The operating system that is used on all CABI servers is Windows 2008 R2 Enterprise Service Pack 1.

(11)

Chapter 2: Implementing CABI N-Tier Environment 11

Chapter 2: Implementing CABI N-Tier

Environment

You can install and implement the CA Business Intelligence infrastructure by leveraging the default CA Business Intelligence installation and configuration as specified in CA Business Intelligence documentation. However, there are instances where a more robust reporting infrastructure is needed. CA Business Intelligence is an enterprise solution that can support multiple configurations and address- performance, scalability, and reliability concerns of larger enterprises.

In a multiproduct and multiuser environment, a single CABI instance cannot provide optimum performance to end users. CABI clustered implementation ensures that sufficient resources are available on each tier for processing large number of reports and scheduled jobs.

This section contains the following topics: Pre-requisites (see page 11)

CABI N-Tier Implementation (see page 12)

Pre-requisites

Complete the following pre-requisites before you implement the CABI N-tier environment:

■ _{Install the .NET Framework on all servers.}

(12)

CABI N-Tier Implementation

Perform the following steps to complete the CABI N-tier implementation: 1. Create users for CMS and Audit databases in SQL Server. (see page 12)

2. Create CMS_DSN and AUDIT_DSN ODBC connections on the Intelligence Tiers. (see page 14)

3. Set up CABI Common File Share on Shared File Repository (see page 16). 4. Install first CABI Intelligence Tier. (see page 17)

5. Install CABI Web Application Tier. (see page 23) 6. Install second Intelligence Tier. (see page 28) 7. Install CABI Processing Tier. (see page 33)

8. Configure servers in CABI N-Tier Environment. (see page 38) 9. Configure Input and Output File Repository Servers (see page 41).

Create Users for CMS and Audit Databases in SQL Server

CABI supports Microsoft SQL Server and Oracle as its system database. Microsoft SQL Server 2008 R2 is used as the database server for this implementation. Create the CMS and Audit databases, users, and provide the users with dbowner privileges, before installing CABI.

Follow these steps:

1. Log in to the SQL Server Management Studio on the database server as an Administrator user.

2. Expand the Security, Logins folder and create two users as CMSAdmin and AuditAdmin.

(13)

Chapter 2: Implementing CABI N-Tier Environment 13 3. Right-click Databases and select New.

The New Database dialog opens.

4. Enter the database name as CMS.

5. Click the eclipse (…) button for the Owner field The Select Database Owner dialog opens.

(14)

7. Expand the Security, Logins folder; right-click the CMSAdmin user and select Properties.

8. Change the default database to CMS in the Properties section.

9. Click User Mapping and assign the db_owner role to the user in the Properties section.

10. Repeat Steps 3 to 9 to create the CMSAUDIT database and assign AuditAdmin as the owner.

Create CMS_DSN and AUDIT_DSN ODBC Connections on Intelligence Tiers

CABI uses ODBC data source connections to connect to the system databases (CMS and Audit). Create the data source connections on all intelligence and processing tiers, before installing the CABI.

1. Double-click the odbcad32 executable file from the C:\Windows\SysWOW64\ folder and start the ODBC Administrator.

2. Click the System DSN tab and click Add. The Create New Data Source dialog opens. 3. Select SQL Server from the list and click Finish.

Note: If SQL Server is not available in this list, download and install the appropriate

MS SQL Server driver from the Microsoft website.

4. Provide the name of the data source, which is used in the BusinessObjects XI (BOXI) install process and click Next.

(15)

Chapter 2: Implementing CABI N-Tier Environment 15 5. Click the With SQL Server authentication using a login ID and password entered by

the user option, enter the already created CMS user name and password, and click Next.

This verifies the user credentials and tests the connection to the database.

6. Resolve any connection or login problems before continuing with the creation of the data source connections.

7. Click the Change the default database to option and select CMS from the drop-down list, and click Next.

Note: The default database for this user is the CMS database.

8. Click Finish to complete the DSN configuration. The ODBC Microsoft SQL Server Setup dialog opens.

(16)

16 N-Tier Implementation and Configuration Guide 9. Click Test Data Source.

The test result displays the message.

10. Resolve any connection or login problems if the test is not successful and click OK. 11. Repeat Steps 1 to 10 for the CMSAUDIT database using the AuditAdmin user.

Set up CABI Common File Share on Shared File Repository

For the current CABI installation, the share is created on an individual Windows server and is shared using both Windows and NFS. Therefore, you can access it directly from another computer or can mount it on an ESX server. However, we recommend you to create this share on a high available SAN or NAS storage.

1. Log in to the Server, which is used to store the file repository, as an Administrator user.

2. Open Windows explorer and create a new folder named CABI_SHARE. 3. Right-click the folder and select Properties section.

4. Click Share to share the folder.

5. Click the Share tab and click Permissions. 6. Select Everyone from the list of users/groups.

(17)

Chapter 2: Implementing CABI N-Tier Environment 17 7. Click Permission Level and change it to Read/Write so that the BOXI servers can

store files on this share.

The folder has a sharing icon now.

8. Create three sub-folders named Index, InputFiles, and OutputFiles in the shared folder.

Install the First CABI Intelligence Tier

Intelligence tiers are responsible for the following main functions:

■ Authentication and Authorization

■ File repository management

■ _{Database access}

■ _{Event management}

1. Run Setup.exe from the CABI media.

2. Click OK on the CA Business Intelligence Setup dialog. The Welcome dialog opens.

3. Click Next.

The End User License Agreement dialog opens. 4. Accept the license agreement and click Next.

(18)

5. Select No for templates and response file and click Next.

6. Select No for the Do you want to save the response file option and click Next.

7. Click Install.

The CA Business Intelligence Setup dialog opens. 8. Click Next.

(19)

Chapter 2: Implementing CABI N-Tier Environment 19 9. Accept the license agreement and click Next.

10. Select the required language packs and click Next. The Install Type dialog opens.

11. Select the Custom or Expand Install option and accept the default install location.

Note: You can provide a new install location by clicking Browse.

12. Click Next.

The Select Features dialog opens. 13. Perform the following selections:

a. Expand Client Components and select Import Wizard and Universe Designer.

Note: Clear all other components.

(20)

c. Clear the following options under Server Components:

■ MySQL under Central Management Server

■ Crystal Reports Processing Server

■ Publication Job Server

■ Report Application Server

■ Multi-Dimensional Analysis Server

■ Crystal Reports Job Server

■ Destination Job Server

■ List of Values Job Server

■ Desktop Intelligence Job Server

■ Program Job Server

■ Adaptive Job Server

■ Web Application Container Server

■ Adaptive Processing Server

■ Web Intelligence Processing Server

■ Desktop Intelligence Servers

(21)

Chapter 2: Implementing CABI N-Tier Environment 21 d. Clear the Enable servers upon installation check box, and click Next.

The CMS Clustering dialog opens.

14. Provide the following information and click Next.

■ Select Yes for new CMS.

■ Enter 6400 for the CMS port.

■ Enter the CMS Administrator password

■ Clear the Configure the BusinessObjects Enterprise Administrator password at a later time check box.

Note: The CMS Administrator password set on this dialog is the BOXI Application

Administrator. The associated username is Administrator.

15. Accept default values for Server Intelligence Agent configuration and click Next. The CMS Database Information dialog opens.

16. Assign the CMS_DSN and Audit_DSN for database connectivity and click Next. 17. Click Finish when the install completes.

This initiates the patch installation.

18. Restart the server after the patch installation is complete.

Perform Post-Installation Steps

After you install the first CABI Intelligence Tier, perform the following steps to complete the post-installation.

1. Open the Central Configuration Manager utility. 2. Stop the Server Intelligence Agent.

(22)

3. Right-click the Server Intelligence Agent and select Properties section.

4. In the Configuration tab, select the Change Cluster Name to check box and type CABI-CLUSTER in the text box.

5. Click Apply and click OK.

6. In the Properties tab, under the Log On As section, provide the following information:

(23)

■ Select the local Administrator account using the Browse button in the User field.

■ Enter the password of the local Administrator user in the Password and Confirm Password fields.

Note: A domain account can also be used in the User field but the user must be a

part of Local Administrators group on the Intelligence Tier.

8. Start the Server Intelligence Agent in the Central Configuration Manager.

Install the CABI Web Application Tiers

Important! Check the following validations, before installing the Web Application Tiers:

■ Web Tiers are able to ping all other CABI servers using the FQDN and hostname

■ _{The tomcat port 8080 is not blocked by any firewall}

3. Click Next.

(24)

4. Accept the license agreement and click Next. The Install CA Sample Templates dialog opens.

5. Select No for templates and response file and click Next.

6. Select No for the Do you want to save the response file option and click Next. 7. Click Install.

The CA Business Intelligence Setup dialog opens. 8. Click Next.

The End User License Agreement dialog opens. 9. Accept the license agreement and click Next. 10. Select the required language packs and click Next.

(25)

Chapter 2: Implementing CABI N-Tier Environment 25 11. Select the Web Tier option and use the default install location, and click Next.

The Select Features dialog opens.

Note: You can provide a new destination location by clicking Browse.

12. Select all components and click Next. The Existing CMS Information dialog opens. 13. Provide the following information.

■ Enter the first Intelligence Tier for the CMS hostname

■ Enter 6400 for the CMS port

■ Enter the CMS Administrator Password

14. Click Next.

(26)

■ Select the Java Web Application Server check box.

■ Select the Install Tomcat application server and deploy to it option. The Configure Tomcat dialog opens.

16. Use the default port values and click Next. The Start Installation dialog opens. 17. Click Next to start Installation.

18. Clear the Launch SAP BusinessObjects Administration Console check box and click Finish.

This initiates the patch installation.

(27)

Perform Post-Installation Steps

After you install the Web Application Tier, perform the following steps to complete the post-installation.

1. Log in to the first Web Tier.

2. Open Windows Explorer and navigate to C:\Program Files

(x86)\CA\SC\CommonReporting3\Tomcat55\webapps\PlatformServices\WEB-INF\c lasses.

3. Create a new file and name it as cluster.properties as shown: cms.clusters=@<cluster_name>

cms.clusters.<cluster_name>=<first intelligence tier>. <second intelligence tier> An example is shown in the following screen.

4. Save the file.

5. Open the file dsws.properties present under C:\Program Files

(x86)\CA\SC\CommonReporting3\Tomcat55\webapps\dswsbobje\WEB-INF\classes 6. In the file, for the domain property enter the value as the host name of first

intelligence tier. An example of the setting is provided below.

7. Save the file.

Open the Central Configuration Manager application from Start, All Programs, Business Objects XI 3.1, and Business Objects Enterprise.

(28)

8. Restart the Tomcat service.

9. Perform the installation and post-installation steps on the second Web Tier.

Install the Second CABI Intelligence Tier

Important! Verify if second Intelligence Tier is able to ping the first Intelligence Tier, before executing the setup.exe.

3. Click Next.

(29)

Chapter 2: Implementing CABI N-Tier Environment 29 5. Select No for templates and response file and click Next.

6. Select No for the Do you want to save the response file option and click Next.

7. Click Install.

The CA Business Intelligence Setup dialog opens.

8. Click Next.

(30)

9. Accept the license agreement and click Next. 10. Select the required language packs and click Next.

The Install Type dialog opens.

11. Select the Custom or Expand Install option and accept the default install location.

12. Click Next.

The Select Features dialog opens.

13. Perform the following selections: a. Clear the following components:

■ Client Components

■ Web Tier Components

b. Expand Server Components and clear the following components:

■ MySQL (under Central Management Server)

■ Crystal Reports Processing Server

■ Publication Job Server

■ Report Application Server

■ Multi-Dimensional Analysis Server

■ Crystal Reports Job Server

■ Destination Job Server

■ List of Values Job Server

(31)

■ Adaptive Job Server

■ Adaptive Processing Server

■ Web Intelligence Processing Server

■ Dashboard and Analytics Servers

c. Clear the Enable servers upon installation check box, and click Next. The CMS Clustering dialog opens.

■ Select No to enter information of the existing CMS server.

■ Enter 6400 for the CMS port.

■ Enter the server name of the first Intelligence Tier for the existing CMS Hostname.

■ Enter the CMS Administrator password. The Server Intelligence Agent dialog opens. 15. Accept default values and click Next.

The CMS Database Information dialog opens. 16. Provide the following information and click Next.

■ CMS Database:

– Existing Database: SQL Server (ODBC)

– Login ID: CMSAdmin

– Password: *****

■ Enable the Auditing Database option

■ Auditing Database:

– Existing Auditing Database: SQL Server (ODBC)

– Login ID: AUDITAdmin

– Password: *******

■ Clear the Reset existing database check box 17. Click Next to start the installation.

Note: The CABI installer installs BusinessObjects Enterprise.

18. Click Finish when the install completes. This initiates the patch installation.

(32)

19. Restart the server after the patch installation is complete.

Perform Post-Installation Steps

After you install the second CABI Intelligence Tier, perform the following steps to complete the post-installation.

1. Log in to the second Intelligence Tier.

2. Launch the Central Configuration Manger from Start, All Programs, Business Objects XI 3.1, and Business Objects Enterprise.

3. Stop the Server Intelligence Agent

4. Right-click the Server Intelligence Agent and select Properties section. 5. In the Configuration tab, verify that the Server Intelligence Agent belongs to

CABI-CLUSTER.

6. In the Properties tab, under the Log On As section, provide the following information:

■ Clear the System Account check box.

■ Select the local Administrator account using the Browse button in the User field.

(33)

■ Enter the password of the local Administrator user in the Password and Confirm Password fields.

Note: A domain account can also be used in the User field but the user must be a

part of Local Administrators group on the Intelligence Tier.

Install the CABI Processing Tier

Important! Check the following validations, before installing the Processing Tier:

■ _{Processing Tiers are able to ping all other servers}

■ Verify \\CABI-Store\CABI_SHARE is accessible from both the Processing Tier servers

3. Click Next.

(34)

5. Select No for templates and response file and click Next. 6. Click Install.

The CA Business Intelligence Setup dialog opens.

7. Click Next.

The End User License Agreement dialog opens. 8. Accept the license agreement and click Next. 9. Select the required language packs and click Next.

The Install Type dialog opens.

10. Select Custom or Expand Install option and accept the default install location.

11. Click Next.

The Select Features dialog opens. 12. Perform the following selections:

a. Clear the following components:

■ Client Components

■ Web Tier Components

■ Samples

(35)

Chapter 2: Implementing CABI N-Tier Environment 35 b. Expand Server Components and clear the following components:

■ Central Management Server

■ Event Server

■ Input File Repository Server

■ Output File Repository Server

■ Crystal Reports Cache Server

c. Clear the Enable servers upon installation check box, and click Next. The Search ServiceClustering dialog opens.

13. Enter the share pointing to the index folder created \\CABI-STORE\SHARE\Index and click Next.

The CMS Clustering dialog opens.

■ Enter the name of first Intelligence Tier server for CMS Hostname

■ Enter 6400 for CMS port

■ Enter CMS Administrator password The Server Intelligence Agent dialog opens.

(36)

15. Accept the default values for the Server Intelligence Agent configuration and click Next.

16. Click Next to start the installation.

Note: The CABI installer installs the BusinessObjects Enterprise.

17. Click Finish when the install completes. This initiates the patch installation.

18. Restart the Processing Tier when prompted to do so. Restart the server after the patch installation is complete.

19. Repeat Steps 1 to 17 on the second Processing Tier.

Perform Post-Implementation Steps

Upon default installation of CABI in N-tier environment, the Dashboards menu is not enabled in InfoView. This issue can be resolved by following the steps that SAP suggested. The following SAP note contains the issue details:

1710027 - InfoView Dashboard option is unavailable on multi-server install.

However, you can enable the Dashboard menu by using a workaround.

1. Log in to first Processing Tier server.

2. Open the Packages folder from the C:\Program Files

(37)

Chapter 2: Implementing CABI N-Tier Environment 37 3. Copy all the files with extension .XML and .XSD to the same folder location on the

intelligence tiers.

4. Restart the Server Intelligence Agent on the intelligence Tiers from the Central Configuration Manager application.

(38)

Configure Servers in the CABI N-Tier Environment

The servers are disabled after the install process. Enable the servers on the respective tiers to complete the configuration. A table detailing the servers that require enable on each tier is provided in this section.

2. Log in to the Central Management Console on the [Web] Application Tier from Start, Programs, BusinessObjects XI 3.1, BusinessObjects Enterprise, and BusinessObjects Enterprise Central Management Console.

3. Log in using the Administrator user name and password credentials and select Authentication as Enterprise.

4. On the CMC Home page, in the Organize section, click Servers.

Note: You can navigate in the Central Management Console using any of the

following traversals:

■ The shortcuts in the organize section.

■ The icon tabs to the left of the shortcuts.

(39)

Chapter 2: Implementing CABI N-Tier Environment 39 5. Click the Servers List node in the Servers tree.

All available application processes are displayed in the right pane.

The following screenshot provides information about the server components that you must enable or disable for each tier

Note: The following table displays the server components sorted by the Kind

column. We recommend that you sort the CMC Server list based on the Kind column.

6. Select and right-click the server name, and click Enable Server or Disable Server as shown in the following image.

Note: If you mark a server as disabled, it cannot process jobs in spite of it being

(40)

7. Use the following table to enable or disable BOXI servers based on their corresponding tier.

The first column lists the server by its kind which corresponds with the BOXI Kind column. These servers are further classified based on the server name, which corresponds to the BOXI Server Name column.

Note: An X in the column indicates "Enable this server component on all server

machines on this tier"; A blank in the column indicates "Disable this server component all server machines in this tier".

Kind - Server Name Intelligence

Tier

Processing Tier

Web Application Tier

Adaptive Processing Server X

Adaptive Processing Server – Multi Dimensional Analysis Services Server

X

Central Management Server X

Connection Server X

Crystal Reports Cache Server X

Crystal Reports Processing Server X

Dashboard Analytics Server X

Dashboard Server X

Event Server X

File Repository Server – Input File Repository

X

File Repository Server - Output File Repository

X

Job Server – Adaptive Job Server X

Job Server – Crystal Reports Job Server

X

Job Server – Destination Job Server X

Job Server – List of Values X

Job Server – Program Job Server X

Job Server – Publication Job Server X

PM Metrics Server X

(41)

Kind - Server Name Intelligence

Tier Processing Tier Web Application Tier PM Rules Server X

Predictive Analysis Server X

Process Analysis Server X

Report Application Server X

Sets Profile Server X

Sets Query Server X

Web Intelligence Processing Server X

Configure Input and Output File Repository Servers

The installation process sets the input and output file repositories to the local host. Upon the installation of the CABI N-tier environment, configure the file repository servers manually to the shared input and output file repository folders.

2. Launch the Central Management Console application.

3. Log in using the Administrator user name and password credentials and select Authentication as Enterprise.

4. On the CMC Home page, in the Organize section, select Servers and click the Kind column to sort the servers by Kind.

a. For each File Repository Server whose server name consists of InputFileRepository, right-click and select Properties section:

■ Change the Temporary Directory to

“\\CABI-STORE\CABI_SHARE\InputFiles\Temp “

■ Change the File Store Directory to “\\CABI-STORE\CABI_SHARE\InputFiles “

(42)

a. For each File Repository Server whose server name consists of OutputFileRepository, right-click and select Properties section:

– Change the Temporary Directory to

“\\CABI-STORE\CABI_SHARE\OutputFiles\Temp”

– Change the File Store Directory to “\\CABI-STORE\CABI_SHARE \OutputFiles”

– Click Save and Close

5. Log in to the first Intelligence Tier and launch Central Configuration Manager application.

6. Restart Server Intelligence Agent.

(43)

Chapter 3: Configuring Additional Options for CABI 43

Chapter 3: Configuring Additional Options

for CABI

The additional configuration is not required for CABI N-tier install, but you can perform them on product server.

This section contains the following topics:

Configure CABI Tomcat for SSL (HTTPS) (see page 43) Integrate CA Business Intelligence with LDAP (see page 47)

Install and Configure Apache Load Balancer for CABI Web Application Tiers (see page 58)

Configure CABI Tomcat for SSL (HTTPS)

The Tomcat web server for CABI provides a non-SSL connector by default. However, you can configure Tomcat to use SSL, which secures the communication between CA Business Intelligence web servers and client environments.

1. Log in to the CABI first Web Tier server.

2. Open the Central Configuration Manager application and stop the Apache Tomcat service.

3. Open the command prompt and navigate to the %JAVA_HOME/bin folder.

Note: The default location is C:\Program

Files(x86)\CA\SC\CommonReporting3\javasdk\bin.

4. Run the command %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA and provide the information for the following questions:

■ Enter keystore password

(44)

Configure CABI Tomcat for SSL (HTTPS)

■ What is the name of the organizational unit

■ What is the name of the organization

■ What is the name of your city or locality

■ What is the name of your state or province

■ What is the two-letter country code for this unit

5. Enter yes on the confirmation prompt and press the Enter key.

6. Press Enter for the Enter key password for <tomcat> to use the same password. A .keystore file is created under C:\Users\Logged_In_User home folder.

7. Copy the .keystore file to the C:\Program Files (x86)\CA\SC\CommonReporting3 folder.

8. Open Server.xml under C:\Program Files

(x86)\CA\SC\CommonReporting3\Tomcat55\conf folder using the text editor. 9. Find the following section, which is commented out.

10. Uncomment the connector port section and add the following line:

keystoreFile="C:/Program Files (x86)/CA/SC/CommonReporting3/.keystore" keystorePass="password"

(45)

Chapter 3: Configuring Additional Options for CABI 45 12. Start the Tomcat service from the Central Configuration Manager application.

These steps disable the InfoView and CMC on port 8080 and enable on port 8443. New InfoView URL:

https://<Web Tier>:8443/InfoView App/logon.jsp New CMC URL:

https://<Web Tier>:8443/CmcApp/logon.face

Important! This procedure is required for configuring for SSL.

1. Open Windows Explorer and navigate to the folder C:\Program Files

(x86)\CA\SC\CommonReporting3\BusinessObjects Enterprise 12.0\win32_x86. 2. Right-click on the cmc.url and select Properties section.

3. Change the URL for CMC app and click Apply.

4. Launch CMC from the Start menu and verify whether the changed URL is working. 5. Navigate to the folder C:\Program Files

(x86)\CA\SC\CommonReporting3\Tomcat55\bobjsetup. 6. Right-click on the InfoView .url and select Properties section. 7. Change the URL for InfoView app and click Apply.

8. Launch CMC from the Start menu and verify whether the changed URL is working. 9. Repeat the Configure CABI Tomcat for SSL procedure and Steps 1 to 8 on second

Web Tier to enable the second Web Tier for SSL.

Configure Applications to Use the New InfoView URL

After configuring the CABI Web Server for SSL, reconfigure the products that are integrating with CABI, to use the new HTTPS URL. The following sections provide detailed steps for configuring different CA products to use the new URL.

■ Configure CA Service Desk Manager

■ Configure CA Service Catalog

■ _{Configure CA Clarity}

(46)

Configure CA Service Desk Manager

1. Log in to the CA Service Desk Manager (SDM) web interface as an Administrator user.

2. Click Administration, Options Manager, and Web Report.

3. Change the value for bo_server_location from http://<Web Tier>:8080 to https://<Web Tier>:8443.

4. Restart the CA Service Desk Manager service.

Configure CA Service Catalog

1. Log in to the CA Service Catalog as an Administrator user.

2. Click Administration, Configuration, and CA Business Intelligence (CABI) and change the values as shown in the following screen.

3. Restart the CA Service Catalog service.

Configure CA Clarity

1. Log in to the CA Clarity NSA as an Administrator user. 2. Click Servers and click Properties section.

3. Click Reporting.

4. Change the value for Service URL http://<Web

Tier>:8080/dswsbobje/services/session to https://<Web Tier>:8443/dswsbobje/services/session.

5. Change the value for Web URL from http://<Web Tier>:8080 to https://<Web Tier>:8443.

6. Restart the CA Clarity services.

(47)

Integrate CA Business Intelligence with LDAP

Configure CA Service Operations Insight

1. Log in to the CA Service operations Insight (SOI) as an Administrator user. 2. Expand the CA Service Operations Insight UI server configuration, ServerName,

Report Configuration. 3. Change the following values:

■ Report port: 8443

■ Enable SSL: yes 4. Save the changes. 5. Restart CA SOI services.

6. Log in to the CA SOI to verify whether the dashboard and reports hyperlinks are working.

Integrate CA Business Intelligence with LDAP

A new group in the active directory named CABIUsers is created to map the users in CABI during configuration.

Note: A new active directory server is created to configure LDAP integration in the same

DVNAT environment with the server name as LDAP Server.

2. Launch the Central Management Console application.

3. Log in using Administrator user name and password credentials. 4. Click Authentication in the Manage section of the CMC Home page.

The Authentication dialog opens.

(48)

48 N-Tier Implementation and Configuration Guide 5. Double-click on LDAP.

The LDAP configuration wizard opens. 6. Click Start LDAP Configuration Wizard.

7. Type the host name and the port of LDAP server in the form of hostname:port In the Add LDAP host box and click Add.

8. Click Next.

9. Select Microsoft Active Directory from the LDAP Server Type drop down.

10. Click Show Attribute Mappings.

(49)

Chapter 3: Configuring Additional Options for CABI 49 11. Change the following mapping values in the LDAP Server Attribute Mappings

section and click Next to proceed.

■ Username : sAMAccountName

■ Default User Search Attribute: sAMAccountName

(50)

13. Enter the distinguished name of Administrator user in the Distinguished Name text field.

Example: CN=Administrator,CN=Users,DC=itg,DC=local.

14. Type the Administrator user password in the Password text box and click Next to set the SSL settings.

15. Select Basic (No SSL) for SSL and click Next to set the SSO settings. 16. Select Basic (No SSO) for Authentication and click Next.

17. Select the Create a new account for every added LDAP alias option under the New Alias Options section.

(51)

Chapter 3: Configuring Additional Options for CABI 51 18. Select the Create new aliases when the Alias Update occurs option under the Alias

Update Options section.

19. Click Finish.

20. Type the CABIUsers group name (created earlier) in the Add LDAP group text box.

21. Select the Import Full Name and Email Address, and Give LDAP attribute binding priority over AD attribute binding options on the same dialog.

(52)

52 N-Tier Implementation and Configuration Guide 22. Click Update.

The CABIUsers group CN is updated automatically.

Integrate CA Business Intelligence with Tivoli Directory Server

CABI can integrate with different LDAP servers. Integrating with the Active Directory is described in the previous section. This section describes the process to integrate with the IBM Tivoli Directory Server.

Perform the following tasks to integrate the CA Business Intelligence with Tivoli Directory Server:

1. Create Group in Tivoli Directory Server. 2. Configure LDAP Authentication.

Create Group in Tivoli Directory Server

Create a group and add the required users to the group in Tivoli Directory Server. After the group is created, this group gets mapped in CABI and the respective users are imported.

1. Log in to the Tivoli Directory Server Web Administration Tool.

2. Enter User DN as root and password for root user on the Directory server login dialog.

The Tivoli Directory Server Web Administration Tool dialog opens. 3. Expand Users and groups and click Add Group on the left pane.

(53)

Chapter 3: Configuring Additional Options for CABI 53 4. Enter the group name as CABIUsers and click Next.

5. Under Users click Add and select all users that are required to be part of the group, and click OK.

(54)

Configuring LDAP Authentication

After you create the group and add the required users to the group in Tivoli Directory Server, configure LDAP authentication to complete the integration of the CABI with Tivoli Directory Server.

1. Log in to CABI as an Administrator.

2. Click Authentication under Manage section and open LDAP settings.

3. Enter the LDAM server name as follows servername:ldap port in the Add LDAP host field and click Add.

(55)

Chapter 3: Configuring Additional Options for CABI 55 5. Change the mapping information as follows and click Next.

■ User Name: uid

■ Default User Search Attribute: uid

(56)

7. Enter the distinguished name of Administrator user as cn=root, in the Distinguished Name and password details in the Password fields.

8. Click Next to set the SSL settings. 9. Click Next to set the SSO settings. 10. Click Next on Authentication dialog.

11. Select the following LDAP alias options and click Next.

(57)

Chapter 3: Configuring Additional Options for CABI 57 13. Enter the group dn value created for CABI and click Add in the Add LDAP group

field.

14. Click Update.

The dialog displays with the added group name in the Add LDAP group section. 15. Close the LDAP setting and navigate to Users And Groups, Users List.

16. Verify whether all the users are imported.

17. Launch InfoView login dialog and verify whether the user is able to login as LDAP user and run a report.

Modify InfoView to Select Different Authentication Types

After integrating CABI with an external directory server, modify the InfoView application to select the different authentication types. The default setting for InfoView allows only Enterprise authentication.

1. Log in to first Web Tier.

2. Open Windows Explorer and open the WEB-INF folder from C:\Program Files (x86)\CA\SC\CommonReporting3\Tomcat55\webapps\InfoView App\.

(58)

Install and Configure Apache Load Balancer for CABI Web Application Tiers

3. Make a copy of web.xml file.

4. Change the value of the authentication.visible parameter from false to true.

5. Open the Central Configuration Manager application, and restart Apache Tomcat service.

6. Repeat Steps 1 to 5 on second Web Tier. 7. Launch the InfoView using URL

8. Provide the following login details:

Username

Specifies the username of LDAP user

Password

Specifies the password

Authentication

Select the LDAP

Install and Configure Apache Load Balancer for CABI Web

Application Tiers

CABI N-tier environment has two web tiers running Tomcat web server. However, the load balancing feature is not available to distribute the load on two web servers. Hence, we recommend using Apache Load Balancer to distribute the user sessions between the two servers that are based on the priority.

(59)

Pre-requisites

The following list is the prerequisites to install and configure Apache Load Balancer for CABI Web Tiers:

1. Download the Apache HTTP Server with SSL support

(httpd-2.2.22-win32-x86-openssl-0.9.8t.msi) from http://httpd.apache.org. 2. Download the Apache Tomcat Connectors

(tomcat-connectors-1.2.35-windows-i386-httpd-2.2.x.zip) from

http://tomcat.apache.org/download-connectors.cgi and extract the "mod_jk.so" file.

3. If IIS web server is installed on the Apache web server, perform the following steps: a. Stop the World Wide Web Publishing Service, and change the Startup type to

Manual.

b. Open the Services Control Panel, locate and right-click the World Wide Web Publishing Service, and select Properties section.

(60)

c. Change the Startup Type to Manual and click Stop.

d. Click OK.

(61)

Install the Apache HTTP Server

1. Double-click the httpd-2.2.22-win32-x86-openssl-0.9.8t.msi file that was downloaded as part of a prerequisite.

The Apache HTTP Server 2.2 – Installation Wizard Welcome dialog opens. 2. Click Next.

The License Agreement dialog opens. 3. Accept the license agreement and click Next.

The Read This First dialog opens. 4. Read the text and click Next.

The Server Information dialog opens.

5. Provide the appropriate server parameters and click Next. The Setup Type dialog opens.

6. Select the Custom setup type and click Next. The Custom Setup dialog opens.

(62)

7. Keep the default features and click Change to change the destination folder. The Change Current Destination folder dialog opens.

8. Change the installation drive to D: and click OK. The Custom Setup dialog opens.

9. Click Next.

The Ready to Install the Program dialog opens. 10. Click Install.

After the installation is complete, the Installation Wizard Completed dialog opens. 11. Click Finish.

(63)

Perform Post-Installation Steps

Open Internet Explorer and type the http://localhost URL.

On successful installation of the Apache HTTP Server, the following message displays:

Configure Apache HTTP Server

After you complete the installation and post-installation of the Apache HTTP server, configure the Apache HTTP server.

1. Copy the mod_jk.so file that was extracted as prerequisite, to the D:\Program Files (x86)\Apache Software Foundation\Apache2.2\modules folder.

2. Open the httpd.conf file from the D:\Program Files (x86)\Apache Software Foundation\Apache2.2\conf folder.

(64)

4. Create a worker.properties file in the D:\Program Files (x86)\Apache Software Foundation\Apache2.2\conf folder.

5. Add the following lines and save the file.

6. Create a uriworkermap.properties file in the D:\Program Files (x86)\Apache Software Foundation\Apache2.2\conf folder.

(65)

Chapter 3: Configuring Additional Options for CABI 65 8. Restart the Apache2.2 service from the Services control panel.

Configure CABI Web Tier

Installing and configuring the Apache HTTP server is complete after you configure the CABI Web Tier.

2. Open the server.xml file from the C:\Program Files

(x86)\CA\SC\CommonReporting3\Tomcat55\conf folder using text editor. 3. Search and find the following line:

<!-- Define an AJP 1.3 Connector on port 8009 line.

4. Close the comment by adding --> at the end of the line as shown in the following dialog:

5. Delete the following line:

(66)

6. Add the following lines in the same section:

7. Find the followng line:

8. Modify the Engine element to add the jvm route information as shown in the following screen:

9. Save the server.xml file.

10. Restart Apache Tomcat server from the Central Configuration Manager application.

11. Repeat Steps 1 to 10 on the second Web Tier.

Important! However, in Step 8, change the jvmroute to web07.

12. Open the URL in IE and verify whether CMC opens successfully. 13. Open the URL and verify whether InfoView opens successfully.

(67)

Chapter 4: Deploying CABI Reports of CA Products 67

Chapter 4: Deploying CABI Reports of CA

Products

This chapter describes how to deploy CABI reports of CA products that are integrated in the CABI N-tier environment.

CA products that integrate with CABI provide a Business Intelligence Archive Resource (BIAR) file. The BIAR file generally has the following content:

■ _{Product universes} ■ Universe connection

■ _{Report folders and report objects} ■ _{Product-specific report groups} ■ Custom access levels

Each universe connection requires an ODBC or JDBC connection to the product database, which is created or installed before importing the BIAR file.

Deploy the following CA product reports in the CABI N-tier environment: 1. CA Service Catalog Manager r12.7

2. CA Software Compliance Manager r12.0.9 3. CA IT Client Manager r12.5

4. CA Clarity r13

5. CA Service Desk Manager r12.6

6. CA Service Operations Insight (CA SOI) r3.0

Note: To Deploy CA SOI reports ensure that you deploy CA CAF to enable CustomParams

for CA SOI, and install the Reports component to enable CA SOI reporting.

The reports of most of the products listed above can be deployed using biconfig utility. Some products like CA Service Desk Manager, CA SOI, CA ITCM provide a configuration utility to deploy the universe and reports.

(68)

Deploy CA Service Catalog Manager Reports

This section contains the following topics:

Deploy CA Service Catalog Manager Reports (see page 68) Deploy CA Software Compliance Manager Reports (see page 73) Deploy CA IT Client Manager Reports (see page 76)

Deploy CA Clarity Reports (see page 82)

Deploy CA Service Desk Manager Reports (see page 89)

Deploy CA Asset Portfolio Manager Reports (CA Services Provided Reports) (see page 93)

Deploy CA CAF to Enable CustomParams for Custom Prompt Pages (see page 96) Deploy CA Service Operations Insight (CA SOI) Reports (see page 100)

Deploy CA Service Catalog Manager Reports

To deploy the CA Service Catalog Manager R12.7 reports in CABI N-tier environment, perform the following steps:

1. Log in to the first Intelligence Tier server as an administrator.

2. Copy the SLCM_universe.biar file to a folder on the first Intelligence Tier. The Service Catalog BIAR file is available on the Service Catalog server at the a working location:

C:\Program Files (x86)\CA\Service Catalog\reporting\CABI\biar

The BIAR file name for CA Service Catalog is SLCM_universe.biar.

3. Copy the complete BICONFIG folder from the CABI media to the folder where you copied the SLCM_universe.biar file.

4. Open the odbc32.exe file from the following location: C:\Windows\SysWOW64

(69)

Chapter 4: Deploying CABI Reports of CA Products 69 5. Select the System DSN tab and click Add.

The Microsoft SQL Server DSN Configuration window opens.

6. Enter SLCM_DSN as the data source name and SQL Server name (where the Master

Database (MDB) is located), and click Next.

7. Select the options as illustrated in the following screenshot, and click Next:

Note: Enter the login ID as usmuser and the associated password.

8. Click Finish to complete the ODBC setup, and click Test Data Source to verify the connection.

9. Repeat Steps 4 to 8 to create an ODBC connection on the second Intelligence Tier and Processing Tiers.

(70)

10. After you verify that the reports run without fail, open the xml_biar_import.xml file in a text editor. The xml_biar_import.xml file is located at the …\biconfig\samples folder.

11. Make the following changes in the xml_biar_import.xml file: <biar-file name>: The BIAR file to be deployed with the complete path <rdms>: The database type SQL or Oracle

<datasource>: The ODBC DSN Name created in Steps 6-8 <server>: The database sever name

<username>: The user to connect to MDB database.

12. Open the Command Prompt window and change the working directory to biconfig. Run the biconfig command to deploy the BIAR file. Run the following command to display the Online Help.

BIConfig –help

The biconfig utility is also explained in the biconfig-readme.txt file located in the biconfig folder.

The reports and universe are deployed.

Verify the Report Deployment

After you deploy the CA Software Compliance Manager report in the CABI N-tier environment, perform the following procedure to verify the report deployment:

1. Launch the Designer from Start, All Programs, Business Objects XI 3.1, Business Objects Enterprise.

(71)

Chapter 4: Deploying CABI Reports of CA Products 71 3. Select File, Import.

The Import Universe window opens.

4. Click Browse.

The Select a Universe Folder window opens.

(72)

72 N-Tier Implementation and Configuration Guide 6. Click OK.

Verify that the universe is imported successfully.

7. Log in to any Web Tier server.

8. Launch InfoView from Start, All Programs, Business Objects XI 3.1, Business Objects Enterprise.

9. Log in as an administrator and select the Document List tab.

10. Expand Public Folders to view the CA Reports and the newly created CA SLCM folder.

11. Click Admin Reports and double-click any report to run it.

The CA Service Catalog Manager R12.7 reports are deployed successfully.

Note: The SLCM reports work only if the user exists in CABI and SLCM, and is a

member of any out-of-box SLCM groups like Service Catalog Administrators, Service Delivery Administrator.

For more information about the user management for SLCM, see the Integrating CA Products with CA Business Intelligence section to set up the user database.

(73)

Deploy CA Software Compliance Manager Reports

Chapter 4: Deploying CABI Reports of CA Products 73

Deploy CA Software Compliance Manager Reports

To deploy the CA Software Compliance Manger reports in the CABI N-tier environment, perform the following steps:

1. Log in to the first Intelligence Tier server as an administrator. 2. Copy the SLCM_universe.biar file to a folder on first Intelligence Tier.

The BIAR file for CA Software Compliance Manager (SWCM) is available on the installataion media located at the following folder:

\Web Application Folder\AlleghenyInstallFiles\BIEK folder The BIAR file name is Allegheny_r1_Reporting.biar.

3. Open the odbc32.exe file that is located in the C:\Windows\SysWOW64 folder. The ODBC Data Source Administrator window opens.

4. Select the System DSN tab and click Add.

The Microsoft SQL Server DSN Configuration window opens.

5. Enter AllegheneyBiek as the data source name and SQL Server name (where the MDB is located).

6. Click Next.

7. Select the options as illustrated in the following screenshot and enter the login credentials:

8. Click Finish to complete the ODBC setup and click the Test Data Source button to verify the connection.

(74)

9. Repeat Step 3-8 to create ODBC connections on the second Intelligence Tier and Processing Tiers.

10. Open the Command Prompt window, change the working directory to biconfig, and execute the biconfig command to deploy the BIAR file. To display the Online Help, run the following command:

BIConfig –help

The biconfig utility is also explained in the biconfig-readme.txt file present under the biconfig folder.

The reports and universe are deployed.

Verify the Report Deployment

After you deploy the CA Software Compliance Manager report in the CABI N-tier environment, you can verify whether the report deployment is done correctly.

1. Launch Designer from Start, All Programs, Business Objects XI 3.1, Business Objects Enterprise.

2. Log in as an administrator and select File, Import. 3. Click Browse.

(75)

Chapter 4: Deploying CABI Reports of CA Products 75 5. Expand the CA Universes folder, and select the CA Allegheny folder.

Verify that the universe is imported successfully.

6. Launch the CABI InfoView on any Web Tier server. 7. Log in as an administrator and select Document List.

8. Expand Public Folders, CA Reports and the newly created CA Software Compliance Management folder with multiple sub folders.

9. Click any sub folder and double-click any report to run it. Verify that the report runs successfully.