BPM and SOA Are Going Mobile: An Architectural Perspective

74
Guido Schmutz Trivadis Torsten Winterberg OPITZ CONSULTING Deutschland GmbH BPM and SOA Are Going Mobile Oracle Open World, September 2013 An Architectural Perspec;ve [CON2253]

Transcript of BPM and SOA Are Going Mobile: An Architectural Perspective

Page 1: BPM and SOA Are Going Mobile: An Architectural Perspective

Titelfolie:  •  Damit  beginnt  ein  Vortrag.  •  Haup6tel:  1zeilig!  •  Unter;tel:  max  2.  Zeilen  •  Referent:  Name,  Funk+on,  OC  Niederlassung  

•  Logo:  Op+onal.    Entweder  ein  Kunden/  oder  themenbezogenes  Logo  verwenden.  Ideal  quadra+sch,  3  Raster  breit.  

•  Fusszeile  mit  HaupHtel  füllen.  

Guido  Schmutz  Trivadis  Torsten  Winterberg  OPITZ  CONSULTING  Deutschland  GmbH  

BPM  and  SOA  Are  Going  Mobile  

Oracle  Open  World,  September  2013  

An  Architectural  Perspec;ve  [CON2253]  

Page 2: BPM and SOA Are Going Mobile: An Architectural Perspective

The  Team:  Masons-­‐of-­‐SOA  n  Bernd  Trops  (Talend):  

[email protected]  

n  Clemens  Utschig-­‐Utschig  (Boehringer-­‐Ingelheim):  clemens.utschig-­‐utschig@boehringer-­‐ingelheim.com  

n  Berthold  Maier  (T-­‐Systems):  berthold.maier@t-­‐systems.com  

n  Hajo  Normann  (Accenture):  [email protected]  

n  Torsten  Winterberg  (OPITZ  CONSULTING):  torsten.winterberg@opitz-­‐consul;ng.com  

n  Jürgen  Kress  (Oracle  Corp.)  [email protected]    

n  Guido  Schmutz  (Trivadis):  [email protected]  

n  Danilo  Schmiedel  (OPITZ  CONSULTING):  danilo.schmiedel@opitz-­‐consul;ng.com  

www.soa-­‐community.com  

Page 3: BPM and SOA Are Going Mobile: An Architectural Perspective

Mobile  Development  What  does  this  mean  today?  

 An  architectural  point  of  view  

Page 4: BPM and SOA Are Going Mobile: An Architectural Perspective

We  need  an  iPhone  App!                      2008  

Page 5: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 6: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 7: BPM and SOA Are Going Mobile: An Architectural Perspective

Cloud-­‐Services  become  more    and  more  important  

Dropbox,  Evernote,  …  

Page 8: BPM and SOA Are Going Mobile: An Architectural Perspective

We  need  an  Android  App!            2010  

Page 9: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 10: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 11: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 12: BPM and SOA Are Going Mobile: An Architectural Perspective

Market  share  mobile  OS  

Design:  •  Das  Farbschema  ist  im  Design  als  „OC  2009“  hinterlegt.  

•  Ebenso  sind  die  Schrigarten  als  „OC  2009“  hinterlegt.  

•  Die    Standardfarben  sind:      

           

           

   

       

Page 13: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 14: BPM and SOA Are Going Mobile: An Architectural Perspective

Acceptance  of  Android  Versions  

Design:  •  Das  Farbschema  ist  im  Design  als  „OC  2009“  hinterlegt.  

•  Ebenso  sind  die  Schrigarten  als  „OC  2009“  hinterlegt.  

•  Die    Standardfarben  sind:      

           

           

   

       

hVp://www.iphoneblog.de/2012/10/08/android-­‐in-­‐welcher-­‐version/  

Page 15: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 16: BPM and SOA Are Going Mobile: An Architectural Perspective

The  Web:  Cross-­‐Plahorm  Write  Once,  run  everywhere  

Page 17: BPM and SOA Are Going Mobile: An Architectural Perspective

Browsers  

Design:  •  Das  Farbschema  ist  im  Design  als  „OC  2009“  hinterlegt.  

•  Ebenso  sind  die  Schrigarten  als  „OC  2009“  hinterlegt.  

•  Die    Standardfarben  sind:      

           

           

   

       

Page 18: BPM and SOA Are Going Mobile: An Architectural Perspective

               

