Friday Mar 16, 2007

Communications Suite 5 and Java ES: The Parting of the Ways

Just a heads-up about the forthcoming Communications Suite 5 release, in case you've missed it: Comms in no longer part of Java ES. So, all the Comms Suite 5 products--Messaging Server 6.3, Calendar Server 6.3, Instant Messaging 7.2--aren't part of the Java ES 5 bundle, and they won't be part of a Java ES bundle going forward. You'll download a separate Comms software bundle now, once we make it available. In addition, there will be separate Comms Install and Upgrade Guides. In the past, this information was included in the Java ES docs.

Here's the official statement that will appear in the docs:

Change in Availability of Communications Suite Products

Beginning with this release of Communications Suite 5, communications products are being removed from the Sun Java Enterprise System entitlement. Communications products are available as part of the Communications Suite or as individual products. Communications products will no longer be installed through the Java Enterprise System installer. Communications product components continue to interoperate with Java Enterprise System components.

This change in entitlement does not affect the communications products in Java Enterprise System 2005Q4. If you have communication products installed, no change will occur to your entitlement.

Thursday Mar 15, 2007

Communications Suite 5 Q&A: Access Manager, Delegated Admin, and Schema

There continues to be a fair amount of confusion (or miscommunication on our part) around Access Manager, Delegated Administrator, and schema choice. And the same confusion potentially could exist when it comes to deploying Comms Suite 5. So, here in a nutshell, are what I think are the basic questions and answers surrounding these products. I'll try and keep track of these issues going forward and continue to post them.

  1. In Communications Suite 5, does Delegated Administrator 6.4 still require you to deploy Access Manager?
    Yes, Delegated Administrator 6.4 still requires you to deploy Access Manager.
  2. In Communications Suite 5, does Communications Express 6.3 require you to deploy Access Manager?
    Starting with the Communications Suite 5 release, this dependency on Access Manager for Schema 2 has been removed.

    In previous releases, Communications Express used the following APIs and libraries to establish connections and fetch information from an LDAP store:

    • Domain MAP API (which a part of Communications Express) if Communications Express was deployed using Schema 1 mode.
    • Access Manager SDK if Communications Express was deployed using Schema 2

    This made Communications Express dependent on Access Manager in Schema 2 mode even though Access Manager is not mandatory for it to work apart from just connecting and fetching information from the LDAP store.

  3. When do I need to deploy Schema 2? Do I only need Schema 2 in an Access Manager/Delegated Administrator situation?
    Delegated Administrator currently supports only Schema 2. Other situations requiring Schema 2 include integration with Portal Server, and with Access Manager (for SSO).
For more information on these topics, see my previous entry.

Wednesday Mar 14, 2007

Communications Suite 5 Doc Leak: Installing on a Single Host

I know we're not shipping Communications Suite 5 until March 23, but you can go ahead and grab a copy of single host deployment example now:

http://docs.sun.com/app/docs/doc/820-0086

This deployment example describes how to install Sun Java Communications Suite 5 software on one computer for a functioning deployment. This document is intended for any evaluator, system administrator, or installation technician who wants to install and evaluate the services delivered by these components.

Now all you have to do is wait for the bits.

Update In the past, this example has documented how to install the Communications Channels (portlets) provided by our Portal Server product. That's a thing of the past. Looks like Portal is no longer providing these specific Comms Channels anymore, though the 'capability' to deploy these channels still exists. Heads-up to those of you who have used this out-of-the-box functionality in previous releases.

Friday Mar 09, 2007

Comms Suite 5: The Long Wait Is Over

Good news for those of you who have been waiting, ahem, a bit longer than you initially thought: Communications Suite 5 will be available March 23, 2007.

If you haven't seen my previous posts on what's new in this upcoming release, here they are:

Wednesday Feb 28, 2007

Communications Suite Users - Check out Jhawk's Blog

Heads up: Jonathon Hawkins, Sun Unified Communications Architect, has some great new posts up on his blog, including:

  • Directory Scalability at Telcoms
  • Communication Express: Authentications Between Components
  • Communications Express Deployments in 6.3

Friday Feb 16, 2007

Communications Suite - Suggestion Box

My email server was down from around 6pm last night until noon today (sendmail, not Messaging Server), and once back up, I decided to do some cleanup on my--ahem!--out of control inbox. (Afterall, a smaller inbox WILL help in times of system recovery.)

