• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

WAS ND cluster and .properties directory path

 
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

We are currently moving from a stand-alone Websphere 5.1.2 environment to a clustered WebSphere Application Server 6.1 ND environment. Our cluster will be made up of 2 servers. We have several applications that make extensive use of custom -properties files. These files live in the WEB-INF/classes directory of each specific application and are used to hold our web application specific configuration data (i.e. datasource parameters, jndi names, etc). These environment variables include paths to some XSLTs and images located within the web applications' file structure.

My issue is that where I thought a simple relative path would allow the paths in the .properties to start from the web applications' document root, instead, start from the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps directory. This is a problem in that to reach the actual web application install root, you have to specify the proper CELL_NAME. The way I understand it is that there will be two cell names (one per server in the cluster) and depending on where the code is running will dictate which path is needed.

I am looking for some documentation that suggests a way to have the .properties path dynamically defined, either at deployment time, or at runtime. Or to configure where the relative path start directory is defined. I have tried to figure out a way to access the WebSphere Environment variables from within the .properties file, but I can't seem to find anything useful. Has anyone had any experience with this?

Any help is greatly appreciated, thanks in advance.

Heath.
 
reply
    Bookmark Topic Watch Topic
  • New Topic