Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Accelerators are the pre-built solutions that are provided for specific purposes. These Accelerators are in the form of zip files. 

To deploy the Accelerators, follow the steps given below:

  1. Go to migration 4.0.0 · adeptiainc/adeptia-connect-migration (artifacthub.io) to view the details of migration helm package.
  2. Add migration repo using following command:

    helm repo add adeptia-connect-migration https://adeptia.github.io/adeptia-connect-migration/charts/
  3. Click DEFAULT VALUES to download the values.yaml file.

  4. Provide values for the following properties and environment variables in values.yaml file as shown in the table below.

    Variable/Property

    Value

    BACKEND_DB_URL<URL of the backend database server>
    • jdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Backend Database Name>
    • jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>
    BACKEND_DB_USERNAME<Username of your backend database server>
    BACKEND_DB_PASSWORD<Password for your backend database server>
    BACKEND_DB_DRIVER_CLASS<Backend database driver class name>
    BACKEND_DB_TYPE<Type of the backend database server> For example, SQL-Server.
    SHARED_PATH<Environment variable in the values.yaml file that contains the configured shared path> The default value for this variable is /shared. This is the folder created at the root level in the PVC when you deploy Adeptia Connect.
    MIGRATION_XML_FILE_PATH

    <Path of the folder that contains the required Accelerators in the PVC>.

    The Accelerators bundled with the application are by default located at shared/accelerators location in the PVC. You need to place the downloaded Accelerators at some other location in the PVC.
  5. Navigate to the migration directory, and run the below command to install the driver.

    helm upgrade -i migration adeptia/migration -f adeptia/values.yaml -n <NAMESPACE>
    The Migration job does not get deleted automatically after the deployment is complete. You need to manually delete it before you start a new deployment. 

Related topics

Migrate

  • No labels