Article Categories
- All Categories
-
Data Structure
-
Networking
-
RDBMS
-
Operating System
-
Java
-
MS Excel
-
iOS
-
HTML
-
CSS
-
Android
-
Python
-
C Programming
-
C++
-
C#
-
MongoDB
-
MySQL
-
Javascript
-
PHP
-
Economics & Finance
SAP PI messaging service is JMS compliant or not
SAP PI (Process Integration) messaging service is JMS compliant. SAP PI Messaging Server 7.4 AEX is compatible with JMS 1.02 and JMS 1.1 specifications. Using Java Messaging Service, you can connect external messaging systems to the Integration Engine.
JMS Compliance in SAP PI
SAP PI supports JMS through dedicated adapters that enable integration with JMS-compliant messaging systems. This compliance allows SAP PI to communicate with various enterprise messaging platforms using standard JMS protocols.
Key Features
- Compatible with JMS 1.02 and JMS 1.1 specifications
- Supports JMS message properties transfer
- Enables routing, mapping, and BPE operations
- Works with both sender and receiver JMS channels
JMS Message Properties
SAP PI provides a feature called XI adapter-specific message properties that allows additional adapter information to be attached to XI messages. This feature enables JMS message properties to be transferred and processed within SAP PI ?
Supported Message Properties
The JMS adapter supports up to 10 JMS message properties that can be copied into XI message properties with names DCJMSMessageProperty0 to DCJMSMessageProperty9.
Data Type Support
JMS message properties support the following data types ?
- boolean
- byte, short, int, long
- float, double
- String
These values are normalized to strings when converted to XI message properties at the sender JMS channel. In the receiver JMS channel, you can configure specific types to coerce the normalized properties back to their original types.
Configuration Requirements
JMS message properties transfer is available from XI 3.0 support pack 18 onwards. The configuration involves ?
- Sender JMS Channel: Copy JMS message properties into XI adapter-specific message properties
- Receiver JMS Channel: Copy XI adapter-specific message properties back into JMS message properties
Important Limitations
Transfer of custom JMS message properties is only supported for JMS compliant messages. This feature will not work for WebSphere MQ in legacy mode, as it doesn't follow JMS compliance standards.
Legacy Support
Between support pack 14 to 18, the JMS adapter had limited support for only two JMS string properties (DCJMSStringProperty1 and DCJMSStringProperty2). This approach is now deprecated in favor of the enhanced message properties support.
Conclusion
SAP PI messaging service is fully JMS compliant, supporting JMS 1.02 and 1.1 specifications. This compliance enables seamless integration with JMS-based messaging systems and supports comprehensive message property handling for enterprise integration scenarios.
