WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Add a transport to the list of permitted transports [Settings]

Add a transport to the list of permitted transports.

To view this pane in the console, click the following path:

Service integration > Buses > [Content Pane] bus_name > Security > [Additional Properties] Permitted Transports > [Content Pane] member_name.

Related concepts
Inbound transport options
Related information
Administrative console buttons
Administrative console preferences

Configuration tab

Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.

General properties

Transport chain name

Select the transport name from the list of chain names.

Required No
Data type drop-down list
Range
InboundBasicMessaging
This transport chain is allows communication using the TCP protocol. The default port used by this chain for the first server on the node is 7276. You should verify that the selected port is not already used, for example if you are configuring a second server with the same name as the first server. Messaging engines hosted in other application servers and JMS applications running in a client container can communicate with the messaging engines of the server using this transport chain.
InboundSecureMessaging
This transport chain is provides secure communication using the secure sockets layer (SSL) based encryption protocol over a TCP network. The default port used by this chain for the first server on the node is 7286. You should verify that the selected port is not already used, for example if you are configuring a second server with the same name as the first server. The SSL configuration information for this chain is based on the default SSL repertoire for the application server. Messaging engines hosted in other application servers and JMS applications running in the client container can communicate using this transport chain.
InboundBasicMQLink
This transport chain is supports WebSphere MQ queue manager sender channels and applications using the WebSphere MQ messaging provider connecting over a TCP network. The default port used by this chain is 5558, although this can be automatically adjusted to avoid conflicts.
InboundSecureMQLink
This transport chain is enables WebSphere MQ queue manager sender channels and applications using the WebSphere MQ messaging provider to establish SSL based encrypted connections over a TCP network. The default port used by this chain is 5578, although this is automatically adjusted to avoid conflicts.
BootstrapBasicMessaging
This transport chain is used to establish bootstrap connections to inbound chains configured for TCP-only connections to an application server, such as the InboundBasicMessaging chain.
BootstrapSecureMessaging
This transport chain is used to establish secure connections using secure sockets layer (SSL) based encryption. The SSL configuration used is taken from the default SSL repertoire when used in an application server environment or from a configuration file when used by the client container. This chain can be used for establishing bootstrap connections to inbound chains that are configured to use SSL, for example, the InboundSecureMessaging chain. Success in establishing such a connection depends on a compatible set of SSL credentials being associated with both this bootstrap outbound chain and also with the inbound chain to which the connection is being made.
BootstrapTunneledMessaging
This transport chain is used to establish bootstrapping connections that are tunneled through HTTP. This transport chain tunnels JFAP using HTTP wrappers. Before you can use this bootstrap transport chain, you must define a corresponding server transport chain on the bootstrap server. (See Servers > Application servers > server_name > Messaging engine inbound transports.)
BootstrapTunneledSecureMessaging
This transport chain tunnels JFAP using HTTP wrappers. Used to establish bootstrapping connections that are tunneled through secure HTTP (HTTPS). Like the BootstrapSecureMessaging outbound chain, this chain also derives its SSL configuration from the default SSL repertoire when used in an application server or from a configuration file when used in the client container.
OutboundBasicMQLink
This transport chain is used to establish connections with WebSphere MQ queue manager receiver channels. It is used when communicating with WebSphere MQ through a WebSphere MQ link.
OutboundSecureMQLink
This transport chain is used to establish connections with WebSphere MQ queue manager receiver channels that have been secured using SSL. It is used when communicating with WebSphere MQ through a WebSphere MQ link. The SSL configuration used is taken from the default SSL repertoire for the application server being used to contact the queue manager.
OutboundBasicWMQClient
This transport chain is used when communicating with WebSphere MQ receiver channels. It is used when communicating with WebSphere MQ through a WebSphere MQ server.
OutboundSecureWMQClient
This transport chain is used when communicating with WebSphere MQ receiver channels that have been secured using SSL. It is used when communicating with WebSphere MQ through a WebSphere MQ server.

You can manage inbound chains through the administrative console by selecting either Servers > Application servers > server_name > Messaging engine inbound transports orServers > Application servers > server_name > WebSphere MQ link inbound transports. You can also use these administrative console panels to define new transport chains from a set of templates.

The outbound chains that an application server uses for bootstrap operations are defined when the server is defined. They can be altered, or new bootstrap chains can be defined, using the wsadmin tool.


Reference topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/sibresources/SIBPermittedTransports_DetailForm.html

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