dataverse migration - DDI

[gua...@ualberta.ca]

While migrating dataverse from 3.6.2 to 4.5.1, I have a question regarding the following step:

4. run dataset APIs: execute the following HTTP request on the Dataverse 4.0 application to initiate dataset migration: http://<hostname>/api/batch/migrate?path=<parent directory of DDI files>&key=<Dataverse Admin API Key> Where to find <parent directory of DDI files>? is <Dataverse Admin API Key> the same as Dataverse Admin API Token? if not, where to find it? Thanks in advance!

[Condon, Kevin M]

Yes, key is the same as API token.

The parent directory of DDI files is the path to the directory where the ddi files were created in step 2 of the migration_presteps.txt, 2. "Run the script ./versions_source_". 

Please check the directory from which you ran this script. There should be a subdirectory named ddi and that is where the files are generated. So, the full path in the above migration command should be <path where versions_source_ script was run>/ddi , I believe.

---

From: dataverse-m...@googlegroups.com <dataverse-m...@googlegroups.com> on behalf of gua...@ualberta.ca <gua...@ualberta.ca>
Sent: Wednesday, November 9, 2016 10:33:44 AM
To: Dataverse Migration Working Group
Subject: dataverse migration - DDI

 

While migrating dataverse from 3.6.2 to 4.5.1, I have a question regarding the following step:

4. run dataset APIs: execute the following HTTP request on the Dataverse 4.0 application to initiate dataset migration: http://<hostname>/api/batch/migrate?path=<parent directory of DDI files>&key=<Dataverse Admin API Key> Where to find <parent directory of DDI files>? is <Dataverse Admin API Key> the same as Dataverse Admin API Token? if not, where to find it? Thanks in advance!

--
You received this message because you are subscribed to the Google Groups "Dataverse Migration Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-migrati...@googlegroups.com.
To post to this group, send email to dataverse-m...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-migration-wg/5ec314d1-841c-4962-8864-949b03e8a91b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Guanwen Zhang]

The problem is I ran step 2 in a temporary virtual machine with dataverse 3.6.2. The 4.5.1 is on a separate virtual machine.

The step 2 produced 

[root@zk-dev3 ~]# ./versions_source_.sh http://localhost/dvn/ddi 10.7939

0 studies processed.

0 released versions;

0 had versions other than released;

Total 0 versions processed.

So not sure if it is right, and where is the DDI file? Also, do I need to copy the ddi file to the 4.5.1 VM?

regards

On Wed, Nov 9, 2016 at 9:18 AM, Condon, Kevin M <kco...@hmdc.harvard.edu> wrote:

Yes, key is the same as API token.

The parent directory of DDI files is the path to the directory where the ddi files were created in step 2 of the migration_presteps.txt, 2. "Run the script ./versions_source_". 

Please check the directory from which you ran this script. There should be a subdirectory named ddi and that is where the files are generated. So, the full path in the above migration command should be <path where versions_source_ script was run>/ddi , I believe.

---

From: dataverse-migration-wg@googlegroups.com <dataverse-migration-wg@googlegroups.com> on behalf of gua...@ualberta.ca <gua...@ualberta.ca>

Sent: Wednesday, November 9, 2016 10:33:44 AM
To: Dataverse Migration Working Group
Subject: dataverse migration - DDI

While migrating dataverse from 3.6.2 to 4.5.1, I have a question regarding the following step:

4. run dataset APIs: execute the following HTTP request on the Dataverse 4.0 application to initiate dataset migration: http://<hostname>/api/batch/migrate?path=<parent directory of DDI files>&key=<Dataverse Admin API Key> Where to find <parent directory of DDI files>? is <Dataverse Admin API Key> the same as Dataverse Admin API Token? if not, where to find it? Thanks in advance!

--
You received this message because you are subscribed to the Google Groups "Dataverse Migration Working Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-migration-wg+unsub...@googlegroups.com.
To post to this group, send email to dataverse-migration-wg@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-migration-wg/5ec314d1-841c-4962-8864-949b03e8a91b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Henry Zhang

Sr. Sys. admin and Storage Specialist

[Condon, Kevin M]

OK, that is the problem. At the top of the migration_presteps doc it says to download and use  the v3.6.3 version of the war file in order to support exporting versions.

I'm not sure why you had 0 results but at the very least you should upgrade to v3.6.3, rerun the export and confirm and preserve the ddi directory. You could potentially zip up that directory and move it to your target machine and run the import there but confirm it actually exports DDI files.

[Guanwen Zhang]

I think it would be helpful I provide some context.

Since we don't want to take the risk of messing up the current production DVN-3.6.2, we would like to do this on a separate virtual machines.

The followings are what I did

1. Create a brand new virtual machine called DVN-3.6.2-new. It was installed with CentOS 7, glassfish 3.1.2 (which is the same as current production machine), JDK 1.6, and Postgresql Server 9.2.15

2. Install dataverse 3.6.2, and manually installed it on DVN-3.6.2-new. This steps give me a working version of dataverse 3.6.2 with

empty studies.

3. From the current production machine called DVN-3.6.2, I dumped its postgresql for dvnDb as dvnDb_prod.sql

4. On DVN-3.6.2-new, I import the dumped dvbDb_prod.sql.  At this step, should I copy all the study files from production to here?

    During the migration, I didn't copy the studies

5. Following migration-presteps.txt 

Are these right? I asked Gustavo, he said it sounds good. But from my end, I really don't know if it is right or wrong.

Million thanks for the help.

regards

On Wed, Nov 9, 2016 at 10:29 AM, Condon, Kevin M <kco...@hmdc.harvard.edu> wrote:

OK, that is the problem. At the top of the migration_presteps doc it says to download and use  the v3.6.3 version of the war file in order to support exporting versions.

I'm not sure why you had 0 results but at the very least you should upgrade to v3.6.3, rerun the export and confirm and preserve the ddi directory. You could potentially zip up that directory and move it to your target machine and run the import there but confirm it actually exports DDI files.

[Condon, Kevin M]

Quick question: when you ran the versions_source script, which namespace did you specify?

./versions_source_ http://localhost/dvn/ddi 1902.1

1902.1 is our namespace and won't be present in your db. Make sure you are using the right one(s). If you have more than one, you will need to repeat for each.

Otherwise your steps to create a test v3.6 source platform seem ok. I am not sure you need the production files at this point but am checking. I did not see where you upgraded your test v3.6.2 war file to v3.6.3. Was that done? Also, confirm you can access the db from this box, does the app load and function from a browser?

Try checking the server.log for errors too when you run the export.

---

From: Guanwen Zhang <gua...@ualberta.ca>
Sent: Wednesday, November 9, 2016 12:52 PM
To: Condon, Kevin M
Cc: Dataverse Migration Working Group
Subject: Re: dataverse migration - DDI

 

[Guanwen Zhang]

I used 10.7939 as our namespace. It is the same as the production one we used.

regards

Henry

[Guanwen Zhang]

I dropped the DVN-web 3.6.3 war file into    autodeploy folder, and I saw a filed with name called autodeploy succeeded.

Is there any other way to verify that 3.6.3 deployment is successful?

regards