[jira] [Commented] (ATLAS-2122) OMAG Server
[
https://issues.apache.org/jira/browse/ATLAS-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418712#comment-16418712
]
Mandy Chessell commented on ATLAS-2122:
---
Review board link is : https://reviews.apache.org/r/65979/
> OMAG Server
> ---
>
> Key: ATLAS-2122
> URL: https://issues.apache.org/jira/browse/ATLAS-2122
> Project: Atlas
> Issue Type: New Feature
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>Priority: Major
> Attachments: 0001-ATLAS-2122-Basic-OMAG-Server.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
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2122) OMAG Server
[
https://issues.apache.org/jira/browse/ATLAS-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418709#comment-16418709
]
Mandy Chessell commented on ATLAS-2122:
---
Hello Mark, yes this is correct
> OMAG Server
> ---
>
> Key: ATLAS-2122
> URL: https://issues.apache.org/jira/browse/ATLAS-2122
> Project: Atlas
> Issue Type: New Feature
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>Priority: Major
> Attachments: 0001-ATLAS-2122-Basic-OMAG-Server.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
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2122) OMAG Server
[
https://issues.apache.org/jira/browse/ATLAS-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401709#comment-16401709
]
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: https://issues.apache.org/jira/browse/ATLAS-2122
> 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
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2122) OMAG Server
[
https://issues.apache.org/jira/browse/ATLAS-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394802#comment-16394802
]
CASSIO DOS SANTOS commented on ATLAS-2122:
--
[~mandy_chessell] I was able to build and start the server setting spring boot
as the parent in the root pom.xml, I wonder if you managed to get that to work
in a different way. I also had to change the versions of springboot and
springframework to 1.5.10 and 4.3.14 to avoid conflicts with some of the IGC
omrs dependencies. Is there any special reason why you chose the older
versions, or to not adopt 2.0? I suspect it may have to do with atlas
dependencies, but if that's the case and if all we want is to build a server to
run a repository proxy for IGC (or any other adapter) connector I don't think
we should be constrained by any atlas dependency.
I believe that the connector provider path parameter in the call to register
the event adapter actually refers to the event adapter provider.
After setting the IGC adapter and connector providers and setting the native
URL for the connector and the adapter (I'm assuming those are the url to the
IGC server and to the topic connector (IGC KAfka bootstrap server) I'm not sure
how to configure the IGC user name and password (the IGC Kafka topic name
itself can be hard-coded). I guess that's related to your comment on not being
able yet to pass complex objects like connection objects. For now we can hard
code the values we need to establish the connection and test end-2-end
scenarios.
I'd like to set up a cohort with two registered IGC systems. Do you think we
can get that to work at this stage?
> OMAG Server
> ---
>
> Key: ATLAS-2122
> URL: https://issues.apache.org/jira/browse/ATLAS-2122
> 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
(v7.6.3#76005)
