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

CORS support from WSO2 API Manager 2.0.0

Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources  on a web page to be requested from another domain outside the domain from which the first restricted resource was served. For example, an HTML page of a web application served from http://domain-a.com makes an <img src >  request for a different domain as 'domain-b.com' to get an image via an API request.  For security reasons, browsers restrict cross-origin HTTP requests initiated from within scripts as in above example and only allows to make HTTP requests to its own domain. To avoid this limitation modern browsers have been used CORS standard to allow cross domain requests. Modern browsers use CORS in an API container - such as  XMLHttpRequest  or Fetch - to mitigate risks of cross-origin HTTP requests.Thing to  note is it's not only sufficient that the browsers handle client side of cross-origin sharing,but also the servers from which these resources getting need to handl
Post a Comment
Read more

[WSO2 AM] APIStore User Signup as an approval process

In previous versions of WSO2 APIManager before 1.6.0, it was allowed any user who's accessible the running APIStore come and register to the app.But there will be requirement like,without allowing any user to signup by him/her self alone,first get an approve by a privileged user and then allow to complete app registration.Same requirement can be apply to application creation and subscription creation as well.To fulfill that,we have introduced workflow extension support for  WSO2 APIManager  and you can find the introductory post on this feature from my previous blog post on " workflow-extentions-with-wso2-am-160 " . From this blog-post,I'll explain how to achieve simple workflow integration with default shipped resources with  WSO2 APIManager 1.6.0 and WSO2 Business Process Server 3.1.0 with targeting "user-signup" process. Steps First download the WSO2 APIManager 1.6.0[AM] binary pack from product download page . Extract it and navigate to
Post a Comment
Read more