Schema Model Migration with Shared Nothing Persistence

Using Shared Nothing persistence to migrate a schema model.

You can choose one of these options:

  • Deploy the new EAR with the additional field and restart all nodes. System will automatically alter the space as needed during recovery.
  • If it is not desired to restart cache nodes, shut down all inference engines. Connect with AS administrator and alter the space to add new fields as shown in example below.

    The new field must be nullable as is the case for all user fields in BusinessEvents .

    alter space name"dist-unlimited-bs-readOnly-Test--be_gen_Concepts_Simple" add (field name "long_field" type 'LONG' nullable true)
    alter space name"dist-unlimited-bs-readOnly-Test--be_gen_Concepts_Simple" add (field name "con_cept_array" type 'BLOB' nullable true)

    Then start the inference engines.

  • Hot deployment of new properties for Shared Nothing persistence has been added .
Note: Adding a concept property of type contained concept with the contained concept type set to an existing concept is supported only for the options above.
  • Dropping existing field

    This option is available only in AS-2.1.2 release. Keep the existing unused fields as is, without assigning any values.

Note: With AS-2.1.2: simply deploy the new EAR without the dropped field and restart all the nodes. System will automatically alter the space as needed during recovery.

Altering of existing field types: Not supported (requires a custom solution).

Hot Deployment of New Properties

Hot deployment of new properties into existing TIBCO BusinessEvents concepts is available only in these cases:

  • When cache Object Management is enabled with no persistence or Shared Nothing persistence.
  • When the concepts with new properties are cache-only.