© 2013 CA

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 2 of 22

This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 3 of 22

Table of Contents

1 Overview .......................................................................................................................................... 4

2 Upgrade Process ............................................................................................................................... 6

2.1 Overall Upgrade Process .......................................................................................................... 6 2.2 New Development ................................................................................................................... 6 2.3 Minimize Risk of Production Upgrade (Test/Development Environment Refreshes) ................. 6 2.4 1st Stage (Conditional Stage) - Preview Environment ................................................................ 6 2.5 UAT/Regression Testing ........................................................................................................... 7 2.6 Go Live Project Site ID / Opening Support Tickets ..................................................................... 7 2.7 2nd Stage (Test Environment) .................................................................................................... 8 2.8 3rd Stage (Production Environment) .......................................................................................... 8 2.9 4th Stage (Development and Remaining Non-Production Environments) ................................... 9 2.10 Schedule .................................................................................................................................. 9

3 Other Service Changes & Considerations ........................................................................................ 11

3.1 Environment Operating System Upgrade................................................................................ 11 3.2 SFTP Mount............................................................................................................................ 11 3.3 SFTP URL ................................................................................................................................ 11 3.4 SFTP Account Credentials ....................................................................................................... 11 3.5 Integrations / GEL Scripting .................................................................................................... 11 3.6 Oracle 11 Compatibility .......................................................................................................... 12 3.7 Portal Users ........................................................................................................................... 12 3.8 Vanity URL ............................................................................................................................. 12 3.9 Federated SSO Target URL ...................................................................................................... 12

4 Reporting Changes ......................................................................................................................... 13

4.1 New Business Object Universes .............................................................................................. 13 4.2 Update Business Objects Report Tables Job ............................................................................ 13 4.3 Create Business Objects Users Job.......................................................................................... 14 4.4 Migrated Components ........................................................................................................... 14 4.5 Server Names and IP Addresses.............................................................................................. 14 4.6 Business Objects Designer ...................................................................................................... 14

5 Clarity Add-In Impact ...................................................................................................................... 15

6 Client Application Compatibility ...................................................................................................... 16

7 CAPA .............................................................................................................................................. 17

8 Additional Questions ...................................................................................................................... 18

9 Appendix A – Monthly Maintenance Windows ............................................................................... 19

10 Appendix B – Upgrade Checklist ..................................................................................................... 20

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 4 of 22

This guide provides information about the service upgrade process for the latest SA (Service Available) Release of CA Clarity PPM On Demand v13. The upgrade to v13 is more involved than some previous upgrades. This guide provides information about the upgrade process, planning considerations, service changes, and considerations for any add-ins currently in use.

Review the following documents, available from the CA Clarity™ PPM Release 13.1.00 - On Demand Bookshelf located on CA Support (support.ca.com), 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 CA Clarity PPM 13.1 release.

Change Impact and Upgrade Guide: Provides technical information about changes in CA Clarity PPM for this release and highlights user actions to take. Important! Review this entire guide before upgrading to CA Clarity PPM v13. This guide provides insight on planning the upgrade, training and roll-out efforts.

Resolved Defects

Business Objects Universes for CA Clarity PPM Reference Guide: Describes how to create Business Objects reports using the Business Objects universes created for CA Clarity PPM

Additionally, review the documentation for each add-in currently in use. Existing add-ins will be upgraded using CA Clarity Studio. Any configured views will be overwritten with applied changes within the add-in. See Section 5 Clarity Add-In Impact for more information.

Please note that we have created a CA Clarity On Demand collaboration site where you may post questions, share ideas and information regarding the v13 upgrade or the CA Clarity On Demand Service, in general. We’ve recently posted Clarity v13 training videos on the support site. The purpose of each video is to give a short, but comprehensive, walk-thru of the new functionality in v13. These videos can be downloaded and used to help train/socialize the new features of v13 with your team. You can find them by searching on “Clarity videos” on the support site or clicking on this link: CA Clarity Project & Portfolio Manager v13.0 Video Index. The video index provides HTML and MP4 links for the videos. You may right click on the MP4 link and “Save Target As…” to save a local copy of the video; however, refer to the Confidentiality slide at the beginning of the videos for legal rights around sharing.

Beginning with the release of 13.0.1 an additional add-in is included called the Clarity Solution Pack. This add-in is a collection of dashboard and reporting content to be used in conjunction with the PMO Accelerator add-in. The relevant documentation related to this new content pack is located here. The PMO Accelerator is a prerequisite of the Clarity Solution Pack because most of the dashboards and reports reference content that is delivered in the PMO Accelerator. The most recent version of the PMO Accelerator Product Guide and Release Notes are available from the above mentioned bookshelf on CA Support. The Clarity Solution Pack includes the following content:

