Portal Connection 

The Portal Connection Framework offers an API that enables control over the request. This layer enables several Connection implementations to be plugged into the portal. Each implementation may have a different request cycle.

Connectionimplementations are delivered and packaged as regular portal applications, with the following constraints:

·        The application must be declared as Load-on-startup in the application-config section of the deployment descriptor

·        The connection must register itself to the portal registry

·        The connection must implement the IServletConnection interface

By default two connections are provided by the portal runtime:

Connection	Type	Description
/runtime/connections/portal	Servlet connection	Default connection of the portal
/runtime/connections/soap	Soap connection	Handle any incoming SOAP request

Connection Registration at Start Up:

The registration must bind an object of type IServletConnection in the connections JNDI context of the portal registry. This can be done during the initialization of a service that has been marked as load on startup.

public synchronized void init(IServiceContext context) {    mm_connection = new MyConnection();    try {       PortalRegistry.getInstance().bind(          "/runtime/connections/MyConnection",          mm_connection);    } catch (NamingException e) {    } }

The IServletConnection interface has defined a method:

·        handleRequest(IDispatcherContext) – the dispatcher context provides access to the environment in which the connection is started. It provides access to request and response