Hello, Ivy Team,

We are planning to move one existing installation of Axon.Ivy Server to another machine. What are the pitfalls in such scenarios?

  • We will copy-paste the whole installation folder to the new server (the file system paths will be the same)
  • We will attach the AxonIvySystemDatabse to the new server (p.s. we will also migrating to different db server)
  • We need to change the license file
  • We need to update the configuration to point to the new db server
  • Probably we need to update the server name in the Admin UI

All should be straightforward, right ? Are we missing something ?

Best Regards, Yordan

asked 21.11.2017 at 08:29

Stelt0's gravatar image

accept rate: 12%

Yeah you got the main points.

If you migrate into a new network environment you might have to check that third parties are still accessible. SMTP; ExternalDbs, SystemDB, WebServices, ... But thats all project specific.


answered 22.11.2017 at 02:42

Reguel%20Wermelinger's gravatar image

Reguel Werme... ♦♦
accept rate: 70%

Thanks for the hints ! I`ll post back here after we do the migration if something else was needed

(23.11.2017 at 01:14) Stelt0 Stelt0's gravatar image

The migration was done as discussed so far. It works just fine. Thanks !

(29.11.2017 at 01:53) Stelt0 Stelt0's gravatar image
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 21.11.2017 at 08:29

Seen: 1,681 times

Last updated: 29.11.2017 at 01:53