Page History
...
Load tables | SQL commands may be used to load any static or dynamic tables in your application. | The commands execute under the user profile that the aXes server is executing under. You should authorise authorize that user profile for read access to the SQL tables required for this purpose. This user does not need any rights to other data base tables that may be on the system. |
Deploy the save file containing the aXes definitions to the target system | On the target system, use the IBM i RST command to restore the aXes files into the target system's application folder.
If someone on the target system starts Axes as a developer/designer and attempts to identify a screen and save the definition, they will cause the screens.jsn file to be (re)published. This will effectively remove all the screen definitions from it except for the new screen they have just defined. In this case you would need to restore the screens.jsn file(s) again. Note that aXes eXtensions that are to be used by all applications on this system should be placed in the axes/ts/screens folder of the target system, not to individual application folders. If the same aXes eXtension exists in the screens folder and the application folder, the eXtension in the application folder should take precedence but cannot be guaranteed so you should check which version is being used. | To restore the save file use a command like this:
|
Verify IE settings | Verify IE settings on every PC from which RAMP-TS is used. |