Appendix E       Stability of MQ Interfaces


MQ uses many interfaces, that might be of use to administrators for automating administration tasks. Table E-1 classifies these interfaces according to how stable they are, that is, how unlikely they are to change in subsequent versions of the product. The classification scheme is described in Table E-2.

Table E-1    Stability of MQ 3.0 Interfaces 

Interface	Classification
imqbrokerd command line interface	Evolving
imqadmin command line interface	Unstable
imqcmd command line interface	Evolving
imqdbmgr command line interface	Unstable
imqkeytool command line interface	Evolving
imqobjmgr command line interface	Evolving
imqusermgr command line interface	Unstable
Output from imqbrokerd, imqadmin, imqcmd, imqdbmgr, imqkeytool, imqobjmgr, imqusermgr	Unstable
imqobjmgr command file	Evolving
imqbrokerd command	Stable
imqadmin command	Unstable
imqcmd command	Stable
imqdbmgr command	Unstable
imqkeytool command	Stable
imqobjmgr command	Stable
imqusermgr command	Unstable
JMS API (javax.jms)	Standard
JAXM API (javax.xml)	Standard
Administered Object API (com.sun.messaging)	Evolving
imq.jar location and name	Stable
jms.jar location and name	Evolving
imqbroker.jar location and name	Private
imqutil.jar location and name	Private
imqadmin.jar location and name	Private
imqservlet.jar location and name	Evolving
imqhttp.war location and name	Evolving
imqhttps.war location and name	Evolving
imqxm.jar location and name	Evolving
jaxm-api.jar location and name	Evolving
saaj-api.jar location and name	Evolving
activation.jar location and name	Evolving
mail.jar location and name	Private
dom4j.jar location and name	Private
fscontext.jar location and name	Unstable
providerutil.jar location and name	Unstable
Broker log file location and content format	Unstable
passfile	Unstable
accesscontrol.properties	Unstable

Table E-2    Interface Stability Classification Scheme 

Classification	Description
Private	Not for direct use by customers. May change or be removed in any release.
Evolving	For use by customers. Subject to incompatible change at a major (e.g. 3.0, 4.0) or minor (e.g. 3.1, 3.2) release. The changes will be made carefully and slowly. Reasonable efforts will be made to ensure that all changes are compatible but that is not guaranteed.
Stable	For use by customers. Subject to incompatible change at a major (e.g 3.0, 4.0) release only.
Standard	For use by customers. These interfaces are defined by a formal standard, and controlled by a standards organization. Incompatible changes to these interfaces are rare.
Unstable	For use by customers. Subject to incompatible change at a major (e.g. 3.0, 4.0) or minor (e.g. 3.1, 3.2) release. Customers are advised that these interfaces may be removed or changed substantially and in an incompatible way in a future release. It is recommended to customer to not create explicit dependencies on unstable interfaces.