Clarity PPM SaaS Transition Program Guide...We are transitioning Clarity PPM SaaS customer...

Broadcom Proprietary and Confidential. © 2020 Broadcom. All rights reserved.

1 of 16

Clarity PPM SaaS Transition

Program Guide

Last Updated Date: March 5th 2020

Clarity PPM SaaS Transition Program Guide

Broadcom Proprietary and Confidential. © 2020 Broadcom. All rights reserved. 2 of 16

Contents

Table of Contents

Contents 2

Program Overview 3

Glossary 3

Service changes and considerations 4

URL Changes 4

VPN 4

Portal and SSO 4

Clarity PPM Database in SaaS 5

Transition Overview 5

Selected Non-Production Upgrade & Transition 6

Pre-Transition Activities 6

Broadcom Activities 6

Customer Activities 6

Transition Activities 8



Issue Resolution Process 11

Production Upgrade & Transition 11

Production Upgrade Preparation Meeting 11

Transition Activities 12



Production Issue Resolution Process 13

Custom Jaspersoft Report Conversion 13

Other Non-Production Environment Cloning 13

Reference Information 13

Responsibility Matrix 13

Important Support Links 15



Program Overview

Broadcom’s Software as a Service, herein referred to as Broadcom SaaS, is transitioning Clarity

PPM SaaS customers from the current data centers to the Google Cloud PlatformTM (GCP). As

a world class SaaS provider, Broadcom is undertaking this effort to continue to improve the

service that we are providing by leveraging modern SaaS capabilities offered by GCP.

This document provides information that will assist customers in planning for the GCP transition

activities.

This document is current as of the publication date indicated on the title page. Broadcom will

update this document as we progress through the data center transition project and other

relevant information is finalized. The descriptions and content listed here were accurate at the

date of publication, but are subject to change without notice. This document will in no way

modify or be considered to supplement any warranties, service level descriptions or other

provisions contained in your agreement with Broadcom relating to Clarity PPM SaaS. An

updated version of this document will be provided to customers by their point of contact when a

customer’s transition activity begins.

Glossary

The following are frequently used acronyms in this document:

DR Disaster Recovery

SA Service Availability

SFTP Secure File Transfer Program

URL Uniform Resource Locator (i.e. a http web address)

GCP Google Cloud Platform

PostgreSQL PostgreSQL (pronounced "post-gress-Q-L") is an open source relational

database management system (DBMS)

PoC Point of contact



Service changes and considerations

As part of the SaaS transition the following are service changes:

URL Changes

● Your organization will be able to access Clarity PPM using the same URL as they do

prior to the transition.

● URLs for the the following functionality will change:

○ Jaspersoft

○ OData

○ SFTP

○ SSO Deeplink

● New URLs will be provided to you as your respective environments are transitioned to

the new SaaS platform.

VPN

Certain customers were provided time bound VPN access for direct database

connection, on an exception basis, to the current SaaS platform. This functionality will be

deprecated in the new platform.

As an alternative, after the transition to the GCP data center, we recommend customers explore the use of the OData REST API to connect to the data warehouse database for necessary reporting information. In addition, the OData service will provide a WebSQL functionality that allows admins to write/test queries against the DWH schema. WebSQL is for validating queries and viewing small data only. WebSQL cannot be used for data extraction.

Portal and SSO

