150 - 200 of 221 tags for viewpoint

Pages

Created for Spring MVC framework, Spring form tags allow you to bind data to the backing object used by your portlet's controller object. This is especially useful for implementing preferences in a portlet, but they can be used anywhere a form is required. These are the same kind of tags discussed in the JSP and Tags page.

Writing quality unit tests for portlet controllers is important in the development process because doing so results in sound code. Unit testing quickly reveals flaws and regressions in code that has been written, allowing code to be more easily maintained.

The following article gives you a summary on how to implement the service layer in your portlet.

The following article describes how to implement data caching for better performance in your portlet.

The following article describes what you need to know to create a view in your portlet.

The following article describes how to add security and role based access to your portlet.

The following article describes how to internationalize the content within your portlet.

The Viewpoint Framework allows the user be able to configure their portal to view data in any timezone they desire and store this preference on the server. Database data on the Viewpoint Server is available as UTC, which is to be converted to user timezone on the display side (browser).

The default CSS styles for the widget library are defined in global.css in CommonsWeb. Styles for individual portlets should be defined in the css directory of each portlet. The PDK will create this directory for you. Although it is acceptable to have multiple stylesheets for a portlet, the best page loading performance is achieved with the fewest stylesheets. A unique CSS classname should be assigned to each new type of portlet that is developed. In order to prevent namespace collision, this CSS classname selector should be used in all portlet style sheets.

The following article describes conceptually how the Viewpoint Security Model is structured.

For general purpose DOM searching and manipulation, the jQuery library has been included with Teradata Viewpoint.

Additionally, some commonly needed javascript functions are gathered in the files and JS Classes below.

The following article displays in a diagram all the major parts of a portlet.

The Viewpoint Portlet Development Kit (PDK) is a set of APIs, user interface widgets, styles and other assets that allow you to develop portlets for Teradata Viewpoint. The PDK also includes a "lite" version of Viewpoint that you can run on your desktop. You can download Viewpoint PDK here.

Prerequisites

  • Intermediate understanding of the Java programming language
  • Intermediate to advanced level of Javascript, HTML, and CSS web programming experience
  • Understanding of the Spring MVC framework
  • Understanding of JDBC

It can be helpful to see the directory layout of a portlet.  Here is an example using the Hello portlet.

Inversion of Control (IoC) is the software architecture notion where the flow control of an object has been inverted from the more common architecture of "object A calls library procedure A" to "library procedure A calls object A". In this case of IoC, library procedure A is an abstract implementation (a Java Interface) of a given functionality that is dependent on object A's concrete implementation (a Java Interface implementation).

This article describes how to include online help with your portlet and how to create a sample help topic.

Developing portlets for Viewpoint requires a level of knowledge in certain technologies aside from being only a Java developer. Below are brief descriptions of some of the technologies used and links to books/webpages for more information.

The Business Delegate design pattern provides an extra layer of abstraction between the presentation view and the business services, in the case of Viewpoint; this is the Viewpoint Data Collection System (DCS).

The following series of articles describe the basic concepts required for understanding how to build and create Viewpoint portlets.  They describe what technologies are used and how portlets are structured.  You can download the Viewpoint PDK here.

This checklist is meant to be a guide of best practices for portlet designers and developers. Complying with all of these items will ensure that your portlet maintains a consistent look and feel, and performs well within the Viewpoint portal.

The following are a series of articles that provide reference information on how to create portlets, and the technologies you would need to know before you start developing them.

Teradata Viewpoint uses a highly configurable logging mechanism to output log messages. By default, it has been configured to output log messages to the server console. You can use the logging mechanism described below to format and print log messages from your portlet.

Teradata Viewpoint is a web portal that is a container for portlets. A portlet is a self-contained component that a portal user can display on one of their portal pages.

Viewpoint provides an enhanced security architecture, known as VISA (Viewpoint Information Security Architecture), that allows an individual portlet to specify its own security domain model and still plug-in to the overall security system to take advantage of common services. The key features of VISA include:

The VISA policy/authorization/verdict engine may initially seem a a little daunting, but it's really quite simple.

Before a security policy decision can be made, VISA must know the identity of the user attempting the action in question. Identity is established through a process of authentication: typically using a username and password.

