Configuring a core group transport

When you configure a core group, you can specify the type of network transport that you want the high availability manager to use for network communications.

Before you begin

Complete the following actions before you start to configure a core group transport.

About this task

Change the transport setting for a core group if the current transport type does not meet your needs. For example, you might need to increase security, you might want to maximize replication throughput, or a core group might need to use the core group bridge service.

Avoid trouble Avoid trouble: If a core group needs to use the core group bridge service, you must select Channel framework as its transport mechanism. If you select Unicast, you might receive error message CHFW0029E, which indicates that the transport chain was not initialized because the address was already in use.gotcha

To change the core group transport for a core group, complete the following procedure.

Procedure

  1. In the administrative console, click Servers > Core Groups > Core group settings, and select an existing core group, or click New if you are creating a new core group.
  2. Under Transport type, select the type of transport that you want to use for this core group.
    Deprecated feature Deprecated feature: You can select one of the following types of transports. However, if possible, select Channel framework because support for unicast transports is deprecated.depfeat
    • Channel framework is the default transport type, and is a flexible point-to-point transport. If you choose this transport type, you must also select one of the transport chains that is listed in the Transport chain field.
      • If you select DCS, the high availability manager performs related network communication over non-secure sockets.
      • If you select DCS-Secure, the high availability manager performs related network communication over Secure Sockets Layer (SSL) encrypted sockets.
    • Unicast, is a point-to-point transport over standard non-secure operating system-level TCP/IP network connection facilities.
  3. Click Synchronize changes with nodes, and then click OK.
  4. Select Synchronize changes with nodes, and then click Save again.
  5. Restart the servers containing core group members.

Results

The new transport values are in effect after the servers restart.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 18, 2014 05:01 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=trun_ha_cfg_transport
File name: trun_ha_cfg_transport.html