Skip to main content

An approach to integrate applications in to a portal engine


Displaying existing web interface of an application

Creating a portlet with a more granular level without relying on JSR 168 portlet API is done by embedding the web interface of an application to an IFrame (Inline Frame) portlet.

An IFrame portlet invokes an URL inside an IFrame within the portlet window. It gets content referenced by an URL and displays it in a portlet. IFrame portlets can be downloaded freely or else they can be found already integrated in many web portals. Thus a user can use a portlet integrated to a portal or either create a custom IFrame portlet. Basically these portlets contain following jsp pages:

--configuration.jsp (for edit mode) -This is for adding configuration values such as source URL of directing web page, look and feel attributes and authenticating attributes.

--view.jsp (for view mode) - This makes possible to view the embedded web page inside the current portal page with the help of the functions in the portlet namespace.

--proxy.jsp- This facilitates passing timeout values and authentication values.

Following custom configurations can be done to a default IFrame portlet.

--It is possible to configure the embedded URL by limiting the ‘iframeSrc’ portlet preferences attribute to a custom URL instead of adding the URL of embedded web page several times at each time the IFrame portlet is added to a portal page.

--It can be changed the portlet name by changing the parameter ‘portlet-name.value’ in the portlet.xml file.

--It is possible to manage session timeouts of an IFrame with Ajax using a XMLHttpRequest call to refresh the content inside the portlet without having to refresh the entire portal page[6].

--It can be configured to retrieve the user name and password of the current user, who is viewing the page using the ‘getUser’ method of the ‘PortalUtil’ class and that will be used to authenticate against the embedded web page.

Comments

Post a Comment

Popular posts from this blog

Convert an InputStream to XML

For that we can use DocumentBuilder class in java. By using the method parse(InputStream) ; A new DOM Document object will return. InputStream input; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); DocumentBuilder parser = factory.newDocumentBuilder(); Document dc= parser.parse(input); In the above code segment,by using the created Document object,the corresponding XML file for the inputStream can be accessed. References: http://www.w3schools.com/dom/dom_intro.asp http:// download.oracle.com/javase/1.4.2/docs/api/javax/xml/parsers/DocumentBuilder.html
2 comments
Read more

Concat two xml values with XSLT

The use-case described in this blog-post,is there's an WSO2 ESB node setup to proxy an incoming message to a particular back-end endpoint.  Before delivering the message to the back-end endpoint,from the ESB node itself,this incoming message need to processed and change its inside xml payload format. For eg: Below is the incoming message <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"> <OwnerData> <Name>John Smith</Name> <openedDate>12/12/80</openedDate> <quality>good</quality> </OwnerData> <CinemaHallData> <rows>100</rows> <seats> <seat>50</seat> <seat>60</seat> </seats> </CinemaHallData> </CinemaHall> This message need to be changed as  below; <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"...
3 comments
Read more

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage  as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...
7 comments
Read more