Oracle Portal Development Kit
Installing the PDK-URL Services Inline Rendering and Parameter Passing Samples

Welcome to the PDK-URL Services.  Now that you have successfully installed the URL Services Framework and Samples, you may want to use PDK-URL Services to create URL-based portlets.  This article describes how to install and configure the PDK-URL Services parameter passing and inline rendering portlets.

 

With parameter passing portlets, the Portal user can specify for himself what parameter values to pass to the URL on which the portlet is based.  With inline rendering, portlet links can be rendered inside the body of the portlet, instead of causing the whole browser to redirect to the selected destination.

ASSUMPTIONS

  1. You have already installed the samples downloaded with the most recent PDK-Java Framework and and understand the steps required to display a URL Services Portlet on a portal page. For more information on installing PDK-Java and Samples, please review the Installing the JPDK and Samples article.

  2. You have installed the PDK-URL Services runtime by following the Installing the URL Services Samples article.

  3. You are using this sample with Portal 3.0.8 and up.

  4. You are using JPDK 3.0.9.0.4 and up.

SETUP

Note: This section will update an Oracle HTTP Server configuration file, zone.properties. We recommend that you backup file before making the changes specfiied.  zone.properties is located at %ORACLE_HOME%\Apache\Jserv\servlets on NT. This file is  located at $ORACLE_HOME/Apache/Jserv/etc on UNIX.

Updating the zone.properties

  1. Stop the Oracle HTTP Server.

  2. Open zone.properties.

  3. Under the Servlet Aliases section add the following: 
    servlet.urlparams.code=oracle.portal.provider.v1.http.HttpProvider
  4. Under the Aliased Servlet Init Parameters section, add the following:
    servlet.urlparams.initArgs=provider_root=C:\urlservices\providers\urlparams,sessiontimeout=1800000, debuglevel=1

  5. Save and close the file.

  6. Start the Oracle HTTP Server.

  7. Now, test that you can execute the Adapter by calling the newly added alias. For example, type in the URL:
    http://host.domain:port/servlet/urlparams
  8. You should receive a sample page.

Updating provider.xml

  1. Go to the location of the provider.xml for this SSL Portlet.  It is located in the D:\urlservices\providers\urlparams directory.  The provider.xml file is setup to use a proxy server.  Note:  You will either need to alter these tags or remove them.  The portlets access URLs over the internet, so if you may or may not need a proxy server to access external URLs.

    1. If you do not need to use a proxy server, remove the following tags.

      <proxyInfo class="oracle.portal.provider.v1.http.ProxyInformation">

      <httpProxyHost>www-proxy.us.oracle.com</httpProxyHost>

      <httpProxyPort>80</httpProxyPort>

      </proxyInfo>

    2. If you need to use your own proxy server, alter the <httpProxyHost> and <httpProxyPort> tags and specify your proxy server and port.  

VIEW PORTLET

  1. Now that you have successfully tested your new alias and updated the provider.xml file, you will need to register a new provider that calls this alias.

  2. Register your new Provider.

    1. Name:  MyParameterPassingPortletProvider

    2. Display Name:  My PDK-URL Parameter Passing Portlet Provider

    3. Provider ID: Leave blank, it will automatically be generated

    4. Timeout:  100

    5. Timeout Message:  My PDK-URL Parameter Passing Portlet Provider Timed Out

    6. Implementation Style:  Web

    7. Register on Remote Nodes: No

    8. Provider Login Frequency: Never

    9.  URL:  http://host.domain:port/servlet/urlparams

  3. Click on OK.

  4. Now add your new portlet to a page.  

Now that you have successfully installed your own  PDK-URL Services parameter passing and inline rendering portlets using URL services, please look for future articles that will guide you through adding services to your portlet such as NLS, SSL, basic authentication, etc. Review the following URL services articles for detailed information about the URL services architecture:

Revision History: