Hi Berin, > >>Instrument is broken up into three packages. > >> > >>Instrument (AKA Instrument Client) is used for your > >>components to define > >>the "instrument points", or the values you are exposing to > the outside > >>world. > >> > >>Instrument Manager is used internally with Fortress so that you can > >>expose those instrumenation points outside the JVM. To do > that, just > >>adjust the "instrument" configuration file in the connectors > >>like this: > >> <connectors> > >> <connector class="altrmi" port="15555"/> > >> </connectors> > >>If you don't want to expost that port, just comment out the > connector. > > > > > > OK, do I have to put this as child in the xconf or is there > a separate > > config file? If I use this, I must also have the AltRMI > archives added > > somewhere in the classpath for my webapp (works currently > without)? For > > Merlin I saw in a config file an entry for the host .. do I > have to config > > this now, too? > > The Swing example in the FOrtress archive has an example instrument > configuration file. It will show you how to make it work. > > The Fortress Complete JAR currently incorporates all the AltRMI JAR > files. Instrument will work without the AltRMI archives very well. > The only caveat is that the client has to be in the same JVM.
just to get an impression I started the Swing example ... COOL ... I liked it :) Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
