Ending session in DFS
Comments
-
ServiceContexts normally expire by themselves so you don't need to explicitly unregister them. The expiration timeout is 60 minutes by default and you can change it in dfs-runtime.properties.
If you still wish to unregister the context manually you can use "com.emc.documentum.fs.rt.services.ContextRegistryService" to do so, but you need to provide the URL of the ContextRegistryService in this case, not the module name as you would do for ContextFactory. This can be inconvenient.
0 -
Please see the "Server runtime startup settings" section of the Deployment guide.
The following list describes the precedence that dfs-runtime.properties files take depending on their location:
• a local-dfs‑runtime.properties file in the local classpath
• a runtime properties file specified with ‑Ddfs.runtime.properties.file
• a dfs‑runtime.properties packaged with emc‑dfs‑rt.jarFor example, settings in the local-dfs‑runtime.properties file on the local classpath will take precedence of identical settings in the dfs‑runtime.properties file that is located in emc‑dfs‑rt.jar or the one specified with the ‑D parameter. The DFS application must be restarted after any changes to the configuration. As a best practice, use the provided configuration file that is deployed in the emc‑dfs‑rt.jar file for your base settings and use an external file to override settings that you specifically wish to change.
0
Categories
- All Categories
- 109 Developer Announcements
- 49 Articles
- 100 General Questions
- 122 IM Services
- 40 OpenText Hackathon
- 31 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 897 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 122 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management