Hello guys,
As far as i know, the dfc.properties manage the comportment of the dfc layer on client side. In this case, what's thé goal of the dfc.properties on the CS (in documentum/config) ? For the JMS ?
Thanks !
If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.
dfc.properties is for DFC client configuration. The Content Server is a client itself, for example when an admin script runs!
If you want to get funky, then do the following:
search for all dfc.properties files located on Content Server
edit and insert line:
dfc.data.dir=c\:/Temp/DfcClients/<client name>
where client name is the folder where dfc.properties file is located. use war or ear file name if located under JMS
You should also see that all the dfc.properties files on the CS, refer back to one central file.
along with JMS, CS also needs dfc.properties as we can include several other properties to tell content server to use them. If you go through dfcfull.properties, you will know more..
Ok, that's make sense !
But.... For me CS is the core plateform and not a client. An admin script, for example, is à DQL or API or Job that runs at client outside the CS.
As dnvhariprasad stated, java methods are clients to CS. Process Engine is separate for CS, so its client as well.
Thanks.
