Tuesday Feb 12, 2008

Synchronica Mobile Gateway 3.5 works with Sun Comms Suite 5


Synchronica Mobile Gateway 3.5 with New Features for Consumer and Business Market

Additional Back-end, Provisioning, and Billing Support Reduces Time to Market for Business and Consumer Mobile Email and Synchronization Services

GSMA Mobile World Congress, Barcelona, Hall 2.0, Stand 2J25, February 12, 2008. - Synchronica plc, international vendor of mobile email and synchronization software, has announced Mobile Gateway 3.5 with new back-end support for Microsoft Exchange 2007 and Sun Java Communications Suite 5.

Mobile Gateway 3.5 also introduces support for the Java Content Repository (JCR) standard, allowing it to be integrated easily with third-party personal information management (PIM) systems, significantly reducing the development time. The new product incorporates a billing API (Application Programming Interface) to facilitate both prepaid billing, predominantly used in the consumer sector, and post-paid billing favored by corporate accounts.

Mobile Gateway 3.5 further features a new mobile registration interface that allows consumers to sign up easily and quickly from their phone by using WAP, activating the service directly from the device without requiring access to a PC.

In the business sector, Frost & Sullivan predicts that mobile email will become a must-have application, with revenues estimated to grow from EUR 1.86 billion in 2007 to EUR 6.65 billion in 2012.

By adding support for Microsoft Exchange 2007 and Sun Communications Suite 5, Mobile Gateway 3.5 enables operators to provide a carrier-grade mobile email and PIM synchronization service to the majority of users working in businesses, without forcing them to use a specific device. This makes the use of a single device for both business and private email a reality, removing the headache of carrying multiple devices for executives on the move.

"The enormous popularity of the Apple iPhone has demonstrated that consumer and business use of mobile phones is converging, and operators are starting to look at how best to serve both markets on a single device", says Synchronica CEO Carsten Brinkschulte.

At the same time that mobile email becomes a must-have application in the business sector, Visiongain predicts that consumer mobile email accounts will increase to 184 million users by 2011. Because Mobile Gateway 3.5 supports popular consumer email services such as Gmail, AOL, Yahoo, or any POP3 or IMAP mailbox, it is equally attractive to operators introducing consumer mobile email services.

Using the open standards Push IMAP and SyncML, Mobile Gateway 3.5 integrates with the native email and synchronization clients built into more than 1.5 billion devices from all major handset manufacturers like Sony Ericsson, Palm, Nokia, Samsung, Motorola.

This is ideal for business users who need secure mobile access to corporate email and calendar information, as well as users in the prosumer and consumer markets, as it supports both smartphones and mass market feature phones without requiring an additional client to be installed on the device.

As a key advantage, unmatched by other products, Mobile Gateway does not require any additional software installation on the users' PC or firewall modification in the corporate network. Instead, Mobile Gateway is operated in the data center of the service provider and connects to the user's mail server through a secure connection.

The combination of this zero footprint architecture with an additional over-the-air provisioning module eases service activation and improves adoption rates.

"By extending our back-end support to include Microsoft Exchange 2007 and Sun Communications Suite 5 and continuing to support open standards and popular consumer email services, Synchronica can provide a single solution that can deliver carrier-grade mobile push email and PIM synchronization to both consumer and business users on a wide range of devices", says Synchronica CEO Carsten Brinkschulte.

"We are delighted to announce these important enhancements to our flagship product Mobile Gateway. This is another important step in our mission to bring carrier-grade push email, PIM synchronization, and backup and restore services to every phone on the planet, whether it is in the hands of a European executive on his Sony Ericsson P990, a U.S. prosumer on his Apple iPhone, or a consumer in Bangladesh accessing emails on his Nokia 1101", adds Brinkschulte.


Technorati Tags: , ,

Monday Feb 11, 2008

Come Meet Us at the Communications User Group!

Come Join Us for Talks on our Future Products.. Presentations by Current Customers. Face to Face Meetings with us.. and just to Party!

We would like to invite customers of the Sun Java Communications Suite are invited to attend.

