Broker provides Java and C APIs. These are documented in Programmer’s Guides and Javadoc which can be found in the _documentation/Broker_and_JMS directory of a 7.1 installation.
The Broker Administrator’s Guide identifies how document types can be created. These include using Developer, the Broker admin client API (more on this below), or My webMethods by adding a JMS topic as a Broker document type.
The Broker admin client API defines a class named BrokerAdminTypeDef. This class provides methods to create, modify or destroy document types (the documentation still uses “event” which was the term used for “document” in previous versions). This would be the class to use to define document types on Broker.
In refreshing my understanding (it’s been a while since I’ve coded anything against Broker directly) I found that the Javadoc indicates that BrokerAdminTypeDef is deprecated but does not identify a replacement (nor could I find a class that looked like it was a replacement). The Broker Java Administration Programmer’s Guide for 7.1 has “Manageing Broker Event Types” as chapter 1, which seems really odd. In the 6.5.2 guide it was chapter 4, after overview, broker server/broker, and broker client chapters.
My guess is that the plan was to deprecate BrokerAdminTypeDef but they decided to back off of that for some reason and didn’t update the Javadoc. It seems that BrokerAdminTypeDef may disappear, possibly in favor of JMS equivalents. But that’s pure speculation.
That’s probably more info than you were looking for. Is there a reason that you don’t want to use Developer to create type defs? Unless you’re using Broker without IS at all, you’ll probably need the type defs on IS at some point.
#Flow-and-Java-services#webMethods#Integration-Server-and-ESB