English/日本語

Add properties to be overwritten into:
<TOMCAT_PATH>/shared/classes/app-server-core.properties

In the source code, properties are managed by the Spring context file propertyContext.xml.

<list>
  <value>classpath:nemakiware.properties</value>
  <value>classpath:nemakiware-capability.properties</value>
  ...
  <value>classpath*:app-server-core.properties</value>
</list>

These properties files are loaded in this order, so the latter overwrites the former.

However, the first following files don't overlap each other.
All the default properties are described here:

• nemakiware.properties
  Properties in this file are the most important and overwritten frequently.

• nemakiware-capability.properties
  Defines CMIS capability. Some item can be configurable, though, basically you should NOT change this.

• nemakiware-basetype.properties
  Defines CMIS object type's attributes following CMIS specification. Basically you should NOT change this.

• nemakiware-property.properties
  Defines CMIS property's attributes following CMIS specification. Basically you should NOT change this.

The above list of property fils define static properties.
Almost all of these can be overwritten by CouchDB configuration on the fly, except for CouchDB settings and some repository info metadata.
Dynamic property within CouchDB takes precedence over static properties.

LibreOffice or OpenOffice must be preinstalled.
capability.extended.preview=true
and

Linux
jodconverter.officehome=/opt/libreoffice4.4
Mac
jodconverter.officehome=/Applications/LibreOffice.app/Contents
Windows
TODO

#Referenced setting files Some setting files are designated by a property.
They are specified by name (not by path) and loaded by the class loader.
You can change it to your own custom file put under, for example, <TOMCAT_PATH>/shared/classes.
Original setting files are in <SOUCE_PATH>/core/src/main/webapp/WEB-INF/classes.

• permission.yml
  Defines all kinds of permission(cmis:read, cmis:write, etc.)
• permission-mapping.yml
  Defines the mapping between an CMIS action(e.g.canDelete.Object) and required permissions to execute it