Here are a few comments/observations on the new 9x versions of webmethods ,based on recent upgrade experience.Please add your own as comments or if you see a better way of doing it.
1. Designer-Since webmethods has deprecated Developer(RIP old friend) totally ,anyone who moved directly from developer to designer in 9x directly may see themselves hopelessly disoriented.(Unless you had the foresight to switch to Designer from 8x itself) Here are a few Designer related observations/Tips Arrange your designer windows to mimic the erstwhile Developer to minimize heartburn. This is especially useful while debugging where the default designer windows can really have you pulling out your hair(In my case ,teeth ,since I have precious little hair left) There is no "Trace to Here" feature in Designer .However we can use the base eclipse breakpoint feature to trace code Set up breakpoints by doubleclicking on the extreme left of the code line(The breakpoint will display as a red dot) Use the F8 shortcut to trace to a preset breakpoint See attachments for screenshots 2. IS instances-We can now spin up as many instances of integration server as we want without having to install the whole shebang from the start. This is especially useful while patching the environment. Since all our components like IS ,MWS and Broker can now reside in one root folder with common shared components. The only component where they have not provided this feature is OFP where we have to install an OFP for each IS separately. Hopefully next release will fix this. 3. Resubmit button for Process instance-This is one thing that SAG messed up with in 98.There is no multi resubmit button for Process Models. Now each resubmit needs to be done from within the instances ,Meaning more clicks and wastage of time and support costs when we have to resubmit process instances in bulk. Hopefully SAG will add this in future releases. Maybe we can all put in a feature requests to include that again so that SAG sits up and listens Till then, we probably have to write a service to resubmit Process instances in bulk and possibly write a CAF front end for it 4. SFTP Support: With 9x ,webMethods has provided supporting services for sftp operations, which is neat. It uses jsch apis to do its business(which we were already using with custom java services to connect to sftp clients).Nevertheless its good to have out of the box services provided by SAG for SFTP. The implementation involves setting up of aliases for the sftp server and users,which is nice as we can verify the credentials are working beforehand rather than waiting for an integration to fail. What's missing ,however, is the ability to create sftp ports so that external clients can connect to webMethods. Probably enough feature requests to SAG can move them to add it in the next iteration. 5. Trust Store for Enterprise Profile in TN-We can no longer simply add certificates and Private keys to our enterprise profile. Now we need to configure a trust store and configure it in the Enterprise Profile Certificate tab. However if you use the Database migration utility ,It automatically migrates all the certificates in the Enterprise Profile and the subsequent behavior is like any other profile. 6. Terracotta-The Jury is still out on the verdict on Terracotta. From what ive seen it’s a bit of extra work to set up the terracotta servers, however once I got the hang of it and its future possibilities ,it sort of grew on me. Heap space was one off the biggest limiting factors while writing and designing integrations in webMethods in the past. We used to write elaborate logic to keep the memory utilization low or risk crashing the server. With Terracotta taking giving us the capability to handle higher heaps outside the IS wtithout risking its integrity ,gives us the flexibility to dumb down our integrations and deal with Volume purely at the Administration level. Also this opens the gate for future big data endeavors. But its too soon to say as there may be a few kinks they might need to smooth out before its smooth sailing. 7. Universal Messaging-With Broker going out of support in 2020,nows the time to start evaluating UM and formulating a plan for implementation. The 9.9 readme mentions something about a direct movement from Broker to UM, but cannot comment as I haven't tried it. But UM has license cost so this might be the best time to evaluate if you want to stick to SAG or get a cheaper messaging solution.