\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={An approach for exposing legacy applications for integration in modern enterprise business processes},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2011-05-19 (revised: 19 May 2011)}
\def\TheID{\makeatother }
\def\TheDate{2011-05-19}
\title{An approach for exposing legacy applications for integration in modern enterprise business processes}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

\renewcommand\Authands{ and }

\date{\small \em Received: 19 April 2011 Accepted: 9 May 2011 Published: 19 May 2011}

\maketitle


\begin{abstract}
        


Organizations have legacy software applications and systems, which are valuable assets and still critical to their current business operations. One of the key challenges for today's enterprises is how to effectively and efficiently integrate these legacy assets with other. internal and external applications and business processes. Modernizing legacy systems using SOA may help an organization to meet the increasing demands of the business processes integration while maintaining its large investment in legacy systems. SOA bridges the gap between business processes and technology resulting in improved reuse of existing applications and interoperability of desperate applications. Sometimes it is required to integrate legacy system with other application in a short span of time. As per the business requirements although SOA may address the solution, but it is very difficult to integrate due to several issues in service identification and mapping in legacy application and business processes.In this paper an approach is proposed for participation and alignment of legacy applications in the enterprise business processes in a short span of time with the help of business process modeling and SOA, incorporating both Top down and bottom up approach together. As a case study, the paper describes the exposure of a prototype legacy banking application for participation in a service-oriented architecture.The paper also proposes a novel way of determining the key business logic and resources embedded in a legacy C/C++ application with a reverse engineering approach so that the SOA mapping is automated and the constraints like memory and processing can be analyzed.

\end{abstract}


