IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Additional Tivoli Enterprise Portal configurations > Configure HTTP communication between the portal client and server

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Browser client

Take the steps outlined in this section to configure the browser client.

  1. In the Manage Tivoli Enterprise Monitoring Services window, right-click Tivoli Enterprise Portal browser client.

  2. Select Reconfigure.

  3. In the properties list, locate and double-click the property tep.connection.protocol.

  4. In the Edit Tivoli Enterprise Portal Browser Parameter window, change the value to http.

  5. Click OK.

  6. Click OK to close the Configure Tivoli Enterprise Portal Browser window.

  1. Edit the $CANDLEHOME/platform/cw/applet.html file.

  2. Scroll down to the following section at the end of the file:

      var parameters = { 'cache_archive': cache_archive,                    'cache_version': cache_version,                    'java_arguments': javaArgs,                    'applet_stop_timeout': '5000',                    'kjr.trace.params': 'ERROR',                    'cnp.publishurl.encryptuid': 'false',                    'cnp.cmwapplet.systemout': 'YES',                    'code': 'candle.fw.pres.CMWApplet',                    'codebase': 'classes/',                    'mayscript': 'true',                    'cache_option': 'plugin',                    'scriptable': 'true',                    'kjr.trace.mode': 'LOCAL',                    'cnp.publish.url': 'true',                    'cnp.window.timeout': '0',                    'javax.net.ssl.trustStore': 'jcf.jks'
                       };

    Add the following line: 'tep.connection.protocol': 'http'

  3. To enable secure communication using https, substitute https where http is specified for the new parameter.

For the browser client, the valid options are iiop and http. These values instruct the client to use either the CORBA IIOP protocol or the HTTP protocol. The use of the secure HTTPS protocol is determined by the protocol specified in the URL used to connect to the portal server. For example, if you connect to the portal server using a URL that starts with http://, all communication with the server is unencrypted. The following table describes the browser client behavior:


Browser client behavior

tep.connection.protocol value URL begins with Result
http "http://" All communication uses the HTTP protocol.
https "https://" All communication uses the HTTPS protocol.


Parent topic:

Configure HTTP communication between the portal client and server

+

Search Tips   |   Advanced Search