.NET use in webMethods Flow and Java Services

I work in a heavy .NET environment. I have migrated one of the .NET apps they use to a Java Service (a little painful), and would like to know how others are handling Flow/Java Service implementations in this environment. Depending on the company the language wars continue on what is best, but in my opinion you use what works and is handed upon you.

Can I create .NET services within SAG Designer easily as Java Services? Is the webMethods Microsoft Package a separate product which has to be purchased from the base product?

Right click on a folder in Designer, select New then select .NET Service. The docs and help describe the prerequisites for creating .NET services.

Another approach is to have the components that wM IS is going to call expose an HTTP endpoint (payload could XML, JSON, whatever) instead of having wM IS tap into low-level library components. Of course the app team may not be willing to do that so using the .NET capabilities within wM IS may be okay.

@reamon thanks for the response. I found the documentation and it looks like an add-on to the normal base product install. It is unclear if the add-on is a separate purchase or just downloading the install files. Which is more prevalent with webMethods services? Java services or is there a good portion of .NET services created in Designer?

FLOW services are the most prevalent. There should (in general) be very few Java/.NET services. Interactions with other systems should generally be via HTTP or messaging, not via libraries. Of course, there are times where using a library is needed/useful but that has become increasingly the exception over the years. Use XML or JSON over HTTP calls instead, when possible.

1 Like

Thanks for the insight. I have installed the webMethods Package for Microsoft .NET adapter. I’ll have to do some reading in order to take advantage of this feature.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.