HTML5  

HTML  elements   JavaScript   CSS  

HTML5  is  the  evolu+on  of  web  development  

Page 19: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 20: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 21: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 22: BPM and SOA Are Going Mobile: An Architectural Perspective

Business  Logic  

User  Interface  Request  

Backend  Frontend  

Classical  Architecture  

Response  Storage  

Rendering  

Page 23: BPM and SOA Are Going Mobile: An Architectural Perspective

User  Interface  

Storage  

REST  Calls  

Local  Storage  

Presenta;on  Logic  REST  Backend  

Single  Page  Web-­‐Apps  

Backend  Frontend  

Page 24: BPM and SOA Are Going Mobile: An Architectural Perspective

SOFEA  /  Webapps  

Source:  Life  above  the  Service  Tier,  How  to  Build  Applica/on  Front-­‐ends  in  a  Service-­‐Oriented  World  

Page 25: BPM and SOA Are Going Mobile: An Architectural Perspective

Hybrid  Apps  

Design:  •  Das  Farbschema  ist  im  Design  als  „OC  2009“  hinterlegt.  

•  Ebenso  sind  die  Schrigarten  als  „OC  2009“  hinterlegt.  

•  Die    Standardfarben  sind:      

           

           

   

       

Na;ve  App  

HTLM  CSS  

JavaScript  

WebView  

Na;ve  App  

Page 26: BPM and SOA Are Going Mobile: An Architectural Perspective

1 2 3 4

Start  process  from  mobile  device    

Start  process  for  insurance  

immediately  

Page 27: BPM and SOA Are Going Mobile: An Architectural Perspective

Mobile  Tasklist  

Page 28: BPM and SOA Are Going Mobile: An Architectural Perspective

Mobile  Dashboards  

Page 29: BPM and SOA Are Going Mobile: An Architectural Perspective

Mobile  Processdesign  

Page 30: BPM and SOA Are Going Mobile: An Architectural Perspective

Mobile  process  documenta;on  

Page 31: BPM and SOA Are Going Mobile: An Architectural Perspective

Mobile  Alarm  /  Monitoring  

Page 32: BPM and SOA Are Going Mobile: An Architectural Perspective

Warning:  Avoid  the  Many-­‐cheap-­‐Apps-­‐Architecture-­‐Maintenance-­‐Hell  

Page 33: BPM and SOA Are Going Mobile: An Architectural Perspective

Mobile  Integra;on  Technologies  

SOAP  •  Has  a  reputa;on  for  being  

complex  and  heavyweight  •  Has  a  formal  contract  

language  to  define  message  formats  

•  Supports  standardized  security  approaches  and  tools  

•  Supports  XML  and  Binary    

REST  •  Has  a  reputa;on  for  being  

simple  and  lightweight  •  No  formal  contract  

language  to  define  message  formats  

•  Security  is  a  major  challenge  due  to  lack  of  standardiza;on  

•  Supports  mul;ple  data  types  (JSON,  Text,  XML,  Binary)  

Page 34: BPM and SOA Are Going Mobile: An Architectural Perspective

SOAP  Style  

34  

Mobile  Integra;on  Panerns  

REST  Style  

Page 35: BPM and SOA Are Going Mobile: An Architectural Perspective

REST  API  Schema  Ak;on   Typ   URI  Schema  

customerByUsername   GET   /api/customers?username=fred  

rentalsByCustomerId   GET   /api/rentals?customerId=7  

carTypes   GET   /api/cartypes  

ci;es   GET   /api/ci;es  

availableCars   GET   /api/availableCars?cityId=1          &startDate=2011-­‐10-­‐28-­‐…          &endDate=2011-­‐10-­‐30-­‐…          &maxPrice=90  

rentCar   POST   /rental/          Body:  {carId=...,startDate=...,endDate=...}  

Date  format:  "yyyy-­‐MM-­‐ddTHH:mm:ss.SSSZ"    

Page 36: BPM and SOA Are Going Mobile: An Architectural Perspective

Mobile  Integra;on  Technologies  

XML  •  “Na;ve”  format  for  

enterprise  data  exchange  •  Highly  formal  structure  •  Content  CAN  be  validated  •  Formats  can  change  only  

when  all  par;es  agree  •  Supports  mul;ple  data  

types  (Text,  Binary)  

JSON  •  “Na;ve”  format  for  web  

