What is the best way to move an existing project from one ApplinX server to another?
In older versions of ApplinX, the following was recommended (by Sabratec at the time):
(A) Create a “Configuration Only” export (GXZ) of the application. Then, stop the ApplinX service, and take a copy of the project’s ApplinX.MDB file.
(B) On the new server, set up the location the project will live in (e.g., C:\Projects<project>\db, and copy the “clean” ApplinX.MDB file (from C:\Program Files\Software AG\ApplinX\host-applications\New Application\db)
(C) Import the “Config Only” GXZ to create the project and have it refer to the newly created repository.
(D) Stop the ApplinX service, and replace the ApplinX.MDB with the one from the old server (with all the application code in it). Re-start the ApplinX service, open the Administrator and “synchronize” the database. And you’re ready to go!
I believe we did it this way because there may have been some problem with importing/exporting GXZ files.
Are all these steps necessary anymore? Or can we just create a “full” export (config + entities) from the first server, and just import the entire application into the new server?
We’ve been noticing a few cases where ApplinX 5.2.4.0011 seems to be losing some nodes in Path Procedures (e.g., the “MapScreen” nodes, and a few other mappings). We haven’t found a pattern to this yet, but want to make sure we’re transferring the application properly (as we move it from one server to another).
Thanks in advance.
Tom
#webMethods#Mainframe-Integration#ApplinX