What is the upgrade plan to follow to do an upgrade of Virtual Appliance?
search cancel

What is the upgrade plan to follow to do an upgrade of Virtual Appliance?

book

Article ID: 282519

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

What is the upgrade plan to follow to do an upgrade of Virtual Appliance?

Environment

Virtual Appliance 14.5

Resolution

Supported Upgrade Paths

Symantec IGA supports upgrades ONLY from release 14.4 or 14.4.x to 14.5. Clients on releases prior to 14.4, must upgrade to 14.4 first before they can upgrade to 14.5.

 

Upgrade Prerequisites

Backups
Please take a full backup of the databases/schemas used by Identity Manager, Identity Governance,

Upgrade Overview

This discusses how vApp performs the upgrade and considerations if in a cluster.  This also discusses how each component is upgraded and the "patch_vapp" command from within your session.

Performing the Virtual Appliance Upgrade

 

 
When the Provisioning Server domain is different from the domain that comes by default - "im" (Should be asked about the client environment but not always needed)
 
 
 

Confirmation

Post upgrade, ensure that all services have started. You can examine the status of a service in the Virtual Appliance dashboard. If services have not started, start them manually.

List of start command aliases below depending on what components have been installed and used:

start_dxserver
 
Starts all Symantec Directory DSAs.
 
Note: 
If all Symantec Directory DSAs are started, the monitor will not display per-DSA status. Instead, it displays "[OK] All DSAs are started".
 
start_ig
 
Starts Identity Governance application.

start_im
 
Starts Identity Manager application.
 
start_ip
 
Starts Identity Portal application.
 
start_jcs
 
Starts the Connector Server.
 
start_oracle
 
Starts the internal Oracle 11g Express database (if deployed).
 
start_ps
 
Starts the Provisioning Server.