pages  •  No  formal  structure  •  Content  cannot  be  

validated  •  Easy  to  change  •  Text  only  

 

Page 37: BPM and SOA Are Going Mobile: An Architectural Perspective

37  

REST:  URI  addressing  and  data  representa;on  

Mobile  Integra;on  Panerns  

Page 38: BPM and SOA Are Going Mobile: An Architectural Perspective

JSON  as  exchange  format  for  data    Request:  $  curl  -­‐-­‐user  fred:pass  http://localhost:8484/...  

.../rylc-­‐html5/backend/api/customers?username=fred    

Response:      {        "city":"Steintal",        "email":"fred@die-­‐feuersteins.de",        "enabled":true,        "id":1,        "name":"Fred  Feuerstein",        ...      }  

Page 39: BPM and SOA Are Going Mobile: An Architectural Perspective

Titel  und  2  Inhalte  mit  Überschrigen  •  Layout  für  2  spal;ge  Listen  mit  Überschrigen  

•  Titel:  1-­‐2zeilen  •  Überschrigen  1zeilig  •  Inhalt:    

•  3-­‐5  Punkte  o  2-­‐3  Hauptpunkte  mit  Unterpunkten  

•  Max  bis  zur  3.  Ebene  •  Achtung:  Sofern  Text  1.  Spalte  zu  Dicht  an  2.  Spalte,  korrigiere  Textboxbreite!  

old   new  

The  Web  is  evolving…  

Documents    Declara;ve  HTML  

Templates  Request/Response  

Thin  Client  

Applica;ons  Programma;c  DOM  

APIs  Synchroniza;on  Thick  Client  

Page 40: BPM and SOA Are Going Mobile: An Architectural Perspective

Digital Natives

Page 41: BPM and SOA Are Going Mobile: An Architectural Perspective

Back to terminator vision

Page 42: BPM and SOA Are Going Mobile: An Architectural Perspective

Google  Glasses  

Google Glasses © http://www.flickr.com/photos/azugaldia/7457645618

Page 43: BPM and SOA Are Going Mobile: An Architectural Perspective

Internet of Things

Page 44: BPM and SOA Are Going Mobile: An Architectural Perspective

hVp://blog.trentonsystems.com/machine-­‐to-­‐machine-­‐technology-­‐efficient-­‐economy    

Page 45: BPM and SOA Are Going Mobile: An Architectural Perspective

A  high-­‐level  M2M  system  architecture  

Page 46: BPM and SOA Are Going Mobile: An Architectural Perspective
Page 47: BPM and SOA Are Going Mobile: An Architectural Perspective

Data  Driven  Applica;ons  as  new  breed  

“It’s  about  using  data  to  make  our  customer  touch  points  more  engaging,  more  interac;ve,  more  data-­‐driven.”    

Page 48: BPM and SOA Are Going Mobile: An Architectural Perspective

Central  vs.  Applica;on  Databases  

48  

•  Applica;on  Database  •  Only  accessed  by  a  single  applica;on  •  Only  the  applica;on  using  the  database  

needs  to  know  about  the  structure  •  Easier  to  maintain  and  evolve  the  schema  •  More  freedom  to  choose  the  database  •  Applicable  to  SOA  (i.e.  Data  Service/En;ty  

Service)  with  good  Service  Autonomy  •  Ready  for  the  cloud  

•  Central  Database  •  Using  SQL  as  the  integra;on  mechanism  

between  applica;ons  •  applica;ons  store  data  in  common  DB  •  Improves  communica;on,  all  

applica;ons  operate  on  consistent  set  of  data  

•  Structure  ends  up  to  be  more  complex  •  Changes  need  to  be  coordinated  with  all  

other  applica;ons  using  the  database  •  Side-­‐effects  (i.e.  adding  database  index)  

DB

Application 1 Application 2 Application 3

DB

Application 1 Application 2 Application 3

DB DB

Page 49: BPM and SOA Are Going Mobile: An Architectural Perspective

Rela;onal  vs.  Aggregate  Data  Models  

49  

•  Aggregate  is  a  term  that  comes  from  Domain-­‐Driven  Design  (Evans)  

•  An  aggregate  is  a  collec;on  of  related  objects,  that  should  be  treated  as  a  unit  –  Unit  for  data  manipula;on  and  

management  of  consistency  

