Asset Suite / PassPortGeek

Based on Ventyx putting much of the logic in Java and Ventyx jar files as opposed to using WebMethods, er... methods, IBD appears to have been intended to run with multiple integration products; WebMethods, WebLogic, etc. When customizing, it's understandable if the developer wants to use straight WebMethods for maintaining the pipe and limiting the Java to interfaces with PassPort / Asset Suite.

In general the interfacing between PassPort / Asset Suite and BD is "throw it over the wall". By this it's meant that PP/AS will finish its work, by for example writing a Purchase Order in "Indus XML" to table TIDPPXML, commit it to the database and its done with it. BuyDemand periodically looks for, or "polls", Purchase Orders in TIDPPXML, reads them out and deletes them from TIDPPXML.

In a similar manner, BD processes a shopping cart by writing it to TIDCATMP and committing it to the database. The closing of the child web browser running BD, which was initially launched on the I010 panel and invoked BD running on WebMethods, returns control to program tigi010.ccp which recognizes that a return from a URL has occurred (don't know if more than 1 URL icon on a panel would work), does some checking and calls tigmrbak.csm. Tigmrbak.csm processes the shopping cart off of TIDCATMP and into the current Material Request.

Working with BuyDemand and WebMethods