Tuesday Jul 28, 2015

Update: Communications Suite Documentation Now on Oracle Help Center

If you are having trouble getting automatically redirected to the new location of the Communications Suite documentation after the CommSuite Wiki was decommissioned (see CommSuite Wiki Has Moved On), here are some direct links to help you out:

We have also noticed the following issues, when being redirected from the old wikis.oracle.com  site to the new location:

  1. HTTPS style links, such as https://wikis.oracle.com/display/CommSuite,  do not redirect, and give an error.
  2. Removing the "https://" from the link and retrying, redirects you to the Oracle Community site. If you read the top of that page, there is a link, FAQ: Wikis.oracle.com FAQ, which explains that the documentation has moved to the Oracle Communications documentation page.
  3. In general, typing an old wiki link without "https://" redirects you to the Oracle Communications documentation page.

Wednesday Jul 15, 2015

CommSuite Wiki Has Moved On

Communications Suite Documentation Now on Oracle Help Center

After July 15, 2015, the CommSuite Wiki will be decommissioned. To find Communications Suite documentation, you'll need to go to the Oracle Help Center, also known as docs.oracle.com. There you'll find documentation for current and legacy Communications Suite releases. As reported previously, we have been transitioning Communications Suite documentation to Oracle Help Center since last year.

For a complete listing of Communications Suite documentation, visit the Oracle Communications documentation page and scroll to the Unified Communications Suite section. There you will find legacy release documentation (in the form of PDF files) as well as up-to-date product documentation (in a variety of formats).

Wednesday Aug 13, 2014

Unified Communications Suite Documentation: A New Direction

OTN Path Ahead

With the availability now of Unified Communications Suite 7.0.6 (shipped on August 13), you'll notice that we are also transitioning to publishing product documentation on the Oracle Documentation Site (also referred to as Oracle Technology Network, or OTN), at:


Scroll to the bottom of this page to view the links to the UCS documentation.

For the Unified Communications Suite 7.0.6 release, documentation for the following component products is published to OTN:

  • Connector for Outlook
  • Contacts Server 8.0
  • Instant Messaging Server

This documentation is only on OTN, and not on the Communications Suite wiki. You'll find pointers to this OTN documentation where you would normally expect to find it on the wiki. Suite-wide documentation for 7.0.6, as well as for the other component products (Messaging Server, Calendar Server, Indexing and Search Service, and so on) is updated on the wiki for this release. Thus, for this release, and perhaps one or two more, the Communications Suite documentation is on both the wiki and OTN.

Going forward, we expect to get all of our documentation onto OTN. With that in mind, here is a mini-FAQ to help you with this new documentation direction:

  1. Why are we moving the UCS documentation to OTN?
    We are moving the UCS documentation to OTN where other Oracle documentation resides so customers are able to find our documentation where they expect it to be. The UCS documentation will also have the same look and feel as other Oracle CGBU documentation that our customers use, allowing for a common user experience across CGBU products.
  2. Will the CommSuite wiki go away?
    No. Previously released documentation will stay on the wiki.
  3. Can I still leave documentation comments?
    Yes. You can still log in to wikis.oracle.com and leave comments. By the way, OTN also enables you to email comments, which are forwarded to us.

Thursday Dec 26, 2013

Phone Home with WebRTC

How annoying in this day and age, right? You are in your browser and want to make a video chat or place a VoIP call, and you are summarily informed that you are short on some required plug-in or other software. This may soon be a scenario of the past, as we see WebRTC come into being. With this in mind, two of my colleagues in SDP recently wrote some posts on WebRTC. Go check 'em out:

Thursday Oct 31, 2013

Unified Communications Suite Ships New Version

