Auto-provisioning a migration bundle lets you bootstrap configurations onto a CA API Gateway in a consistent manner. The migration bundles are imported on startup, after the Gateway license has auto-provisioned successfully (see Auto-Provision a Gateway License). For information on creating migration bundles, see the Gateway Migration section.
This topic applies to these Gateway form factors: Appliance, Virtual Appliance, and Container.
Note the following about migration bundles:
To auto-provision a migration bundle for an Appliance or Virtual Appliance Gateway:
Create the target directory:
# mkdir -p /opt/SecureSpan/Gateway/node/default/etc/bootstrap/bundle
Set the appropriate permissions:
# chmod -R 775 /opt/SecureSpan/Gateway/node/default/etc/bootstrap/bundle
Copy the migration bundle(s) into the
Tips: (1) Bundles must end with
.bundle as a file extension. (2) For the Gateway to fail at startup when a bundle import fails, the bundles must have the
.req.bundle file extension.
Restart the Gateway service:
# service ssg restart
(Optional) Once the migration bundle is auto-provisioned, you may remove the bundle directory created in step 2:
# rm -rf /opt/SecureSpan/Gateway/node/default/etc/bootstrap/bundle
The migration bundle is now imported.
For information on how to auto-provision a migration bundle for the Container Gateway, see "Customize the Container Gateway. The instructions in the Dockerfile perform the auto provision." in