Configure the Ajax proxy to allow FileNet requests

The CCM portlet makes direct requests to the FileNet server which may be embedded with Connections or deployed to a separate server. Configure the Ajax proxy so that requests can pass through the Ajax proxy. If we installed the embedded option when we installed IBM Connections, we do not need to perform these steps.

1. Determine the http and https URLs for the FileNet server.

   Edit...

   WAS_HOME/AppServer/profiles/Dmgr01/config/cells/cell/LotusConnections-config/LotusConnections-config.xml

   ...and locate the <sloc:serviceReference> entry with the value serviceName="ecm_files"...

   <sloc:serviceReference bootstrapHost="" 
                          bootstrapPort="" 
                          clusterName="" 
                          enabled="true" 
                          serviceName="ecm_files" 
                          ssl_enabled="true">
           <sloc:href>
               <sloc:hrefPathPrefix>/dm</sloc:hrefPathPrefix>
               <sloc:static href="http://xxx.rtp.raleigh.ibm.com" ssl_href="https://xxx.rtp.raleigh.ibm.com"/>
               <sloc:interService href="https://xxx.rtp.raleigh.ibm.com"/>
           </sloc:href>
       </sloc:serviceReference>

   Take note of the href and the ssl_href attributes to use to run the command in step 3.

2. Configure the Ajax proxy to handle all requests to FileNet:

   cd wp_profile_root]/ConfigEngine   
   ./ConfigEngine.sh action-config-ajax-proxy-SNPortlets-filenet \
                     -DICfilenetURL=[ssl_href_attribute] \
                     -DICfilenetURLunsecured=[href_attribute] \
                     -DWasPassword=[was-admin-password]

3. To remove the Ajax proxy configuration for FileNet:

   ConfigEngine action-remove-ajax-proxy-SNPortlets-filenet \
                -DWasPassword=[was-admin-password]
   

Parent topic:
Deploy the Connections Portlets