Welcome to the Clarity PPM SaaS Transition Blog series. This blog series will provide you updates around the Clarity PPM SaaS transition to the Google Cloud Platform™ (GCP). In order to keep our customers informed of our SaaS transition, we will be posting blogs, on a regular basis, on various transition-related topics.
Let's start this post by reviewing the current status. As of Jan 2020, Broadcom has started provisioning new customers in the GCP based SaaS platform. We have also made progress towards transitioning current Clarity PPM SaaS customers to GCP.
However, the original Clarity PPM SaaS transition timeline, communicated in October 2019, has been delayed. We intend to begin the Clarity PPM SaaS transitions in March 2020. The initial set of customers targeted to transition to GCP, in March, have been contacted by their single point of contact (PoC) from Broadcom. These customers are now preparing for the transition.
While you wait for your Broadcom PoC to contact you, let's review some key activities that you will perform after they contact you:
The high-level process that we will follow to migrate Clarity PPM SaaS from our current data center to GCP is given below. Our next blog post on 2nd March will provide more information about how to be ready for the SaaS transition.
Now that you understand the transition process, let's review some changes you will encounter after you have migrated to GCP.
2. 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. Remember that WebSQL is for validating queries and viewing a small amount of data. WebSQL cannot be used for data extraction.
3. Portal and SSO: The SaaS Portal (as it's used today) will be replaced with a new SSO solution in the new SaaS infrastructure. Customers who use the Portal for Federated SSO should work with Broadcom to update the deep link integration between customers IdP and Clarity PPM. We intend to retain Portal functionality in the new SSO solution, however, one change will be to the login username to be the user's email address. We will have a detailed blog post and documentation on using Federated SSO for Clarity PPM (GCP) very soon.
4. Clarity PPM Database: As part of the transition, the database that hosts Clarity PPM schemas will change from Oracle™ to PostgreSQL™.
Key Benefits of Transitioning to GCP
Let's end this blog post by reviewing some of the key benefits of migrating to the GCP platform.
3. Automated Updates
Thank you for being a part of the Clarity PPM community. Please write to firstname.lastname@example.org in case you have any specific questions for us. The next blog post covering how to be ready for SaaS transition and will be published on 2nd March 2020.#ca_clarity_ppm #gcp #clarityppmsaas