| |
|
| |
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 provision any backend site using the Manage web application and the Web Dock portlets. |
| |
|
| |
The WebSphere Portal programming model is an extension of the J2EE programming model. Developers use it to implement Web applications that leverage the rich set of WebSphere Portal platform capabilities. Capabilities include aggregation and integration of components into page hierarchies, flexible ... |
| |
|
| |
The WebSphere Portal programming model is an extension of the J2EE programming model. Developers use it to implement Web applications that leverage the rich set of WebSphere Portal platform capabilities. Capabilities include aggregation and integration of components into page hierarchies, flexible ... |
| |
|
| |
The Web Dock portlet can send events to other portlets on the same page using client side eventing. |
| |
|
| |
The Web Dock portlet can receive events from other portlets on the same page. |
| |
|
| |
h2 IBM Lotus Sametime proxy server upgrade for IBM WebSphere Portal V7: V7IBM Lotus Sametime proxy server upgrade for IBM WebSphere Portal V7 h2
Installing Lotus Sametime proxy server upgrade for WebSphere Portal V7: V7Installing Lotus Sametime proxy server upgrade for WebSphere ... |
| |
|
| |
After creating a working application component, you can duplicate the component. This feature allows you to create multiple copies that have the same settings but different host or context root information. |
| |
|
| |
You can edit the web application component if changes are required. For example, you might have to change the context root or the host name. You might also want to change the settings associated with the component. |
| |
|
| |
After you attach a Web Dock portlet to a page, you can edit the settings. |
| |
|
| |
You can install a new version of the web application bridge. |
| |
|
| |
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. A lightweight IFrame portlet displays ... |
| |
|
| |
If you have an existing catalog version of the Web application bridge, you can migrate to the current version. |
| |
|
| |
The Web Dock portlet is capable of publishing a JSR 286 based portlet event. |
| |
|
| |
The Web Dock portlet is capable of subscribing to a JSR 286 based portlet event. |
| |
|
| |
The web application bridge supports sending events from the client side and server side. The WebDock portlet is capable of sending and receiving events from other portlets on the same page using a client side technique based on OpenAjax. With client side events, no page refresh is required. The ... |
| |
|
| |
The web application bridge supports the Simple and Protected GSSAPI Negotiation (SPNEGO) as the web authenticator for the application server. SPNEGO support relies on the scenario where IBM® WebSphere® Application Server is already configured for SPNEGO web authentication. |
| |
|
| |
The troubleshooting information is useful for planning and implementing your web application bridge integration. |
| |
|
| |
You can remove the web application bridge feature from IBM® WebSphere® Portal. |
| |
|
| |
If you have an existing, nonbeta version of the web application bridge, you can upgrade it to the current version. |
| |
|
| |
If you have an existing beta 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. |
| |
|
| |
Learn what is new with the latest version of the web application bridge. |
| |
|
| |
You can use filters to manipulate the request content going from the IBM® WebSphere® Portal page to the backend site. You can also use filters to manipulate the response coming from the backend site to the portal page. These filters are basically servlet filters. |
| |
|
| |
View information on setting up your operating system for IBM® WebSphere® Portal. Other components might require additional steps; see the product documentation for the specific components you want to install for information. |