Windows
There are no Windows specific prerequisites to use push notifications.
IBM i Prerequisites
Mandatory PTFs
To use the HTTP methods for push notifications on the IBM i, there is a PTF that must be applied prior.
| O/S | PTF |
|---|---|
| V7R5M0 | SI81847 |
| V7R4M0 | SI81848 |
| V7R3M0 | SI81849 |
Configuring Required Permission for Your Certificate Store
The user profile of your LANSA listener e.g. DC@PGMLIB must have READ access to the certificate store file you will be using when you make your HTTP request.
Make sure that the user profile has READ and EXECUTE access to all directories in the file path.
The default system certificate store located on this path:
/QIBM/USERDATA/ICSS/CERT/SERVER/DEFAULT.KDB
Trusted Certificate Authority (CA) Certificates List
Make sure the list of trusted CAs is up-to-date, as the absence of the required CA certificates will stop you from being able to make secure HTTP requests.
Web Application
In order for your web application to subscribe a user to receive push notifications the webpage must be using a service worker and your website must be running in HTTPS.
Keys
In order to subscribe a user to push notifications and to send a push notification a valid EC prime256v1 Private Key in PEM format must be used. The same certificate must be used to generate the Vapid public key for the subscribing a user and passed into the push SendPush method.
Limitations
There exists limitations to the availability of some notification properties that can utilized by some browser for the displaying of a notification. For instance, Firefox does use the image property and if you were to set the PushMessageImageUrl property on the sending of notification, this will be ignored by any Firefox subscribed browsers and no image would be displayed.
To view which properties are available on a given browser see here