Move On-Premises installation to a different server Is it possible to migrate the products to a new server without losing any (related) content?
We installed the following products (version 5.x) on a temporary server:
- Workflow v5.20.1
- Web v5.11
- Printing v5.8
- Reporting v5.11
And registered all of the products above as separate apps with Portal for ArcGIS (v10.6.1). Portal for ArcGIS and the Geocortex products are both running on-premises.
In the near future we will have a new (dedicated) server for the Geocortex products and we want to ‘move’ the above 5-series products from the temporary server to the new server, without (from the end-user point of view) lose any (created) content.
Will the files in the ‘ProgramData\Geocortex’ directory be correctly updated, for all the products?
What will change:
1. Server (temporary server: Windows 2016, new server: Windows 2019) + IIS Application Pool identity (different user account);
2. Redirect URL;
3. If possible: one app ID (Geocortex 5-Series), instead of an app ID per product. This provides single sign-on between the designers, so we can switch freely between them without having to sign in again.
What will not change:
1. Portal for ArcGIS
2. Version of Geocortex products is equal to the temporary server and the new server
3. ..\ProgramData\Geocortex\.. this will be copied from the temporary server to the new server (the application pools will be stopped first, to take the products offline, to prevent data changes while we move the data directory).
Thanks in advance.
-
Or is it that simple, like: https://communities.geocortex.com/s/feed/0D5f200006MLrvwCAD ??? @Ken Lyon?
0 -
Hi @Erik de Jonge? , thanks for the question.
It is possible to move the data to a new location. We've recently updated the documentation to make this clearer. Please refer to this section:
Manage an On-Premises Installation > Manage the Post-Installation Configuration
0 -
Thank you @Ken Lyon? we will follow these steps to move the data.
0 -
@Ken Lyon Unfortunately this did not work for us. Since the redirect URL also changed, all the content refer to the 'old' redirect URL (for example workflow license URL). So moving data directory only work if you don't change the redirect ULR('s) or start changing all the JSON and XML files in the Data Directory and Portal Directory which is kind of tricky.
0 -
Hmm, right enough. I think our documentation up to this point has been primarily about moving the data directory while using the same server. As it currently stands, there are a number of things that would need to be done manually.
One idea might be to try exporting and re-importing a workflow. That is:
- Open a workflow in Workflow Designer on the old server.
- Choose File > Export and save it to a JSON file.
- Open Workflow Designer on the new server.
- Choose File > Import and select the file from step 2.
I realize if you have a large number of workflows this could be an unappealing prospect, but if it works it'd be simpler than manually editing urls all over the place.
Please let me know how it goes. I'd like to see how we can improve this process.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
5 kommentarer