What tools are in your webMethods Toolkit

[wMusers.Com1 (wMusers.Com)]

Customware’s Nathan Lee is on a roll. In today’s post he lists a few tools that are in his “toolkit” on every webMethods Integration Server project.

---

[b]quote:[/b]

With webMethods and creating mechanisms, I tend to find that the following “toolkit” of things are quite useful:

• an “invokeService” java service (that is: a service that takes in the pipeline and the service name you want to invoke and makes a call to invoke it) []specifications (not used that much in normal day to day stuff, but the equivalent of a java interface in webMethods… defines the inputs/outputs of a service so that you provide an implementation of a certian operation) []properties management services (to allow you to have configuration files that you change a few properties to alter the way the mechanism works) []Wrapper documents (they allow you to wrap up your payload and add metadata to the document) []Knowledge of the IData and IDataCursor and java services (in order to be able to directly play around with the pipeline, moving beyond what is capable using flow alone). [*]knowledge of the ServerAPI and Service utility objects in the webMethods API (these give you access to some of the extra stuff you need to know about what’s going on with execution)

So what tools are in your toolkit? Add your comments on Nathan’s blog.<!-/quote-!>

---

Mark

(Message edited by mcarlson on August 22, 2005)