on 07-03-2014 7:11 AM
Hi guys
I have test JavaEE application deployed in SAP NW AS JAVA 7.4 via telnet
I enable http failover on_request in config tool (screen1)
In META-INF folder i put application-j2ee-engine.xml
<application-j2ee-engine xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd"><fail-over-enable mode="on_request" delta="on" xsi:type="fail-over-enableType_enable"/></application-j2ee-engine>
And add parameter icm/HTTP/J2EE/force_server_switch = 1 in J00 and SCS profiles
After that i restart SAP NW instance
My JavaEE app shows me time when session is created.
How i testing session failover:
1. undeploy test JavaEE app
2. deploy test JavaEE app
Refresh browser but session created time is new.
This means that the old session is not saved ((
I try monitor failover from SAP Managment Console in Sessions.
When undeploy session is gone . After that deploy, refresh browser and session is become .
Id Hash parameter the same before undeploy and after deploy.
How understand my session failover is working ? Stored in file? Where this files is placed on filesystem?
Session failover is used to move sessions from one server node to another in case the server node currently managing the session fails. You need to have more than one server node to test the failover, undeploying/redeploying the application is not a proper test. The persistency of the session depends on parameter session.persistent.storage.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can have several server nodes within a single AS JAVA instance. On a single AS JAVA instance you can use all 3 options: shared memory, database or file. Across multiple AS JAVAs you should use database. See the documentation for details.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.