Oracle® Fusion Middleware

Installation and Upgrade Guide for Oracle WebCenter WSRP Producer for .NET

11g Release 1 (


March 2011

This book describes how to install and deploy the Oracle WebCenter WSRP Producer for .NET (previously called the .NET Application Accelerator) 11g Release 1 (

Hardware and Software Requirements for Oracle WebCenter WSRP Producer for .NET

The following hardware and software is required to develop and deploy portlets using the Oracle WebCenter WSRP Producer for .NET.

Table 1

Component Requirements

Host Computer


  • Oracle WebLogic Portal 10.3.2 with patch UFTG (the password for this patch in Smart Update is F7C3Y31I) and patch DT6N (the password for this patch in Smart Update is PP6BUVQS).

    The UFTG patch corrects a major issue with cookie management and must be applied in order for the Oracle WebCenter WSRP Producer for .NET to function on WLP.

    The DT6N patch corrects an issue with proxied ASP.NET AJAX resources and must be applied if you are using or planning to use ASP.NET AJAX features.

  • Oracle WebCenter


Oracle WebLogic Portal must be configured to block cookies from being stored in the browser (set resource-cookies to block-all in wsrp-producer-registry.xml).

Additional Documentation

The following additional documentation is available.

Table 2

Document Description

Release Notes

The release notes provide information about new features, issues addressed, and known issues in the release.

Development Guide

The Development Guide for Oracle WebCenter WSRP Producer for .NET provides detailed information on authoring portlets using the Oracle WebCenter WSRP Producer for .NET.

Installing the Oracle WebCenter WSRP Producer for .NET

The installation package installs the Oracle WebCenter WSRP Producer for .NET and configures necessary system tools. For details, see Understanding Your Installation.

Before beginning installation, make sure your system meets the prerequisites for installation. For details, see Hardware and Software Requirements for Oracle WebCenter WSRP Producer for .NET.

To install the Oracle WebCenter WSRP Producer for .NET, follow the steps below:

  1. Launch the installer (OracleWebCenterWSRPProducerForDotNet.msi) as a local administrator or as a user who has rights to configure IIS and set file permissions on the folder in which you wish to install the product.

  2. Complete the installation wizard pages as described in the table that follows.

Table 3 Wizard Pages

Wizard Page Description

Select Installation Folder

Enter the folder where you would like the product installed.

Confirm Installation

If you are ready to install the product click Next to proceed.

A panel showing the installation progress should appear. The installer will also launch a small number of command windows.

Installation Complete

Click Close to close the installer.

Understanding Your Installation

The installer adds files and saves configuration settings in the following areas:

File System

The installer sets the localized "NETWORK SERVICE" account to have modify access on the files in the \wsrpdefault directory. The localized "NETWORK SERVICE" account is the default user assigned to execute ASP.NET applications.

The installer lays down the following folders and files:

  • \Uninstall_resources: Contains executables used by the uninstaller to properly remove virtual directories and shortcuts added by the installer.

  • \assembly version: Contains assemblies required by the product.


    The installer does not place these assemblies in the GAC by default.
  • \wsrpdefault: Contains a working example of a deployment with the following subfolders:

    • \App_Themes: Contains styles and skins.

    • \bin: Contains assemblies for the IIS application associated with the \wsrpdefault folder.

    • \wsdl: Contains the SOAP endpoint files (.asmx) and WSRP definition files (.wsdl). In particular, WSRPService.wsdl lists the fully qualified paths to the SOAP endpoints. This file can be used to set a different fully-qualified domain name for the host machine.

    • \portlets: Contains Web Parts or application files.


The installer sets up an IIS web site and IIS virtual directory with application. Both are set to point at the \wsrpdefault folder described in the previous section. An IIS application pool called OraAppPool2 is created to run applications.

The web site is set up on the first available port starting at 8678. If you are using Windows 7 or Windows 2008, you will need to make sure that this port is available to computers coming from the outside (you may need to punch hole in your firewall for this port).

The IIS application is targeted at the virtual directory, \wsrpdefault, not the IIS web site, so you must navigate to the wsrpdefault virtual directory (e.g. rather than the root IIS web site (e.g.


Oracle WebLogic Portal's WSRP consumer does not properly render compressed content returned from IIS 7.0 and IIS 7.5. If you are running the WSRP producer for .NET on Windows 2008 or Windows 7, and you are using WebLogic Portal as the consumer, be sure to disable dynamic compression on IIS.

Start Menu

The installer adds the following items to the Start Menu:

  • Oracle Online Documentation

  • Uninstall

  • WSRP 1.0 WSDL (registers Web Parts placed in the /wsrpdefault folder as WSRP 1.0 portlets)

  • WSRP 2.0 WSDL (registers Web Parts placed in the /wsrpdefault folder as WSRP 2.0 portlets)

The WSDL links should be launched in your default browser. To register the portlets, copy one of these links into your WSRP consumer.

Confirming a Successful Installation

To confirm a successful installation, import the WSDL file for the sample Web Part included with installation into your WSRP Consumer using the steps below.

  1. From the Start Menu, click Start|Programs|Oracle Application Accelerator for .NET|WSRP 1.0 WSDL. The WSDL file should open in a browser window.

  2. Copy the URL from the browser window and paste it into your WSRP Consumer's registration tool. If you see any errors:

    • Confirm that the fully-qualified domain name generated by the installer is correct. If it is not correct, you will need to adjust both the URL to the wsdl and the URLs specified in the WSDL (see Understanding Your Installation for details on the location of the WSDL files).

    • Confirm that the host allows traffic on the port specified. By default, in Windows 2008 and Windows 7, only TCP traffic is allowed on port 80. You will need to adjust the firewall settings.

  3. You should see a single portlet called Simple Date Time in the list of portlets available on the WSRP producer. Select this portlet and add it to your portal.

  4. If your installation is working correctly, you should be able to see an example portlet with the following functionality:

    • A button that displays the latest date and time using ASP.NET AJAX.

    • A button that displays the latest date and time using standard ASP.NET postback.

    • Personalization of a single string preference from your WSRP Consumer's editor (the Personalize drop-down menu in Oracle WebCenter or the Edit button in Oracle WebLogic Portal).

Upgrading Existing .NET Application Accelerator Portlets

To upgrade existing Oracle WebCenter Interaction (or AquaLogic Interaction) portlets developed using the .NET Application Accelerator version 1.x, you must make modifications to your code. If you are upgrading from version 1.0, first upgrade to version 1.1.

If your portlet uses the profile provider, you must change the name and type of the profile provider defined in your project's Web.config file to WSRPProfileProvider as shown in the code snippet below.

<profile enabled="true" defaultProvider="WSRPProfileProvider" automaticSaveEnabled="true">
        <clear />
            <add name="WSRPProfileProvider" type="oracle.appaccel.wsrp.WebService.providers.profile.WSRPProfileProvider" applicationName="WSRPProfileProvider"/> 
        <clear />

For portlets developed for Oracle WebLogic Portal that use the profile provider, you must also upgrade property names to the 1.1 MP1 syntax. In version 1.0, the property set name was appended to the property name. In 1.1 MP1, the property name is placed in a group element.

  1. For each custom property set or user profile grouping, create a <group> element in the <properties> element within the <profile> element in the Web.config file for the portlet project. Add each user profile property to its respective group. Each property must be defined with a name and a type. If you provide a default value, it will be used if the property is not available.


    The name of the property must match the name sent by the source application.
        <group name="homeInfo">
            <group name="online">
                <add name="email" type="string"/>
        <group name="CustomProperties ">
            <add name="title" type="string" defaultValue="No Title"/>
        <group name="MyProfile">
            <add name="Name" type="String" defaultValue="Guest"/>
            <add name="Age" type="Int32"/>
  2. Reference the property in the portlet page by name using the Profile object. The correct syntax is shown below.

    string title = Profile.CustomProperties.Title
    string name = Profile.MyProfile.Name;
    int age = Profile.MyProfile.Age;

The other namespace changes implemented in version 1.1 MP1 provide new classes and do not affect existing 1.0 portlets. (You may need to add namespaces to access new functionality.)

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired.

Oracle Fusion Middleware Installation and Upgrade Guide for Oracle WebCenter WSRP Producer for .NET


Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.