Xcelsius Dashboards

Crystal Reports

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 5 of 22

Note: If you limit the file extensions when uploading documents in your CA Clarity PPM installation, you need to include the SWF (Adobe Flash) file extension in your authorized file extension list (Administration/General Settings-System Options/Document Manager Options) on all of your environments before your upgrade begins. The installation which is performed by On Demand of the interactive portlets included in the add-in will fail if you do not include this extension and may result in a delay of upgrading your environments which do not have this extension in your authorized file extension list. If you do not limit file extensions when uploading documents and you do not have a file extension list defined, please disregard.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 6 of 22

The overall upgrade process is referenced in the table below.

Week 1 Week 2 Week 3 Week 4 Customer Selected Post Prod Upgrade

Preview or Test UAT Start

Test upgrade (if received Preview)

Production upgrade

Development

In an effort to minimize risk and adhere to best practices, any new development activities should be ceased or completed prior to upgrading.

The Test and Development environments are upgraded using existing data. In order to minimize risk and ensure a successful Production upgrade, it is strongly recommended that your organization opens a support ticket requesting Production data to be refreshed into the first non-production system scheduled for the upgrade. Ensure to provide at least a week of lead time for the refresh requests (request any date/schedule on these refresh tickets to occur before the scheduled upgrade to the respective non-production environment).

If you are upgrading from a 12.x version of Clarity, then data will be refreshed from the production environment to a new non-production environment on the v13 code base, referred to as the Preview environment. This new Preview environment will be available for your use for a period of four weeks. The result of this stage is that you will have an environment which you can leverage to become familiar with the new version and also create testing scripts for your UAT/Regression testing which should be performed in your Test environment when upgraded.

Note: Use your Production credentials for access to the Application, InfoView and the CMC.

The delivery of your Preview or upgraded Test environment will be provided within the initial ticket you have opened requesting the upgrade. If you are receiving a Preview environment, the URL information will also be provided on this ticket.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 7 of 22

SFTP URL and login credentials for the Preview environment will not be provided on this ticket. If you require the use of SFTP on the Preview environment, please open a ticket under your Go Live Project Site ID to enable this functionality within the Preview system.

The Preview or Test system requires approximately 2-3 days to be processed and is delivered from the start date of your upgrade. Once the Preview or Test environment details have been updated on the ticket, it will be your indication that the system is ready for use. The customer contact associated to the ticket will also receive an email notification via the ticket and is responsible for notifying other individuals that require a status of the upgrade. If you have any issues you feel are related to delivery of this environment, please open a case specific to the issue to ensure the appropriate attention and expertise is applied.

Once the Preview v13 environment (or 1st upgraded non-production system) has been provided, you may use it to familiarize yourself with the new features, test any expected bug resolutions and also assist with the creation of testing scripts which should be utilized on the next stage (2nd Stage) to perform your UAT/Regression testing to ensure that the application performs as expected. Your testing should cover the following:

Testing scripts developed during your initial implementation

Applicable bug fixes

New functionality

Custom reports and universes

Data integrations

Custom Processes with GEL scripting

Custom Portlets with NSQL data providers

Add-In packages and related configurations

Global Delivery (GD) components

Interfaces

Note: If upgrading from 12.x, all support tickets related to this upgrade must be opened under your Go Live Project Site ID in order to have them addressed in a timely manner as part of this upgrade.

If you are upgrading from a 12.x version of Clarity, then you will have a Go Live Project Site ID which should or will be provided to you on an upgrade notification email. If your upgrade is a minor upgrade within v13, then please disregard this section.

During this upgrade process you should only utilize the Go Live Project Site ID to open support tickets as part of your testing (see section 2.4) and the Production upgrade ticket (see section 2.7).

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 8 of 22

If your users need to open support tickets, they will need to be joined to the Go Live Project Site ID. Please note that only ‘members’ of the Go Live Project Site ID can open Support tickets.

For assistance on how to add additional members of your team to the Go Live Project Site ID and how to open tickets under your Go Live Project Site ID, please refer to the “CA Clarity On Demand Upgrade - How To Use Go Live Project Site ID.pdf” file attached to your upgrade notification email.

Note that delays will occur if tickets are not opened under your Go Live Project Site ID.

