5.2.2. Configure Socket Bindings

Socket bindings can be defined in unique socket binding groups. The Standalone Server contains one such group, the standard-sockets group, and is unable to create any further groups. Instead you can create alternate Standalone Server configuration files. For the Managed Domain however, you can create multiple socket binding groups and configure the socket bindings that they contain as you require. The following table shows the available attributes for each socket binding.

Table 5.2. Socket Binding Attributes

Component Description Role
Name Logical name of the socket configuration that should be used elsewhere in the configuration. Required
Port Base port to which a socket based on this configuration should be bound. Note that servers can be configured to override this base value by applying an increment or decrement to all port values. Required
Interface Logical name of the interface to which a socket based on this configuration should be bound. If not defined, the value of the "default-interface" attribute from the enclosing socket binding group will be used. Optional
Multicast Address If the socket will be used for multicast, the multicast address to use. Optional
Multicast Port Bound to the lifecycle of the conversation. The conversation scope is between the lengths of the request and the session, and is controlled by the application. Optional
Fixed Port If the above contexts do not meet your needs, you can define custom scopes. Optional

  • Configure Socket Bindings in Socket Binding Groups

    Choose either the Management CLI or the Management Console to configure your socket bindings as required.

    • Configure Socket Bindings Using the Management CLI

      Use the Management CLI to configure socket bindings.

      1. Add a New Socket Binding

        Use the add operation to create a new address setting if required. You can run this command from the root of the Management CLI session, which in the following examples creates a new socket binding titled newsocket, with a port attribute declared as 1234. The examples apply for both Standalone Server and a Managed Domain editing on the standard-sockets socket binding group as shown. 
        [domain@localhost:9999 /] /socket-binding-group=standard-sockets/socket-binding=newsocket/:add(port=1234)

      2. Edit Pattern Attributes

        Use the write-attribute operation to write a new value to an attribute. You can use tab completion to help complete the command string as you type, as well as to expose the available attributes. The following example updates the port value to 2020 
        [domain@localhost:9999 /] /socket-binding-group=standard-sockets/socket-binding=newsocket/:write-attribute(name=port,value=2020)

      3. Confirm Pattern Attributes

        Confirm the values are changed by running the read-resource operation with the include-runtime=true parameter to expose all current values active in the server model. 
        [domain@localhost:9999 /] /socket-binding-group=standard-sockets/socket-binding=newsocket/:read-resource

    • Configure Socket Bindings Using the Management Console

      Use the Management Console to configure socket bindings.

      1. Log into the Management Console.

        Log into the Management Console of your Managed Domain or Standalone Server.

      2. Select the Profile tab

        Select the Profiles tab at the top right.

      3. Select the Socket Binding item from the navigation menu.

        Select the Socket Binding menu item from the navigation menu. If you are using a Managed Domain, select the desired group in the Socket Binding Groups menu.

      4. Add a New Socket Binding

        1. Click the Add button.
        2. Enter any required values for Name, Port and Binding Group.
        3. Click the Save to finish.

      5. Edit Interface Attributes

        1. Select the Socket Binding to edit and click the Edit button.
        2. Enter any required values such as Name, Interface or Port.
        3. Click the Save to finish.
Report a bug