•  The  rela;onal  model  takes  the  informa;on  and  divides  it  into  tuples  (rows)  

•  A  tuple  is  a  limited  data  structure  –  no  nes;ng  of  tuples    –  no  list  of  values  

Page 50: BPM and SOA Are Going Mobile: An Architectural Perspective

NoSQL  Databases    Big  Data  frameworks  are  ogen  associated  with  the  term  NoSQL  •  Not  only  SQL  •  The  power  of  SQL  is  not  needed  for  all  problems  •  Specialized  solu;ons  may  be  faster  or  more  scalable  •  Bring  the  ability  to  handle  semi-­‐structured  and  unstructured  data  •  NoSQL  complements  RDBMS    •  Different  types  of  NoSQL  today:  

•  Key-­‐value,  Column-­‐Family,  Document,  Graph  Big  Data  frameworks  and  NoSQL  are  related  but  not  necessarily  the  same  •  Some  big  data  problems  may  be  solved  rela;onally  

 

Page 51: BPM and SOA Are Going Mobile: An Architectural Perspective

Polyglot  Persistence  Defines  a  hybrid  approach  to  persistence  •  Using  mul;ple  data  storage  technologies  •  Selected  based  on  the  way  the  data  is  used  by  an  applica;on  Decisions  •  Have  to  decide  what  data  storage  technology  to  use  (Rela;onal  or  NoSQL)  •  Today  it‘s  easier  to  go  with  rela;onal  New  Data  Access  APIs  •  Each  data  store  has  its    

own  mechanisms  for    accessing  the  data  

Solu;on  •  Wrap  data  access    

code  into  services  (Data/  En;ty  Service)  exposed  to    applica;ons  

51  

Service-Oriented Polygot Persistence Model

User Session Service

Shopping CartService Order Service

Product CatalogService

Recomendation Service

E-commerce Application

Shopping cart data User Sessions Product Catalog RecomendationsCompleted Order

Key-Value RDMBS Document Graph

Page 52: BPM and SOA Are Going Mobile: An Architectural Perspective

Unified  (Mobile)  Architecture  

   

52  Enterprise  Applica;ons  

SOAP  

JMS  

REST   RDMBS  Internet  of  

Things  

Mobile  Apps  

Local  ESB  

External  Cloud  Service  Providers  

Enterprise  Service  Bu

s  (ESB)  

EJB  

Cloud  to  Device  Messaging  (C2DM)  

Service  Ga

teway  

CEP  

HTTP/JSON  Applica;on  

Server  

Complex  Event  Processing  (CEP)  /  Fast  Data  

NoSQL  /  Big  Data  

BPM    und  SOA    Pla}orm  

REST  

SOAP  DB  

LDAP  /  Enterprise  IDM  

(Big)  Data  Analy;cs  

Business  Logic  

NoSQL  

Web  Apps  

DB  

Analy;cal  Applica;ons  

Data  Warehouse  

Data  Integra;on  

RDMBS  

Page 53: BPM and SOA Are Going Mobile: An Architectural Perspective

Unified  (Mobile)  Architecture  

   

53  Enterprise  Applica;ons  

SOAP  

JMS  

REST   RDMBS  Internet  of  

Things  

Mobile  Apps  

Local  ESB  

External  Cloud  Service  Providers  

Enterprise  Service  Bu

s  (ESB)  

EJB  

Cloud  to  Device  Messaging  (C2DM)  

Service  Ga

teway  

CEP  

HTTP/JSON  Applica;on  

Server  

Complex  Event  Processing  (CEP)  /  Fast  Data  

NoSQL  /  Big  Data  

BPM    und  SOA    Pla}orm  

REST  

SOAP  DB  

LDAP  /  Enterprise  IDM  

(Big)  Data  Analy;cs  

Business  Logic  

NoSQL  

Web  Apps  

DB  

Analy;cal  Applica;ons  

Data  Warehouse  

Data  Integra;on  

RDMBS  

Oracle  Service  Bu

s  (OSB)  

Oracle  WebLogic  Server  

Oracle  SOA  Suite  

Oracle  BPM  Suite  

Oracle  ADF  

Oracle  Event  Processing  (OEP)  

Oracle  NoSQL  Database  

Oracle  BigData  Appliance  (BDA)  

Oracle  ADF  Mobile  

Oracle  Da

ta  Integrator  (O

DI)  

Oracle  ADF  