Your Test environment will be upgraded in this second stage. If you received a Preview environment, the Test environment upgrade will begin on (start date + 15 business days) and will be delivered by the end of 16th business day. You should transition your testing efforts from the Preview to the Test environment to perform any additional testing necessary to ensure preparedness for the upcoming Production upgrade (Stage 3). The Preview system will be reclaimed the week following your Test upgrade.

If your upgrade is within v13 (minor upgrade) then your Test system will be upgraded beginning on your confirmed start date.

If your testing efforts take more than 90 days on Test, we recommend a refresh of Production data into your Development environment and an upgrade to Development take place prior to scheduling your Production upgrade. Please open a ticket in order to have your Development environment upgraded first before Production if your testing efforts have exceeded 90 days (another separate ticket should be opened for the refresh of Production data into Development to occur prior to the confirmed Development upgrade date).

The initial ticket you have opened requesting the upgrade as listed in section 2.3.1 will be used to communicate your upgraded Test environment details or within a sub ticket of the initial ticket if you received a Preview environment. Once the Test environment details have been posted to the ticket, it will be your indication that the system is ready for use. The customer contact associated to the ticket will also receive an email notification via the ticket and is responsible for notifying other individuals that require a status of the upgrade.

Once the Test environment has been upgraded, it would not be possible to downgrade to the prior version.

If you have any issues you feel are related to delivery of this environment, please open a case specific to the issue to ensure the appropriate attention and expertise is applied.

Your upgrade will not continue until you open a ticket titled “Testing Complete, Upgrade Production” to request the upgrade to your Production system.

Please allow for 6 business days minimum of lead time for this request. Once the Production ticket has been opened, it does not guarantee availability of the upgrade to occur the following weekend. Availability of the date requested as well as standard maintenance

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 9 of 22

windows (see Appendix A) will need to be considered prior to a confirmation of a date provided on the ticket from the On Demand Team.

The Production environment upgrade will start on a Friday after the close of business and is typically completed by the next day on Saturday (end of day). Once the Production environment has been delivered to you on the ticket opened requesting the upgrade, it will be your indication that the system is ready for use. The customer contact associated to the ticket will also receive an email notification via the ticket and is responsible for notifying other individuals that require a status of the upgrade.

If you require immediate assistance to a major issue that has been identified with your post-upgrade Production system, please open a Severity 1 ticket (under your Go Live Project Site ID if one was provided). If rollback to the prior version is necessary, the rollback will contain all the data prior to the Production upgrade.

If your organization is currently provisioned within the On Demand Portal, then the users assigned to the Production environment on the Portal will have access to Production if the user also exists within Clarity.

After the Production upgrade has been completed, the Development and any remaining Non-Production environments will be upgraded in the final stage of the overall upgrade process. A sub ticket will be opened from the Production upgrade ticket by On Demand to communicate the upgrade to your Development and any remaining non-production environments which remain on the previous version. The Development upgrade will start 6 business days after the Production Upgrade has been completed, to be delivered on the 7th business day. As an example, if your Production upgrade completes on April 7th, the development environment will be delivered on the 17th. Exceptions to this typical completion date may occur occasionally and any delay would be communicated via the ticket, if necessary. Once these remaining environments have been upgraded, should you have any issues, please open a case specific to the issue to ensure the appropriate attention and expertise is applied.

If you are upgrading from 12.x, we will close your Go Live Project Site ID 4 weeks after the Development upgrade which would indicate the completion of your upgrade cycle. You may still view any ticket content after the Go Live Project Site ID is closed, however, the tickets would be read only and no updates would be possible. If you are experiencing any issues after the 4 week period after your Development Environment has been upgraded, please open a ticket under your Standard Support Site ID.

For most clients, the overall timeline to upgrade all three application instances is approximately seven to eight weeks. Some clients with large data sets and complex configurations may require additional testing time.

The following table outlines the sequence of tasks and activities to complete a full cycle upgrade for a typical customer:

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 10 of 22

Stage Description Days

1 Upgrade Production data in a Preview environment

Use of Preview for generation of testing scripts & UAT/Regression Testing

15

2 Test environment is upgraded

UAT/Regression Testing

15

3 Production environment is upgraded 1

4 Development/Remaining Non-Production environments are upgraded. Old systems are also decommissioned.

10

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 11 of 22

For customers upgrading from 12.0.x to v13, all application servers will be migrated from Windows to Linux-based servers.

