Director,  Solu-ons  Architecture,  WSO2    

Mifan  Careem  

SOA  Pa+erns:  

File  Gateway    for  Modernizing  Legacy  Systems  

Senior  So5ware  Engineer  WSO2  

Jason  Catlin  

Agenda  ๏  About  WSO2  

๏  SOA  and  Legacy    Moderniza?on  

๏  Legacy  systems  and  file  based  ops  

๏  File  based  Gateway  

๏  Related  PaDerns  

๏  Bringing  it  all  together  

๏  References  2  

3  

About  the  Presenters  

๏  Mifan  Careem,  Director  of  Solu?ons  Architecture  at  WSO2  

๏  Mifan  AT  WSO2.com  

๏  Works  closely  with  clients  and  WSO2  engineering  and  sales  teams,  in  defining  domain  specific  solu?ons  architectures  

๏  Jason  Catlin,  Senior  SoMware  Engineer  at  WSO2  

๏  Jason  AT  WSO2.com  

๏  Helps  sales  teams  with  technical  pre-­‐sales  queries  and  works  closely  with  customers  in  solving  customer  problems  

4  

About  WSO2  ๏  Global  enterprise,  founded  in  2005  

by  acknowledged  leaders  in  XML,  web  services    technologies,  standards    and  open  source  

๏  Provides  only  open  source  plaXorm-­‐as-­‐a-­‐service  for  private,  public  and  hybrid  cloud  deployments  

๏  All  WSO2  products  are  100%  open  source  and  released  under  the  Apache  License  Version  2.0.  

๏  Is  an  Ac?ve  Member  of  OASIS,  Cloud  Security  Alliance,  OSGi  Alliance,  AMQP  Working  Group,  OpenID  Founda?on  and  W3C.  

๏  Driven  by  Innova?on  

๏  Launched  first  open  source  API  Management  solu?on  in  2012  

๏  Launched  App  Factory  in  2Q  2013  

๏  Launched  Enterprise  Store  and  first  open  source  Mobile  solu?on  in  4Q  2013  

5  

What  WSO2  delivers  

6  

Business  Model  

The  need  to  Modernize  Enterprise  Systems  ๏  With  ?me,  enterprises  need  to  evolve  their  

exis?ng  systems,  opera?ons,  business  logic  and  partners  to  meet  modern  day  needs  and  innovate  

๏  Exis?ng  systems  may  consist  of  legacy  technologies,  legacy  logic  contained  in  files,  complex  infrastructure  and  legacy  transport  such  as  FTP  etc.  

๏  Due  to  the  ?me  and  cost  complexi?es,  prior  investments,  integra?on  requirements  and  infrastructure  factors,  enterprises  cannot  leave  behind  the  exis?ng  plaXorms  

๏  Hence  organiza?ons  required  the  capability  to  modernize  these  exis?ng  systems  with  minimal  risk  and  minimal  effect  to  the  legacy  systems  in  a  short  ?me-­‐frame  

7  

Drivers  for  moderniza?on  

๏  Time  and  schedule  

๏  Minimized  development  and  deployment  costs  

๏  Monitoring  and  metering  

๏  Quality  

๏  Minimized  Risk  

๏  System  performance  

๏  Agility  and  flexibility  

8  

Moderniza?on  strategies  

๏  Informa4on  integra4on  

๏  Web  enabling  legacy  plaXorms  

๏  End  to  end  service  plaXorm  

9  

An  Enterprise  Requirement  ๏  Modernize  an  exis?ng  legacy  tax  plaXorm  that  uses  files  

as  the  media  of  communica?on.  Batch  opera?ons  are  based  on  files  that  are  pushed  via  FTP  from  3rd  party  systems.  Output  to  the  flow  should  eventually  be  files  

10  

File  Gateway  PaDern  

11  

๏  Solu?on:  Intermediary  two-­‐way  file  processing  logic  is  posi?oned  between  the  legacy  system  and  the  service  

๏  Applica?on  

๏  Inbound:  Detect  file  drops,  transform  and  use  

๏  Outbound:  intercept  service  output,  transform  and  convert  to  files  

Example  Scenario  

12  

๏  Files  are  pushed  from  external  systems  into  a  file  store  

๏  FTP,  SFTP  

๏  File  store  is  monitored  by  a  gateway  

๏  File  content  is  processed  from  input  file  

๏  Processing  takes  place  based  on  content  of  files  

 

WSO2  ESB  as  a  File  Gateway  

13  

WSO2  ESB  -­‐  Concepts  ๏  Proxy,  Sequences,  Mediators  

๏  VFS  Transport  

๏  WSO2  ESB’s  feature  rich  file  transport  

๏  VFS  transport  uses  the  versa?le  Apache  Commons-­‐VFS  library  as  the  underline  library  for  various  file  system  related  opera?ons  

๏  WSO2  ESB's  VFS  transport  consider  all  file  names  as  URIs  

๏  Smooks  Mediator  

๏  In-­‐built  ESB  mediator  for  effec?ve  transforma?ons  

๏  Enterprise  Integra?on  PaDerns  14  

A  Smooks  EDI  Scenario  

๏  Drop  an  Electronic  Data  Interchange  (EDI)  file  to  VFS  input  directory.  

๏  ESB  picks  the  file  and  sends  to  its  Smooks  mediator.  

๏  Smooks  mediator  transforms  the  EDI  file  to  XML  format.  

๏  Based  on  the  message  type  sending  file  to  correct  endpoints.  

15  

ESB  sequences  using  graphical  tool  

16  

File  Gateway  for  other  scenarios  

17  

Diagram

Impact  and  Issues  

๏  The  type  of  logic  provided  by  this  paDern  is  unsuitable  when  immediate  replies  are  required  by  either  service  or  legacy  system.    

๏  Deployment  and  governance  of  two-­‐way  file  processing  logic  can  further  add  to  opera?onal  complexity  and  may  require  specialized  administra?on  skills.  

18  

Focus  on  your  priori?es!  

19  

Related  PaDerns  

๏  Data  Format  Transforma?on  

๏  Protocol  Bridging  

๏  Legacy  Wrapper  

๏  Mul?-­‐channel  Endpoint  

20  

Bringing  it  all  together  

21  

The  bigger  picture  

22  

Demo  

23  

Summary  

๏  Many  legacy  systems  maintain  core  business  logic  in  file  based  opera?ons  

๏  The  File  Gateway  paDern  acts  as  a  media?on  layer  between  file  logic  and  service  logic  

๏  File  Gateway  can  be  implemented  using  various  technologies  and  concepts  such  as    WSO2  ESB,  WSO2  BPS,  WSO2  AS,  VFS  transport,  Smooks  mediator  

24  

25  

References  

๏  Enterprise  Integra?on  PaDerns  with  WSO2:  hDps://docs.wso2.com/display/Integra?onPaDerns  

๏  WSO2:  hDp://wso2.com/  

 

Contact  us  !