Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Remove Connected Asset OMAS and fix assemblies
Signed-off-by: Mandy Chessell <mandy_chessell@uk.ibm.com>
  • Loading branch information
mandy-chessell committed May 14, 2019
1 parent 44bd54f commit 7421e28
Show file tree
Hide file tree
Showing 120 changed files with 450 additions and 15,225 deletions.
1 change: 0 additions & 1 deletion CODEOWNERS
Validating CODEOWNERS rules …
Expand Up @@ -27,7 +27,6 @@ open-metadata-implementation/governance-servers @mandy-chessell
open-metadata-implementation/access-services @mandy-chessell
open-metadata-implementation/access-services/asset-consumer @mandy-chessell
open-metadata-implementation/access-services/asset-owner @mandy-chessell
open-metadata-implementation/access-services/connected-asset @mandy-chessell
open-metadata-implementation/access-services/community-profile @mandy-chessell
open-metadata-implementation/access-services/digital-architecture @mandy-chessell
open-metadata-implementation/access-services/enterprise-architecture @mandy-chessell
Expand Down
25 changes: 17 additions & 8 deletions Content-Organization.md
Expand Up @@ -15,7 +15,6 @@ The Egeria content is organized into the following modules:
* **[asset-consumer](open-metadata-implementation/access-services/asset-consumer)** - create connectors to access assets.
* **[asset-owner](open-metadata-implementation/access-services/asset-owner)** - manage metadata and feedback for owned assets.
* **[community-profile](open-metadata-implementation/access-services/community-profile)** - manage personal profiles and communities.
* **[connected-asset](open-metadata-implementation/access-services/connected-asset)** - provide metadata about assets for the connectors.
* **[data-engine](open-metadata-implementation/access-services/data-engine)** - exchange metadata with a data processing engine.
* **[data-platform](open-metadata-implementation/access-services/data-platform)** - exchange metadata with a data platform.
* **[data-privacy](open-metadata-implementation/access-services/data-privacy)** - support a data privacy officer.
Expand All @@ -37,8 +36,12 @@ The Egeria content is organized into the following modules:
* **[authentication-plugins](open-metadata-implementation/adapters/authentication-plugins)** support extensions to technology such as LDAP that are used to verify the identity of an individual or service requesting access to data/metadata.
* **[governance-engines-plugins](open-metadata-implementation/adapters/governance-engines-plugins)** support plugins to governance engines to enable them to use open metadata settings in their validation and enforcement decisions, and the resulting actions they take.
* **[open-connectors](open-metadata-implementation/adapters/open-connectors)** are connectors that support the Open Connector Framework (OCF).
* **[connector-configuration-factory](open-metadata-implementation/adapters/open-connectors/connector-configuration-factory)** creates **Connection** objects to configure the open connectors.
* **[access-services-connectors](open-metadata-implementation/adapters/open-connectors/access-services-connectors)** contains the topic connector implementations for each of the access services that support inbound events through an InTopic.
* **[configuration-store-connectors](open-metadata-implementation/adapters/open-connectors/configuration-store-connectors)** contains the connectors that manage the open metadata configuration.
* **[connector-configuration-factory](open-metadata-implementation/adapters/open-connectors/connector-configuration-factory)** creates **Connection** objects to configure the open connectors.
* **[data-store-connectors](open-metadata-implementation/adapters/open-connectors/data-store-connectors)** contain OCF connectors to data stores on different data platforms.
* **[event-bus-connectors](open-metadata-implementation/adapters/open-connectors/event-bus-connectors)** supports different event/messaging infrastructures. They can be plugged into the topic connectors from the access-service-connectors and repository-service-connectors.
* **[governance-daemon-connectors](open-metadata-implementation/adapters/open-connectors/governance-daemon-connectors)** contains connectors for the governance daemon servers that monitor activity or synchronize metadata and configuration asynchronously between different tools.
* **[repository-services-connectors](open-metadata-implementation/adapters/open-connectors/repository-services-connectors)** contains connector implementations for each type of connector supported by the Open Metadata Repository Services (OMRS).
* **[audit-log-connectors](open-metadata-implementation/adapters/open-connectors/repository-services-connectors/audit-log-connectors)** supports different destinations for audit log messages.
* **[cohort-registry-store-connectors](open-metadata-implementation/adapters/open-connectors/repository-services-connectors/cohort-registry-store-connectors)** contains connectors that store the cohort membership details used and maintained by the cohort registry.
Expand All @@ -48,21 +51,27 @@ The Egeria content is organized into the following modules:
* **[inmemory-repository-connector](open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/inmemory-repository-connector)** - provides a local repository that is entirely in memory. It is useful for testing/developing OMASs and demos.
* **[omrs-rest-repository-connector](open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/omrs-rest-repository-connector)** - enables IBM Information Governance Catalog to support open metadata.
* **[ibm-igc-repository-connector](open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/ibm-igc-repository-connector)** - uses the OMRS REST API to call an open metadata conformant repository.
* **[configuration-store-connectors](open-metadata-implementation/adapters/open-connectors/configuration-store-connectors)** contains the connectors that manage the open metadata configuration.
* **[event-bus-connectors](open-metadata-implementation/adapters/open-connectors/event-bus-connectors)** supports different event/messaging infrastructures. They can be plugged into the topic connectors from the access-service-connectors and repository-service-connectors.
* **[governance-daemon-connectors](open-metadata-implementation/adapters/open-connectors/governance-daemon-connectors)** contains connectors for the governance daemon servers that monitor activity or synchronize metadata and configuration asynchronously between different tools.
* **[data-store-connectors](open-metadata-implementation/adapters/open-connectors/data-store-connectors)** contain OCF connectors to data stores on different data platforms.
* **[rest-client-connectors](open-metadata-implementation/adapters/open-connectors/rest-client-connectors)** contains connector implementations for issuing REST calls.
* **[admin-services](open-metadata-implementation/admin-services)** - supports the configuration of the OMAG Server Platform. This configuration determines which of the open metadata and governance services are active.
* **[common-services](open-metadata-implementation/common-services)** - support modules that are reused by other services.
* **[ffdc-services](open-metadata-implementation/common-services/ffdc-services)** - provides base classes and validation for First Failure Data Capture (FFDC).
* **[metadata-security](open-metadata-implementation/common-services/metadata-security)** - provides integration points for fine-grained security for metadata.
* **[multi-tenant](open-metadata-implementation/common-services/multi-tenant)** - provides management of server instances within the OMAG Server Platform.
* **[ocf-metadata-management](open-metadata-implementation/common-services/ocf-metadata-management)** - provides metadata management for the [Open Connector Framework (OCF)](open-metadata-implementation/frameworks/open-connector-framework) properties and APIs.
* **[repository-handler](open-metadata-implementation/common-services/repository-handler)** - provides an enhanced set of services for accessing metadata from the [repository services](open-metadata-implementation/repository-services).
* **[frameworks](open-metadata-implementation/frameworks)** - frameworks that support pluggable components.
* **[open-connector-framework](open-metadata-implementation/frameworks/open-connector-framework)** provides the interfaces and base implementations for components (called connectors) that access data-related assets. OCF connectors also provide detailed metadata about the assets they access.
* **[open-discovery-framework](open-metadata-implementation/frameworks/open-discovery-framework)** provides the interfaces and base implementations for components (called discovery services) that access data-related assets and extract characteristics about the data that can be stored in an open metadata repository.
* **[governance-action-framework](open-metadata-implementation/frameworks/governance-action-framework)** provides the interfaces and base implementations for components (called governance actions) that take action to correct a situation that is harmful the data, or the organization in some way.
* **[governance-servers](open-metadata-implementation/governance-servers)** - servers and daemons to run open metadata and governance function.
* **[admin-services](open-metadata-implementation/governance-servers/admin-services)** - the admin services support the configuration of the OMAG Server Platform. This configuration determines which of the open metadata and governance services are active.
* **[discovery-engine-services](open-metadata-implementation/governance-servers/discovery-engine-services)** - supports automated metadata discovery.
* **[open-lineage-services](open-metadata-implementation/governance-servers/open-lineage-services)** - provides historic warehouse for lineage.
* **[security-sync-services](open-metadata-implementation/governance-servers/security-sync-services)** - supports automated configuration of security engines.
* **[server-chassis](open-metadata-implementation/governance-servers/server-chassis)** - the server chassis provides the server framework for the OMAG Server Platform.
* **[stewardship-services](open-metadata-implementation/governance-servers/stewardship-services)** - supports automated stewardship actions.
* **[virtualization-services](open-metadata-implementation/governance-servers/virtualization-services)** - supports automated stewardship actions.
* **[platform-services](open-metadata-implementation/platform-services)** - the platform services support REST APIs for the OMAG Server Platform.
* **[repository-services](open-metadata-implementation/repository-services)** - metadata exchange and federation - aka the Open Metadata Repository Services (OMRS).
* **[server-chassis](open-metadata-implementation/server-chassis)** - the server chassis provides the server framework for the OMAG Server Platform.
* **[user-interfaces](open-metadata-implementation/user-interfaces)** - browser based user interfaces.
* **[access-services-user-interface](open-metadata-implementation/user-interfaces/access-services-user-interface)** - provides a user interface that supports the user-facing Open Metadata Access Services (OMASs).
* **[server-configuration-user-interface](open-metadata-implementation/user-interfaces/server-configuration-user-interface)** - provides the administration user interface for an open metadata server.
Expand Down
Expand Up @@ -18,7 +18,7 @@
<!-- Copy the Jars for the OMAG Server-->

