Get the Software

Skip to end of metadata
Go to start of metadata

Get the Software to Install a Communications Suite Deployment

Topics:

This icon represents downloading and installing." Download

To install a Communications Suite 7 deployment, download the necessary software from http://edelivery.oracle.com/.

  1. Click Continue in the first paragraph.
    A new page is displayed.
  2. From the drop-down menu, select Oracle Communications Applications and platform then click Go.
    A list of items is displayed.
  3. Select Oracle Communications Unified Communications Suite 7 Media Pack then click Continue.
    A set of Communications Suite downloads is displayed.
  4. Click Download for the component you need.

In addition, you might need some or all of the following dependent component products, which you obtain separately:

For more information about Communications Suite 7 component product dependencies, see Requirements for Communications Suite 7.

Download the JES 5 Update 1 distro to obtain Access Manager 7.1 and Web Server 7.0 software.

MySQL 5.1 (required for Calendar Server 7) is included in the Sun Java Communications Suite distro.

Notes and Caveats

Download the GlassFish Enterprise Server file directly from the Communications Suite download site. Do not install the version of Application Server bundled with JES 5 Update 1. That is an older version of Application Server.
Download Directory Server Enterprise Edition 6.3.1 (minimum) from the Communications Suite download site before you run the JES 5 Update 1 installer. Do not install the version of Directory Server bundled with JES 5 Update 1. That is an older version of Directory Server.

If you already started with an older DSEE version, you can still get to the recommended DSEE 6.3.1. You must apply an upgrade patch as well as other patches to upgrade to DSEE 6.3.1.

For example, if you obtained the native package format of DSEE on the Solaris 10 x86 or SPARC platform, you must start by installing the DSEE 6.2 version bundled with JES 5 Update 1, then upgrade to DSEE 6.3.1.

You can instead take the easier path: Download and install the version of DSEE 6.3.1 directly from the Communications Suite download site.

If you are installing Access Manager 7.1 on a Red Hat Linux system, you should verify that a compatible version of Java Development Kit (JDK) is installed. For details, see Verifying the Correct JDK Version to Support Access Manager.
The Communications Suite DVD does not contain the Sun JES 5 Update 1 distro or the Directory Server Enterprise Edition software.
To download Connector for Outlook or Communications Sync, choose Windows as the download platform on the download page.

Licensing Information

For more information regarding entitlements (RTU and support) and licensing, see Communications Suite Licensing Information.

Labels:
installing installing Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jun 12, 2008

    There are native packages for DSEE 6.3 on RHEL.
    Go to sunsolve.sun.com and get patch 125309 (latest rev is -07).
    The patch contains the RPMs.

    Aside: In reality, there are no "patches" on Linux unlike Solaris.
    Thus a "linux" patch on sunsolve contains full RPMs.

    DSEE 6.3 is recommended for CS6 because DSEE 6.2 is no longer available.

    Communications Express does run with DSEE 6.2

  2. Jun 12, 2008

    >> about DSEE version: what is your recommendation for RHEL 4?

    The recommendation from the Directory Server team is to also run DS6.3 due to known issues with DS6.2:

    http://blogs.sun.com/dsee/entry/dsee_6_2_sun_alert

    >> Unfortunately there is no easy DSCC install and I could not find smcwebserver.

    DSCC installation is fairly straight-forward (and faster) from the ZIP installer e.g.

    ***************
    => download zip install version of Directory Server 6.3

    => expand download
    => as the root user:
    mkdir dsee6; cd dsee6
    gunzip -dc ../DSEE.6.3.Linux-X86-full.tar.gz | tar xf -

    => install product
    cd DSEE_ZIP_Distribution
    ./dsee_deploy install -i /opt/sun/directory/
    => accept license

    => deploy directory server instance
    mkdir -p /var/opt/sun/directory/
    cd /opt/sun/directory/ds6/bin
    ./dsadm create /var/opt/sun/directory/dsins1
    Directory Manager password: <directory manager password>

    => create base user/group suffix
    ./dsadm start /var/opt/sun/directory/dsins1
    ./dsconf create-suffix "<suffix>"
    Enter "cn=Directory Manager" password: <directory manager password>
    ***************

    You would replace <directory manager password> with an appropriate password, and <suffix> with an appropriate value for your environment e.g. o=isp

    The smcwebserver is actually part of the JES5u1 installer and should be installed if you select "All Shared Components".

  3. Oct 15, 2009

    sje

    The documentation recommends using Sun Java System Application Server 9.1 Update 2 for the delegated administrator.
    I can't find this product in the downloads. Where do we get this product from? The Sun Java Enterprise System 5u1 download only contains Application Server Enterprise Edition 8.2 Patch 2.

    1. Oct 16, 2009

      You can still get it from the Comms 6 U2 download site.

      Joe

  4. Jan 12, 2010

    DSEE 7 is not mentioned. If we have to install today is it preferrable to use DSEE 6.3.1 or DSEE 7 or is it indifferent ?

    1. Jan 12, 2010

      DS 6.3.1 is the officially supported version for the Comms 7 release. DS 7 will most likely be supported in a future update.

      Joe

    2. Jun 16, 2010

      DSEE 7 was released after Comms Suite R7 was released. Having said that, unofficially, a couple of users have not encountered any issues with using DSEE7 with Comms Suite R7.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.