The server uses the JSESSIONID cookie to route web service requests to the correct JVM. If a web service response contains this cookie, it must be sent back to the server in each subsequent web service request if:
A server-side session is kept open across requests (see the discussion of the sessionScenario element below), and EAM is deployed to more than one JVM.
If the server decides the cookie is unnecessary (e.g. the server is configured to run in stateless mode) it will not return the cookie to the client.
Under some circumstances the server may return additional cookies as well (e.g. for routing in a cloud deployment). Subsequent requests for the same session should include any cookies previously set by the server.