Configuration of two XML files in your portlet's WEB-INF folder is required to integrate your portlet with VISA. The first file is the familiar web.xml where listener and filter classes are configured.

The following series of articles talk about how portal and portlet security is handled within Viewpoint.  They also describe how to implement security and permissions within your portlet.

Teradata Javascript Widgets provide the advanced GUI features that application developers want in data presentation without burdening the developer with the need to write a lot of tedious javascript code and CSS.

Rewind is a new feature in Teradata Viewpoint 13.0 that enables the user to move back in time to see what the portal looked like in the past. This is especially useful for investigating problems because the user can view the state of the system before, during, and after the problem occurred.

Namespacing a portlet view is very important because it prevents the unintended interaction of multiple portlets on the same page. This can easily happen if multiple HTML elements on the page have the same ID name or JavaScript variables have the same name due to closures.

Viewpoint recommends using the tool-tipping feature built into all supported browsers as the preferred way to show supporting or explanatory text. This is straightforward and easy to use, and does not add the performance overhead of the custom tooltip described below. The TDTTM implementation described below is deprecated as of Viewpoint 14.01

This section describes how to add unified client-server validation to JSP pages using the Teradata Viewpoint Client Validation Framework (CVF).

The JavaServer Pages (JSP) technology allows web developers to easily create dynamic web content. JSP consists of the Standard Tag Libraries (JSTL) and user-defined Tag libraries. Tag libraries provide users with a way to add reusable web components to their projects.

A JSP tag is a tag that you can embed in your JSP page just like regular HTML tags (e.g., the <table> tag). However, your JSP tag is not sent to the browser. Instead, it is evaluated by the JSP engine on the server side. The output of your tag is inserted into the page at the location where the tag was embedded.

The Data Access Object (DAO) design pattern is used in object-oriented programming languages in order to provide an interface to a database without providing details on the implementation of that database. By doing so, the implementation of a database may change without requiring changes to code that makes use of the data stored in the database.

This is a particularly difficult task to implement in a portlet, so let's start by understanding the challenges. First, what is a refreshed, parameterized page? A parameterized page is a page that can display dynamic information and needs parameters to determine the content that will be displayed.

 Here is the process for implementing a class that renders and processes a page that contains a form:

 Here is the process for implementing a class that renders a page:

You have two options for creating controller classes. You can extend the classes provided by SpringMVC or you can extend classes provided by Teradata Viewpoint. Both types of classes are configured the same way in your application configuration files.

When you create a new portlet project using the PortletGenerator, the project will contain an Ant based build system. You can use the following ant targets to build and deploy your portlet:

The following tutorial provides a step-by-step demonstration of how to generate a new portlet and how to modify the generated source files to create the Hello portlet summary page and preferences page.

The following tutorial provides a step-by-step demonstration of how to generate the DynamicQuery portlet and modify the generated source files to display data from your Teradata database.

It can be useful to save the last credentials and query specified by the user for a portlet instance so these fields do not have to be repopulated every time the user logs out of the portal and then back in. There are several modifications to the current code that need to be made to accomplish this task.

Once we have implemented the ConnectionManager to successfully retrieved our SQL query data, we need to wire it up so we make ajax calls to the server and run a query using the ConnectionManager. This is where the DynamicQueryDataserverController comes in.

Once we have created our ConnectionManager interface and ConnectionManagerImpl class that implements the interface, we need to make our implementation useful by hooking it into our DynamicQueryManager since it handles our business logic.

Once the project is generated, we will create and implement the ConnectionManager to run single statement queries against the Teradata Database using JDBC.

This section describes how to generate the DynamicQuery portlet project with the PortletGenerator. Once the project has been generated, we can start building the code necessary to both interface with the database through JDBC and interface with the user through the Viewpoint Portal.

The DynamicQuery portlet allows a user to submit a SQL query to a Teradata Database and view the query's result-set within the portlet.

This portlet demonstrates:

The amount of skew in a Teradata system can change frequently as requests move from step to step. So we would like for our portlet to refresh its contents periodically. This section describes the changes you will need in order to add a periodic refresh to your page.