1 / 14

HMC and ESS

HMC and ESS. HMC Hierarchy Management Component. What is HMC ?. HMC is used to manage hierarchies such as trees. Central point that is shared by different applications in Amadeus. Application Identifiers can be stored at node level. Technical node. Created through WO. Building a hierarchy.

kim
Télécharger la présentation

HMC and ESS

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. HMC and ESS

  2. HMCHierarchy Management Component

  3. What is HMC ? • HMC is used to manage hierarchies such as trees. • Central point that is shared by different applications in Amadeus. • Application Identifiers can be stored at node level.

  4. Technical node. Created through WO. Building a hierarchy HMC Root Amex Root LSS Other root tree Amex Europe Amex North America Amex Asia 1A QF Distributor (L0) EMEA Company (L1) UK Division (L2) NCE1A0990 Organization London Organization Unit Future enhancement Office Chelsea

  5. Technical nodes • The technical nodes are used to store node types and rules for the tree. • For Amex, node types are L0, L1 or L2 • For Amex, rules are : • L0 can have L0 or L1 as children • L1 can only have L2 as children • L2 can have L2 as children

  6. Technical nodes • For LSS, node types are ORG, OGU or OFF • For LSS, rules are : • ORG can have OGU or OFF as children • OGU can have OGU or OFF as children • OFF cannot have children

  7. Technical nodes - Rules AMEX LSS • Rules are static and they are set at technical nodes level.

  8. Applicative nodes • The applicative nodes represent all the nodes but the technical ones. • Applicative key/value can be stored at applicative node level. The value should be an applicative identifier • Apart of applicative key/value and label, nothing is stored at node level. It is a pure hierarchy where a node only knows its parent and its children. • Key/value are ‘signed’. They belong to a group (SEP, CSX, SBR, …). They form a triple (Group, Key, Value) or also called Applicative Key. • Unicity at node/tree level for a triple is customizable.

  9. Applicative nodes - Example Amex Europe UK

  10. Interfaces

  11. Conclusion • Application may interface with HMC using their own identifier so called triple. • Application also has the ability to interface with HMC using the internal HMC Id. • HMC has a customizable way to manage unicity for triple at node and tree level. • HMC does not own any data apart from Ids. Even the label of the node is not stored in HMC (at least for AMEX project).

  12. Extended Security Server • ESS is the user management part • It is used to manage the users and their roles • It is also used for authentication and password management

  13. Extended Security Server • ESS is the user management part • It is used to manage the users and their roles • It is used for authentication and password management • It is used to manage the policy

  14. Extended Security Server

More Related