This chapter describes the pre-installation steps you must complete before installing and configuring Oracle Communications Convergence.
GlassFish Server or Oracle WebLogic Server is a Java application and needs a Java environment in which to run.
Install the 32-bit Java JDK if you run a 32-bit OS. Install the 64-bit Java JDK if you run a 64-bit OS.
Download the Java software from the Oracle web site:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
For each optional or required software application you plan to install to deliver Convergence services, you must satisfy its software requirements and pre-installation tasks. For example, if you plan to integrate Convergence with Oracle Communications Messaging Server, Oracle Communications Calendar Server, and Oracle Communications Contacts Server, you must satisfy the software requirements for each of these applications and complete all their pre-installation tasks.
You prepare your directory server by running the directory server setup script (comm_dssetup.pl) against it. You can run the script in either interactive or silent mode.
You must ensure that the directory server is running the correct version of the directory server setup script. See "System Requirements" for more information about the required script version.
To prepare the directory server:
Download the comm_dssetup.pl script from the Oracle software delivery web site:
The comm_dssetup.pl script is available in the same software package as the Convergence software.
Copy the directory server ZIP file to a temporary directory on your directory server hosts and extract the files.
Log on to the directory server host machine as the superuser (root).
Start the directory server, if necessary.
Change to the directory where you extracted the comm_dssetup.pl script.
Install the comm_dssetup.pl script.
./commpkg install
Select Comms DSsetup from the list of applications to install and proceed with the installation.
See "commpkg Reference" for more information about the commpkg command.
Run the comm_dssetup.pl script without any arguments.
/usr/bin/perl comm_dssetup.pl
Answer the command-line prompts.
Note:
You can use either LDAP Schema 2 or Schema 1.If the directory server is already installed at your site, users have already been provisioned. If you have just installed the directory server at your site, then you need to provision users. For information about provisioning users and schema, see Communications Suite Schema Reference.
Install and configure the Oracle Communications software required to deliver your planned Convergence services.
Refer to the documentation for each Oracle Communications application for pre-installation, installation, configuration, and post-installation details.
You must enable HTTP service in Messaging Server by setting the related configuration parameters.
To enable MSHTTP, do one of the following and restart Messaging Server:
If Messaging Server is deployed with a legacy configuration, set service.http.enable parameter to 1.
If Messaging Server is deployed with a Unified Configuration, set the http.enable parameter to 1.
See the Messaging Server wiki for more information about http parameters:
You must enable email message body filtering in Messaging Server. Message body filtering allows users to create mail filter rules on the content of email messages.
To enable email message body filtering, do one of the following:
If Messaging Server is deployed with a legacy configuration, edit option.dat, locate the ENABLE_SIEVE_BODY parameter, and set it to 1.
If Messaging Server is deployed with a Unified Configuration, set the mta.enable_sieve_body parameter to 1.
See the Messaging Server wiki for more information about the enable_sieve_body parameter:
http://msg.wikidoc.info/index.php/Enable_sieve_body_MTA_option
If you are configuring Convergence with the Instant Messaging service, do the following to prepare Instant Messaging Server:
Configure Instant Messaging Server with the XMPP/HTTP Gateway Deployment parameter set to false.
As the XMPP/HTTP Gateway is deployed through Convergence, its value is set to true when you configure Convergence.
See Instant Messaging Server Installation and Configuration Guide for more information.
Using the Instant Messaging Server imconfutil command-line utility, add the c2s component:
imconfutil -u set-listener-prop s2s protocols="s2s,component,c2s" -c /opt/sun/comms/im/config/iim.conf.xml
Using the imconfutil command, set the iim_agent.enable property to true:
imconfutil set-prop iim_agent.enable=true -c /opt/sun/comms/im/config/iim.conf.xml
Using the imconfutil command, configure the httpbind component Jabber ID (JID) and password. For example:
imconfutil add-component id=httpbind1 jid=convergence1-jid.httpbind.MyDomain.com password=secret -c /opt/sun/comms/im/config/iim.conf.xml
Using the imconfutil command, configure the avatar component JID and password. For example:
imconfutil add-component id=avatar1 jid=avatar1-jid.avatar.MyDomain.com password=secret -c /opt/sun/comms/im/config/iim.conf.xml
Note:
The httpbind and avatar JIDs can be any string. These values do not have to identify a particular Instant Messaging host and domain name. However, it is a good practice to make these values meaningful. For example, include the host and domain name in these JIDs to make the identifiers easy to recognize.The passwords for the httpbind and the avatar JIDs can be unique. They do not have to match any other password used for Instant Messaging Server or other back-end servers.
The JIDs and passwords configured in the iim.conf.xml file must match the httpbind and Avatar JIDs that you specify when you run the Convergence initial configuration program.
See "Configuring Instant Messaging for Multiple Convergence Instances" if you intend to configure multiple instances of Convergence to use the same Instant Messaging server.
If you are configuring multiple instances of Convergence to use one Instant Messaging server, you must set up a unique httpbind and avatar JID value for each instance of Convergence. See "Preparing Instant Messaging Server for Convergence Integration" for information about setting httpbind and avatar JID values.