oracle.panama.messaging.transport
Class TransportLocator

java.lang.Object
  |
  +--oracle.panama.messaging.transport.TransportLocator

public final class TransportLocator

extends java.lang.Object

 The class is the entry point of the transport API. 
 
 This class is a singlton implementation and it offers
 bootstrapping to acquire access to either 
 the messaging interface or the driver interface, depending
 on particular needs of the application.

 OracleAS Wireless Transport system is offered by the corresponding runtime 
 component for message delivering and receiving. This component supports 
 open transport and is by itself independent of the actual wireless protocols.  
 The component employs various techniques to boost performance, fault 
 tolerance and scalability of message delivering.  
 The transport component aims to enhance the functionality and performance of 
 previous versions of OracleAS Wireless.  Two main interfaces are exposed through this set of 
 APIs.  On the top of this layer the messaging APIs are available to develop 
 applications to send and receive messages.  On the bottom of the layer driver 
 APIs are available for transport specific drivers to be plugged into the 
 OracleAS Wireless system. 

 General Transport Architecture

 The messaging APIs are independent of the underlying network protocols.  
 The key operations the APIs offered are to send and receive messages to 
 device recipients.  An abstraction of device recipients hides the protocol 
 specific natures of the various devices from applications.  Developers can 
 then be focused on developing message content of their particular applications 
 rather than worrying about the actual delivery mechanism for the wide ranging 
 types of devices.  The messaging API accepts a description of the recipients 
 then guarantees the delivery of the messages, including communicating with 
 the device using whatever native protocols appropriate for the devices, 
 for example, email, SMS, fax or voice.  

 It is apparent that there must exist components that are transport protocol 
 specific for the system to work from end to end.  This is how the driver API 
 layer comes into play.  The driver API provides an extensible interface for 
 network/protocol specific drivers to be plugged into the OracleAS Wireless system.  
 A driver is the place to deal with specific network protocols, for example, 
 email, SMS or fax.  Drivers can be developed for any protocol.  
 As long as it honors the driver interface we specify, it can be added to the 
 system as a valid driver, extending the existing pool of supported protocols.  
 
 The transport component, together with the messaging API, nicely partitions 
 the role and responsibilities of most typical messaging applications.  
 Those that are primarily responsible for content generation should be 
 using the messaging API, without worrying how the content ends up in devices.  
 Those that are responsible for communication protocols with the driver APIs to 
 make sure messages correctly get to devices of the recipients, without worrying 
 about how and when the content were generated. 

 The transport system ties the two layers together by performing comprehensive
 matching and routing logic. It offers a simple and powerful platform for 
 messaging applications by further dealing with reliability, load distribion 
 and other issues commonly needed by today's high demanding messaging applications


<dl>
<dt>Author:</dt>
<dd>jxiang</dd>
</dl>
<hr>














<table>
<tr>
<td>Method Summary</td>
</tr>
<tr>
<td>DriverController</td>
<td>getDriverController()


          Acquire instance for access to the driver interface.</td>
</tr>
<tr>
<td>static TransportLocator</td>
<td>getInstance()


          Get the singleton instance of the TransportLocator.</td>
</tr>
<tr>
<td>MessagingController</td>
<td>getMessagingController()


          Acquire instance for access to the messaging interface.</td>
</tr>
</table>

<table>
<tr>
<td>Methods inherited from class java.lang.Object</td>
</tr>
<tr>
<td>equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait</td>
</tr>
</table>
 










<table>
<tr>
<td>Method Detail</td>
</tr>
</table>

<h3>
getInstance</h3>
<pre>
public static TransportLocator getInstance()

Get the singleton instance of the TransportLocator.

Returns:

the singleton transport locator instance.

getMessagingController

public MessagingController getMessagingController()

Acquire instance for access to the messaging interface.

Returns:

the messaging controller instance.

getDriverController

public DriverController getDriverController()

Acquire instance for access to the driver interface.

Returns:

the driver controller instance.