Integration Server 10.3 | Configuring On-Premise Integration Servers for webMethods Cloud | Managing Applications | About Sharing Metadata on an On-Premise Integration Server
 
About Sharing Metadata on an On-Premise Integration Server
You create applications on the on-premise Integration Server to share services with Integration Cloud. Keep the following points in mind while sharing services through an application:
*You can share only services running on the on-premise Integration Server configured to create applications on Integration Cloud.
*You can share only services contained in custom packages.
*You can share services from different packages in the same application. For example, if service A is located in package A, and service B is located in package B, you can add both service A and service B to the same application.
*You can share only those services that have an input and/or output signature specified.
*You can share only those services whose signatures are of the following data types:
*String
*String List
*Document
*Document Reference
*Document List
*Document Reference List
*Object
*Object List
*Any Object or Object List placed into the service pipeline, and therefore any Object or Object List in a service signature, must be a serializable data type. If it cannot be serialized, the pipeline cannot be exchanged with a remote Integration Server. Further, the class names for the data type must be included in the Integration Server whitelist classes file or a package whitelist classes file for the pipeline to be deserialized at the destination Integration Server. Classes defined by Integration Server are already included in the whitelist class file. This requirement applies to all Object and Object List variables, including those contained in a Document or Document List. For more information about the Integration Server whitelist, see the webMethods Integration Server Administrator’s Guide.
*You can set the on-premise Integration Server to send service results to Integration Cloud in batches.
*You cannot share service signatures that include:
*Cyclical dependencies of document references.
*Fields of type String Table, including fields of type String Table in a Document.
*An empty Document or Document List.
*You must configure one or more accounts to associate with the application before you can upload the application to Integration Cloud. For more information about configuring accounts, see Configuring Accounts for Integration Cloud .
*You must upload the application for the updates to be shared with Integration Cloud if you edit:
*The application.
*The signature or referenced Document of a service shared by the application.
*When you upload an application, it replaces the application and operations available on Integration Cloud with the one that you upload.