Work with specific protocols and standards > AS4 > AS4 tasks > Modify an AS4 polling client pickup

Modify an AS4 polling client pickup

When you add a trading pickup, the wizard prompts you to provide a basic set of parameters. After you create the pickup, you can open the maintenance page for the pickup. This enables you to view and manage a comprehensive set of parameters. Some of these parameters were automatically set when you added the object, and can only be modified after you add the object.

Procedure

In the Activator user interface, select Trading configuration > Manage trading configuration.
From the list of communities, click the name of a community to display the Summary page for that community.
Click Trading pickup in the navigation graphic to open the community's Trading Pickups page.
From the list of available pickups, click the name of an AS4 (polling) pickup to open the maintenance page for that pickup.
View and modify fields as required. The fields are described in the following section.
After making any modifications, click Save changes.

AS4 trading pickup (polling) maintenance fields

AS4 polling settings tab

Partner name – You cannot directly modify this field. This field is automatically populated based on partner delivery exchange selection.
Delivery exchange – This field displays the delivery exchange that is selected to send the pull request message to the partner server. To modify parameters of this exchange, click the name that is displayed, and in the Change this delivery page, modify settings as required.
Delivery URL – You cannot directly modify this field. This field is automatically populated based on partner delivery exchange selection.
Message partition channel (MPC) – You cannot directly modify this field. This field is automatically populated based on partner delivery exchange selection.
Override message partition channel (MPC) – Optionally enter an alternative MPC identifier to override the value specified in the previous field. If you enter a value in this field, the same value must be configured for the polled queue on your partner's machine.
- If you leave this field blank, the MPC on the selected partner delivery exchange is applied for the exchange. If the partner delivery exchange MPC field is also empty, then the default-implicit (empty) MPC is applied for the exchange.
- If you enter the default-explicit MPC, this default MPC is applied for the exchange. (Default is http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/defaultMPC).
- If you enter an alternative MPC identification, the alternative is applied for the exchange.

Advanced tab

User message processing

Header section:

Parse SOAP headers into message metadata – Select this option if you want to SOAP headers to be carried as metadata attributes with the message.
XPath reference to SOAP header to parse – If you selected the previous option (Parse SOAP headers into message metadata), enter an XPath expression to resolve the header.
Click Add to display the Local XPath field and then enter an XPath expression. Enter any legal XPath expression. Xpath wildcard syntax is permitted. If the expression resolves to more than one node, only the value of the first matching node is included in the metadata value.

Body / Attachments section:

Process SOAP body – Select this option to process the contents of the SOAP body of the pulled message.
Process attachments – Select this option to process the attachments of the pulled SOAP message.
- Group attachments – Select this option take the attachments of the original message (after they were split into separate messages) and enter them as attributes (metadata) of the SOAPBody.

Processing section:

Generate receipt – Select this option if you want to generate receipts for messages that are pulled from the remote partners polling queue.
Restrict maximum file size for this transport – Optionally specify the maximum size of files that this transport can handle, per message pull. If Activator receives a file larger than the maximum, the file is rejected and a message is written to the events log.

Pull request processing section:

Maximum pull requests per polling interval – The highest number of pull requests per polling interval, that the community can send to retrieve messages that are queued in the AS4 polling queue on the partner server. The polling interval is set in the field below.
Polling interval (seconds) – (Default = 60) The interval, in seconds, Activator waits between polling actions for messages to retrieve.