I have been trying to finish this for a couple of weeks in my free time (did I say free time?)... I have some code fragments for that and I need to combine them all.
Anyway, This is a very simple database, But it will be very useful for me and I hope for others... Before going forward, I need some feedback about it. The database is called TestCopier. The purpose of this application is to create test/development databases from production ones. The following screen shows a preview.
Some features in my mind:
- Percentage is important, but it's not the first X%. There is a randomizing algorithm to find different sets each run. - The copied documents will have the exact same UNID with the source. However, the database will have different replica id. - I'm planning to use Lotusscript, but it might be changed. - User can save this profile for future uses. - Delete attachments in copied docs would be possible (by David Leedy).
Now there are more complicated possibilities:
- Instead of forms, I can use only formulas. So it would be more flexible but we will lose "copy the rest" feature. - Cross key lookups (by Nathan): Pickup some field values from, say, Customer docs and lookup them in some view (e.g. get selected customers' order documents). - Run some kind of formula to profile documents to change profile document values in test databases. So you can preserve those changes each time you need it. - Run some kind of formula to make changes every document, so you can alter some server/DB/Name references for copied documents.
Two critical HTTP problems in Domino 9...
Fri, Mar 29th 2013 6:48a Serdar Basegmez After I upgraded my servers to Domino 9, I have found two problems affecting HTTP task. 1. Redirect TCP to SSL problem... My HTTP task stopped responding just after the upgrade. When I look into thread logs I saw that it was redirecting every requests to the same URL! After a couple of tests, I found that if you have "Redirect TCP to SSL" checked in your Internet Site document, it fails with infinite redirection problem. I posted the issue into the N/D 9.0 Social Edition forum and [read] Keywords: administration
Happy Pi Day present: Pi Calculator for XPages...
DOTS Deep Dive 4: I can schedule myself...
Thu, Feb 21st 2013 5:20a Serdar Basegmez Finally, we will be able to enable FeedMonster for CollaborationToday project. While doing final touches, I have been challenged by a question: "Can we schedule DOTS tasklets programmatically?" Actually, this is in the wish list for the next version of DOTS. But we can do some trick here. I didn't test this on Domino 9 but it should work. Here is the code: package org.openntf.news.playground.tasklets; import org.eclipse.core.runtime.CoreException; import org.eclipse.core [read] Keywords: domino
DOTS Deep Dive 3: Warning for Deadlocks
Thu, Feb 14th 2013 7:03a Serdar Basegmez Last time, I have blogged about the importance of the importantance of canceling tasklets... In most of the time, canceling a task is a 'choice' you have. You might want to stop the task for a reason. However, a very important problem is falling into deadlocks. If somehow your code falls into a deadlock or stuck situation, that would lock your DOTS container entirely. DOTS uses a basic mechanism for identifying scheduled tasklets that are stuck. Every tasklet starts its life with a pre [read] Keywords: ibm
DOTS Deep Dive 2: Cancel me or I will crash your server...
Wed, Feb 13th 2013 3:53a Serdar Basegmez I just wanted to emphasize an important functionality within DOTS... One of our slides in the recent DOTS session in IBM Connect 2013, we have talked about the "monitor" argument in tasklets. It has two important uses. First of all, you might let DOTS container know about your progress. Second, it allows you to cancel your task in a less-disruptive manner. Let's dive into code here. Our tasklet is running every five seconds and wait 30 seconds each run: @RunEvery( every=5, [read] Keywords: domino
DOTS Deep Dive 1: Art of Scheduling Tasklets
Mon, Feb 11th 2013 4:02a Serdar Basegmez After a successful IBM Connect session, I started a series of posts, based on feedbacks I received from other developers. There was a little thing I didn't test before the session and this issue has been asked a couple of times: Possible conflicts between scheduled tasklets. Unfortunately, current implementation within DOTS is based on single threaded approach for tasklets. There are three different threads responsible in DOTS tasklet container for scheduled, manual and triggerred tasklet [read] Keywords: domino