Skip to Content

Seeburger – Part 2 – Seeburger Workbench

Before reaching here, I hope you are clear about the Basics of Seeburger Adapter suite or else please refer this (Seeburger – Part 1 – The Basics). 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. I will hereby briefly discuss features of various options available in Seeburger Workbench. *Addressbooks: *This provides an alias to the long mailbox addresses for using it comfortably in PI

[Seeburger – Part 3 – Addressbooks | 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.

[Seeburger – Part 4 – Message Monitor | 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.

[Seeburger – Part 6 – Classify & Split Secret | Seeburger – Part 6 – Classify & Split Secret]

*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.

[Seeburger – Part 5 – Message Recovery | 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.


You must be Logged on to comment or reply to a post.
  • Hi prateek,
               I like to add a new feature of the seeburger with version 1.8.x that thera is an option called systemStatus where you can check the adapters installed currently ,active threads and also the mappings available (both sys and user mappings)..I felt that the mapping feature provided was very useful to find out the deployment of was successfull or not


    • Indeed Rajesh! Thanks for giving this information. I have some idea about various possible things in Seeburger Workbench. Thats the reason towards end of the blog I have mentioned
      “The information here would be updated based on more input from community and the functionalities I may come across”
      For now, I will add this to the blog.

      Best regards,

  • Prateek,

    To add a point here,property store parameters needn’t be used in each n every case whenever Seeburger functions have been used. However, its mandatory to configure when J2EE server is using port other than 50000.

    Anoop Garg