Running the Magic xpi GSA Service (Magic xpi 4.9)
When you install Magic xpi 4.x, it is highly recommended that you select to install an OS service called Magic xpi GSA (Grid Service Agent). This is loaded as an OS service (Windows) or as an init daemon (UNIX), depending on the operating system that you are using.
The Magic xpi GSA service is responsible for first loading the grid and then deploying the Magic Space, in that order. These two modules (the grid and the Magic Space) are GigaSpaces infrastructure modules. A Magic xpi 4.x project cannot run if these two modules are also not running.
If you did not choose to install the GigaSpaces GSA service automatically during the installation, you can install and uninstall the service manually by running the following commands:
These files are located under the following path:
<Magic xpi installation>\Runtime\OS_Service\scripts
With some operating systems, such as Windows 7 and above, you must run these commands using administrator credentials.
It is recommended that you use the dedicated OS service to start the GSA service automatically when your computer starts. To start the GSA service automatically, follow these steps:
-
Click Start, and then Run. The Run dialog box opens.
-
In the Run dialog box, enter services.msc. The Services dialog box opens.
-
In the Services dialog box, double-click on Magic xpi 4.x GSA. The Magic xpi 4.x GSA Properties (Local Computer) dialog box opens.
-
In the Magic xpi 4.x GSA Properties (Local Computer) dialog box's Startup type parameter, select Automatic from the drop-down list.
-
Click OK to finish.
To run the GSA service in a command line, and then deploy the Space:
-
Run the magicxpi_gs-agent.bat file to load the grid. If the Magic xpi GSA service is configured to automatically deploy, then it will automatically deploy the Space as well. If not, use the Magicxpi_deploy.bat file to deploy the Magic Space.
These files are located under the following path:
<Magic xpi installation>\Runtime\GigaSpaces-xpi\bin
When the Magic xpi GSA service starts on a specific machine, it loads the grid locally and searches the LAN for other grid components with the same Lookup Locator names. If any such components are found, the local grid is considered to be part of that Lookup Locator. In this way, a single unified grid is established in the network.
|
|
It is important to remember that the Magic xpi engines run under the user that is defined for the GSA service and not by the logged in user. By default, the user defined for the service is the Local System account. For running Magic xpi on a single machine, this is usually fine. However, on a clustered environment, the service should run as a user who has privileges to access network resources.
|
To verify that the grid is running:
-
From the installation shortcuts, run GigaSpaces UI. A GS utility with several tabs will open.
-
If the grid has started properly, you should see your machine listed in the Hosts tab. When you select the Development Machine check box during installation (the default option), under the machine name you should have one GSA, one GSC, one GSM, and one LUS. If the grid has failed to start properly, you should verify that the LookupGroupName= flag and the LookupLocators= flag are configured correctly. Click here for more information.
Once the grid is up and running, the Magic xpi GSA service automatically deploys the Magic Space on the grid. How the Magic Space is deployed on the grid, such as how many partitions and backups to use, is defined (by default) in the magicxpi_sla.xml file, which is located under:
<Magic xpi installation>\Runtime\config
