© copyright 2009 - Amadeus Nice / all rights reserved / unauthorized use and disclosure strictly forbidden HMC and ESS

© copyright 2009 - Amadeus Nice / all rights reserved / unauthorized use and disclosure strictly forbidden

HMC and ESS


HMCHierarchy 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.


Building a hierarchy

HMC Root

Amex Root

Other root tree

Amex NorthAmerica

Amex Europe

Amex Asia

UK

London

Chelsea

Technical node. Created through WO.

Distributor (L0)

Company (L1)

Division (L2)

LSS

1A QF

EMEA

NCE1A0990Organization

Organization Unit

OfficeFuture enhancement


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


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


Technical nodes - Rules

AMEXNode type Children

ORG OGU

ORG OFF

OGU OGU

OGU OFF

LSS

Rules are static and they are set at technical nodes level.

Node type Children

L0 L0

L0 L1

L1 L2

L2 L2


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.


Applicative nodes - Example

Amex Europe

UK

Group Key Description Value Unicity level

SEP COMCO Cite code XATLXATL Tree

SEP IMGCO Image code COMPANY Node

CSX COMCO Company Profile YJ1RND Tree

CSX PROFST Profile structure 8235846 Node

: User : User

HMCHMC

1: getChildren(SEP, COMCO, XATLXATL, maxDepth, maxCommunity)

2: Ok - List of children

3: getChildren(SEP,IMGCO,COMPANY, maxDepth, maxCommunity)

4: KO - Triple (SEP,IMGCO,COMPANY) not unique in tree


Interfaces

HMC Interfaces Interface

Create node VNODCQ

Get parent node from HMC Id VPNORQ

Get parent node from App Key VPNKRQ

Get children node by HMC Id VCNORQ

Get children from App Key VCNKRQ

Manage applicative key VAPKUQ

Search Community by App key VSAKRQ

Delete node VNODDQ


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).


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



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



ESS Interfaces Interface

Authenticate VLUHLQ

Retrieve Login Area for a User VNOURQ

Change Login Area VLHALQ

Change Password VLUCPQ

Request Reset Password VPCICQ

Confirm Reset Password VPCIUQ

Logout VLSSOQ

Create User VEUSCQ

Delete User VEUSDQ

Retrieve User Details VEULRQ

Self Update User VSEUUQ

Update User (Admin) VEUSUQ

Search User VEUSRQ

Create/Update Policy VPOLCQ

Retrieve Policy VPOLRQ

Documents

© copyright 2009 - Amadeus Nice / all rights reserved / unauthorized use and disclosure strictly forbidden HMC and ESS