Leave feedback
  • Ad Hoc Notifications

Write an Article
Wednesday 23 July, 2014
Karim El-Cheikh Karim El-Cheikh StreamServe Employee
0 likes 1716 views

Notification framework for Ad Hoc Correspondence documents (on-demand) has been released in StreamServe 5.6.1 and can be used to initiate workflows in hosting applications based on notifications.

The AdHoc (on-demand) notification is based on lightweight Spring messaging framework which is used in the StreamServe web application framework.Workflows in hosting applications based on notifications can thus be initiated. The notifications are based on SSSP via REST API access.

 

For SSSP OpenText StreamServe provides a publish-subscribe-channel named “notificationsChannel” and if a customization wants to make use of it i.e. listen to the notifications, the implementer needs to place a file named “sssp-notification.xml” first in the classpath for the SSSP webapp and there he can configure how he wants to listen to the events. The notification event sent will contain a header and a body. The header will be populated with a topic namespace and a topic id:
    topicNamespace* = streamserve.notification.sssp.<document|message>
    topicID* = <the action e.g. create, get, delete, etc.>
You integrate with external systems via declarative adapters (JMS, JMX, RMI, TCP, HTTP Request, File, AMQP etc.) for consumption of notification and they are then published for the following actions:
        Create document
        Get document
        Insert resource
        Save resource
        Delete resource
        Submit document
        change or set attributes

For SSSP OpenText StreamServe provides a publish-subscribe-channel named “notificationsChannel” and if a customization wants to make use of it i.e. listen to the notifications, the implementer needs to place a file named “sssp-notification.xml” first in the classpath for the SSSP webapp and there he can configure how he wants to listen to the events. The notification event sent will contain a header and a body. The header will be populated with a topic namespace and a topic id:

  • topicNamespace* = streamserve.notification.sssp.<document|message>    
  • topicID* = <the action e.g. create, get, delete, etc.>

 

You integrate with external systems via declarative adapters (JMS, JMX, RMI, TCP, HTTP Request, File, AMQP etc.) for consumption of notification and they are then published for the following actions:

 

  • Create document
  • Get document      
  • Insert resource      
  • Save resource      
  • Delete resource       
  • Submit document        
  • Change or set attributes

 

Comments (0)

   


Post comment