Hello,
We're trying to export all the assets (a few hundreds of books and views) which are on our PAW server from a production server and import them to a dev server.
I've started to play with the "Lifecycle Management" tools but I was wondering is there was an easier way.
My difficulties at this time:

• The Lifecycle Management Export system seems limited to 100 assets at a time
• I'm not able to export assets with the same name but which belongs to different folders
• I need to change all the TM1 server names manually
• There no way, AFAIK, to script the export/import process

Thanks for your help !
Regards,

------------------------------
Bob
------------------------------
#PlanningAnalyticswithWatson

Hi Rob
If you don't have other PAW assets in Dev that you need to retain you could take a backup of your entire production PAW instance and restore it to your DEV environment. To avoid renaming the servers can you run servers (TM1 databases)  in dev with the same name as the servers in prod?

------------------------------
Paul Coggan
------------------------------

Original Message:
Sent: Thu July 23, 2020 10:02 AM
From: Robert MILLI
Subject: Migrate hundreds of assets from PAW prod to dev

Hello,
We're trying to export all the assets (a few hundreds of books and views) which are on our PAW server from a production server and import them to a dev server.
I've started to play with the "Lifecycle Management" tools but I was wondering is there was an easier way.
My difficulties at this time:

• The Lifecycle Management Export system seems limited to 100 assets at a time
• I'm not able to export assets with the same name but which belongs to different folders
• I need to change all the TM1 server names manually

Thanks for your help !
Regards,

------------------------------
Bob
------------------------------

#PlanningAnalyticswithWatson

Thanks Paul for your answer,
Your solution is, IMHO, the best in town expect that you've pointed out my issue... the servers names are not the same between prod and non-prod as in non-prod, all the servers name have a dedicated suffix (MyServer in prod will become MyServerDev in Dev, MyServerQal in Qal, MyServerPpd in Ppd ).
We've decided to do it this way in order to ensure that when you're updating object there no mistake due to the common server name.
Going through the Lifecycle Management system gave us the ability to edit the export file and rename the server names prior reimporting the updated export.
Going through the backup/restore crash during the restore as the server names are not the same.
You seems to suggest there a way to change the server names in the backup itself. Could you point me toward some documentation about how to do it ?
We're asked by our business users to reset the tests environments on a weekly basis so we need to find out some kind of method that could be scripted in a way or another.
Regards,

------------------------------
Bob
------------------------------

Original Message:
Sent: Fri July 24, 2020 01:26 AM
From: Paul Coggan
Subject: Migrate hundreds of assets from PAW prod to dev

Hi Rob
If you don't have other PAW assets in Dev that you need to retain you could take a backup of your entire production PAW instance and restore it to your DEV environment. To avoid renaming the servers can you run servers (TM1 databases)  in dev with the same name as the servers in prod?

------------------------------
Paul Coggan

Original Message:
Sent: Thu July 23, 2020 10:02 AM
From: Robert MILLI
Subject: Migrate hundreds of assets from PAW prod to dev

Hello,
We're trying to export all the assets (a few hundreds of books and views) which are on our PAW server from a production server and import them to a dev server.
I've started to play with the "Lifecycle Management" tools but I was wondering is there was an easier way.
My difficulties at this time:

• The Lifecycle Management Export system seems limited to 100 assets at a time
• I'm not able to export assets with the same name but which belongs to different folders
• I need to change all the TM1 server names manually

Thanks for your help !
Regards,

------------------------------
Bob
------------------------------

#PlanningAnalyticswithWatson

Original Message:
Sent: 7/24/2020 12:24:00 PM
From: Robert MILLI
Subject: RE: Migrate hundreds of assets from PAW prod to dev