\keywords{Legacy Applications, W eb services, Integration, Service oriented architecture, business process modeling.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{INTRODUCTION}]{INTRODUCTION}\par
usiness organizations have a large investment in software written in legacy programming languages and architecture. Today, most of the organizations run systems that have been developed a long time ago and are still adapted and maintained to meet current needs \hyperref[b0]{[1]}. Approaches used in legacy systems sometimes differ considerably from today's modern paradigms. Adapting legacy software systems to new requirements also requires their migration and integration with new technologies and applications.\par
A Legacy Information System can be defined as "any information system that significantly resists modification and evolution" \hyperref[b0]{[1]}. These Information Systems pose considerable problems including brittleness, inflexibility, isolation, non-extensibility, lack of openness on the enterprise IT infrastructure. They significantly resist further modification and evolution. Legacy systems were designed for internal, enterprise wide usage while today's enterprise demands for inter enterprise communications and support for agile business processes.\par
There are various methods proposed including supplementing or replacing restrictive legacy applications and technology with newer, open standards-based applications and technologies, but still retaining existing business functions \hyperref[b1]{[2]}. Legacy renovation is an expensive task. As the requests for modifications, new development and integration accumulate, it is very difficult to keep pace and enable a more agile enterprise. So it is advantageous to integrate legacy application with new applications while retaining the business logic intact.\par
SOA models the enterprise business workflow as a collection of business services, these services can be easily Reused and integrated in the organization to address the application requirements \hyperref[b2]{[3]}  \hyperref[b3]{[4]}. Rather than developing from the ground up every time a change is needed, new assets can be created easily from existing services, saving time and money  {\ref [5]}. The most important advantage of SOA is to provide a data bridge between incompatible and desperate technologies \hyperref[b4]{[6]}.\par
BPM is a set of technologies and standards for the design, execution, and administration and monitoring of complex, automated business processes BPM provides the facility to monitor, analyze, control and improve the execution of these processes in real time \hyperref[b7]{[7]}. Existing Web Services can be integrated as the counterparts of steps in business processes. Examples are credit verification in an on-line order process \hyperref[b8]{[8]}.\par
Several approaches for Legacy application integration and migration towards Service oriented architecture have been proposed in the past but they B ©2011 Global Journals Inc. (US) include difficulties in identifying candidate services from legacy application and their alignment with the organizational business processes requirements. Wrapping functions of legacy systems for exposing as web services may be a fast way for migration towards SOA, However the services provided are technologyoriented and do not fully address business goal or scenario, which might lead to the services not being fully utilized as per the business goals. The top-down approaches analyze existing business processes in order to identify adequate services but services are business oriented and may failed to get the needed functionality in legacy applications.\par
Our proposed method uses BPM and SOA together in order to make legacy participation in the enterprise business processes by means of exposing and orchestrating services. We used both top-down BPM driven and bottom up SOA driven service identification mechanism along with automated discovery of business logic in legacy codes to better align legacy application with business needs.\par
The reminder of the paper is organized as follows: Section 2 provides background information needed to understand the paper, Section 3 presents the proposed approach for legacy service exposure and participation in enterprise business processes with a case scenario, section 4 describes Discussion of result and historical approaches for legacy system migration and integration. We conclude with summary and future directions in section 5. 
\section[{II.}]{II.} 
\section[{BACKGROUND INFORMATION}]{BACKGROUND INFORMATION}\par
An organization has a collection of interrelated business processes, which consist of a series of activities, jointly represent a business goal. For instance an order process in a B2B environment includes several activities networked with each other to complete the order process business goal. These business processes may have their span in several desperate applications in the enterprise and beyond.\par
The ''service'' is an application logic or underlying computing resource with an abstraction of the underlying implementation \hyperref[b2]{[3]}, that is exposed through an interface and which can be invoked over a network with standard protocols \hyperref[b9]{[9]}. The most important application of SOA is to align the services to the business requirements and to facilitate reusability of existing services connecting the various operational systems that automate an enterprise's business processes \hyperref[b10]{[10]}.\par
Bottom-up approaches examine legacy systems and standard software for the identification of services. The bottom-up approach analyses the existing application for all available functions that can be exposed as a web service. With a bottom-up approach the definition of services originates in the domain of the application \hyperref[b12]{[11]}. This approach results in a large number of available functions which can be exposed as services but does not tell anything about their usability. In bottom-up approach Services are discovered, rather than defined as requirements, therefore it tends to lead to poor business services as it preserves the current solution instead of addressing business needs.\par
The top-down approaches analyze existing business processes in order to identify adequate services. This approach looks at the processes in the business domain, decomposes them into sub process/tasks/functions until 'logical units of work' are defined, which we call services. The decomposition of the process in itself is not enough to discover services, because we will have to convert the 'candidate-service' into a real-world executable and discoverable service. This means we have to compare the functionality of the service with the available infrastructure but it does not reach deep into the architecture and implementation domain.\par
By combining these two approaches together we may get the best of both eliminating the shortcomings of each one and integration with the current application infrastructure and readiness for the business needs we are looking for. Therefore, a hybrid approach combining both methods is applied in order to minimize the problems associated with these approaches \hyperref[b13]{[12]} \hyperref[b14]{[13]}.The hybrid meet-in-the middle approach combines top-down and bottom-up techniques in order to identify services that better correspond to both the business requirements and the existing systems \hyperref[b15]{[14]}. It provides a compromise between the top-down and bottom-up techniques that eliminates the most significant disadvantages. We proposed a meet in the middle approach with automatic discovery of prospective services in the legacy application for integration in business processes. 
\section[{III.}]{III.} 
\section[{PROPOSED APPROACH}]{PROPOSED APPROACH}\par
The proposed approach is a combined meet in the middle approach consists of BPM and SOA along with the reverse engineering of legacy application in order to identify the candidate services and their participation in the enterprise business processes. It eliminates the disadvantages of failure in getting the needed functionality in legacy applications and lengthy time of top down approach and non-business orientation of bottom up approach. Basically, we are proposing consolidated approach that provides guidance on the derivation of both business services and supporting software services to achieve a close business and IT alignment. The proposed method is influenced by meet in the middle approach by Inaganti and Behera with some improvements by minimizing the problem in finding of candidate service in legacy application \hyperref[b16]{[15]}.\par
This approach requires a comprehensive analysis of the legacy application and not just the mapping .In this paper we also presented a reverse engineering approach to extract the information of the legacy application through resource extraction from the application along to generate and publish the service.\par
The proposed technique can be summarized as a methodology for mapping legacy application resources to modern enterprise environment by BPM and SOA with the help of Reverse Engineering to facilitate the identification and extraction of the key business logic from Legacy application and alignment with business requirements. Figure \hyperref[fig_0]{1} shows the block diagram of proposed method. As an example scenario, here we introduced a prototype legacy banking application developed in C++. The Application is a monolithic standalone C++ application with no external interface for communication with other applications. The application stores the data in flat file system and provides various inbuilt functionalities like opening an account, deposit money, withdraw money, get balance, viewing of transactions and various reports. One can interact with it only through application GUI which is inbuilt in the code.\par
We assume that there are certain situations arises due to business needs, in which above application is required to be integrate with some other modern applications and business processes. As stated earlier in the paper, it is not viable to replace or rewrite the legacy application with new code. As the legacy application is standalone and the logic is embedded deep in the form of functions, it is very difficult to handle this situation. Our approach resolves the problem without rewriting the legacy code and without interrupting the operation or maintenance of the legacy system.\par
We presented a business process of ATM here. The ATM process resembles the new business requirement and we have to address it by using core business logic of legacy application. The ATM application will be a thin client with only GUI. The ATM GUI will provide only the user interface and the orchestrator takes care of proper sequencing of operations and calling of web services from legacy application. Various new business conditions and constraints, which are not present in legacy application may be addressed with the orchestrator, for example prohibiting withdraw operation in case of insufficient balance or not allowing a certain transaction if the number of transaction exceeds, without rewriting of the core component of the legacy application. The methodology is mentioned in following steps. Analyze the Core Business process.\par
In the first step, it is necessary to analyze functional domain of business process and understand the business requirements. During the initial analysis phase, basic decisions regarding identifying the most important functions of the domain and showing their interrelationships is identified. The business structure and the functions of the business process are specified \hyperref[b17]{[16]}. A business process reveals how an individual process activity is linked with another in order to achieve a business objective. We have to identify the start and end events of a particular business activity, human interactions with the process, automated activities and links with the other applications and organization's processes. This step results in a core coarse grained business process. This analysis results in the development of the "to-be" process model that an SOA solution is intended to implement \hyperref[b8]{[8]}.\par
In the context of our scenario we analyzes how a user will interact with ATM, how the business process will progress with the user interaction. This step results in the use case of ATM process, actors, activities and the flow of business.\par
ii. 
\section[{Model the core business processes}]{Model the core business processes}\par
In this step we design the core business process found in previous step into a graphical model using a BPM modeler, as in our case Intalio \hyperref[b7]{[7]}. At first, the business process is modeled at a high level where activities in the Business Process Diagram usually aggregate sub processes, which are graphically evaluated in another sub process BPM diagram. A [+] sign inside an activity denotes a process that can be decomposed into sub-processes \hyperref[b18]{[17]}. We marked each task which requests an external service as service task. One of the purposes of the process model is to define process execution and to create the BPMN notation for this purpose.\par
The BPMN defines both the graphical notation and the semantics of a Business Process Diagram, We model the diagram with core elements of a BPD which comprises Flow Activities, Tasks represented by a rounded-corner rectangle which is a generic term for work that has to be performed, Events which are diagrammed as a circle, Gateway Objects represented by a diamond symbol which are used to control the divergence and convergence of a sequential flow. By means of these basic Flow Objects. The core process contains at least one POOL which is executable and can be deployed on orchestration Engine.\par
The core business process acts as an orchestrator which will direct and invokes the various Web services from legacy and other third party applications to form and execute a complete business activity \hyperref[b19]{[18]}.\par
iii. 
\section[{Business Process refinement}]{Business Process refinement}\par
In this step we perform decomposition or refinement of sub processes of core BPM Diagram into elementary or atomic business functions. Business process refinement identifies service tasks, message activities, and events and actions in the sub process \hyperref[b12]{[11]}. When the business process is subdivided into sub-processes or decomposed into granular activities the lowest level tasks will consist of small, cohesive "logical units of work", that are supported by the functionality offered by distinct services. It results in discovery of elementary business functions which can be addressed by web services in the application domain \hyperref[b20]{[19]}. Delegating functionality into sub business processes prevents business processes from becoming overly large, complex and difficult to maintain. The refinement can be seen in authorization process diagram.\par
After refinement of sub processes the next step is to find out the Service Tasks which provide some sort of service which could be calling a Web service or an automated application. We will find the task which will call the legacy and other web services process. This service tasks will call atomic (single) web service interfaces of legacy application.\par
In the case of authorization sub process the call authorize task invokes the authorize function of legacy application as shown in yellow color in figure  {\ref 2}. 
\section[{c) Existing asset analysis and Service identification in Legacy Application}]{c) Existing asset analysis and Service identification in Legacy Application}\par
The purpose of this step is to identify assets in the legacy application i.e. business logic and legacy functionality which are capable of supporting the realization of services that meet business needs. The focus is on existing assets that play a role in business processes 14]. We initially perform a coarse-grained mapping of business processes and process activities to the portfolio of existing applications and application interfaces. Later in the specification, we perform a more fine-grained mapping, including message specification. We also identify various system resources so that the performance can be measured. i. 
\section[{Component identification in legacy application}]{Component identification in legacy application}\par
Service identification On the one hand, it is to determine what business functionalities should be provided by the target service in the application domain. On the other hand, the business functionalities embedded in the legacy system should be identified in order to be reused in the target service \hyperref[b21]{[20]}. In this step the legacy application will be reverse engineered and we will find the various resources and embedded business logic to be exposed as web services by adopting bottom up approach. The analysis reveals the reuse potential of existing legacy components. The results of this step include information on system architecture, system components, infrastructure details and interfaces.\par
The proposed work identifies that this is a tedious process and the complexity grows with the line of code that reflects the business logic. Therefore a summary of the business logic present in the code is of extreme important. Here it is performed by a automatic reverse engineering tool. The working description of the tool is as given below.\par
First the tool Scans the program and tokenizes the program. Thereafter it removes the comments and blank sections. It Extracts the function definitions and other resources using following logic:-1. Check if there is a "(" token in the line or not If so, extract the previous token ( which can be function name or a predefined function or key words like if, for and so on) 2. Check if the token is a key word or not. If not, scan till the end and look for a ";" if it is not there, scan for another token appeared before the current token with space separation. 3. If the previous token is a key word (which reflects the return type) then marks the current line as the function definition. Extract the arguments and return types.\par
An approach for exposing legacy applications for integration in modern enterprise business processes ©2011 
\section[{Identify the point of functionality in legacy application}]{Identify the point of functionality in legacy application}\par
In the previous step we found the information about application resources and various functions present in the Legacy application through reverse engineering. Now we identify the points of functionality of the legacy application that may be useful to implement the needed web services to interact with service task in the Orchestrator \hyperref[b16]{[15]}. In the output of automated tool we find the independent functions calls so that it can be used to designate or make as a point of functionality, it means, among several functions we found the one that contains the functionality of interest for service tasks found in top down approach. For example found\textunderscore account function may be used to make authorize function wrapper that can be used as point of functionality and can be exposed as web service and mapped with service task.\par
iii.\par
Exposure of identified functions as web service.\par
The functions identified in previous step as the point of functionality are now exposed as web services \hyperref[b20]{[19]}. The Service interface defines the types of messages and the message exchange patterns that are involved in interacting with the service, together with any conditions implied by those message.. The definition of functions which has to be called by service task has been written in a single header file test.h. The header file guides the GSOAP tool to generate stubs for needed web services. Now we write the web service module by using identified functions of previous step and with the help of GSOAP supporting files. All the exposed web services can be called through the WSDL Interface and the Service end point URL \hyperref[b21]{[20]}. WSDL describes the operations that a service can support, and the parameters each operation accepts and returns. End point URL serves as a service provider. The application web service will provide the response to service task upon calling with appropriate parameters. Figure \hyperref[fig_3]{4} describes the wsdl portion for input and output parameter for Authorize operation. The service matching activity maps the service task to corresponding atomic web service in the application layer. Each atomic service task exactly maps single web service \hyperref[b16]{[15]}. There may be some situation in which a service task will be divided in more than one service task and it may comprised of more than one point of functionality. We will map the service accordingly, for example the fund transfer service task will be associated to two services i.e. deposit and withdraw. Several service task may be associated to same service, for example a withdraw service may be associated to both withdraw and fund transfer service tasks. These concepts can be seen in Fig \hyperref[fig_5]{1 and Fig 6}.\par
At the end of this step we complete the matching and mapping of all the service task and corresponding web services with each other. 
\section[{e) Service realization and orchestration}]{e) Service realization and orchestration}\par
All the web services exposed from legacy system were atomic and asynchronous, that means there is no such execution or sequence order is set by default. In a business process there are several operating conditions upon which a business activity relies. For example a withdraw service can only be happened after authentication service, it must not happened before. Assembling services in order to accomplish business logic and business processes is called orchestration. \hyperref[b2]{[3]} Explains orchestration as "the implementation of a business related workflow owned by a single entity through the combination of business relevant services". The orchestrator is deployed as a BPEL program in the Orchestration director engine.\par
In this step we define orchestration logic as the business logic that sequences, coordinates and manages conversations among Web services. This entire thing is expressed in BPEL. To execute a BPEL process a BPEL engine is needed which parses the BPEL code and executes the contained instructions. The Core Web services that are used by the BPEL program have to be deployed in advance. The whole orchestrator is deployed on Intalio BPMS server which acts as an Orchestration director engine. The orchestrator may be called in presentation mechanism through its WSDL and endpoint URL. In the ATM application a Java GUI reforms the presentation task which uses the orchestrator.  
\section[{DISCUSSIONS AND RELATED WORK}]{DISCUSSIONS AND RELATED WORK}\par
The implementation and results of the proposed method may be understood by following demonstration of the case scenario. In figure \hyperref[fig_4]{5} an account summary page is displayed. We can understand that all the logic is embedded deep in the code of legacy application.\par
In figure \hyperref[fig_5]{6} the composite fund transfer service task in the orchestrator is elaborated. New business process requires a fund transfer mechanism, which needs to be achieved from the existing code. This is done in the modeler by calling and sequencing two web services from legacy application thus making a composite process. In the sample banking application no individual authentication is required as the software interacts only through its GUI and it is accessed by bank authorities. But as per the requirement of ATM business process as the application is exposed to an external world then it is very important to put an authentication mechanism. This is incorporated in the orchestrator as shown in figure  {\ref 7}.\par
The results demonstrate the process proposed in this work with a sample banking application as elaborated in the case description. The system can map legacy application at par with the requirement of business using exposure of functionality through web services and the usability by orchestration of BPM process. Further the released services can be used by any language or application like Java and C\# through the service description. This also proves that by adopting the proposed technique one would be able to integrate new logics with the existing business logic or would be able to seamlessly upgrade the existing services without having to make any changes in the coding in the legacy application. Therefore the architecture minimizes the maintenance cost by maintaining the business logic in the middle layer independent of the implementation.\par
In the past several methods for legacy system modernization have been proposed and discussed. \hyperref[b22]{[21]} elaborated the white-box modernization and blackbox modernization approaches comparisons.\par
Fig.  {\ref 7} Intalio ATM orchestrator process with interfaces \hyperref[b23]{[22]} Proposed a method to address the issues on migrating legacy systems into a Web enabled environment by using CORBA. \hyperref[b24]{[23]} Used reverse engineering techniques to encapsulate the logic with JNI wrapper. \hyperref[b25]{[24]} Proposed a method to make interactive legacy systems accessible by wrapping interactive functionalities. \hyperref[b26]{[25]} Proposed a tool based approach to wrap the legacy codes. All of the methods were focused on the application modernization only rather than addressing the business domain. In our approach we emphasized on a close business and IT alignment. 
\section[{V. CONCLUSION}]{V. CONCLUSION}\par
In this work a legacy application mapping technique by combining top-down approach with bottom-up approach is proposed using SOA and BPM. The method defines how a legacy application should be exposed as services and how these services can be used to fulfill business goals. The solutions principles are demonstrated through the results. Instead of using the manual functionality discovery in the legacy service identification stage, a tool is developed to automatically identifying the services. The interoperability of the entire solution is shown in the result section. The prime criteria and objective of the work has been to prove the proposed design of legacy application mapping and integration to participate in enterprise business processes. As the services are exposed to be used on network, performance calibration and tuning is another aspect and the speed and processing capabilities of the environments used must be taken into consideration. The proposed approach performance and speed issues are some of the work that can be associated with the future direction of research for this work.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Fig. 1}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-3.png}
\caption{\label{fig_1}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5823}\includegraphics[]{image-4.png}
\caption{\label{fig_2}58 MayFig. 2 Fig. 3}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Fig. 4}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-6.png}
\caption{\label{fig_4}Fig. 5}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{6}\includegraphics[]{image-7.png}
\caption{\label{fig_5}Fig. 6}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-8.png}
\caption{\label{figure8}}\end{figure}
 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Addison-Wesley ()]{b11}\label{b11} 	 		\textit{},  		 			Addison-Wesley 		.  		2005.  	 
