Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Overview

This sample demonstrates how to build a Portlet project in SAS AppDev Studio 3.3, and also how to create a .par file from the project so that the project can be tested in SAS^® Information Delivery Portal. The instructions assume that you have already completed the new workspace setup steps that were performed after the installation.

Create a New Portlet Project

1. Build a new Java project by following the instructions in Sample 32233.
2. When building the project, select either SAS Information Delivery Portal JSP Portlet or SAS Information Delivery Portal Remote Portlet, depending on whether you are building a local portlet or a remote portlet.

   

3. On the next page, fill in the portlet information. This information is primarily used to generate the portlet.xml, and can easily be modified later by editing the portlet.xml.

   Here is an example of properties for the SAS Information Delivery Portal JSP Portlet template.

   

4. When you are done entering the properties, click Finish to build the portlet.

Build the .par File and Deploy It to the Portal

SAS AppDev Studio does not provide any method to test the portlet locally. When you are ready to test the portlet, you must create a ,par file, and then copy that file to the machine where the Portal is installed.

1. Right-click on the [ProjectName].xml file, and select Run As ► Ant Build.

   

2. Right-click on the project, and select Refresh.

   

3. Right click on the [ProjectName].par file, and copy the file.

   

4. Move the .par file to the following location on the server where Portal is running:
   [SASHOME]\Web\Portal2.0.1\DeployedPortlets

   Note: If a copy of the .par file is already deployed to the Portal, you must stop the Portal and delete the existing file before copying the new file to the DeployedPortlets directory.

   Tip: When building a portlet, you might need to restart the server multiple times while making changes. To speed up the process, as soon as you know that you will need to push a new copy of the .par file, restart the application server and delete the existing .par file. By the time that you are ready to copy changes to the DeployedPortlets directory, the Portal will be started and ready to test the new portlet instance.





---

These sample files and code examples are provided by SAS Institute Inc. "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Recipients acknowledge and agree that SAS Institute shall not be liable for any damages whatsoever arising out of their use of this material. In addition, SAS Institute will provide no support for the materials contained herein.

---

These sample files and code examples are provided by SAS Institute Inc. "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Recipients acknowledge and agree that SAS Institute shall not be liable for any damages whatsoever arising out of their use of this material. In addition, SAS Institute will provide no support for the materials contained herein.

Operating System and Release Information