Modify an HTTP(S) (embedded) trading 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 to view and manage a more comprehensive set of parameters. Some of these parameters were automatically set when you added the object, and can only be modified aft er you add the object.

Procedure

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

HTTP trading pickup (embedded) maintenance fields

HTTP(S) (embedded) settings tab

Click the Global HTTP server or View settings for this embedded server link to view the HTTP(S) server configuration.

The Local URL field displays the local port and path the embedded HTTP(S) server uses. A server starts on each computer in the cluster using this information. If you have only one computer, only one server is started.

The URL used by partners field displays the URL that your partners use to connect to the HTTP(S) server to exchange messages.

Accounts tab

To enable HTTP basic authentication for this pickup, select the option This server requires a username and password to enable basic authentication.

When you select this option, you can then create accounts for partner users who are authorized to connect to this pickup. You can create as many accounts as you require, however one account must be designated as the default account.

To create a user:

  1. Click Add.
  2. Enter a user name and password. The user name must be unique within the community. The password must conform to the requirements of the password policy.
  3. If you already have one or more HTTP users defined for the community, you can click the name of a user from the list of available users and then click Save to use that user for the current pickup.
  4. Select a password policy. See Manage password policies of transport users.
  5. Click Save.
  6. If there is more than one user in the list of users for this pickup, specify which user is the default user by clicking next to the user in the Default column.
  7. Click Save changes.

Advanced tab

Use the settings on this tab to specify how to process the inbound messages that you consume through this pickup.

  • Sequence consumed messages based on their delivery exchange – Select this option if you want messages that are consumed by this pickup to be delivered in their original consumption order per resolved destination delivery. When Activator consumes messages on this pickup that are then delivered over multiple delivery exchanges, the messages are filtered and ordered in their consumed sequence for each delivery, and processed in parallel per delivery. For details about this functionality, see Sequential message delivery.
  • Synchronous response generated in backend – When this option is selected, Activator keeps the inbound HTTP or HTTPS connection open so a synchronous response can be built by the back-end system.
  • The response built by the backend uses the connection ID that was generated by the inbound transfer or set in a map that is processed by a service. This response is sent over the same open connection.
  • Configuration requirements:
    • You must ensure that the sender and receiver of the message are identified before the response is generated. You can do this, for example, by hard coding the sending and receiving parties on the From address and To address tabs of the pickup, or by selecting XML parsing options for address resolution.
    • To successfully return a synchronous response over a No Packaging HTTP(S) trading pickup, you must create a Partner delivery with the same type of No packaging HTTP(S) protocol.
  • Back up the files that go through this transport – Select this option to have the system back up copies of the messages it consumes on this pickup. This is required for the system to perform fail-over operations such as attempting to send messages again (retries) in case of a transport connection failure. Without backups, a message in process cannot be recovered if the server or a processing node stops or restarts. Backups are needed to resubmit messages to back-end applications or resend messages to partners.
  • Restrict maximum file size for this transport – Use this option to specify the maximum size of files a transport can handle.
  • If the pickup consumes a file larger than the specified maximum, the file is rejected and a message is written to the events log.
  • Express the maximum size in bytes. Do not use commas. For example, a kilobyte is 1024 bytes, a megabyte is 1048576 bytes, a gigabyte is 1073741824 bytes. The smallest maximum allowed is 1000 bytes. For the upper limit, you can enter the largest number the field can accommodate.

Related topics

Related Links