Oracle  WebLogic    Server  

Java  Embedded  

Oracle  Database  Mobile  Server  Web  Sockets  

OEP  Embedded  Oracle  Business  Intelligence  Founda+on  Suite  

Oracle  Business  Ac+vity  Monitoring  (BAM)  

Oracle  Go

lden

Gate  

Oracle  NoSQL  DB  

Oracle  RDBMS  

Oracle  Database    Mobile  Server  

Oracle  IDM  Oracle  AP

I  Gatew

ay  (O

AG)  

Page 54: BPM and SOA Are Going Mobile: An Architectural Perspective

Conclusion  

Page 55: BPM and SOA Are Going Mobile: An Architectural Perspective

§  Mobile  Apps  today  §  Think  in  new  architecture  panern  

§  Na;ve  Apps,  mobile  Web-­‐Apps,  Hybride  Apps  §  HTML5,  Single-­‐Page-­‐Apps,  Many-­‐Cheap-­‐Apps-­‐Hell,…      

§  Mobile  Apps  tomorrow  §  Not  only  B2C  and  B2B,  but  M2M  §  Explosion  of  

§  Number  of  Devices  §  Data  /  Events  §  Need  for  Integra;on  

§  Combina;on  of  Cloud,  Big  Data,  Fast  Data  /  Event  Processing,  Mobile,  IoT  is  the  future  

Page 56: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  products  fi6ng  in  this  architecture  

Page 57: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  ADF  Mobile  

•  Enables  Customers  to  mobile-­‐enable  enterprise  applica;ons  –  One  common  pla}orm  for  desktop  and  

mobile  applica;ons  (Android  &  iOS)  –  Handle  mul;ple  channels  and  network:  

browser,  na;ve,  and  hybrid  applica;ons  

•  Technology  founda;on  for  future  Oracle  applica;ons  mobile  development  

Page 58: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  ADF  •  End-­‐to-­‐end  development  

framework  for  Java  EE  •  Based  on  industry  standards  •  Full  model-­‐view-­‐controller  

implementa;on  •  Rich  web,  mobile  and  desktop  UI  •  Focus  on  reusability  •  Visual  and  declara;ve  

development  •  Integrated  security  and  

customiza;on  

Page 59: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  Database  Mobile  Server  •  Secure,  efficient,  resilient  mobile  

data  synchroniza;on  with  Oracle  Database    

•  Remote  applica;on,  user  and  device  management    

•  Standards-­‐based  encryp;on  for  remote  data,  in  both  storage  and  transit    

•  Robust  and  reliable  mobile  data  synchroniza;on  over  unreliable  networks  

•  Highly  scalable  server  configura;on,  suppor;ng  large  and  growing  mobile  or  remote  deployments    

•  Integra;on  with  ADF  Mobile  

Page 60: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  API  Gateway  (OAG)  •  Serves  REST  APIs  and  SOAP  Web  Services  to  

clients  –  Converts  REST  to  SOAP  –  Converts  XML  to  JSON  

•  Supports  other  protocols  also  –  FTP,  SFTP,  FTPS  –  TIBCO  Rendezvous  and  EMS  –  JMS  (to  IBM  WebSphere  MQ,  Ac;veMQ,  JBOSS  

Messaging,  etc)  

•  Applies  security  rules  –  Authen;ca;on:  OAuth,  HTTP  Auth,  Cer;ficate  

Auth,  WS-­‐Security  –  Content  Filtering:  Detec;on  of  SQL  Injec;on,  

XSS,  Viruses  

•  Monitoring  of  API  and  Service  usage  •  Caching  and  Traffic  Management  (rou;ng,  

thronling)  

Page 61: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  Service  Bus  (OSB)  –  Message  &  Service  Integra;on  

•  Embedded  access  to  service  result  caching  

•  Intelligent  content  and  iden;ty  based  rou;ng  

•  Rich  set  of  transports/adapters  •  Data-­‐oriented  services  and  REST  

support  •  Dynamic  message  transforma;on  

and  streaming  •  Built-­‐in  monitoring,  management  

and  QoS  •  Configura;on-­‐driven  message  and  

service  integra;on  •  Op;mized,  pluggable,  policy-­‐driven  

transport  and  message  security    

Page 62: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  Data  Integrator  (ODI)  –  Data  Integra;on  

