Configuring Oracle WebCenter Interaction Portlets in the Web
Control Consumer
To configure an existing .NET Web application to be used
in Oracle WebCenter Interaction, you must make a new entry in the
web application's Web.config file.
Once you add an entry to the Web.config file, all gatewayed
requests to the web application are transformed for use with Oracle
WebCenter Interaction. You can still access your web application directly;
the module is bypassed for any request that does not originate from
a portal server. For example templates, see the following folders
in the installation directory: \deploy\Web.config and \deploy\web.config.node
(node only). Your IIS Web Application Server must have direct web
access to the portal Image Service.
Note: Any .NET portlet page that
performs postbacks (including auto-postback) must be gatewayed. For
details on configuring the gateway, see the Oracle WebCenter Interaction
Web Service Development Guide or the portal online help.
In the /configuration/system.web node of the Web.config
file, add a new node that specifies the HttpModule class and containing
assembly, as shown in the example below:
<httpModules>
<add type="Com.Plumtree.Remote.Loader.TransformerProxy, Aqualogic.WCLoader, Version=3.1.0.0, Culture=neutral, PublicKeyToken=d0e882dd51ca12c5" name="PTWCFilterHttpModule" />
</httpModules>