Dynamische Schnittstellenkommunikation mit CSL JSON/REST und Escort SQL

Size: px

Start display at page:

Download "Dynamische Schnittstellenkommunikation mit CSL JSON/REST und Escort SQL"

Shannon Walker
6 years ago
Views:

1 GTUG presentation Dynamische Schnittstellenkommunikation mit CSL JSON/REST und Escort SQL 19. Oktober 2017 Helmut Bernhard (comforte EMEA Senior Solutions Architect)

2 Can you remember this slide (6 months ago)? > The telecommunications industry (1996) > The banking industry (2010) > Encore - The banking industry (2012) > From M2M to IoT (2014) 2

3 The Incremental Software Architecture is needed! ComForte, customers, implementation partners and the solution partner did: > extensive architecture discovery and analysis to generate an incremental software architecture > Architecture decomposition (structural, behavioural and volatile attributes) > Architecture verification (design substantiation, architecture stresstesting and capacity planning) > To allow an incremental software Architecture following the > EA/Microservices principles and > Satisfies the management & business levels down to the technological & system levels > All needed to overcome lack of interoperability, performance degradation, over expended system federation, low scalability, low reuse and too tight coupling 3

4 What did change the last 6 months? > The caravan moves on. Our new customer projects are moving from: > SOAP JSON/REST > SOAP &.net and stay there (for heavy weighted transactions) > Internal cloud (Azure) > Homebanking Open Banking API > Regulated Banking Deregulated Banking (e.g. PSD2 Banking API (PISP/AISP/XS2A) > Isolated reservation systems JSON/REST enabled > Rigid Internal systems partner access via JSON/REST > Test environments Persistent Application including NonStop SQL MP/MX > Monolithic apps Scalable solutions > Simple GUIs Responsive design (HTML5) > Legacy Server Mixed client/server setups 4

CSL - Client Server Link - base architecture description > The CSL Manager is a NonStop process pair which oversees the TCP listener processes (i.e., starts, stops and monitors the CSL TCPs and is able to restart the TCP listener in its backup CPU).

5 CSL - Client Server Link - base architecture description > The CSL Manager is a NonStop process pair which oversees the TCP listener processes (i.e., starts, stops and monitors the CSL TCPs and is able to restart the TCP listener in its backup CPU). > The TCP listener process provides the communication layer of CSL Base through which access to applications on NonStop is gained. The CSL TCP listens on a TCP/IP port assigned to the CSL TCP for incoming connection requests coming from remote clients. Once a connection request has arrived it is forwarded to a CSL Executor process which establishes the TCP/IP session with the remote client. Multiple TCPs can be started (listening to multiple ports) and each TCP can have executors running in every CPU. > The REST wrapper handles the mapping from JSON to the message expected by the application; it is a Pathway server and inherits all the scalability and availability provided by Pathway. > CSL Studio is a development tool which enables rapid deployment of NonStop applications as a REST Web service by consuming the DDL of the application and producing client consumable documents and by deploying a REST wrapper to the NonStop to act as a gateway between the NonStop and the remote facility. 5

CSL - Client Server Link - REST Server overview CSL REST Server on NonStop means, that there is NO application code change for the Application Server/Pathway environment and CSL protects customer s

6 CSL - Client Server Link - REST Server overview CSL REST Server on NonStop means, that there is NO application code change for the Application Server/Pathway environment and CSL protects customer s investment in NonStop application logic > For development you can use for example the Pathway CSL Echo server and on the client side our customers using the OpenSource Tool SoapUI (has also REST functionality) 6

7 CSL - Client Server Link - REST Server Advanced Design Possibilities > Adding a specific REST-API > This has the following advantages > Give the REST API a distinct version id and its subordinate resources distinct names instead of using default names > Offer the HTTP GET verb in addition to the POST verb for accessing a resource > Specify HTTP query parameters being populated at runtime within the corresponding request message to the back-end server > Using message views > One of the main reasons is: > Hiding data items from the REST client and also allowing these hidden items to contain correct values at runtime is supported by CSL REST using message views and message defaulting > Using TMF > If the interactions with a back-end server initiated by a REST client must be monitored using TMF then the following options are available with CSL REST: > The control over the TMF transactions (i.e. begin, resume and terminate TMF transactions) is given to the REST client > The TMF transaction is controlled by the CSL REST wrapper outside the control of the REST client. 7

CSL - Client Server Link - REST Client Lite overview > With CSL REST Client lite an easy way to convert the

DOM library (supports C/C++ clients) > JSON content is produced and processed by customer (via JSON DOM Lib

> The interaction with the remote Server is done via the CSL REST Client Proxy (Pathway Server Class) and with

8 CSL - Client Server Link - REST Client Lite overview > With CSL REST Client lite an easy way to convert the NonStop environment to a REST client is offered, consisting of: > HTTP Client Proxy > API library and a > JSON DOM library (supports C/C++ clients) > JSON content is produced and processed by customer (via JSON DOM Lib functions). > The interaction with the remote Server is done via the CSL REST Client Proxy (Pathway Server Class) and with the help of the GET and POST functions, offered from the http API > Cloud connections (e.g. Microsoft Azure) are supported Today

Full blown CSL NonStop REST Client > A full blown CSL NonStop REST Client is currently in beta and will support - besides WSDL - the Swagger/OpenAPI format for service contracts > Content support for

9 Full blown CSL NonStop REST Client > A full blown CSL NonStop REST Client is currently in beta and will support - besides WSDL - the Swagger/OpenAPI format for service contracts > Content support for JSON and XML > Full integration in CSL Studio (supports MS VS. and Eclipse) > Furthermore COBOL applications are also supported besides C/C++ > This is the foundation for upcoming IoT, PSD2 and Open Banking API s, i.e. to design and implement the respective scenarios (e.g. EU-PSD2 AISP/PISP/XS2A) based on recommendations like the upcoming The Berlin Group implementation framework regarding PSD2 and over IoT frameworks like OPC UA, ETSI IoT, etc. 9

10 Example Open Banking API "balances": Response Body Parameters: "groupheader": "creationdatetime": " T06:44:00Z", "httpcode": 200, "messageidentification": "wgjkcyetftk" "response": "accounts": [ "id": "FI EUR", "account": "identification": "country": "FI", "iban": "FI " "currency": "EUR", "owner": "name": "Oy cccompany AB" "product": "SHEKKITILI", "type": "CACC" [ "amount": "123.60", "type": "ITAV" "amount": "111.50", "type": "ITBD" } ], "links": [ "href": "/v1/accounts/fi eur", "rel": "details" "href": "/v1/accounts/fi eur/transactions", "rel": "transactions" } ] "id": "FI EUR", "account": "identification": "country": "FI", "iban": "FI " "currency": "EUR", "owner": "name": "Firm OY" 10

11 Example Open Banking API (cont) > Example balance enquiry ] } "response": "account": "id": "FI EUR", "account": "identification": "country": "FI", "iban": "FI " "currency": "EUR" "links": [ "href": "/v1/accounts/fi eur", "rel": "details" "href": "/v1/accounts/fi eur/transactions", "rel": "transactions" "continuationkey": " ", "transactions": [ "id": " ", "entryreference": " ", "amount": "currency": "EUR", "value": "100.00" "bookingdate": "date": " " "creditdebitindicator": "CRDT", "entrydetails": "transactiondetails": "relatedparties": "debtor": "name": "Matti xxxxäläinen" } } } "valuedate": "date": " " } 11

