In this final entry in our series on the SDK we’ll touch on Cognos Extended Applications, a set of JSP tags that enable the development of custom “portlets” that can be hosted by a number of “portal” applications, including IBM’s Websphere portal and SAP’s Enterprise Portal (as well as Cognos Connection, of course.)
JSP technology includes the ability to create custom tags that contain back-end code. Just as a set of tags like <a> </a> means something specific to the browser, and <%> </%> are used to demarcate code that will be executed on the server side (but is contained within the JSP page) the user can create tags of their own that will call code when the page is rendered but exists in a java class the user has created.
The Cognos SDK includes several tags libraries that can be used to create JSP pages that can then be registered with a portal. Once again, these libraries enable the user to essentially perform any task that can be performed through the normal interface, but extended or combined as the user wants. Once registered the JSP portlet will be available to users of the existing corporate portal. The details of registering a JSP page with the portal vary with the portal being used.
The Extended Applications approach is ideal for the development of content you want to present within an existing portal, but it is complex, and requires the use of the JSP portion of the J2EE stack.
The C8 SDK is a powerful tool for organizations that want to extend the power of Cognos 8 within the enterprise, and provides a number of tools to do so. The BI Bus API provides a set of classes that can be used to build applications that interact with C8 “from the ground up”. The URL API provides an easy, ‘lightweight” way of calling methods to interact with C8 via a correctly formatted URL, or from JavaScript within a client. Finally, Extended Applications provides a set of custom JSP tags within libraries that can be used to create JSP pages that can then be registered as portlets within an enterprise portal.
#1 by stu jackman on August 11, 2010 - 9:59 pm
Good list! Another option (for Cognos 8.4.1) is the Cognos Mashup Service API. It provides a REST and a doc/lit SOAP interface to BI content you create in Cognos.
#2 by BI Centre on August 11, 2010 - 11:21 pm
I would agree that the Cognos SDK can open more rich functionality to your application. The key is to have a solid development framework for your application and have the Cognos SDK as a complement to acquire more value. I always found that identifying its usage to the executive level always required some creativity and planning.
#3 by Peter on August 15, 2010 - 9:59 pm
I agree – particularly on your first point. For example, I’ve seen management convinced of the usefulness of a series of utilities developed over an extended period, only to discover that the utilities themselves have been developed in a number of different ways, using different languages, resulting in a disintegrated and difficult to maintain tool set.
#4 by Sebastian on September 16, 2010 - 6:03 am
Hello,
I’m interested in that topic. Is there some documentation or something else about your work, especially about the use an migration of Extended Applications?
In my mind, the BI documentation is not wery detailed enough.