•  Out-­‐of-­‐the-­‐box  integra;on  with  databases,  ERPs,  CRMs,  B2B  systems,  flat  files,  XML  data,  LDAP,  JDBC,  ODC  

•  Knowledge  module  framework  for  extensibility  

•  In-­‐database  transforma;ons  and  data  integrity  controls  on  all  databases  

•  Rich  ETL  for  Oracle  databases  •  Integrates  with  Oracle  GoldenGate  

for  real-­‐;me  data  warehousing  •  Metadata-­‐driven  data  lineage  and  

impact  analysis  •  Integrates  with  Oracle  Enterprise  

Data  Quality  for  advanced  profiling,  cleansing,  matching  and  data  governance  needs  

Page 63: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  Goldengate  –  Data  Replica;on  

•  High  performance  data  replica;on  •  Heterogeneous  sources  and  

targets  •  Conflict  detec;on  and  resolu;on  •  Real-­‐;me  and  deferred  apply  •  Event  marker  infrastructure  •  Flexible  topology  support  •  Data  encryp;on  •  ETL  and  JMS  integra;on  •  Rou;ng  and    •  compensa;on  •  Ini;al  load  capability  

Page 64: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  SOA  Suite  –  Service  Integra;on  •  Unifies  Oracle  and  3rd  party  

Cloud  applica;ons  with  on-­‐premises  

•  Enables  rapid  delivery  of  exis;ng  applica;ons  into  mobile  channel  

•  Improves  partner  collabora;on  with  bener  B2B  and  API  Management  

•  Fast  Data  support  with  embeddable  real-­‐;me  event  pla}orm  

•  Op;mized  integra;on  to  Oracle  Applica;ons  running  on  Oracle  Exalogic  

Page 65: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  BPM  Suite  –  Business  Process  Management  

•  Business  driven  design,  execu;on  and  improvement  

•  Common  process  model  facilitates  Business-­‐IT  collabora;on  

•  Complete  support  for  any  type  of  process,  including  Adap;ve  Case  Management  

•  Modernize  and  unify  exis;ng  applica;ons  

•  Time-­‐to-­‐value  &  packaged  best  prac;ces  with  Process  Accelerators  

Page 66: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  Event  Processing  (OEP)  

•  Lightweight  Java    Applica;on  server  

•  Deployable  stand-­‐alone,  integrated  in  SOA  stack  or  lightweight  on  Embedded  Java  

•  Con;nuous  Query  Language  (CQL)  based  on  SQL  syntax  

•  Easy  to  use  Development  Environment  

•  Enterprise  class  High  Availability,  Scalability,  Performance  and  Reliability  

•  Various  Integra;on  Opportuni;es  using  AQ,  JMS  and  HTTP  Publish/Subscribe  Connec;vity…    

•  Coherence  Integra;on  

Page 67: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  Business  Ac;vity  Monitoring  (BAM)  

•  Monitor  business  processes  &  services  in  real-­‐;me  

–  Key  Performance  Indicators  (KPIs)  –  Service-­‐Level  Agreements  (SLAs)  

•  Analyze  events  as  they  occur    –  Correlate  events  &  KPIs  –  Iden;fy  trends  as  they  emerge  –  Alert  users  to  bonlenecks  &  solu;ons  

•  Act  on  current  condi;ons  –  Event-­‐driven  alerts  –  Real-­‐;me  dashboards  –  BPEL  processes  &  web  services  

integra;on  

Page 68: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  Big  Data  Appliance  •  Massively  scalable  infrastructure  to  store  and  

manage  big  data  •   Big  Data  Connectors  delivers  load  rates  up  to  

12TB  per  hour  between  Data  Applicance  and  Oracle  RDMBS  

•  Based  on  Cloudera’s  distribu;on  •  Integrated  into  Oracle  Enterprise  Manager  •  Advanced  analy;cs  with  Oracle  R  on  Hadoop  

data  •  Handle  low-­‐latency  unstructured  workload  

with  the  pre-­‐installed  Oracle  NoSQL  database  •  Infiniband  connec;vity  between  node  and  

across  racks  •  Flexible  configura;on  choices  allowing  flexible  

growth  for  Haddop  and  Oracle  NoSQL  databases  

Page 69: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  NoSQL  Database  •  Simple  Data  Model  

•  Key-­‐value  pair  with  major+sub-­‐key  paradigm  •  Read/insert/update/delete  opera;ons  

