A Lotus Domino Weblog Tue, 18 May 2010 15:08:16 +0000 http://tooltips.teamstudio.com/tooltips.nsf en http://tooltips.teamstudio.com/tooltips.nsf/rss.gif http://tooltips.teamstudio.com/tooltips.nsf A Change is Gonna Come... http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-82XNZM John Coolidge http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-82XNZM http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-82XNZM Can you feel it? Spring is coming! For those of us in the northeast, green grass and warm weather still seem a long way off, but change is in the air. And we've got some exciting news!

For the past couple of years, Teamstudio has hosted three separate blogs, each one with a different focus. As much as we've loved hosting and posting on them, it's time to simplify things a bit. So, we've decided to consolidate the blogs into a single, super-duper, extra-strength site, which provides all wit and wisdom of our blogs in one convenient package.

Sure, this helps keep things simple for us, but it also simplifies things for you! Now you only have one blog to visit instead of three--and you'll still get all the information you've come to expect.

So, without further ado, allow us to introduce our new blog: Get the Most from Notes (http://www.getthemostfromnotes.com). We chose the name because we want to help you do just that!

As always, you can join us as we chat about industry news, happenings and events, and we'll give you the scoop on what's new at Teamstudio. Of course, we'll continue to provide tool tips and ideas on how to bring order to your Notes environment (not that your environment is in any way disorderly, mind you). We'll keep you posted on the athletic and adventurous endeavors of the braver members of our team, and, from time to time, we'll even wax philosophical about vampires vs. werewolves (well, maybe not--but you get the idea!).

So check out our new digs and come back to visit often! As always, we want to hear what you think, and your comments and questions are most welcome.
]]> Tue, 23 Feb 2010 17:54:33 +0000 0 General Want to prove you're not reading your users' email? http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/KFRA-7UFNKY Karen Frasca http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/KFRA-7UFNKY http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/KFRA-7UFNKY Usage Monitor is a great tool for tracking database activity.  But this means it can also be used to prove lack of activity.  Usage Monitor uses a top down filter scheme to determine what to watch.  So the configuration shown below says to ignore anything I do to my own mail file, because I am supposed to be reading that.  It also says to ignore anything any of the admins do in the tech Support mail file, because we are also supposed to be reading that.  The last entry says for all other mail databases, track what admins do in these files.  An empty log file will show that there was no unauthorized access of your users mail files.  Note that you would need to add a specific reference for every member of the admin team to ignore activity to their own mail file.
(  read more...)

A picture named M2

As a side note, the order is important.  If the last entry was first, it would take precedence when you accessed your own mail file.   ]]> Thu, 30 Jul 2009 17:32:39 +0000 0 Watch all Db's with Snapper (the easy way) http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7TWLL6 John Coolidge http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7TWLL6 http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7TWLL6 Quick tip allowing you to automatically watch all the db's you are working on in snapper.

In the database path just put an Asterisk (*). This will watch all design change saves in Domino  Designer
]]> Mon, 13 Jul 2009 15:50:34 +0000 0 Snapper Hot News Teamstudio Releases Edition 24B http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7SAHPE John Coolidge http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7SAHPE http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7SAHPE here
]]> Fri, 22 May 2009 13:22:10 +0000 0 General Running Teamstudio tools outside the Notes Client advanced http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7PESAN John Coolidge http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7PESAN http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7PESAN Running Teamstudio tools outside the Notes Client I showed you how to run our client tools outside the Notes Client.

Lets take it up a notch read more...


How would you like to have a shortcut in the quick launch bar, desktop, Etc to launch our tool into a specified Lotus Notes database? It actually is very simple. Using the following syntax, change the path in you new shortcut to the text shown below:
For CIAO! use C:\lotus\notes\nciao.exe "Servername/domain!!dbpath" For Configurator use C:\lotus\notes\nconfy.exe "Servername/domain!!dbpath" For analyzer use C:\lotus\notes\ndean.exe "Servername/domain!!dbpath" For Design Manger use C:\lotus\notes\nlibr.exe "Servername/domain!!dbpath" For delta use C:\lotus\notes\ndelta.exe "Servername/domain!!dbpath"

