Eaiesb Migration Approach
3 likes•593 views
The document discusses different approaches for migrating from an older SeeBeyond eGate 4.5.X system to the newer Java CAPS platform. It describes using the Schema Run-time Environment (SRE) which allows running existing 4.X components without conversion. It also outlines the process of fully converting components to the new Java CAPS platform, including rewriting collaborations and business processes. The benefits and disadvantages of each approach are provided.
Eaiesb Migration Approach
- 1. Billing Per Hour EAIESB
- 2. Billing Per Hour EAIESB - SeeBeyond Migration Approach
- 3. Billing Per Hour EAIESB - SeeBeyond Migration Approach - eGate 4.5.X
- 4. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE
- 5. Billing Per Hour EAIESB - SeeBeyond Migration Approach - eGate/SRE System Diagram
- 6. Billing Per Hour EAIESB - SeeBeyond Migration Approach - ICAN
- 7. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Java CAPS
- 8. Billing Per Hour EAIESB - SeeBeyond Migration Approach - eGate 4.5.X Coding Primarily Monk Code using eGate integrator Java use was limited Developer's were not Java programmers Designer was limited to mostly drag-and-drop Operations rather than having full access to the code
- 9. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Why SRE Why SRE? Java technology back end appealing JMS messaging compatible across platforms Better access to collaboration code and tools Projects on logical hosts not dependent on repository once running More flexible project design with services running under application servers Benefits of SOA Opportunity to redesign critical interfaces to become more flexible .
- 10. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE Architecture
- 11. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Why SRE Schema Run-time Environment (SRE) — For upgrades from 4.5.x Java CAPS Add-on that makes it possible to run 4.x Components in 5.X Existing configuration (Collaborations, ETDs, Schemas, etc) can be run as is without change Need to Export and Import the Schemas Run-time environment can be viewed and controlled through 5.1 Enterprise Manager SRE Monitor Java Message Service (JMS) Messages can be sent/received to/from 5.1 4.x run-time environment and editors rebuilt for 5.1 interoperability Conversion avoided
- 12. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
- 13. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
- 14. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE Benefits Instant No need to re-compile ETDs or Collaborations No need to re-write existing Monk or Collaboration for the Java Programming Language Components in the SRE interact with each other and with external systems with the same functionality that existed prior to upgrading Seamless Data Exchange Publish/subscribe to SRE Schema from Java EE Platform Project Publish/subscribe to Java EE Platform Project from SRE Schema
- 15. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE Benefits Unified Monitoring (SRE, only) Web-based monitoring, same as for Java EE Platform/Project components Familiar Maintenance Continued maintenance of SRE components with familiar tools No Impact on Future Development New Java EE Platform Projects can be developed without affecting SRE components
- 16. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Converting eGate 4.5.X to Java CAPS
- 17. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Java CAPS Suite of Sun products entirely built on Java EE Platform and other standards Product architecture, design paradigm and runtime environment are completely different from 4.x and 3.6.x 4.5.x components (Collaborations, ETDs, Business Processes, Schemas, etc.) have to be converted into 5.x Java EE Platform components (Java Technology/XSLT Collaborations, Business Processes, OTDs, Connectivity Maps, Deployments Profiles, Environments, Projects). Requires significant code changes/re-writes.
- 18. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Conversion Steps Use available meta data (DTD, XSD, WSDL, Cobol Copybook, etc.) to build respective 5.1 OTDs User-defined, database, and other ETDs have to be rebuilt into 5.1 OTDs 4.5.x Collaborations for the Java Programming Language have to be re-written using existing data mappings, transformations and other business rules Monk Collaborations have to be re-written into Java Programming Language
- 19. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Conversion Steps 4.5.x Business Processes have to be re-designed. 5.x eInsight Business Process Manager (BPM) has been completely re-engineered and now BP flow is controlled by BPEL Monk-based eWay Adaptors and Java Technology Connection Points have to be re-built. In 5.x connectivity parameters are divided into two groups: Connectivity Map and Environment Need to re-consider scalability, deployment, user management and ACL options
- 20. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Benefits Highly scalable Java EE Platform 1.4 compliant platform featuring JMS API 1.1, JCA 1.5 Transaction support: JTA 1.0.1and JTS 1.1 Other Java technologies Create SOA and composite applications Take advantage of new products: eVision Studio, eBAM Studio, eTL Integrator, eView Studio Integrate with Java Enterprise System (Java ES) products (5.1.x) Sun Java System Portal Server, Sun Java System Access Manager, Sun Java System Directory Server Support for multiple Application Servers (5.1.x) Sun Java System Application Server 8.1 EE, Websphere 6, Weblogic 9, JBOSS
- 21. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrade Advantages & Disadvantages Advantages Protects investments in 4.5.x. Easiest and less expensive way to upgrade to 5.x Disadvantages Requires to maintain two platforms: SRE and Java EE Platform SRE is a “frozen” platform: will never evolve Cannot create SOA and Composite Applications
- 22. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
- 23. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
- 24. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
- 25. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Publish / Subscribe to SRE Configure JMS API queues or topics as usual in the Java EE Platform Project Deploy queues or topics to a Java EE Platform JMS API IQ Manager with configuration matching that of the SRE JMS API IQ Manager
- 26. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
- 27. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Publish / Subscribe to Java CAPS Create eWay Adaptor Connection in SRE Schema that points to the Java EE Platform JMS API IQ Manager
- 28. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Monitoring from Java CAPS Component status shown when component is selected in browser Components can be started/stopped
- 29. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Upgrading to SRE
- 30. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE and Java CAPS at Runtime
- 31. Billing Per Hour EAIESB - SeeBeyond Migration Approach - SRE and Java CAPS at Runtime
- 32. Billing Per Hour EAIESB - SeeBeyond Migration Approach - Conversion Advantages and Disadvantage Advantages The latest and greatest evolving platform. Just one single platform to maintain Disadvantages Java EE Platform Conversion is more expensive than SRE Migration
- 33. 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
- 34. Billing Per Hour Thank You Thank You