Clarity

 View Only
  • 1.  Clarity SaaS Transition: Post Transition Activities

    Broadcom Employee
    Posted Apr 06, 2020 08:40 AM

    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 six 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. 


    In this post, the focus will be on the activities customers and Broadcom will perform after the production environment is transitioned to the GCP data center.

    Activities Conducted by Broadcom

    • Broadcom will bring the customer's production environment offline.
    • Broadcom will back up customer data and configuration files from their production environment.
    • Broadcom will upgrade the Clarity production instance to the current GA release.
    • Broadcom will transition the Clarity data from Oracle to PostgreSQL.
    • Broadcom will apply the configuration changes converted during the transition of the non-production environment to the upgraded production environment. Examples of these configuration changes include:
        • NSQL lookups
        • NSQL based portlets
        • Processes, with active or on-hold status, with GEL scripts with SQL query
        • Jaspersoft content
          • Studio reports
          • Input queries
    • Broadcom will apply the latest version of the supported add-ins.
    • Broadcom will transfer all data and configuration files to the GCP data center using a secure channel.
    • Broadcom will restore the data to the new production instance in the GCP data center.
    • Broadcom will test the production environment in the GCP data center to ensure it is accessible, the process engine is operational, and out of the box jobs and reports are executing as expected.
    • Broadcom will configure the customer's production environment URL for the new instance in the GCP data center.
    • The Broadcom PoC will notify customers that the production environment is ready for testing along with the following information:
      • Clarity URL
      • Jaspersoft URL
      • SFTP location
      • SSO information (if applicable)
      • OData URL (if applicable)
    • Broadcom will sign-off on the successful transition of the production environment.

    Activities Conducted by Customers

    Once the Broadcom PoC informs customers that the production environment is ready for testing, customers should immediately begin testing activities. Customers will have a final opportunity to test the system and provide a Go/No Go decision to your Broadcom PoC. 

    Issue Resolution Process

    If customers encounter any issues during their production environment testing, they should contact the Broadcom PoC immediately who will manage the triage and issue resolution process.

    Custom Jaspersoft Report Conversion

    As part of the transition to the GCP data center, Broadcom will convert a customer's custom Jaspersoft reports.  In order to prepare, customers need to be aware that Broadcom will take a tiered approach. Broadcom will work with the customer to select a few key reports to be made available during a customer's non-production environment testing period. These reports will also be available when the customer goes live in the GCP data center. The remaining reports will be delivered after customers have gone live in the GCP data center.  

    Please review the following information to ensure you are prepared for the transition:

    • Select a minimal set of key reports to be converted. certain reports may require significant effort to convert.
    • Those reports identified as key reports may not be able to be converted prior to  going live in the GCP data center. However, after the key reports are identified, your PoC will share the list of reports with Broadcom's engineering team to ensure customers and Broadcom agree on the reports that can be delivered when you go live in the GCP data center.
    •  Any modification to the functionality of your source reports will be out of scope.
    • Broadcom will queue the non-key reports for conversion after you go live in the GCP data center. 
    • Broadcom will work towards converting a customer's remaining reports as quickly as possible after going live on the GCP data center. The Broadcom PoC will keep customers informed of the status of report conversion. 
    • Broadcom will deliver the reports after they are converted. Customers are expected to test the reports and provide timely feedback.

    Cloning Additional Non Production Environments 

    If customers have more than one non-production environment, the Broadcom PoC will work with you to identify which non-production environment should be transitioned first to the GCP data center. All other remaining non-production environments will be cloned, from production, and provisioned in the GCP data center after the production environment is transitioned successfully. 

    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 13, 2020



    #ca_clarity_ppm #gcp #clarityppmsaas

     

     



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


  • 2.  RE: Clarity SaaS Transition: Post Transition Activities

     
    Posted Apr 07, 2020 01:46 PM
    Thank you for the continued updates Suman!

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



  • 3.  RE: Clarity SaaS Transition: Post Transition Activities

    Posted Apr 28, 2020 03:31 PM
    Thank You Suman!

    Does Broadcom have any time estimates for each of these tasks. I presume the core product will be migrated over a weekend. Some guidelines on estimated application downtime would be helpful. Jaspersoft Tiered Approach timelines would also be helpful to better plan and prepare our end users.

    I presume customer is responsible for any external integrations and adapters. Is there any change impact to SOAP, Rest API and Jason calls?

    Regards
    Rahul


  • 4.  RE: Clarity SaaS Transition: Post Transition Activities

    Broadcom Employee
    Posted Apr 28, 2020 03:37 PM
    Hi Rahul

    Yes there is a detailed plan and we discuss with each of the customers. If you would like to have further discussion please send out an email to  clarityppm.saas@broadcom.com and we will be happy to discuss. 

    For the adapter provided by HCL we are taking care of that while working with them. On the Rest/SOAP/JASON - the clarity URL remains the same but Jaspersoft URL changes, so dont expect any impact in clarity. 


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