Obviously change your path to point to the directory the files are in and replace the path with the db you want to open with our tool.
You can run multiple occurrences of each tool simultaneously, but be mindful of the performance load to your pc
This tip comes from a combination of people.
Chad Schelfhout who created smarticon code for running our tools and
Ahren Niles who wrote a db specific version. Thanks Guys. Keep the tips coming ]]> Thu, 19 Feb 2009 20:42:33 +0000 2 Analyzer CIAO Configurator Delta Finding the right version to roll back to http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7NPPRP John Coolidge http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7NPPRP http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7NPPRP So the really cool code idea you had did not work so well. Well here comes CIAO to the rescue.. But wait so many versions to choose from, what do I do
(  read more...)
Open you CIAO! client and select the element in question

A picture named M2

Double Click the element or right click and choose show history
Select two versions to compare,, your current and a previous.
A picture named M3

Click on Delta you will get a window summarizing differences.
A picture named M4

You see here that some things changed (Represented by the red x icon) and some things were added (Represented by the green arrow icon)
By double clicking on the form name in the window you can get a visual representation of the changes, if possible.
A picture named M5
You then can decide what version to rollback to. Highlight it and click on rollback. You now have the version you wanted.
 The next tip will explain the various options in the CIAO based Delta window.

]]> Tue, 27 Jan 2009 18:33:00 +0000 0 CIAO Sneak Peek Analyzer template preview http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JKIY-7NCLRC John Kingsley http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JKIY-7NCLRC http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JKIY-7NCLRC At our last Tool Time presentation, I showed some new views that are going to be part of the next release.  There is also a hidden view that allows some of the advanced filters I demonstrated.  Here is that template.  Note that this has not been signed by a typical ID, and it has a different file name from the template released with Analyzer (to allow roll back if necessary), and it claims to be the same template name as the regular template.  You should sign and rename as appropriate for your situation.  And needless to say, this sneak peek version is not the supported release version, but feel free to contact me with questions.

]]> Fri, 16 Jan 2009 15:58:56 +0000 0 Analyzer Teamstudio Tool Time http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7N9K53 John Coolidge http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7N9K53 http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7N9K53 Starting in January we will be hosting what we hope will be a monthly on-line session to showcase 1-2 of our products. The first of these sessions will cover Analyzer and the Best Practice Filters and will be held on Thursday, January 15th at 1 PM EST using Webex Event Center.

We have added this session to our website event listing (http://www.teamstudio.com/pressroom/events-calendar.html?region=NALA#185)

Please join us for this event
]]> Tue, 13 Jan 2009 14:35:12 +0000 0 Analyzer Running agents in Build Manger; Advanced Features http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7MZMT5 John Coolidge http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7MZMT5 http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7MZMT5 Use the following two-part procedure to set up Build Manager to use the advanced features of Run Agent, including passing parameters to the agent, logging messages from agent, and confirming successful completion of an agent.
(  read more...)

If you want to pass parameters to an agent or check its status after it runs, check the
Enable additional options using agent parameter database checkbox in the Advanced
Options section.

The following advanced options appear:
– Get agent status from parameter database after agent runs
– Include messages from agent in the promotion log
– Pass parameters to agent

If you want, check the Get agent status from parameter database after agent runs.
The Fail promotion if agent does not confirm success—check if you want the database
promotion to fail if the agent does not run to completion.

If you want, check the Include messages from agent in the promotion log

Part One: set up database and signers on the target server.

1. Make sure AgentParameters.nsf is saved in the Teamstudio directory of the target
server (the server where the database containing the agent is located).

2. Make sure the ID promoting the database in Build Manager has Editors rights for
AgentParameters.nsf.

3. Make sure the signer of the targ et agent has Editor rights for AgentParameters.nsf.

Part Two: include the TSAgentParameters library and code to call it.

1. Copy the TSAgentParameters script library from AgentParameters.nsf.

2. Use your custom code to call the methods exposed by the global object
TSAgentParameters. For more detailed documentation of these method s, view the
script libraries source code, especially the “TSAgentParameterMgr” class.

The following code fragments illustrate common operations:
Include the library, in the options section:
A picture named M2

Check that the TSAgentParameter object was created. Build Manager always passes
NoteID. If you call the agent without this parameter, no object is created:
A picture named M3

Check if it registered error, for example, if it couldn’t find the document or the parameter db:
A picture named M4

Get a single parameter by name

A picture named M5

Get all parameter names as an array

A picture named M6

Log a message to the parameter db:

A picture named M7

Mark status complete. This is what lets Build Manager know if the agent completed successfully:
 A picture named M8

Copying the underlying parameter item to a new document

A picture named M9

A complete example:

A picture named M10
]]> Mon, 05 Jan 2009 16:52:55 +0000 0 Build Manager CIAO make version not working? http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7M5K3Y John Coolidge http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7M5K3Y http://tooltips.teamstudio.com/tooltips.nsf/d6plinks/JCOE-7M5K3Y While running the make version in CIAO you get the following error: You are not authorized to perform that operation.
This will aid in troubleshooting the error (  read more...)

This document will show you how to find hidden design elements causing issues making a version in CIAO

In my example db I have 4 views. I have hidden one based on a role named “Hide”
I do not have that role so I only see three views. Now, for this exercise, assume you don’t know about the hidden design element.

A picture named M2

While running the make version in CIAO you get the following error:

A picture named M3

Followed by

A picture named M4

Discovering the hidden design element can be challenging, but it is possible. To discover a design element you cannot access you should perform the following steps:
1.        Enable Client Debugging,
2.        Put the following in your Notes client’s notes.ini
a.        Console_LogLevel=2
b.        LOG_SESSIONS=1
c.        LOG_CONNECTIONS=1
d.        TCP_DEBUG_ALL=1
e.        CLIENT_CLOCK=1
f.        CONSOLE_LOG_ENABLED=1
g.        DEBUG_CONSOLE=1
3.        Restart your Notes client.
4.        You will see a console window open up with your Note Client. Run your make version step with this window open.
5.        When you get the error referenced above look at the logging console. It should contain data similar to this:

A picture named M5

6.        The line ending with “(You are not authorized to perform that operation)” indicates the offending (i.e. hidden) design element, and the element is identified by its NOTE_ID.

Now that you know the NOTE_ID of the hidden design element, how do you find and obtain access to it? The instructions for accomplishing this are as follows:

NOTE: Before beginning these next steps, you’ll need to work with someone who has been granted “Full Access Admin” rights, or you need to work with your Domino Administrator and obtain these rights for yourself.

You will also need to obtain a small, free tool known as Notespeek. Notespeek allows you to look at the “insides” of a Notes database – think of it as a “code x-ray” for Notes. You can obtain a copy of Notespeek from here:
http://www-01.ibm.com/support/docview.wss?uid=swg24005686

1.        Click on the top left corner of the log window and chose edit/mark:

A picture named M6

2.        Highlight the NOTEID contained on the error line and choose Edit/Copy. The NoteID begins with the letters “NT”, as shown below:

A picture named M7

3.        Open Notespeek and navigate to the problem database:

A picture named M8

4.        Choose Data/Open Note…

A picture named M9

5.        Enter in the NOTEID you copied from the previous step, and click ok:

A picture named M10

6.        You now see it found view 3, which is the “hidden” view. Look at the entry for the $Readers item and you will find the listing (“[Hide]”) causing the issue.


A picture named M11


Now that you know the role needed to access the hidden element, you can have your name added to this role in the database’s Access Control List (ACL). Once you’re in the [Hide] role for this database, you’ll be able to access the design element, and the publish action should work as well. ]]> Mon, 08 Dec 2008 14:33:29 +0000 1 CIAO