Agile Product Lifecycle Management - Oracle · Agile Product Lifecycle Management Portfolio...

of 36/36
Agile Product Lifecycle Management Portfolio Analytics Installation Guide v2.1.2 January 2008 Part No. E11863-01
  • date post

    25-Jun-2020
  • Category

    Documents

  • view

    5
  • download

    0

Embed Size (px)

Transcript of Agile Product Lifecycle Management - Oracle · Agile Product Lifecycle Management Portfolio...

  • Agile Product Lifecycle Management

    Portfolio Analytics Installation Guide v2.1.2

    January 2008 Part No. E11863-01

  • Portfolio Analytics Installation Guide

    Copyright and Trademarks Copyright © 1995, 2008, Oracle. All rights reserved.

    The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

    The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

    If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

    U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

    The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

    Oracle and Agile are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

    The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

    ii Agile Product Lifecycle Management

  • iii

    CONTENTS Copyright and Trademarks................................................................................................................... ii

    Introduction...................................................................................................................... 1 What is Portfolio Analytics?..................................................................................................................1 Who Should Use Portfolio Analytics?...................................................................................................2 Agile PLM Datamart .............................................................................................................................2 Portfolio Analytics Architecture.............................................................................................................3 Installation Requirements.....................................................................................................................3 Language Support................................................................................................................................4

    Installing Portfolio Analytics ............................................................................................ 5 Installation Sequence ...........................................................................................................................5 Installing Embarcadero DT/Studio Components ..................................................................................5

    DT/Engine Repository ........................................................................................................................................................6 Installing Agile OLAP............................................................................................................................6 Installing Oracle Client on the Agile OLAP Computer..........................................................................7 Installing the Portfolio Analytics Application.........................................................................................7

    Required Software for Portfolio Analytics ETL Components ..............................................................................................8 Required Software for Portfolio Analytics Cubes and Reports...........................................................................................8 Starting the Portfolio Analytics Installer ..............................................................................................................................9

    Portfolio Analytics Folders....................................................................................................................9 ETL Folders........................................................................................................................................................................9 Cubes and Reports Folders ...............................................................................................................................................9

    Administering Portfolio Analytics ................................................................................... 11 Overview of Portfolio Analytics Administration...................................................................................11 Assigning Roles and Privileges to Portfolio Analytics Users..............................................................12 Migrating Agile PLM Users to Cognos to Enable Single Sign-on ......................................................12

    LDAP Configuration File ...................................................................................................................................................13 Configuring Agile PLM Fields .............................................................................................................13

    Activity Fields Configured Automatically for Portfolio Analytics........................................................................................14 Configuring Custom Agile PPM Fields .............................................................................................................................14 Handling MultiList Fields...................................................................................................................................................14

    Portfolio Analytics Configuration Files................................................................................................15

  • Portfolio Analytics Installation Guide

    Using DT/Studio to Run Portfolio Analytics ETL Scripts ....................................................................15 Starting a Portfolio Analytics Task in DT/Studio ...............................................................................................................15 Recommended Order of Tasks ........................................................................................................................................16 Stopping a DT/Studio Task ..............................................................................................................................................16 Modifying a Task’s Properties ..........................................................................................................................................17 Checking the Task Log.....................................................................................................................................................17 Scheduling DT/Studio Tasks ............................................................................................................................................18

    Building Portfolio Analytics Cubes......................................................................................................18 Possible Errors in Building Cubes ....................................................................................................................................18 Tips for Building Cubes ....................................................................................................................................................19

    Portfolio Analytics ...............................................................................................................................19 Checking the Dimensions of Cubes .................................................................................................................................19

    Creating Additional Cubes and Reports.............................................................................................19 Scheduling the Building of Cubes ......................................................................................................20 Customizing Cubes ............................................................................................................................20

    Adding Flex Fields to the Datamart ..................................................................................................................................20 Adding new Cubes and Reports to Portfolio Analytics .....................................................................................................20

    Installer Panels ............................................................................................................... 23 Agile PLM Datamart Panels ...............................................................................................................23 Portfolio Analytics Panels...................................................................................................................24

    Installing Datamart......................................................................................................... 29 Upgrading an Existing Agile PLM Datamart.......................................................................................29

    Overview of Agile PLM Datamart Upgrade.......................................................................................................................29 Upgrading the Agile PLM Datamart from Portfolio Analytics 9.0 SP3 to 9.2 ....................................................................29

    iv Agile Product Lifecycle Management

  • v

    Preface The Oracle|Agile documentation set includes Adobe® Acrobat™ PDF files. The Oracle Technology Network (OTN) Web site (http://www.oracle.com/technology/documentation/agile.html) contains the latest versions of the Oracle|Agile PLM PDF files. You can view or download these manuals from the Web site, or you can ask your Agile administrator if there is an Oracle|Agile Documentation folder available on your network from which you can access the Oracle|Agile documentation (PDF) files.

    Note To read the PDF files, you must use the free Adobe Acrobat Reader™ version 7.0 or later. This program can be downloaded from the Adobe Web site (http://www.adobe.com).

    The Oracle Technology Network (OTN) Web site (http://www.oracle.com/technology/documentation/agile.html) can be accessed through Help > Manuals in both the Agile Web Client and the Agile Java Client. If you need additional assistance or information, please contact support (http://www.oracle.com/agile/support.html) (http://www.oracle.com/agile/support.html) for assistance.

    Note Before calling Agile Support about a problem with an Oracle|Agile PLM manual, please have ready the full part number, which is located on the title page.

    TTY Access to Oracle Support Services

    Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.

    Documentation Accessibility

    Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/ http://www.oracle.com/accessibility/.

    Readme

    Any last-minute information about Oracle|Agile PLM can be found in the Readme file on the Oracle Technology Network (OTN) Web site (http://www.oracle.com/technology/documentation/agile.html).

    Agile Training Aids

    Go to the Oracle University Web page (http://www.oracle.com/education/chooser/selectcountry_new.html) for more information on Agile

    http://www.oracle.com/technology/documentation/agile.htmlhttp://www.adobe.com/http://www.oracle.com/technology/documentation/agile.htmlhttp://www.oracle.com/agile/support.htmlhttp://www.oracle.com/agile/support.htmlhttp://www.oracle.com/accessibility/http://www.oracle.com/accessibility/http://www.oracle.com/technology/documentation/agile.htmlhttp://www.oracle.com/education/chooser/selectcountry_new.html

  • Training offerings.

    Accessibility of Code Examples in Documentation

    Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

    Accessibility of Links to External Web Sites in Documentation

    This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

    vi Agile Product Lifecycle Management

  • Chapter 1

    Introduction

    This chapter includes the following:

    What is Portfolio Analytics? ................................................................................................................................. 1 Who Should Use Portfolio Analytics? .................................................................................................................. 2 Agile PLM Datamart............................................................................................................................................. 2 Portfolio Analytics Architecture ............................................................................................................................ 3 Installation Requirements .................................................................................................................................... 3 Language Support ............................................................................................................................................... 4

    Important Portfolio Analytics is not included on the Agile PLM 9.2 installation CD. Portfolio Analytics is installed from its own CD and requires a separate licence key from Agile PLM 9.2. For more information please contact Agile Solutions Delivery.

    What is Portfolio Analytics? Portfolio Analytics provides a platform and tools that let you conduct multidimensional analysis on Agile Product Portfolio Management (PPM) programs across the enterprise. There are two versions of Portfolio Analytics, Advanced and Basic.

    Portfolio Analytics Advanced includes the following three components: Product Intelligence Platform — a framework that includes the Agile PPM Connector, ETL

    (extraction, transformation, and load) scripts, and the Agile PLM Datamart. Agile OLAP — online analytical processing (OLAP) software that draws information from the

    Agile PLM Datamart to model and build multidimensional data sets, or cubes, that let you quickly perform analysis and generate reports.

    Portfolio Analytics cubes and reports— a collection of cubes and reports that can be launched from the Agile Web Client.

    Portfolio Analytics Basic includes the Product Intelligence Platform. It does not include Agile OLAP or the Portfolio Analytics cubes and reports.

    The Agile PLM database is a comprehensive representation of the transaction data in Agile PLM. The Agile PLM database schema supports transactions such as data retrieval, real-time updates, data presentation, and workflow. The Agile PLM Datamart schema facilitates querying and reporting, which is valuable for analyzing performance trends and estimating future trends, and provides an intermediate store for historical Agile PPM data.

    Querying, reporting, and analysis require storage space and processing resources, and could have a significant impact on application performance if they ran against the transaction database. For this reason, Agile PLM and Agile PLM Datamart schemas have separate users, even though they can exist on the same database instance. The Agile PLM Datamart database schema is optimized for custom reporting, ad hoc queries, and analysis against Agile PPM.

    The Agile PLM Datamart contains all of the relevant data available in the Agile PPM application.

    Agile Product Lifecycle Management Page - 1

  • Portfolio Analytics Installation Guide

    The data model for the Agile PLM Datamart is different from that of the Agile PPM application datamodel in that it is better suited for querying and analysis. It comprises a set of Star Schemas—dnormalized Facts and a set of supporting Dimensions—each providing the basis for a

    e-

    n area of

    hnologies. It gives you direct access to your data and lets you import data from other sources.

    g o-market analysis, cost management, issues resolution, or portfolio

    e the datamart to gather information about key performance indicators

    grate Agile PLM Datamart data with other datamarts or the company’s data warehouse.

    Agile PLM Datamart

    performance trends and estimating future

    s

    for cution.

    tamart includes the following kinds of Agile PPM data:

    s

    The Agile PLM Datamart is based on a modular decision-support architecture with a set of common dimensions, and a set of Star Schemas each supporting a specific sub-area of analysis.

    functional analysis such as Financial Analysis, Time-to-Market Analysis, and so on.

    Portfolio Analytics is an open platform for analysis, based on industry-standard tec

    Who Should Use Portfolio Analytics? Portfolio Analytics is useful to the following groups of users:

    Users with operational business process responsibility, such as executives and project managers. These users can use the datamart for running standard reports and queries.

    Analysts or commodity managers who perform ad hoc queries and analyses in decision-makinsituations, such as time-tscore or trend analysis.

    Managers who can usand historical trends.

    Information technology specialists who can inte

    The Agile PLM datamart is a comprehensive representation of transaction data in the Agile PLM database. The Agile PLM database schema supports transactions such as data retrieval, real-timeupdates, data presentation, workflow, and so on. The Agile PLM Datamart schema facilitates querying and reporting, which is valuable for analyzingtrends, and provides storage for historical Agile data.

    Querying, reporting, and analysis require storage space and processing resources, and could have a significant impact on application performance if they run against the transaction database. For thireason, Agile PLM and Agile PLM Datamart schemas have separate users, even though they can exist on the same database instance. The Agile PLM Datamart database schema is optimizedcustom reporting, ad hoc queries, and analysis against Agile Program Exe

    The Agile PLM Da

    Activities Gates Discussion Users User Groups

    Page - 2 Agile Product Lifecycle Management

  • Chapter 1

    Portfolio Analytics Architecture Portfolio Analytics includes several components, as represented by the following diagram. Equation 1: -1: Portfolio Analytics Architecture

    Agile DBETL

    Agile PLM Datamart Agile OLAP (Cognos)

    Star Schemas OLAP Cube Cube BrowsersReporting

    ETL

    Data Source

    Staging & Dimensional

    Schemas

    At the left of the diagram is the Agile PLM database, the transaction database that contains all Agile Program Execution data and is designed for executing business processes and user interface needs. External data sources are also represented at the left of the diagram. For example, with the help of Agile Solutions Delivery, you may implement an analytics solution that combines data from the Agile PLM database, external data sources, and additional flat files.

    Using ETL (extraction, transformation, and loading) scripts, the data is extracted from the data sources and loaded into relational schemas that comprise the Agile PLM Datamart:

    Staging schema — contains raw data, which can be used for staging purposes before moving to other datamarts

    Dimensional schema — a star schema that enhances the performance of multidimensional queries. The dimensional schema summarizes transactions into multidimensional views for analysis and reporting, unlike the Agile PLM transactional database. User queries on the Agile PLM Datamart are extremely fast because the data consolidation has already been done. The data is placed into a cube structure users can rotate, which is well-suited for financial summaries.

    Once the Agile PLM data has been extracted, transformed, and loaded into the Agile PLM Datamart, Agile OLAP provides the multidimensional analysis tools for manipulating and reporting on the cubes. Users can access the cubes and reports directly from the Agile Web Client.

    Installation Requirements For a list of hardware and software requirements for Portfolio Analytics, see the Agile PLM Capacity Planning and Deployment Guide.

    Page - 3

  • Portfolio Analytics Installation Guide

    Important The Portfolio Analytics extraction code for DT/Studio is currently only supported on Windows.

    Language Support Portfolio Analytics 2.1.2 is an English only product. No other languages are currently supported.

    Page - 4 Agile Product Lifecycle Management

  • Chapter 2

    Installing Portfolio Analytics

    This chapter includes the following:

    Installation Sequence .......................................................................................................................................... 5 Installing Embarcadero DT/Studio Components.................................................................................................. 5 Installing Agile OLAP........................................................................................................................................... 6 Installing Oracle Client on the Agile OLAP Computer ......................................................................................... 7 Installing the Portfolio Analytics Application ........................................................................................................ 7 Portfolio Analytics Folders ................................................................................................................................... 9

    Installation Sequence To install Portfolio Analytics, follow this installation sequence:

    Important You must restart your computer after installing each component of Portfolio Analytics.

    1. Make sure Agile PLM application server is installed and running and is using the latest license key you have received to enable Portfolio Analytics.

    2. Make sure the Agile PLM Datamart database schema is installed and running. For more information, refer Oracle|Agile PLM Datamart Setup Guide.

    3. Install Embarcadero DT/Studio components on a Windows 2000 or 2003 server. This includes DT/Engine and DT/Console. For more information, see Installing Embarcadero DT/Studio Components (on page 5).

    4. Install Portfolio Analytics ETL tools on a Windows 2000 or 2003 server. For more information, see Starting the Portfolio Analytics Installer (on page 9).

    If you purchased the Advanced version of Portfolio Analytics, complete the following steps.

    5. Install Agile OLAP (Cognos) on a separate computer. For more information, see Installing Agile OLAP (on page 6).

    6. Make sure a database client is installed on the computer where you are installing Agile OLAP. For more information, see “Installing Oracle Client on the Agile OLAP Computer (on page 7).

    7. Install Portfolio Analytics cubes, reports, and utilities on the Agile OLAP computer. For more information, see Starting the Portfolio Analytics Installer (on page 9).

    Installing Embarcadero DT/Studio Components Portfolio Analytics includes the following Java-based ETL tools from Embarcadero Technologies:

    DT/Engine — A data integration engine that can move and transform data between heterogeneous databases and files. DT/Engine’s ETL tool extracts the data from the source Agile PLM system, performs transformation needed on the source data, and loads the data into

    Agile Product Lifecycle Management Page - 5

  • Portfolio Analytics Installation Guide

    the Agile PLM Datamart.

    DT/Console — The monitoring component of DT/Studio. DT/Console is an administrative interface that lets you monitor the DT/Engine and remotely manage and schedule ETL tasks.

    Note Portfolio Analytics currently supports DT/Studio on Windows only. The Portfolio Analytics installer automatically deploys the Agile ETL code directly into the repository.

    Install DT/Engine and DT/Console from the separate Embarcadero DT/Studio CD included with Portfolio Analytics. For complete installation instructions, please see the separate Embarcadero installation documentation.

    Agile requires that you install Embarcadero Systems DT/Studio on a Windows 2000 or Windows 2003 computer. DT/Engine can point to a metadata repository (such as an Oracle database) on a Windows or a Solaris computer. You can install DT/Engine and DT/Console in any order. For hardware and software requirements, please see the DT/Studio documentation from Embarcadero Technologies.

    If a previous version of either DT/Engine or DT/Console is installed already, uninstall it before installing version 2.3.

    Note Embarcadero Technologies periodically releases service packs for DT/Studio. Make sure you install the latest DT/Engine or DT/Console service packs before installing Portfolio Analytics ETL components.

    DT/Engine Repository

    DT/Engine stores data in normalized form in a metadata repository. The repository provides security, version control, and rollback capability. It also allows you to generate reports.

    Agile recommends using the same database server you are using for the Agile PLM Datamart for the DT/Engine repository database. Either create a new database instance on the Agile PLM Datamart computer, or add a new user to the Agile PLM Datamart instance called DTUSER (or something similar). When you install DT/Engine, you are prompted to specify the repository database. If you prefer, you can install DT/Engine without specifying a repository. However, you will need to specify and configure the repository later using DT/Console.

    Note Before you install Portfolio Analytics ETL components, you must set the DT/Repository. Otherwise, Portfolio Analytics ETL tasks will not be uploaded to the repository.

    Installing Agile OLAP OLAP stands for Online Analytical Processing, decision support software that provides multidimensional views and hierarchies of your enterprise data. Agile OLAP is the name given to the Cognos Series 7 software that is included with the Advanced version of Portfolio Analytics.

    You should install the following Cognos Series 7 products in the following order:

    Sun ONE Directory Server or other Cognos supported server (located on the Cognos Supplementary Software CD)

    Page - 6 Agile Product Lifecycle Management

  • Chapter 2

    Note The Sun ONE Directory Server must be installed before all other Cognos components.

    Impromptu Administrator PowerPlay Enterprise Server PowerPlay Transformer

    There are other Cognos Series 7 products, but they are not needed for Portfolio Analytics.

    Before installing Cognos components, refer to the document called System Requirements for Cognos Series 7 Version 2 available from Cognos.

    Note After you install Cognos Series 7 products, make sure you install a database client (for Oracle) on the same computer. The database client is needed to connect to the Agile PLM Datamart to build cubes. For installation instructions, see “Installing Oracle Client on the Agile OLAP Computer” below.

    Cognos provides a separate documentation CD for Cognos Series 7 products. For complete installation instructions for Cognos Series 7, see the following Cognos installation guides:

    Cognos Series 7 Solution for Windows Installation Guide Cognos Series 7 Supplementary Software Installation Guide Cognos Series 7 Impromptu® Administrator for Windows Installation Guide Cognos Series 7 PowerPlay® Transformer Edition for Windows Installation Guide

    Note st reinstall the Portfolio If you change the computer where Agile OLAP is installed, you muAnalytics ETL components on the Agile PLM Datamart computer.

    the data. You can install the Oracle 9i Client or Oracle 10g Client from the separate Oracle CDs.

    Note se to connect from

    Installing Oracle Client on the Agile OLAP Computer Agile OLAP (Cognos) requires a database client application to connect to the Agile PLM Datamart. The database connection is needed to build multidimensional cubes from

    The name of the connection alias (also called Net Service Name) you uthe Cognos computer to the Agile PLM Datamart must be plmanalytics.

    For Oracle 9i Client or Oracle 10g Client installation instructions, please see the Oracle documentation.

    ows the same initial process up through the panel where you select the components to install.

    sure

    Installing the Portfolio Analytics Application The Agile PLM installer is a Java program. The installation of all components foll

    Before installing the Portfolio Analytics application, make

    You have installed all required software.

    Page - 7

  • Portfolio Analytics Installation Guide

    ents, see For information about software needed for Portfolio Analytics ETL componRequired Software for Portfolio Analytics ETL Components (on page 8). For information about software needed for Portfolio Analytics cubes and rep orts, see

    alytics Cubes and ReportsRequired Software for Portfolio An (on page 8).

    d lock up the installation. You can turn the virus protection on after the installation is

    Required Software for Portfolio Analytics ETL Components

    PLM to the Agile PLM Datamart

    ing.

    se schema and the database is up and

    You have disabled virus protection.

    If virus protection is enabled, components used in the installer can be falsely identified as being infected ancomplete.

    Portfolio Analytics ETL components include:

    Agile PLM Connector, software that connects Agile ETL (extraction, transformation, and load) scripts

    Before installing Portfolio Analytics ETL components, make sure:

    The Agile PLM 9.2 application server and the Agile PLM 9.2 database are both up and runn You have installed the Agile PLM Datamart databa

    running.

    You have installed DT/Engine and DT/Console.

    Note You can install DT/Engine and DT/Console on any Windows 2000 or Windows 2003 computer.

    You have configured DT/Engine to connect to a database repository located on Datamart computer.

    the Agile PLM

    Note all Portfolio Analytics ETL components on a Windows 2000 or

    You have installed all Windows updates, especially for the DirectX component.

    Agile requires that you inst2003 server. For hardware and software requirements, please see the Agile PLM Capacity Planning Guide.

    Required Software for Portfolio Analytics Cubes and Reports

    Portfolio Analytics cubes and reports must be installed on the sam(Cognos) is installed.

    e computer where Agile OLAP

    ccessfully and the services are running.

    Oracle Client software to connect to the

    Before installing Portfolio Analytics cubes and reports, make sure

    Cognos is installed su The Oracle Client is installed. Cognos requires the

    Agile PLM Datamart.

    Page - 8 Agile Product Lifecycle Management

  • Chapter 2

    Starting the Portfolio Analytics Installer

    To s t

    1. Log using a login with local Administrator permissions.

    Unzip the installation bundle at the root of your drive.

    n th click the S

    3. If you obt folder on the CD and double-

    our computer’s drive C. If

    tart he Portfolio Analytics installer:

    in to the computer

    2. If you obtained the Portfolio Analytics installation bundle from the Agile FTP site:

    1.

    2. I e Portfolio Analytics installation folder, open the Windows subfolder, and double-etup.exe file. ained a Portfolio Analytics CD, go to the Windows sub

    click the Setup.exe file.

    Note The setup program copies files it needs to run to ythere is insufficient disk space available on drive C to complete the installation,

    er location. Click Choose, select a folder installer will start.

    you will be prompted to choose anothon another drive, click OK, and the

    After a few moments, the Welcome screen appears.

    ut any screen in the installer, click Help.

    ETL Folders

    rtfolio Ana alyticsHome> folder has the g subfolder

    4. For information abo

    Portfolio Analytics Folders

    After Po lytics ETL components are installed, the

  • Portfolio Analytics Installation Guide

    Folder Contains

    PA_cubes_and_reports Portfolio Analytics cubes and reports

    UI , used to customize the PowerPlay Web client, which is used to view Portfolio Analytics cubes. Files, such as company logos

    SSO Utilities for migrating Agile PLM users to the Cognos LDAP server to enable single sign-on of Agile and Cognos clients.

    Page - 10 Agile Product Lifecycle Management

  • Chapter 3

    Administering Portfolio Analytics

    This chapter includes the following:

    Overview of Portfolio Analytics Administration .................................................................................................... 11 Assigning Roles and Privileges to Portfolio Analytics Users ............................................................................... 12 Migrating Agile PLM Users to Cognos to Enable Single Sign-on ........................................................................ 12 Configuring Agile PLM Fields .............................................................................................................................. 13 Portfolio Analytics Configuration Files ................................................................................................................. 15 Using DT/Studio to Run Portfolio Analytics ETL Scripts...................................................................................... 15 Building Portfolio Analytics Cubes ....................................................................................................................... 18 Portfolio Analytics ................................................................................................................................................ 19 Creating Additional Cubes and Reports .............................................................................................................. 19 Scheduling the Building of Cubes........................................................................................................................ 20 Customizing Cubes.............................................................................................................................................. 20

    Overview of Portfolio Analytics Administration Portfolio Analytics administration is fairly straightforward, mainly because the Agile PLM Datamart is a separate database that must be maintained and administered separately from the Agile PLM server. For Portfolio Analytics administration, there are several areas of concern:

    Assigning Roles and Privileges — Users must have appropriate privileges to view and use Portfolio Analytics cubes and reports.

    Migrating Agile PLM Users to Cognos — Agile PLM users with access to Portfolio Analytics cubes and reports should be added to the Cognos LDAP directory to enable a single sign-on for Agile PLM and Cognos clients. Agile provides a simple utility to migrate Agile PLM users to the Cognos system.

    Configuring Custom Page Two and Page Three Fields — If you configure Page Two or Page Three fields, they are not used in any of the default cubes and reports. You have to customize the Agile PLM Datamart and the Portfolio Analytics cubes and reports to take advantage of custom fields.

    Scheduling Extraction, Transformation, and Loading (ETL) Tasks — For effective use of Portfolio Analytics, data must be extracted from the Agile PLM server, transformed, and loaded to the Agile PLM Datamart on a regular basis. Portfolio Analytics includes DT/Studio, an ETL engine from Embarcadero Technologies, to manage the ETL process.

    Building Cubes — Each time data is loaded into the datamart, the Portfolio Analytics cubes must be rebuilt.

    Agile Product Lifecycle Management Page - 11

  • Portfolio Analytics Installation Guide

    Assigning Roles and Privileges to Portfolio Analytics Users After you install Portfolio Analytics and add the analytics report folders to Web Client, only users with the Read, Discover, and Run Report privileges for all reports can use them. Users without the necessary report privileges can’t even see the Portfolio Analytics cubes and reports. To expose Portfolio Analytics cubes and reports to other users, assign them the Portfolio Analytics User role.

    For more information about roles and privileges, see the Agile PLM Administrator Guide.

    Migrating Agile PLM Users to Cognos to Enable Single Sign-on After you install Portfolio Analytics Advanced, you need to ensure that all Agile PLM users with the Portfolio Analytics User role are duplicated in the Cognos LDAP directory. The duplication of users in the two systems enables users to log in only once when using the Agile PLM and Cognos clients.

    Note Any Agile PLM users that don't exist in the Cognos LDAP directory can't log into Cognos, and therefore can't launch Portfolio Analytics cubes and reports.

    Agile provides a trusted signon plug-in for Cognos that stores information to identify users but allows Cognos Access Manager to validate them. To use the Agile single sign-on plug-in, you need to register it with your Cognos system using the Access Manager Registration Wizard.

    After you register the Agile single sign-on plug-in with your Cognos system, you can run simple utilities to migrate users from Agile PLM to Cognos. The Agile PLM administrator should run these scripts periodically to update the Cognos system with any new users that have been added to the Agile PLM system.

    To migrate Agile PLM users to Cognos:

    1. Register the Agile single sign-on plug-in with Cognos:

    2. Start the Access Manager Registration Wizard. Click Start > Programs > Cognos Series Seven Version 3 > Tools > Access Manager - Registration Wizard.

    3. If the Welcome screen appears, click Next. The Server Selection dialog box appears. 4. Enter the Cognos server LDAP information:

    Host: The computer where the Cognos LDAP is installed. Make sure you enter the full domain name.

    Port/SSL Port: The Cognos server port. The default is 389. Base Distinguished Name: The default is o=Cognos, c=CARuntime administrator distinguished name: The runtime administrator user. The default is cn=Directory ManagerPassword: Password for the runtime administrator.

    Page - 12 Agile Product Lifecycle Management

  • Chapter 3

    5. To enable SSL, check the Enable SSL box. 6. Click Next. The Security Settings dialog box appears. 7. Select Custom Security, and click the Browse button to select a DLL. 8. Select the following file \bin\cognos_sso.dll and then click Open. 9. Check the Use custom security at all times box. 10. Click Next and Finish. 11. Configure sign-ons for the default Cognos namespace:

    12. Start the Access Manager Administration tool. Click Start > Programs > Cognos Series Seven Version 3 > Tools > Access Manager - Administration.

    13. Select the Directory Servers > > default folder. 14. Choose Edit > Properties. 15. Click the Signons tab. 16. In the Active Signons box, select Both. 17. Click OK. 18. Restart the Web Server on the Cognos computer.

    19. Stop all Cognos services on the Cognos computer, and then restart them.

    20. Open the agile_home\Analytics\SSO folder on the Cognos computer, and run BatchMaintTool.bat. This creates a flat file of Agile users who have the Portfolio Analytics role. Once the file is created, it loads the users into the Cognos LDAP so they can view the cubes and reports.

    If there were any errors in migrating users, they are reported in the output log file (log.txt).

    LDAP Configuration File

    In the agile_home\Analytics\SSO, there is a file named LDAPConfig.xml. It specifies the following information:

    SourceConn — connection information for the Agile PLM database UserLocale — the user’s locale code, such as en_US LogPath — the path where GetUsers.bat generates a log file if any errors are generated CognosFilePath — the path where BatchMaintTool.bat gets the list of Agile PLM users RoleNames the list of Agile PLM roles whose users you want to migrate to Cognos — UserAttributes — the list of attributes that are migrated along with each user

    Generally, you don’t need to modify LDAPConfig.xml. However, you may want to modify the RoleNames or UserAttributes parameters. You can open LDAPConfig.xml in a text editor and change those parameters.

    Configuring Agile PLM Fields This section describes how to configure Agile PLM fields to support Portfolio Analytics cubes and

    Page - 13

  • Portfolio Analytics Installation Guide

    reports. Additional Portfolio Analytics fields needed for cubes and reports are configured automatically during Agile PLM installation, but your company may choose to configure other fields to be used in cubes and reports.

    Activity Fields Configured Automatically for Portfolio Analytics

    When you install Portfolio Analytics ETL components, the setup program configures five custom Page Two fields for the Activity class and its subclasses. The Portfolio Analytics cubes and reports rely on these custom fields.

    The five custom fields are:

    Market_Opportunity NPV Revenue_Forecast Strategic_Fit Technical_Feasibility

    All five fields contain numeric values. When you run scripts to extract Agile PPM data, the data for these fields is extracted and provided in the staging schema for possible custom use.

    Note If you don't provide data for these five numeric fields in your Agile PPM programs, some Portfolio Analytics cubes won’t be built successfully.

    Important Although these fields are automatically enabled when you install Portfolio Analytics, Page Two itself is invisible by default. To enable Page Two, in the Classes window double click Activities Class, select the Page Two tab and then select Yes from the Visible drop-down list. Once you have made your changes, click Save.

    Configuring Custom Agile PPM Fields

    Users with Administrator privileges can configure custom fields on Page Two and Page Three for any Agile PLM subclass. The Portfolio Analytics ETL scripts do not support custom fields out-of-the-box, nor do the Portfolio Analytics cubes and reports. However, you can extend Portfolio Analytics to extract, transform, and load data for any custom Agile PPM fields that your company enables. For help in doing that, contact your Agile Solutions Delivery representative.

    Handling MultiList Fields

    A MultiList field is a list field that is capable of having multiple values selected. Program classes and subclasses can have MultiList flex fields configured on Page Two and Page Three. When you use the ETL scripts to extract and load data for these MultiList flex fields, the MultiList data isn’t treated as separate list values. Instead, the values selected for each MultiList field are treated as one delimited string.

    Note Portfolio Analytics allows up to 255 characters for a delimited MultiList value. If any MultiList values used by Portfolio Analytics exceed 255 characters, the ETL scripts will fail when you try to load data into the Agile PLM Datamart.

    Page - 14 Agile Product Lifecycle Management

  • Chapter 3

    To handle the MultiList data differently, you could create a separate lookup table in the ADatamart to hold values for the MultiList field. You could then use DT/Studio to define a transformation task that parses the individual MultiList values. However, that’s a custom solutionthat may require Java programming and expertise in DT/Designer, Embarcadero Systems’ ETL development tool. For he

    gile PLM

    lp in writing custom data transformations, contact your Agile Solutions Delivery representative.

    folder are configured with va ntered during installation. You do not n these files.

    Portfolio Analytics Configuration Files When you install Portfolio Analytics ETL components, the setup program creates a \Analytics\config subfolder. The files contained in the \config sub

    lues e eed to modify

    Fi le Descr ipt ion

    AAConfig.xml nections to the Agile PLM (source) and Agile PLM Datamart (destination) Provides condatabases.

    DefaultValues.xml IDs used by the Agile PLM Connector to fetch Provides default classes and attribute metadata from the Agile PLM server.

    Log4j.config mation about where log files should be generated during data extraction Provides inforand loading.

    SDKConfig.xml Provides connection information for the Agile PLM application server.

    io, these scripts are also referred to as task definition files. They perform the following

    nc

    the records so they adhere to the structure in the Agile PLM Datamart database

    Starting a Portfolio Analytics Task in DT/Studio

    scripts using DT/Console, a Java application. The XML scripts

    u

    2. clicking Start > Programs > Embarcadero DT/Studio 2.2 > Embarcadero DT/Console

    3. the

    Using DT/Studio to Run Portfolio Analytics ETL Scripts After you install Portfolio Analytics ETL components on the Agile PLM Datamart computer, the \Analytics\ETL folder contains XML scripts used to extract, transform, and load data.In DT/Studfu tions:

    Extract data from the Agile PLM database. Transformschema.

    Load the data into the Agile PLM Datamart database.

    You can run Portfolio Analytics ETLare DT/Studio task definition files.

    To r n a Portfolio Analytics ETL script:

    1. Make sure DT/Engine Manager is started.

    Start DT/Console by2.2 > DT/Console 2.2. If this is the first time you are running DT/Console or if you do not automatically connect to

    Page - 15

  • Portfolio Analytics Installation Guide

    DT/E e, you are prompted to log in. Enter the username and password, andngin click OK.

    Note The default DT/Engine username/password is dtadmin/dtadmin123.

    4. the Agile PLM database and loads it into the

    che

    Note hain called Agile Analytics runs the above tasks in that respective

    After logging in, open the Tasks node. By default, the following tasks appear: PLM_AST_ALL — Task that extracts data from Staging schema of the Agile PLM Datamart. PLM_ADW_COM_ALL — Task that loads common Agile PLM data from the Staging schema into the Dimensional schema of the Agile PLM Datamart. PLM_ADW_PA_ALL — Task that loads data related to Portfolio Analytics from the Staging s ma into the Dimensional schema of the Agile PLM Datamart.

    A task corder.

    rmation on how to set the repository, see the separate DT/Studio

    Note re the Agile PLM application server and

    If no tasks appear in the Tasks node, it could be because the DT/Repository has not been set. For infodocumentation.

    5. Select a task, such as PLM_AST_ALL, and click the Start button.

    Before starting to extract Agile PLM data, make suthe Agile PLM database are both up and running.

    When you run a DT/Studio task such as PLM_AST_ALL, it actually calls several subtasks to move data from the Agile PLM database to the Agile PLM Datamart database. The subtasks extract and load all Agile PLM data, not just the information that changed since the last time you ran the task.

    The time it takes to perform a data load depends on the size of data contained in Agile PPM. If you

    s

    sk that you run are stored in task log files, which are accessible from the

    Recommended Order of Tasks

    chain runs Portfolio Analytics DT/Studio tasks in the following order:

    area, you can perform other transformations before loading the data

    Stopping a DT/Studio Task

    y

    have many programs, it can take several hours.

    Weekly or nightly batch runs are recommended, but multiple batches may be processed arequired. You can use the DT/Console scheduler to schedule a task to run automatically.

    The results from each taLog tab in DT/Console.

    The Agile Analytics task

    1. PLM_AST_ALL

    2. PLM_ADW_COM_ALL

    3. PLM_ADW_PA_ALL

    Of course, it’s really only essential to run the PLM_AST_ALL task first. It loads data into the staging schema of the Agile PLM Datamart. What you do with the staged data is completely up to you. Once the data is in the staginginto the dimensional schema.

    DT/Studio runs a task until it and its subtasks are finished. You can stop a task from running at an

    Page - 16 Agile Product Lifecycle Management

  • Chapter 3

    time. If you want to stop a task from running mid-task, you must first close DT/Console and then stop and restart DT/Engine.

    To stop an Agile task running in DT/Studio:

    perties you set for the task. For more information see, Modifying a Task’s Properties

    Because Agile tasks run in a separate Java program, rather than stopping DT/Console as described above, simply close DT/Console and then stop DT/Engine. When you are ready for your task to run again start DT/Engine and then open DT/Console. Whether or not your task resumes running where it left off or starts again from the beginning depends on the pro

    (on page 17).

    k behaves when you restart it depends on

    isFullLoad False ed successfully.

    The ble lists the properties you can set for ea

    Modifying a Task’s Properties

    You can restart a task that you’ve stopped. How the tassettings contained in the task’s custom.properties file.

    For example, if the isFullLoad property is set to 1 (True), the task runs from beginning to end. If is set to 0 ( ), then the task runs from the last subtask that complet

    following ta ch task.

    Property Descr ipt ion

    debug Sets whether logging is enabled. Default is 1 (true).

    isFullLoad oad of data, or to resume from the last subtask that was Sets whether to perform a full lcompleted. Default is 1 (true).

    initialize . Default is 1 (true). Sets whether to deploy the task to the repository

    dbtype Sets the database type (Oracle or SQL Server)

    CUSTOM_TASK to a table in the administrative .

    The specified custom task is used to move some statistical dataschema of the Agile PLM Datamart. Do not modify this setting

    PRE_TASK Sets global variables for DT/Engine before running the task.

    POST_TASK Resets global variables for DT/Engine after running the task.

    ns fail, you need to identify which of the subtasks failed and then view the task’s file based log.

    from the shortcut menu.

    , which means it failed.

    6. Click Refresh to view the log.

    Checking the Task Log

    After running a DT/Studio task, you can check Log tab to see if the data loaded successfully. If any of the Portfolio Analytics task chai

    To view the file-based log for a DT/Studio task:

    1. Select the Tasks node in the navigation pane in the left. 2. In the right pane, click the End Date/Time column to sort by the end date. 3. Scroll down until you see a task that aborted. The status column will read “Aborted.”

    4. Right-click the aborted task, and choose View File Based Log5. Select a transformer that’s red

    Page - 17

  • Portfolio Analytics Installation Guide

    Scheduling DT/Studio Tasks

    DT/Console provides a simple scheduling tool that lets you run tasks on a recurring basis, such as daily or weekly.

    You should schedule extractions and loading of data during off-hours, such as at night when very few users are accessing the Agile PLM and Agile PLM Datamart databases.

    Note Before using the DT/Console scheduler, confirm that the system date and time on your computer are accurate.

    To schedule DT/Studio tasks:

    1. In DT/Console, select the task and click the Add Schedule button. The Schedule Properties dialog box appears.

    2. Specify the schedule name, start date, start time, and recurrence settings (such as whether the task runs on a daily basis). Click OK.

    3. When prompted that the schedule has been added, click OK.

    Building Portfolio Analytics Cubes After data has been loaded into the Agile PLM Datamart, you are ready to build the cubes that are installed with Portfolio Analytics Advanced on the Agile OLAP (Cognos) computer. A cube is a multidimensional data source. It contains facts (data) organized by different dimensions to provide faster retrieval.

    Each Portfolio Analytics cube has several predefined reports. Portfolio Analytics reports are generated at run time from data contained in the cube.

    Important You cannot build Portfolio Analytics cubes until after you load data successfully into the Agile PLM Datamart. For more information, see Using DT/Studio to Run Portfolio Analytics ETL Scripts (on page 15).

    To build Portfolio Analytics cubes:

    On the Agile OLAP computer, run the following file(s):

    agile_home\Analytics\Cognos\PA_Cubes_and_Reports\buildCubes.bat

    Note It may take several minutes to finish building all the cubes.

    Possible Errors in Building Cubes

    If all the necessary Agile PLM data isn’t loaded in the Agile PLM Datamart, one or more of the cubes won’t be built successfully. To check whether each cube was successfully built, open the log file for each cube in the \cer3\bin folder. The following table lists possible errors you may see in the log files.

    Page - 18 Agile Product Lifecycle Management

  • Chapter 3

    Error (s) Cause

    The temporary file for PowerCube ‘CubeName’ is empty. Check that your source file contains data.

    The Agile PLM Datamart does not have sufficient data for PowerPlay Transformer to build the cube.

    A general exception has occurred during operation ‘attach database’.

    The Oracle 9i Client is not installed, or the plmanalytics connection alias has not been defined.

    TNS:could not resolve service name.

    Transformer can’t read the database [TTM] defined in agile_home\Analytics\Cognos\PA_Cubes_and_Reports\ filename.iqd.

    Tips for Building Cubes

    To successfully build all of the cubes provided with Portfolio Analytics, make sure your Agile PLM data meets the following minimum requirements:

    Portfolio Analytics Discussion and Action Item cube — Make sure at least one activity has a discussion object and an

    action item object.

    Financials cube — Make sure programs have budgeted, estimated, and actual costs for labor, fixed costs, and capital expenses. Also, make sure programs have data for the Revenue_Forecast field.

    Portfolio cube — Make sure programs have data for the NPV, Strategic_Fit, Market_Opportunity, and Technical_Feasibility fields.

    Resource cube — Make sure resources and resource pools that are assigned to programs have data for the Bill Rate, Labor Rate, and Overhead Rate fields. Also, make sure at least one activity has a resource pool assigned to it.

    Time To Market cube — Make sure there are activities.

    Checking the Dimensions of Cubes

    Each cube has several dimensions. These dimensions can be mapped to columns in the Agile PLM Datamart tables. To see what data is needed to build each cube, go to the \Analytics\Cognos\PA_Cubes_and_Reports folder on the Agile OLAP (Cognos) computer. Start PowerPlay Transformer and open the Cognos Transformer model file (*.mdl) for the cube. The Dimension Map window shows the dimensions for the cube.

    Creating Additional Cubes and Reports This manual describes how to build and administer predefined cubes and reports included with Portfolio Analytics Advanced. However, you can also use Cognos Series 7 tools to define additional cubes and reports suited for your enterprise. For information on how to create cubes and reports, see the Cognos documentation. For detailed information about the Agile PLM Datamart schemas,

    Page - 19

  • Portfolio Analytics Installation Guide

    download the Agile PLM Datamart schema documentation from the Agile Documentation Web site.

    Scheduling the Building of Cubes The Portfolio Analytics cubes use the Agile PLM Datamart as its datasource. Therefore, each time you perform a data load on the Agile PLM Datamart, you need to rebuild the Portfolio Analytics cubes. You should schedule buildCubes.bat to run after data is loaded successfully into the Agile PLM Datamart. You can use a third-party scheduling tool to automate the building of cubes each evening or however frequently you run the ETL scripts to load new data.

    Customizing Cubes This section describes how to create customized Portfolio Analytics cubes and reports. For further assistance in creating custom cubes and reports and integrating them with your Agile PLM system, contact Agile Solutions Delivery.

    Important The Staging schema of the Agile PLM Datamart must be populated and Agile PLM fields must be populated and turned on prior to performing any customizations on Portfolio Analytics cubes. To populate the Staging schema, run the PLM_AST_ALL task. For more information, see Starting a Portfolio Analytics Task in DT/Studio (on page 15).

    Adding Flex Fields to the Datamart

    To add Flex Fields to the Datamart:

    1. In Agile Java Client, log in as an Administrator and enable the field you want to use in your new cube. Ensure the field is populated.

    2. Record the field’s Base ID for later use.

    Note You can print the Agile Classes Report to display Base IDs for all fields.

    3. Create a new Datamart table in the ADW Schema.

    4. Create a new DT/Studio ETL task that maps the AST table to your newly created Datamart table.

    5. Include a new task in the Portfolio Analytics task chain.

    6. In DT/Console, run the task chain to populate the new table.

    You can now add new cubes and reports to Portfolio Analytics using the information contained within the new Datamart table.

    Adding new Cubes and Reports to Portfolio Analytics

    To add new Cubes and Reports:

    1. After creating a new cube (*.mdl and *.mdc) and report (*.ppx), place them in \Analytics\Cognos\PA_Cubes_and_Reports with the other Portfolio Analytics cubes and reports.

    2. Using the OLAP Cubes and Reports function, add the new cubes and reports to the PowerPlay

    Page - 20 Agile Product Lifecycle Management

  • Chapter 3

    Enterprise Server Administrator.

    3. From PowerPlay Enterprise Server Administrator, open the added cubes and reports in a browser window. Be sure to copy the URL(s) to a notepad text file for use later in this process.

    4. Backup the existing PLMReports_en_US.csv file on the DT/Studio Server. This file resides in the agile_home\Analytics\bin folder.

    5. Open the PLMReports_en_US.csv file for editing. The file contains three columns: Column 1: “Target Report Folder” - this is the target folder for the new report. The Target

    Report Folder must be nested under the PLM Analytics\Portfolio Analytics report folder and it must be created before running PXReport.bat.

    Column 2: “Report Name” - the name you give the new Agile customer report object. Column 3: “Cognos URL” - the URL for the report. Retrieve the URL you saved to a text

    file earlier in this process and copy it to this location. Be sure to replace the domain name of the server with #machine_name#.

    6. Remove all lines of data in the report and replace them with the new cube and report information. The file should now contain only the new information you want to add.

    7. Run PXReport.bat.

    8. Alter user roles and privileges as necessary to allow proper user access.

    9. Add a line to buildcubes.bat for each new cube. See Building Portfolio Analytics Cubes (on page 18).

    Page - 21

  • Chapter 4

    Installer Panels

    This chapter includes the following:

    Agile PLM Datamart Panels................................................................................................................................. 23 Portfolio Analytics Panels .................................................................................................................................... 24

    Agile PLM Datamart Panels The following installer panels appear when you install the Agile PLM Datamart:

    Panel Step(s) to Per form

    Oracle Database Version Select the version of your Oracle database server. Agile supports the following Oracle versions:

    Oracle 9i R2 Database Server

    Oracle 10g Database Server

    Agile Product Lifecycle Management Page - 23

  • Portfolio Analytics Installation Guide

    Panel Step(s) to Per form

    Source Datamart Database Details

    Enter your source Agile PLM Datamart (Portfolio Analytics 9.0 SP3) database information. The database must be running and you must have a net service configured to connect to it. If you do not know these database values, see the database administrator responsible for your Agile PLM Datamart database server.

    Database Host Name

    Enter the fully qualified domain name of the computer where the Agile PLM Datamart database server is installed.

    Database Port

    Enter the database port. For Oracle, the default database port is 1521.

    Database SID

    Enter apdm (for Agile Portfolio Analytics Datamart).

    Admin Schema Password

    Enter the Admin schema (ADMIN) database user password for the Agile PLM Datamart. The default password is admin.

    Staging Schema Password

    Enter the Staging Schema (STG) database user password for the Agile PLM Datamart. The default password is stg.

    Dimensional Schema Password

    Enter the Dimensional Schema (SIN) database user password for the Agile PLM Datamart. The default password is sin.

    Note If your Agile PLM Datamart database is configured to use different values than the defaults listed above, specify that information instead.

    Portfolio Analytics Panels The following installer panels appear when you install Portfolio Analytics:

    Panel Step(s) to Per form

    Welcome Click Next.

    License Agreement Read the Agile Analytics license agreement, and then select I accept the terms of the license agreement.

    Customer Information Enter your user name, company name, and license key. Your license key determines which Agile Analytics components can be installed.

    Choose Component(s) Select the components to install. The list of components depends on the license key that you entered in the previous panel.

    When you select each component, a description of it appears in the Description box.

    Page - 24 Agile Product Lifecycle Management

  • Chapter 4

    Panel Step(s) to Per form

    New Installation or Upgrade Select whether to install a new Portfolio Analytics application or to upgrade from an existing Portfolio Analytics 9.0 SP3 installation.

    If you upgrade an existing installation, the Agile PLM Datamart must be running.

    Note After installation is finished, there are additional steps you must perform to upgrade the Agile PLM Datamart from version 9.0 SP3 to 9.2. See Upgrading an Existing Agile PLM Datamart (on page 29) from Version 9.0 SP3 to Version 9.2.”

    Installation Location Enter the directory where you want to install Agile Analytics components. This directory is also referred to as the Agile Home.

    Agile PLM Database Details Enter your source Agile PLM database information. The database must be running and you must have a net service configured to connect to it. If you do not know these values, see the database administrator responsible for your Agile PLM database server.

    Agile Database Host Name

    Enter the fully qualified domain name of the computer where the Agile PLM database server is installed.

    Agile Database Port

    Enter the database port. For Oracle, the default database port for is 1521.

    Agile Database Instance

    Enter the Oracle System Identifier that refers to the instance of the Oracle database running on the server. The default SID is agile92.

    Agile Database User

    Enter the database user. The default user is agile.

    Agile Database User Password

    Enter the password for the Agile PLM database user. The default password is tartan.

    Note If your Agile PLM database is configured to use different values than the defaults listed above, specify that information instead.

    Page - 25

  • Portfolio Analytics Installation Guide

    Panel Step(s) to Per form

    PLM Datamart Database Details

    Enter your destination Agile PLM Datamart database information. The database must be running and you must have a net service configured to connect to it. If you do not know these values, see the database administrator responsible for your Agile PLM Datamart database server.

    PLM Datamart Database Host Name

    Enter the fully qualified domain name of the computer where the Agile PLM Datamart database server is installed.

    PLM Datamart Database Port

    Enter the database port. For Oracle, the default database port is 1521.

    PLM Datamart Database SID

    Enter the Oracle System Identifier that refers to the instance of the Oracle database running on the Agile PLM Datamart server. The default SID is aadm (for Agile Analytics Datamart).

    PLM Datamart Database Admin User Password

    Enter the Admin schema (AAD) database user password for the Agile PLM Datamart. The default password is aad.

    PLM Datamart Database Staging Schema Password

    Enter the Staging schema (AST) database user password for the Agile PLM Datamart. The default password is ast.

    PLM Datamart Database Dimensional Schema Password

    Enter the Dimensional schema (AST) database user password for the Agile PLM Datamart. The default password is adw.

    Note If your Agile PLM Datamart database is configured to use different values than the defaults listed above, specify that information instead.

    Agile OLAP (Cognos) Information

    Enter the fully qualified domain name of the computer where Agile OLAP (Cognos) is installed.

    OLAP stands for Online Analytical Processing, decision support software that provides multidimensional views and hierarchies of your enterprise data. Agile OLAP is the name given to the Cognos Series 7 software that is included with the Advanced version of Agile Analytics.

    Agile Analytics Login URL Specify the fully qualified URL to access the Agile PLM server. Format: :/// Example: http://plm.agile.agilesoft.com/Agile

    Start of the Fiscal Year Specify the day and month that begins your company's fiscal year. This setting allows you to run the system in fiscal and calendar years.

    Choose Link or Shortcut Folder

    Depending on your operating system, select where you would like to create links or product icons for Agile Analytics. These shortcuts allow you to quickly launch Agile Analytics programs.

    To create Agile PLM icons for all users, make sure the Create Icons for All Users box is checked.

    Page - 26 Agile Product Lifecycle Management

    http://plm.agile.agilesoft.com/Agile

  • Chapter 4

    Panel Step(s) to Per form

    Pre-Installation Summary Review the information you provided in previous panels to make sure it's correct before you install.

    If the information is correct, click Install. If you need to make any changes, click Previous to go to a previous panel.

    Install Complete You have finished Agile Analytics installation. Click Done to close the installer. Depending on the components you installed, your computer may restart when you click Done.

    Page - 27

  • Chapter 5

    Installing Datamart

    This chapter includes the following:

    Upgrading an Existing Agile PLM Datamart ........................................................................................................ 29 For complete details on installation and administration of Datamarts, refer Agile PLM Datamart Setup Guide.

    Upgrading an Existing Agile PLM Datamart

    Overview of Agile PLM Datamart Upgrade

    The Agile PLM Datamart upgrade from version 9.0 SP3 to 9.2 doesn’t rely on SQL scripts. Instead, you must install a new instance of the Agile PLM Datamart 9.2 and then use Portfolio Analytics 9.2 ETL tools to transfer the data from the old datamart to the new one. This ensures that the existing staging and dimensional data in your datamart are preserved in the new datamart. Equation 2: -1: Upgrading the Agile PLM Datamart from 9.0 SP3 to 9.2

    Agile PLM Datamart 9.0 SP3

    Source Datamart

    Agile PLM Datamart 9.2

    Destination Datamart

    ETL

    Upgrading the Agile PLM Datamart from Portfolio Analytics 9.0 SP3 to 9.2

    To upgrade the Agile PLM Datamart from Portfolio Analytics 9.0 SP3 to 9.2, follow this installation sequence:

    1. Make sure Agile PLM 9.2 application server is installed and running and is using the latest license key you have received to enable Portfolio Analytics.

    2. Make sure the Agile PLM Datamart 9.0 SP3 database is running.

    3. Make sure the Agile PLM Datamart 9.2 database schema is installed and running. See Agile PLM Datamart Setup Guide.

    4. Uninstall the Portfolio Analytics 9.0 SP3 application.

    5. On a Windows 2000 or 2003 server (such as the computer where the Portfolio Analytics 9.0 SP3 application had been installed), install the following Embarcadero DT/Studio components:

    Agile Product Lifecycle Management Page - 29

  • Portfolio Analytics Installation Guide

    DT/Engine and DT/Console. For more information, see Installing Embarcadero DT/Studio Components.

    6. Start the Portfolio Analytics installer. For more information, see Starting the Portfolio Analytics Installer.

    For information about any screen in the installer, click Help.

    Note When the New Installation or Upgrade screen appears, select Upgrade Existing Installation.

    7. Complete the installation. When installation is finished, select “Yes, restart my computer” and then click Done.

    8. After the computer restarts, make sure DT/Engine Manager is started.

    9. Start DT/Console by clicking Start > Programs > Embarcadero DT/Studio 2.2 > Embarcadero DT/Console 2.2 > DT/Console 2.2. If this is the first time you are running DT/Console or if you do not automatically connect to the DT/Engine, you are prompted to log in. Enter the username and password, and click OK.

    Note The default DT/Engine username/password is dtadmin/dtadmin123.

    10. After logging in, open the Tasks node.

    Note If no tasks appear in the Tasks node, it could be because the DT/Repository has not been set. For information on how to set the repository, see the separate DT/Studio documentation.

    11. Select the UPG_90SP3_TO_92 task, and click the Start button. 12. Wait while the Portfolio Analytics 9.0 SP3 data is transferred to the Agile PLM Datamart for

    Portfolio Analytics 9.2.

    UPG_90SP3_TO_9213. After the task is finished, delete and all other tasks whose name starts with “UPG_”.

    Note UPG_90SP3_TO_92 and the other upgrade tasks should be run only once. If you delete the upgrade tasks from DT/Console, you’ll avoid inadvertently running them again.

    Page - 30 Agile Product Lifecycle Management

    Copyright and TrademarksIntroductionWhat is Portfolio Analytics?Who Should Use Portfolio Analytics?Agile PLM DatamartPortfolio Analytics ArchitectureInstallation RequirementsLanguage Support

    Installing Portfolio AnalyticsInstallation SequenceInstalling Embarcadero DT/Studio ComponentsDT/Engine Repository

    Installing Agile OLAPInstalling Oracle Client on the Agile OLAP ComputerInstalling the Portfolio Analytics ApplicationRequired Software for Portfolio Analytics ETL ComponentsRequired Software for Portfolio Analytics Cubes and ReportsStarting the Portfolio Analytics Installer

    Portfolio Analytics FoldersETL FoldersCubes and Reports Folders

    Administering Portfolio AnalyticsOverview of Portfolio Analytics AdministrationAssigning Roles and Privileges to Portfolio Analytics UsersMigrating Agile PLM Users to Cognos to Enable Single Sign-onLDAP Configuration File

    Configuring Agile PLM FieldsActivity Fields Configured Automatically for Portfolio AnalyticsConfiguring Custom Agile PPM FieldsHandling MultiList Fields

    Portfolio Analytics Configuration FilesUsing DT/Studio to Run Portfolio Analytics ETL ScriptsStarting a Portfolio Analytics Task in DT/StudioRecommended Order of TasksStopping a DT/Studio TaskModifying a Task’s PropertiesChecking the Task LogScheduling DT/Studio Tasks

    Building Portfolio Analytics CubesPossible Errors in Building CubesTips for Building Cubes

    Portfolio AnalyticsChecking the Dimensions of Cubes

    Creating Additional Cubes and ReportsScheduling the Building of CubesCustomizing CubesAdding Flex Fields to the DatamartAdding new Cubes and Reports to Portfolio Analytics

    Installer PanelsAgile PLM Datamart PanelsPortfolio Analytics Panels

    Installing DatamartUpgrading an Existing Agile PLM DatamartOverview of Agile PLM Datamart UpgradeUpgrading the Agile PLM Datamart from Portfolio Analytics 9.0 SP3 to 9.2