After some difficulties trying to obtain details on the different possible states that a B2B message can have, I could get the following information valid for the B2B Business Message states:
MSG_COMPLETE: Business message state after completion of message transfer (and after receiving acknowledgment of the transmission in case of Ack/FA). Wire message state is moved to MSG_COMPLETE state as well.
MSG_WAIT_ACK: Business message state when an outbound message is sent to trading partner and B2B waits for Ack to be received.
MSG_ERROR: Business message state after a problem occurs in B2B or a negative acknowledgement is received from the trading partner. Wire message state is moved to
MSG_ERROR state as well.
MSG_WAIT_TRANSMIT: Business message state while B2B is sending message to trading partner. This state is also observed for the messages when they are queued in case of sequencing.
MSG_WAIT_FA: Business message state when an outbound message is sent to trading partner and B2B waits for Functional Ack to be received.
MSG_SEND_FA: Business message state when B2B is sending Functional Ack to a trading partner.
MSG_WAIT_BATCH: Business message state while messages are batched up during the interval before batch expiration. After the batch expires, the entire batch of messages are sent out, and business and wire message states move to MSG_COMPLETE (or MSG_ERROR if a problem occurs).
MSG_WAIT_STACK: Business message state when there is any transport error in case of sequencing.
MSG_WAIT_TA1: Business message state while waiting for TA1 Message for EDI-X12.
MSG_SEND_TA1: Business message state while sending TA1 Message for EDI-X12.
MSG_CONTINUE_PROCESS: Business message state when message is being processed in B2B(engine).
MSG_COLLAB_WAIT: Business message state when message is waiting for Collaboration.
MSG_PROCESS_ACK: Business message state while processing an Acknowledgement.
MSG_SEND_ACK: Business message state when an inbound message is received from trading partner and B2B is sending an Acknowledgement.
MSG_SEND_EXP: Business message state while sending an Exception message.
MSG_PROCESS_EXP: Business message state while Processing an Exception Message
MSG_INVALID: This state the default/first state when the message processing begins in B2B. This state should not be encountered while monitoring the Message states in B2B.
I'm hoping Oracle introduce this information in the official documentation and extends it to cover both wire and application messages.
Note: This information is valid for the 11.1.1.7 version of SOA Suite.
MSG_COMPLETE: Business message state after completion of message transfer (and after receiving acknowledgment of the transmission in case of Ack/FA). Wire message state is moved to MSG_COMPLETE state as well.
MSG_WAIT_ACK: Business message state when an outbound message is sent to trading partner and B2B waits for Ack to be received.
MSG_ERROR: Business message state after a problem occurs in B2B or a negative acknowledgement is received from the trading partner. Wire message state is moved to
MSG_ERROR state as well.
MSG_WAIT_TRANSMIT: Business message state while B2B is sending message to trading partner. This state is also observed for the messages when they are queued in case of sequencing.
MSG_WAIT_FA: Business message state when an outbound message is sent to trading partner and B2B waits for Functional Ack to be received.
MSG_SEND_FA: Business message state when B2B is sending Functional Ack to a trading partner.
MSG_WAIT_BATCH: Business message state while messages are batched up during the interval before batch expiration. After the batch expires, the entire batch of messages are sent out, and business and wire message states move to MSG_COMPLETE (or MSG_ERROR if a problem occurs).
MSG_WAIT_STACK: Business message state when there is any transport error in case of sequencing.
MSG_WAIT_TA1: Business message state while waiting for TA1 Message for EDI-X12.
MSG_SEND_TA1: Business message state while sending TA1 Message for EDI-X12.
MSG_CONTINUE_PROCESS: Business message state when message is being processed in B2B(engine).
MSG_COLLAB_WAIT: Business message state when message is waiting for Collaboration.
MSG_PROCESS_ACK: Business message state while processing an Acknowledgement.
MSG_SEND_ACK: Business message state when an inbound message is received from trading partner and B2B is sending an Acknowledgement.
MSG_SEND_EXP: Business message state while sending an Exception message.
MSG_PROCESS_EXP: Business message state while Processing an Exception Message
MSG_INVALID: This state the default/first state when the message processing begins in B2B. This state should not be encountered while monitoring the Message states in B2B.
I'm hoping Oracle introduce this information in the official documentation and extends it to cover both wire and application messages.
Note: This information is valid for the 11.1.1.7 version of SOA Suite.
No comments:
Post a Comment