Preparing the source system

Run the save_v10_source_configuration.py script to gather the source system configuration.

Before you begin

About this task

The save_v10_source_configuration.py script:

Creates a data directory with all configuration saved in it.
Generates two YAML files in the same directory as the script:
- gateway_portal_mapping.yaml
- provider_org_credentials.yaml
Important: The YAML files must be filled in:
- gateway_portal_mapping.yaml must be filled in if, when restoring onto the target system, you choose to run register_gateway_portals_in_target.py in silent mode. See step 3.c in Restoring the target system on Kubernetes, OpenShift, and Cloud Pak for Integration.
- provider_org_credentials.yaml must be filled in if, when restoring onto the target system, you choose not to use the migration user credentials while updating Portal and Gateway information. See step 4 and step 6 in Restoring the target system on Kubernetes, OpenShift, and Cloud Pak for Integration.

To view script parameters:

python3 save_v10_source_configuration.py --help

Procedure

Create a directory called FFM and copy all python scripts to this directory.
Kubernetes, OpenShift, or Cloud Pak for Integration: Save configuration from the source system.
To save the source system configuration, run save_v10_source_configuration.py with the appropriate parameters for your deployment:
- If all subsystems are in the same namespace, and you are using username/password authentication.
  This command saves configuration of all the installed subsystems in the namespace:
```
python3 save_v10_source_configuration.py -u USERNAME -p PASSWORD -s PLATFORM_API_HOSTNAME -r REALM_NAME -n NAMESPACE
```
- If a subsystem needs to be skipped so that its configuration is not saved:
  - Skip Portal:
    python3 save_v10_source_configuration.py -u USERNAME -p PASSWORD -s PLATFORM_API_HOSTNAME -r REALM_NAME -n NAMESPACE -skip_ptl
  - Skip Analytics:
    python3 save_v10_source_configuration.py -u USERNAME -p PASSWORD -s PLATFORM_API_HOSTNAME -r REALM_NAME -n NAMESPACE -skip_a7s
- If all subsystems are in the same namespace, and you are using SSO authentication:
```
python3 save_v10_source_configuration.py --sso -s PLATFORM_API_HOSTNAME -n NAMESPACE
```
- If all subsystems are in different namespace, and you are using username/password authentication:
```
python3 save_v10_source_configuration.py -u USERNAME -p PASSWORD -s PLATFORM_API_HOSTNAME -r REALM_NAME -mgmt_ns <mgmt_namespace>  -ptl_ns <ptl_namespace> -gw_ns <gw_namespace> -a7s_ns  <a7s_namespace>
```
- If the cluster has multiple Gateways, Portals, or Analytics subsystems distributed across namespaces in the cluster, you can save the configuration of the source system using one of the ways shown below. Multiple namespaces need to be separated by "|" symbol. The namespaces used in below example command are ns1, ns2, ns3. Both commands work the same way.
  - python3 save_v10_source_configuration.py -u USERNAME -p PASSWORD -s PLATFORM_API_HOSTNAME -r REALM_NAME -n "ns1|ns2|ns3"
  - python3 save_v10_source_configuration.py -u USERNAME -p PASSWORD -s PLATFORM_API_HOSTNAME -r REALM_NAME -mgmt_ns "ns1" -ptl_ns "ns1|ns2" -gw_ns "ns1|ns2|ns3" -a7s_ns "ns1|ns2"
- If ingress-ca certificates must be saved or exported in the configuration, run the previous commands with -export_cert flag. Applicable only when you are saving management subsystem configuration.

What to do next

Configure your target deployment:

Installing the target system on Kubernetes, OpenShift, and Cloud Pak for Integration