LDN - Luminis Developer Network

At one time, we seemed to get adapter logs rolled over based upon the log file size. We would end up with adapter.log, adapter.log.1, adapter.log.2... where adapter.log is the current log, adapter.log.1 is the next most recent, etc.

Does anyone know where this behavior is activated?

It would be handy to have for other logs as well (Eg. dispatch.log, ldi_event_data.log, etc).

I realize I could do it via "time" by making a cron entry but having it rolled based upon log file size is preferred.

TIA, Lee

What is a typical processing rate handled by your LMB? We're currently processing 50 events per minute.

We have Banner 8 running on a HP-UX 11.23 rx6600.  We have the brokers communication between it and the Luminis box (Sun).  We have many cases where a student won't get imported/built in Luminis because the email they have specified is the same as one or more other users.  If one of these entries is imported via "cptool import ims <filename>" then we get an error with the error and student ID.  This is fine.

At the U of S we take the XML messages from Banner and rewrite them before handing them off to Luminis.  This is both for LDI extracts and also LDI messages on-the-fly.  This post is not talking about the actual rewriting of the messages, I am concentrating only on how we intercept the LDI messages that are coming across JMS.