Absent Member.. Toby Harvey Absent Member..
Absent Member..

PPM Cluster - how do you manage shared log/report/attachment locations?

I would like to know how others manage their PPM clusters, especially in regards to the shared locations used for attachments and reports. 


The conf file has entries such as "com.kintana.core.server.ATTACHMENT_DIRNAME=" and the HP install guide suggests using full UNC paths - other than that there is very little documented detail on this. 


Do others here use this UNC method and if so is the location on the same box, a separate box or maybe SAN? Are you using SMB shares or another sharing technology (NFS, other)?


Does anyone use a drive mapped or attached to each box and then managed by an external product (to control locking and write conflicts)?


What pros and cons does each method have and what effects might each have on other configuration entities?


All thoughts welcomed as I am looking to explore all options.

2 Replies
Absent Member.. Oscar_Pereira Absent Member..
Absent Member..

Re: PPM Cluster - how do you manage shared log/report/attachment locations?

Hello Toby,


In Cluster configuration having nodes in different physical servers, most customers will use a common shared directory, it can be a folder in the same server, different server or using a SAN.

Directories that needs to be shared by all members of the cluster (other logs directory are inherited from








For Unix, please make sure the shared directory from Primary server is NFS mounted upon startup on the secondary server systems. Please work with the Unix System Admin on this step along with making sure that the NFS users have read/write/list access to the shared drive on Primary system. Try to use the same mount name as the primary so the directory structure is similar across cluster. Example, /u1/apps/kintana/logs.


For Windows, do not use the mounted drive letter, i.e. d:/kintana. Instead use the UNC, Universal Naming Convention, format to access the directory on the Primary system. Switch “\” to “/” in server.conf file. Ex. \\\d$\kintana. This is due to the way window services work.

Also, one will need to associate a user account to the Windows Services for the PPM service. This user must have read/write/list permission to the directory on the Primary server. Otherwise, PPM server cannot be started via the Windows Services. Log into the secondary server system, and try to access the Primary server’s directory. Try list, create and delete files to validate there are no file system level permission issues.

For the attachments, you may want to explore a new feature introduced in 9.1 sp3
PPM Center Database DMS solution, check the Release notes for PPM 9.1 sp3 for more details


It will store the attachments in the database…



Oscar Pereira

Established Member.. Shan_2005
Established Member..

Re: PPM Cluster - how do you manage shared log/report/attachment locations?

Just to mention here that the common directories should be shared and Attachments etc parameters should be the shared folder name similar to /<server_name or IP>/<shared_folder_name>.

Once these are changed, Run kUpdateHTML and JSP compiler; delete Temp and work folders and than Restart the server. Also, the existing Logs/ attachments and Reports should be moved to the new shared location.








The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.