Jolt uses the Oracle Tuxedo Service Metadata Repository as the database where Oracle Tuxedo services are defined, such as name, number, type, parameter size, and permissions. The repository functions as a central database of definitions for Oracle Tuxedo services and permits new and existing Oracle Tuxedo services to be made available to Jolt client applications. An Oracle Tuxedo application can have many services or service definitions, such as ADD_CUSTOMER, GET_ACCOUNTBALANCE, CHANGE_LOCATION, and GET_STATUS. All or only a few of these definitions can be exported to the Metadata Repository. Within the Metadata Repository, the developer or system administrator uses the Metadata Editor to export these services to the Jolt client application. The original Jolt Repository is deprecated now and all service definitions that it stores can be loaded to Oracle Tuxedo Service Metadata Repository. For more information, see Migrating from Jolt Repository to Oracle Tuxedo Service Metadata Repository.

All Repository services that are exported to one client are exported to all clients. Oracle Tuxedo handles the cases where subsets of services may be needed for one client and not others.

The following figure illustrates how the Metadata Repository brokers Oracle Tuxedo services to multiple Jolt client applications. (Four Oracle Tuxedo services are shown; however, the WITHDRAW service is not defined in the repository and the TRANSFER service is defined but not exported.)