EMC Documentum Content ManagementInteroperability Services

EMC® Documentum® ContentManagement Interoperability

ServicesVersion 6.7

Deployment Guide

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-91031-508-435-1000www.emc.com

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kindwith respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitnessfor a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarksused herein are the property of their respective owners.© Copyright 2011 EMC Corporation. All rights reserved.

Table of Contents

Preface ................................................................................................................................. 5

Chapter 1 About CMIS Deployment .............................................................................. 7CMIS deployment with Content Server installation.............................................. 7Supported environments.................................................................................... 7Application archive ........................................................................................... 7

Chapter 2 Configuration Settings ................................................................................. 9General JVM configuration settings .................................................................... 9Using urandom generators on Linux systems ...................................................... 9EMC CMIS configuration files ........................................................................... 10DFC configuration ............................................................................................ 10CMIS runtime properties .................................................................................. 11Anonymous access settings ........................................................................... 17Maximum items default and upper limit settings............................................ 18

Chapter 3 Deploying to Supported Application Servers .............................................. 19Apache Tomcat 5.5 and 6.0 ................................................................................ 19IBMWebSphere 6.1........................................................................................... 20IBMWebSphere 7.0........................................................................................... 20Oracle WebLogic Server 10g (10.3.0) and 11g (10.3.3)........................................... 21Red Hat JBoss EAP 4.3.0.................................................................................... 21Red Hat JBoss EAP 5.1 ...................................................................................... 22

Chapter 4 Post Deployment ......................................................................................... 23Validation ........................................................................................................ 23RESTful AtomPub service document ................................................................. 23Web service entry points ................................................................................... 23

EMC Documentum Content Management Interoperability Services 6.7 Deployment Guide 3

Table of Contents

List of Tables

Table 1. CMIS archive files and container environments ....................................................... 8Table 2. Properties in dfc.properties that are relevant to CMIS ............................................. 10Table 3. EMC CMIS startup properties ............................................................................... 12Table 4. CMIS web service endpoints ................................................................................. 23

4 EMC Documentum Content Management Interoperability Services 6.7 Deployment Guide

Preface

This manual describes how to deploy EMC Documentum Content Management InteroperabilityServices (CMIS) to a supported servlet container, as well as information about configuration of theCMIS server environment.

Intended audienceThis manual is for system administrators or programmers who wish to deploy EMC DocumentumCMIS.

Revision historyThis section contains a description of this document’s revision history.

Revision Date Description

April 2011 Initial publication


Preface


Chapter 1About CMIS Deployment

This chapter covers some general topics that you should familiarize yourself with before beginningyour EMC Documentum Content Management Interoperability Services (CMIS) deployment.

CMIS deployment with Content ServerinstallationIf you have installed EMC Documentum Content Server version 6.7 and only need to deploy CMIS onthe server where your Content Server is hosted, then there is no need to perform any deploymentprocedure described in this guide. EMC Documentum CMIS is deployed as part of the ContentServer installation, and runs in the Java Method Server listening on port 9080 on the Content Serverhost. The Java Method Server is an instance of JBoss 4.3. However, even if you exclusively use theinstance of EMC Documentum CMIS available on Content Server, you should still familiarize yourselfwith the configuration options described under Chapter 2, Configuration Settings.

If you want to deploy EMC CMIS to another location or supported container, follow the proceduresdescribed in the remainder of this guide.

Supported environmentsBefore you begin deployment, review the EMC Documentum CMIS 6.7 Release Notes to make sure thatthe environment to which you are deploying is supported. In particular, check the matrix in theWebapplication server environments section to make sure that you are using a supported application serverversion on a supported operating system, and that any required updates from the application servervendor have been applied. Check the Java version support section to make sure that your applicationserver is running a supported version of the JVM.

Application archiveTo deploy CMIS, you will need to download one of the following files:


About CMIS Deployment

Table 1. CMIS archive files and container environments

Archive Container(s)

emc-cmis.war Apache Tomcat (all versions)JBoss (all versions)IBM WebSphere 7.0

emc-cmis-was61.ear IBM WebSphere 6.1

emc-cmis-wls.ear Oracle WebLogic 11g (10.3.3)

emc-cmis-wls1030.ear Oracle WebLogic 10g (10.3.0)


Chapter 2Configuration Settings

