This week's book giveaway is in the Other Open Source APIs forum. We're giving away four copies of Storm Applied and have Sean Allen, Peter Pathirana & Matthew Jankowski on-line! See this thread for details.
Appriciate your time and solutions on below problem. Share your experiance.
Currently we are setting up the horizontal CLUSTERING (cluster created in machine-1 and federated member from machine-2) and have following problem in setup. We are using WAS ND5.1.1 version.
Our project/application refers/access the external properties files thru Shared Library crated/settings and we have created our cluster members in 2 different separate machines (machine-1, machine-2) and the external properties file exist in primary cluster member machine (machine-1) and it works when we the cluster send a request to primary member, but when the request send to member-2 (machine-2) by stopping machine-1 server then there is no shared library defined/mapping in machine-2 and its failing. Pls advise how to handle this situations and provide the instructions on this setup.
Already we have IHS server installed and working fine without cluster and is there any special setting needs to be done in IHS server after cluster implementation.
Rather than accessing the file directly from the file system, make the resource accessible by a service, potentially implemented through a stateless session bean. Then mitigating access to the resource would be machine neutral.
If its not mandatory that the properties file has to be external, you can package it with your EAR and deploy the app to the cluster. You then shouldn't have any problems with file access. The obvious flipside is that you need to re-deploy the app everytime the properties change. I'm not sure if WAS allows shared libs at a cluster scope. If that's the case, you may do that. But again, you may end up frequently changing them.
The ideal solution [not sure if it is practical in WAS] would be to have a fileHandler(via JNDI...) with the file residing on the filesystem(so that it can be changed easily) made available at the cluster scope. But this basically boils down to the SSB approach suggested by Cameron.