Abstract: Schema information is provided with transmission of a data object. When a data object is converted to a transmission format, schema information for the object type is added to the transmission format element. The unmarshalling code uses the schema information to update a schema registry at the receiving end. The schema registry may then be used as a tool for converting the transmission format element back to the data element. The next time an object of that object type is sent to the recipient, the schema information is not added to the transmission format element.

Abstract: Provided is a method, system, and program for providing an object discovery agent (ODA) client. There is one object discovery agent (ODA) client and at least one ODA, wherein each ODA is associated with one application and includes: (i) application programming interfaces (APIs) to communicate with the associated application to discover definition information on objects maintained by the application and (ii) code to communicate with the ODA client. The ODA client communicates with one of the at least one ODA to cause the ODA to gather definition information on at least one object used by one application. The gathered object definition information is provided to an integration server to integrate the object in an environment including heterogeneous objects from different applications.

Abstract: Provided is a method, system, and program for providing an object discovery agent (ODA) client. There is one object discovery agent (ODA) client and at least one ODA, wherein each ODA is associated with one application and includes: (i) application programming interfaces (APIs) to communicate with the associated application to discover definition information on objects maintained by the application and (ii) code to communicate with the ODA client. The ODA client communicates with one of the at least one ODA to cause the ODA to gather definition information on at least one object used by one application. The gathered object definition information is provided to an integration server to integrate the object in an environment including heterogeneous objects from different applications.

Abstract: Provided is a method, system, and program for providing an object discovery agent (ODA) client. There is one object discovery agent (ODA) client and at least one ODA, wherein each ODA is associated with one application and includes: (i) application programming interfaces (APIs) to communicate with the associated application to discover definition information on objects maintained by the application and (ii) code to communicate with the ODA client. The ODA client communicates with one of the at least one ODA to cause the ODA to gather definition information on at least one object used by one application. The gathered object definition information is provided to an integration server to integrate the object in an environment including heterogeneous objects from different applications.

Abstract: An apparatus, system, and method are disclosed for automatically maintaining identity relationships among disparate enterprise information systems. The apparatus comprises a synchronization hub comprising an identity relationship repository, a relationship service module, a consistency module, and an adjustment module. The relationship service is configured to access a target relationship entry using a unique key from a source business object, wherein the source business object is representative of changes made in a source enterprise information system. The various components and modules of the synchronization hub cooperate to determine identity relationships that need updating and to propagate identity relationship changes to one or more destination enterprise information servers.

Abstract: When a data object is sent from one application to another, the marshaling code includes type information with transmission of the data object. When the data object is converted to the transmission format, type information for the data object is added to the transmission format element. The unmarshaling code uses the type information to obtain schema information for converting the transmission format element back to the data element.

Abstract: A computer implemented method, an apparatus and computer instruction are provided for deployment of roles. Aspects of the present invention allow user to define in a schema a definition of a relationship that comprises a set of roles participating in the relationship. Each role in the set of roles is defined as an inlined role or an independent role. After the schema is processed, aspects of the present invention determine if the role in the set of roles is an inlined role or an independent role based on the definition of the relationship, deploy the relationship and the role as a single entity if the role is an inlined role, and deploy the relationship and the role as separate entities if the role is an independent role.

Abstract: A mechanism is provided for converting after image data into a delta level change. An after image business graph is first transformed into a generic after image business graph. Another transformation is performed transforming the generic after image business graph into a second after image business graph, using delta information from another enterprise information system is used to create a delta business graph. A final transformation is performed to convert the delta business graph into a generic delta business graph.

Abstract: A method is provided for using a templated pattern to define part types on a web service definition language (WSDL) interface. Applying the templated pattern enables peer services to define a transparent contract between specific WSDL part types. The templated pattern is used to wrap the original business object with the enriched business graph schema. The templated business graph is created by extending the business graph complex type that is provided by the business object framework runtime and adding an element delegating to the original business object.

Abstract: Schema information is provided with transmission of a data object. When a data object is converted to a transmission format, schema information for the object type is added to the transmission format element. The unmarshaling code uses the schema information to update a schema registry at the receiving end. The schema registry is used as a tool for converting the transmission format element back to the data element. The next time an object of that object type is sent to the recipient, the schema information is not added to the transmission format element.

