B2B Web Service Infrastructure/Architecture. Writen and presented by BOUSQUET-HOURAT BERTRAND

Transcription

1 B2B Web Service Infrastructure/Architecture Writen and presented by BOUSQUET-HOURAT BERTRAND

2 Agenda NM releases / s available Service architecture Publish / subscribe Architecture constraints Conclusion / Q&A 2

3 NM Releases Release Cycle RL 13 RL 13.1 RL 14 RL 14.1 RL 15 RL 15.5 RL 16 RL 16.5 RL 17 RL

4 Operational s 2 platforms Pre-Operational platform (Pre-OPS) for test Operational platform (OPS) 2 services versions Deprecated release: RL 15 Current release: RL 16 RL 15 RL 16 NM B2B Web Service Pre-OPS NMVP Client Application RL 15 RL 16 ATM partner NM OPS 4

5 Operational s B2B Web Services Customers Deprecated versus Current release usage Apr 2011 May 2011 Jun 2011 Jul 2011 Aug 2011 Sep 2011 Oct 2011 Nov 2011 Dec 2011 Jan 2012 Feb 2012 Mar 2012 Apr 2012 Fully migrated Partially migrated Not yet migrated 5

6 SWIM Master Class dedicated 1 additional platform Non-Operational platform for Validation exercise 1 service version (anticipated compare to OPS and pre-ops) Current release: NM 16.5 still under development Exercise ongoing on same platform (SESAR Validation exercise preparation). NM B2B Web Service RL 16.5 NMVP Client Application NMVP ATM partner NM 6

7 Web Services / RPC* Web services paradigm: based on query/reply communication Service s Consumer explicitly requests the service to the provider Asymmetric communication: always initiated by the consumer The provider never sends spontaneously any information Pure client-server example, where: The consumer is the client the one that initiates the communication the active part The provider is the server, the one that waits for requests and serves them the passive part * RPC: Remote Procedure Call² This type of communication is adequate to ask the provider to execute a service 7

8 NM Solutions Simple and Powerful Solutions Based on Query/Reply RPC paradigm is simpler than the publish/subscribe one consumer remains a client application provider remains a server application SLA is well understood. Also, the subscribe part vanished: the consumer requests what it needs when it needs it: access to the NM information is not subject to any preliminary registration only subject to what is exactly required at an exact moment in time. Same way as when querying information in the past: consumer does not need to store the information on its side: NM stores that data already. => duplicate storage is not efficient and not recommended In this paradigm, the consumer polls the NM to get the information that it needs, with two alternatives 8

9 Publish / Subscribe Registration handled by the consumer application Consumer application has a publish/subscribe layer Publish/subscribe layer registers the subscription information (callback, class of information requested) The publish/subscribe layer polls the NM to check if there is new information available When new data is available, the publish/subscribe layer invokes the callback of the upper layer For the upper layer it is as if the Publish/Subscribe is done with the NM This solution can be readily used. No new development by NM. Pub/Sub Layer NM Upper Layer 9

10 Constraints ARO AO AO Software NM Services PreOPS only CFSP Software CFSP AO AO Certificate Not duplicated (1 / end customer / connection) CFSP alone, only PreOPS access User ID and Password associated to each certificate Agreement: 1 to be signed per end user => Listing all certificates Charging 2 free per end customer Admin. fee for subsequent one 10

11 Conclusions B2B Web Services Releases available: SWIM Master Class (on NMVP) => Only NM 16.5 Operational s => NM 15 and NM 16 Web services paradigm based on query/reply Publish/subscribe only via your own intermediate layer Certificates (for Operational usage) Not duplicated (1 / end customer / connection) Only 1 connection per certificate at a time CFSP alone, only PreOPS access 11

12 Questions? Questions? 12