<fileSet>
<directory>../../open-metadata-implementation/governance-servers/server-chassis/server-chassis-spring/target</directory>
<directory>../../open-metadata-implementation/server-chassis/server-chassis-spring/target</directory>
<outputDirectory>./server</outputDirectory>
<includes>
<include>*.jar</include>
Expand All @@ -30,7 +30,7 @@
<!-- Copy the properties for the OMAG Server-->

<fileSet>
<directory>../../open-metadata-implementation/governance-servers/server-chassis/server-chassis-spring/src/main</directory>
<directory>../../open-metadata-implementation/server-chassis/server-chassis-spring/src/main</directory>
<outputDirectory>./server</outputDirectory>
<includes>
<include>resources/*</include>
Expand Down Expand Up @@ -94,16 +94,6 @@
<directoryMode>0755</directoryMode>
</fileSet>

<fileSet>
<directory>../../open-metadata-implementation/access-services/community-profile/connected-asset-client/target/</directory>
<outputDirectory>./clients</outputDirectory>
<includes>
<include>*.jar</include>
</includes>
<fileMode>0755</fileMode>
<directoryMode>0755</directoryMode>
</fileSet>

<fileSet>
<directory>../../open-metadata-implementation/access-services/data-engine/data-engine-client/target/</directory>
<outputDirectory>./clients</outputDirectory>
Expand Down
Expand Up @@ -17,7 +17,7 @@
<!-- Copy the Jars -->

<fileSet>
<directory>../../open-metadata-implementation/governance-servers/server-chassis/server-chassis-spring/target</directory>
<directory>../../open-metadata-implementation/server-chassis/server-chassis-spring/target</directory>
<outputDirectory>.</outputDirectory>
<includes>
<include>*.jar</include>
Expand All @@ -29,7 +29,7 @@
<!-- Copy the properties -->

<fileSet>
<directory>../../open-metadata-implementation/governance-servers/server-chassis/server-chassis-spring/src/main</directory>
<directory>../../open-metadata-implementation/server-chassis/server-chassis-spring/src/main</directory>
<outputDirectory>.</outputDirectory>
<includes>
<include>resources/*</include>
Expand Down
Expand Up @@ -48,11 +48,6 @@
<artifactId>community-profile-spring</artifactId>
<version>${open-metadata.version}</version>
</dependency>
<dependency>
<groupId>org.odpi.egeria</groupId>
<artifactId>connected-asset-spring</artifactId>
<version>${open-metadata.version}</version>
</dependency>
<dependency>
<groupId>org.odpi.egeria</groupId>
<artifactId>digital-architecture-spring</artifactId>
Expand Down
Expand Up @@ -48,11 +48,6 @@
<artifactId>community-profile-client</artifactId>
<version>${open-metadata.version}</version>
</dependency>
<dependency>
<groupId>org.odpi.egeria</groupId>
<artifactId>connected-asset-client</artifactId>
<version>${open-metadata.version}</version>
</dependency>
<dependency>
<groupId>org.odpi.egeria</groupId>
<artifactId>digital-architecture-client</artifactId>
Expand Down
2 changes: 1 addition & 1 deletion open-metadata-implementation/access-services/README.md
Expand Up @@ -195,7 +195,7 @@ options). The implementation of the OMRS Connector handles the
communication between the OMAS application and the metadata repositories,
whether this is through local or remote calls.

The [administration services](../governance-servers/admin-services/README.md) provide
The [administration services](../admin-services/README.md) provide
the ability to configure, start and stop the access services.

----
Expand Down
Expand Up @@ -41,20 +41,44 @@ String getAssetForConnection(String userId,
* @param startFrom starting element (used in paging through large result sets)
* @param pageSize maximum number of results to return
*
* @return list of Asset summaries
* @return list of unique identifiers of assets with matching name.
*
* @throws InvalidParameterException the name is invalid
* @throws PropertyServerException there is a problem access in the property server
* @throws UserNotAuthorizedException the user does not have access to the properties
*/
List<Asset> getAssetsByName(String userId,
String name,
int startFrom,
int pageSize) throws InvalidParameterException,
PropertyServerException,
UserNotAuthorizedException;
List<String> getAssetsByName(String userId,
String name,
int startFrom,
int pageSize) throws InvalidParameterException,
PropertyServerException,
UserNotAuthorizedException;


