#813993 - FAQ: Message status in the adapter framework
For more explanation:
we have four types of background processing jobs in the J2EE Adapter
Engine.
1) The Delete Job, which removes all final Msgs from DB, where the
persist duration has already expired.
2) The Archive Job, which first archives the Msgs and aftewards delete
them. The same rules apply, as in 1: Msgs have to be final (DLVD or
FAIL) and the persist duration must be expired.
3) The Restart Job: Retries all Msgs in status NLDV - which means the
automatic retries have been expired (3 times with 5 minutes interval as
default).
4) The Recover Job: Was introduces to reinsert all "broken" messages
into the correct Messging System components, after some severe error
situation, e.g. DB connectivity loss. This kind of job effects the
performance, as it requires some heavy synchronization. But we cannot
provide any exact numbers, as this depends on the status distribution ofall msgs in the DB.
This job e.g. reloads all msgs in status HOLD into the sequencer and
tries to restart all first msgs in HOLD, where the immediate predecessormessage is in final status.
In your case, you can use the Restart Job to resend NLDV messages. You
can go to http://<host>:<port>/rwb
-> Component Monitoring -> Integration Server -> Adapter Engine ->
Background Processing
-> Create
- choose a job name, choose Job Type "Restart".
- Choose the Start Date/Time for the first run of the restart job (you
can trigger the restart job any time, using the "Start Now" button)
- save the job using the "Save" button.
- go to edit mode by clicking the "Edit" button
- go to tab "Rules"
- configure rules to narrow the scope of the restart job to the messagesyou want to restart.
- don't forget to save the job
- either let the Restart Job run automatically at the configured time ortrigger it manually