Sign inSign up

exoplatform/cmis-server

By exoplatform

•Updated over 7 years ago

Basic cmis server for test purpose - NOT FOR PRODUCTION USES

Image
0

1M+

exoplatform/cmis-server repository overview

⁠CMIS 1.1 compliant opencmis server

⁠Docker

docker build -t opencmis .
docker run -p 9000:8080 opencmis

⁠How to use it

⁠CMIS 1.1

WS (SOAP) Binding: http://localhost:9000/cmis/services11/cmis?wsdl⁠ AtomPub Binding: http://localhost:9000/cmis/atom11⁠ Browser Binding: http://localhost:9000/cmis/browser⁠

⁠CMIS 1.0

WS (SOAP) Binding: http://localhost:9000/cmis/services/cmis?wsdl⁠ AtomPub Binding: http://localhost:9000/cmis/atom⁠

⁠Authentication

Basic Authentication

Default users :

  • user1 / cm1sp@ssword
  • user2 / cm1sp@ssword
  • user3 / cm1sp@ssword
  • user4 / cm1sp@ssword
  • user5 / cm1sp@ssword

⁠Configuration options

All the following options can be defined with standard Docker -e parameter

docker run -e MY_ENV_VARIABLE="value" ... exoplatform/cmis-server

or Docker Compose way of defining environment variables

version: '2'
services:
...
  exo:
    image: exoplatform/cmis-server
    environment:
...
      JVM_LOG_GC_ENABLED: true
      CMIS_USERS_PASSWORD: mycomplicatedpassword
...
⁠CMIS

5 users (user1, ..., user5) are created by default in the cmis container. Their password can be provided with this environment option :

VARIABLEMANDATORYDEFAULT VALUEDESCRIPTION
CMIS_USERS_PASSWORDNOcm1sp@sswordspecify the cmis users password
⁠JVM

This environment variables can be used :

VARIABLEMANDATORYDEFAULT VALUEDESCRIPTION
JVM_SIZE_MINNO512mspecify the jvm minimum allocated memory size (-Xms parameter)
JVM_SIZE_MAXNO512mspecify the jvm maximum allocated memory size (-Xmx parameter)
JVM_METASPACE_SIZE_MAXNO128mspecify the jvm maximum allocated memory to MetaSpace (-XX:MaxMetaspaceSize parameter)
JVM_LOG_GC_ENABLEDNOfalseactivate the JVM GC log file generation (location: $EXO_LOG_DIR/platform-gc.log)
⁠Frontend proxy

The following environment variables must be passed to the container to configure Tomcat proxy settings:

VARIABLEMANDATORYDEFAULT VALUEDESCRIPTION
PROXY_VHOSTNOlocalhostspecify the virtual host name to reach eXo Platform
PROXY_PORTNO-which port to use on the proxy server ? (if empty it will automatically defined regarding EXO_PROXY_SSL value : true => 443 / false => 80)
PROXY_SSLNOtrueis ssl activated on the proxy server ? (true / false)
⁠Tomcat

The following environment variables can be passed to the container to configure Tomcat settings

VARIABLEMANDATORYDEFAULT VALUEDESCRIPTION
HTTP_THREAD_MAXNO200maximum number of threads in the tomcat http connector
HTTP_THREAD_MINNO10minimum number of threads ready in the tomcat http connector
ACCESS_LOG_ENABLEDNOfalseactivate Tomcat access log with combine format and a daily log file rotation
⁠JMX

The following environment variables should be passed to the container in order to configure JMX :

VARIABLEMANDATORYDEFAULT VALUEDESCRIPTION
JMX_ENABLEDNOtrueactivate JMX listener
JMX_RMI_REGISTRY_PORTNO10001JMX RMI Registry port
JMX_RMI_SERVER_PORTNO10002JMX RMI Server port
JMX_RMI_SERVER_HOSTNAMENOlocalhostJMX RMI Server hostname
JMX_USERNAMENO-a username for JMX connection (if no username is provided, the JMX access is unprotected)
JMX_PASSWORDNO-a password for JMX connection (if no password is specified a random one will be generated and stored in /opt/exo/conf/jmxremote.password)

With the default parameters you can connect to JMX with service:jmx:rmi://localhost:10002/jndi/rmi://localhost:10001/jmxrmi without authentication.

Tag summary

Content type

Image

Digest

Size

272.9 MB

Last updated

over 7 years ago

docker pull exoplatform/cmis-server