Tables
- Platforms and connection modes
- WebSphere MQ Java installation directories
- Samples directories
- CLASSPATH setting to run WebSphere MQ base Java applications, including the WebSphere MQ base Java sample applications
- CLASSPATH setting to run WebSphere MQ JMS applications, including the WebSphere MQ JMS sample applications
- The location of the WebSphere MQ Java libraries for each platform
- Administration verbs
- Syntax and description of commands used to manipulate subcontexts
- The JMS object types that are handled by the administration tool
- Syntax and description of commands used to manipulate administered objects
- Property names and valid values
- The valid combinations of property and object type
- Property names for queue and topic URIs
- Symbolic values for queue properties
- The JMS 1.1 domain independent interfaces
- Possible values for NameValueCCSID field
- MQRFH2 folders and properties used by JMS
- Property data types
- JMS header fields mapping to MQMD fields
- JMS properties mapping to MQMD fields
- JMS provider specific properties mapping to MQMD fields
- Outgoing message field mapping
- Outgoing message JMS property mapping
- Outgoing message JMS provider specific property mapping
- Incoming message JMS header field mapping
- Incoming message property mapping
- Incoming message provider specific JMS property mapping
- Load1 parameters and defaults
- ASFClient1 parameters and defaults
- TopicLoad parameters and defaults
- ASFClient3 parameters and defaults
- Comparison of representations of property values within the administration tool and within applications
- Utilities supplied with WebSphere MQ classes for Java Message Service
- CipherSpecs supported by WebSphere MQ and their equivalent CipherSuites