SCORT and CRM. To quickly integrate your Mainframe applications with CRM

Transcription

1 1 1 SCORT and CRM To quickly integrate your Mainframe applications with CRM

2 CRM - Mainframe integration 2 2 Look after your customers: Everyone wishes and needs to do it CRM software products offer numerous options but they are not designed to easily connect to existing Mainframe applications ( and without the customer information held in the existing systems a great deal of valuable knowledge would be ignored...!)

3 CRM - Mainframe integration 3 3 Mainframe applications can be considered as operating in two modes: Business Logic mode which applies business rules to the data Presentation mode which applies presentation logic to the data to create terminal interaction The two modes are often inter-twined and this often prevents the integration of the applications with CRM systems. As a result, this integration requires re-writing the applications

4 CRM - Mainframe integration 4 4 A CRM project is a major initiative Integration with existing applications often implies a hidden project (which can be unmanageable) to re-write the applications : Technically complex Often under-estimated Interdependance of transactions Batch processing requirements Tendancy to underestimate the effort required to re-write even where little new functionality is involved

5 5 5 The 3 pratical methods EAI Bus Integration the Rolls Royce Direct Integration without the EAI Bus Integration though the user interface dare to take a less expensive route!

6 6 6 EAI Bus: the Rolls Royce approach Often the CRM project is joined with the implementation of an EAI Bus This is the real Rolls Royce approach : CRM and the integration of the existing information system... Application services shared and accessible by everyone (CRM initially, Call centre ) CRM Applicat. X Applicat. Y Mainframe EAI Bus IMS CICS

7 EAI Bus: the Rolls Royce approach 7 7 The Rolls Royce approach... Yes, BUT A minor detail is often forgotten or under estimated: The costs and the delay from re-writing mainframe services (accounting, batch integration etc.) EAI Bus to Mainframe connectors are frequently not well developed... (a Cobol record, is nothing like XML ) CRM Applicat. X EAI Bus Applicat. Y Mainframe IMS CICS

8 8 8 CRM, EAI & SCORT e-business Integrator 3270 Access without re-writing High performance connector architecture Mainframe 3270 IMS CICS e-business Integrator A.O. CRM Applicat. X JMS GTW A.O. DKLink IMS CICS EAI Bus A.O. = Access Object

9 CRM, EAI & SCORT e-business Integrator 9 9 SCORT e-business Integrator supports: Integration of existing 3270 applications (without re-writing) Highly efficient integration with comprehensive tools (including testing and debug utilities) All the development tools required to build, debug, test and deploy business objects. An indispensable complement to any EAI project ensuring the feasibility and timely completion...

10 CRM and direct integration 10 Faced with the total cost of CRM & EAI systems, the CRM vendors have developed a new strategy: Directe integration (without the EAI Bus) Does it help? What is the difference? Is it any easier to integrate current systems? NO - the fundamental problem remain: Cost of re-writing applications applications Poor connector components in service mode

11 11 11 Direct integration & e-business Integrator and always Access without re-writing High performance connector architecture Mainframe 3270 IMS CICS e-business Integrator A.O. CRM Java Integration A.O. DKLink IMS CICS

12 12 12 Integration though the user interface Dare to take the less expensive route! There is a third way: Integration though the user interface Admittedly can be less powerful But much less expensive!!! But much more quickly!!! And without a doubt quite sufficient in the majority of cases

13 Integration though the user interface 13 How does it work? Build HTML links to the Mainframe elements in the user interface of the CRM system On clicking an HTML link : A Mainframe session is opened (or used if already open) Navigate through the session or use an Access Object to do the work Execute the Mainframe service (1 or n screens) The user can navigate as desired through the re-engineered screens SCORT e-business Integrator has a number of features to support the development of this approach in a very short time.

14 Integration via user interface: a demo? A sample CRM screen might offer three services from an existing Mainframe system: 14 14

15 Integration via user interface: demo (2) When the List Customer button is clicked, a request is sent to SCORT e-business Integrator SCORT e-business Integrator opens a Mainframe session and automatically goes to the first screen list

16 Integration via user interface: demo (3) Clicking on the customer id with the ID in parameter SCORT e-business Integrator picks up the Mainframe session and quickly (after testing the state) moves to the right screen 16 16

17 Integration via user interface: demo (4) Clicking «customer id» with the ID in parameter, but the ID is invalid SCORT e-business Integrator picks up the Mainframe session and will get the message No Such Customer The user can easily take control of the Mainframe session and complete the operation

18 18 18 Integration via user interface: demo (5) Very easy! 123 Can be mixed with the functions of application publication using SCORT e-business Integrator JSP reformatting Complex AO (rebuilding the GUI of the application) PRINTING through PDF For information The demo above was made in less than 2 days!

19 SCORT and CRM : The benefits 19 Support for many Mainframe architectures Support for mixed transactions on the S/390 - zseries No modification of the Mainframe at all: seamless integration Very powerful development, maintenance and testing utilities. Easy to use and control 3 possible methods of integration as required for the best combination of quality and price