1. Using Oracle Jolt
  2. Migrating from Jolt Repository to Oracle Tuxedo Service Metadata Repository

7 Migrating from Jolt Repository to Oracle Tuxedo Service Metadata Repository

Jolt Repository is deprecated in this release. All service definitions stored in Jolt repository can be loaded in the Tuxedo metadata repository using the bulk loader tool.

The original Jolt repository server JREPSVR is also deprecated, and all services that JREPSVR provided are now provided by TMMETADATA. If tmloadcf detects presence of JREPSR in ubbconfig, it automatically removes JREPSVR and adds TMETADATA if not already configured.

Using one repository (Tuxedo metadata repository) and one server (TMMETADATA) improve operational effectiveness and reduces the risk of service definitions getting out of sync.

Note:

  • TMMETADATA must run on Oracle Tuxedo 12c Release 2 (12.2.2) or later.
  • Oracle Tuxedo Service Metadata Repository does not support package function.
  • Bulk Loader is still supported but some behaviors are changed.
    • Do not support for deleting service definitions. You must use tmloadrepos -d service[...] or the Metadata Editor to delete services.
    • Do not support for deleting service definitions. You must use tmloadrepos -d service[...] or the Metadata Editor to delete services.
    • The servicetype must be "service"; otherwise you cannot update this service definition.

This topic includes the following sections: