WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Defining outbound chains for bootstrapping

Use this task to define new outbound chains using the wsadmin utility. The chains created can be used for bootstrapping connections to messaging engines.

The process of creating outbound chains for bootstrapping involves several overall steps:
  1. Locate the appropriate TransportChannelService configuration object. This object is the parent object of all the objects created.
  2. Create the individual channels that comprise the transport channel service. Some of these channels may require references to other configuration objects.
  3. Assemble the channels that have been created into an outbound channel chain.
The channels used to build an outbound bootstrap chain determine the protocol with which the outbound chain can be used to bootstrap. The following table shows all valid bootstrap chains with their bootstrap protocols:
Bootstrap protocol TCP channel SSL channel HTTP channel HTTP tunneling channel JFAP channel
TCP X       X
SSL X X     X
HTTP X   X X X
HTTPS X X X X X

For example, a chain for bootstrapping using the SSL protocol would consist of a TCP channel, SSL channel, and JFAP channel. When creating chains, the order of channels in the chain is important. You must specify channels in the order (left to right) in which they appear in the above table.

The example in this topic describes how to create a bootstrap chain capable of bootstrapping using the HTTPS protocol. This requires a chain containing all the channel types described, therefore it is easy to see how chains for other protocols can be created by omitting channels during the chain creation step.

  1. Locate the TransportChannelService object for the server in which you wish to create the new chain. For example in a network deployment configuration, you can list the available TransportChannelService objects and select the appropriate service as follows:
    wsadmin> $AdminConfig list TransportChannelService
    (cells/BadgerCell01/nodes/BadgerCellManager01/servers/dmgr|server.xml#TransportChannelService_1)
    (cells/BadgerCell01/nodes/BadgerNode01/servers/nodeagent|server.xml#TransportChannelService_1095711814579)
    (cells/BadgerCell01/nodes/BadgerNode01/servers/server1|server.xml#TransportChannelService_1095712023139)
    (cells/BadgerCell01/nodes/BadgerNode01/servers/server2|server.xml#TransportChannelService_1095712039302)
    wsadmin> set tcs [lindex [$AdminConfig list TransportChannelService] 2]
    (cells/BadgerCell01/nodes/BadgerNode01/servers/server1|server.xml#TransportChannelService_1095712023139)
  2. Define an outbound TCP channel called testTCPChannel:
    wsadmin>set tcpChannel [$AdminConfig create TCPOutboundChannel $tcs "{name testTCPChannel}"]
    testTCPChannel(cells/BadgerCell01/nodes/BadgerNode01/servers/server1|server.xml#TCPOutboundChannel_1095969213949)
  3. Define an outbound SSL channel called testSSLChannel. There are two steps required to define such a channel.
    1. Identify the SSL alias to be used by the channel.
      wsadmin>foreach obj [$AdminConfig list SSLConfig] { puts "$obj [$AdminConfig show $obj alias]]" }
      (cells/BadgerCell01|security.xml#SSLConfig_1) {alias BadgerCellManager01/DefaultSSLSettings}]
      (cells/BadgerCell01|security.xml#SSLConfig_1095711819776) {alias BadgerNode01/DefaultSSLSettings}]
    2. Create an SSL channel as in the following example, in which the BadgerNode01/DefaultSSLSettings alias is used:
      wsadmin>set sslChannel [$AdminConfig create SSLOutboundChannel $tcs "{name testSSLChannel} (sslConfigAlias BadgerNode01/DefaultSSLSettings}"]
      testSSLChannel(cells/BadgerCell01/nodes/BadgerNode01/servers/server1|server.xml#SSLOutboundChannel_1095971760671)
  4. Define an outbound HTTP channel called testHTTPChannel:
    wsadmin>set httpChannel [$AdminConfig create HTTPOutboundChannel $tcs "{name testHTTPChannel}"]
    testHTTPChannel(cells/BadgerCell01/nodes/BadgerNode01/servers/server1|server.xml#HTTPOutboundChannel_1095971896556)
  5. Define an outbound HTTP tunneling channel called testHTCChannel:
    wsadmin>set htcChannel [$AdminConfig create HTTPTunnelOutboundChannel $tcs "{nam
    e testHTCChannel}"]
    testHTCChannel(cells/BadgerCell01/nodes/BadgerNode01/servers/server1|server.xml#HTTP
    TunnelOutboundChannel_1095972164201)
  6. Define an outbound JFAP channel called testJFAPChannel:
    wsadmin>set jfapChannel [$AdminConfig create JFAPOutboundChannel $tcs "{name testJFAPChannel}"]
    testJFAPChannel(cells/BadgerCell01/nodes/BadgerNode01/servers/server1|server.xml#JFAPOutboundChannel_1095972226631)
  7. Finally, create the channel chain by combining the channels defined so far. For example, to create a chain called testChain:
    wsadmin>$AdminConfig create Chain $tcs "{name testChain} {enable true} {transportChannels {$tcpChannel $sslChannel $httpChannel $htcChannel $jfapChannel}}"
    testChain(cells/BadgerCell01/nodes/BadgerNode01/servers/server1|server.xml#Chain_1095972662147)
Related concepts
Outbound transport options
Connecting applications to a service integration bus

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjk1000_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)