The MSMQReceiver component is used to receive messages from MSMQ. The name of the queue from which a message needs to be retrieved can be specified using the CPS.

Anchor
MSMQRec_Config&Test MSMQRec_Config&Test

Configuration and Testing

The MSMQ server and queue can be configured in the connection properties panel of Configuration Property Sheet (CPS).

Managed Connection Factory

Figure 1: Managed Connection Factory in MSMQReceiver CPS

Please refer the respective sections in MSMQSender4.0 page for the information about the properties Use Connection Details From Input, Connection Configuration and Connection Pool Params.

Interaction Configurations

Figure 2: Interaction Configuration panel

Monitoring Configuration

Scheduler Configuration

Please refer the respective section in Common Configurations page.

Error Handling

Please refer Error Handling section Common Configurations page for details.

Anchor
_Toc372741000 _Toc372741000

Input and Output

Anchor
_Toc372741001 _Toc372741001

Input Schema

There is no input schema for this adapter.

When the property Use Connection details from input is chosen, the following input schema with the element ConnectionFactorySettings is generated. Properties that are used to create the connection are present under this element.

Figure 3: Input schema with ConnectionFactorySettings

Anchor
_Toc372741002 _Toc372741002

Output Schema

There is no output schema for this adapter.

Anchor
_Toc372741003 _Toc372741003

Functional Demonstration

Anchor
_Toc372741004 _Toc372741004

Scenario 1

Receive messages from a local MSMQ Server.
Configure the MSMQ Receiver as described in Configuration and Testing section and use feeder and display component to send sample input and check the response respectively.

Figure 4: Configuration the MSMQ Receiver

Sample Input

Figure 5: Demonstrating Scenario 1 with sample input

Sample Output

Figure 6: Demonstrating Scenario 1 with sample output

Anchor
_Toc372741005 _Toc372741005

Use case scenario

In the revenue control packet example the transaction file details are received from an MSMQ server from where they are picked up by other applications for processing.

Figure 7: Revenue control packet

The event process demonstrating this scenario is bundled with the installer. The bundled process shows it as a File Reader component instead of a MSMQ Receiver component.
Documentation of the scenario and instructions to run the flow can be found in the Help tab of the flow in eStudio.

Anchor
_Toc372741006 _Toc372741006

Useful Tips

• If a queue specified in the CPS does not exist in a local or remote MSMQ server, it is not automatically created.
• This component runs only on Windows Platform.