Configuring the Ajax proxy to allow FileNet requests | HCL Digital Experience

Configure the Ajax proxy so that direct requests that the CCM portlet makes to the FileNet server are allowed to pass through the proxy server.

About this task

The CCM portlet makes direct requests to the FileNet server, which might be embedded with HCL Connections or deployed to a separate server. You must configure the Ajax proxy so that requests can pass through the Ajax proxy.
Note: If you installed the embedded option when you installed HCL Connections, you do not need to do these steps.

Procedure

  1. Determine the HTTP and HTTPS URLs for the FileNet server.
    1. Find the URLs configured for HCL Connections by looking in LotusConnections-config.xml at:
      • For a clustered deployment: /AppServer/profiles/dmgr_profile/config/cells/cell_name/LotusConnections-config
      • For a stand-alone deployment: /AppServer/profiles/app_server_profile/config/cells/cell_name/LotusConnections-config
    2. Locate the <sloc:serviceReference> entry with the value serviceName="ecm_files". The entry looks like:
      <sloc:serviceReference bootstrapHost="" bootstrapPort="" clusterName="" enabled="true" serviceName="ecm_files" ssl_enabled="true">
              <sloc:href>
                  <sloc:hrefPathPrefix>/dm</sloc:hrefPathPrefix>
                  <sloc:static href="https://hclpnpsupport.hcltech.com/csm?id=kb_category&kb_category=c0ef98b71bb0778083cb86e9cd4bcbf2" ssl_href="https://xxx.rtp.raleigh.ibm.com"/>
                  <sloc:interService href="https://xxx.rtp.raleigh.ibm.com"/>
              </sloc:href>
          </sloc:serviceReference>
    3. Take note of the href and the ssl_href attributes to use to run the command in step 3.
  2. Open a command line and change to the following directory:
    • AIX: wp_profile_root/ConfigEngine
    • Linux: wp_profile_root/ConfigEngine
    • Solaris: wp_profile_root/ConfigEngine
    • Windows: wp_profile_root\ConfigEngine
  3. Run this command to configure the Ajax proxy to handle all requests to FileNet:
    ConfigEngine action-config-ajax-proxy-SNPortlets-filenet -DICfilenetURL=ssl_href_attribute -DICfilenetURLunsecured=href_attribute 
    -DWasPassword=password
  4. Run the following command if you want to remove the Ajax proxy configuration for FileNet:
    ConfigEngine action-remove-ajax-proxy-SNPortlets-filenet -DWasPassword=password