This chapter provides information on configuration settings that affect EMC CMIS, including JVM,Linux, and application properties settings. This chapter covers the following topics:

• General JVM configuration settings, page 9

• Using urandom generators on Linux systems, page 9

• EMC CMIS configuration files, page 10

• DFC configuration, page 10

• CMIS runtime properties, page 11

General JVM configuration settingsTo provide adequate heap space and PermGen space for the CMIS application, we recommendthe following JVM settings:

• -Xms512m

• -Xmx512m

• ‑XX:MaxPermSize=128m

Using urandom generators on Linux systemsThere are issues with implementation of pseudo-random number generators on Linux. For moreefficient randomization, Linux systems should use urandom generators that are faster but less secure.

To change the source of secure random numbers from random to urandom, set thejava.security.egd system property as follows:-Djava.security.egd=file:///dev/urandom

Specifying this system property will override the securerandom.source setting to urandom.

If the application server is on Red Hat Linux, the application server startup script (for examplerun.sh for JBoss, and startWeblogic.sh for WebLogic) must be modified to set the optionin the JVM.


Configuration Settings

EMC CMIS configuration filesEMC CMIS uses these configuration files to set properties for different layers of the application:

• dfc.properties, which contains property settings for the underlying DFC (DocumentumFoundation Classes) client. The settings critical to your deployment are the connection broker andglobal registry settings, as well as other settings, described under DFC configuration, page 10.

• cmis-runtime.properties, which includes properties specific to the CMIS layer. Theseproperties are described under CMIS runtime properties, page 11.

DFC configurationThe dfc.properties file provides property settings for the Documentum Foundation Classesruntime. This file is located in APP-INF/classes if you are deploying the EAR file, or inWEB-INF/classes if you deploying the WAR file.

Table 2, page 10 describes properties in the dfc.properties file that are relevant for CMIS. Forexample, the dfc.properties files includes the critical settings that are required for CMIS to reacha connection broker (historically called a docbroker) and connect to a Content Server.

Table 2. Properties in dfc.properties that are relevant to CMIS

Property Value

dfc.docbroker.host[0] The fully qualified hostname for the connectionbroker. You can add backup hosts by addingnew properties and incrementing the indexnumber within brackets.

dfc.docbroker.port If you wish to use a port for the connectionbroker other than the default of 1489, add a portkey.

dfc.globalregistry.repository The global registry repository name.

dfc.globalregistry.username The username of the global registry user.The global registry user, who has the defaultusername dm_bof_registry, must have readaccess to objects in the /System/Modules and/System/NetworkLocations only.

dfc.globalregistry.password An encrypted password value for the globalregistry user.

dfc.search.external_sources.enable True, to enable Documentum Federated SearchServices (formerly known as ECIS); false, todisable ECIS.

You must specify the Documentum FederatedSearch Services host machine name indfc.search.ecis.host.



Property Value

dfc.search.external_sources.host Specifies the Documentum Federated SearchServices (formerly known as ECIS) host machinename.

You must set dfc.search.ecis.enable totrue.

dfc.cache.ddinfo.size Valid values are 1 to 10000. Controls the memorycache size of the Content Server data dictionary.

This parameter is required for the CMIS typedefinition cache.

dfc.cache.type.currency_check_interval

Valid values are 0 to 86400.

This parameter is required for the CMIS typedefinition cache.

You can either copy the username and encrypted password for the global registry user from thedfc.properties file on the global registry Content Server host, or you can select another globalregistry user and encrypt the password using the following command:java -cp dfc.jar com.documentum.fc.tools.RegistryPasswordUtilspassword_to_be_encrypted

CMIS runtime propertiesThe cmis-runtime.properties file enables you to set properties that affect application behaviorat the CMIS layer.

These properties are optional unless otherwise specified, and if not specified will default to a valuedocumented in the following table. If a supplied value for an integer or boolean property is invalid,the default value will be used instead.

These items are cached:• Repository MIME types

• Repository object types

• DFC session service tokens for logged-in users



Table 3. EMC CMIS startup properties

Name Description Default value Permissiblevalues | range

security.configuration.file Required. File name of security(XWS-Security) configuration for SOAPbinding web services.

cmis-security.xml security filename string

cmis.mime_type.cache_expiration_after_x_seconds

Indicates the expiration timeout for MIMEtype cache.

Repository MIME types are cached inmemory to help with performance.

