Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Push Notifications in Pega MKT does not work though HTTP Proxy



The issue reported environment has HTTP proxy configured in WebSphere JVM for Internet connectivity.
So in order to setup environment for Push Notification user has white-listed the following URLs in proxy:
  •; as described here:

Based on official Google and Apple documentation, and this has not been documented  in Pega Marketing (MKT) documentation.

Apple Push Notification service (APNS) integration has been moved to next Phase thus currently user is trying to test Google Cloud messaging (GCM) integration. Unfortunately it does not want to work even though user confirmed through curl command executed from Pega 7 servers that white-listing for proxy is correct, user is getting correct response from Google.

Note: See
 exact curl command in Steps to Reproduce section.

Given above user suspect Pega MKT uses old, deprecated Google GCM URL that is:

Error Messages

No error messages but failed to send message to GCM

Steps to Reproduce

1. Launch Pega Marketing.
2. Go to Configuration > Settings > Channels > Push Notification.
3. Add a new Application with Android variant, using for example the following values:
  • Application Name: xxx_BANKING
  • Application Description: xxx Banking Application
  • What Platform is this for: Android
  • What is the unique ID for this app variant: xxx-ANDROID-SMARTPHONE
  • What is the google key: xxxxx

4. When variant is created click on the actions button and use the following token: xxxx


Root Cause

URL used by PRPC in GCM and APN is not documented.


GCM (Google Cloud messaging) 
Pega Marketing ships gcm-server.jar in its own codeset. Base Pega ships this jar as prgcmserver.jar. Both jars have the following URL specified for the GCM endpoint: 

Apple Push Notification service (APNS) 
Pega Marketing previously used to ship apns jars in its codeset. Pegasystems stopped doing this as of the last release (7.21) and the Pega Marketing batch functionality relies on the apns jar shipped as part of Pega. Even with previous releases (such as 7.12, 7.13), there should be no discrepancy between the information used by the Pega Marketing jar and the Pega jar. The APNs code utilizes the following destinations: 

Gateway: Host =, Port = 2195 
Feedback: Host =, Port = 2196 

Gateway: Host =, Port = 2195 
Feedback: Host =, Port = 2196 


Published May 25, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us