SaaS Portal (as it's used today) will be replaced with Okta in the new SaaS

infrastructure. Customers using Portal for Federated SSO should plan to work with

Broadcom to update the deep link integration between customers IdP and Clarity PPM.

Broadcom will be leveraging Okta in conjunction with standard SAML authentication

integrated within Clarity PPM.



We will work with your team to setup a deep link with your IdP and our new SSO

solution. More details will be provided closer to the transition activity.

As part of the Portal replacement, the ODUM tool will also be deprecated. User

management will be done in Clarity PPM. A new sync job will be built into Clarity PPM

that will synchronize information (e.g., creating a new user or deactivating an existing

user) between Clarity PPM and Okta.

Clarity PPM Database in SaaS

We are transitioning Clarity PPM SaaS customer environments from our current data

center located in third party data center (CoLo) to the Google Cloud PlatformTM (GCP).

This transition is being done to provide more modern SaaS capabilities to our

customers. As part of the transition, the database that hosts Clarity PPM schemas will

change from OracleTM to PostgreSQLTM.

Transition Overview

Transition of the data center from current infrastructure to GCP based infrastructure has been

defined into three categories. These categories are broken as follows:

1. Pre-transition activity

2. Non-Production environment transition activity

3. Production environment transition activity



Selected Non-Production Upgrade & Transition

Pre-Transition Activities

Below is the list of activities that will be performed prior to any of your environment being

transitioned to GCP. These activities can begin anytime but must be completed prior to your

non-production environment transition to GCP:

Broadcom Activities

● Broadcom SaaS will notify all Clarity PPM SaaS customers about the overall

transition program to get the customer to begin planning.

● Subsequent notification is sent prior to the scheduled transition period with additional

information on the transition schedule for all your environment instances.

● A point of contact (PoC) will be assigned to you approximately 1 week prior to your

non-production environment transition to GCP.

○ The PoC will set up a status update cadence with you to review the following:

■ Review the timeline:

■ Review the end to end process

■ Testing approach

■ Review impact to application URL, SFTP access, SSO, and HDP

○ The PoC will work with you to determine which non-production environment

should be transitioned to GCP first.

○ The PoC will work with you to confirm you have gone through the product

documentation.

○ The PoC will work with you to confirm you have started building your

functional and technical testing checklist.

○ We will access your upgraded non-production environment for the purposes

of functional testing prior to the initial handoff.

○ The PoC will discuss your testing status during the scheduled touch points.

Customer Activities

● Your organization will need to plan for testing resources during the transition of your

non-production environment.

● Please be prepared to provide information to your PoC, which includes but not

limited to:

○ Which non-production environment to be transitioned to GCP first?



○ SSO IDP (Identity Manager Application Name) and setup information (ex.

URL, etc.).

● Provide acknowledgement for the following:

○ If you complete your non-production environment testing sooner, we can

coordinate to move the production transition date forward.

○ You understand you have a three (3) weeks allotted for testing of the selected

non-production environment upon handoff.

○ You should be prepared to execute your testing strategy and scripts

immediately upon the handoff of the migrated non-production environment.

○ Reviewed the SaaS transition FAQ document.

○ We will access your upgraded non-production environment for the purposes

of functional testing prior to the initial handoff to you.

○ Freeze any new development on your non-production environment and

promote any existing development in flight to production.

■ In the event if the development work cannot be migrated to

production, then we recommend making off-line backup copies of

those. These development changes will need to be manually applied

by you in the transitioned environment.

○ We will begin the non-production transition based on a copy of your

production environment.

● Prepare testing checklist

○ Generate a checklist of the following:

■ Functional area list

● List of functionality leveraged in Clarity PPM. This list should

be similar to the post upgrade testing that is performed today.

■ Technical list

● NSQL lookups

● NSQL based portlets

● GEL Scripts with sql

● Jaspersoft content

○ Studio reports

○ Input queries

■ Additional component checklist (this list will be different for each

customer)

● Integration between third party application and Clarity PPM

● SFTP usage

● OData usage

● SSO Implementation

○ If applicable, provide your SSO IDP (Identity Manager

Application) name and setup information (ex. URL,

etc.)

○ Prepare your internal team who will be involved during the testing of your

non-production environment in GCP.



■ The list of resources involved will depend on the functional and

technical area to be tested.

● All development activities including creating or enhancing custom components such

as reports, GEL scripts and any other custom code must be completed at least two

weeks prior to the scheduled beginning of the transition process .

○ Includes testing any new development and migrating them to production.

● Work with your PoC if you need to update your internal environments, as applicable,

with the following new information that will be furnished prior to the scheduled

transition:

○ If there exists IP address filtering within your organization’s firewall, you will

need to update the firewall settings to allow inbound traffic from the external

facing IP addresses of the service in GCP.

● Work with your PoC to ensure that you have the ability to reach the GCP datacenter

from your business network and perform the following tests:

○ A link will be shared that represents your geographical location, please

access that link with the browsers supported by your organization.

● Work with your integration team to initiate an HTTPS call to the URL that will be

shared for your region to ensure that inbound integrations to the service are also

reachable.

○ If these tests are successful, then no changes are required to your networks

firewall settings.

○ If any of these tests are unsuccessful, then IP address filtering is likely in use,

please engage the network administrator for your organization to update the

firewall rules to white list the range for your region.

Transition Activities

The following are the activities to be performed by Broadcom and your organization during the

transition:

Broadcom Activities

● Your data and configuration files from your production environment will be backed up and used to perform transition activities without impact to any of your environments.

● Backup copy of Clarity PPM instance will be upgraded to the GA version

● Clarity PPM data, from the backup copy, will be transitioned from Oracle to PostgreSQL, which includes

o Clarity PPM data

o Clarity PPM’s configurations such as

▪ NSQL lookups

▪ NSQL based portlets

▪ GEL Scripts with sql



▪ Jaspersoft content

● Studio reports

● Input queries

NOTE: Customers on Clarity 15.x or higher can use an out of the box job that finds custom built studio components and generates a 20 tab Excel output. Details of the “PPM Customization Discovery Analysis Job” can be found in our product documentation located at https://techdocs.broadcom.com.

● Apply the latest version of the supported add-ins.

● All data and configuration files are transferred to GCP using a secure channel.

● The transitioned data will be restored to the new instance.

● After the transition of an environment, Broadcom SaaS Operations will perform environmental testing, such as ensuring the environment is accessible, process engine is operational, and out of the box jobs and reports are executing as expected.

● The current URL from your selected non-production environment will be pointed to the new GCP instance.

● Your PoC will notify you that the non-production environment is ready for your testing along with the following information:

o Clarity PPM URL

o Jaspersoft URL

o SFTP location

o SSO information (if applicable)

o OData URL (if application)

● Your PoC will work with you to triage and report issues and submit them for resolution.

● The selected non-production instance in the previous datacenter is deleted 30 days after successful transition of the environment.

Customer Activities

Once the PoC informs you that the selected non-production environment is ready for testing, you should immediately begin testing activities. Initial testing within your non-production environment should focus upon determining if there are any application errors or general database integrity issues by, but not limited to, performing typical role based activities such as creating projects, performing typical project activities, submitting timesheets, creating resources, executing processes and reports, etc.

Important! It’s imperative that comprehensive integrity testing is performed as

issues that are not uncovered in this stage will result in a delay of your “Go Live”

date.

● Although the primary Clarity SaaS URL will not be changing, some shared service

URLs will be changing and we will provide updated information (e.g., URL, etc.)

when your non-production environment will be made available to you for testing:

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/clarity-project-and-portfolio-management-ppm-on-premise/15-7-1/reference/clarity-ppm-jobs-reference.html#concept.dita_257921c2670f11e6abaaedee906f06e94d30afd2_PPMCustomizationDiscoveryAnalysisJob

https://techdocs.broadcom.com/



o Jaspersoft Advanced Reporting

o SFTP Host name and passwords

o OData URL

o SSO information

● All credentials will remain the same as the previous environment with the exception

of SFTP credentials.

● If you are leveraging key exchange for SFTP authentication, existing keys will be

migrated by Broadcom to the new SFTP service.

● The following client tools will need to be updated with the new information provided:

o Jaspersoft Studio Client connection information

o BI tools leveraging the OData service

o SFTP Clients and integrations

● You are responsible for functional and data testing which includes but is not limited to the following (it is expected that you will complete this testing within the allotted time):

o Your testing should include the following, but not be limited to:

▪ Create a new application, asset, product, idea, project, program,

portfolio, timesheet, portfolio and save. Update and save an instance

of these objects as well.

▪ Test any other modules that you are using.

▪ Test out of the box PMO & CSP Accelerator add-in content when

converting from SQL to Oracle as SQL related code will need to be

adjusted by your organization or CA Services as a part of the

conversion/upgrade.

▪ Within Studio, please also open an object and manipulate an attribute

or create a new attribute, then save. Test all objects by opening and

saving within that respective object.

o Test any customizations such as:

▪ Reports

▪ Lookups

▪ Portlets

▪ GEL scripts

o Integrations using the new URL.

o If you use SFTP for any integrations, you should test the new solution.

o HCL Global Delivery (GD) components

● If you have SSO authentication enabled in your environment, then you will need to work with your PoC to enable a deep link between your identity management (IdP) solution and Clarity PPM in the new infrastructure.

● Once your testing has completed, please provide your PoC an approval and acceptance of the successful transition of the non-production environment

NOTE:

Initial testing within your non-production environment should focus upon

determining if there are any application errors or general database integrity

issues by, but not limited to, performing typical role based activities such as



creating projects, performing typical project activities, submitting timesheets,

creating resources, executing processes and reports, etc.

Important! It’s imperative that comprehensive integrity testing is performed as

issues that are not uncovered in this stage will result in a delay of your “Go Live”

date. Your testing should include the following:

● Create a new application, asset, product, idea, project, program, portfolio,

timesheet, portfolio and save. Update and save an instance of these

objects as well.

● Test any other modules that you are using.

● Test out of the box PMO & CSP Accelerator add-in content when

converting from SQL to Oracle as SQL related code will need to be

adjusted by your organization or CA Services as a part of the

conversion/upgrade.

● Within Studio, please also open an object and manipulate an attribute or

create a new attribute, then save. Test all objects by opening and saving

within that respective object.

Issue Resolution Process

Should you encounter any issues during your testing, please track each item on the issue

tracker spreadsheet template provided by your assigned PoC. The issues will be triaged and

remediation results updated in the spreadsheet.

Production Upgrade & Transition

Production Upgrade Preparation Meeting

After successful transition of your non-production environment, the PoC will discuss your

production transition plans with you. Specific items to be discussed are as follows:

● Confirmation of the development freeze (no new development and configuration

changes promoted to production from the start of the transition of your non-

production environment)

● Unlike non-production, transitioning your production environment will have

extended downtime. Your PoC will provide more specific information prior to your

production environment transition.

● Discuss lessons learned during the non-production transition

● Review/update the go live checklist, provided at the end of this document



Transition Activities

Broadcom Activities

● Production environment is brought offline

● Your data and configuration files from your production environment will be backed up.

● Clarity PPM instance will be upgraded to the GA version

● Clarity PPM data will be transitioned from Oracle to PostgreSQL

● Your configuration changes that were converted during the non-production environment transition will be applied in the production environment, such as:

▪ NSQL lookups

▪ NSQL based portlets

▪ GEL Scripts with sql

▪ Jaspersoft content

● Studio reports

● Input queries

● Apply the latest version of the supported add-ins

● All data and configuration files are transferred to GCP using a secure channel

● The transitioned data will be restored to the new instance

● After the transition of an environment, Broadcom will perform environmental testing, such as ensuring the environment is accessible, process engine is operational, and out of the box jobs and reports are executing as expected

● Your production environment URL will be pointed to the new GCP instance

● Your PoC will notify you that the production environment is ready for your testing along with the following information:

o Clarity PPM URL

o Jaspersoft URL

o SFTP location

o SSO information (if applicable)

o OData URL (if application)

● Sign-off on the successful transition of the production environment.

Customer Activities

After your current production dataset has been upgraded/converted and moved into

PPM SaaS, you’ll have a final opportunity to perform testing of the system and provide

a Go/No Go decision to your PoC.



Production Issue Resolution Process

Any issues encountered by customers during the production go-live, contact your

assigned PoC for immediate issue triage and resolution.

Custom Jaspersoft Report Conversion

As part of the transition to GCP we will convert your custom Jaspersoft reports. In order to

prepare, please be aware that we will take a tiered approach in that a select few key reports

identified by you can be made available during your non-production testing period which would

also be available as part of your Go Live with the remaining reports delivered post Go Live.

Please review the following specific parameters of the report conversion aspect of your

transition to prepare:

● Key reports selected should be kept to a minimum as certain reports may require

significant effort to convert

● All key reports identified may not be able to be converted in time for your Go Live,

however, after the key reports are identified, your PoC will share the list of reports

identified with our Engineering Team to ensure there is a discussion and agreement on

which ones can be delivered in time for your Go Live

● There will be no modifications to the scope of your source reports

● For any remaining reports not identified to be key for your Go Live will be queued for

conversion

● We will work towards delivering your remaining converted reports as quickly as possible

post Go Live and your PoC will keep you informed on status

● We will deliver reports as they are converted, please test and provide timely feedback

Other Non-Production Environment Cloning

If you have more than one non-production environment, the PoC will work with you to

identify which non-production environment should be transitioned first to the new

platform.

All other remaining non-production environments will be cloned, from production, in the

new SaaS platform, after the successful transition of the production environment.

Reference Information

Responsibility Matrix



Task Customer Broadcom

Project Planning

Migration Dates Primary

Program Guide Content Acknowledgement Primary

Project Kick Off Meeting Assist Primary

Test Plans / Planning Primary

Database Upgrade/Conversion (Non Production)

Technical Database Upgrade/Transition/Refactorization Primary

Testing Primary

Issue Triage / Resolution Assist Primary

Environment Validation Sign Off (Non Prod) Primary

Go Live Planning Meeting Assist Primary

Database Upgrade/Conversion (Production Go Live)



Technical Database Upgrade/Transition/Refactorization Primary

Testing Primary

Issue Triage / Resolution Assist Primary

Environment Validation Sign Off (Prod) Primary

Federated SSO (if applicable)

Setup Deep Link w/ your IdP and Okta Assist Primary

Configure / Establish SAML Exchange with Clarity Assist Primary

Transition Existing Users to Okta Primary

Maintain Users Primary

Important Support Links

Review the following documents, available from the Clarity PPM SaaS TechDocs site, to

prepare for this upgrade:

● Release Notes: Describes new enhancements, changes to third-party software support,

and other information specific to this release. These Release Notes include cumulative

information for the Clarity PPM SaaS v15.7.1 release.

● Change Impact and Upgrade Guide: Provides technical information about changes in

CA PPM for this release and highlights user actions to take. Important! Review this

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/clarity-project-and-portfolio-management-ppm-on-premise/15-7-1.html



entire guide before upgrading to Clarity PPM SaaS v15.7.1. This guide provides insight

on planning the upgrade, training and roll-out efforts.

Clarity PPM SaaS Transition Program Guide...We are transitioning Clarity PPM SaaS customer...

Documents

Transcript of Clarity PPM SaaS Transition Program Guide...We are transitioning Clarity PPM SaaS customer...