This property specifies how often theMIME type cache will be flushed.

3600 1 - 8,640,000 (100days)

cmis.token.cache_expiration_after_x_seconds

Indicates the expiration timeout for servicetoken cache.

Service tokens for login users are cachedin memory to save the cost of new DFCsessions.

This property specifies how often theservice token will be flushed.

3600 1 - 8,640,000 (100days)




cmis.type_info.cache_expiration_after_x_seconds

Indicates the expiration timeout (inseconds) for the CMIS type definitioncache.

When the specified interval has elapsedand if repository object types have changedin the repository, then the CMIS typedefinition cache is flushed and reloadedwith the updated object types from therepository.

The repository’s object type definitionsare cached in memory to improveperformance. In addition, object type andproperty definitions are loaded into thecache lazily.

3600 1 - 8,640,000 (100days)

cmis.mime_type.cache_size The cache size for mime type.

The cache size should not be less than therepository list size.

10 1 - 10,000

cmis.token.cache_size The cache size for service token.


10 1 - 10,000

cmis.type_info.cache_size The cache size for CMIS type definition.


10 1 - 10,000




cmis.temp_file_cleaner.periodically_cleanup_every_x_seconds

Period in seconds of temp file cleanup task.

Temp files are cleaned up by a scheduledtask.

This property specifies the interval of thenext cleanup task execution.

600 1 - 8,640,000 (100days)

cmis.temp_file.expiration_after_x_seconds

Indicates the expiration timeout for tempfile of local content stream.

Temp files might be generated on the serverside for content stream manipulation. Ifthe server is not able to determine whetherto delete the temp file immediately, thedeletion will be delayed until the temp fileexpires.

This property determines how long thetemp files live before they expire.

600 1 - 8,640,000 (100days)

cmis.default_max_items The default maximum number of items ina returned collection. This value is usedif the client does not provide a value formaxItems.

If value = -1 or value = 0 then the value willbe set to Integer.MAX_VALUE.

For usage, see Maximum items default andupper limit settings, page 18.

100 -1 - Integer.MAX_VALUE




cmis.max_items_upper_limit The allowedmaximum value for maxItems.This sets an upper limit on maxItemsprovided by a client.

This setting is recommended for systemscalability and performance.

If value = -1 or value = 0 then the value willbe set to Integer.MAX_VALUE.

For usage, see Maximum items default andupper limit settings, page 18.

2000 -1 - Integer.MAX_VALUE

cmis.exception.full_message.append

Indicates whether to output errormessages from layers below CMIS; that is,Documentum error messages.

These messages can help to identify theroot cause of exceptions.

true true, false

cmis.anonymous_access.repository[index]

The name of the repository to which togrant anonymous access.

