Lots of fun. For example, let’s say you place your certs in /opt/webMethods65/Broker/certs. When you initially select a keystore and assign it to a Topic Connection Factory you would specify a remote keystore location and point to that folder. After entering the password and saving, go look at the SSLKeystore property in the wmjmsnamingcontext infoset. It will point to the location on the portal server where a copy of the cert was created (e.g. c:\webMethods65\Portal<blah>).
In my opinion, MwS is OK for the basics but when you get into some of the more obscure areas it does some very weird things such as deleting all of the pub/sub permissions or changing the broker server setting unintentionally when you edit a Topic Connection Factory (TCF)
Don’t get me wrong, I see the potential, its just that MwS for Broker and JMS has got some potentially dangerous, productivity sapping and nearly always annoying behaviors in the current release.
Start a quirky behavior list and submit it as feature requests. Hopefully, they will eventually show up in the product.
Mark
#webMethods-BPMS#webMethods#MWS-CAF-Task-Engine