1. NiXS 4.0 – Overview NiXS-message NiXSMessage NiXSDocType: Enum ( Request, Response, Acceptance, Exception); NiXSDocVersion: String NiXSDoc: String BizDoc: String Attachment ContentType: String ContentId: String Content: Binary ContentName: String Type MessageType : (Enum: RvCM/AE, JMS, WDSL); Är av en 0..* 1 New features in 4.0 The NiXS-specification can know be used for messaging between business systems in a B2B- messaging scenario, not only between a business system and a B2B-server. NiXS 3.0 only supported message type RVCM/AE. NiXS 4.0 is extended to support other messagetypes. The NiXS-specification will be divided into several documents (a logic specification and a binding to each message type supported. The attribute NiXSDocVersion is moved from NiXSDoc to NiXSMessage.

2. NiXSDoc TimeStamp: TimeStamp ConversationId: String TransactionId: String MessageId: String Request TransactionName: String BizDocName: String BizDocVersion: String Exception ExceptionType: String OriginalMessageId: String Reason ErrorSpecification: String Error: String 1..* ErrorArgument Name: String Value: String 0..* Response BizDocName: String BizDocVersion: String Acceptance OriginalMessageId: String Type AcceptanceType: Enum ( MessageReceived, BusinessMessageTransfered, BusinessMessageValidated, BusinessMessageAccepted) 1 New features in 4.0 MessageTypes AcceptanceException and TransactionSuceeded is replaced by a generic accptance message that could be of one of the types (MessageReceived, BusinessMessageTransfered, BusinessMessageValidated, BusinessMessageAccepted). ConversationTimeToLive is a new attribute introduced in NiXSDoc. The value is set by the application initiating the conversation. ConversationSetup is a new element in the RequestDoc. If the request is the first request in a conversation, the element MUST be present. If the request doesn’t initiate the conversation the element SHOULD NOT be present. All attributs in the ConversationSetup element are mandatory. In 4.0 all message types MUST contain a MessageId. ConversationSetup ConversationTimeToLive: Timestamp BPA: String FromActor: String IsLegallyBinding: String FromRole: String CounterPartyId: String CollaborationName: String 0..1

3. Business System B2B Server B2B Server Business System Request MSHAck/Error ebMS Header validation MessageReceived/Exception NiXS header validation Busiiness Process and payload syntax validation ReceiptAck/ ReceiptException Request BusinessMessageValidated/Exception BusinessMessageTransfered/Exception Validation of business rules AcceotanceAck/ AcceptanceException BusinessMessageAccepted/Exception Response NiXS Header validation Response MSHAck/Error ebMS Header validation Busiiness Process and payload syntax validation ReceiptAck/ ReceiptException Validation of business rules AcceotanceAck/ AcceptaneException Business Messaging Diagram (Transaction) MessageReceived/Exception BusinessMessageTransfered/Exception BusinessMessageValidated/Exception BusinessMessageAccepted/Exception

4. Request MSHAck/Error ebMS Header validation MessageReceived/Exception NiXS header validation Busiiness Process and payload syntax validation ReceiptAck/ ReceiptException Request BusinessMessageValidated/Exception BusinessMessageTransfered/Exception Validation of business rules AcceotanceAck/ AcceptanceException BusinessMessageAccepted/ExceptionResponse NiXS Header validation Response MSHAck/Error ebMS Header validation Busiiness Process and payload syntax validation ReceiptAck/ ReceiptException Validation of business rules AcceotanceAck/ AcceptanceException Business Messaging Diagram for layers of backend systems (Transaction) MessageReceived/Exception BusinessMessageTransfered/Exception BusinessMessageValidated/Exception BusinessMessageAccepted/Exception Business System A Request MessageReceived/Exception Response BusinessMessageAccepted/Exception BusinessMessageTransfered/Exception BusinessMessageValidated/Exception BusinessMessageAccepted/Exception Business System B B2B Server B2B Server Business System B BusinessMessageAccepted/Exception Response Validation of business rules NOTICE! Validation of business rules can be performed by Business system B or/and C, D, E etc… Validation of other systems lower down in the hierarchy MUST be performed within System B:s validation process. This imply that System B MUST NOT send a BusinessMessageAccepted to the B2B-server, until System B has received a BusinessMessageAcceptance from all underlaying systems [e.g. System A].

5. ValidationOfBusiness rules (Details) If layers of Business Systems are collaborating, one has to consider where to perform business rule validation. It is important that (In this scenario) system A wait for BusinessMessageAccepted from all underlaying systems until it sends a BusinessMessageAccepted to the B2B- server. Notice – Underlaying systems [B,C,D] might as well use other under laying systems/services to perorms its part of the validation. In that case, the same principle should be used. System B must wait for all its underlaying systems/services to send a BusinessMessageAccepted until it sends a BusinessMessageAccepted to Business System A. Business System A Business System B Business System C Business System D Validation of business rules Response BusinessMessageAccepted/Exception Response Validation of business rules B2B Server BusinessMessageAccepted/Exception AcceptanceAcknowledgment/Exception

6. Business System B2B Server B2B Server Business System Request MSHAck/Error ebMS Header validation MessageReceived/Exception NiXS header validation Busiiness Process and payload syntax validation ReceiptAck/ ReceiptException Request BusinessMessageValidated/Exception BusinessMessageTransfered/Exception Validation of business rules AcceotanceAck/ AcceptanceException BusinessMessageAccepted/Exception Response NiXS Header validation Response MSHAck/Error ebMS Header validation Busiiness Process and payload syntax validation ReceiptAck/ ReceiptException Validation of business rules AcceotanceAck/ AcceptaneException Handling TimeOut (Transaction) MessageReceived/Exception BusinessMessageTransfered/Exception BusinessMessageValidated/Exception BusinessMessageAccepted/Exception TransactionTimeOut ReceiptTimeOut AcceptanceTimeOut

7. Business System B2B Server B2B Server Business System Request MSHAck/Error ebMS Header validation MessageReceived/Exception NiXS header validation Request Validation of business rules AcceotanceAck/ AcceptanceException BusinessMessageAccepted/Exception Response NiXS Header validation Response MSHAck/Error ebMS Header validation ReceiptAck/ ReceiptException Validation of business rules AcceotanceAck/ AcceptaneException Business Messaging Diagram (Conversation) MessageReceived/Exception BusinessMessageTransfered/Exception BusinessMessageAccepted/Exception Request Conversation Transaction

8. ConversationTimeOut New features in 4.0 ConversationTimeToLive is a new attribute introduced in NiXSDoc. The value is set by the application initiating the conversation. The ConversationTimeToLive value is mapped towards the timeToLive value in ebMS header in the public message. All messages within the same conversation instance will the use this value through the lifetime of the converstion. Any public message violating the timeToLive value should result in: The conversation should be terminated in failure. All transaction within the conversation should be terminated in failure. Exception messages should be sent to the trading partner as well as to the backend system. The B2B-server does not have to wait for a message violating the ConversationTimeToLive to initiate a Exception to the BusinessSystem. It can be proactive by performing regular comparison between the TimeToLive value of ongoing conversations and current sysdate. By doing this timed out conversations can be dedected.

9. TimeToLive (according to ebMS 2.0)

10. BPSS 1.04 Messaging Diagram