Communications User Group Meeting
When: March 20
Where: Sun Office in Itasca, IL.

To Register or For More Information, Please see the following Link


Technorati Tags: , , , , ,

Thursday Feb 07, 2008

CNET #1 Download: OpenOffice

Congrads to the Hamburg Team working on OpenOffice/StarOffice!


Technorati Tags:

Friday Dec 21, 2007

The 15 Biggest Tech Disappointments of 2007

Yahoo News: The 15 Biggest Tech Disappointments of 2007

#1 Windows Vista
#2 High-Def Format War
#3 Facebook
#4 Yahoo
#5 Apple iPhone's Pricing Snafu

Thursday Dec 13, 2007

Next Gen Web Client Feedback

Some of the comments on my earlier post on "Start Thinking about Sun's New Web Communication Client!"

Q: Why does Sun still require mshttpd? Why do we need an additional layer?

The mshttpd server provides an established interface for our Web Mail Access Protocol (WMAP). The mshttpd process has been in place for nearly 8 years going back to Netscape Messaging Server 4.15sp7. We felt it eliminated a lot of risk by leveraging the existing HTTP services. This process is also required for legacy support of our Sun Java Systems Communication Express (UWC) client.

Q: Why does mshttpd only talk IMAP to a Sun Message Store? Will mshttpd support 3rd Party IMAP Servers in the future?


The mshttpd server uses a number of Sun's private extensions to IMAP. Namely.. Proxy Authentication. These extensions are not part of the open standards of IMAP. It is on the roadmap to support 3rd Party Servers in our new Web client.

Q: Why won't we support the Opera Browser?


The Opera Browser was considered. It is supported by the Ajax toolkit used in the Web Client, however we are narrowing our focus to ensure we have a solid release on more established browsers such as Microsoft Internet Explorer and Mozilla's Firefox.

Monday Dec 10, 2007

Start Thinking about Sun's New Web Communication Client!

As some of you have read on Jim Parkinson's Weblog.. As the Vice-President of Communications Software says.. we are definately going for a "Wow Factor." The exciting new AJAX-based client (code named Kendo) will be available in the first half of CY2008. While you are waiting for this product to arrive, we would like to outline some of the requirements that would be needed to allow you to deploy this new client.

Ng-Architecture-1(click to enlarge image)

The above image demonstrates the three components to the new Kendo client: the web browser, the web container, and the communications services.

Web Browser

The new web client utilizes Ajax to provide a "rich" user experience. The objective is to avoid potential complications brought in by plugins such as Flash. This means we are trying to focus on using the capabilities common within the most popular types of web browsers: Microsoft Internet Explorer, Mozilla FireFox, and Apple Safari.

Web Container

The new client is built on some of the latest in Web 2.0 technologies. These technologies require a Web Container which has Glassfish and Grizzly capabilities. The supported web container for the Kendo client will be Sun Java System Application Server 9.1. The changes would remove the Sun Java Web Server as a supported Web container.

Messaging Server

The Kendo client will require the mshttpd which is included in the Sun Java System Messaging Server 7.0. In most cases, the mshttpd will run on the same server as the Kendo Web Container. The mshttpd will evaluate WebMail requests against LDAP entries to proxy IMAP connections to the back-end Message Store servers.

The back-end Message Store servers will be required to be the equivalent to Messaging Server 6.3. Earlier 6.x versions must be at patch level 120228-25 or higher (see patch readme). Messaging Servers running on prior releases must upgrade to use the Kendo client.

Directory / Schema

Kendo will support Sun Java Systems Directory Server Enterprise Edition 6.x. The new Kendo client adds some additional attributes to the existing schema. Kendo will support both the old schema (schema 1) and the current schema (schema 2).

Technorati Tags: , , , , , ,

Thursday Nov 29, 2007

Joy to the World: a Web server, a web cam and House Christmas Lights

Control the Christmas lights of some guy's house.. through the Internet!! The guy somewhere in Europe.. I guess it is Europe given by the 9 hours difference and the different electrical plugs... http://www.lightscontrol.com

Technorati Tags: ,

