1 / 23

PCS Web Services v.6: Concept Changes

This document outlines the concept changes for PCS Web Services version 6, including architectural improvements, better test coverage, and unified model mapping configuration. It also covers trivial changes, schema updates, and new operations.

varney
Download Presentation

PCS Web Services v.6: Concept Changes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PCS Web Services v.6 Envelope concept changes Jana Karcheska, Valerija Velinovska 2019-03-07, Vienna

  2. PCS Team (1) Valerija Velinovska Technical Coordinator Gorazd Titizov Project Manager, Scrum Master Jana Karcheska Architect, Product Owner Proxy Mate Back Product Owner

  3. PCS Team (2) Ignatij Gichevski Software Engineer Hristijan Dimitrieski Technical Coordinator Trajche Naumoski Senior Software Engineer Aleksandra Hristov UX Architect Aleksandar Cindrikj Senior UX Engineer

  4. PCS Team support Aleksandar Petreski Senior System Engineer Slavcho Trnkovski Senior Database Administrator App Support Team (24/7)

  5. New URL(s) • Test system • https://pcstest3.rne.eu/pcs/services/PcsWebServices_v6?wsdl • Production system (not yet available) • https://pcs-online.rne.eu/pcs/services/PcsWebServices_v6?wsdl

  6. Authentication Request AuthenticateData is removed HTTP “X-Authorization”header should be sent with each request instead JSON Web token expires at 3AM every day

  7. Web Service spring cleaning Upgrade to latest libraries versions Architectural improvements Better test coverage Unified model mapping configuration between web service model and domain Unified authorization between web service layer and domain

  8. Trivial changes (1) • Complex types in CamelCase • elements_underscored Why is this important: remove complex mappings to our Java domain code and consistency Request/Response elements are not changed to underscore notation from pragmatic reasons as they are too many and are not mapped to domain objects

  9. Trivial changes (2) • Removed previous versions target namespaces • Everything is now under http://eu/rne/pcs-online/WebServices-v6/types • Remove obsolete operation that were not implemented or used • createDossier • getRegBodiesForIMAgency • getProdAgencyUserDataForDossier • getIMUserDataForDossier etc.

  10. Changes in Trasse schema type type processingStatus managedByPcs

  11. Changes in TrasseElementschema type Alternative Origin Departure time zoneoffset Arrival manualoffset Alternative Destination Departuremanualoffset Arrival time zoneoffset Construction Starting Point

  12. Changes in TrasseElementschema type Earliest/Latest Arrival Offset Reference point Earliest/Latest Departure Offset Traffic periodId

  13. Changes in TrasseElementschema type Use separate Agency Id fields for responsible RU and IM Minimum Dwell period time is defined in minutes Responsible IM Id Agency Agency Id Min DwellPeriod Time Responsible RU Agency Id

  14. All catalogue fields in separate type UsedCatalogueData All catalogue fields in catalogue dossiers in separate type CatalogueData All train parameters are in a separate type TrainParameters All times and offsets are in a separate type Times Changes in TrasseElement schema type

  15. Pathfinderintegration root element renamed to WsDossierContainer Complex type defined to combine the choice between Agency PCS or Non PCS (UIC) ID Other important changes in types

  16. Calendar inconsistency error code for acceptance indicator update to green Incorrect responsible RU/IM pair of id’s for path section Several status codes regarding acceptance indicator, production and commercial progress status fields set inappropriately Additional error codes could be expected New Error codes

  17. Change to the running days in existing sub-path New sub-paths with defined running days New EC behavior – Switch calendar

  18. The system shall downgrade the acceptance indicator of the RU responsible in a neighbor territory when at least one of the following changes occur on the Border: a) operation point b) arrival or departure time c) manual or time zone offset – in case it is done on the Border, otherwise an offset change in the middle of the Sub-path will trigger running days change d) dwell time e) running days f) alternative origin or destination New EC behavior – Acceptance Indicators downgrade

  19. TsiTrainIdelement will be moved from dossier to path element. All paths that belong to one TSI Variant will have the same TsiTrainId but they will have different TsiPathId. TSI Identifiers

  20. TSI Identifiers and new schema types

  21. New Operations • GetPathVariants • To be used by RNE for warehouse • To be used by anyone who needs to get timetable combinations constructed by PCS • CreateUserVariant • Used by leading RU in Open phase • UpdateUserVariant • Used by leading RU in Open and Harmonization • GetTsiVariants • Used by TIL or RU’s integrated via PCS without CI/TIL

  22. PCS Web service v.6 Timeline

  23. Hands-on Demo Questions & Answers

More Related