•  Scalability  •  Dynamic  data  par;;oning  and  distribu;on  •  Op;mized  data  access  via  intelligent  driver  

•  High  availability  •  One  or  more  replicas  •  Disaster  recovery  through  loca;on  of  replicas  •  Resilient  to  par;;on  master  failures  •  No  single  point  of  failure  

•  Transparent  load  balancing  •  Reads  from  master  or  replicas  •  Driver  is  network  topology  &  latency  aware    

•  Elas;c  •  Online  addi;on/removal  of  Storage  Nodes    •  Automa;c  data  redistribu;on  

Page 70: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  WebLogic  Server  §  Java  EE  6  applica;on  server  

§  Java  SE  6  and  7  cer;fica;on  

§  High  Performance  Pla}orm  for  Mission  Cri;cal  Cloud  Applica;ons  

§  Deep  Integra;on  with  Oracle  Database  12c  -­‐  Mul;tenant  and  RAC  

§  Real-­‐;me  data  processing  through  GoldenGate  HotCache  &  Live  Events  

§  Built-­‐in  support  for  HTML5  and  WebSockets  for  rich  mobile  and  cloud  applica;ons  

Oracle  Database  12c  

Page 71: BPM and SOA Are Going Mobile: An Architectural Perspective

Oracle  Iden;ty  Management  •  Simplified  Iden;ty  Governance  

–  Access  Request  Portal  with  Catalog  and  Shopping  cart  UI  

–  In  product,  durable  customiza;on  of  UIs,  forms  and  work  flows  

–  Privileged  Account  Management  –  leverage  Iden;ty  connectors,  workflows,  audit  

•  Complete  Access  Management  –  Integrated  SSO,  Federa;on,  API  Management,  Token  

Management,  Granular  Authoriza;on  –  Mobile  applica;on  security  with  SSO,  device  finger  

prin;ng  and  step  up  authen;ca;on  –  Social  iden;ty  log-­‐in  from  popular  social  media  sites  –  REST,  OAuth,  XACML  

•  Directories  that  Scale  –  OUD  op;mized  on  T4  hardware  delivering  3x  

performance  gain  and  15%  of  set  up  ;me  

Page 72: BPM and SOA Are Going Mobile: An Architectural Perspective

Contact  

Page 73: BPM and SOA Are Going Mobile: An Architectural Perspective

© OPITZ CONSULTING GmbH 2011 Seite 73 Mobile Lösungen und BPM

Konstruktionsraster 20mm 4mm

OPITZ CONSULTING Vorlage Powerpoint 2010; Version 1.11; 10.02.2010; TGA, MVI, JWI

Kontakt 1. fach: •  Diese Folie wird als vorletzte

Folie genutzt, um den individuellen Bezug zum Referenten herzustellen.

•  Als Foto muss ein quadratisches Foto des Referenten in qualitativ hochwertiger Form vorliegen.

•  Das Foto geht über 3 Rasterbreiten.

•  Die Daten der Adresse sollten vollst. eingegeben werden

Contact  

Torsten  Winterberg  Business  Development  &  Innova+on    OPITZ  CONSULTING    Deutschland  GmbH  Kirchstr.  6,  51647  Gummersbach,  Germany  Phone:  +49  173  54  79  302  torsten.winterberg@opitz-­‐consul+ng.com  @t_winterberg    

Page 74: BPM and SOA Are Going Mobile: An Architectural Perspective

© OPITZ CONSULTING GmbH 2011 Seite 74 Mobile Lösungen und BPM

Konstruktionsraster 20mm 4mm

OPITZ CONSULTING Vorlage Powerpoint 2010; Version 1.11; 10.02.2010; TGA, MVI, JWI

Kontakt 1. fach: •  Diese Folie wird als vorletzte

Folie genutzt, um den individuellen Bezug zum Referenten herzustellen.

•  Als Foto muss ein quadratisches Foto des Referenten in qualitativ hochwertiger Form vorliegen.

•  Das Foto geht über 3 Rasterbreiten.

•  Die Daten der Adresse sollten vollst. eingegeben werden

Contact  

Guido  Schmutz  Technology  Manager    Trivadis  AG  Europa-­‐Strasse  5,  8152  GlaVbrugg,  Schweiz  Phone:  +49  173  54  79  302  [email protected]  

@gschmutz