AS2 Transport Service Configuration

AS2 Transport Service

The AS2 Transport Service configuration file is "as2.properties" and is located in the "services/config" directory. It controls the various ports where the AS2 Transport runs.

  • com.boomi.transport.as2.port - The regular HTTP port where the AS2 Transport will listen. If this is not set, then the sslPort value must be set otherwise the AS2 Transport will not start. Default is 8080.
  • com.boomi.transport.as2.host - The host name of the AS2 Transport web server, by default it is localhost and should not be changed.
  • com.boomi.transport.as2.sslPort - The SSL HTTP port where the AS2 Transport will listen. If this is not set, then the regular HTTP port value must be set otherwise the AS2 Transport will not start.
  • com.boomi.transport.as2.sslAlias- The SSL certificate alias of the public/private key within the Boomi Integration Platform that should be used to create the SSL port, by default this is not set. If this is not set or references an SSL certificate that does not exist or is a public certificate, the SSL port will not be created.
  • com.boomi.transport.as2.sslClientAlias - The SSL certificate alias that represents the client. Used when trading partners require SSL Client Authentication. The alias used here should be the same one that the trading partner uses to validate SSL connections.
  • com.boomi.transport.as2.externalHost - The external host name of the machine that will be used when requesting Asynchronous MDNs. This host name should be the name of host that external clients should be used. This can be an IP address as well as a regular host name. For example, if trading partners are sending AS2 messages to "www.company.com/as2" then the value of this property should be "www.company.com"
  • com.boomi.transport.as2.logMessages - Either "true" or "false", Turns on individual message logging for both inbound and outbound messages. The message logging will include all AS2 message properties and encrypted payload and should be used for debugging purposes only. The default value if "false". Once you change this to "true", restart your Boomi services. Now set to "true", any files that are received by the Boomi AS2 Server will be placed in the log/as2 directory under the AS2 ID of your trading partner.
  • com.boomi.transport.as2.httpAcceptCount - The maximum number of concurrent AS2 connections the AS2 Transport should accept on the regular HTTP port. A message is accepted when it initially hits the server and before it gets passed to a thread to be processed. This value should not be greater than the maximum number of threads. If the maximum accept count is reached while processing messages, then the server will wait until a thread becomes free. The default is "10".
  • com.boomi.transport.as2.httpMaxThreads - The maximum number of threads the server should process at any given time on the regular HTTP port. Increasing this number will allow more messages to be processed concurrently, but will also require more resources on the system. The default is "150".
  • com.boomi.transport.as2.httpMinThreads - The minimum number of threads on the regular HTTP port the server should keep alive while the system is idle. Maintaining a minimum number of threads will reduce the overhead it takes to create a new thread to process messages. The default is "4".
  • com.boomi.transport.as2.sslAcceptCount - The maximum number of concurrent AS2 connections the AS2 Transport should accept on the SSL port. Default is "10".
  • com.boomi.transport.as2.sslMaxThreads - The maximum number of threads the server should process at any given time on the SSL port. The default is "150".
  • com.boomi.transport.as2.sslMinThreads - The minimum number of threads on the SSL port the server should keep alive while the system is idle. The default is "4".
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.