The Property Broker monitor lets you display and view the following:
- property broker events
- active actions
- active wires
- registered properties and actions
This tool is posted at the following "Lotus Sandbox" location which also explains how to install it:
The tool is launched via Debug - Show Components and Properties menu options. In the remainder of this page, you will find the following sections:
- Tracing a property
- Emulation Tab
This tool is used for a run time analysis of the property broker registry and events happening in the broker. The different tabs are dynamic and represent realtime events and data. They will all change as the environment changes around it. You can accomplish the following with this tool:
- Use the Console tab to see the different events happening in the broker.
- The Current Page tab shows the components on the current page. It shows the actions and parameters for each of the components.
- The Active Actions tab shows all active registered actions currently in the broker.
- Active Wires tab shows all of the currently enabled wires in the broker.
- The Types tab shows all of the registered types in the broker registry.
- Trace Properties with additional logging.
- Emulate action invocations.
Tracing a property
You can use the Property Broker Monitor tool to trace a property. This allows you to see errors and code paths if there are problems sending or receiving property changes. By navigating to the Active Actions tab in the PB Monitor and to an input or output parameter for an action you can right click on it and select the Trace option. This is essentially the same as doing a "pbt " from the OSGI console. The events are then published to the PB Monitor Console tab.
The emulation tab allows you to "spoof" a property change and watch it execute through the broker to receiving components. There are two ways you can emulate a property change - one, calling the action directly and two, using an active wire.
Calling the action directly
When you call an action directly, the monitor will be taking in the text value and attempt to convert it to the correct property type. Here is a screen shot with some explanation of how to call an action directly by explaining the key parts of the tab.
1. Select the "Call an action directly" option.
2. Find the action from the appropriate owner you want to call. In this case I selected the SetSelectedDate action from my Notes Calendar.
3. Type in the value you want to send to the actions input parameter (see the next bullet for a cool tip).
4. If the type of the parameter is known to the monitor it will attempt to show you the text format you must use. In this case it is an xsd:dateTime.
5. The next list of name value pairs is the information for what the source property must look like in order for the action to take in the property change.
Using an active Wire
The only difference between this option and calling the action directly is the monitor will construct the property change and send the value to the broker using the from owner ID specified in the wire. This will truly emulate execution flow of a production property change.