If one repository is configured asanonymous accessible, set its repositoryname here. You can set multiplerepositories for anonymous access, or setall available repositories to be anonymouslyaccessible (see Anonymous access settings,page 17.

Not-Set valid repositoryname string




cmis.anonymous_access.principal.username[index]

The Documentum login name to be usedfor anonymous access to the repositorywith the same index. See Anonymousaccess settings, page 17.

Not-Set valid user loginname string

cmis.anonymous_access.principal.password[index

The Documentum password for the userlogin with the same index. See Anonymousaccess settings, page 17.

Not-Set valid userpassword



Anonymous access settings

You can configure a principal to allow access to a single repository, to multiple but not all repositories,or to all available repositories.

To make only one repository anonymously accessible, set the anonymous_access properties asfollows:cmis.anonymous_access.repository[0]=<reponame>cmis.anonymous_access.principal.username[0]=<username>cmis.anonymous_access.principal.password[0]=<password>

To enable anonymous access to multiple repositories, configure each repository by incrementingthe index on the properties:cmis.anonymous_access.repository[0]=<reponame>cmis.anonymous_access.principal.username[0]=<username>cmis.anonymous_access.principal.password[0]=<password>cmis.anonymous_access.repository[1]=<reponame1>cmis.anonymous_access.principal.username[1]=<username1>cmis.anonymous_access.principal.password[1]=<password1>

If all repositories available to the CMIS services allow anonymous access, and if the username andpassword for the principal are the same on all repositories, you can use the wildcard, * (asterisk),as follows:cmis.anonymous_access.repository[0]=*cmis.anonymous_access.principal.username[0]=<username>cmis.anonymous_access.principal.password[0]=<password>



Maximum items default and upper limit settings

The CMIS specification defines the maxItems parameter as “the maximum number of items toreturn in a response”. Many CMIS services/resources support this parameter for paging purposes.Typically, a CMIS client will provide a maxItems setting in requests to such resources and services.However, in cases when the client does not provide a value for maxItems, CMIS will use a defaultvalue. The CMIS server administrator can set this default using the cmis.default_max_itemsruntime property.

In some cases a client (perhaps with malicious intent) may set maxItems to an excessively large valuein a request, which may negatively affect server performance. To guard against this possibility, theCMIS server administrator can set an upper limit to maxItems in cmis.max_items_upper_limit.

If either property has a value of -1 or 0, CMIS will set no upper bound on the number of itemsreturned, so that the effective limit is Integer.MAX_VALUE. CMIS determines the effective maxItemsvalue using both of these property settings, as follows:maxItems = MIN(client_or_default_max_items, server_max_items_upper_limit),where a value of -1 or 0 is treated as equivalent to Integer.MAX_VALUE


Chapter 3Deploying to Supported ApplicationServers

The following sections provide information on deployment of EMC CMIS to supported applicationservers.

• Apache Tomcat 5.5 and 6.0, page 19

• IBM WebSphere 6.1, page 20

• IBM WebSphere 7.0, page 20

• Oracle WebLogic Server 10g (10.3.0) and 11g (10.3.3), page 21

• Red Hat JBoss EAP 4.3.0, page 21

• Red Hat JBoss EAP 5.1, page 22

Apache Tomcat 5.5 and 6.0On all supported versions of Tomcat, deploy emc-cmis.war.

Before deploying check the EMC Documentum CMIS 6.7 Release Notes to verify that you are deployingon a certified minor version of Tomcat. Also check to make sure that the Tomcat JVM settings meetthe recommendations specified in General JVM configuration settings, page 9, as the Tomcat defaultsettings may not be adequate. Tomcat provides various options for application deployment. You canuse the following procedure to perform a simple war file deployment.

1. Stop the Apache Tomcat server.

2. Copy the WAR file to the <TomcatHome>/webapps directory.

3. Start the Apache Tomcat server.On startup, Tomcat unpacks the WAR file to a <TomcatHome>/webapps/<application_name>directory, where <application_name> is the name of the WAR file without the file extension.

For more information refer to the Tomcat 5.5 or Tomcat 6.0 deployment documentation.


http://tomcat.apache.org/tomcat-5.5-doc/deployer-howto.html

http://tomcat.apache.org/tomcat-6.0-doc/deployer-howto.html

Deploying to Supported Application Servers

IBM WebSphere 6.1On WebSphere 6.1 deploy emc-cmis-was61.ear.

Before deploying, check the EMC Documentum CMIS 6.7 Release Notes to determine whether you haveinstalled all required IBM WebSphere fix packs.

Use the following procedure to deploy CMIS using the Integrated Solutions Console.

1. Start WebSphere 6.1 server.

2. Add a custom property:

a. Select Application servers > ServerName >Web container > Custom properties.

b. Add a custom property com.ibm.ws.webcontainer.removetrailingservletpathslash with the value true.

3. Install emc-cmis-was61.ear.

4. Configure the class loader policy for the CMIS application:

a. Set Class Loader Order to Classes loaded with application class loaderfirst.

b. SetWar Class Loader Policy to Single class loader for application.

5. Start the CMIS application.

IBM WebSphere 7.0On WebSphere 7.0 deploy emc-cmis.war.

Before deploying check the EMC Documentum CMIS 6.7 Release Notes to determine whether you haveinstalled all required IBM WebSphere fix packs.

1. Update the WebSphere JRE:Copy jaxb-impl.jar from emc-cmis.war/WEB-INF/lib/ to <WebSphere_HOME>/AppServer/java/jre/lib/ext.

2. Start WebSphere 7.0 Server.

3. Configure the class loading policy:

a. Select Application servers > Server_Name.

b. Set Classloader Policy to Single.

c. Set Classloaded with local class loader first (parent last).

4. Add a custom property:

a. Select Application servers > ServerName >Web container > Custom properties.

b. Add a custom property com.ibm.ws.webcontainer.removetrailingservletpathslash with the value true.



5. Install emc-cmis.war.

6. Start the CMIS application.

Oracle WebLogic Server 10g (10.3.0) and 11g(10.3.3)On Oracle WebLogic 10g, deploy emc-cmis-wls1030.ear.

On Oracle WebLogic Server 11g, deploy emc-cmis-wls.ear.

To successfully deploy CMIS on Oracle WebLogic you will need to turn off the container’s HTTPBasic authentication. Instructions on how to do this are incorporated into the procedure below. Formore general information refer to the section "Understanding BASIC Authentication with UnsecuredResources" in the Oracle document Programming WebLogic Security.

Follow these steps to deploy CMIS on Oracle WebLogic:

1. Turn off the WebLogic container’s HTTP Basic authentication:

2. Edit the following file and save it: <WebLogic_home>/user_projects/domains/<domain>/config/config.xml.

a. Find the <security-configuration> section of the file.

b. If enforce-valid-basic-auth-credentials is already defined in this section,then change its value to false. Otherwise, add the following line before the</security-configuration> line:<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>

3. Restart the WebLogic server.

4. Deploy the CMIS archive file using the WebLogic Console.

Red Hat JBoss EAP 4.3.0On JBoss EAP 4.3.0 deploy emc-cmis.war.

You can deploy the CMIS or an ECS EAR file to JBoss using normal JBoss deployment. The followingdeployment procedure is applicable for JBoss 4.3.0:

1. Copy the EAR file to the <JBossInstallationDir>/server/<serverName>/deploydirectory where <JBossInstallationDir> is the installation directory for JBoss and <serverName> isthe name of the JBoss server.

2. Start the JBoss application server if it is not already started. If JBoss is already running, theEAR file will deploy automatically.


http://download.oracle.com/docs/cd/E11035_01/wls100/security/thin_client.html#wp1057361

http://download.oracle.com/docs/cd/E11035_01/wls100/security/thin_client.html#wp1057361

http://download.oracle.com/docs/cd/E11035_01/wls100/security/index.html


Red Hat JBoss EAP 5.1On JBoss EAP 5.1 deploy emc-cmis.war.

You can deploy CMIS to JBoss EAP 5.1 using the normal JBoss deployment procedure. However, youwill need to perform the following steps to configure JBoss at startup:

1. Add the following startup argument to the JBoss startup script (run.sh on Linux and Unix,or run.bat on Windows):-Djboss.vfs.forceVfsJar=true

2. Start JBoss with the following argument to bind it to all IP addresses.$ run.bat -b 0.0.0.0

For more detail refer to http://community.jboss.org/wiki/JBossRunParameters.


for more detail: http://community.jboss.org/wiki/JBossRunParameters

Chapter 4Post Deployment

This chapter describes deployment validation and the CMIS service addresses.

ValidationOn successful deployment, you should be able to access the CMIS home page at the following URL:http://<host>:<port>/<contextPath>

Note: The application context path will vary depending on your deployment. In most deploymentsthe default context path will be emc-cmis, based on the name of the archive file.

RESTful AtomPub service documentThe service document defining the RESTful AtomPub binding can be obtained from this address:http://<host>:<port>/<contextPath>/resources/

Web service entry pointsYou can view the WSDL for any of the SOAP web services via a URL similar to the following:http://<host>:<port>/<contextPath>/services/RepositoryService?wsdl

TheWSDL files for each of the CMIS web services are essentially identical: each one defines endpointsfor all of the CMIS web services, which are shown in the following table:

Table 4. CMIS web service endpoints

Web service Address

ACLService http://<host>:<port>/<contextPath>/services/ACLService

DiscoveryService http://<host>:<port>/<contextPath>/services/DiscoveryService

MultiFilingService http://<host>:<port>/<contextPath>/services/MultiFilingService

NavigationService http://<host>:<port>/<contextPath>/services/NavigationService


Post Deployment

Web service Address

ObjectService http://<host>:<port>/<contextPath>/services/ObjectService

RelationshipService http://<host>:<port>/<contextPath>/services/RelationshipService

RepositoryService http://<host>:<port>/<contextPath>/services/RepositoryService

VersioningService http://<host>:<port>/<contextPath>/services/VersioningService


Index

AACLService

URL, 23anonymous access

all repositories, 17multiple repositories, 17one repository only, 17repository, 15settings, 17user name, 16user password, 16wildcard (*), 17

AtomPubservice document URL, 23

Ccache

CMIS object type definition size, 11CMIS type definition update

interval, 11expiration, DFC session service

tokens, 12expiration, MIME type, 12items cached, 11size, CMIS type definition, 13size, MIME type, 13type definition cache expiration, 13

cmis.anonymous_access.principal.passworddescription, 16

cmis.anonymous_access.principal.usernamedescription, 16

cmis.anonymous_access.repositorydescription, 15

cmis.default_max_itemsdescription, 14response, 18

cmis.exception.full_message.appenddescription, 15

cmis.max_items_upper_limitdescription, 15response, 18

cmis.mime_type.cache_expiration_after_x_secondsdescription, 12

cmis.mime_type.cache_sizedescription, 13

cmis-runtime.propertiesdescription, 11

cmis.temp_file_cleaner.periodically_cleanup_every_x_secondsdescription, 14

cmis.temp_file.expiration_after_x_secondsdescription, 14

cmis.token.cache_expiration_after_x_secondsdescription, 12

cmis.token.cache_size, 13cmis.type_info.cache_expiration_after_x_

seconds, 13cmis.type_info.cache_size

description, 13collection. See responsecom.documentum.fc.tools.

RegistryPasswordUtils, 11connection broker

specifying host name, 10specifying port, 10

Content Serverinstallation on, 7

DDFC

session service token cacheexpiration, 12

session service token cache size, 13dfc.cache.ddinfo.size

description, 11dfc.cache.type.currency_check_interval


Index

description, 11dfc.docbroker.host

description, 10dfc.docbroker.port

description, 10dfc.globalregistry.password

description, 10dfc.globalregistry.repository

description, 10dfc.globalregistry.username

description, 10dfc.properties

location, 10dfc.search.external_sources.enable

description, 10dfc.search.external_sources.host

description, 11DiscoveryService

URL, 23docbroker. See connection brokerDocumentum CMIS

home page URL, 23

EEAR file

emc-cmis-was61.ear, 8emc-cmis-wls.ear, 8emc-cmis-wls1030.ear, 8

ECIS. See Federated Search Services (FS2)encryption

global registry user password, 11error messages

Documentum, 15

FFederated Search Services (FS2)

enabling, 10host name, 11

Gglobal registry repository

encrypt user password, 11specifying repository name, 10specifying user name, 10specifying user password, 10

Hheap space

JVM, 9

Iinstallation

files, list of, 7JBoss 4.3.0, 21JBoss 5.1, 22non-Content Server host, 7on Content Server host, 7Tomcat, 19validation, 23WebLogic, 21WebSphere 6.1, 20WebSphere 7.0, 20

Integer.MAX_VALUEresponse, 18

Jjava.security.egd

Linux, 9JBoss

4.3.0, installation, 215.1, installation, 22installation file, 8

JVMheap space, 9PermGen space, 9

LLinux

java.security.egd, 9securerandom.source, 9urandom generators, 9

MmaxItems. See responseMIME type

cache expiration, 12cache size, 13

MultiFilingServiceURL, 23

NNavigationService


Index

URL, 23

OObjectService

URL, 24

PPermGen space

JVM, 9

RRelationshipService

URL, 24repository, 17

See also anonymous accessanonymous access, 15 to 16, 17

RepositoryServiceURL, 24

responsecmis.default_max_items, 18cmis.max_items_upper_limit, 18Integer.MAX_VALUE, 18maximum number of items, 14, 18maximum number of items, client

setting, 15maxItems, 18

Ssecurerandom.source

Linux, 9security

SOAP binding Web services securityconfiguration file, 12

security.configuration.filedescription, 12

Ttemporary files

cleanup interval, 14

expiration, 14Tomcat

installation, 19installation file, 8

Uurandom generators

Linux, 9user, 17

See also anonymous accessconfiguration, anonymous, 17

VVersioningService

URL, 24

WWAR file

emc-cmis.war, 8Web service

WSDL entry point URLs, 23WebLogic

10g (10.3.0), installation file, 811g (10.3.3), installation file, 8installation, 21

WebSphere6.1, installation, 206.1, installation file, 87.0, installation, 207.0, installation file, 8

X-Xms

recommended value, 9-Xmx

recommended value, 9-XX:MaxPermSize

recommended value, 9


Documents

EMC Documentum Content ManagementInteroperability Services