Skip Headers
Oracle® Communication and Mobility Server Administrator's Guide
Release 10.1.3

Part Number E10292-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

C The Oracle Communicator Configuration File

This appendix includes the customize-sample.xml file for Oracle Communicator described in Chapter 11, " Configuring Oracle Communicator".

The customize-sample.xml File

customize-sample.xml (Example C-1) is the template file for customize.xml.

Example C-1 The customize-sample.xml File

<?xml version="1.0" encoding="UTF-8" ?> 
- <Customize>
- <!-- 
 in order to provide default settings for the installation,
     this file should be edited and renamed customize.xml,
     then included in the Oracle Communicator installation
     self-extracting RAR (i.e. OracleCommunicatorSetup.exe)
     for true/false values, 0 means false, 1 means true
     it is expected that most administrators will need
     to modify at least the proxy and XDMS settings to
     reflect the site topology, and that most administrators
     will choose to modify the STUN and LDAP settings
     as well
     this file lists default values; any property in this
     file may be removed with no impact on the installation;
     it is recommended that an administrator only keep
     those properties for which they intend to use
     non-default values
- <!-- 
 the Vendor section contains properties that will
       remain the same for all user accounts in the
       installation and is not editable through the
       UI by the user 
- <Vendor>
- <!-- 
 if 1, the "Service Settings" menu option will
       be visible, which will open the URL specified
       in Account/Provisioning/Location in a browser 
- <Account>
- <!--  whether or not to use the outbound proxy 
- <!-- 
 the address of the proxy server, preceded by sip:
     if this is not specified, the default is 
     outbound.<host> where <host> comes from the user's
     SIP address 
- <!--  the default UI theme to use 
- <!-- 
 the XDMS server, presence rule and hard state settings;
     if this is not specified the default for the Host is 
     xcap.<host> where <host> comes from the user's SIP address;
     the other values are the same as default except RootContext
     defaults to services instead 
- <XDMSSettings>
- <!-- 
 whether to use rport as described in RFC 3581 for
     NAT traversal; the default is 0; rport may
     not be supported by OCMS in a cluster environment,
     in which case this should be 0 
- <!--  the STUN server 
- <!-- 
 the LDAP server(s) to use for contact searching; by
     default no LDAP server is provided 
- <LdapServers>
- <LdapServer>
- <!-- 
 the attribute to use as the distinguished name
     for authorization 
- <!-- 
 the SipUriAttribute indicates which
     LDAP schema attribute, if any, should be
     mapped to the SIP address of a contact 
- <!-- 
 if true, indicates the SIP address
     of the contact returned by the LDAP server
     will have the sip: protocol prepended 
- <!-- 
 if true, this will cause the SIP address
     of the contact returned by the LDAP server
     to be made lowercase 
- <!-- 
 the URL to launch if the user selects "Service Settings"; that
     option will only be available to the user if Vendor/SelfProv
     is 1 
- <Provisioning>
- <!-- 
 enables/disables VersionControl and provides the URL
              to the upgrade policy XML document; see the
              Administrator's guide for more information;
              by default, VersionControl is disabled 
- <VersionControl>
- <!-- 
 enables/disables the file transfer functionality; in order
     to support file transfer you must have the FileTransferServlet
     deployed; the Location should be the full URL of the
     FileTransferServlet (e.g. 
- <FileTransfer>
  <Location />