Enabling push notification for the WAS proxy server

If you set up a WebSphere® Application Server for long polling, you must enable push notification for that WebSphere Application Server.

Before you begin

About this task

Procedure

  1. To enable push notification, make the following change in LotusConnections-Config.xml:
    <sloc:serviceReference bootstrapHost="admin_replace" bootstrapPort="admin_replace" clusterName="" enabled="true" 
    serviceName="pushnotification" ssl_enabled="true">
       <sloc:href>
          <sloc:hrefPathPrefix>/push</sloc:hrefPathPrefix> 
          <sloc:static href="admin_replace" ssl_href="admin_replace"/> 
          <sloc:interService href="admin_replace"/> 
       </sloc:href> 
    </sloc:serviceReference>
  2. To configure push notification settings, you must update pushnotification-config.xml. The following example provides some sample information. The settings that you need in your environment might vary.
    <config id="pushnotification"      
              xmlns="http://www.ibm.com/connections/pushnotification/pushnotification-config/1.0"
              xmlns:tns="http://www.ibm.com/connections/pushnotification/files-config/1.0"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"      
              xsi:schemaLocation="http://www.ibm.com/connections/pushnotification/pushnotification-config/1.0
          pushnotification-config.xsd">
              
           <cache>
                <user timeout="3600000" />
           </cache>
    
           <db dialect="DB2" />
    
           <message>
                <queue maximumAgeInHours="720"/>      
           </message>
    
           <scheduledTasks>
                <task name="MessagePrunning" interval="0 0 0-23/3 * * ?|0 30 1-23/3 * * ?" enabled="false" type="internal"/>      
           </scheduledTasks>
    
           <server> 
               <bayeuxServer logLevel="3"/>          
               <transports timeout="60000" interval="0" metaConnectDeliverOnly="true" maxQueue="-1"/>
           </server>
    </config>
  3. Enable the source provider of the filesync channel:
    1. Verify that the filesync entry in files-config.xml is set to true:<fileSync enabled="true">
    2. In the Files application, make sure the applicable users and groups have the security role filesync-user assigned.

      For example, to assign the filesync-user role to all authenticated users, navigate to Applications > Application Types > Enterprise Applications > Files > Security role to user/group mapping from the Websphere console. Select the filesync-user check box for All Authenticated in Application's Realm.

    3. Verify that the gatekeeper flag FILESYNC_PUSH_NOTIFICATION_SERVICE is set to true. The default value is false.
  4. Enable the notification center's use of the push notification service.
    Verify that the gatekeeper flag NEWS_PUSH_NOTIFICATION_SERVICE is enabled.