/**
* Returns a list of assets that match the token. The following calls are issued in
* in order for find the asset.
* - getAssetProperties passing the token as the GUID
* - getAssetByName passing the token as the name
*
* @param userId userId of user making request.
* @param assetToken token used to find the Asset - may be a name or GUID
* @param startFrom starting element (used in paging through large result sets)
* @param pageSize maximum number of results to return
* *
* @return a list of unique identifiers for the matching assets
*
* @throws InvalidParameterException one of the parameters is null or invalid.
* @throws PropertyServerException there is a problem retrieving the asset properties from the property servers).
* @throws UserNotAuthorizedException the requesting user is not authorized to issue this request.
*/
List<String> getAssetsByToken(String userId,
String assetToken,
int startFrom,
int pageSize) throws InvalidParameterException,
PropertyServerException,
UserNotAuthorizedException;

/**
* Returns the asset corresponding to the supplied connection name.
*
Expand Down
Expand Up @@ -45,7 +45,7 @@
<!-- Asset Consumer is built on Connected Asset -->
<dependency>
<groupId>org.odpi.egeria</groupId>
<artifactId>connected-asset-client</artifactId>
<artifactId>ocf-metadata-client</artifactId>
<version>${open-metadata.version}</version>
</dependency>

Expand Down

0 comments on commit 7421e28

Please sign in to comment.