Migrating the Development Environment

To benefit from the Data Packager, you must migrate your existing packaging and deployment setup.

This section presents the migration tooling concepts.

If you have defined all your packages using BUILD.CONTROL/DL.DEFINE or any other packaging tool, you can use a command line tool to create packages in the new data packager format.

Migration

Migration Tooling

You can achieve the following goals with Data Packager tooling:

• Create package definition CSV files out of folder structures that include any Design Studio records (.d, .data.eson, .version, .enquiry, .eson, etc.).
• Create packages out of package definition files.
• Build or deploy data packages in a continuous integration setup or through simple command line.

How many packages?

It is recommended to separate packages in such a way that they are independent from other packages. This approach will enable very high-productivity, for instance, by leveraging Temenos Continuous Deployment offering.

The fundamental recommendation is that you must not have the same data record in two different packages. There has to be one unique source of truth per data record. In the near future, Data Packager will provide the tooling to ensure uniqueness of data across data packages.

Migration Options

This topic describes at a very high level some migration options.

• Migrate only new development

  You do not migrate all your existing Temenos Transact local customizations. You start using the new Data Packager only for all new work.

• Migrate full local development

  Identify all your local Temenos Transact customizations (ideally leveraging naming conventions to identify your data) and create initial packages out of it.

• Migrate without any SCM usage

  The use of a SCM system is not mandatory but highly recommended.

  You can still decide to use only the Web data packager to manage your packages.

Migrating the Packaging and Deployment Setup

Follow the below steps to migrate packaging and deployment setup:

1. Identify a Temenos Transact reference environment that holds configuration data as in production.
2. Create a CSV list (or lists) of the data records you would like to extract.
3. Create a package(packages) out of the CSV file(s).
   • It is recommended to store the package unzipped in a SCM (Source Control Management) system of your choice.
   • You can then build a CI (Continuous Integration) pipeline to rebuild packages automatically.
4. Deploy the packages either through the web interface or typically by issuing a curl request to deploy API. Sample curl:

   curl -X POST -L -F 'package=@fullpath/mypackage.zip;type=application/zip' ${DEPLOY_SERVER_URL}/api/v1.0.0/meta/dsfpackages/deploy