Eaiesb

1,223 views

Published on

EAIESB Java CAPS Migration Apporach

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,223
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Eaiesb

  1. 1. Billing Per Hour EAIESB
  2. 2. Billing Per Hour EAIESB - SeeBeyond Migration Approach
  3. 3. Billing Per Hour EAIESB - SeeBeyond Migration Approach - eGate/SRE System Diagram
  4. 4. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Java CAPS
  5. 5. Billing Per Hour EAIESB - SeeBeyond Migration Approach - eGate 4.5.X <ul><li>Coding </li></ul><ul><ul><li>Primarily Monk Code using eGate integrator </li></ul></ul><ul><ul><li>Java use was limited </li></ul></ul><ul><ul><li>Developer's were not Java programmers </li></ul></ul><ul><ul><li>Designer was limited to mostly drag-and-drop </li></ul></ul><ul><ul><li>Operations rather than having full access to the code </li></ul></ul>
  6. 6. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Why SRE <ul><li>Why SRE? </li></ul><ul><ul><li>Java technology back end appealing </li></ul></ul><ul><ul><li>JMS messaging compatible across platforms </li></ul></ul><ul><ul><li>Better access to collaboration code and tools </li></ul></ul><ul><ul><li>Projects on logical hosts not dependent on repository once running </li></ul></ul><ul><ul><li>More flexible project design with services running under application servers </li></ul></ul><ul><ul><li>Benefits of SOA </li></ul></ul><ul><ul><li>Opportunity to redesign critical interfaces to become more flexible . </li></ul></ul>
  7. 7. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE Architecture
  8. 8. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Why SRE <ul><li>Schema Run-time Environment (SRE) — For upgrades from 4.5.x </li></ul><ul><ul><li>Java CAPS Add-on that makes it possible to run 4.x Components in 5.X </li></ul></ul><ul><ul><li>Existing configuration (Collaborations, ETDs, Schemas, etc) can be run as is without change </li></ul></ul><ul><ul><li>Need to Export and Import the Schemas </li></ul></ul><ul><ul><li>Run-time environment can be viewed and controlled through 5.1 Enterprise Manager SRE Monitor </li></ul></ul><ul><ul><li>Java Message Service (JMS) Messages can be sent/received to/from 5.1 </li></ul></ul><ul><ul><li>4.x run-time environment and editors rebuilt for 5.1 interoperability </li></ul></ul><ul><ul><li>Conversion avoided </li></ul></ul>
  9. 9. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
  10. 10. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE Benefits <ul><li>Instant </li></ul><ul><ul><li>No need to re-compile ETDs or Collaborations </li></ul></ul><ul><ul><li>No need to re-write existing Monk or Collaboration for the Java Programming Language </li></ul></ul><ul><ul><li>Components in the SRE interact with each other and with external systems with the same functionality that existed prior to upgrading </li></ul></ul><ul><li>Seamless Data Exchange </li></ul><ul><ul><li>Publish/subscribe to SRE Schema from Java EE Platform Project </li></ul></ul><ul><ul><li>Publish/subscribe to Java EE Platform Project from SRE Schema </li></ul></ul>
  11. 11. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Converting eGate 4.5.X to Java CAPS
  12. 12. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrade Advantages & Disadvantages <ul><li>Advantages </li></ul><ul><ul><li>Protects investments in 4.5.x. </li></ul></ul><ul><ul><li>Easiest and less expensive way to upgrade to 5.x </li></ul></ul><ul><li>Disadvantages </li></ul><ul><ul><li>Requires to maintain two platforms: SRE and Java EE Platform </li></ul></ul><ul><ul><li>SRE is a “frozen” platform: will never evolve Cannot create SOA and Composite Applications </li></ul></ul>
  13. 13. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Publish / Subscribe to SRE <ul><li>Configure JMS API queues or topics as usual in the Java EE Platform Project </li></ul><ul><li>Deploy queues or topics to a Java EE Platform JMS API IQ Manager with configuration matching that of the SRE JMS API IQ Manager </li></ul>
  14. 14. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Publish / Subscribe to Java CAPS <ul><li>Create eWay Adaptor Connection in SRE Schema that points to the Java EE Platform JMS API IQ Manager </li></ul>
  15. 15. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Monitoring from Java CAPS <ul><li>Component status shown when component is selected in browser </li></ul><ul><li>Components can be started/stopped </li></ul>
  16. 16. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
  17. 17. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE and Java CAPS at Runtime
  18. 18. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE and Java CAPS at Runtime
  19. 19. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Conversion Advantages and Disadvantage <ul><li>Advantages </li></ul><ul><ul><li>The latest and greatest evolving platform. </li></ul></ul><ul><ul><li>Just one single platform to maintain </li></ul></ul><ul><li>Disadvantages </li></ul><ul><ul><li>Java EE Platform Conversion is more expensive than SRE Migration </li></ul></ul>
  20. 20. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE / Java CAPS Managing Capabilities OS independent. Can be installed on any OS OS dependent. Can be installed only on windows All schemas can be managed from a single dashboard. For opening every schema, we need a separate interface. Will take considerably less time. Takes longer to open a schema. For some of the IB schemas it takes close to an hour Web based so no installation required on every workstation Installation required on each and every workstation JCAPS Enterprise Manager SRE Schema Manager
  21. 21. Billing Per Hour Thank You Thank You

×