If you are on a version prior to v12.0.x and if your organization is using an FTP mounted drive there will be a change to this mount which may affect any processes that are reading/writing to this location. The new mount location will be “/fs0/clarity1/share” which is a symlink. The symlink will allow you to restore processes from one environment to another without code adjustments for the location to your shared folder. The “/fs0/clarity1/share” will point to Development, Testing, or Production folders within the SFTP mount respective to the environment.

If you are upgrading from version 12.0.x and if your organization is using an SFTP mounted drive the SFTP URL will change with the upgrade of v13. The URL for each datacenter is listed below. If your datacenter is not listed, please disregard this section and you may continue to use your existing SFTP resource.

West Coast (SJC): from ftp.myclarity.com to sftp1.ondemand.ca.com

East Coast (SST): from ftp.myclarity.com to sftp2.ondemand.ca.com

EMEA (MUN): from ftp.myclarity.com to sftp3.ondemand.ca.com

Any SFTP client may be used to connect to the location. You may also test without account credentials by using the telnet command via port 22 from a system to ensure network access to your respective SFTP location listed above.

If you are upgrading from version 12.0.x, your account credentials used to connect to the SFTP location will change. The new account information will be provided upon completion of each environment and will be communicated to your technical contact.

A number of clients have developed integrations that leverage a shared directory that can be called within GEL scripts. The following code is required and illustrates the proper GEL syntax with the integration location:

GelParams:

<gel:parameter var="ShareFolder" default="/fs0/clarity1/share"/> The ShareFolder parameter is the same folder that is accessed through your SFTP account associated to your environment folder. Subdirectories are optional, however, and can be created and included in the GEL parameter.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 12 of 22

When using XOG through GEL using the <soap:invoke> tag, instead of hard-coding the endpoint to a specific host URL you may specify <soap:invoke endpoint="internal"> to allow GEL to automatically determine the correct SOAP URL for the local environment. This will prevent situations where a database restored from Production into a non-production environment having XOG URLs that still specify the Production environment.

For any GEL scripts where the NIKU_HOME var is hard-coded, the following syntax should be used in order to dynamically retrieve this information:

<core:invokeStatic className="java.lang.System" method="getenv" var="NIKU_HOME">

<core:arg value="NIKU_HOME"/>

</core:invokeStatic>

<gel:parse file="${NIKU_HOME}/config/properties.xml" var="properties"/>

Oracle 11 is the database vendor and version used with v12.1.x and higher. Verify that any query tools used for development are compatible with this version of Oracle.

For customers provisioned within the CA On Demand Portal, enablement of the Centralized Account Management will occur using the ca_portal@dummy.com account. If you already have this feature enabled, the account credentials used to leverage this feature will change to ca_portal@dummy.com. This account must not be modified and will be maintained by the CA.

Vanity URL’s, a URL with a company name such as ACME.ondemand.ca.com, will no longer be supported. If your environments already have URLs in the format “cppm####.onedemand.ca.com”, these would not change.

If your organization uses Federated SSO and leverages the “TargetURL” parameter, the internal links used by end users will need to be updated to reflect the new URLs of your Clarity environments.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 13 of 22

Previously, CA Clarity PPM shipped with a single Business Objects universe. CA Clarity PPM v12.1.x and higher introduces four new pre built Business Objects universes. The following universes are supported:

CA PPM Investments

CA PPM Resource

CA PPM Timesheet

CA PPM Investment Financials

See the Business Objects Universes for CA Clarity PPM Reference Guide for details on each universe.

Note the following:

Each universe contains views written specifically for that universe.

No reports are shipped as part of these four new universes.

A new job has been created to populate tables specific to the new universes and enables data to appear in reports:

Update Business Objects Reports

There are 5 checkboxes each populating different tables:

Update Portfolio Content populates a table, ‘RPT_PORTFOLIO_CONTENT’, which simply builds a link between a portfolio and all the investment contents.

Update WBS Index builds a pointer table, ‘RPT_WBSINDEX’, which links summary tasks to all the tasks within the summary task’s hierarchy. This is used when reporting Phases, Activities and Tasks under a project.

Update Universe Calendar sets up a calendar, ‘RPT_CALENDAR’, with start and finish dates as well as an FTE for the time range. Stores records in increments of DAILY, WEEKLY, MONTHLY and QUARTERLY.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 14 of 22

Update Program Hierarchy populates RPT_PROGRAM_HIERARCHY which stores pointers for programs and all the associated projects.

Update OBS updates the data mart OBS tables NBI_DIM_OBS and NBI_DIM_OBS_FLAT.

