The comForte CSL product is a flexible and powerful messaging middleware framework for the HP NonStop platform. This presentation describes the product on several levels: (1) Elevator pitch (Why/How/What?) (2) Technical Use Cases (Geeky!) (3) Business Cases (4) How to modernize a legacy COBOL application (5) Competing products

1. Copyright comForte 2014
1

2. Copyright comForte 2014
2

3. Copyright comForte 2014
3

4. Copyright comForte 2014
4

5. Copyright comForte 2014
5

6. Copyright comForte 2014
6

7. Copyright comForte 2014
7

8. Copyright comForte 2014
8

9. Copyright comForte 2014
9

10. Copyright comForte 2014
10

11. Copyright comForte 2014
11

12. Copyright comForte 2014
12

13. Copyright comForte 2014
13

14. Copyright comForte 2014
14

15. Copyright comForte 2014
15

16. Copyright comForte 2014
16

17. Copyright comForte 2014
17

18. Copyright comForte 2014
18

19. Copyright comForte 2014
19

20. Copyright comForte 2014
20

21. This is the basic architecture of many Legacy NonStop applications which were designed decades ago.
Pro: Separation of business logic and presentation layer.
Pro: Server classes can be implemented in a rich variety of languages.
Pro: Built-in capability to “scale up” (called dynamic provisioning in cloud computing terms).
Con: If Screen Cobol is used for client code, administrators have to contend with significant limitations in GUI capabilities, and
no language other than Screen Cobol is supported for GUI design.
Con: If Cobol is used for server code, it is getting harder and harder to find skilled Cobol programmers.
Copyright comForte 2014
21

22. Using TUC #1 it is relatively straightforward to present an existing Pathway server as SOAP service to the outside world and
then replace the presentation layer (which was in the Screen Cobol code prior) with a new ‘fat client’.
Pro: SOAP(WSDL) provides a well-defined interface into the HP NonStop system.
Pro: Server classes do not need to be changed.
Con: The SOAP protocol relies on XML, which is a rather heavy-weight way to describe data. This can put unacceptable load
on the HP NonStop system in high-volume environments.
Copyright comForte 2014
22

23. Using the Technical Use Case #3, a three-tier infrastructure can be implemented.
Pro: Server classes do not need to be changed.
Pro: The “Application server” is now running on the mid tier system where more modern and cost-effective development and
deployment is possible. The mid tier system can be virtualized and run on commodity platforms. As the mid tier is “stateless”, it
can be run in several parallel instances, reducing in a high availability and linear scalability.
Copyright comForte 2014
23

24. From Figure 3, the three-tier architecture, it is only a little step to put the “Application server” into a cloud infrastructure.
comForte chose Microsoft Azure as example, but the approach would work just as well in any other Cloud architecture.
Microsoft Azure is a rather powerful IaaS cloud infrastructure. The comForte CSL Azure cloud demo only uses a small part of
the full Azure Cloud infrastructure as shown in this slide. See aforementioned Connect article for more details.
Copyright comForte 2014
24

25. This is how the Microsoft Cloud services connect – on a high level – to the HP NonStop system
Copyright comForte 2014
25

26. This shows some more details - please compare with Figure 3 a few slides back
Copyright comForte 2014
26

27. Copyright comForte 2014
27

28. Copyright comForte 2014
28

29. We tried to honestly and fairly represent the competing products. Any omissions or mistakes, please let us know and we’ll fix
this.
Copyright comForte 2014
29

30. Copyright comForte 2014
30

31. Copyright comForte 2014
31

32. Copyright comForte 2014
32