Installing Systinet on a Different Server (Magic xpa 3.x)
I’m providing a web service and would like to install Systinet on a different server. How can I install it on a different server and direct it to the existing installation of Magic xpa?
When you need to separate between the web server (Systinet) and the application, like when using the DMZ server for the web server only, you will need to install Systinet manually (or install another instance of Magic xpa).
After Systinet is installed you need to direct it to the Magic xpa installation. To do this, carry out the following steps:
-
Create a folder containing the MGrqcmdl.exe, MGrqgnrc.dll, MgRqSoap.dll and mgreq.ini files. (Copy them from the installation directory of Magic xpa.)
-
Change the mgreq.ini file so that it points to the broker. (You will need to add the name or IP of the machine that is running the broker.)
-
Make sure that the ports of the broker and the engines are opened for communication between the two machines. (The range of the engines' ports can be set in the magic.ini file under the [MAGIC_COMMS] section.)
-
In a text editor, open the server.bat file, which is located at %wasp_home%\bin\.
-
Search for "-Djava.library.path and set the path of this setting to point to the folder you created in step 1.
Now, you can start Systinet and it will communicate with a Magic xpa installation on a different machine.