Escort SQL Overview > Escort SQL is the fastest, lowest cost and lowest risk method for converting applications and data from Enscribe to SQL. > No need to rewrite your programs to convert to SQL.

12 Escort SQL Overview > Escort SQL is the fastest, lowest cost and lowest risk method for converting applications and data from Enscribe to SQL. > No need to rewrite your programs to convert to SQL. Convert to SQL in weeks, not months and years > Use Escort SQL to shorten legacy system development times. Example: Change a field definition from YYMMDD to YYYYMMDD and recompile only the programs that need the new definition > Deploy third party ODBC and JDBC tools, such as Microsoft Tools, open source tools and hundreds of other commercially available products. > An Escort SQL migration converts the legacy system in small, manageable and quick increments. Migrate the database one file at a time to SQL, with no reprogramming. Migrate the application one program at a time to native SQL. 12

Step One DB conversion > In many cases, today's Enscribe files were not originally designed as the "clean", normalized databases that we all would prefer > Escort SQL gives you a second chance to

13 Step One DB conversion > In many cases, today's Enscribe files were not originally designed as the "clean", normalized databases that we all would prefer > Escort SQL gives you a second chance to change all those things you don't like about your existing files in the process of converting them to SQL. Expand or eliminate fields and reformat compressed data (i.e. an example is dates with current YYMMDD or other formats being expanded into fully millennium compliant dates) 13

Step Two DB loading > Our high-speed parallel database loader loads the existing Enscribe data into the new SQL tables very efficiently, using all the rules you have supplied about how

14 Step Two DB loading > Our high-speed parallel database loader loads the existing Enscribe data into the new SQL tables very efficiently, using all the rules you have supplied about how the data is to be transformed > Once your production data is loaded into the tables, these same transformation routines will be used at runtime to successfully READ and WRITE the data 14

When that happens, comforte Escort SQL kicks into action.

15 Step Three - Enscribe/SQL Emulation > When an Enscribe programs requests to open a file, comforte Escort SQL will detect when your programs attempt an Enscribe operation against a SQL table. When that happens, comforte Escort SQL kicks into action. From that point on, comforte Escort SQL will do all I/O to that file on behalf of that program > As mentioned before, the program can't tell that the file(s) have been changed to SQL. This means you can change one file to SQL or change them all. 15

Development > Acquisition > Customers work with comforte because they need to > Lower Cost of Operations of HP Nonstop Applications > Lower

16 Why comforte as a partner? > 30+ years experience in HP NonStop server market place > the largest HPE Nonstop ISV > Growing Solution Set through > In-house Development > Acquisition > Customers work with comforte because they need to > Lower Cost of Operations of HP Nonstop Applications > Lower Operational Risk by enhancing data protection and overall security > Support New Business Initiatives driving new application developments > Better integrate HP Nonstop within Enterprise IT > Understand the strategic importance of HP Nonstop in their Enterprise 16

comforte - contacts Andreas Lutz Senior Key

Neuruppin, Germany Tel: +49-176-24481915 Helmut

Lincoln Str. 22 65189 Wiesbaden, Germany Tel.

17 comforte - contacts Andreas Lutz Senior Key Account Manager Alte Ruppiner Allee Neuruppin, Germany Tel: Helmut Bernhard Senior Solutions Architect Abraham Lincoln Str Wiesbaden, Germany Tel.: a.lutz@comforte.com h.bernhard@comforte.com 17

GTUG presentation comforte s solutions in the modernisation arena. 27 April 2017, Helmut Bernhard (comforte EMEA Senior Solutions Architect)

GTUG presentation comforte s solutions in the modernisation arena 27 April 2017, Helmut Bernhard (comforte EMEA Senior Solutions Architect) Every industry has it s modernisation wakeup calls > The telecommunications