Renaming Repository - Using Project file

@northswejohan @hollyatsafe

 

I was able to accomplish this task by doing the following:

 

 

1. Add the Workspaces you need to move to a renamed repository to a new project file and download

 

2. Use 7zip to extract the archive to a new folder

 

3. Open each extracted file with a Text Editor (Notepad++) and do a find replace for the existing Repository name and replace with the new name you want

 

4. Rename the .fsproject file to .zip and open with 7zip

 

5. Drag and Drop each updated file from the unzipped folder you ran the find replace process on into the archive

 

6. Close and Rename the .zip back to .fsproject

 

7. Import into FMEServer

 

 

Once complete you should see your new repository name and the models in it. My environment is FME 2019 Build 19813 running on Windows Server 2016 and I have super user privileges. I first tested my project redeployment into a Linux Docker setup same FMEServer build number to be safe and it worked perfectly.

 

 

I originally tried using a workbench process to automate this but I could not seem to match the CRC signatures on the final project file so FMEServer rejected the edited files upon import. I hope this helps and good luck!

 

 

Before:

 

After:

@northswejohan @hollyatsafe

 

I was able to accomplish this task by doing the following:

 

 

1. Add the Workspaces you need to move to a renamed repository to a new project file and download

 

2. Use 7zip to extract the archive to a new folder

 

3. Open each extracted file with a Text Editor (Notepad++) and do a find replace for the existing Repository name and replace with the new name you want

 

4. Rename the .fsproject file to .zip and open with 7zip

 

5. Drag and Drop each updated file from the unzipped folder you ran the find replace process on into the archive

 

6. Close and Rename the .zip back to .fsproject

 

7. Import into FMEServer

 

 

Once complete you should see your new repository name and the models in it. My environment is FME 2019 Build 19813 running on Windows Server 2016 and I have super user privileges. I first tested my project redeployment into a Linux Docker setup same FMEServer build number to be safe and it worked perfectly.

 

 

I originally tried using a workbench process to automate this but I could not seem to match the CRC signatures on the final project file so FMEServer rejected the edited files upon import. I hope this helps and good luck!

 

 

Before:

 

After:

Hi @davisblack,

 

 

I would like to caution FME Server users that while this method might work, this is not recommended nor supported by Safe Software. This may cause unintended behaviour and we cannot guarantee it to work between releases.

 

 

We are aware of the idea to support renaming in FME Server, however this is unlikely to be implemented in a near release.

 

 

Thanks for sharing what you've found, and if you decide to continue with this method please proceed with caution (and make backups before changing anything).