I’m trying to describe this as accurately and concisely as I can. I’m sorry this is so long.
As far as I know, none of what I describe here is contrary to the Active4D documentation. But I have been alerted by Aparajita that this configuration may not be viable. He recommended that the Active4D folder should be in the A4D default directory C:\ProgramData\4D\com.Aparajita\Active4D\ It is my intention to test his recommendation in the future.
Today I set up staging environment with Active4D plugin v7.0r8, with 4D Remote v19.7.288.328. (Windows)
In the production environment the v7.2r1 key file will match the machine IP address, but it does not match the staging environment IP address.
The following was tested using 4D Remote as the HTTP Server, with all Active4D configuration documents static at the launch of 4D Remote.
I tried using a 7.2r1 version Active4D.1.2.3.4.key with the v7.0r8 plugin, and Active4D would not run, with this combination A4D Init returned a 2. I previously tried using 7.2r1 key and plugin on this same machine and Active4D would not run, A4D Init returned a 2.
So I reverted to using their existing production v7.0r8 Active4D.5.6.7.7.key, which is IP-mismatched to the new installation machine, but matched to the plugin version 7.0r8, and it works OK with SESSIONS disabled.
When it runs, that is when A4D Init returns a 0, and the only warning in the Active4D.log is the expired mode key.
A4D Default Directory path exists, empty.
C:\ProgramData\4D\com.Aparajita\Active4D\
The Active4D folder is in the plugin Resources folder, with the Active4D.5.6.7.8.key.
In the Active4D folder are two sub folders:
Conf (contains a copy of all the .ini files in the parent Active4D folder)
Lib (contains a copy of all of the .a4l files in the parent Active4D folder)
The Active4D.ini “lib dirs =” path is to the path above.
The Active4D Web Root folder /Web/ is in the 4D Remote Database Folder.
The 4D Remote Web Root /Web_Static/ is in the 4D Remote Database Folder.
Sometime in the future I’m going to see if the v7.2r1 key works correctly when the IP matches the machine. At that time I may test to see if putting the Active4D folder in the A4D default directory makes the newest plugin version work.
If it does not, then I believe I will need a key down-grade for plugin version 7.0r8 or 7.0r9, so the Active4D will run in non-expired mode.
David Ringsmuth