Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
  • G06F8/61—Installation
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/54—Interprogram communication
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/54—Interprogram communication
  • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/20—Software design
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/30—Creation or generation of source code
  • G06F8/36—Software reuse
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/70—Software maintenance or management
  • G06F8/77—Software metrics

Definitions

• Embodiments of the invention are generally related to cloud services, and are particularly related to a system and method for insulating a web interface application from underlying technologies in a cloud-based integration service.
• iPaaS Integration platform as a service
• An iPaaS platform can provide a design time for developers to design, deploy and monitor integration projects.
• these integration projects can be tied to particular runtime engine, and cannot be deployed to a different runtime engine without additional work.
• the abstraction layer can include an application programming interface that exposes a plurality of services to the web interface application, for use in the entire life cycle of an integration project.
• the web interface application is agnostic of the underlying frameworks that persist the integration project, and the runtime engines that are to execute the integration project.
• the application programming interface can persist the integration project in a runtime-engine-neutral format, and can transform the integration project from the runtime-engine-neutral format to a runtime-engine- specific format at deployment time.
• Figure 1 illustrates an integration cloud service in accordance with an embodiment.
• Figure 2 illustrates a system for insulating a Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• Figure 3 further illustrates a system for insulating a web Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• Figure 4 further illustrates a system for insulating a web Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• Figure 5 illustrates a sequence diagram for insulating a web Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• Figure 6 illustrates a method for insulating a web Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• Integration platform as a service, for example, Oracle Integration Cloud
• ICS can provide a cloud-based platform for building and deploying integrations flows that connect applications residing in the cloud or on-premises.
• Figure 1 illustrates an integration cloud service in accordance with an embodiment.
• an ICS 107 can provide a cloud-based integration platform for designing, executing, and managing ICS integration flows.
• the ICS can include a web application 109 and an ICS runtime 1 15 executing on an application server 117 in an enterprise cloud environment (for example, Oracle Public Cloud) 101.
• the web application can provide a design time that exposes a plurality of user interfaces for a developer to design, activate, manage, and monitor an ICS integration flow.
• An activated ICS integration flow can be deployed and executed on the ICS runtime.
• a plurality of application adapters 113 can be provided to simplify the task of configuring connections to a plurality of applications, by handling the underlying complexities of connecting to those applications.
• the applications can include enterprise cloud applications of the ICS vendor (for example, an Oracle RightNow) 105, third-party cloud applications (for example, Salesforce) 103, and on- premises applications 119.
• the ICS can expose simple object access protocol (SOAP) and representational state transfer (REST) endpoints to these applications for use in communicating with these applications.
• SOAP simple object access protocol
• REST representational state transfer
• an ICS integration flow can include a source connection, a target connection, and field mappings between the two connections.
• Each connection can be based on an application adapter, and can include additional information required by the application adapter to communicate with a specific instance of an application.
• an ICS integration flow can be defined in an ICS project, which can include a structured set of artifacts, for example, metada, Java Connector Architecture (JCA) files and web service definition language (WSDL) files.
• An ICS project can be deployed and executed in the ICS runtime, and can be used to integrate cloud applications and on-premises applications.
• an ICS project is an integration project.
• an ICS can include a web Ul application for ICS developers to design ICS projects, and a runtime for executing the projects.
• an ICS project During the life cycle of an ICS project, a developer often needs to use a plurality of interfaces. For example, during the development phase, the developer can perform CRUD (create, read, update, and delete) operations on the project. During the deployment phase, the developer can compile and deploy the project. These operations can be performed in different interfaces. In addition, an ICS project can be developed in a format specific to a particular runtime engine, and cannot be reused for a different runtime engine without additional work.
• CRUD create, read, update, and delete
• the system can provide an abstraction layer that insulates a web interface application from underlying technologies.
• the abstraction layer includes an application programming interface that exposes a plurality of services to the web interface application, for use in the entire life cycle of an integration project.
• the web interface application is agnostic of the underlying frameworks that persist the integration project, and the runtime engines that are to execute the integration project.
• the application programming interface can persist the integration project in a runtime-engine-neutral format, and can transform the integration project from the runtime-engine-neutral format to a runtime-engine-specific format at deployment time.
• the abstraction layer can reside between the web interface application, and one or more runtime engines in the ICS runtime, thereby insulating the ICS web interface layer from the underlying integration technology.
• a plurality of handlers can be provided, each for a particular runtime engine.
• a handler specific to a runtime engine can be used to transform an ICS project from a runtime-engine-neutral format to a format specific to the runtime engine.
• the abstraction layer can be used to generate and validate ICS packages, export and import an ICS project, bootstrap the persistence store with pre-defined ICS project and data, and move ICS data between ICS project instances.
• Figure 2 illustrates a system for insulating a Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• an abstraction layer 209 can include an API that exposes a plurality of functionalities to the web Ul application for use in managing the life cycle of an ICS project.
• Each of the functionalities for example, CRUD (create, read, update and delete) 21 1 , activation 213, and monitoring 215, can be visible on a single interface in the web Ul application.
• the abstraction API can provide a plurality of services using a plurality of classes/objects, for example, a persistence manager 217 and an operation manager 219, to insulate these functionalities from the underlying technologies (for example, persistence frameworks and runtime engines), which can provide flexibility and code reuse when the underlying technologies change.
• a persistence manager 217 and an operation manager 219 to insulate these functionalities from the underlying technologies (for example, persistence frameworks and runtime engines), which can provide flexibility and code reuse when the underlying technologies change.
• the developer can create a plurality of ICS objects (for example, connection objects, and integration flow objects). These objects need to be read, updated or deleted.
• a plurality of persistence frameworks 223 can be plugged into the abstraction layer, and can be used by the operation manager, to perform the CRUD operations without the knowledge of the web Ul application.
• the operation manager provides a set of interfaces that can insulate the exposed functionalities from the persistence framework configured to perform the functionalities.
• the abstraction layer can further include a plurality of project templates (for example, OSB templates), and a project handler 227 that can automatically select a runtime-engine-specific handler (for example, OSB handler), based on a user's selection of a particular runtime to host the ICS project.
• the selected runtime-engine-specific handler can convert the runtime-engine-neutral project retrieved by the operation manger from a persistence store, to a runtime-engine-specific project using one or more project templates 225.
• the operation manager can deploy 233 the runtime-engine-specific project to a particular runtime engine.
• the abstraction API further includes a runtime metrics presenter 221 , to format and display runtime metrics 231 collected by APIs exposed by the ICS runtime.
• the runtime metrics can include numbers of transactions and failed transactions per second for a given ICS integration flow, logging information for each successful invocation, activity stream showing, e.g., during the last 20 records.
• the exposed API by the ICS runtime can also be used to download transaction log files, and to retrieve user-specified requests for a particular type of runtime metrics.
• Figure 3 illustrates a system for insulating a web Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• the web Ul application can provide an interface for an ICS developer to create ICS projects 305, which can be persisted into a persistence store 315 using the pluggable persistence framework in a runtime-engine-neutral format.
• a runtime-engine-neutral ICS project can represent a project structure that is not specific to a particular runtime/integration engine, and can be defined by the web Ul application.
• a runtime-engine-neutral project can include metadata defined in an XML format that represents configuration such as source applications, target applications, integration patterns, and schemas.
• an ICS project class can represent a runtime-engine-neutral format project, and can encapsulate the required metadata.
• An instance of the ICS project class (ICS project artifacts 314) can be stored to the persistence store.
• the persistence manager can perform session management 311 and resource locking/unlocking 313 while an ICS project is being developed.
• the persistence manager can keep tract of the status of each resource (e.g., files and metadata), and prevent a developer from unlocking a resource that another developer locks.
• different persistence frameworks for example, OSB configuration framework, and Oracle Enterprise Repository (OER)
• OSB configuration framework for example, OSB configuration framework, and Oracle Enterprise Repository (OER)
• OER Oracle Enterprise Repository
• Figure 4 further illustrates a system for insulating a web Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• the operation manager can be used to activate an ICS project.
• an ICS project needs to be activated by explicitly performing a "build" action to generate an enterprise archive (EAR) file from the ICS project, selecting the EAR file from a web interface to deploy it, and using a third interface to monitor the deployed project.
• the abstraction layer can combine the EAR file generation, and deployment and monitoring of the ICS project into a single step in a particular interface.
• the Activation button can be placed beside an ICS project name.
• an ICS developer can be prompted to select a particular runtime to deploy the ICS project.
• the operation manager can retrieve 41 1 the runtime-engine-neutral project from the persistence store using the persistence manager, transform the ICS project into a runtime-engine-specific format, generate an EAR file, and invoke APIs exposed by the specific runtime engine, for example Oracle Service Bus runtime engine (OSB) , to deploy the EAR file thereon.
• OSB Oracle Service Bus runtime engine
• the operation manager can invoke the project handler, which can select a runtime-engine-specific handler to transform the project, based on the runtime selected by the ICS developer.
• the persistence manager can pass a runtime-engine-neutral project 415 to the project handler, which can return a runtime-engine-specific project to the operation manager.
• the project manager can deploy 419 the transformed project to a specific runtime engine to execute the project.
• a plurality of runtime-engine-specific handlers can be provided by the abstraction layer, for example, an Oracle Service Bus (OSB) handler 427, and a business execution process language (BPEL) handler 447.
• OSB Oracle Service Bus
• BPEL business execution process language
• the OSB handler can retrieve OSB templates from, e.g., a database, and use the templates and associated metadata to add specifics needed for the ICS project to run on an OSB runtime engine.
• a plurality of methods can be used to transform the ICS project using the retrieved templates and metadata.
• monitoring of the deployed project can be performed through the same user interface where the activation button described above is located.
• the ICS runtime can expose a set of APIs used to display runtime metrics, such as number of transactions and failed transactions per second for a given ICS integration flow, logging information for each successful invocation, activity stream showing, e.g., the last 20 records.
• the exposed API can also be used to download log files for all the transactions, and to receive user-specified requests for a particular type of runtime metrics.
• Figure 5 illustrates a sequence diagram for insulating a web Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• a persistence manager 504 can be invoked to create resources (step 512) using a persistence framework API 505.
• the resource creation can include persist the ICS project files to an underlying database of the persistence framework API.
• a developer can activate (step 515) the ICS project.
• the project activation can cause an operation manager 506 to create packages (step 514) using the persisted resources retrieved from the persistence store.
• the operation manager can receive (step 1)
• the created packages and invoke a project handler 508 to create a transformed project (step 518).
• the operation manager can further invoke a runtime deployment bean 509 to deploy the transformed project (step 521).
• a click on a button to activate the ICS project can perform the steps of retrieving the runtime-engine-neutral project, creating project packages (compiling the project), transforming the project into a runtime-engine-specific project, and deploying the transformed project.
• a monitoring screen can be automatically displayed, wherein requests for runtime metrics (step 526) can be sent to the ICS runtime hosting the deployed project.
• Runtime metrics can be received (step 527) by the monitoring interface, and displayed in various formats (for example, bar charts).
• Figure 6 illustrates a method for insulating a web Ul application from runtime engines in an ICS runtime, in accordance with an embodiment.
• a web Ul application is provided on a computer including a microprocessor, wherein the web Ul application provides a design time for an ICS.
• an abstraction application programming interface is provided, the abstraction API exposing a plurality of services to the web Ul application, for use in designing, deploying and monitoring an ICS project.
• the ICS project is persisted in a runtime-engine-neutral format.
• the ICS project is converted into a format specific to one of the runtime engines in the ICS runtime.
• Embodiments of the present invention may be conveniently implemented using one or more conventional general purpose or specialized digital computer, computing device, machine, or microprocessor, including one or more processors, memory and/or computer readable storage media programmed according to the teachings of the present disclosure. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.
• the present invention includes a computer program product which is a non-transitory storage medium or computer readable medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention.
• the storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Stored Programmes (AREA)

Priority Applications (3)

Applications Claiming Priority (4)

Publications (1)

Family

ID=56148674

Family Applications (1)

Country Status (5)

Families Citing this family (4)

Family Cites Families (30)

• 2016
  • 2016-06-02 US US15/171,908 patent/US10216504B2/en active Active
  • 2016-06-03 EP EP16730612.5A patent/EP3304306A2/en not_active Ceased
  • 2016-06-03 CN CN201680041115.2A patent/CN108139947B/zh active Active
  • 2016-06-03 JP JP2017562992A patent/JP6691554B2/ja active Active
  • 2016-06-03 WO PCT/US2016/035758 patent/WO2016196959A2/en not_active Ceased

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events