Valid SAF Elements for JMS SAF Client Configurations

Reliably Sending Messages Using the JMS SAF Client 7-5

7.2.1.4 Valid SAF Elements for JMS SAF Client Configurations

The weblogic-client-jms root element of the weblogic-jms.xsd schema contains several top-level elements that correspond to server-side WebLogic JMS SAF features. Table 7–2 identifies the management MBean to which each top-level element in the schema corresponds. All of the properties in these management MBeans work the same in the JMS SAF client implementation as they do in server-side SAF JMS configurations, except for those described in the following tables. Table 7–3 describes the differences between the standard SAFAgentMBean fields and the fields in the JMS SAF client configuration file. Table 7–2 weblogic-client-saf Elements weblogic-client-jms Element WebLogic Server Management Bean connection-factory JMSConnectionFactoryBean saf-agent SAFAgentMBean saf-imported-destinations SAFImportedDestinationsBean saf-remote-context SAFRemoteContextBean saf-error-handling SAFErrorHandlingBean persistent-store For more information, see Section 7.2.1.5, Default Store Options for JMS SAF Clients. Note: You can only specify one persistent-store and saf-agent element in a JMS SAF client configuration file. Table 7–3 Modified SAFAgentMBean Fields Server-side SAF Fields Difference in JMS SAF Client Configuration File PersistentStore Not available. There is only one persistent store defined. ServiceType Not available. This can only be a sending agent. BytesThresholdHigh Threshold properties are not available. BytesThresholdLow Threshold properties are not available. MessagesThresholdHigh Threshold properties are not available. MessagesThresholdLow Threshold properties are not available. ConversationIdleTimeMaximum Not available. This field is only valid for receiving messages. AcknowledgeInterval Not available. Only valid for receiving messages. IncomingPausedAtStartup Not available. No way to un-pause; same effect achieved by not setting the JMS SAF client property. ForwardingPausedAtStartup Not available. No way to un-pause; same effect achieved by not setting the JMS SAF client property. ReceivingPausedAtStartup Not available. No way to un-pause; same effect achieved by not setting the JMS SAF client property. 7-6 Programming Stand-alone Clients for Oracle WebLogic Server Table 7–4 describes the differences between the standard JMSConnectionFactoryBean fields and the fields in the JMS SAF client configuration file. Table 7–5 describes the differences between the standard SAFImportedDestinationsBean fields and the fields in the JMS SAF client configuration file.

7.2.1.5 Default Store Options for JMS SAF Clients