Best Practices

HCL Domino Domino Forum
1

Hi:

I’m looking for recommendations on how to handle a client application which spans multiple .nsfs.

There are agents that copy and update documents from one .nsf to another. I’m about to move it to production and am wondering about the use of a profile document to hold the paths to the various applications to make deployment from test to production easier? Would this be the proper way to handle these references or is there a better, more straightforward method in 9.x? As well, there are embedded views between the applications. Is there anyway I can handle these so that they work seamlessly in testing as well as in production without having to go in and update their reference points each and every time?

Apologies if these questions are lame but I’ve been working on my own in Notes for the past 13 years and am hoping there’s a better way to handle these configuration type things that I’ve missed along the way.

Thanks

Is.

2

Subject: I use profiles pervasively for this.

Set up the profile defaults so when you create the profile, it points reasonably well to where you intend the other database to go.

I remember doing some things from outlines because you could similarly program the server / database to retrieve the proper information from there, and you wouldn’t be redesigning on every deployment.

I know there are some ways to embed views that won’t let you do the simple @function programming to specify them. And I’ve avoided them in my designs, because they don’t handle loose coupling like what you’re looking for.

3

Subject: Best Practices

Thanks for your input - the profile doc situation is as I suspected, the embedded view situation may cause a bit of pain, but I’ll try to minimize usage.

thanks

Is.