Wednesday Nov 28, 2007

Unified Messaging and Sun Java System Messaging Server

In general.. Sun offers an open platform for Unified Messaging services. The trend in the industry is to use open interfaces into "internet-based" email messaging platforms. As we at Sun are not actually providing voice features, we can however allow companies who have expertise leverage the successes Sun has had in providing massive scalability and manageability. We believe the the customer chooses the messaging platform, and then they choose a Unified Messaging platform to layer on top of it.


Some voice vendors still favor a "locked in" strategy which tie the customer to a proprietary storage mechanism. Today's realities make this less desirable because of the rapid development of voice features based on Web 2.0 cause these vendors to move less rapidly due to the overhead of development on these aging proprietary stores.

Sun enables features on these Voice platforms that come directly from our experience in email. Notification is a clear example of this. Many vendor solutions consist of one of three approaches to sending a notification of a new message:

\* "scan" all the mailboxes for new voicemail (IMAP polls)

\* forward a copy of the message to a notification server

\* maintain two mailboxes for each user

The worse method is the "scan". In this mechanism, a notification server will scan every mailbox of every user to identify new voice messages. The tragic consequences of this method is "timely notifications" versus "loss of performance" of your email platform.

The "copy on delivery" mechanism has a value in that it is supported on nearly every major email platform. The issue with this mechanism is that the forwarded message does not necessarily indicate the true state of the mailbox. A user who is logged into IMAP will still get a new message notification. The technical complexity of clearing a notification also makes this an unreliable mechanism.

The "notification mailbox" mechanism may have some merits. A voice mail message arrives in both the regular email inbox and the voice mail inbox. The two downsides of this approach are that first the email administrator needs to maintain two mailboxes and second that IMAP access does not take into account a message notification reset.

The example below indicates how Sun Java Messaging Server provides a "Universal Notification Service" for Mailbox changes. The notification mechanism is closely tied to the actual Message Store itself. This gives the benefit of matching the notification to the actual state of the mailbox. The new message notification is cleared no matter how the voice mail is actually retrieved; either by IMAP or by Phone.


Read more about how to configure Java Message Queue notifications in the

"Configuring a JMQ Notification Service" in the Sun Java System Messaging Server 6.3 Administration Guide

{, }
[composed and posted with ecto]

Technorati Tags: , , ,

Monday Nov 26, 2007

Test Post

testing new Blogging client (Ecto) Tranquilize (Feat. Lou Reed) from the album "Sawdust" by The Killers

Setting up NetBeans 5.5 for Dojo AJAX Development

Inserting the Dojo Toolkit into NetBeans 5.5

1. Download the latest version of Dojo Toolkit

At the time I'm writing this, the toolkit is currently on version 1.0.1

2. Unpack the Packaging.
This will create a directory called “dojo-release-1.0.1”. Save this directory in a location which you will
use it later.
Picture 2.png

In my case, I'm copying this directory into my Development folder.

3. Start up NetBeans 5.5

Picture 3.png

4. Create a new Project.

File->New Project->Web->Web Application

Picture 4.png

and press the Next button.

5. Define the New Project.

Project Name: HelloDojo

You can leave the rest unless you need to save the project in another location.

Picture 5.png

Click the Finish Button.

6. Examining the Web Project's Directory Structure

NetBeans should display the following..

Picture 6.png

The Directory Structure Represents the two important directories: (we will ignore the rest for now)

a. Web Pages - The HTML, JSP, CSS and Image files. Also this contains XML files used by the Server.
b. Source Packages - Server-side Java Implementations (Servlets and Enterprise Beans)

7. Copy Dojo Toolkit into the Web Pages Directory

Picture 7.png

NetBeans will reflect this change. (highlighted below)

Picture 8.png

Congrads.. You are now ready to start your Dojo Development!

Writing your first Dojo Application

1. Setting up Dojo in your Page

This example has been taken directly from the “The Book of Dojo” section entitled Hello World - Dojo for the Attention-Impaired. Full credit should be given to “lance” who is the author. I'm adding to this example the NetBeans work we did in the previous section.