Thanks Paul for your answer,
Your solution is, IMHO, the best in town expect that you've pointed out my issue... the servers names are not the same between prod and non-prod as in non-prod, all the servers name have a dedicated suffix (MyServer in prod will become MyServerDev in Dev, MyServerQal in Qal, MyServerPpd in Ppd ).
We've decided to do it this way in order to ensure that when you're updating object there no mistake due to the common server name.
Going through the Lifecycle Management system gave us the ability to edit the export file and rename the server names prior reimporting the updated export.
Going through the backup/restore crash during the restore as the server names are not the same.
You seems to suggest there a way to change the server names in the backup itself. Could you point me toward some documentation about how to do it ?
We're asked by our business users to reset the tests environments on a weekly basis so we need to find out some kind of method that could be scripted in a way or another.
Regards,

------------------------------
Bob
------------------------------

Original Message:
Sent: Fri July 24, 2020 01:26 AM
From: Paul Coggan
Subject: Migrate hundreds of assets from PAW prod to dev

Hi Rob
If you don't have other PAW assets in Dev that you need to retain you could take a backup of your entire production PAW instance and restore it to your DEV environment. To avoid renaming the servers can you run servers (TM1 databases)  in dev with the same name as the servers in prod?

------------------------------
Paul Coggan

Original Message:
Sent: Thu July 23, 2020 10:02 AM
From: Robert MILLI
Subject: Migrate hundreds of assets from PAW prod to dev

Hello,
We're trying to export all the assets (a few hundreds of books and views) which are on our PAW server from a production server and import them to a dev server.
I've started to play with the "Lifecycle Management" tools but I was wondering is there was an easier way.
My difficulties at this time:

• The Lifecycle Management Export system seems limited to 100 assets at a time
• I'm not able to export assets with the same name but which belongs to different folders
• I need to change all the TM1 server names manually

Thanks for your help !
Regards,

------------------------------
Bob
------------------------------

#PlanningAnalyticswithWatson

Hi Ryan,
Thanks for Answering. For Lifecycle Management Export file, I do agree that it's a "json" file and it shouldn't be that difficult to change the servers name.
For the PAW "classical" backup feature, it creates a set of files that are not json files.
Here are the files I get for a regular backup:

• mysql.zip
• 20200724_023003.log
• bss.zip
• couchdb.zip
• mongo.zip
• mongo_db.zip

I would like to find out in which files the server names are set in order to change them by script.
Regards,

------------------------------
Bob
------------------------------

Original Message:
Sent: Fri July 24, 2020 01:05 PM
From: Ryan Clapp
Subject: Migrate hundreds of assets from PAW prod to dev

I've looked at the exports and It really is just a bunch of json. I would test using notepad++ find and replace in files feature. Replace the old instance name with the new one.

Ryan Clapp

Sr. Manager

AWS FinTech

Sent from my mobile device

Original Message:
Sent: 7/24/2020 12:24:00 PM
From: Robert MILLI
Subject: RE: Migrate hundreds of assets from PAW prod to dev

Thanks Paul for your answer,
Your solution is, IMHO, the best in town expect that you've pointed out my issue... the servers names are not the same between prod and non-prod as in non-prod, all the servers name have a dedicated suffix (MyServer in prod will become MyServerDev in Dev, MyServerQal in Qal, MyServerPpd in Ppd ).
We've decided to do it this way in order to ensure that when you're updating object there no mistake due to the common server name.
Going through the Lifecycle Management system gave us the ability to edit the export file and rename the server names prior reimporting the updated export.
Going through the backup/restore crash during the restore as the server names are not the same.
You seems to suggest there a way to change the server names in the backup itself. Could you point me toward some documentation about how to do it ?
We're asked by our business users to reset the tests environments on a weekly basis so we need to find out some kind of method that could be scripted in a way or another.
Regards,

------------------------------
Bob

Original Message:
Sent: Fri July 24, 2020 01:26 AM
From: Paul Coggan
Subject: Migrate hundreds of assets from PAW prod to dev

Hi Rob
If you don't have other PAW assets in Dev that you need to retain you could take a backup of your entire production PAW instance and restore it to your DEV environment. To avoid renaming the servers can you run servers (TM1 databases)  in dev with the same name as the servers in prod?

