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

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...

How to rollback/commit processing messages from WSO2 ESB when enabled JMS transaction

This blog post describes the below use-case where WSO2 ESB 4.6.0 act as the intermediate channel in-between two JMS queues. The Use-case First messages will be de-queue to a proxy service deployed in WSO2 ESB from an queue in ActiveMQ message broker. Then inside ESB,the incoming messages will undergo with some message mediation flow and then the message will be send to another JMS queue deployed in JBoss server. Inside the ESB,following failures could be happen; a) Failures during message mediation process failure inside ESB [for example if you use dbreportmediator/lookup mediator inside mediation flow,some times failures can happen due to database connection failures] b) Message sending failure,due to endpoint is unavailability.[For example,the JBoss ...

TPP Journey through WSO2 Open Banking

Introduction 2018 is all set to be a game-changing year for European banking. The Revised Payment Services Directive (PSD2) has opened the door to new third party providers [TPPs] to connect with banks and manage finances of bank customers on behalf of them. The PSD2 regulation has mandated banks to expose their core-banking account data and payment services to authorized TPPs to consume. Thus as a bank it’s essential to have a solution which will securely expose their internal banking services to third party providers in a trusted manner. WSO2 Open Banking solution provides all required components to expose bank APIs in a well secured manner in order to become PSD2 compliant. This article explains about the importance of the TPP role in PSD2 domain, the requirements set that banks need to provide for TPPs by PSD2 regulations and how WSO2 Open Banking solution supports these requirements. From my last blog ,I have given an introduction for PSD2 and WSO2 Open Banking soluti...

Open Space

Search This Blog