The first thing we will do is:

a. Load a Cascading Style-Sheet (CSS). We will be using “Tundra” from the Dijit theme library.
b. Insert a script element into the head element. This loads the Dojo JavaScript to enable Dojo.
c. Place the “tundra” CSS class into the body tag
d. I changed the default “JSP Page” title to “HelloDojo Page”

Picture 10.png

2. Load the Required Widget/Modules

In this step, we will load the Button widget. (see “SECTION 2”)

Picture 11.png

3. Add the Widget to the HTML

Inside the BODY tag, place a new instance of the Button widget on the page.

Picture 12.png

At this time, you can actually try something out. Press the “Run Main Project” button to construct a WAR file to be installed on TomCat.

Picture 13.png

We now have a button. It doesn't do anything, but we have a button!

4. Add an Event to the Button

We are adding a specialized script tag in the above button to handle a mouse click event.

Picture 14.png

This mouse click will cause an Alert to Popup. If you run it, and click on the button, you should see the following..

Picture 15.png

This is it.. you have a very basic AJAX application working on NetBeans 5.5. Next week, I will show out the Server-side Java will provide more useful information than just a PopUp.

Final Thoughts..

I hope you found this information useful. I will be continuing this series further to include our new AJAX-based Web Client (code named Kendo). Please stay tuned..

Technorati Tags: , ,

Sunday Oct 28, 2007

Where's the Solaris version of Lightning 0.7??

I received a few comments about when the Solaris version of the plugin will be available. I'm not officially on the team, I'm on the Server-side of Calendar Server engineering. I can however say that I'm hearing on the Sun internal development aliases that the Solaris version of the Plugin is planned for next week.

The plugin for Mozilla Thunderbird 2.x will allow access (via WCAP) to calendars and "to do" lists on our Sun Java Calendar Server.

Technorati Tags: , , , , ,

Thursday Oct 25, 2007

Thunderbird Plugin for Sun Calendar Server releases version 0.7

Lightning 0.7 has now officially been released. If you want the Sun Calendar Server (WCAP) version use the link below.

Link to the Plugins

Calendar Weblog listing the improvements

Technorati Tags: , , ,

Tuesday Oct 23, 2007

Skype's Major Outage Blamed on Microsoft

Skype's service outage should serve as a warning to any company offering services to its customers. The message is clear.. Microsoft Windows Vista isn't ready for 7x24.

The massive outage on August 16 and August 18 caused denied Skype's subscribers access to their accounts and ability to make phone calls. The company is reporting that the cause was due to the standard monthly Windows updates causing Skype's production PCs to reboot unexpectedly.

A report by Ferris Free News Service believes that this outage was due to the standard monthly Windows updates causing PCs running Skype to reboot. These updates were unique because "they FORCED a reboot of unattended PCs" without notice to administrators. All this happened within normal working hours when usage of the popular Skype service was at its peak.

This reboot eventually caused a spiraling failure when after the reboots. The reconnects after the reboots forced failures of their authentication servers that and problems with their network routing algorithms created the "perfect storm."

Further Readings

ComputerWorld's Richi Jennings on the Outage

Technorati Tags: , , , ,

Monday Oct 15, 2007

Comms Suite's Priorities Outlined..

In case you haven't noticed it, Jim Parkinson (our Executive VP for Communication Products) has posted the future priorities for our Communication Suite Products.

 JP's Blog Entry:  Communicate Products the New Client is coming along!!

Sunday Oct 07, 2007

Ramping up for CEC in Las Vegas

I'm about to board an airplane to head to Las Vegas for our CEC Conference for Sun Field Folks and Partners. If you are in the area, feel free to stop by one of our two Communications Software booths. I will also be giving a presentation on our next Web Client at the following location.

Session ID: SFT9934
Session Title: Sun Java Communications Suite : New Web 2.0 Client
Track: Software
Room: Skyview East 2
Date: 2007-10-09
Start Time: 16:45

Technorati Tags:


I'll be writing about topics that would interest users and developers of Sun Java Communication Suite.


« December 2016