This service alters the characteristics of an existing polling notification. You must populate the input pipeline according to the table below before calling this service. To obtain a list of supported template and schedule properties, call the service wm.art.dev.notification:fetchPollingNotificationTemplateMetadata. You must disable a polling notification before updating its properties, using the disablePollingNotification service. For more information, see the webMethods Integration Server Built-In Services Reference for your release.

You might want to modify the following items:

These items are represented, respectively in the input pipeline as connectionAlias, notificationSettings, scheduleSettings,and publishableRecordDef.You may provide values in any or all of these parameters when calling this service. For the first three of these parameters, the service attempts to overlay the given values onto the notification's current values. The resulting set of merged property values are used to reconfigure the polling notification.

For instance, you can change the connection resource that the polling notification uses by providing a new connectionAliasinput parameter. If you omit this parameter, the notification continues to use its current connection resource. If you are changing only the connection resource, it is not necessary to provide the notificationSettings,scheduleSettings,or publishableRecordDefinput parameters.

For an example of setting values within the pipeline, see wm.art.dev.notification:createPollingNotificationNode. In particular, note that when constructing the notificationSettingsparameter, the value of the systemName metadata attribute is the adapter-specific internal name of a property. You should substitute the actual internal system property name for the systemName placeholder. (You can fetch the name using wm.art.dev.notification:fetchPollingNotificationTemplateMetadata.)

Unlike notificationSettingsand scheduleSettings, with publishableRecordDefyou must provide values defining the entire document; the service does not attempt to merge these values into the current publishable record definition. The values in publishableRecordDefwill replace the current definition values. You populate the publishableRecordDefparameter in much the same manner that you populate notificationSettings (as described above). The difference is that the fieldNamesand fieldTypesproperties view an array of String. There is a one-to-one correspondence between the elements in these two arrays.

When specifying property values, you must provide values that conform to the underlying data types of those properties.

Be aware of any resource domains registered by the notification, and set the notification's properties according to the interdependencies between resource domains. Knowledge of these interdependencies is adapter-specific, and beyond the scope of this service. This service does not interpret resource domains.

None.