Configuring Multiple Systems on the Same Server
If needed, you can create multiple .NET UI systems on the same server. However, some aspects of each .NET UI system are set up individually. Review the following example to understand these requirements. They assume a Test, Production, and Train system were configured on a Windows server. This setup on a UNIX server would use the same relative paths.
If you want to provide .NET UI clients with access to additional database sets—for example, the Training database set—you cannot share the same administration database between the sets.
When you use the Perl deployment script to set up these systems, several directories are created and populated based on the unique Web application names you defined:
• Test
• Production
• Train
Each .NET UI system has a unique directory in Tomcat webapps:
• c:\TomcatInstallDir\webapps\test
• c:\TomcatInstallDir\webapps\production
• c:\TomcatInstallDir\webapps\train
The setup process creates additional subdirectories for each system. It creates \mfgpro for configuration files and QAD Standard Edition (MFG/PRO) Progress programs (.p files) and \qad for the compiled .NET UI-specific r-code. For example, for the test .NET UI system these directories are:
• c:\mfgsvr\test\com\qad
• c:\mfgsvr\test\com\mfgpro
After running the setup process for the three environments, each system also has a unique configuration .ini file stored in the log files directory you specify. These examples assume you used the QADInstallDir as the logs directory:
• c:\mfgsvr\test_dt2.ini
• c:\mfgsvr\production_dt2.ini
• c:\mfgsvr\train_dt2.ini