In order to use the rich sets of tool provided by Seeburger, it provides an additional Front-end for configuration and monitoring of Seeburger message flows. The various features of available with Seeburger Workbench are mentioned below:
If "SeeXIExtendedTools.sca" is properly deployed on the Adapter Engine of PI, then the Seeburger Workbench could be accessed using the following URL
http://<XIhost>:<port>/seeburger
where Port refers to the HTTP Port of J2EE.
This is how the main screen of Seeburger Workbench can be seen where authentication could be done using PI username and password. The screen shown below may be a bit different at based on versions of installed sca files.
The biref description of these components are as follows:
Addressbooks: This provides an alias to the long mailbox addresses for using it comfortably in PI
http://scn.sap.com/people/prateek.srivastava3/blog/2009/08/05/seeburger-part-3-addressbooks
Digital Signature: The security related settings could be done using the Signature option for your specific Business partners. These partners needs to be maintained individually at this option along with the list of Accepted Signers. However, this is not always used when all security settings are handled at PI.
Message Monitor: This option is used to monitor all the EDI messages that flow through Seeburger Adapters. The monitoring could be done specific to various adapters installed.
http://scn.sap.com/people/prateek.srivastava3/blog/2009/08/05/seeburger-part-4-message-monitor
Message Splitter: Splitter is used for splitting the EDI Interchange (EDI files containing several types of Business Documents) into individual EDI files. Although this is not the only feature available with the Splitter module.
Message Tracking: Seeburger Message tracking is a tool more for a Business consultant to look for the message based on Functional terms. e.g. Payload search based on Sales Order number.
Recovery Monitor: There are times when Seeburger adapters are unable to deliver messages to their required destination due to various reasons and these messages are stuck within Seeburger. These messages could then be recovered using this recovery monitor.
http://scn.sap.com/people/prateek.srivastava3/blog/2009/08/05/seeburger--part-5--message-recovery
Resource Management: This option helps in configuration and monitoring of resources for those Seeburger set of adapters which requires such allocations for a short span of time.
e.g. X400|# adapters requires this allocation only for polling duration. Or ISDN protocol based adapters. This option is however not mandatory for all the cases.
Mapping Variables: This interesting feature diminishes the standard mapping limitation with PI about storing a global variable to be used across the mappings. This option allows configuring some permanent variables to be used across the mappings. E.g. Some global counters.
Property Store: Although not a very crucial component, Property Store has to be used in some cases. E.g if Seeburger functions are used, then this entry must be present. Other usage could be related to some Message Tracking related entries. 
System Status: This option is only available with versions >= 1.8.x. This option could be used to check the adapters installed currently, active threads and also the mappings available (both mappings_sys and mappings_user).
Apart from these, there are certain features like Message Archiving that requires separate Front End installation to be used further.