[jira] [Commented] (ATLAS-2109) Create basic IGC OMRS Connector for existing releases
[ https://issues.apache.org/jira/browse/ATLAS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16325707#comment-16325707 ] Mandy Chessell commented on ATLAS-2109: --- The OCF Connection for the IGC Connector is added to the server configuration as the connection to the local repository. During server start up, the IGC Connector is created from the Connection information. The Connection is passed to the new IGC Connector. If the IGC Connector needs its own configuration parameters from the administrator, they can be set up in the Connection. This includes protected properties for security. Hopefully the IGC does not this. Each OMAG server will have its own security identity Requests from the IGC Connector will flow using its local server identity. This server identity is the identity that needs to be given access to the IGC REST API and the IGC Kafka topic to enable the connector/event mapper to do their work. > Create basic IGC OMRS Connector for existing releases > - > > Key: ATLAS-2109 > URL: https://issues.apache.org/jira/browse/ATLAS-2109 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: Mandy Chessell > > This is the first version of the IGC OMRS Connector that works with existing > IGC servers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2109) Create basic IGC OMRS Connector for existing releases
[ https://issues.apache.org/jira/browse/ATLAS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16325702#comment-16325702 ] Mandy Chessell commented on ATLAS-2109: --- Hello Cassio - this is exactly right up to the point that the EntityDetail object is created from the call to the IGC connector. The EntityDetail object should then be passed to the repository event processor object that is passed to the repository event mapper on the setRepositoryEventProcessor(OMRSRepositoryEventProcessor repositoryEventProcessor) method. The repository event processor implements the org.apache.atlas.omrs.eventmanagement.OMRSRepositoryEventProcessor interface. This includes a method called: void processNewEntityEvent(String sourceName, String originatorMetadataCollectionId, String originatorServerName, String originatorServerType, String originatorOrganizationName, EntityDetail entity); The other parameters are provided to the event mapper on the initialize() call. When the processNewEntityEvent() method is called, the repository event processor will look up the configuration rules defined for how events from the local repository (IGC in this case) should be processed. It then routes the supplied EntityDetail to the right OMRSEventPublisher instances running in the server which will create the event payload and push to Kafka. The IGC connector/event mapper does not need to locate the active version of the event payload, construct the OMRS Event payload, nor locate the correct OMRS Topic Connector to pass the event to it. The OMRS handles all of that. > Create basic IGC OMRS Connector for existing releases > - > > Key: ATLAS-2109 > URL: https://issues.apache.org/jira/browse/ATLAS-2109 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: Mandy Chessell > > This is the first version of the IGC OMRS Connector that works with existing > IGC servers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2109) Create basic IGC OMRS Connector for existing releases
[ https://issues.apache.org/jira/browse/ATLAS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16325699#comment-16325699 ] CASSIO DOS SANTOS commented on ATLAS-2109: -- [~mandy_chessell] If SSL certificates need to be retrieved for the IGC connector to call the IGC REST APIs, would that happen during registration of the IGC connector? I haven't looked at that area of the code in detail yet, and we can proceed with manual certificate installation for testing/demo, but I'd like to confirm if we'd have a UI (or REST API?) to register a connector that would involve setting up a connection and accepting a certificate, or something along those lines. > Create basic IGC OMRS Connector for existing releases > - > > Key: ATLAS-2109 > URL: https://issues.apache.org/jira/browse/ATLAS-2109 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: Mandy Chessell > > This is the first version of the IGC OMRS Connector that works with existing > IGC servers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2109) Create basic IGC OMRS Connector for existing releases
[ https://issues.apache.org/jira/browse/ATLAS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16325695#comment-16325695 ] CASSIO DOS SANTOS commented on ATLAS-2109: -- [~mandy_chessel] By "call the IGCOMRSConnector" in the previous comment I meant call the IGCOMRSRepositoryConnectorProvider.getConnector(igcConnection).getMetadataCollection().getEntityDetail(ridOfIGCTerm). The igcConnection instance of Connection contains all the information needed for the methods in IGCOMRSMetadataCollection to make the corresponding calls to the IGC REST API (including SSL certificate). Does that make sense? > Create basic IGC OMRS Connector for existing releases > - > > Key: ATLAS-2109 > URL: https://issues.apache.org/jira/browse/ATLAS-2109 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: Mandy Chessell > > This is the first version of the IGC OMRS Connector that works with existing > IGC servers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2109) Create basic IGC OMRS Connector for existing releases
[ https://issues.apache.org/jira/browse/ATLAS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16325687#comment-16325687 ] CASSIO DOS SANTOS commented on ATLAS-2109: -- [~mandy_chessel] In the implementation of IGCOMRSRepositoryEventMapper we are listening to messages that IGC sends to the InfosphereEvents topic in the kafka server IIS is configured to send messages to. Say a message is received for the publishing of a new glossary term in IGC. The message has the RID of the glossary term but not all its metadata, so the event mapper will call the IGC OMRS connector to get the metadata given the GUID in the IGC event to get the corresponding EntityDetail. It then creates an event containing an OMRSEventV1InstanceSection with entityType set to OMRSInstanceEventType.NEW_ENTITY_EVENT and entityDetail set to the EntityDetail instance returned from the IGC OMRS connector. That event would then be sent to the KafkaOMRSTopicConnector directly from IGCOMRSRepositoryEventMapper. Am I understanding this flow correctly? Am I missing any step? > Create basic IGC OMRS Connector for existing releases > - > > Key: ATLAS-2109 > URL: https://issues.apache.org/jira/browse/ATLAS-2109 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: Mandy Chessell > > This is the first version of the IGC OMRS Connector that works with existing > IGC servers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2109) Create basic IGC OMRS Connector for existing releases
[ https://issues.apache.org/jira/browse/ATLAS-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162923#comment-16162923 ] Mandy Chessell commented on ATLAS-2109: --- Hello Cassio, the IGC OMRS Connector is used for both loading metadata from Atlas into IGC and for extracting metadata on demand from IGC. The on demand call could come from the OMAS interfaces, or the IGC Event Mapper. The IGC Event Mapper is listening on IGC events and then using the IGC OMRS Connector to extract the changes metadata and post it to the other open metadata repositories in the cluster eg Atlas. This is documented on https://cwiki.apache.org/confluence/display/ATLAS/Integrating+using+the+Adapter+pattern > Create basic IGC OMRS Connector for existing releases > - > > Key: ATLAS-2109 > URL: https://issues.apache.org/jira/browse/ATLAS-2109 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: Mandy Chessell > > This is the first version of the IGC OMRS Connector that works with existing > IGC servers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
