Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment > Administer application servers


Configure transport chains

A transport chain consists of one or more types of channels, each of which supports a different type of I/O protocol, such as TCP or HTTP. Network ports can be shared among all of the channels within a chain. The channel framework function automatically distributes a request arriving on that port to the correct I/O protocol channel for processing.

Ensure that a port is available for the new transport chain. If set up a shared port, :

You need to configure transport chains to provide networking services to such functions as the service integration bus component of IBM service integration technologies, the caching proxy, and the high availability manager core group bridge service.

We can use either the admin console or wsadmin commands to create a transport chain. If you use the admin console...


Procedure

  1. In the admin console...

    Servers > Server Types > WebSphere application servers > server_name

    or Servers > Server Types > WebSphere proxy servers > server_name

    , and then select one of the following options, depending on the type of chain you are creating:

    For application servers, in the Container settings section select one of the following options:

    • Click SIP Container Settings > SIP container transport chains .

    • Click Web container settings > Web container transport chains .

    • In the Server messaging > either Messaging engine inbound transports or WebSphere MQ link inbound transports .

    For proxy servers, under HTTP proxy server settings, click Proxy server transports and select either HTTPS_PROXY_CHAIN or HTTP_PROXY_CHAIN. Then click HTTP proxy inbound channel.

  2. Click New.

    The Create New Transport Chain wizard initializes. During the transport chain creation process, you are asked to:

    • Specify a name for the new chain.

    • Select a transport chain template

    • Select a port, if one is available to which the new transport chain is bound. If a port is not available or to define a new port, specify a port name, the host name or IP address for that port, and a valid port number. If you are configuring a chain that contains a TCP channel, the wizard displays a list of configured TCP channels and a list of the ports that the listed TCP channels are not using. We must select one of the ports that none of the other TCP channels are using.

      Similarly, if you are configuring a transport chain that contains a UDP channel, the wizard displays a list of already configured UDP channels and a list of the ports that these UDP channels are not using. We must select one of the ports that none of the other UDP channels are using.

    When you click Finish, the new transport chain is added to the list of defined transport chains on the Transport chain panel.

  3. Click the name of a transport chain to view the configuration settings that are in effect for the transport channels contained in that chain.

    To change any of these settings, complete the following actions:

    1. Click the name of the channel whose settings you need to change.
    2. Change the configuration settings.

      Some of the settings, such as the port number, are determined by what is specified for the transport chain when it is created and cannot be changed.

    3. Click on Custom properties to set any custom properties that are defined for the system.

  4. When you the configuration changes, click OK.
  5. Stop the application server and start it again.

    We must stop the application server and start it again before your changes take effect.


What to do next

Update any routines we have that issue a call to start transports during server startup. When a routine issues a call to start transports during server startup, the product converts the call to a transport channel call. If you create a new web container transport chain, the initial value for the writeBufferSize attribute is 8192, which is too small for most web container transport chains. IBM recommends that you use the admin console or wsadmin scripting to change the value of this attribute to 32768. Complete the following steps to use the admin console, to change the value of this attribute:

  1. Click Servers and expand Server Types.

  2. Click WebSphere application servers > server_name

  3. Expand Web Container Settings and click Web container transport settings > transport_chain_name.

  4. Click Web container inbound channel.

  5. Specify 32768 in the Write buffer size field, and click OK.

  6. Click Save.

To change the value using wsadmin scripting, see the documentation about working with Web container inbound channel properties files.


Related


Transport chains
HTTP transport collection
HTTP transport settings
Transport chains collection
Transport chain settings
HTTP tunnel transport channel settings
HTTP transport channel settings
TCP transport channel settings
DCS transport channel settings
SSL inbound channel
SIP inbound channel settings
SIP container inbound channel settings
User Datagram Protocol (UDP) Inbound channel settings
Web container inbound transport channel settings
DataPower appliance manager transport channel settings
HTTP transport channel custom properties
HTTP Tunnel transport channel custom properties
TCP transport channel custom properties
Transport chain problems
Delete a transport chain
Disable ports and their associated transport chains
SIP UDP transport channel custom properties
Messaging engine communication
Use wsadmin scripting
Work with web container inbound channel properties files
Administer application servers


Related


JFAP inbound channel [Settings]
WebSphere MQ link MQFAP inbound channel [Settings]
HTTP error, FRCA, and NCSA access log settings
Ports collection
SIP container

+

Search Tips   |   Advanced Search