The Provider Test enables you to successfully test and display your portlets exposed as a web provider without an Oracle9iAS Portal installation.  This article describes how to setup and use the Provider Test utility.

ASSUMPTIONS

1. You have the Oracle9iAS Http Server Core installed.  This is just the web server with no products or tools installed.  You can download the HTTP Core at Oracle9iAS Portal Center:  Portal Studio - Getting Started.

SETUP ON OC4J

• Add the following entry in $J2EE_HOME/default-web-app/WEB-INF/web.xml

 <servlet>
               <servlet-name>testProvider</servlet-name>
               <servlet-class>testProvider</servlet-class>
  </servlet>
• Copy the following jar files in $J2EE_HOME/lib
• prohttp.jar
• testProvider.jar

• Add the following repositories in zone.properties

  repositories=D:\ORACLE9iAS\Apache\Jserv\servlets\prohttp.jar

  repositories=D:\ORACLKE9iAS\Apache\Jserv\servlets\testProvider.jar

  Note:  replace the directories listed above with your directory information.

   

• Add the following entry in zone.properties

servlet.testProvider.code=testProvider

• Copy the following jar files in $ORACLE_HOME/Apache/Jserv/servlets
• prohttp.jar
• testProvider.jar

• Goto http://hostname:port/j2ee/servlet/testProvider (OC4J)  or http://hostname:port/servlet/testProvider (Jserv)
• Enter the provider url and the range of portlet that needs to be tested for e.g
• url:  http://hostname:portl/servlet/sample
• Start portlet id : 1
• End Portlet id : 5
• Click on Submit
• A result table is displayed with the results of testing the provider/portlet.

The utility simulates Oracle9iAS Portal and makes calls to your provider. It tells you whether the calls made to register, deregister, and display show modes passed or failed.  A message of fail for a show mode may mean that you are not displaying that show mode at all, it may not necessarily be an error.  If you receive the fail message for a show mode that should be available, then it is a message that something is wrong.  The utility checks the following api calls to the provider.  

• Registration of Provider
• InitSession call (DoLogin)
• For Each Portlet ("start portlet" to "end portlet") increment by 1
• Portlet registration
• Get Porlet info
• Is the portlet runnable
• Copy Portlet
• Mode Show
• Mode Customize
• Mode Show Details
• Mode Preview
• Mode Edit Defaults
• Mode Help
• Mode About
• Deregistration of Provider

If your portlet does not display a particular mode, the Provider Test displays the result for that mode as 'failed'.  Registration, DoLogin, and Deregistration are displayed at the end of the HTML output.

• The Result page does not show the portlets properly in the table

• The utility uses HTML Table to format the results and this problem can occur if the portlets are not rendering the correct html (especially in mode other then Show). Ensure that the tables are properly closed in other modes also.

• For example:  Porltet 1 of the PDK-Java samples does not close the HTML table in mode_show, therefore the other portlets do not show up properly in the HTML output of the Provider Test.  Try view portlets 2 to 5 and/or view portlet 1 separately.

• April 4, 2002.