Deploying Web Requesters on Different Servers (Optional) (Magic xpa 4.x)
In the configuration shown in the diagram below, the Web servers are deployed separately, on a front-end server residing in the DMZ firewall. This server requires a different setup sequence.
For the Web requester, IIS7 is required.
On the Web server located at the DMZ, you should install Magic xpa with the following configuration:
-
In the Product Components screen, select the ASP .NET (Microsoft) option in the Internet Requesters section.
-
Uncheck the Install the Grid Service Agent (GSA) as a service check box.
-
To enable the front-end requester to connect to the Space, define the same value for the locators that you defined for the rest of the application servers.
Note: The Apache Tomcat Web requester (<Magic xpa installation>\GigaSpaces-xpa\apache-tomcat\MagicScripts.war) can similarly be deployed (manually) on a dedicated Web server machine.
These configurations will enable the Web requester to communicate with the space.
Since the Magic xpa server will not be running on this machine, it will only be used to host the external requesters and will not run any of the grid components or the Magic xpa engines.
The flow of Web requests is as follows:
-
An HTTP client (be it a browser, a RIA client, or any software that makes HTTP calls) submits an HTTP request to the Web server.
-
The Web server invokes the Web requester (GigaSpaces's Web requester is the MgWebRequester.dll file located at: Scripts\bin).
-
The Web requester:
a. Parses the HTTP request
b. Writes an MgHttpRequest object into the space
c. Waits for a matching MgHttpResponse object with the same exchangeId field.
