Chapter 16. Configuring remoting and connections

• The remoting endpoint
• HTTP connector
• Outbound connections

• Configure endpoint settings to tailor communication for specialized services or environments. For example, you can adjust authentication and security settings to separate administrative traffic from regular application traffic.
• Update an existing endpoint configuration to meet security or performance requirements. For example, adjusting settings like authentication retries or timeouts can improve security and ensure optimal performance under varying loads.

Prerequisites

• JBoss EAP is running.

• Create a new HTTP connector to establish remote communication using the HTTP upgrade-based remoting protocol. This enables secure and efficient remote access to JBoss EAP services.
• Update an existing HTTP connector to optimize performance, enhance security, or integrate with specific network configurations. Adjusting attributes such as authentication mechanisms or connection timeouts improves reliability and ensures compliance with security policies.
• Delete unnecessary HTTP connectors to simplify configuration and reduce security risks. Deleting unused connectors helps maintain a clean and secure environment by minimizing exposure to unauthorized access.

Prerequisites

• JBoss EAP is running.

• Create a new outbound connection to establish communication with external services. This enables seamless data exchange and integration with remote systems.
• Update an existing outbound connection to enhance performance, strengthen security, or align with network configurations. Adjusting attributes such as the target URI improves reliability and ensures compatibility with system requirements.
• Delete unnecessary outbound connections to streamline configuration and reduce security risks. Deleting unused connections helps maintain a clean and secure environment by minimizing exposure to unauthorized access.

Prerequisites

• JBoss EAP is running.

• Create a new remote outbound connection to enable secure communication with external services. This ensures applications can interact with remote systems using specified protocols and authentication methods.
• Update an existing remote outbound connection to enhance security, improve performance, or integrate with specific network configurations. Adjusting attributes such as outbound socket bindings or authentication settings ensures stability and compliance with security policies.
• Delete unnecessary remote outbound connections to simplify configuration and reduce security risks. Deleting unused connections helps maintain a clean and secure environment by minimizing exposure to unauthorized access.

Prerequisites

• JBoss EAP is running.

• Create a new local outbound connection to enable secure and efficient communication within the same server instance. This helps streamline internal interactions without requiring external networking.
• Update an existing local outbound connection to improve performance, modify socket bindings, or align with specific configurations. Adjusting attributes such as outbound socket bindings ensures stability and compatibility.
• Delete unnecessary local outbound connections to simplify configuration and reduce security risks. Deleting unused connections helps maintain a clean and secure environment by minimizing exposure to unauthorized access.

Prerequisites

• JBoss EAP is running.

• Configure an IO worker for remoting to improve performance and manage remoting tasks efficiently. Ensure that the worker is defined in the IO subsystem.
• Modify the network interface settings to align remoting with the required public, management, or unsecure interface. Configuring the correct interface ensures proper connectivity.
• Adjust the socket binding for the remoting subsystem to specify the appropriate port and maintain compatibility with network and security policies.

• Enable secure transport with STARTTLS to protect remoting communications. Ensure that your configuration verifies secure connections to prevent security risks, such as man-in-the-middle attacks.

  IO worker

  Use the following command to set the IO worker for remoting. Ensure that the worker is defined in the IO subsystem before running this command:

  /subsystem=remoting:write-attribute(name=worker, value=WORKER_NAME)

  Network interface

  The network interface used by the remoting subsystem is the public interface. This interface is also used by other subsystems, so exercise caution when modifying it.

  <interfaces>
     <interface name="management">
        <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
     </interface>
     <interface name="public">
        <inet-address value="${jboss.bind.address:127.0.0.1}"/>
     </interface>
     <interface name="unsecure">
        <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
     </interface>
  </interfaces>

  In a managed domain, the public interface is defined per host in its host.xml file.

  Socket binding

  The default socket binding for the remoting subsystem binds to port 8080.

  Secure transport configuration

  Remoting transports use STARTTLS to establish a secure connection, such as HTTPS or Secure Servlet, if the client requests it. The same socket binding, or network port, is used for secured and unsecured connections, so no additional server-side configuration is necessary. The client requests secure or unsecured transport as needed. JBoss EAP components that use remoting, such as Jakarta Enterprise Beans, ORB, and the Jakarta Messaging provider, request secure interfaces by default.