Oracle® Fusion Middleware

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.

Additional Documentation

The following additional documentation is available.

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.

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">
    <providers>
        <clear />
            <add name="WSRPProfileProvider" type="oracle.appaccel.wsrp.WebService.providers.profile.WSRPProfileProvider" applicationName="WSRPProfileProvider"/> 
    </providers>
    <properties>
        <clear />
    </properties>
</profile>

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.

   Note:

   The name of the property must match the name sent by the source application.

   <properties>
       <group name="homeInfo">
           <group name="online">
               <add name="email" type="string"/>
           </group>
       </group>
       <group name="CustomProperties ">
           <add name="title" type="string" defaultValue="No Title"/>
       </group>
       <group name="MyProfile">
           <add name="Name" type="String" defaultValue="Guest"/>
           <add name="Age" type="Int32"/>
       </group>
   </properties>
   

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 http://www.oracle.com/accessibility/.

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 http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.