This job should be run nightly to keep the tables up to date.

This job creates missing, active users on Business Objects and adds these users to the CA-PPM-Reporting-User User Group in Business Objects. Users are created with a blank password and are prompted to change the password when initially logging in to Business Objects Infoview. This job must be initially run before the execution of reports and must be scheduled based upon the frequency of newly added users to Clarity.

Note: This job will not add users that are marked as “External” on the Resource side. If you require these externally flagged resources to be able to run reports from Clarity, please uncheck the External flag and then execute the Business Objects Users Job. Once the job has completed, you may re-select the External flag for the users. These users would now be able to run reports within Clarity.

The following information is intended to supplement the information within the “Reporting Changes Introduced for Business Objects” on the Change and Impact Guide, and the Business Objects Universes for CA Clarity PPM Reference Guide.

Efforts will be made to migrate all custom content; however, all content may not migrate successfully. Careful testing of all custom reports and universes is essential for a successful upgrade.

No report instances (report snapshot data from the report library) will be migrated as part of the upgrade. Save copies of all report instances before the upgrade.

Custom reports may require recompilation based upon data model and/or connection changes. (See the Technical Reference Guide for information about additions, deletions, or updates to the data model.) All reports should be tested and adjustments made to the reports within the UAT period.

New stock universes will be included.

Existing Infoview accounts will be migrated.

Reports scheduled within Infoview must be rescheduled.

As part of this upgrade, server names and IP addresses will change. Please note that any reports that have this information hardcoded will need to be updated.

If you currently use the BO Designer, you will need to upgrade to the most recent version. Please open a new support ticket on the CA Support site to request the latest version of this tool set.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 15 of 22

As part of the upgrade to v13, all previously installed add-ins are upgraded; however, to preserve existing view configurations, the updates will not be applied. Upgraded add-in items can be reviewed and applied using the Add-In Details page in CA Clarity Studio. Please review the product guide for each add-in to decide which upgraded views should be applied and which ones should be adjusted manually. Product guides for add-ins are available from the CA Clarity PPM 13.0 SP 1 (On Demand) Bookshelf located on CA Support (support.ca.com)

Note: Applying a view overwrites the configuration of the existing view. The only way to restore overwritten views is a complete system restore.

From a reporting perspective, the following add-ins contain new reports:

PMO Accelerator

CA Clarity PPM Accelerator for the PMBOK Guide

CA Clarity Grants Manager

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 16 of 22

Customers upgrading to v13 who are using Open Workbench, the CA Clarity PPM Microsoft Project Interface, or the XOG client must review the following notes on client application compatibility:

Versions of Open Workbench installed prior to this release are not compatible with this release.

Uninstall the previous version of Open Workbench and install the version provided with this release. The installer also prompts for the installation of CA Clarity PPM Schedule Connect, which is required to use Open Workbench with CA Clarity PPM.

Versions of the CA Clarity PPM Microsoft Project Interface installed prior to this release are not compatible with this release.

Uninstall the previous version of the Microsoft Project Interface and install the version provided with this release. The installer prompts for the installation of CA Clarity PPM Schedule Connect, which is required to use Microsoft Project with CA Clarity PPM.

Note: See the Using Clarity with Open Workbench and Microsoft Project Guide for more information about how to map CA Clarity PPM fields to Microsoft Project.

All XOG client users must upgrade to the CA Clarity PPM version of this client software. Uninstall the XOG client before installing the new version.

Note: See the XML Open Gateway Developer Guide for more information.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 17 of 22

Based upon the user interface enhancements that are included in this release, clients that use the CA Productivity Accelerator will be required to update their custom content. The CAPA development client would also need to be upgraded to v11.1 in order to update your custom content.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 18 of 22

If you have additional questions, please open a ticket under your Go-Live Project and they will be answered as quickly as possible.

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 19 of 22

When requesting your Production upgrade, please consider the below monthly maintenance windows where upgrades could not be scheduled:

Maintenance Window Month

Maintenance Window Date

October 2012 October 13th

November 2012 November 10th

December 2012 December 8th

January 2013 January 12th

February 2013 February 9th

March 2013 March 9th

April 2013 April 13th

May 2013 May 11th

June 2013 June 8th

July 2013 July 13th

August 2013 August 10th

September 2013 September 14th

October 2013 October 12th

November 2013 November 9th

December 2013 December 14th

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 20 of 22

Physical Upgrade of customer environments,

System testing and validation (ie: application and background services up and running)

