airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2704) Improve the process of running the Sharing Registry data migrator
Date Thu, 10 May 2018 17:21:00 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470776#comment-16470776
] 

Marcus Christie commented on AIRAVATA-2704:
-------------------------------------------

A lot of these have been addressed now by providing a sample properties file and a README.md
describing what needs to be done to run the AiravataDataMigrator.  I think we can further
improve this by making service calls instead of direct DB access, as mentioned above.  However,
I think this is good enough for now.

> Improve the process of running the Sharing Registry data migrator
> -----------------------------------------------------------------
>
>                 Key: AIRAVATA-2704
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2704
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Marcus Christie
>            Priority: Major
>
> Currently the process of running the sharing registry data migrator is undocumented and
probably unnecessarily complex. Here's what [~tilaks26] and I had to do to run it:
> * (/) create a src/main/resources directory and copy the airavata-server.properties file
from airavata-server-configuration into this directory
> * (/) we then needed to change the following properties
> ** sharingcatalog.jdbc.driver=org.mariadb.jdbc.Driver
> ** sharingcatalog.jdbc.url=jdbc:mariadb://XXX.XXX.XXX.XXX:3306/sharing_catalog
> ** sharingcatalog.jdbc.user=airavata
> ** sharingcatalog.jdbc.password=XXXXXXXXXXXXXX
> ** credential.store.server.host=XXX.XXX.XXX.XXX
> ** regserver.server.host=XXXXX.XXXXX.XXXXX
> ** regserver.server.port=8970
> ** trust.store=/path/to/client_truststore.jks
> ** trust.store.password=...
> * (/) next was modifying ConnectionFactory and add the MySQL connection info
> * (/) we also needed to add the mariadb driver to the pom.xml
> {code:xml}
> <dependency>
>     <groupId>org.mariadb.jdbc</groupId>
>     <artifactId>mariadb-java-client</artifactId>
>     <version>2.0.2</version>
> </dependency>
> {code}
> * also had to run {{mvn install}} in sharing-registry to run the openjpa enhancement
otherwise we got errors about the models not being enhanced.
> I think ideally we would only make calls to the services instead of accessing the database
directly, but perhaps I'm missing something and we really do need to access the database directly.
 Also we need an easier way of running it, maybe with some Maven integration so we can run
it from Maven.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message