Datastore configuration lifecycle

Overview

Manage multi-configurations

Modify a configuration

Application isolation

Overview

Before Datastore can use the configuration, you must create it and deploy it in the Repository:

  1. Import formats and dictionaries into the Designer and create the configuration.
  2. Deploy the configuration in the Repository.
  3. Inject data into Datastore and create queries.

Configuration lifecycle

Each time you deploy a new package, the Configuration Repository creates a configuration that is defined by:

  • An identifier
  • The list of types in this configuration.

Repository provides an API to:

  • Get the latest configuration identifier.
  • Get a given configuration identifier.
  • List the differences between two configurations.
  • Filter the list of valid types according to a date.
  • Get the validity period for a type.

Manage multi-configurations

In Datastore, you can create configuration data for several applications by switching from one application to another. To each application corresponds a namespace.

When the Repository manages several applications, it allows:

  • The service team to handle several customer applications in the same Designer.
  • A customer to manage several copies of its applications or several applications.
  • Multi-tenant architecture with a common Configuration Repository. Instances of Datastore can be installed on different servers.

Modify a configuration

When you modify a configuration with the Axway Designer, at deployment time these changes may impact the database schema or the components settings.

Create new deployment version

Application isolation

The application concept is used to define an environment and ensure consistency of the structures and query definitions.

To publish configurations and query definitions from a Test/Pre-production environment to a Production environment, the two environments must share the same application name.

Related Links