Resolution of any system or environment issues

Understand and manage the Upgrade process

Create and execute an upgrade plan

Perform Regression and UAT Testing

Identify & Resolve non-standard component compatibility issues

Update personalized training materials

Track, Manage and Perform any post-upgrade tasks

Be sure all production issues either have been resolved or will be resolved with the upgrade

Finalize any development and promote to Production

Request copy of Production to non-Prod environment(s) o Required to refresh the Test Environment on Major Upgrades and strongly suggested for

minor upgrades o Necessary in order to allow OD to test Production dataset upgrade on your non-Prod

environment(s) o File a Support Ticket for each non-Prod environment requesting the copy of Prod to that

environment

Review the Upgrade Process Guide o Provides guidance on what to expect during the upgrade o Has links to important sites and documents o Provides high-level timeline

Review all Release Notes for changes to assess impacts o Components – Reports, Portlets, Processes, Jobs or Interfaces o Training Materials – Manuals, Guides, On-Line o Add-Ins – New or Updated Components

File Support Ticket requesting an upgrade to the desired version

o Minimum 1 week lead-time for scheduling o [Major Upgrade Only] Preview Environment will be set up with a copy of Production o Upgrade Request ticket will cover both Preview and Test o A Go-Live Site Project ID will be issued as part of Upgrade notification

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 21 of 22

The Preview Environment is established on Major Upgrades using a copy of your current Production DB to allow you to review v13 and provide better estimates for your Upgrade Plan. This is not a test system and all tasks should be completed within 3 weeks.

Determine if you need the SFTP Site Enabled o Needed if you need to validate interfaces or data packages o File a support ticket to request the SFTP site enablement under your Go-Live Site Project

ID

Perform high-level analysis of impacts o Focus on highly impacted areas identified in Pre-Upgrade Prep first o Identify and record a list of non-standard components that need to be change to be

compatible with the new version Who is responsible for resolution of the issues Engage appropriate parties for estimates

o Estimate the time needed to update training materials and roll out to users o For System Issues: Be sure to open any tickets for issues concerning the upgrade under

your Go-Live Site Project ID (use std. Support ID for upgrades from 13.x to 13.x)

Generate or Update any Testing or UAT Scripts

Select and Apply Add-Ins o Apply any updated or new components from Add-Ins (eg: PMO Accelerator or Content

Pack) o Validate the Add-Ins and confirm inclusion on other environments o Document the items applied to repeat on other environments o The Preview environment is a perfect place to apply only the ones you think you need

and also check out new ones before moving to one of your real environments o NOTE: You cannot uninstall Add-Ins & Preview cannot be restored to a prior state

Review Estimate of Impacts o Adjust Project Schedule as appropriate o Finalize estimates for

Components – Issue Resolution or Updates Training & Training Materials Change Management Efforts

[Major Upgrades Only] Test Environment will be automatically upgraded 15 business days after the Preview/Start Date.

Perform Regression Testing o Execute regression testing to fully test the Upgrade o Keep list of additional issues or changes

Update Non-Standard Components and Other Issues o Engage appropriate resources to update components o Keep a list of all fixes that have been applied o Resolve any other issues identified

Apply Selected Add-Ins

Perform UAT Testing o Run through preview UAT scripts to validate

Version 3.7

© 2013 CA Technologies. All rights reserved. Page 22 of 22

o Have users try out new version and give feedback

Create Migration Plan and Post-Production Checklist o Need to move all updates done in Test to Prod after Upgrade o Need to identify any testing or validation that needs to be done Post-Prod Upgrade

Training & Change Management o Finalize any training materials o Schedule training

Schedule Production Upgrade o Submit Support ticket requesting upgrade of Production Environment and include your

desired timeframe/maintenance window o [Major Upgrade] Use your Go-Live Project Site ID o [Minor Upgrade] Use your standard Support ID o Validate that your resources are available

Create a Short Interval Schedule for Upgrade o Needed if several components need to be updated after Upgrade o Ensures that the right people are available to perform task or for validation

Once upgrade is complete, test and perform post-Prod tasks from Production task list

Apply Add-Ins

Perform Final Environment Validation o For System Issues: Be sure to open a support ticket under the appropriate ID

These environments will typically be upgraded 7 business days after the Production Environment – Please be sure all development has been completed prior to upgrade

If there were updates made get your environment compliant with the new version, you will need to either:

o Perform the same set of Post-Prod tasks that were done on Prod o Request a DB copy from Prod to the Non-Prod environment

Validate the environment