In the process of my cleanup, I came across an email thread that I thought I'd post, to see if the Comms Community cares to discuss. The topic: What information pertaining to Comms could we (Sun) provide more in-depth training/knowledge coverage on? Here are the responses. Granted, I'm only one tech writer on Comms, but the more feedback I can gather on issues such as this, the better off I can come to my SMEs and try and argue for what the customer needs. (Note: I believe this was initially a "training" request, but from where I sit, waiting for training courses to come out (no offense to our training coordinators and developers) takes too long to address the info/knowledge gaps.)

Messaging Server:

  • Practice with channel rewriting, including:
    • Special channel for outbound mail to a problematic host
    • Secure submission channels
  • How to use aliasdetourhost
General Comms Topics
  • Migrating events out of Microsoft Exchange and into Comms
  • Co-existence with Microsoft Exchange
  • Supporting large deployments of Connector for Outlook
  • Synchronizing with PDAs
  • Use of Non-Comms Express clients with Comms
  • Sizing Workshop
  • Sieve Topics
    • Vacation filters
    • System wide filters
    • Channel filters
    • Options/commands available in the Sieve scripts

Just for grins, I took a look at what some of us have been discussing about general Comms topics we "think" we should be working on in terms of Comms training/knowledge enhancement:

  • Deployment Architecture and Planning
  • Installation & Deployment Strategies
  • Planning Single Sign-On (Access Manager, Messaging SSO, Hybrid SSO)
  • Securing your Internet MTA
  • Customizing UWC
  • Migrations from Messaging Express to Comms Express
  • Deployments in Solaris 10 Zones
  • Automating Installations / Configurations for Production Deployments
  • Tuning UWC (incl. Solaris 10 DTrace and JVM Tuning)
  • Troubleshooting UWC (incl. Outlook, Calendar, Access Mgr, Directory & Messaging)
  • Transitioning Deployment Architectures to Comms Suite v5 (next release)

Now, for more data points. I did an internal survey of our field/engagement forces a few months back, with the same question, and got these responses:

  • Messaging Server Best Practices Guide
  • Configuring Communications Suite for SSL
  • Sizing a Communications Suite 25K User Deployment, including Communications Express
  • Initial Patch Levels for all Communications Suite Products (by release)
  • Gathering Debug Data for Messaging Server (data a customer needs to collect before calling Support)
  • Calendar Coexistence Using SyncML/Synchronica
  • Messaging Server Benchmark Data
  • Best Practices for Backup Up Lots of Data
  • Deployment Example: Comms Suite on T1000/T2000 and Solaris Zones
  • Deployment Example: Comms Suite in a Two-tiered Architecture

In an ideal world, we'd be working on all these topics, but unfortunately, we have to prioritize them and assign what resources we have accordingly. The good news is, some of these topics have already been addressed, or are in the process of getting addressed by documentation. Now that I have this list assembled and am looking at it in its entirety, I see that another post is in order to recap where we're at, and where we hope to go. Stay tuned for details.

And as always, drop a line if you have any suggestions on what docs/information you'd like to see us work on.

Thursday Feb 01, 2007

Communications Suite Products and DST: Daylight Saving Time Changes (2007)

I'm sure most of you are following this:

The Energy Policy Act of 2005 mandates that US DST will start on the second Sunday in March and end on the first Sunday in November. In 2007, the start and stop dates will be March 11 and November 4, respectively. These dates are different from previous DST start and stop dates. In 2006, the dates were the first Sunday in April (April 2, 2006) and the last Sunday in October (October 29, 2006).

In case you want to know how this affects the Communications Suite products, here's the link:

http://www.sun.com/bigadmin/hubs/dst/software/#Messaging_Server_Calendar_Server

Communications Suite Documentation: Coming Attractions