\bibitem[ European Conference on SoftwareMaintenance and Reengineering ()]{b27}\label{b27} 	 		\textit{},  	 	 		\textit{European Conference on SoftwareMaintenance and Reengineering}  		2006. IEEE Computer Soc.  	 
\bibitem[Jianzhi et al. ()]{b24}\label{b24} 	 		‘A grid oriented approach to reusing legacy code in ICENI framework’.  		 			L Jianzhi 		,  		 			Z Zhang 		,  		 			H Yang 		.  	 	 		\textit{Proc. of the 2005 , IEEE I nternational Conference on Information Reuse and Integration},  				 (of the 2005 , IEEE I nternational Conference on Information Reuse and Integration)  		2005. IEEE Computer Soc.  	 
\bibitem[Comella-Dorda et al. ()]{b22}\label{b22} 	 		‘A survey of black-box modernisation approaches for information systems’.  		 			S Comella-Dorda 		,  		 			K Wallnau 		,  		 			R C Seacord 		,  		 			J Robert 		.  	 	 		\textit{Proceedings of the International Conference on Software Maintenance},  				 (the International Conference on Software Maintenance)  		2000. IEEE CS Press. p. .  	 
\bibitem[Zimmermann et al. ()]{b17}\label{b17} 	 		‘Analysis and Design Techniques for Service-Oriented Development and Integration’.  		 			O Zimmermann 		,  		 			N Schlimm 		,  		 			G Waller 		,  		 			M Pestel 		.  	 	 		\textit{Proc. GI Jahrestagung},  				 (GI Jahrestagung)  		2005. p. .  	 
\bibitem[Mitra ()]{b7}\label{b7} 	 		\textit{Business-driven development},  		 			T Mitra 		.  		 \url{http://www.ibm.com/developerworks/webservices/library/ws-bdd}  		2005. IBM.  	 	 (IBM developerWorks article) 
\bibitem[Canfora et al.]{b25}\label{b25} 	 		 			G Canfora 		,  		 			A R Fasolino 		,  		 			G Frattolillo 		,  		 			P Tramontana 		.  		\textit{A wrapping approach for},  				 	 
\bibitem[Emig et al. (2006)]{b18}\label{b18} 	 		‘Development of SOA-Based Software Systems -an evolutionary Programming Approach’.  		 			C Emig 		,  		 			J Weisser 		,  		 			S Abeck 		.  	 	 		\textit{IEEE Conference on Internet and Web Applications and Services ICIW'06},  				 (Guadeloupe / French Caribbean)  		February 2006.  	 
\bibitem[Gandhi (2010)]{b14}\label{b14} 	 		‘Fastening the SOA/SOMA Service identification approaches with project environments’.  		 			S Gandhi 		.  	 	 		\textit{IBM Developerworks},  				March 2010.  	 
\bibitem[Rao ()]{b3}\label{b3} 	 		‘Finding Services in the Mainframe’.  		 			A S Rao 		.  	 	 		\textit{Linux for you December},  				2008 5. May 2007. p. .  	 	 (SOA Magazine Issue VII) 
\bibitem[Global Journal of Computer Science and Technology Volume XI Issue X Version I]{b6}\label{b6} 	 		\textit{Global Journal of Computer Science and Technology Volume XI Issue X Version I},  		 	 
\bibitem[Sneed]{b26}\label{b26} 	 		‘Integrating legacy software into a service oriented architecture’.  		 			H M Sneed 		.  	 	 		\textit{Proc. 10th},  				 (10th)  		 	 
\bibitem[Chatarji]{b4}\label{b4} 	 		\textit{Introduction to Service Oriented Architecture. (SOA)},  		 			J Chatarji 		.  		 	 
\bibitem[Bisbal et al. (1999)]{b0}\label{b0} 	 		‘Legacy information systems: issues and directions’.  		 			J Bisbal 		,  		 			D Lawless 		,  		 			B Wu 		,  		 			J Grimson 		.  	 	 		\textit{IEEE Software}  		Sept/Oct 1999. 16  (5)  p. .  	 
\bibitem[OMG Business Process Modeling Notation ()]{b19}\label{b19} 	 		 \url{http://www.omg.org/spec/BPMN/1.2/}  		\textit{OMG Business Process Modeling Notation},  				2009.  	 
\bibitem[Fareghzadeh ()]{b20}\label{b20} 	 		‘Service Identifi cation Approach to SOA Development’.  		 			N Fareghzadeh 		.  	 	 		\textit{Proceedings of World Academy of Science, Engineering and Technology}  		2008. 35.  	 
\bibitem[Zhang et al. ()]{b21}\label{b21} 	 		‘Service identification and packaging in serviceoriented reengineering’.  		 			Z Zhang 		,  		 			L Ruimin 		,  		 			H Yang 		.  	 	 		\textit{Proc. of the 17 th International Conference on Software Engineering and Knowledge Engineering},  				 (of the 17 th International Conference on Software Engineering and Knowledge Engineering)  		2005. IEEE Computer Soc.  	 
\bibitem[Inaganti and Behara ()]{b16}\label{b16} 	 		‘Service Identification: BPM and SOA handshake’.  		 			S Inaganti 		,  		 			G Behara 		.  	 	 		\textit{BPTrends}  		2007.  	 
\bibitem[Erl ()]{b2}\label{b2} 	 		\textit{Service-Oriented Architecture: Concepts, Technology, and Design},  		 			T Erl 		.  		2005. Upper Saddle River, NJ, USA: Prentice Hall PTR.  	 
\bibitem[Papazoglou and Georgakopoulos ()]{b9}\label{b9} 	 		‘Service-Oriented Computing’.  		 			M Papazoglou 		,  		 			D Georgakopoulos 		.  	 	 		\textit{Communications of the ACM}  		2003. 46  (10) .  	 
\bibitem[Papazoglou and Van Den Heuvel ()]{b12}\label{b12} 	 		‘Service-Oriented Design and Development Methodology’.  		 			M P Papazoglou 		,  		 			W J Van Den Heuvel 		.  	 	 		\textit{Int.J. of Web Engineering and Technology}  		2006.  	 
\bibitem[Asranjani (2004)]{b13}\label{b13} 	 		\textit{Service-oriented modeling and architecture, How to identify, specify, and realize services for your SOA},  		 			Ali Asranjani 		.  		November 2004.  	 	 (IBM Developerworks) 
\bibitem[Services/Introduction-to-Service-Oriented-Architecture-SOA/ An approach for exposing legacy applications for integration in modern enterprise business processes ©2011 Global Journals Inc]{b5}\label{b5} 	 		‘Services/Introduction-to-Service-Oriented-Architecture-SOA/ An approach for exposing legacy applications for integration in modern enterprise business processes ©2011’.  	 	 		\textit{Global Journals Inc}  		US.  	 
\bibitem[Arsanjani et al. ()]{b15}\label{b15} 	 		‘SOMA: a method for developing service-oriented solutions’.  		 			A Arsanjani 		,  		 			S Ghosh 		,  		 			A Allam 		,  		 			T Abdollah 		,  		 			S Ganapathy 		,  		 			K Holley 		.  	 	 		\textit{IBM Systems Journal}  		2008. 2008. 47  (3)  p. .  	 
\bibitem[The Modernization Imperative]{b1}\label{b1} 	 		\textit{The Modernization Imperative},  		Oracle Magazine.  	 
\bibitem[Koehler et al. (2008)]{b8}\label{b8} 	 		‘The Role of Visual Modeling and Model Transformations in Business-driven Development’.  		 			J Koehler 		,  		 			R Hauser 		,  		 			J Kuster 		,  		 			K Ryndina 		,  		 			J Vanhatalo 		,  		 			M Wahler 		.  	 	 		Electronic Notes in Theoretical Computer Science  		28 April 2008. 211 p. .  	 
\bibitem[Newcomer and Lomow]{b10}\label{b10} 	 		\textit{Understanding SOA with Web Services},  		 			Eric Newcomer 		,  		 			Greg Lomow 		.  		 	 
\bibitem[Zou and Kontogiannis (2000)]{b23}\label{b23} 	 		 			Ying Zou 		,  		 			Kostas Kontogiannis 		.  		\textit{Web-based Legacy System Migration and Integration" the 4th International Conference in Systematic, Cybernetics and Informatics (SCI)},  				 (Orlando, USA)  		July 2000. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
