BUSINESS PROCESS EXECUTION LANGUAGE (BPEL) APPLICATION GENERATOR FOR LEGACY INTERFACES
First Claim
1. A method for capturing and converting legacy applications into a Business Process Execution Language (BPEL) model supporting a Service Oriented Architecture (SOA), the method comprising:
- identifying a business entry type, a name, and a plurality of variables of the legacy applications;
defining a package and a plurality of file names used by the legacy applications;
flagging a starting panel to enter into the BPEL model;
starting a recorder for recording the legacy applications;
entering data on a screen of a data processing device running the legacy applications;
mapping the plurality of variables of the legacy applications to a plurality of fields and to a plurality of sub-fields of the BPEL model;
identifying and highlighting the plurality of fields and the plurality of sub-fields;
identifying one or more fields out of the plurality of fields to differentiate a request from a plurality of requests;
identifying and generating partner links via a submit button located on the screen of the data processing device;
identifying additional input variables of the legacy applications;
mapping the additional input variables of the legacy applications to arbitrary variables;
highlighting one or more of the plurality of fields that indicate one or more error conditions;
generating a fault handler for each of the one or more error conditions;
repeating the previous steps until an end result is generated;
ending the recorder;
choosing one or more variables to be returned as a result of processing the legacy applications;
flagging the end result;
saving the end result;
generating an ear (Enterprise Archive) file that packages business process resource files;
generating resource files describing a sequence of invokes that represent the legacy applications as a first set of SOA services having a plurality of variables; and
generating a second set of SOA services associated with assigns for mapping the plurality of variables of the first set of SOA services to the second set of SOA services.
5 Assignments
0 Petitions
Accused Products
Abstract
A method for capturing and converting legacy applications into a Business Process Execution Language (BPEL) model supporting a Service Oriented Architecture (SOA), the method comprising: starting a recorder for recording the legacy applications; mapping the plurality of variables of the legacy applications to a plurality of fields and to a plurality of sub-fields of the BPEL model; highlighting and identifying the plurality of fields and the plurality of sub-fields; identifying and generating partner links; identifying additional input variables of the legacy applications; mapping the additional input variables of the legacy applications to arbitrary variables; repeating the previous steps until an end result is generated; and ending the recorder.
61 Citations
9 Claims
-
1. A method for capturing and converting legacy applications into a Business Process Execution Language (BPEL) model supporting a Service Oriented Architecture (SOA), the method comprising:
-
identifying a business entry type, a name, and a plurality of variables of the legacy applications; defining a package and a plurality of file names used by the legacy applications; flagging a starting panel to enter into the BPEL model; starting a recorder for recording the legacy applications; entering data on a screen of a data processing device running the legacy applications; mapping the plurality of variables of the legacy applications to a plurality of fields and to a plurality of sub-fields of the BPEL model; identifying and highlighting the plurality of fields and the plurality of sub-fields; identifying one or more fields out of the plurality of fields to differentiate a request from a plurality of requests; identifying and generating partner links via a submit button located on the screen of the data processing device; identifying additional input variables of the legacy applications; mapping the additional input variables of the legacy applications to arbitrary variables; highlighting one or more of the plurality of fields that indicate one or more error conditions; generating a fault handler for each of the one or more error conditions; repeating the previous steps until an end result is generated; ending the recorder; choosing one or more variables to be returned as a result of processing the legacy applications; flagging the end result; saving the end result; generating an ear (Enterprise Archive) file that packages business process resource files; generating resource files describing a sequence of invokes that represent the legacy applications as a first set of SOA services having a plurality of variables; and generating a second set of SOA services associated with assigns for mapping the plurality of variables of the first set of SOA services to the second set of SOA services. - View Dependent Claims (2, 3, 4)
-
-
5. A system for capturing and converting legacy applications into a BPEL model supporting a SOA, the system comprising:
-
a network; and a host system in communication with the network, the host system including software to implement a method comprising; identifying a business entry type, a name, and a plurality of variables of the legacy applications; defining a package and a plurality of file names used by the legacy applications; flagging a starting panel to enter into the BPEL model; starting a recorder for recording the legacy applications; entering data on a screen of a data processing device running the legacy applications; mapping the plurality of variables of the legacy applications to a plurality of fields and to a plurality of sub-fields of the BPEL model; identifying and highlighting the plurality of fields and the plurality of sub-fields; identifying one or more fields out of the plurality of fields to differentiate a request from a plurality of requests; identifying and generating partner links via a submit button located on the screen of the data processing device; identifying additional input variables of the legacy applications; mapping the additional input variables of the legacy applications to arbitrary variables; highlighting one or more of the plurality of fields that indicate one or more error conditions; generating a fault handler for each of the one or more error conditions; repeating the previous steps until an end result is generated; ending the recorder; choosing one or more variables to be returned as a result of processing the legacy applications; flagging the end result; saving the end result; generating an ear (Enterprise Archive) file that packages business process resource files; generating resource files describing a sequence of invokes that represent the legacy applications as a first set of SOA services having a plurality of variables; and generating a second set of SOA services associated with assigns for mapping the plurality of variables of the first set of SOA services to the second set of SOA services. - View Dependent Claims (6, 7, 8)
-
-
9. A computer program product for capturing and converting legacy applications into a BPEL model supporting a SOA, the computer program product comprising:
a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising; identifying a business entry type, a name, and a plurality of variables of the legacy applications; defining a package and a plurality of file names used by the legacy applications; flagging a starting panel to enter into the BPEL model; starting a recorder for recording the legacy applications; entering data on a screen of a data processing device running the legacy applications; mapping the plurality of variables of the legacy applications to a plurality of fields and to a plurality of sub-fields of the BPEL model; highlighting the plurality of fields and the plurality of sub-fields; identifying the plurality of fields and the plurality of sub-fields; identifying one or more fields out of the plurality of fields to differentiate a request from a plurality of requests; identifying and generating partner links via a submit button located on the screen of the data processing device; identifying additional input variables of the legacy applications; mapping the additional input variables of the legacy applications to arbitrary variables; highlighting one or more of the plurality of fields that indicate one or more error conditions; generating a fault handler for each of the one or more error conditions; repeating the previous steps until an end result is generated; ending the recorder; choosing one or more variables to be returned as a result of processing the legacy applications; flagging the end result; saving the end result; generating an ear (Enterprise Archive) file that packages business process resource files; generating resource files describing a sequence of invokes that represent the legacy applications as a first set of SOA services having a plurality of variables; and generating a second set of SOA services associated with assigns for mapping the plurality of variables of the first set of SOA services to the second set of SOA services.
Specification