Never a dull moment here in Comms Suite docs. That is, there is never any downtime, I'm always getting new requests for information deliverables. So, here's a quick update on what's in the pipeline:

  • Tech Note: Using Sun StorageTek 53xx NAS with Messaging Server Message Store
    This technical note describes how to configure the Sun StorageTek 53xx NAS for use with Sun Java System Messaging Server. (Basically, you now have two options for NAS: NetApp and Sun StorageTek.)
  • Tech Note: Using ZFS with Messaging Server Message Store
    I'm told this is a hot item right now, so we're going to try and get this out ASAP.
  • Case Study: Migrating From Critical Path to Sun Java Communications Suite
    This case study describes a real-world migration from the Critical Path email system to Sun Java Communications Suite, which includes Sun Java System Messaging Server and Sun Java System Directory Server. This case study highlights the use of the Sun Groupware Migration Toolkit and Sun Groupware Migration Methodology in migrating 1.5 million Critical Path mailboxes to the Sun platform in a project that took just four months to complete.
  • BigAdmin Tech Tip: Receiving a Daily Summary of Sun Java System Calendar Server Events and Tasks by Email
    This tech tip describes how to provide your Sun Java System Calendar Server users with a daily summary of their Sun Java System Calendar Server events and tasks, emailed to their inbox or mobile device each weekday morning. You do this by creating a Bourne shell script, daily_summary.sh, which uses Web Calendar Access Protocol (WCAP) commands. On a daily basis, this script finds all events and tasks from your users' calendars then emails them to the individual users. (Note: This is ready to be published, we're just fine tuning the script.)
  • Technical Note: Troubleshooting Sun Java System Messaging Server Message Queues
    This technical note describes how to troubleshoot the Sun Java System Messaging Server MTA, specifically message build-up in channels, including the TCP channels (tcp_local and tcp_intranet) and ims-ms channel. (I'm waiting for my SME to sign off on this one.)

As usual, I hope the Comms Suite community finds this kind of information useful and pertinent, and if you have any suggestions or doc needs, please feel free to leave a comment or drop me a line.

Tuesday Jan 30, 2007

Wanted: A Few Good Communications Suite Examples

We in documentation hear what customers want: more examples. Communications Suite examples, especially for deployment, are unfortunately far and few between. Good news is that I'm updating the single-host deployment example for the upcoming Communications Suite 5 release.

And more good news: the document itself is shrinking by a number of pages. Does this mean that the Comms Suite stack (along with the Java ES components it requires) is getting easier to install? Well, maybe. Some changes in the Communications Suite 5 release that are reflected in this doc include:

  • Portal Server is no longer installed. (That alone probably accounts for the page reduction I mentioned above.)
  • Solaris Operating System (OS) 10 is used.
  • Hosted domains are now configured.
  • Proxy auth is now the way that Single Sign-On is accomplished. As a result, Access Manager is no longer required for Communications Express and there are fewer configuration settings that you have to enter. (Sigh of relief there.)

I should have this document ready at release time, unlike in the past, where we had some lag time between getting the release bits installed to be able to test the doc and get it out.

BTW, if you are looking for current Communications Suite (aka Communications Services) examples, check them out here:

Monday Jan 22, 2007

Documentation Funhouse - Finding Communications Suite Docs on d.s.c.

Okay, over the weekend the docs.sun.com site underwent some changes. If you're having problems finding the Communications Suite (Messaging Server, Calendar Server, Instant Messaging) doc collections, you are not alone. They have been relocated. Here are your choices to get the docs in this new taxonomy:

  1. Use the Communications Suite Hub Library tab. The way I've set up the doc links is to use the underlying IDs that should not change, regardless of what structure gets set up on d.s.c.
  2. Navigate the new d.s.c. tree as follows:

    - Click the Sun Java Enterprise System link on the docs.sun.com front page.

    - Click the Collaboration and Communication link.

    - Click the appropriate product collection.

  3. Use the following new links to go directly to the appropriate product collections:

    - Messaging Server: http://docs.sun.com/app/docs/prod/mess.svr#hic

    - Calendar Server: http://docs.sun.com/app/docs/prod/cal.svr#hic

    - Instant Messaging: http://docs.sun.com/app/docs/prod/im#hic

Communications Suite - Overlooking the Obvious?

I get lots of email concerning all kinds of aspects of our Communications Suite products. As a writer, part of my job is to sift and dig through this constant heaping of information, and ultimately help determine what to do with it.

Here's a quick grab bag of facts that seemed perhaps obvious and then again, perhaps not. If we had a Frequently Asked Questions document, this is where I would locate such information. (Note: I am investigating a means to do this on a Sun external site, such that the FAQ would be editable by anyone. Stay tuned for details.)

PDA Access to Communications Express?

You need Sun Java System Communications Sync, which syncs PalmOS and Windows Mobile 5.0 PDAs to Sun calendar and contacts.

Communications Express Without Access Manager?

It's a current requirement, when running Communications Express 6 2005Q4 to have to use Schema 2 and Access Manager. The Access Manager requirement is evidentally removed in the upcoming release (Communications Suite 5, Communications Express 6.3). The Communications Express 6.3 Administration Guide will have the details.

Will a New Messaging Server 6.x MTA Function with a 5.2 Message Store?

It depends on your setup. You cannot mix Messaging Store 5.2 store executables with 6.x MTA executables. However, you may deploy a 6.x MTA running on one host delivering mail to a 5.2 Message Store running on another host. In such a deployment, you'll also need a 5.2 MTA on the store machine because LMTP isn't supported in Messaging Server 5.2, but such a setup will function.

ACLs Missing from Messaging Server 5.2 imsbackup?

The imsbackup utility in Messaging Server 5.2 does not back up the ACLs. This is a known issue. Unfortunately, this could impact maibox migrations. As a workaround, you can get the ACL list from the old store with the following command:

mboxutil -l -p pattern -x

then set it with readership -s after the migration.

Adding New Spelling Dictionaries to Communications Express?

The dictionaries in Communications Express are from ispell, which can be downloaded here:

http://fmg-www.cs.ucla.edu/fmg-members/geoff/ispell-dictionaries.html

See the Communications Express Customization Guide for details on installing the new dictionaries.

Calendar Server: Linux or x86 Front-end with a Solaris SPARC Back-end?

Beginning with Calendar Server 6.3, mixing different architectures for front-end and back-end machines is now supported. The hardware platforms no longer must be the same on each end. The big-endian vs.small-endian incompatibility no longer applies and you can now use both an x86 platform machine and a SPARC platform machine in the same Calendar Server deployment containing front-end and back-end machines. You can also mix Linux and Solaris x86 systems for front-end and back-end machines.

2007 Predictions in the Mobility Market

Interesting predictions for 2007 on mobile email and backup/restore from Synchronica CEO Carsten Brinkschulte:

http://synchronica.cmail1.com/.aspx/e/136380/83252935/

Tuesday Jan 16, 2007

Slicing and Dicing Communications Suite 5 - The Rest of the Story

Continuing this thread on what's new in the upcoming Sun Java Communications Suite 5 release, here's the rest of the story on Instant Messaging, Delegated Administrator, Communications Express, and Connector for Outlook.

What's New in This Release of Instant Messaging

This section includes the following topics:

  • Instant Messaging XMPP Redirect Server

  • Sun Java Enterprise System Monitoring Framework Support in Instant Messaging

  • Instant Messaging Redeploy Script Changes

Instant Messaging XMPP Redirect Server

The XMPP redirect server balances the load between servers in a server pool, increasing performance by decreasing the amount of communication required between servers in a single deployment. The XMPP redirect server increases the probability that two users who will likely share presence information and messages end up on the same node. You use a redirect service to optimize resource utilization. The redirect service directs client connections to specific hosts in the server pool.

Sun Java Enterprise System Monitoring Framework Support in Instant Messaging

This release of Instant Messaging supports version 2.0 of the monitoring framework. This monitoring framework provides information on the length of time for authentication, message delivery, the number of instant messages sent through the service, and other statistics.

Instant Messaging Redeploy Script Changes

The redeploy script used to redeploy Instant Messenger resource files has been renamed to iwadmin.

Event Notification Service (ENS) Support in Instant Messaging

In this release there are two notification services for Calendar pop-ups: Sun Java System Message Queue (JMQ) and Event Notification Service (ENS). In a future release, the Communications Services products (Instant Messaging, Calendar Server, and Messaging Server) will use JMQ exclusively and ENS will be removed. However, for this release, you can continue to use ENS.

Legacy SSL and TLS Support for Instant Messaging

TLS support was added to Instant Messaging in the previous release; however, the Sun Java System Instant Messaging 7 2006Q1 Administration Guide did not adequately cover instructions for setting up TLS. TLS is used for communication between the server and clients, other servers, and Instant Messaging components such as the XMPP/HTTP Gateway. Legacy SSL is still supported for communication between clients and the multiplexor. Legacy SSL is no longer supported by the server. The Sun Java System Instant Messaging 7.2 Administration Guide now provides detailed information about setting up security for your deployment.

As a result of the implementation of TLS in Instant Messaging, you are no longer prompted to enter an SSL port for the server when you run configure.

The following iim.conf parameters are no longer used:

  • iim_server.sslport - No separate port is required for TLS connections.

  • iim_server.usesslport - No separate SSL port.

  • iim_server.secconfigdir - No longer have NSS key and certificate database for the server.

  • iim_server.keydbprefix - No longer have NSS key and certificate database for the server.

  • iim_server.certdbprefix - No longer have NSS key and certificate database for the server.

  • iim_server.coserver1.usessl - This has been replaced with iim_server.coserver1.requiressl.

The following iim.conf parameters are new for this release:

  • iim_server.requiressl

  • iim_server.sslkeystore

  • iim_server.coserver1.requiressl

Refer to the Sun Java System Instant Messaging 7.2 Administration Guide for information about using these parameters.

The Instant Messenger client uses imssl.html and imssl.jnlp only for legacy SSL connections. Instant Messenger supports TLS automatically when it connects to a server that is configured to use TLS.

What's New in This Release of Delegated Administrator

Delegated Administrator 6.4 includes the following changes and new features:

  • Support for Calendar Groups

  • Web Server 7.x Deployment

  • Access to Instant Messaging

  • Debug Log Command for the Delegated Administrator Server

Support for Calendar Groups

Delegated Administrator supports provisioning of calendar groups.

You can use Delegated Administrator to assign calendar service to a group. When the group is first invited to an event, Calendar Server creates a group calendar shared by the users who are members of the group. Invitations to the group appear on the group calendar and on the calendars of the individual members.

The following features implement support for calendar groups:

  • In the console, you can assign service packages with calendar service to groups. In the Create Group wizard, a Calendar Service Details panel allows you to specify Calendar attributes for the group. Calendar service details can be modified in the group properties page.

  • In the command-line utility, the commadmin group create and commadmin group modify commands have been enhanced to support calendar groups.

Web Server 7.x Deployment

Delegated Administrator can be deployed to Sun Java System Web Server 7.x.

When you run the configuration program, config-commda, you can configure the Delegated Administrator server and console to be deployed to Web Server 7.x.

Access to Instant Messaging

Users created in Delegated Administrator will have access to Instant Messaging (IM) service if IM is deployed on your site. Users are automatically assigned basic IM service during user creation.

You must use the Access Manager console to set and manage IM user-access levels. In this release of Delegated Administrator, the Delegated Administrator console does not provide access to IM service and does not provide an interface for managing IM user-access levels.

Debug Log Command for the Delegated Administrator Server

In the command-line utility, the commadmin debug log command creates a Delegated Administrator server log that contains debug statements generated by the Delegated Administrator servlets installed on the Web container.

With the commadmin debug logcommand, you must create the log in the /tmp/ or /var/tmp/ directory.

The commadmin debug log command supersedes the use of the url to enable logging for the Delegated Administrator server. The url used in previous releases can no longer be used for this purpose.

What's New in This Release of Communications Express

New features in Sun Java System Communications Express 6.3 include:

Support for Attachments in Events/Tasks

The Calendar component of Communications Express allows users to include attachments to an event or task.

Next Available Free Period Button

Communications Express allows users to check availability of invitees. If the invitee is not available for the day of the event, the next available free period button displays the availability of the invitee in the subsequent six days.

Address Book Sharing

The Address book component of Communications Express allows users to share their address book globally as well as to specific users. You can also assign specific permissions to users who subscribe to your address book. You can also subscribe to other shared address books.

Support for Multiple Address Book

Communications Express allows users to create and maintain more than one address books.

Preserving Customization

Starting this release, the Communications Express upgrade script will preserve all customizations that have been made in the product. This was not possible in earlier releases and all customizations were lost on a patch upgrade.

Password Encryption

Starting this release Communications Express configurator tool enctyps passwords during configuration. This is done transparently by the configuration tool. Communications Express now has a tool to encrypt and manage passwords. Administrators can change passwords by running this script.

LDAP Failover Mechanism

The LDAP failover mechanism in Communications Express balances load between a number of configured master and slave LDAP servers. This increasing performance by decreases the response time. Communications Express contains an LDAP failover Manager module that is responsible to retrieve connections from the master or slave servers. Each load balancing server maintains a pool of available free connections. Whenever a Communications Express component requires a connection to the LDAP server, the LDAP failover manager provides the component with a connection based on the load balancing strategy employed.

Mail Integration into Communications Express

Starting this release, the Webmail related user interface components have been moved to Communications Express. In the earlier releases of Communications Express, the mail related files were resident in the Messaging Server. Also, in previous releases of Communications Express, the webmail and the web container ports had to be available for it to work. As a result of this change, only the web container port needs to be available for Communications Express to work.

Removal of Access Manager SDK Dependency for Schema 2 Deployment

In previous releases, Communications Express used the following APIs and libraries to establish connections and fetch information from an LDAP store:

  • Domain MAP API (which a part of Communications Express) if Communications Express was deployed using Schema 1 mode.

  • Access Manager SDK if Communications Express was deployed using Schema 2

This made Communications Express dependent on Access Manager in Schema 2 mode even though Access Manager is not mandatory for it to work apart from just connecting and fetching information from the LDAP store. Starting this release, this dependency on Access Manager for Schema 2 has been removed. Communications Express is now shipped with a new Domain MAP API for Schema 2.


Note - As a result of this, users who log in to Communications Express cannot log on to Access Manager Console.


What's New in This Release of Connector for Microsoft Outlook

New features in Sun Java System Connector for Microsoft Outlook 7.2 include:

  • Polling multiple folders.

    A new option in the Deployment Configuration Program allows multiple mail folders, including Inbox to be checked for new unread messages. This option can be useful if message filters have been set up to automatically move incoming messages to specific folders other than Inbox, or if the direct delivery to a specific folder option has been enabled.

  • Creating and sharing multiple calendars and tasks.

  • Creating and sharing multiple address books.

  • Adding attachments to calendar events. Attachments are saved on server.

  • Viewing group memberships within contact details (applies only to the corporate directory).

Wednesday Jan 10, 2007

Communications Suite BigAdmin Hub Shamless Plug

In marketing, it's about capturing eye-balls, getting traffic to your site, and so on. So, with that in mind, how's about a little shameless plug for the Communications Suite Hub, your one-stop shop for everything you need to know about Sun Java Communications Suite.

If you read this blog, you already know that we launched the Communications Suite Hub in Oct '06, so this is not news. However, you might not be checking back regularly for new content, so here's a quick recap of some of the new items:

  • On the Tech Articles tab:
    • Sun BluePrints Article: Migrating Sun Java System Messenger Express Personal Address Book Using the pab2abs.pl Utility
    • Technical Article: Configuring Sun Java System Messaging Server 6.3 and Solaris Cryptographic Framework on Systems With UltraSPARC T1 Processors
    • Technical Article: Email-Forwarding Behavior in Sun Java System Messaging Server 6 2005Q4
  • On the Community tab, recent threads from the Support Forums.
  • On the Support tab, information about the new Sun Gathering Debug Data program to help you to more quickly resolve problems when opening tickets with the Sun Support Center.

The Communications Suite Hub is also a chance for our customers and partners to submit content as well. If you're interested, you can either drop me a direct line at joseph.sciallo@sun.com, or go through the BigAdmin Submit form.

Tuesday Dec 12, 2006

Communications Suite: Sun GDD to the Rescue

Here's a very cool project that I somehow got involved with (set to launch very shortly): Sun Gathering Debug Data. What is it? Perhaps it's best to say what GDD is not first: it is not a methodology, nor a tool, nor a process, nor a product. Rather, GDD is a way to better equip and educate customers who need to contact the Sun Support Center on what debug data they need to provide the first time they call. Analysis of call data for the Sun Support Center showed that all too often, call resolution was slowed by having to re-contact the customer for more data, sometimes multiple times. This translated to less customer satisfaction. The solution is to ask for all the pertinent debug data at the time of the first customer contact. Until now, such a complete list of what data to ask for, and how to collect it, didn't not exist in one convenient place.

Fortunately a team within Sun has taken the time to assemble the various commands, scripts, and processes to provide customers with what they need to cut down problem time to resolution. Customers will be able to download technical documents and scripts, by product, which will walk them through gathering all pertinent debug data related to the type of problem they are experiencing. The first release of GDD supports Messaging Server and Calendar Server, as well as many of the Java ES components, on all of the released operating systems.

You'll access GDD through a new web page that will show up soon (I'll post the link when it is live), as well as from the Comms Hub, and you'll get access to documentation and scripts by product.

For example, for Messaging Server, we've broken the problem areas down as follows:

  • What data to get for all problems
  • Installation problems
  • Hung or unresponsive process
  • Crashed process
  • Routing problem
  • MTA Queue problem
  • Webmail problem
I believe GDD will be a valuable tool for our customers and go a long way towards enhancing their satisfaction when dealing with Sun Support.

UPDATE: Here's the link to the Messaging Server GDD doc:

http://docs.sun.com/app/docs/doc/819-5355

UPDATE II: Here's the link to the Sun GDD site:

http://www.sun.com/service/gdd/index.xml

About

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

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today