IMPORTANT:If you are installing Novell Teaming for use with eDirectory and GroupWise, see Installing Novell Teaming with GroupWise
in Novell Teaming and Conferencing
in the GroupWise 7 Interoperability Guide for more information.
A sample installer.xml file is shown below:
NOTE:For Windows, use forward slashes for all directory paths in the installer.xml file.
<!-- -->
<!-- ICEcore Installation Configuration File -->
<!-- -->
<ICEcoreConfig version="4">
<Install type="0"/>
<Environment>
<!-- The path to JAVA_HOME -->
<JDK JAVA_HOME="" type="Sun" />
<!-- What userid to run as (Linux-only) -->
<!-- Also what userId and groupId to use -->
<!-- as owner of the data directories. -->
<Ids userId="" groupId="" />
<!-- Where does the ICEcore software reside? -->
<SoftwareLocation path="" />
</Environment>
<!-- -->
<!-- Network Settings -->
<!-- -->
<!-- The host name or IP address of the server must be -->
<!-- specified here. The default, localhost, is only -->
<!-- appropriate for test configurations with no remote -->
<!-- access. -->
<!-- -->
<!-- If you have a dedicated server, setting the port -->
<!-- to "80" and/or securePort to "443" avoids having -->
<!-- to specify a port number in browser URLs. -->
<!-- -->
<!-- NOTE: On Linux/UNIX based systems, it is very dangerous -->
<!-- to run this server on any port number less than 1024, -->
<!-- since that would require the web server to run as the -->
<!-- root user. If you must run on a port lower than 1024, -->
<!-- please see the ICEcore documentation referring to port -->
<!-- forwarding via iptables. -->
<!-- -->
<!-- If you use some sort of port forwarding or proxying -->
<!-- (e.g., iptables or iChain), use the listenPort and -->
<!-- secureListenPort settings to specify the port numbers -->
<!-- to use on the SERVER. The port and securePort settings -->
<!-- should refer to what external users use to access -->
<!-- the system. (If not specified, the listen ports use -->
<!-- the corresponding port/securePort setttings.) -->
<!-- -->
<!-- A default certificate is supplied for SSL connections. -->
<!-- You should replace this with your certificate. -->
<!-- This can be placed in the conf/.keystore file or -->
<!-- change the keystoreFile attribute to point to the -->
<!-- certificate. -->
<!-- -->
<!-- -->
<!-- OES2 servers will need to reassign the ajpPort and -->
<!-- shutdownPorts as they will collide with other software. -->
<!-- ajpPort="8010" and shutdownPort="8011" seem to work -->
<!-- well. See the Install Guide Network Planning section -->
<!-- for more details on port conflicts. -->
<!-- -->
<Network>
<Host name="localhost"
port="8080" listenPort=""
securePort="8443" secureListenPort=""
shutdownPort="8005"
ajpPort="8009"
keystoreFile=""
/>
<WebServices enable="true" />
<Liferay sessionTimeoutMinutes="240" />
<TomcatAccessLog enable="false" />
</Network>
<!-- -->
<!-- Memory (RAM) Settings -->
<!-- -->
<!-- ICEcore requires a minimum of 512m to operate. -->
<!-- 1g is recommended for basic production operation. -->
<!-- Generally do not allocate more than 75% of available -->
<!-- physical memory to ICEcore. -->
<!-- -->
<!-- Specify amounts as Nm for N megabytes (e.g., 1500m) or -->
<!-- Ng for N gigabytes (e.g., 3g). -->
<!-- -->
<Memory>
<JavaVirtualMachine mx="1g" />
</Memory>
<!-- -->
<!-- File System Configuration -->
<!-- -->
<!-- Modify the configName to your desired configuration -->
<!-- in the FileSystem element below. You must set the -->
<!-- configName to the exact configuration in the file: -->
<!-- basic - Simple one-directory setup -->
<!-- advanced - Advanced multiple-directory setup -->
<!-- -->
<!-- WARNING! Changing a directory path does NOT relocate -->
<!-- data after the product has been installed. You must -->
<!-- coordinate any changes here with appropriate file system -->
<!-- modifications (including directory protections and -->
<!-- ownership where applicable). -->
<!-- -->
<FileSystem configName="basic">
<!-- The basic configuration only requires that you -->
<!-- specify a root directory for the data and -->
<!-- ICEcore takes care of the rest. -->
<!-- -->
<!-- IMPORTANT NOTE FOR WINDOWS USERS: Use forward -->
<!-- slash as directory separator! -->
<Config id="basic">
<RootDirectory path="/home/icecoredata" />
</Config>
<!-- With the advanced configuration you can specify -->
<!-- individual directory locations. -->
<!-- Add path attributes for those directories you -->
<!-- want to locate elsewhere. For example, -->
<!-- <SimpleFileRepository path="/share/icecoredata" /> -->
<!-- -->
<!-- IMPORTANT NOTE FOR WINDOWS USERS: Use forward slash -->
<!-- as directory separator! -->
<Config id="advanced">
<RootDirectory path="/home/icecoredata" />
<SimpleFileRepository />
<JackrabbitRepository />
<ArchiveStore />
<CacheStore />
<LuceneIndex />
</Config>
<!-- The liferay data dirs configuration allows you to -->
<!-- change the directories that liferay uses for -->
<!-- its internal data directories. The value typically -->
<!-- is a subdirectory where the other ICEcore data -->
<!-- resides. -->
<!-- -->
<!-- Early beta sites may want to use a different setting -->
<!-- called "default", which means the *default directory* -->
<!-- of whatever user id the server runs as. Generally -->
<!-- speaking this is not a great idea, and the option -->
<!-- is there solely to accomodate beta sites who predate -->
<!-- the ability to explicitly set where Liferay stored -->
<!-- its files. -->
<!-- -->
<!-- NOTE: If you change the use setting after you have -->
<!-- already started using liferay, you need to copy -->
<!-- all the data from the default dirs to the new dirs -->
<!-- BEFORE you restart the server! -->
<!-- -->
<!-- IMPORTANT NOTE FOR WINDOWS USERS: Use forward slash -->
<!-- as directory separator! -->
<LiferayDataDirs use="custom">
<RootDirectory path="/home/icecoredata/liferay" />
<DocumentLibraryRoot dir="documentlibrary/root" />
<DocumentVersionLibrary dir="documentlibrary/vroot" />
<JackRabbit dir="jackrabbit" />
<AutoDeploy dir="deploy" />
<Lucene dir="lucene" />
</LiferayDataDirs>
</FileSystem>
<!-- -->
<!-- Database Configuration -->
<!-- -->
<!-- Modify the configName to your desired configuration -->
<!-- in the Datatabase element below. You must set the -->
<!-- configName to the exact configuration in the file: -->
<!-- MySQL_Default - For MySQL -->
<!-- SQLServer_Default - For Microsoft SQL Server -->
<!-- -->
<!-- Change the Resources for the configuration you chose -->
<!-- (the defaults are pretty good for a simple configuration -->
<!-- with the database running locally, but you will probably -->
<!-- have different passwords!). -->
<Database configName="MySQL_Default">
<!-- -->
<!-- MySQL_Default -->
<!-- -->
<Config id="MySQL_Default" type="MySql">
<Resource for="liferay"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/lportal?useUnicode=true&characterEncoding=UTF-8"
username="root"
password="root"
/>
<Resource for="jboss"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/jbossportal?useUnicode=true&characterEncoding=UTF-8"
username="root"
password="root"
/>
<Resource for="icecore"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/sitescape?useUnicode=true&characterEncoding=UTF-8"
username="root"
password="root"
/>
</Config>
<!-- -->
<!-- SQLServer_Default -->
<!-- -->
<Config id="SQLServer_Default" type="SQLServer">
<Resource for="liferay"
driverClassName="net.sourceforge.jtds.jdbc.Driver"
url="jdbc:jtds:sqlserver://localhost/lportal;SelectMethod=cursor"
username="sa"
password="sa"
/>
<Resource for="jboss"
driverClassName="net.sourceforge.jtds.jdbc.Driver"
url="jdbc:jtds:sqlserver://localhost/jbossportal;SelectMethod=cursor"
username="sa"
password="sa"
/>
<Resource for="icecore"
driverClassName="net.sourceforge.jtds.jdbc.Driver"
url="jdbc:jtds:sqlserver://localhost/sitescape;SelectMethod=cursor"
username="sa"
password="sa"
/>
</Config>
<!-- -->
<!-- Oracle_Default -->
<!-- -->
<Config id="Oracle_Default" type="Oracle">
<Resource for="liferay"
driverClassName="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:thin:@//localhost:1521/orcl"
username="lportal"
password="pw"
/>
<Resource for="icecore"
driverClassName="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:thin:@//localhost:1521/orcl"
username="sitescape"
password="pw"
/>
</Config>
</Database>
<!-- -->
<!-- Lucene Configuration Settings -->
<!-- -->
<!-- -->
<!-- The Lucene index can be run "local" (within -->
<!-- the context of this application) or "server" -->
<!-- (run as its own server). Additionally it -->
<!-- can be run as its own server on this system -->
<!-- or on a remote system. -->
<!-- -->
<!-- Note: The rmi port need only be set if running -->
<!-- in server mode. (And then, only if the default -->
<!-- port cannot be used. -->
<Lucene luceneLocation="local">
<Resource
lucene.index.hostname="localhost"
lucene.flush.threshhold="100"
lucene.max.booleans="10000"
lucene.max.merge.docs="1000"
lucene.merge.factor="10"
lucene.rmi.port="1199"
/>
</Lucene>
<!-- -->
<!-- RSS Configuration Settings -->
<!-- -->
<!-- RSS feeds are inherently insecure as they do not -->
<!-- use the standard authentication mechanism. If you -->
<!-- do not want to have users create RSS subscriptions, -->
<!-- set the enable property to "false". -->
<!-- -->
<!-- If you have RSS feeds enabled, you can tune the maximum -->
<!-- number of days to keep in the feed and the maximum -->
<!-- number of days to keep updating a feed when there are -->
<!-- no clients reading it. -->
<!-- -->
<RSS enable="true">
<Feed max.elapseddays="31" max.inactivedays="7" />
</RSS>
<!-- -->
<!-- Email Configuration Settings -->
<!-- -->
<!-- Edit the Outbound and Inbound settings as required. -->
<!-- -->
<!-- -->
<!-- For inbound mail (postings) you need to specify either -->
<!-- pop3 or imap (or pop3s/imaps for SSL connections to -->
<!-- mail servers), and fill out the settings for which one -->
<!-- you choose. These settings are not used until you -->
<!-- enable incoming email within the product. If you do -->
<!-- not plan on using inbound email, you can ignore these -->
<!-- settings. -->
<!-- -->
<!-- -->
<!-- -->
<EmailSettings>
<Outbound>
<Resource
mail.transport.protocol="smtp"
mail.smtp.host="mailhost.yourcompany.com"
mail.smtp.user="icecore@yourcompany.com"
mail.smtp.password=""
mail.smtp.auth="false"
mail.smtp.port="25"
mail.smtps.host="mailhost.yourcompany.com"
mail.smtps.user="icecore@yourcompany.com"
mail.smtps.password=""
mail.smtps.auth="false"
mail.smtps.port="465"
/>
</Outbound>
<Inbound useAliases="false">
<Resource
mail.store.protocol="pop3"
mail.pop3.host="localhost"
mail.pop3.auth="true"
mail.pop3.user="popEmailUserId"
mail.pop3.password="passwordHere"
mail.pop3.port="110"
mail.pop3s.host="localhost"
mail.pop3s.auth="true"
mail.pop3s.user="popEmailUserId"
mail.pop3s.password="passwordHere"
mail.pop3s.port="995"
mail.imap.host="localhost"
mail.imap.auth="true"
mail.imap.user="imapEmailUserId"
mail.imap.password="passwordHere"
mail.imap.port="143"
mail.imaps.host="localhost"
mail.imaps.auth="true"
mail.imaps.user="imapEmailUserId"
mail.imaps.password="passwordHere"
mail.imaps.port="993"
/>
</Inbound>
</EmailSettings>
<!-- -->
<!-- Presence Configuration Settings -->
<!-- -->
<!-- -->
<!-- Use those settings to link your ICEcore and Conferencing -->
<!-- servers together. Leave the presence.service.enable -->
<!-- setting at false if you do not use the conferencing -->
<!-- real time software. -->
<!-- -->
<!-- The values to fill in this section are obtained when -->
<!-- ICEcore Conference has been installed and configured. -->
<!-- If you do not know them now, you can update this -->
<!-- configuration later and apply the settings. -->
<!-- -->
<!-- The jabber.server is the IP or host of the ICEcore -->
<!-- Conference XML Router. -->
<!-- -->
<!-- The default ICEcore Conference admin.id is admin, and -->
<!-- default password is also admin. Change the admin.passwd -->
<!-- to match the ICEcore Conference administrator password -->
<!-- you have set. -->
<!-- -->
<!-- The jabber.domain is the host name of the XML router -->
<!-- -->
<!-- The community.id is the name of the community you -->
<!-- created with the ICEcore Conference console. -->
<!-- -->
<!-- Change the hostname part of the conferencing.url to -->
<!-- the ip or host of the ICEcore Conference Web Portal -->
<!-- (do not change the port or the rest the URL). -->
<!-- -->
<Presence>
<Resource
presence.service.enable="false"
presence.service.jabber.server="zon-server.yourcompany.com"
presence.broker.admin.id="admin"
presence.broker.admin.passwd="admin"
presence.broker.jabber.domain="newzon"
presence.broker.default.community.id="yourcommunity"
presence.broker.zon.url="http://zon-server.yourcompany.com:8000/imidio_api/"
/>
</Presence>
<!-- -->
<!-- Mirrored Folders Configuration Settings -->
<!-- -->
<!-- Mirrored folders are local/shared directories that -->
<!-- are exposed within ICEcore. The directories must be -->
<!-- configured here first before they are available to -->
<!-- the folder configuration interface within ICEcore (see -->
<!-- Modify a Folder). -->
<!-- -->
<!-- For security reasons the set of people who can map -->
<!-- ICEcore folders to these shared directories is limited -->
<!-- Specify the specific ICEcore users or groups that are -->
<!-- allowed to map each folder (separated by semi-colons). -->
<!-- -->
<!-- Each mirrored folder configuration must have a unique -->
<!-- id (use a-z,0-9), and a title to be used in the user -->
<!-- interface. Set enabled to true to make the mirrored -->
<!-- folder configuration active. The examples below show -->
<!-- how to set up both file system and Sharepoint mirrors. -->
<!-- -->
<!-- By default the mirrored folder is set to readonly. -->
<!-- This means that ICEcore users can access the files, but -->
<!-- cannot modify them. Set the readonly attribute to false -->
<!-- to allow read/write access to the folder (based on both -->
<!-- this server's access to the directory and the ICEcore -->
<!-- user's access). -->
<!-- -->
<!-- There are three mirrored folder types: file (for -->
<!-- normal file systems), webdav (for WebdDAV servers) that -->
<!-- support basic authentication, and sharepoint (for -->
<!-- Microsoft Sharepoint WebDAV access). -->
<!-- -->
<MirroredFolders>
<MirroredFolder enabled="false" type="file"
id="fs1" title="Shared Files 1"
rootPath="k:/somedir" readonly="true">
<AllowedUsers idList="admin;u1;u2;u3" />
<AllowedGroups idList="g1;g2;g3" />
</MirroredFolder>
<MirroredFolder enabled="false" type="file"
id="fs2" title="Shared Files 2"
rootPath="/sharedFiles/someDirectory" readonly="true">
<AllowedUsers idList="admin;u1;u2;u3" />
<AllowedGroups idList="g1;g2;g3" />
</MirroredFolder>
<MirroredFolder enabled="false" type="sharepoint"
id="sp1" title="Sharepoint 1"
rootPath="/Shared Documents/cool-dir" readonly="true">
<WebDAVContext hostUrl="http://hostname" user="accessId" password="pass" />
<AllowedUsers idList="admin;u1;u2;u3" />
<AllowedGroups idList="g1;g2;g3" />
</MirroredFolder>
</MirroredFolders>
<!-- -->
<!-- iChain Single Sign-On Support -->
<!-- -->
<!-- -->
<!-- To use iChain SSO, set the enable attribute to true. -->
<!-- Set the Logoff URL to the address used to trigger an -->
<!-- iChain logoff. Also set the ip address of the iChain -->
<!-- proxy server. Only transactions from that address and -->
<!-- localhost are allowed. -->
<!-- -->
<SSO>
<iChain type="1" enable="false">
<Logoff url="http://something" />
<Proxy ipaddr="ipaddr" />
</iChain>
</SSO>
<!-- -->
<!-- Custom Configuration Settings -->
<!-- -->
<!-- Custom properties set here are placed in the -->
<!-- ssf-ext.properties file. -->
<!-- -->
<CustomProperties>
<Resource
/>
</CustomProperties>
</ICEcoreConfig>