This last week has been very busy for us, we have been developing the Object Auditing process for the next version of RAP which should be available by the end of the year. The initial concept of auditing file data used DDM Data Queues to move the auditing data between the systems, the target system didn’t report any results back to the source system. We now have Object replication in the product which required a TCP/IP client server process. Using this for the auditing gives us the ability to reporting back to the source any audit errors we find. The new audit process takes the object values from the source and compares them with the same values on the target system, if it finds any errors it will flag the errors back to a database file on the source. From this file you will be able to select objects for synchronizing between the systems using the same replication process built for object replication requests.
We did a few audts against the development environments (we know these are out of sync between the systems because of the various levels of code) to make sure we get the results we should expect and can confirm the audits work very well. It took about 3-5 seconds to audit about 500 objects from 1 library which should extrapulate fairly well for bigger environments as the API’s work the same no matter what size the object is. Of course this is over the 1GB LAN but for each object we only transfer 50bytes of data from the source and upto 205 bytes for returned errors back to the source.No errors means only 1 byte is returned which makes the process very lean on Bandwidth.
This is more or less the next version completed in terms of content, if we get more requests and it makes sense to add it we will do so, but for now we need to spend the rest of the time we have testing this to death, doing some code reviews and documenting the new release.
Chris…
PS:.. maybe I will get time to get back to the LAMPS server soon!