Endpoint packaging

An endpoint packaging configuration is used to control transmission definitions and distribution windows at the item mapping level. It allows the user to assign a transmission definition and a set of distribution windows to each item mapping that is in the item grouping that is associated with the endpoint for a participant. Each endpoint with an item grouping must have a default endpoint packaging before the participant version can be activated.

Endpoint packaging configurations are defined for receiving point endpoints that have item groupings associated with them. The endpoint packaging has an endpoint item mapping configuration for each of the item mappings that are in the item grouping associated with the endpoint. The endpoint item mapping configuration allows the user to specify the transmission definition and the set of distribution windows to use for the work that belongs to the item mapping. The endpoint packaging must have an endpoint item mapping configuration for all of the item mappings in the item grouping for the endpoint. The following paragraphs describe how the transmission definition and distribution window information in the item mapping is used.
Transmission definition
When the transmission definition in the item mapping is configured to use a specific connection, that connection is the one that is used to send transmissions. The transmission connections page for the participant is used to associate connections with transmission definitions.
Distribution windows
The endpoint item mapping configuration defines a list of the distribution windows that can be used for the work that belongs to the item mapping. Distribution windows that are configured to not allow receivers to opt out cannot be removed from this list of distribution windows. If the distribution window that is assigned to a transaction by Business Rules is not on the list of distribution windows in the endpoint item mapping configuration, the transmission is treated as though it was received at the start of the next distribution window and Business Rules re-processes it.

Because an endpoint packaging has no effect on a sidepoint, only endpoints that have a usage indicator of endpoint are available to be used in endpoint packaging configurations. Endpoints that have a usage indicator of both endpoint and sidepoint may be used for an endpoint packaging, but the packaging does not have any effect when the endpoint is used as a sidepoint.

More than one endpoint packaging configuration can be defined for the endpoint, such as when the participant has RDFI groupings defined. For example, an endpoint may have an endpoint packaging that applies to a specific RDFI grouping and a default endpoint packaging that applies to the rest of the RDFIs. If a specific RDFI grouping is not selected for an endpoint packaging, that endpoint packaging is the default packaging for the endpoint. The default packaging applies to all of the RDFIs that are not a part of an RDFI grouping with an endpoint packaging defined for it.

For example, a participant has an RDFI grouping called ExampleGrouping that groups half of its RDFIs to an endpoint named EXAMPLE. Two endpoint packaging configurations are created for the EXAMPLE endpoint; one endpoint packaging has its RDFI grouping set to default and the other has ExampleGrouping as its RDFI grouping. The following table shows the two endpoint packaging configurations.

Table 1. Endpoint packaging example
Endpoint packaging Endpoint name RDFI grouping name Item mapping name
A EXAMPLE ExampleGrouping ItemMapping1
ItemMapping2
B EXAMPLE Default ItemMapping3
ItemMapping4

In this example, all of the RDFIs in ExampleGrouping use endpoint packaging A because it is associated with the ExampleGrouping RDFI grouping. All of the work that is using the EXAMPLE endpoint and is destined for RDFIs that are not in ExampleGrouping uses endpoint packaging B, which is the default packaging.