Details
-
Type: New Feature
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: EE-3.2.0.GA
-
Fix Version/s: None
-
Component/s: Push Server
-
Labels:None
-
Environment:ICEpush, EPS
Description
Cloud Push makes use of a number of specific configuration parameters: org.icemobile.apns.keyStorePassword, org.icemobile.blackberry.applicationCredentials, c2dm.sender, as well as the APNS keystore. In some cases these parameters are provided via System Properties, but this is not always desirable, and in this case the meta-information is provided either in web.xml or other files within the web application. EPS does not have direct access to these files, however, so will be unable to use Cloud Push without modifying eps.war.
It is desirable that EPS can support Cloud Push without a modified eps.war.
It is desirable that EPS can support Cloud Push without a modified eps.war.
Activity
Ted Goddard
created issue -
Ted Goddard
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Jack van Ooststroom [ jack.van.ooststroom ] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Security | Private [ 10001 ] |
Jack Van Ooststroom
made changes -
Fix Version/s | EE-4.0.0.GA [ 11170 ] |
Jack Van Ooststroom
made changes -
Priority | Major [ 3 ] | Minor [ 4 ] |
Jack Van Ooststroom
made changes -
Fix Version/s | EE-4.1.0.GA [ 12172 ] | |
Fix Version/s | EE-4.0.0.GA [ 11170 ] |
Ken Fyten
made changes -
Fix Version/s | EE-4.1.0.GA [ 12172 ] |
Most of the meta-information is in the form of simple strings, which could easily be sent via JMS. In the case of the APNS keystore, this is currently read from a classloader resource stream, but could be adapted to read a String from a JMS message.
BlackBerry BPNS configuration is more difficult since it makes use of 3rd party classes and a PushSDK.properties. It would be acceptable for BPNS to be the one Cloud Push mechanism that still required eps.war modification.