Failsafe handling of calls to Informatica BPM
Info
This way of fail safe handling is deprecated since 10.0 as the communication between Product 360 server and the BPM engine does now support a message queue mode. See Message Queue API page.
To provide failsafe capabilities for calls to the Informatica BPM engine, there are two strategies available:
messages are buffered within a JMS message queue (See JMS in Product 360)
messages are buffered in memory
The JMS message queue solution offers the possibility to buffer a high number of messages and persist them, but fails if the network connection is broken also. This can be declared as high resilient solution against system failures.
The in memory queue solution has limited capacity and the data is lost if the Product 360 server is shut down.
It is possible to configure one, both or no solution at the same time. In the case both (JMS queue and in-memory queue) are configured, the JMS queue is used as a first failsafe queue and in-memory queue as a backup queue if the JMS connection not available.
The configuration has to be done in the <P360_SERVER_INSTALLATION_ROOT>\configuration\HPM\server.properties file of the P360 server application.
The following properties are relevant for the failsafe handling of calls to Informatica BPM:
|
Property name |
Default value |
Example |
Required |
Description |
|
infa.bpm.queue.jms.connection.url |
uses the audittrail configured jms connection url |
if JMS queue should be enabled |
connection url to the JMS message queue broker. If left empty the JMS queue will be disabled |
|
|
infa.bpm.queue.inMemoryBackupSize |
10000 |
If in memory queue should be available this has to be >0 |
the capacity of the in memory queue. If set to 0 the in memory queue will be disabled |
|
|
infa.bpm.queue.threadpool.size |
50 |
no |
Number of parallel working threads to process queued messages |
|
|
infa.bpm.queue.throttlingDelayMiliseconds |
10000 |
no |
Forced retry delay if a call to Informatica BPM has failed before |
|
|
infa.bpm.queue.messageLifetimeHours |
96 |
no |
If messages are queued they will expire after the given amount of hours |
|
|
infa.bpm.queue.jms.connection.username |
no |
Username if authentication is required |
||
|
infa.bpm.queue.jms.connection.password |
no |
Password if authentication is required If you want to encrypt the password please refer to chapter Encryption of secure information in the Server Installation manual. |
||
|
infa.bpm.queue.jms.queue.suffix |
no |
A suffix that will be appended to the default queue name ("infa.bpm"). The suffix can contain characters a-z, 0-9 |