Clarity

Expand all | Collapse all

Clarity SaaS Transition: Analyzing Your Customization's - Part 2

  • 1.  Clarity SaaS Transition: Analyzing Your Customization's - Part 2

    Broadcom Employee
    Posted 04-20-2020 01:23 PM
      |   view attached

    Welcome to the Clarity SaaS Transition Blog series. This blog series provides customers with updates regarding the Clarity SaaS transition to the Google Cloud Platform™ (GCP).  In the first few blogs, Broadcom provided updates on various aspects of the migration including the overview, pre-transition activities, the actual transition process, and the various authentication methods available in GCP. 


    This post will focus on how to analyze and review customizations within the PPM Customization Discovery Analysis job. The following applies to all customers using Clarity 15.6.1 and lower. 


    Customers using Clarity 15.7, or higher,  review this post to learn how they can use the Customizations Overview report. 


    When the PPM Customization Discovery Analysis job is executed, an excel file is generated that contains custom Clarity database objects such as tables, views, functions, etc... that represents custom content added to the Clarity schema. The file also contains other types of custom Clarity content such as Studio objects and attributes, NSQL queries, GEL scripts, reports, and jobs. 


    Perform the following steps to run the 'PPM Customization Discovery Analysis' job:


    1. Click Home -> under Personal section -> Reports and Jobs.
    2. Click the Jobs tab and then select Available Jobs.
    3. Enter one or more e-mail addresses separated with a comma or semicolon. Each recipient receives a zip file containing the Excel-based output.
    4. Select the Obfuscate Email Address checkbox, if you want to obfuscate email addresses in the Excel file. 
    5. The job is set to execute immediately by default. Click Submit to execute the job. 
    6. Click Jobs -> Log to check the status of the job. 
    7. Extract the zip file and open the excel file to review your Clarity customizations. 
    The PPM Customization Discovery Analysis job may show certain out-of-the-box attributes in the excel. A sample output file is attached to this blog. This sample sheet was generated from the Clarity system with zero customizations. All the objects listed in this sheet will be moved over to the GCP platform. If you see any additional database objects, please work with your Broadcom point of contact to convert them into supported artifacts.

    Customers can use the PPM Customization Discovery Analysis job to:


    • Understand customizations created in your environment. 
    • Focus on the following to help prepare a test plan:
      • NSQL Lookups
      • NSQL Query
      • Processes with GEL scripts
      • Jaspersoft Reports
    • Review database customizations and convert them to supported options.
    • Remove customizations no longer required by the end-users.

      • Customers typically create customizations with a specific objective in mind. 
      • If this objective was a one-time activity, the customizations still exist in the Clarity database but perhaps they are no longer utilized or required. 
      • Customers can use the SaaS transition exercise as an opportunity to clean up the Clarity database.  
      • Any processes with incomplete scripts should be set to Draft status.

    • Update testing plans, to ensure customizations are tested appropriately in the GCP environment. 

    The excel file generated by the PPM Customization Discovery Analysis job provides the following information:

    Note: Remember that the PPM Customization Discovery Analysis job may show certain out-of-the-box attributes in the excel. Use the sample output file attached to this blog to identify the out-of-the-box attributes.


    Item

    Description

    Broadcom's Recommendation

    Attribute

    The file includes a list of custom attributes, for a given Object(created in Studio)

    No customer action is required. All custom attributes will be transitioned to the GCP data center. 

    Custom Script

    The file includes a list of custom GEL scripts available in processes

    Broadcom will only migrate GEL scripts whose status is "active" or "on-hold". Broadcom will not migrate scripts whose status is "draft". 


    Customers should review these GEL scripts & remove any scripts no longer used in the production environment. 

    Object

    The file includes a list of custom Studio objects created.

    No action is required. All custom objects will be migrated to the GCP data center. 

    Query

    The file includes a list of custom NSQL queries 

    All queries will be migrated to the GCP data center. 


    Customers should review these queries and remove any no longer used in the production environment. 

    Report

    The file includes a list of custom report definitions 

    All reports will be migrated to the GCP data center. 


    Customers should select a minimal set of key reports to convert. Certain reports may require significant effort to convert. 


    To learn more about customizing reports, please review this blog. Customers should remove all unused reports from the production environment. 

    Job

    The file includes a list of custom job definitions 

    All jobs will be migrated to the GCP data center. 

    Function

    The file includes a list of database functions created in the Clarity schema.

    Broadcom will not migrate custom functions to the GCP data center. Customers should review and convert the functionality to a supported option.


    Note: The job will list CMN_TRUNC_PM_DATE_FCT function as custom.  However, this is an out-of-the-box function and will be available in PostgreSQL.

    Index

    The file includes a list of indexes created in the Clarity schema.

    Broadcom will not migrate custom indexes to the GCP data center.

    Indexes are rebuilt in PostgreSQL based on the application performance and no action should be required by customers.


    NOTE: The report will list a few indexes as custom. You can review the excel attached to the blog for a detailed list. These indexes will be available in the GCP data center.

    Package

    The file includes a list of database packages created in the Clarity schema.

    Broadcom will not migrate custom packages to the GCP data center. Customers should review and convert the functionality to a supported option.

    Package Body

    The file includes a list of database package body definitions created in the Clarity schema.

    Broadcom will not migrate custom package bodies to the GCP data center. Customers should review and convert the functionality to a supported option.

    Stored Procedure

    The file includes a list of database stored procedures created in the Clarity schema.

    Broadcom will not migrate custom stored procedures to the GCP data center. Customers should review and convert the functionality to a supported option.


    NOTE: The job will list PRJ_BLB_INCIDENT_RESET_ALL_SP stored procedure as custom. However, this is a stored procedure and will be available in PostgreSQL.

    Table

    The file includes a list of tables created in the Clarity schema.

    Broadcom will migrate all tables to the GCP data center.

    NOTE: The report will list a few tables as custom. You can review the excel attached to the blog for a detailed list. These tables will be available in the GCP data center.

    Trigger

    The file includes a list of database triggers created in the Clarity schema.

    Broadcom will not migrate custom triggers to the GCP data center. Customers should review and convert the functionality to a supported option.

    View

    The file includes a list of views created in the Clarity schema.

    Broadcom will not migrate custom views to the GCP data center. Customers should review and convert the functionality to a supported option.



    Thank you for being a part of the Clarity community. Please write to clarityppm.saas@broadcom.com in case you have any specific questions for us.  The next blog will be published on April 27, 2020.

    #ca_clarity_ppm #gcp #clarityppmsaas



    ------------------------------
    Thanks & Regards
    Suman Pramanik
    Sr. Principal Support Engineer | Customer Success & Support, Enterprise Software Division
    Broadcom
    ------------------------------

    Attachment(s)

    xlsx
    DiscoveryAnalysis.xlsx   249 KB 1 version


  • 2.  RE: Clarity SaaS Transition: Analyzing Your Customization's - Part 2

    Former Employee
    Posted 04-20-2020 01:35 PM
    Thank you for the update Suman!

    ------------------------------
    Chris Hackett
    Community Manager, Broadcom Enterprise Software Division
    Broadcom Inc.
    ------------------------------