Running Your Magic xpa Projects (Magic xpa 3.x)
Starting the MgxpaRuntime.exe process is not done directly by the user. The Grid Service Agent (GSA) is responsible for starting, monitoring, and terminating the Magic xpa processes. The startup instructions to the GSA are based on configurations defined in the ProjectsStartup.xml file. Two of the elements that you should be aware of in this file are:
-
NumberOfWorkers – This element determines how many worker threads the server will start upon startup. You can set different numbers of worker threads for different Magic xpa servers. The number of workers that will execute a project at any given time is bound by the license. It is recommended to keep this value as low as possible, since each worker polls the space for requests. (The interval between polling attempts can be configured using the Worker Request Polling Interval environment setting.)
-
NumberOfInstances – If you want several servers to run with exactly the same configuration, you can define a single server section in the ProjectsStartup.xml and define in this element how many of those sections will run. The default value is 1. In this element, you can use the AdditionalOnDemand attribute to set additional servers that will be available on a need-to-have basis (Since version: 3.1).
For example: <NumberOfInstances AdditionalOnDemand="2">0</NumberOfInstances> The default is 0, meaning that the server will not loaded on startup.
When a Magic xpa server is started by a GS agent, it is automatically directed to the grid according to the XAP_LOOKUP_LOCATORS environment variable set in the GigaSpaces-xpa\bin\setenv.bat file of that GS agent. Since version: 3.2
The following sections provide information about running your projects:
For additional information regarding GigaSpaces configuration, refer to: http://docs.gigaspaces.com/xap110adm/moving-into-production-checklist.html.