We shipped the latest version ( of Unified Communications Suite. The following information should get you started:

Some Changes for

Convergence: Version enables you to use the add-on framework to add third-party services to the Convergence UI. These services include:

  • Advertising
  • Click-to-call service
  • Multinetwork IM
  • SMS (both one-way and two-way)
  • Social media applications (Facebook, Twitter, and Flickr)
  • Video and voice calling capability

For more information, see Overview of Add-on Services in Convergence.

Calendar Server: Version provides a number of security enhancements, including supporting the SSL protocol for all front-end and back-end communications, and the ability to list hosts that are allowed to send iSchedule POST requests. For more information, see Securing Communications to Calendar Server Back Ends.

New Platform Support: Oracle GlassFish Server 3, Oracle Solaris 11, and Oracle Enterprise Linux 6.x are supported in this release of Communications Suite.

Friday Aug 23, 2013

How the Project Was Documented

I happened today to come across the by-now-familiar-and-classic-to-many cartoon of project management, and have to say, the "How the project was documented" panel once again had me in stitches.

The great advantage of wiki publication, which we use for Communications Suite, is the ability to get beyond that "panel" and continually improve our documentation. With that in mind, I wanted to alert our Calendar Server users that I have completed a revamp of the Calendar Server 7 Command-Line Utilities page. Not only have I described some of the options more accurately now, but I think the page is more usable as I have moved deprecated options to a separate section at the end of the page.

As usual, feel free to leave a comment if  you have a documentation related question or idea for improvement.

Thursday Jul 25, 2013

Unified Communications Suite 7 Update 4: New Training Available

Unified Communications Suite training courses have been updated for the current release, UCS 7 Update 4. More details are available at Unified Communications Suite Administration.

Friday Jul 12, 2013

Saving Time: Flip the Switch to Handle iMIP

Messaging Server 7 Update 5 and Calendar Server 7 Update 3 Combine to Process Calendar Invites

DalĂ­ Clockface by Philippe Halsman, 1953

As with any new release of software, there may be new features that don't immediately jump out at you or that fly under the radar. So here's one that might fall into that case for the Communications Suite 7 Update 4 release: you can configure Messaging Server and Calendar Server to automatically process calendar invitations from "external" users. By "external," we mean users who reside either on a different Calendar Server deployment administered by a separate group, or on an outside calendaring system, such as Exchange, Google Calendar, and so on.

Technically, what we are talking about here is configuring Messaging Server to post a calendar event received in an iMIP (iCalendar Message-Based Interoperability Protocol) message to Calendar Server by using the iSchedule protocol. That way, users don't have to do any manual processing on the external calendar invite. The Calendar Server deployment automatically processes these invitations coming from external calendar systems, and to users, handling an external calendar invite then appears just like an calendar internal invite. Time saved, users more happy, what could be better than that?

See the following documentation for more of the techie details and procedures to set up your Messaging Server 7 Update 5 deployment:

Wednesday Jun 19, 2013

In the Zone: Comparison of Solaris 11 and Solaris 10

Came across this good summary of Solaris 11 and Solaris 10 zones that folks might find interesting.

Wednesday Jun 12, 2013

Yo, Mule: That Stubborn and Strong Email

More evidence that email is in fact not dead. Key graph for me:

In one year, workers spend on average, the equivalent of 111 workdays dealing with email.  Most would like better search capabilities and document management features. There's a good business case for this: Just 10% increase in efficiency would buy back more than two workweeks per year per employee.

All the more reason to look at our Indexing and Search Service.

Wednesday May 22, 2013

Oracle Communications Messaging Server: Dealing with Password Expiration

Alerting Messaging Server Users that Their Password Is Expiring

Looking at the support forums today, I was reminded of the new password aging support feature in Messaging Server 7 Update 5:

Messaging Server now honors LDAP password policies. It sends an IMAP ALERT when a user's LDAP password is about to expire. Refer to Directory Server documentation for setting this up (see Oracle Identity Management documentation). You can use MeterMaid to limit the frequency of warnings.

A forum user also supplied a cheat sheet on how to update the necessary LDAP, here.

Update: More info here in this Does Messaging Server Or Convergence Support Password Aging Policy ? [ID 1474404.1] article.

Sunday May 19, 2013

Oracle Communications: Cheat Sheet Documentation

Please welcome another of my Infodev blogging comrades, Brenda, to the Oracle blogosphere. Check out her typewriter-girl-turned-into-technical-support post.

Friday May 17, 2013

Oracle Communications Messaging Server: To Compile or Not to Compile

Compiled Versus Non-Compiled MTA Configurations: Which Strategy Is Best?

Recently, we had a discussion around the pros and cons of using a compiled MTA configuration for Messaging Server. What follows is a summary of this discussion, and also how this relates to the new Unified Configuration.

  • Pros of using a compiled configuration:
    • "The main reason for compiling configuration information is performance."
      In the past, say back in Messaging Server 5 days, this used to be important but with current releases is no longer a factor.
    • "Configuration changes can be tested more conveniently because the configuration files themselves are not 'live' when a compiled configuration is in use."
      This is the main reason now for using a compiled MTA configuration.
  • Cons of using a compiled configuration:
    • Introduces some complexity in management.
    • Non-MTA components do not share the same options with MTA components, so changing a compiled configuration could cause some components to be "live" (non-MTA) before others (MTA). This behavior is independent of the configuration type (legacy or Unified).
    • On non-production systems, compiled configuration is probably not worth the additional overhead.
  • Compiled configuration was the default prior to the Messaging Server 7 Update 4 release. So it is important for new installations (Messaging Server 7 Update 5) to understand whether to use a compiled configuration. Still, it seems likely that most sites would and should use a compiled configuration.
  • The command imsimta cnbuild -remove causes a system to stop using a compiled configuration.
  • To test configuration changes before committing them and going live, use the following command structure:
imsimta test -rewrite -noimage_file you@example.com

You can use the following flags to set the path to the configuration file:


These enable you to carefully clone then customize the configuration files before testing.

About Unified Configuration

Unified Configuration has the ability to save a history of changes and roll back to previous configurations. (See the msconfig history command). Thus, if an undesired configuration behavior takes place, even though a configuration may have passed its validity checks, you can still return easily to a previous configuration.

  • Does Unified Configuration obsolete a compiled configuration?
    • Not yet.
    • Does not address the more complex issues of MTA configuration change coordination.
    • You still need to coordinate multiple configuration changes and test them thoroughly prior to going live.


Wednesday May 15, 2013

Oracle Communications Messaging Server: Tips to Get Started with Unified Configuration

Introduced in the latest Messaging Server release (7 Update 5 Patch 28), Unified Configuration offers up a more "unified" approach to administering your messaging configuration:

  • You don't have to manage multiple configuration files with differing formats, and that you have to edit by hand (and so risk potentially causing an error): instead, you use one administrative tool, msconfig, and all legacy configuration files (with some small exceptions) are consolidated into three configuration files (config.xml being where most configuration data is stored). In addition, Unified Configuration performs validation checking to prevent introducing some configuration errors.
  • You no longer have to deal with configuration settings that themselves are not that straight-forward, and in Unified Configuration, you can use the same settings for many options among the MMP, MTA, and message store configurations.

Getting started with Unified Configuration, I found the following tips and information very useful:

  • Use the configutil -H command to translate the legacy configutil option names to Unified Configuration names. For example:
    # configutil -H -o logfile.imap.expirytime
    Configuration option: logfile.imap.expirytime
    Unified Config Name: imap.logfile.expirytime
  • Upgrading to Messaging Server 7 Update 5 (patch 28) does not mean that you HAVE to run Unified Configuration. You can upgrade and continue to run just as you are in legacy configuration. When/if you want to start using Unified Configuration, then you would use the configtoxml Command to update the configuration.
  • You can run msconfig in either interactive or non-interactive mode. As I have been getting used to Unified Configuration, I find that using interactive mode is very helpful, as the parser lets you know if you have entered an incorrect syntax. Also, you don't have to accept the configuration change until you write it to the configuration.
  • Getting more help: run the msconfig help command to get a list of online help topics.
  • When you deal with editing blobs like channels, invoke the editor like this: msconfig edit channels, or for a specific channel, msconfig edit tcp_local. The msconfig edit command invokes the editor specified by the EDITOR shell variable. This is a much easier way to edit things than by trying to use an msconfig set command.

Thursday May 09, 2013

Oracle Communications Customers: What Kind of Documentation Do You Need?

Oracle Communications Customer Advisory Board (CAB) Provides Some Answers

In reading Scott Miller's Road Trip! InfoDev Goes to CAB post, I was struck by one of the answers he got to the age-old question from techwriterdom, "Just what exactly does a customer want in documentation?" Answer: More info on "operations."

In my mind, when customers talk about "operations," they mostly mean this in the context of the operations end of the business: having a document that contains common administrative tasks for their operators on the corporate help desk, who need to quickly triage and resolve "operations" issues that come up. Indeed, the idea of creating a Communications Suite "operations" guide has long been in the back of my mind.

So, let me put Scott's question out to Unified Communications Suite customers: "Just what exactly do you want in documentation?" If your answer concurs with what Scott found out at CAB, that you do want something more along the lines of "operations," perhaps we should start a dialog.


Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.


« July 2016