From issues-return-13934-archive-asf-public=cust-asf.ponee.io@airavata.apache.org Thu May 10 19:19:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 659DD180718 for ; Thu, 10 May 2018 19:19:04 +0200 (CEST) Received: (qmail 99598 invoked by uid 500); 10 May 2018 17:19:03 -0000 Mailing-List: contact issues-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@airavata.apache.org Received: (qmail 99560 invoked by uid 99); 10 May 2018 17:19:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 May 2018 17:19:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 2006AC1022 for ; Thu, 10 May 2018 17:19:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id xEmzh6M57gDP for ; Thu, 10 May 2018 17:19:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 77E3D5FBEA for ; Thu, 10 May 2018 17:19:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id CF4C4E0F6E for ; Thu, 10 May 2018 17:19:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4466A2154D for ; Thu, 10 May 2018 17:19:00 +0000 (UTC) Date: Thu, 10 May 2018 17:19:00 +0000 (UTC) From: "Marcus Christie (JIRA)" To: issues@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRAVATA-2704) Improve the process of running the Sharing Registry data migrator MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-2704?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie updated AIRAVATA-2704: -------------------------------------- Description:=20 Currently the process of running the sharing registry data migrator is undo= cumented 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.pr= operties file from airavata-server-configuration into this directory * (/) we then needed to change the following properties ** sharingcatalog.jdbc.driver=3Dorg.mariadb.jdbc.Driver ** sharingcatalog.jdbc.url=3Djdbc:mariadb://XXX.XXX.XXX.XXX:3306/sharing_ca= talog ** sharingcatalog.jdbc.user=3Dairavata ** sharingcatalog.jdbc.password=3DXXXXXXXXXXXXXX ** credential.store.server.host=3DXXX.XXX.XXX.XXX ** regserver.server.host=3DXXXXX.XXXXX.XXXXX ** regserver.server.port=3D8970 ** trust.store=3D/path/to/client_truststore.jks ** trust.store.password=3D... * (/) next was modifying ConnectionFactory and add the MySQL connection inf= o * (/) we also needed to add the mariadb driver to the pom.xml {code:xml} =E2=80=82=E2=80=82=E2=80=82=E2=80=82org.mariadb.jdbc =E2=80=82=E2=80=82=E2=80=82=E2=80=82mariadb-java-client =E2=80=82=E2=80=82=E2=80=82=E2=80=822.0.2 {code} * also had to run {{mvn install}} in sharing-registry to run the openjpa en= hancement otherwise we got errors about the models not being enhanced. I think ideally we would only make calls to the services instead of accessi= ng the database directly, but perhaps I'm missing something and we really d= o need to access the database directly. Also we need an easier way of runn= ing it, maybe with some Maven integration so we can run it from Maven. was: Currently the process of running the sharing registry data migrator is undo= cumented 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.proper= ties file from airavata-server-configuration into this directory * we then needed to change the following properties ** sharingcatalog.jdbc.driver=3Dorg.mariadb.jdbc.Driver ** sharingcatalog.jdbc.url=3Djdbc:mariadb://XXX.XXX.XXX.XXX:3306/sharing_ca= talog ** sharingcatalog.jdbc.user=3Dairavata ** sharingcatalog.jdbc.password=3DXXXXXXXXXXXXXX ** credential.store.server.host=3DXXX.XXX.XXX.XXX ** regserver.server.host=3DXXXXX.XXXXX.XXXXX ** regserver.server.port=3D8970 ** trust.store=3D/path/to/client_truststore.jks ** trust.store.password=3D... * next was modifying ConnectionFactory and add the MySQL connection info * we also needed to add the mariadb driver to the pom.xml {code:xml} =E2=80=82=E2=80=82=E2=80=82=E2=80=82org.mariadb.jdbc =E2=80=82=E2=80=82=E2=80=82=E2=80=82mariadb-java-client =E2=80=82=E2=80=82=E2=80=82=E2=80=822.0.2 {code} * also had to run {{mvn install}} in sharing-registry to run the openjpa en= hancement otherwise we got errors about the models not being enhanced. I think ideally we would only make calls to the services instead of accessi= ng the database directly, but perhaps I'm missing something and we really d= o need to access the database directly. Also we need an easier way of runn= ing it, maybe with some Maven integration so we can run it from Maven. > 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 un= documented 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=3Dorg.mariadb.jdbc.Driver > ** sharingcatalog.jdbc.url=3Djdbc:mariadb://XXX.XXX.XXX.XXX:3306/sharing_= catalog > ** sharingcatalog.jdbc.user=3Dairavata > ** sharingcatalog.jdbc.password=3DXXXXXXXXXXXXXX > ** credential.store.server.host=3DXXX.XXX.XXX.XXX > ** regserver.server.host=3DXXXXX.XXXXX.XXXXX > ** regserver.server.port=3D8970 > ** trust.store=3D/path/to/client_truststore.jks > ** trust.store.password=3D... > * (/) next was modifying ConnectionFactory and add the MySQL connection i= nfo > * (/) we also needed to add the mariadb driver to the pom.xml > {code:xml} > > =E2=80=82=E2=80=82=E2=80=82=E2=80=82org.mariadb.jdbc > =E2=80=82=E2=80=82=E2=80=82=E2=80=82mariadb-java-client > =E2=80=82=E2=80=82=E2=80=82=E2=80=822.0.2 > > {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 acces= sing 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 ru= nning it, maybe with some Maven integration so we can run it from Maven. -- This message was sent by Atlassian JIRA (v7.6.3#76005)