atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Ottesen (JIRA)" <>
Subject [jira] [Commented] (ATLAS-2122) OMAG Server
Date Fri, 16 Mar 2018 10:17:00 GMT


Mark Ottesen commented on ATLAS-2122:

Regarding the event adapter provider, should the OMRS framework be calling the initialize
method on that object when we call the "instance" method in the REST API?  Today it calls
the 2-argument initialize method in ConnectorBase from getConnector, but the 7-argument initialize
method in OMRSRepositoryEventMapperBase (which extends ConnectorBase) never gets called, so
the event mapper isn't getting connected properly on our side.  We're (trying to) work around
that by adding that call ourselves in the LocalOMRSRepositoryConnector constructor in OMRS,
which is getting us a bit further, as we try to set up the 2-IGC system cohort that Cassio
mentions above - is that the right place to be trying to do that?

> OMAG Server
> -----------
>                 Key: ATLAS-2122
>                 URL:
>             Project: Atlas
>          Issue Type: New Feature
>    Affects Versions: 1.0.0
>            Reporter: Mandy Chessell
>            Assignee: Mandy Chessell
>            Priority: Major
>         Attachments: 0002-ATLAS-2122-initial-OMAG-Server-implementation.patch
> This Jira Assembles the Open Metadata and Governance components into a configurable server
to support the OMAS Access Layer, Repository or native metadata repository.
> The OMAG server is a Spring Boot Application with a simple REST API. It takes the user
Id of the administrator, the server name and cohort name as path variables, other parameters
are passed as request parameters. These are examples of the commands to set up the server
using defaults. 
> Query configuration 
> GET http://localhost:8080/omag/admin/{userId}/{serverName}/configuration/ 
> Set server type name: 
> POST http://localhost:8080/omag/admin/{userId}/{serverName}/server-type?typeName={name}

> Set organization name: 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/organization-name?name={organizationName}

> Enable the access services: 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/access-services/mode?serviceMode=ENABLED

> Enable the Atlas graph repository: 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/mode?repositoryMode=LOCAL_GRAPH_REPOSITORY

> Enable the in-memory repository: 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/mode?repositoryMode=IN_MEMORY_REPOSITORY

> Enable server as a repository proxy: 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/mode?repositoryMode=REPOSITORY_PROXY

> To add the local repository connection for the repository proxy 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/proxy-details?connectorProvider={javaClassName}&url={nativeServerURL}

> To add the local repository's event mapper: 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/event-mapper-details?connectorProvider={javaClassName}&eventSource={resourceName}

> To enable access to a cohort 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/cohort/{cohortName}/mode?serviceMode=ENABLED

> To remove the local repository 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/mode?repositoryMode=NO_LOCAL_REPOSITORY

> To disable the access services 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/access-services/mode?serviceMode=DISABLED

> To disconnect from a cohort 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/cohort/{cohortName}/mode?serviceMode=DISABLED

> To start up OMRS/OMAS services 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/instance 
> To shutdown OMRS/OMAS services 
> DELETE http://localhost:8080/omag/admin//{userId}/{serverName}/instance?permanent=false

This message was sent by Atlassian JIRA

View raw message