Managing the Life Cycle of a Recipe

Most of the recipes undergo a life cycle that involves recipe creation, testing, and deployment on a system where the end-to-end integration flow is tested and confirmed to be successful.

Most of the recipes undergo a life cycle that involves recipe creation, testing, and deployment on a system where the end-to-end integration flow is tested and confirmed to be successful. After a recipe is found to be working satisfactorily and as per the design, it is time to move it to another system. For example, you can first create a recipe in a development environment, then move it to a test environment and finally, bring it to your production environment.

Reltio Integration Hub empowers you to do the following tasks:

  • Export and import packages containing recipes and their dependencies (lookup tables, message templates, and so on.)
  • Package recipes can also be placed in GIT
  • Save every change to the recipe in a version history with the possibility to restore a prior version
  • Use the Project and Folder constructs to organize your recipes and other assets
  • Include all recipe dependencies in the export, and import in a target account
  • Avoid exporting any credentials, keys, or other private data that is required to make a connection to an application

Packages provide a mechanism to export and import recipes and their dependencies from one account to another. To export packages, you will need to first create a manifest. A manifest identifies the recipes that a package should contain and keeps track of dependencies and changes. For more information, see Recipe Life Cycle Management.