You can configure a messaging receiver as an endpoint for receiving notifications in B2B Advanced Communications exchanges. Use Receivers to create and configure a new messaging receiver.
Before you begin
A messaging receiver must be associated with a message queue. Ensure that a system
administrator or a user with the necessary permissions created the required message queue before you
create a messaging receiver.
You also can import a receiver as a resource from another installation of B2B Advanced Communications. For more information about importing receiver as a resource with commands, see Resource commands.
Procedure
To create a messaging receiver:
- Log in to B2B Advanced Communications as a user with the permissions to create a messaging receiver.
- Click Exchanges > Receivers.
- On the Receivers page, click New and
select Messaging.
- On the New Receiver page, specify
values for the following fields:
- Name
Specify a unique name for the messaging receiver.
- Description
Optional: Type a description for the messaging receiver.
- Message Queue
Select the message queue to associate with the messaging receiver. The business application sends
the BDO (message, payload, and attachments) to the message queue that is associated with
the messaging receiver.
Note: If the communications component receives a notification (critical event) about low grid memory, the messaging receivers immediately stop accepting the incoming messages for processing. Messages that are already accepted are processed. After the memory clears and rises higher than the low watermark, another notification is sent to the communications component. Thereafter, the messaging receivers start accepting the messages.
- Number of consumers
Specify the number of consumers for the messaging receiver. B2B Advanced Communications selects messages from the messaging receiver based on the number of consumers. For example, if you specify 1 as the value, one message is picked from the message queue at a time.
- User exits
-
Optional: User exits provide a call to an external program during the ebMS process flow of an AS4 receiver message. You must develop user exits with the provided user exit Java APIs and deploy the OSGi bundles with the user exit commands.
To add a user exit, click Add New User Exits. On the New user exits page, specify values for the applicable fields as follows:
- Name
Name of the user exit.
- Description
Optional: Description of the user exit.
- Service ID
Unique identifier that must start with a letter or an underscore and it cannot contain spaces or special characters.
- Exit point
Point in the receiver process flow when the user exit is started.
- Pre-process
With the Pre-process value selected, the user exit is started before the message enters the receiver process flow. User exits started in Pre-process can have a negative impact on performance and slow the progress of the messages through the system. You must include performance testing of your OSGi user exit bundles as part of your user exit development process.
- Post-process
With the Post-process value selected, the user exit is started after the message exits the receiver process flow. User exits started in Post-process can have a negative impact on performance and slow the progress of the exiting messages through the system. You must include performance testing of your OSGi user exit bundles as part of your user exit development process.
Click Save. The new user exit is now listed on the User Exit Collection page.
To select a user exit from the User Exit collection page, click Select User Exits and select the appropriate Pre-process or Post-process user exit from the drop-down.
- Click Save to save the messaging
receiver configuration. The messaging receiver is automatically started
when you save the configuration.