Setting up an HTTP server adapter for EBICS

An HTTP Server adapter instance is used to receive the incoming EBICS requests and will initiate a business process to start processing the EBICS transactions.

About this task

By default, an HTTP Server adapter instance (EBICS Http Server Adapter) is auto-configured for handling EBICS requests. The HTTP Server adapter instance has a URI mapped to the business process.

The URI /ebicsrequest is the default URI specified in the EBICS HTTP Server Adapter. To configure a new URI:

Procedure

  1. From Sterling File Gateway, select Tools > B2B Console.
  2. From the Admin console, select Deployment > Services > Configuration.
  3. Next to Create New Service, click Go!
  4. From the tree directory, select HTTP Server Adapter and click Save.
  5. Click Next. Type a name and description for your EBICS HTTP Server Adapter instance.
  6. Click Next. Enter a port number and Total Business Process queue depth threshold. Enter 0 for an unlimited queue depth threshold.
  7. Optional: To enable SSL server authentication:
    1. Select User Authentication Required as:
      • Yes: If a connection must pass HTTP basic authentication to be serviced.
      • No: If HTTP basic authentication is not required.
    2. Select Use SSL as Must.
    3. Select a specific SSL version in the TLS version dropdown menu.
      Important:
      • The TLSVersionUIOptions property in the security.properties file specifies which TLS versions are available for selection from the drop-down menu.
      • You can customize the property by adding any of the permissible values to the list or removing any existing values. Permissible values are:
        • TLS1.3
        • TLS1.2
        • TLS1.0-TLS1.3
        • TLS1.2-TLS1.3
        • SystemDefault
      • It is important to note that any other value will be ignored. In such cases, the handshake will proceed using the SSLHelloProtocol property value as a fallback option to ensure secure communication.
      Note:
      • System Default uses the value from security.properties file.
      • In case of NIST Strict, the SSLHelloProtocolForNISTStrict property is used. Otherwise, SSLHelloProtocol property is used.
      • When TLSv1.3 is selected, ensure TLS 1.3 ciphers are configured in the security.properties file under the TLSv13Ciphers property. For the list of supported ciphers, see Cipher suites.
  8. Click add next to New URI. Type the desired URI.
  9. Select Business Process under Launch a BP Or WAR.
  10. Set Send Raw Messages to No.
    Note: The newly configured URI and the HTTP Server port number must match the host URL of the bank's profile.