Abstract: Schema information is provided with transmission of a data object. When a data object is converted to a transmission format, schema information for the object type is added to the transmission format element. The unmarshalling code uses the schema information to update a schema registry at the receiving end. The schema registry may then be used as a tool for converting the transmission format element back to the data element. The next time an object of that object type is sent to the recipient, the schema information is not added to the transmission format element.

Abstract: A method, system, and computer usable code is provided for using a templated pattern to define part types on a web service definition language (WSDL) interface. Applying the templated pattern enables peer services to define a transparent contract between specific WSDL part types. The templated pattern is used to wrap the original business object with the enriched business graph schema. The templated business graph is created by extending the business graph complex type that is provided by the business object framework runtime and adding an element delegating to the original business object.

Abstract: Provided is a method, system, and program for providing an object discovery agent (ODA) client. There is one object discovery agent (ODA) client and at least one ODA, wherein each ODA is associated with one application and includes: (i) application programming interfaces (APIs) to communicate with the associated application to discover definition information on objects maintained by the application and (ii) code to communicate with the ODA client. The ODA client communicates with one of the at least one ODA to cause the ODA to gather definition information on at least one object used by one application. The gathered object definition information is provided to an integration server to integrate the object in an environment including heterogeneous objects from different applications.

Abstract: Provided is a method, system, and program for providing an object discovery agent (ODA) client. There is one object discovery agent (ODA) client and at least one ODA, wherein each ODA is associated with one application and includes: (i) application programming interfaces (APIs) to communicate with the associated application to discover definition information on objects maintained by the application and (ii) code to communicate with the ODA client. The ODA client communicates with one of the at least one ODA to cause the ODA to gather definition information on at least one object used by one application. The gathered object definition information is provided to an integration server to integrate the object in an environment including heterogeneous objects from different applications.

Abstract: When a data object is sent from one application to another, the marshaling code includes type information with transmission of the data object. When the data object is converted to the transmission format, type information for the data object is added to the transmission format element. The unmarshaling code uses the type information to obtain schema information for converting the transmission format element back to the data element.

Abstract: An apparatus, system, and method are disclosed for synchronizing change histories in enterprise applications. An access module accesses a source data object container provided by a source EIS and a destination data object container provided by a destination EIS. The source data object container comprises a source change history, and the destination data object container comprises a destination change history. A transformation module may retrieve a transformation definition from an integration server, or the transformation definition may be provided in some other fashion. An interpretation module interprets the transformation definition to determine the relationships between the source data object container and the destination data object container. A copy module may copy select portions of the source change history to the destination change history.

Abstract: An apparatus, system, and method are disclosed for automatically maintaining identity relationships among disparate enterprise information systems. The apparatus comprises a synchronization hub comprising an identity relationship repository, a relationship service module, a consistency module, and an adjustment module. The relationship service is configured to access a target relationship entry using a unique key from a source business object, wherein the source business object is representative of changes made in a source enterprise information system. The various components and modules of the synchronization hub cooperate to determine identity relationships that need updating and to propagate identity relationship changes to one or more destination enterprise information servers.

Abstract: A mechanism is provided for converting after image data into a delta level change. An after image business graph is first transformed into a generic after image business graph. Another transformation is performed transforming the generic after image business graph into a second after image business graph, using delta information from another enterprise information system is used to create a delta business graph. A final transformation is performed to convert the delta business graph into a generic delta business graph.

Abstract: A computer implemented method, an apparatus and computer instruction are provided for deployment of roles. Aspects of the present invention allow user to define in a schema a definition of a relationship that comprises a set of roles participating in the relationship. Each role in the set of roles is defined as an inlined role or an independent role. After the schema is processed, aspects of the present invention determine if the role in the set of roles is an inlined role or an independent role based on the definition of the relationship, deploy the relationship and the role as a single entity if the role is an inlined role, and deploy the relationship and the role as separate entities if the role is an independent role.

Abstract: A method, system, and computer usable code is provided for using a templated pattern to define part types on a web service definition language (WSDL) interface. Applying the templated pattern enables peer services to define a transparent contract between specific WSDL part types. The templated pattern is used to wrap the original business object with the enriched business graph schema. The templated business graph is created by extending the business graph complex type that is provided by the business object framework runtime and adding an element delegating to the original business object.