Configuring HTTP Proxy support for Push Notifications for Mobile

Enable notifications to be sent to mobile users about Connections events.

Before you begin

You can configure an authenticated or a non-authenticated proxy. Steps 1 is only required if you are using an authenticated proxy.

About this task

To enable and configure HTTP Proxy support for Push Notifications, complete the following steps:

Procedure

From the WebSphere® Application Server Administrator console, navigate to Security > Global security > Java Authentication and Authorization Service > J2C authentication data to add a J2C authentication alias for your Squid Proxy Server user credentials. Specify proxyMobilePushNotificationJAASAuth as the Alias. Ensure that the Prefix new alias names with the node name of the cell (for compatibility with earlier releases) option is not enabled. Click Apply after removing the selection. Click OK.
Check out the mobile-config.xml file for editing. For more information about checking out the file, see the Changing Mobile configuration property values topic.
Open the mobile-config.xml file in a text editor.
Make sure you are updating the deployment manager (Dmgr) server copy of mobile-config.xml. Add the following entries to the Push Notifications section, after PushNotificationReapInterval, in mobile-config.xml:
```
<ProxyHost>yourproxyhost</ProxyHost>
 <ProxyPort>yourproxyport</ProxyPort>
```
The following are example entries:
```
<ProxyHost>calamari.pnp-hcl.com</ProxyHost>
 <ProxyPort>3128</ProxyPort>
```

To configure the HTTP client timeouts, add the following optional Proxy Http Client parameters within the GCM parameter of mobile-config.xml. The default values are shown in the following code example:

<GCM>
    <!-- Number of persistent connections to the GCM service -->
    <MaxPooledConnections>10</MaxPooledConnections>
    <!-- The interval in seconds before pending messages are flushed -->
    <MessageFlushInterval>15</MessageFlushInterval>
    <!-- API Key needed by the server to send the Push Message to GCM -->
    <GCMAPIKey></GCMAPIKey>
    <!-- Sender Id needed by the Client to register itself with GCM -->
    <GCMSenderId></GCMSenderId>
    <!-- Proxy Http Client: The timeout in seconds used when requesting a connection from the connection manager/pool. -->
    <ConnectionRequestTimeout>300</ConnectionRequestTimeout>
    <!-- Proxy Http Client: The timeout in seconds to establish a connection with the Proxy Server. -->
    <ConnectTimeout>100</ConnectTimeout>
    <!-- Proxy Http Client: Defines the socket timeout in seconds, which is the timeout for waiting for data or, put differently, a maximum period inactivity between two consecutive data packets). -->
    <SocketTimeout>300</SocketTimeout>
 </GCM>

Ensure that Push enabled, in the Push Notifications section of mobile-config.xml, is enabled in the deployment manager copy of mobile-config.xml.
Save and check in the mobile-config.xml file.
From the WebSphere® Application Server Administrator console, resynchronize the nodes by updating the application node copies of mobile-config.xml.