Modify an HTTP application delivery

When you add an application delivery, the Wizard prompts you to provide a basic set of parameters. After you create the delivery you can open the maintenance page 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.


  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 delivery in the navigation graphic to open the Application deliveries page.
  4. From the list of available exchanges, click the name of an 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 application delivery maintenance fields

HTTP settings tab

  • URL – URL for connecting to the HTTP server from this delivery.
  • This server requires a username and password to enable basic authentication – Select this option if the HTTP server to which you are connecting requires basic HTTP authentication.
  • If you select this option you must specify the user and password to use to connect to the HTTP server. This must be a user and password pair that is valid on the server.

Advanced tab

  • Maximum concurrent connections – – Default = 100. The maximum number of concurrent connections Activator can open to the external HTTP server to upload files.
  • Retries – This is the number of times Activator will retry connecting to the partner’s transport if the initial attempt to connect and send the message failes.
  • Use custom retry intervals – Select this option to override the default retry intervals with intervals of your choice for this delivery exchange. Default intervals are 5, 10, 15, 30, and 60 minutes. When you select this option, you must enter at least one interval (in minutes) in the Custom retry intervals field. You can enter as many intervals as you like, separated by commas. Activator applies the intervals between successive retry attempts. If necessary, the last interval you list is repeated until either the delivery is successful or the number of permitted retries is reached.
  • Connect timeout (seconds) – Time in seconds Activator waits for a connection to the delivery exchange before the attempt times out. Although the default value is 30 seconds, this may be longer than the interval allowed by your operating system (OS). For example, Windows XP by default allows a maximum timeout of 20 seconds. The actual connect timeout interval is the lesser of the OS timeout and the value set in Activator.
  • Read timeout (seconds) – Time in seconds Activator waits to read data from the delivery exchange before terminating the connection.
  • Response timeout (seconds) – Time in seconds that Activator waits for the server to respond to a request before terminating the connection.
  • Back up the files that go through this transport – Indicates whether the system backs up copies of the messages it sends to or consumes from the HTTP server.
  • Backing up files is strongly recommended. 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 also are needed if you want the ability to resubmit messages to a back-end application or resend messages to partners.
  • Backup files are stored in <Activator\data\backup, unless you specify otherwise.
  • Post-processing script – The full path to an executable file that contains post-processing commands. This field is available for both application and trading deliveries. See Post-processing of consumed messages.

Related topics

Related Links