Originally, when parsing through documents in a Lotus Domino agent, we obtained a view of all the documents and parsed through them one by one to see if the document met certain criteria. Our new solution is to use DocumentCollections instead and to perform a search statement on the DocumentCollection. This results in a more concise list of documents that meet the desired criteria. Performance is considerably increased because the Lotus Domino search function parses through the data much faster than any parsing code using 'if', 'while', and 'for' loops.
Here is an example of how documents were parsed through in the past (assume that the database has already been declared):
View productView = db.getView("Products");
Document productDoc = productView.getFirstDocument();
//Parse through the productDoc using if, while, and for loops to
//see if it meets the desired criteria......
//After finding a matching productDoc, alter or retrieve information
productDoc.getNextDocument();
Here is an example of how a DocumentCollection and the search function can be used to speed up performance:
DocumentCollection dc = db.search("SELECT (Form = ""Product Form"") &
(NumRoomsAvailable = " + 0 + ")");
Document productDoc = dc.getFirstDocument();
//No need to parse documents, since all documents meet criteria
//Alter or retrieve information
productDoc.getNextDocument();
Dan Boyum is a Software Engineer on the Business Solution Test team located at the Rochester, Minnesota, laboratory. He has 2.5 years of experience in the software testing field. His areas of expertise include Lotus Domino and Windows servers on iSeries. Dan can be reached at
Marilyn Dukart is an Advisory Software Engineer on the Business Solution Test team located at the Rochester, Minnesota, laboratory. She has over 15 years of experience in the software testing field. Her areas of expertise include Lotus Domino and WebSphere. Marilyn can be reached at
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online