This type of portlet is the most flexible because it is not actually integrated into the Portal. IURI portlets allow you full access to the browser frame and to take existing web content and display it in the Portal.
This type of portlet always requires interaction between the Portal and a web server. URI portlets can be written as CGI, Java servlets, or HTML pages, and they can reside on a server other than the Portal server. URI portlets tend to be slower than the other portlets.
This type of portlet requires no interaction with an external server, so it provides quick response with very little external resource load. HTML portlets can contain references to applets, ActiveX controls, and images, but the HTML is taken directly from JD Edwards EnterpriseOne database, so the content is static. You can take advantage of pass-through functions, such as RunOWApp and addRunOWAppFI with HTML portlets as well. These functions enable you to launch JD Edwards EnterpriseOne applications.