Server Configuration for HTTP Delivery
Universal Messaging can serve web content over both HTTP and HTTPS communication modes. This section discusses the steps necessary to configure a realm server to deliver web content over HTTP.
Creating a Universal Messaging HTTP (nhp) Interface
Note:
Universal Messaging ships with an HTTP Interface enabled by default.
Universal Messaging provides its own protocol, the Universal Messaging HTTP Protocol (nhp) for the delivery of web content over HTTP. For web communication to take place an interface using this protocol must be created. Creating an interface can be done through the enterprise manager.
Serving Content through File Plugins
A Universal Messaging nhps interface delivers content to connected browsers through file plugins. Generally at least two file plugins will need to be configured to serve a page using the Universal Messaging JavaScript API. The first will be a pointer to the Universal Messaging JavaScript client libraries. The second will be a plugin pointing to the base directory of the web pages which use these libraries.
The Universal Messaging JavaScript client libraries are located in <InstallDir>/UniversalMessaging/javascript/lib. To use these libraries in any content served from an interface a file plugin with a BasePath which points to this directory is necessary. The URL Path of the file plugin may be anything you wish, though it must be referenced the same in the include in your JavaScript code. For example, if you set the URL Path to /lib/js then the following code must be included in your pages:
<script language="JavaScript" src="/lib/js/nirvana.js"></script>
Note:
Universal Messaging ships with a file plugin with the base path /lib/js and the above configuration.
The file plugin which points to your web content is configured in a similar way. The BasePath should point to the fully qualified path of your web directory. The URL Path is the resource location relative to your address. For example, serving content from the root of the website can be done by setting a URL Path of /.
If you prefer, you can host your web application on a different web server entirely. In addition, nirvana.js could be served from such a web server. The Universal Messaging realm server's interface's file plugin (/lib/js in this case) will only be required if you opt to use any of the JavaScript drivers that use postMessage for cross domain communication (see JavaScript driver details for more information).
JavaScript Interface Properties
The behaviour of nhp interfaces when serving web content can be changed through the enterprise manager. These settings can be changed by editing configuration properties available in the JavaScript panel accessed through the interface tab.
Comet Configuration Properties
The Universal Messaging enterprise manager also provides realm wide configuration settings for Comet. These are available in the enterprise manager from the Comet Config panel.