This transport is based on TCP/IP. It uses a separate 'channel' for the request and the reply. It provides an efficient and low cost transport. A port number is optional, if you do not enter a port number the variable policy will be used.
The syntax for the TCP/IP URI is:
socket://<hostname>:<port>
Example: socket://server1:8000
Like the Socket transport but using one bi-directional channel for the request and the reply message. This enables NAT and easier firewall configuration. You can specify a portrange for bidisockets by filling in both a port and the optional endport. When you do not enter a port number or when you use a port range the variable policy is used.
The syntax for the bidirectional sockets URI is:
bidisocket://<hostname>:<port>[-<endport>]/
Example: bidisocket://server1:8000-8004
SSL Sockets (Java 1.4 only). Enables encryption and data integrity on the transport layer.
Authentication=DH
anonymous, Encryption=RC4 128, Data Integrity=MD5 Like the bidiSocket transport
it is using one bi-directional socket
channelfor the requestand the reply message.This enables NAT and easier firewall configuration.You can specify a portrange by filling in
both a port and the optional endport.When you do not enter a port number or when you use a port range the variable policy is used.
The syntax for the Secure Socket Layer (SSL) sockets (Bidirectional) URI is:
sslsocket://<ip_address>:<port>[-<endport>]/
Example: sslsocket://server1:7912
Provides an in-process transport that can be used to run any adapter client with any adapter server in one process. This transport can be used in combination with in-process activation.
The syntax for the 'inproc' URI is:
inproc://localhost:<port>/
Example: inproc://localhost:8000
Java Message Service (JMS) is a Java API for accessing a variety of Message Oriented Middleware products (MOM). The JMS provider implements JMS for a specific MOM. Currently there are JMS providers available for a wide range of message products. Example are:
For a definition on the JMS URI refer to the JMS specific documentation.
A ConnectionPoint can have a variable policy. This means that not all required connection information is present in the ConnectionPoint (e.g. ports etc.) The missing information is filled in at runtime.
Variable Server BusComponent
You can use a BusComponent with a variable ConnectionPoint to start a Server (Activation). This BusComponent can be started more than once.
in case of a socket like transport (sockets, bidisockets or sllsockets), variable means that there is no port specified, or a port range is used.
Variable Client BusComponent
Select Variable Policy also when you want to define a variable client.
The first connection in the list will be the preferred connection. It will be used by default, and other connections will only be used if the preferred connection is not available.