Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyATLAS-1836

...

Forward to Area 1 2 - Assets and Connectors ==>

...

 

In the Atlas build, model files are added in alphanumeric order to build up the type library.  Therefore the model files are numbered to ensure its dependencies have been resolved before a model file is loaded.   For the open metadata types, the model file number is shown in package name to document the intended load order.  The numbering scheme of the metadata areas described in Building out the Apache Atlas Open Metadata Typesystem provides the high-level numbering system.  For example, area 1 has models 0100-0199, area 2 has models 0200-299, etc.   Each area's sub-models are dispersed along its range, ensuring there is space to insert additional models in the future.

...

Servers describe the middleware servers (such as application servers, data movement engines and database servers) that run on the Hosts.   Within the server model we capture its userId. Most metadata repositories are run in a secure mode requiring incoming requests to include the requester’s security credentials.  Therefore we have an identifier for each unique logged on security identity (aka userId).  This identity is recorded within specific entities and relationships when they are created or updated.  By storing the user identifier for the server, it is possible to correlate the server with the changes to the metadata (and related data assets) that it makes. 

See model 0310 Actors in Area 3 for details of how user identifiers are correlated with people and teams).

Figure 9: Servers and their connectivity and capabilities

Open metadata may also capture the network endpoint(s) that the server is connected to and the host it is deployed to.

The endpoint defines the parameters needed to connect to the server.  It also features in the Connection model used by applications and tools to call the server.  Thus through the endpoint entity it is possible to link the connection to the underlying server.

Within the server are many capabilities.  These range from full applications (see 0060 below0170 in Area 1) to security plugins to logging and encryption libraries.  Different organizations and tools can choose the granularity in which the capabilities are captured in order to provide appropriate context to data assets and the decisions made around them.

...