7.4
Table Of Contents
- Migrating vRealize Automation to 7.4
- Contents
- Migrating vRealize Automation
- vRealize Automation Environment User Interfaces
- Migration Prerequisites
- Pre-Migration Tasks
- Review Changes Introduced by Migration from vRealize Automation 6.2.x to 7.x
- Apply Software Agent Patch
- Change DoDeletes Setting on the vSphere Agent to False
- Check Templates in Your vRealize Automation 6.x Source Environment
- Prepare vRealize Automation Virtual Machines for Migration
- Gather Information Required for Migration
- Obtain the Encryption Key
- List Tenant and IaaS Administrators
- Add Each Tenant from the Source Environment
- Create an Administrator for Each Added Tenant
- Synchronize Users and Groups Before Migration to a Minimal Environment
- Synchronize Users and Groups Before Migration to a High-Availability Environment
- Run Data Collection in Source
- Manually Clone the Source Microsoft SQL Database
- Snapshot the Target Environment
- Migration Procedures
- Post-Migration Tasks
- Add Tenant and IaaS Administrators
- Run Test Connection and Verify Migrated Endpoints
- Run Data Collection on Target
- Reconfigure Load Balancers After Migration
- Migrate an External Orchestrator Server
- Reconfigure the vRealize Automation Endpoint
- Reconfigure the vRealize Automation Infrastructure Endpoint
- Install vRealize Orchestrator Customization
- Reconfigure Embedded vRealize Orchestrator Endpoint
- Reconfigure the Azure Endpoint
- Migrate Automation Application Services
- Delete Original Target vRealize Automation IaaS Microsoft SQL Database
- Update Data Center Location Menu Contents After Migration
- Upgrading Software Agents to TLS 1.2
- Validate the Target vRealize Automation 7.4 Environment
- Troubleshooting Migration
- PostgreSQL Version Causes Error
- Some Virtual Machines Do Not Have a Deployment Created during Migration
- Migration Log Locations
- Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
- Data Collection Radio buttons Disabled in vRealize Automation
- Troubleshooting the Software Agent Upgrade
Table 2‑3. vRealize Automation Appliance Management. This interface is sometimes called
the Virtual Appliance Management Interface (VAMI).
Purpose Access Required Credentials
You use vRealize Automation Appliance
Management for these tasks.
n
View the status of registered services.
n
View system information and reboot
or shutdown the appliance.
n
Manage participation in the Customer
Experience Improvement Program.
n
View network status.
n
View update status and install
updates.
n
Manage administration settings.
n
Manage vRealize Automation host
settings.
n
Manage SSO settings.
n
Manage product licenses.
n
Configure the vRealize Automation
Postgres database.
n
Configure vRealize Automation
messaging.
n
Configure vRealize Automation
logging.
n
Install IaaS components.
n
Migrate from an existing
vRealize Automation installation.
n
Manage IaaS component certificates.
n
Configure Xenon service.
1 Start a browser and open the
vRealize Automation appliance splash page
using the fully qualified domain name of the
virtual appliance:
https://vra-va-hostname.domain.name.
2 Click vRealize Automation Appliance
Management.
You can also use this URL to open
vRealize Automation Appliance Management:
https://vra-va-hostname.domain.name:5480.
3 Log in.
n
User name: root
n
Password: Password you
entered when you
deployed the
vRealize Automation
appliance.
Table 2‑4. vRealize Orchestrator Client
Purpose Access Required Credentials
You use the vRealize Orchestrator Client
for these tasks.
n
Develop actions.
n
Develop workflows.
n
Manage policies.
n
Install packages.
n
Manage user and user group
permissions.
n
Attach tags to URI objects.
n
View inventory.
1 Start a browser and open the
vRealize Automation splash page using the fully
qualified domain name of the virtual appliance:
https://vra-va-hostname.domain.name.
2 To download the client.jnlp file to your local
computer, click vRealize Orchestrator Client.
3 Right-click the client.jnlp file and select
Launch.
4 On the Do you want to Continue? dialog box,
click Continue.
5 Log in.
You must be a user with the
system administrator role or
part of the vcoadmins group
configured in the
vRealize Orchestrator Control
Center Authentication
Provider settings.
Migrating vRealize Automation to 7.4
VMware, Inc. 8