Abstract: A method and apparatus are disclosed for discovering and selecting faults where more than one programming model is involved. The present invention enables selection of faults and the mappings necessary to handle exceptions across multiple code environments.

Abstract: In one aspect of the present invention a framework is presented for the generation and execution of code performing conversion to and from an arbitrary native or “wire” data format. The code facilitates a business application using a service provided by a service implementation in accordance with a native language of the implementation which may be different from the language of the business application. The main components of the framework include a model of the information necessary for the formatting of data which may be represented through the extensions to WSDL; a tool time support environment providing structured support for the generation of format handlers; and runtime support for the generated format handlers. In an alternative to this static invocation model, a dynamic usage scenario provides for invocation of format handlers dynamically obtained from a format handler factory. In both cases, the runtime uses a lazy approach to the conversion to and from the native format for improved performance.

Abstract: Presented herein is a method and computer program product for generating, in an Integrated Development Environment (IDE), a software application that is designed to exploit services of multiple Enterprise Information Systems (EISs). In one embodiment, the method associates each of multiple Resource and Tooling Adapters (RTAs) with a selected one of multiple Enterprise Information Services (EISs). A software application, which uses multiple EISs and is developed through development facilities of an Integrated Development Environment (IDE), is identified. Source code that is used to access the services of the multiple EISs is generated by plugging multiple corresponding RTAs into the IDE. Using plugged-in multiple corresponding RTAs in the IDE, data is provided, to the IDE, that describes services available from the multiple EISs to the software application.

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: Embodiments of the present invention provide a connector adapted to convey data between a first application and a second application (or application components). The applications may be hosted by different computer systems interconnected by a communications link or network. The connector in addition to being interposed between the first and second application is adapted to communicate with one or more protocol handlers (wherein a protocol handler provides the formatting of data to conform with a specific protocol—e.g., HTTP, SOAP, etc.). The protocol handlers configure the connector thus allowing data received by the connector from the first application to be serviced (e.g., formatted) to conform to the protocol provided by the protocol handler which has been “plugged” into the connector.

Abstract: The invention relates to Web Services Invocation Framework (WSIF) operations. “interactionSpec” and “connectionSpec” are Java 2 Enterprise Edition Java Connector Architecture interfaces. Their properties are exposed as data in WSIF operations. Thus WSIF support for the Java 2 Enterprise Edition Java Connector Architecture is made functionally more complete.

Abstract: The invention relates to Web Services Invocation Framework (WSIF) operations. “interactionSpec” and “connectionSpec” are Java 2 Enterprise Edition Java Connector Architecture interfaces. Their properties are exposed as data in WSIF operations. Thus WSIF support for the Java 2 Enterprise Edition Java Connector Architecture is made functionally more complete.

Abstract: Mapping of a first native data type instance to a second native data type instance is performed in three stages: the first native data type instance is converted into a first programming language and platform independent representation conforming to a first schema capable of defining base and derived data types; the first programming language and platform independent representation is transformed into a second programming language and platform independent representation conforming to a second schema capable of defining base and derived data types; and the second programming language and platform independent representation is converted into the second native data type instance. The programming language and platform independent representations may be event-based extensible Markup Language (XML) representations implemented according to the Simple API for XML (SAX). The transformation may be governed by an extensible Stylesheet Language Transform (XSLT) stylesheet.

Abstract: Automated interface generation for computer programs operating in different environments is provided. An automated interface generation system, method, computer program product and article of manufacture is provided comprising an import utility and a runtime environment. The import utility imports a COBOL IMS transaction source file, parses the specified input and output message records, and generates an application programming interface. The application programming interface operates with the runtime environment to take the data values from the language of a different environment and translate them to a formatted IMS input message. This format is derived from the definition of the input message record in the COBOL IMS transaction source file. After the IMS transaction has executed, the resulting IMS output message is translated back to the data values of the language of the different environment, said values including the results of the transaction.

Abstract: The invention relates to Web Services Invocation Framework (WSIF) operations. “interactionSpec” and “connectionSpec” are Java 2 Enterprise Edition Java Connector Architecture interfaces. Their properties are exposed as data in WSIF operations. Thus WSIF support for the Java 2 Enterprise Edition Java Connector Architecture is made functionally more complete.

