Modify an HTTP or HTTPS (embedded) application pickup

When you add an exchange, the exchange wizard prompts you to provide a basic set of parameters. After you create the exchange, you can open the maintenance page for the exchange to view and manage a comprehensive set of parameters for the exchange. Some of these parameters were automatically set when you added the object, and can only be modified after 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 Application pickup in the navigation graphic to open the Application pickups page.
  4. From the list of available exchanges, click the name of an HTTP (embedded) exchange to open the maintenance page for that exchange.
  5. View and modify fields as required. The fields are described in the following section.

HTTP (embedded) application pickup maintenance fields

HTTP (embedded) settings tab

  • Embedded HTTP server - If you have defined more than one embedded HTTP server, you can select the server to use with this pickup from the drop-down list.
  • Click the View setting for this embedded server link to view the configuration of the selected server.
  • Local URL – (read only) Displays the URL for client connections to the selected embedded HTTP server.

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 the back-end 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

  • 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