IBM WEBi documentation update - Corrections for "Configuring access to IBM WEBi through a proxy server"

Product documentation


Abstract

The documentation in "Planning, Installing, and Configuring IBM WEBi" contains incorrect information for the configuring access to IBM WEBi through a proxy server.

Content

The following information is an update to the information in Configuring access to IBM WEBi through a proxy server.

Corrected text for "Configuring access to IBM WEBi through a proxy server"

If you embed IBM WEBi in a custom web application and IBM WEBi is not running on the same web application server as the custom application, you must configure access to IBM WEBi through a proxy server. This requirement is caused by the Same Origin Policy that is enforced by most web browsers and restricts cross-server scripting.

About this task

Restriction: IBM WEBi supports only forward proxy servers.

Tip: You can also access IBM WEBi through a proxy server when it is not embedded in another web application, but accessing IBM WEBi through a proxy server increases network traffic and decreases performance.

The proxy server is the web application server where the custom application is running. The proxy server receives the requests that are intended for IBM WEBi and forwards the requests to the IBM WEBi server.

When you include the webi.js JavaScript in your custom web application, you must add the wc_proxy parameter to the URL that points to the installed version of IBM WEBi. The wc_proxy parameter defines a proxy servlet on the application server where the custom application is running.

Tip: You can see a sample version of the wc_proxy parameter in the proxylaunch.jsp file, which is located in the wccommonservices directory of the IBM WEBi installation directory.

To enable your custom application to access IBM WEBi through a proxy server:

Procedure

  1. Construct the URL that points to the instance of IBM WEBi in the webi.js JavaScript and includes the wc_proxy parameter:
    1. Identify the URL of the proxy server where the custom application is running. The URL has the format http://custom_application_host_name:port_number/application_name/ proxy.
    2. Identify the URL to directly request webi.js. The URL has the format http://IBM_WEBi_host_name:port_number/wccommonservices/webi.js.
    3. Append the URL to directly request webi.js to the URL of the proxy server. The URL has the format http://custom_application_host_name: port_number/application_name/proxy/http/IBM_WEBi_host_name: port_number/wccommonservices/webi.js.
    4. Append the wc_proxy parameter that defines the proxy servlet on the application server where the custom application is running. The wc_proxy parameter has the format
      ?wc_proxy=/custom_application_host_name:port_number/proxy/http/ IBM_WEBi_host_name:port_number.

      The complete URL has the format http://custom_application_host_name:port_number/application_name/ proxy/http/IBM_WEBi_host_name:port_number/wccommonservices/webi.js? wc_proxy=/custom_application_host_name:port_number/proxy/http/ IBM_WEBi_host_name:port_number.
  2. Add the URL to the webi.js JavaScript in your custom web application in the first script tag:

    <script type="text/javascript" src="http://custom_application_host_name:port_number/application_name/proxy/http/IBM_WEBi_host_name:port_number/wccommonservices/webi.js? wc_proxy=/custom_application_host_name:port_number/proxy/http/IBM_WEBi_host_name:port_number">

    <script type="text/javascript">
      var webi = new WEBi(desktopName)
      webi.setLayout(layoutName)
      webi.showDesktop()
      webi.performAction(action)
    </script>

Rate this page:

(0 users)Average rating

Document information


More support for:

Content Manager OnDemand for Multiplatforms
WEBi

Software version:

1.0.4

Operating system(s):

AIX, Linux, Linux zSeries, Windows

Reference #:

7020870

Modified date:

2013-06-10

Translate my page

Machine Translation

Content navigation