Configuration
Once you have created the xml plugin on the interface
you require it on, you can then select it from the plugins
panel for the selected interface and enter values as
you wish for the configuration parameters.
The xml plugin requires configuration information relating
its behavior as well as the entry point in the namespace
for the channels you wish to make avilable to vend to
the clients. Below is a table that shows each configuration
parameter and describes what it is used for.
Parameter Name |
Description |
Default Value |
| ChannelRoot |
Name of the channel or folder to render. |
/ |
|
Security Realm |
Name of the authentication realm |
None. |
| StyleSheet |
Name of the style sheet file to use to process
the resulting XML. |
None. |
| UserFile |
Name of the file containing the usernames and
passwords |
None. |
The image below shows the enterprise manager interface
panel with an nhp interface running on port 8080. This
interface has a XML Plugin configured with the my-Channels xml2html stylesheet and it's URL path as /xml. The default
ChannelRoot setting is /, which is the root of the namespace,
i.e. all channels. Once the plugin is created, you can
hit the apply button which will restart the interface
and enable the new xml plugin.

From a browser, it is now possible to enter the url
'http://localhost:8080/xml/' which will render
the realm information page using the stylesheet. The
image below demonstrates the browser view from a Realm
that has an xml plugin on an nhp interface on port 8080.
The realm information is displayed at the top of the
page, and the information on channels and queues is
shown beneath. The stylesheet 'xml2html.xsl' that renders
this within the browser is supplied with the download
under the <server>/plugins/htdocs/style directory
and can be modified as you wish.

As you can see above, each channel or queue is shown
as a link within a table showing the informaiton obtainable
from the XML plugin. Clicking on a channel link, will
then take you to another page that has been rendered
by the xml plugin which will show you the list of events
on a channel. The image below shows the event list for
the JNDI naming channel.

The xml plugin will determine whether the events on
the channel contain byte data, dictionaries or XML documents
and return the relevant elements within the xml document.
The stylesheet applied to the xml document then examines
each element to find out how to render it within the
browser. Each event on the channel or queue is shown
in the table with event id, it's size in bytes and links
to either the byte data, the dictionary or the xml data.
These links are generated by the stylesheet. Clicking
on the data or dictionary links will again return an
xml document from the xml plugin that will be rendered
to either show the base64 encoded event data, or the
event dictionary.
If any events contain xml documents, these will be
returned directly from the xml plugin. The stylesheet
provided will not render event xml documents, since
the structure of these is unknown. You will need to
provide your own style sheet to render your own xml
event documents. |