TECHP09 Web Application Bridge (WAB): “No Coding!” Integration Style for External Web Applications in WebSphere Portal Jason Cornell, Product Manager, IBM Web Content Manager Samit Narula, Web Experience Software Developer, IBM The enterprise today provides web experience through multiple web ...

Learn what is new with the latest version of the web application bridge.

If you have an existing beta version of the web application bridge, you can upgrade it to the current version.

If you have an existing, nonbeta version of the web application bridge, you can upgrade it to the current version.

The intention of the Web Applications Bridge is to support the complex and heterogeneous web applications that have been constructed using common best practices and function according to industry accepted standards.

The site XML descriptor file has many elements that are optional. You can add them to the descriptor file before or after you install it. These elements can show a custom name in the Web Dock portlet skin or customize how IBM® WebSphere® Portal interacts with backend sites.

You can use the site XML descriptor file schema when creating your own site XML descriptor files.

You can provision any backend site that follows the standard http rendering in IBM® WebSphere® Portal. Setting up the web application bridge requires a descriptor file that is installed into WebSphere Portal. You then add the web application to a page with the Web Dock portlet.

If the backend site requires SSL support, you will need to retrieve the security certificates.

The web application bridge uses reverse proxy technology to integrate webbased content providers, such as the Microsoft SharePoint 2007 server, with IBM® WebSphere® Portal. Administrators must first define the virtual web applications or content providers as an XML file. Then they must install ...

You can remove the web application bridge feature from IBM® WebSphere® Portal.

You can install a new version of the web application bridge.