FYI:
Check out this website:
http://www.objectmentor.com/home

The published article section is a real treasure trove!
http://www.objectmentor.com/resources/articleIndex

Robert Martin ( or Uncle Bob as he likes to be called )
has a great series of monthly articles called the Craftsman:
http://www.objectmentor.com/resources/listArticles?key=author&author=Robert%20C.%20Martin

Read at least the first article ( more like a short programmers story ), The Craftsman #1 Opening Disaster.:
"I was delighted to be accepted as Mr. C’s apprentice. But despite high hopes, my first attempt at coding for the master developer quickly hacked my hubris down to size. Would I make it? "

Back to the problem at hand.
I suggest at startup the goApp or other code create and populate a "Settings" object. Then each of your BizObjects can Get any information that they need from the "Settings" object. In fact if you have a superclass of your application bizobjects you can have the superclass do the loading. In the majority of the methods of the bizobj do not reference the setting object, just do this at the Init of the bizObj. Why? Well one reason is in the init process the code can look for the existance of the setting object and if it exists read the 'defaults' from there. If it does not exists, it could be created etc. or have default testing values be added to a class attribute. If the bizobjects directly interface to the settings object and you want to be able to test etc w/o the existance of the setting object code to handle that situation will have to be repeated threw out the class methods.

I'm hoping that a MM experrt will step in and explain that "all we need to do is..."

Anthony