Abstract: Embodiments of the present invention provide a connector adapted to convey data between a first application and a second application (or application components). The applications may be hosted by different computer systems interconnected by a communications link or network. The connector in addition to being interposed between the first and second application is adapted to communicate with one or more protocol handlers (wherein a protocol handler provides the formatting of data to conform with a specific protocol-e.g., HTTP, SOAP, etc.). The protocol handlers configure the connector thus allowing data received by the connector from the first application to be serviced (e.g., formatted) to conform to the protocol provided by the protocol handler which has been “plugged” into the connector.

Abstract: The present invention discloses a computer server having a generic interface for interacting with a variety of middleware products and application programming interfaces. The proposed architecture of the interface is such that knowledge of existing middleware systems is not needed to develop or modify server applications.

Abstract: A development model for architecting enterprise systems presents a service-oriented approach which leverages open standards to represent virtually all software assets as services including legacy applications, packaged applications, J2EE components or web services. This approach provides developers with a standard way of representing and interacting with parts of a business application without having to spend time working with unique interfaces and low-level APIs. Furthermore, individual business application components become building blocks that can be reused in developing other applications. Using the service-oriented approach to integration in accordance with the present invention reduces the complexity, cost, and risk of integration by providing a single, simple architectural framework based on Web Services in which to build, deploy, and manage application functionality.

Abstract: Mapping of a first native data type instance to a second native data type instance is performed in three stages: the first native data type instance is converted into a first programming language and platform independent representation conforming to a first schema capable of defining base and derived data types; the first programming language and platform independent representation is transformed into a second programming language and platform independent representation conforming to a second schema capable of defining base and derived data types; and the second programming language and platform independent representation is converted into the second native data type instance. The programming language and platform independent representations may be event-based extensible Markup Language (XML) representations implemented according to the Simple API for XML (SAX). The transformation may be governed by an extensible Stylesheet Language Transform (XSLT) stylesheet.

Abstract: In one aspect of the present invention a framework is presented for the generation and execution of code performing conversion to and from an arbitrary native or “wire” data format. The code facilitates a business application using a service provided by a service implementation in accordance with a native language of the implementation which may be different from the language of the business application. The main components of the framework include a model of the information necessary for the formatting of data which may be represented through the extensions to WSDL; a tool time support environment providing structured support for the generation of format handlers; and runtime support for the generated format handlers. In an alternative to this static invocation model, a dynamic usage scenario provides for invocation of format handlers dynamically obtained from a format handler factory.

Abstract: The ToolFrame is a code generation tooling framework. Its components form the basis of a generic tooling framework that provides a structured, consistent, and flexible method for developing tools. The ToolFrame separates functionality into components to emphasize substitution of components through common interfaces. This separation is furthered by a common complex object called Resource, used to represent any type of information shared between components.

Abstract: A transformation Web service description describes a Web service capable of receiving a message having a format compatible with a format of a message associated with a first Web service and transforming the message to a transformed message compatible with an input message format for a second Web service. The Web service description may be expressed in the Web services Description Language (WSDL). The Web service description includes a transformation description describing the transformation to be performed. The transformation description may be a programming language and platform neutral description such as an eXtensible Stylesheet Language Transform (XSLT) stylesheet and may be included within a transformer binding which extends WSDL. To support transformations involving multiple inputs and outputs, multiple input and/or output messages may be aggregated into a single multi-part input or output message, where each part has an attribute which references one of the multiple messages to be aggregated.

Abstract: In one aspect of the present invention a resource and tooling adapter (RTA), a new kind of resource adapter, interacts, in the development process, with an integrated development environment (IDE). The RTA, responsive to a request from the IDE, provides identification of the services provided by the EIS. Additionally, the RTA provides data to the IDE describing how to access or invoke those services. Utilizing the data (describing the services and how to use those services of an EIS) an IDE is able to generate a business application designed to exploit the services of the EIS. In a further aspect of the present invention, the RTA (previously employed by an IDE to develop a business application) also provides runtime support to enable communication between the business application and the selected EIS.

Abstract: The present invention provides an HTTP connector implementation to be used by disparate computer systems to communicate with each other over the World Wide Web. In particular, the present invention is directed to business to business communications and meets the specifications of the J2EE Connector Architecture. The present invention provides an HTTP interface that may easily be adapted by existing applications while at the same time shielding the developer from the low level details of the HTTP.