Abstract: An apparatus, system, and method are disclosed for supporting service components written in non-native runtime code in a Service Component Architecture (“SCA”). A read module is included to read an implementation type definition having metadata identifying executable code that executes a new implementation type. A receive module is included to detect a dynamic service call to a service component having the new implementation type. The dynamic service call is defined in an SCA message from a calling SCA component. A passing module is included to pass the dynamic service call to a predefined SCA implementation handler associated with the new implementation type. The SCA implementation handler includes native runtime code and implementation logic for executing the dynamic service call by executing non-native runtime code that returns a result to the SCA implementation handler. A packaging module packages the result in an SCA return message to the calling SCA component.

Abstract: An apparatus and system are disclosed for implementing service qualifiers that define on-demand management requirements for a loosely coupled software service in a service component architecture (SCA) for an integration server by associating a service qualifier with one or more of an SCA service reference, an SCA wire, an SCA interface, or an SCA implementation based on an SCA component definition, requiring the integration server to augment an implementation execution for the SCA service to honor the service qualifier; and accepting user modification and definition of declarative service qualifiers. By allowing the association of service qualifiers with SCA service references, SCA wires, SCA interfaces, and SCA implementations, additional quality of service with which components are executed can be maintained.

Abstract: Provided are a method, system, and article of manufacture, wherein a client component including at least one client interface is provided. Also provided is a target component including at least one service interface, wherein the at least one client interface is capable of matching the at least one service interface. A service interface implementation corresponding to the at least one service interface is provided, wherein the service interface implementation is a dynamic service interface implementation. The dynamic service interface implementation is executed to allow access to the client component to a service provided by the target component.

Abstract: An apparatus, system, and method are disclosed for accessing enterprise information system (EIS) resources in a service component architecture (SCA) for an integration server by selectively binding a service import to a low-level EIS resource adapter (RA) resource of an EIS service provider in response to a declarative binding definition, selectively binding a service import to an EIS service of the EIS service provider in response to a declarative binding definition, and selectively binding a service import to one or more EIS resources through an EIS service mapping configured to transform a service request from the service component client to satisfy an interface pattern of the EIS service provider. By allowing access to resources at different levels and allowing mappings of resources, the requirements of service clients can be met.

Abstract: Provided are a method, system, and program for generating asynchronous interfaces and methods from synchronous interfaces and methods receiving a synchronous interface to a target component having a synchronous method used by a client component to synchronously invoke the target component. An asynchronous interface is generated for the synchronous interface of the target component. An asynchronous method is generated for the generated asynchronous interface having arguments to invoke the target component, wherein the client calls the generated asynchronous method to cause an asynchronous execution of the synchronous method.

Abstract: Provided are a method, system, and program for matching client interfaces with service interfaces. A client component includes at least one client interface and a target component includes at least one service interface. A data structure for the client component associates at least one client interface in the client component with one target component. For each client interface indicated in the data structure, a determination is made as whether there is one service interface in the target component associated with the client interface that is compatible with the client interface.

Abstract: A method and system for incrementally processing program annotations is provided. A source model, a doclet model and a semantic model are used to represent and transform annotations incrementally. The source model represents actual types, fields, and methods that contain annotations. The doclet model includes doclet objects representing tags and attributes for a type, field, and method for a given namespace. Tag handlers registered for the given namespace detect changes in annotations and create or update doclet objects based on the changes. Changes in the doclet model are then transformed into the semantic model and may be persisted for restoration.

Abstract: An apparatus, system, and method are disclosed for accessing enterprise information system (EIS) resources in a service component architecture (SCA) for an integration server by selectively binding a service import to a low-level EIS resource adapter (RA) resource of an EIS service provider in response to a declarative binding definition, selectively binding a service import to an EIS service of the EIS service provider in response to a declarative binding definition, and selectively binding a service import to one or more EIS resources through an EIS service mapping configured to transform a service request from the service component client to satisfy an interface pattern of the EIS service provider. By allowing access to resources at different levels and allowing mappings of resources, the requirements of service clients can be met.

Abstract: An apparatus, system, and method are disclosed for supporting service components written in non-native runtime code in a Service Component Architecture (“SCA”). A read module is included to read an implementation type definition having metadata identifying executable code that executes a new implementation type. A receive module is included to detect a dynamic service call to a service component having the new implementation type. The dynamic service call is defined in an SCA message from a calling SCA component. A passing module is included to pass the dynamic service call to a predefined SCA implementation handler associated with the new implementation type. The SCA implementation handler includes native runtime code and implementation logic for executing the dynamic service call by executing non-native runtime code that returns a result to the SCA implementation handler. A packaging module packages the result in an SCA return message to the calling SCA component.

Abstract: An apparatus, system, and method are disclosed for implementing service qualifiers that define on-demand management requirements for a loosely coupled, platform independent software service in a service component architecture (SCA) for an integration server by associating a service qualifier with one or more of an SCA service reference, an SCA wire, an SCA interface, or an SCA implementation based on an SCA component definition, requiring the integration server to augment an implementation execution for the SCA service to honor the service qualifier; and accepting user modification and definition of declarative service qualifiers. By allowing the association of service qualifiers with SCA service references, SCA wires, SCA interfaces, and SCA implementations, additional quality of service with which components are executed can be maintained.

Abstract: A program product and system are disclosed for receiving a transport message from an external service component by way of an external transport protocol. The transport message includes both primary data and context data. Once received, the primary data and context data are extracted from the transport message and translated into a format required by an SCA message. The primary data is then inserted into a body of the SCA message and the context data is implicitly inserted into a transmit header of the SCA message. The transmit header of the SCA message uses a universal format for carrying context data received over various different external transport protocols.