Get the Software

Skip to end of metadata
Go to start of metadata
installing installing Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jun 04, 2008

    "commpkg upgrade" should work for upgrading most products from the Comms6 beta version to the Comms6 RR version.
    Some products do not support commpkg upgrade, notably CE and Convergence at this time.

    1. Jun 05, 2008

      Hi !

      Thank's both for your answers, that's what i thought about the upgrade, well i guess we're going to move on the beta : our DSEE is 6.3 and i guess it'll be faster to upgrade CE & Convergence rather than upgrading all the messagning sytem : we're on a several hosts over two places and several master DSEE...

      thank's again for your answers !!


  2. Jun 12, 2008


    about DSEE version: what is your recommendation for RHEL 4?
    I realized that there are no native packages for DSEE 6.3 on RHEL, so I installed from zip.
    Unfortunately there is no easy DSCC install and I could not find smcwebserver.
    Would it be better to install DSEE 6.2 from JES 5u1 and upgrade/patch to DSEE 6.3?
    What is the reason for the requirement of DSEE 6.3 for CS6?
    Will Communications Express run with DSEE 6.2?


    1. Jun 12, 2008

      There are native packages for DSEE 6.3 on RHEL.
      Go to 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:

      >> 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. Nov 04, 2008

    Based on this wiki doc, it is clear that Comms Suite 6 does not include all the dependant products (DSEE, AM, WS), and the user is advised of the
    Url's and pages where to download from such required components. It would be nice and clarifier some statements regarding the entitlements (RTU and support) the user have to use such separate licensed products for the purpose of Comms Suite.

      1. Nov 04, 2008

        Sure! Thank you

  4. Jul 12, 2011

    I'm using Sun Java Enterprise System 5u1 is that going to work with Suite 7? It's Enterprise edition 8.2 patch 2 and I can't seem to find any later releases online. Just want to check before I do the install.


    ivr software

    1. Jul 13, 2011

      If you are going to use CommSuite 7 U1, then you'll need to look at the requirements for dependent software for that release:



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.