------------------------------
Paul Coggan

Original Message:
Sent: Thu July 23, 2020 10:02 AM
From: Robert MILLI
Subject: Migrate hundreds of assets from PAW prod to dev

Hello,
We're trying to export all the assets (a few hundreds of books and views) which are on our PAW server from a production server and import them to a dev server.
I've started to play with the "Lifecycle Management" tools but I was wondering is there was an easier way.
My difficulties at this time:

• The Lifecycle Management Export system seems limited to 100 assets at a time
• I'm not able to export assets with the same name but which belongs to different folders
• I need to change all the TM1 server names manually

Thanks for your help !
Regards,

------------------------------
Bob
------------------------------

#PlanningAnalyticswithWatson

Original Message:
Sent: 7/25/2020 5:51:00 AM
From: Robert MILLI
Subject: RE: Migrate hundreds of assets from PAW prod to dev

Hi Ryan,
Thanks for Answering. For Lifecycle Management Export file, I do agree that it's a "json" file and it shouldn't be that difficult to change the servers name.
For the PAW "classical" backup feature, it creates a set of files that are not json files.
Here are the files I get for a regular backup:

• mysql.zip
• 20200724_023003.log
• bss.zip
• couchdb.zip
• mongo.zip
• mongo_db.zip

I would like to find out in which files the server names are set in order to change them by script.
Regards,

------------------------------
Bob
------------------------------

Original Message:
Sent: Fri July 24, 2020 01:05 PM
From: Ryan Clapp
Subject: Migrate hundreds of assets from PAW prod to dev

I've looked at the exports and It really is just a bunch of json. I would test using notepad++ find and replace in files feature. Replace the old instance name with the new one.

Ryan Clapp

Sr. Manager

AWS FinTech

Sent from my mobile device

Original Message:
Sent: 7/24/2020 12:24:00 PM
From: Robert MILLI
Subject: RE: Migrate hundreds of assets from PAW prod to dev

Thanks Paul for your answer,
Your solution is, IMHO, the best in town expect that you've pointed out my issue... the servers names are not the same between prod and non-prod as in non-prod, all the servers name have a dedicated suffix (MyServer in prod will become MyServerDev in Dev, MyServerQal in Qal, MyServerPpd in Ppd ).
We've decided to do it this way in order to ensure that when you're updating object there no mistake due to the common server name.
Going through the Lifecycle Management system gave us the ability to edit the export file and rename the server names prior reimporting the updated export.
Going through the backup/restore crash during the restore as the server names are not the same.
You seems to suggest there a way to change the server names in the backup itself. Could you point me toward some documentation about how to do it ?
We're asked by our business users to reset the tests environments on a weekly basis so we need to find out some kind of method that could be scripted in a way or another.
Regards,

------------------------------
Bob

Original Message:
Sent: Fri July 24, 2020 01:26 AM
From: Paul Coggan
Subject: Migrate hundreds of assets from PAW prod to dev

Hi Rob
If you don't have other PAW assets in Dev that you need to retain you could take a backup of your entire production PAW instance and restore it to your DEV environment. To avoid renaming the servers can you run servers (TM1 databases)  in dev with the same name as the servers in prod?

------------------------------
Paul Coggan

Original Message:
Sent: Thu July 23, 2020 10:02 AM
From: Robert MILLI
Subject: Migrate hundreds of assets from PAW prod to dev

Hello,
We're trying to export all the assets (a few hundreds of books and views) which are on our PAW server from a production server and import them to a dev server.
I've started to play with the "Lifecycle Management" tools but I was wondering is there was an easier way.
My difficulties at this time:

• The Lifecycle Management Export system seems limited to 100 assets at a time
• I'm not able to export assets with the same name but which belongs to different folders
• I need to change all the TM1 server names manually

Thanks for your help !
Regards,

------------------------------
Bob
------------------------------

#PlanningAnalyticswithWatson