Installing the target system on VMware

Create the project directory, configure you target deployment, create the ISO files, and deploy your VMs.

Form factor migration to VMware is supported only from a VMware environment. You cannot migrate a Kubernetes or OpenShift API Connect deployment to VMware.

When you install the target system, before you create the ISO files that are used in the OVA deployment, you must set some of the subsystem properties of your target system to the same values as your source system. Refer to the data directory that you created in Preparing the source system to find these values.

Other subsystem properties can be set to different values from your source subsystem. For example, the API endpoints such as portal-www and platform-api. Changing API endpoints is the typical use-case of a VMware to VMware migration.

Management subsystem

Follow the usual steps for configuring your management subsystem deployment: Preparing the management subsystem for deployment, but set the following properties to the same values as your source system.

Subsystem name.
```
apicup subsys create <management subsystem name> management
```
where <management subsystem name> is the same as your source system.
Encryption secret.
```
apicup certs set <management subsystem name> encryption-secret --encoded-string <v10 source mgmt encryption secret>
```
where <v10 source mgmt encryption secret> is found in data/<management subsystem name>/encryption-secret-*.yaml

Site name.

apicup certs set management site-name=`<site name>`

Credential secrets.

apicup certs set <management subsystem name> atm-credential --encoded-string '<encoded string>'
apicup certs set <management subsystem name> consumer-toolkit-credential --encoded-string '<encoded string>'
apicup certs set <management subsystem name> designer-credential --encoded-string '<encoded string>'
apicup certs set <management subsystem name> toolkit-credential --encoded-string '<encoded string>'
apicup certs set <management subsystem name> juhu-credential --encoded-string '<encoded string>'
apicup certs set <management subsystem name> consumer-ui-credential --encoded-string '<encoded string>'
apicup certs set <management subsystem name> ui-credential --encoded-string '<encoded string>'
apicup certs set <management subsystem name> discovery-credential --encoded-string '<encoded string>'
apicup certs set <management subsystem name> governance-credential --encoded-string '<encoded string>'

where <encoded string> is found in the corresponding secret YAML file in data/<management subsystem name>. For example:

<management subsystem name>-atm-cred.yaml
<management subsystem name>-ccli-cred.yaml
<management subsystem name>-cli-cred.yaml
<management subsystem name>-cui-cred.yaml
<management subsystem name>-dsgr-cred.yaml
<management subsystem name>-juhu-cred.yaml
<management subsystem name>-ui-cred.yaml

The encoded string is stored in credential.json property of each file:

apiVersion: v1
data:
  credential.json: eyAiaWQiOiAiMzhmMzRjOTktODFhNC00NWFkLWFkOTgtMGM1MGFjN2YzYmJjIiwgInNlY3JldCI6ICI3OTIxYzE5Yi1jNWUwLTRhYzQtYTkyZC1iZjNmYWJlZWEwNDIiIH0=
kind: Secret
...

You can use the same management database backup configuration as your source system, or you can specify a new configuration.

Portal subsystem

Follow the usual steps for configuring your portal subsystem deployment: Preparing the portal subsystem for deployment, but set the following properties to the same values as your source system.

Subsystem name.
```
apicup subsys create <portal subsystem name> portal
```
where <portalsubsystem name> is the same as your source system.
Encryption secret.
```
apicup certs set <portal subsystem name> encryption-secret --encoded-string <v10 source ptl encryption secret>
```
where <v10 source ptl encryption secret> is found in data/<ptl subsystem name>/portal-encryption-secret-*.yaml
Site name.
```
apicup certs set <portal subsystem name> site-name <v10 source ptl site name>
```
where <v10 source ptl site name> is found in data/<ptl subsystem name>/config.yaml
Backup configuration.
Use the same backup configuration as your source system to restore your portal sites.