The TCP Server window is displayed.
Alternatively, open the Logical View, right-click a TCP connection, and click Set Binding in > Environment name > Create new TCP Server in the menu.
Hostname |
The host name or IP address of the computer that hosts the TCP server to which you want to connect. |
Port |
The port number to which you want to connect. |
The Port Forwarding Proxy settings help you to specify a proxy through which Rational Integration Tester will connect to the computer that hosts the TCP server. If you do not specify a proxy, Rational Integration Tester uses the host name and port number that is specified on the Settings tab to connect directly to the computer that hosts the TCP server.
Hostname |
The host name or IP address of the proxy through which you want to connect to the computer that hosts the TCP server. |
Port |
The port number of the proxy through which you want to connect to the computer that hosts the TCP server. |
The Socket Options settings helps you to specify socket settings for the transport.
Send 'keep alive' packets |
Select this check box if you want to enable the use of keep alive packets, which are used to maintain the stream connection where possible. |
Enable Nagle's algorithm |
Select this check box if you want to reduce the number of packets that are sent by combining small messages. |
Receive buffer size |
The send and receive buffer sizes define the receive window, which is the amount of receive data (in bytes) that can be buffered at one time on a TCP/IP socket connection. The optimal buffer size depends on network environment factors, such as acknowledgment timing, error rates, network topology, memory size, and data transfer size. Rational Integration Tester uses
a default receive buffer size. If you want to specify a different
receive buffer size, enter the value in the field provided.
Tip: Any value that you enter is treated only as a hint to the
socket and it might be ignored.
|
Send buffer size |
Rational Integration Tester uses
a default send buffer size. If you want to specify a different send
buffer size, enter the value in the field provided.
Tip: Any
value that you enter is treated only as a hint to the socket and it
might be ignored.
|
The Kerberos settings helps you to configure Kerberos authentication for the transport.
Use Kerberos |
Select this check box to enable Kerberos authentication for the transport. Selecting the check box makes available the other controls under Kerberos. |
Principal |
A Kerberos principal represents a unique identity in a Kerberos system to which Kerberos can assign tickets to access Kerberos-aware services. Enter the alias of the principal that you want to use for authentication. |
Credential Type |
Using the list that is provided, specify whether the identity of the principal will be provided in the form of a user name and password or in an external file. Tip: Clicking Username / Password makes
the Username and Password fields
available, and clicking External Config makes
the Config Location field available.
|
Username |
If you clicked Username / Password in the Credential Type list, enter the user name of the principal that you want to use for authentication. |
Password |
If you clicked Username / Password in the Credential Type list, enter the password of the principal that you want to use for authentication. |
Config Location |
If you clicked External Config in the Credential Type list, enter the path and file name of the file that contains identity details about the principal that you want to use for authentication. |
Anonymity |
Kerberos provides a mechanism for principals to authenticate to a remote service without disclosing their identities. By default, this check box is selected. Clear this check box if you want to disclose the principal's identity when data is sent and received. |
Confidentiality |
Kerberos optionally provides confidentiality for data that is sent between the client and server. By default, this check box is selected. Clear this check box if you do not want to use encryption when data is sent and received. |
Integrity |
Kerberos optionally provides integrity for data that is sent between the client and server. By default, this check box is selected. Clear this check box if you do not want to use checksum when data is sent and received. |
Mutual Authentication |
Kerberos optionally supports mutual authentication, which enables a client to validate the identity of a server. By default, this check box is selected. Clear this check box if you do not want to use mutual authentication when data is sent and received. |
Replay Detection |
Kerberos optionally supports replay attack detection, which prevents an eavesdropper from recording the messages that are sent by the client, establishing a new connection, and resending or replaying the same messages. By default, this check box is selected. Clear this check box if you want do not want to use replay detection when data is sent and received. |
Sequence Checking |
Kerberos optionally supports sequence checking, which involves the use of sequence numbers to counter-replay attacks. By default, this check box is selected. Clear this check box if you do not want to use sequence numbers when data is sent and received. |
The Socket Overrides settings help you to specify socket override settings for the port on the TCP server to which you want to connect.
Bind Address |
You can enter a bind address.
Important: If you
do not enter a value in this field, the address that is specified
in the HTTP Bind Address field in the Application
page of Library Manager is used. If no address is specified in the HTTP
Bind Address field in Library Manager, the transport binds
to all local addresses on the computer that hosts the TCP server.
|
Port |
You can enter a port number to override the port number
that is specified in the Settings tab.
Important: You might have to enter a port number in this field
if the port number specified in the Port field
in the Settings tab is being used by a different
program or process on the physical TCP server.
For more information, see Virtualizing TCP. |
The Socket Options settings help you to specify options that will be set on an accepted socket.
For information about the Socket Options settings, refer to Table 3.
Select the Generate message on connection check box if you want Rational Integration Tester to generate a message with an empty body and a messageType of 100 in the header when a connection is accepted.
In the Type list, click an option.
Option | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
All Available Bytes |
This option is the default, but use it only for initial investigation when the format of the data is unknown. Important: The role of a packetizer for inbound data is to split
the stream into meaningful messages. This packetizer treats all of
the data available in a single read as the "meaningful message" to
pass on. A single read can contain multiple messages or a partial
message, which is why this packetizer is not suitable for regular
use. For example, a message that contains 1124 bytes might be received
as a packet of 1024 bytes followed by a packet of 100 bytes (and this
packet might also contain the start of the next message).
|
||||||||||||||||||||||||
Split |
Click this option if you want to use the packetizer settings to split the data stream into packets by using a delimiter that is configured by you. Clicking this option
displays the following controls on the Packetizer tab:
|
||||||||||||||||||||||||
Length |
Click this option if you want the packetizer settings to be used to split length-based data according to a fixed length or a dynamic length that is encoded in the packet. For dynamic lengths, the position can be specified in relation to a known identifier or as a fixed offset from the start of the message. Important: If you set a length of 0, the packetizer passes all
data from a single read, which might not be a complete message. This
behavior is the same as if you use All
Available Bytes.
Clicking this option displays
the following controls in the Packetizer tab:
|
||||||||||||||||||||||||
Delimited |
Click this option if you want the packetizer settings to be used to extract data that is designated by a start token and an end token. Clicking this option displays the following
controls in the Packetizer tab:
Start and end tokens can accept representations of certain
non-printable characters. The following table lists these characters:
|
||||||||||||||||||||||||
ISO 8583 |
Click this option if you want the packetizer to break up the data stream into an ISO 8583 message based on the ISO 8583 schema that is selected by you. Clicking this option
displays the following controls in the Packetizer tab:
|
||||||||||||||||||||||||
SWIFT |
Click this option if you want the packetizer settings to be used to break up the data stream into a SWIFT message that is based on simple SWIFT rules. Clicking this option displays only the Update outbound message with packet details below check box on the Packetizer tab. Select the Update outbound message with packet details below check box if you want the packetizer to update outbound messages with the relevant packet information. |
||||||||||||||||||||||||
Token |
Click this option if you want to use the packetizer settings to extract data that is designated by a start token and an end token and to extract more bytes of data after the end token. Clicking this option displays the following controls
on the Packetizer tab:
Tip: Start and end tokens can accept representations
of certain non-printable characters. For information about the use
of non-printable characters, refer to Table
9.
|
Field | Description |
---|---|
Use SSL | Select this check box to enable security for the transport. Selecting the check box makes the other controls on the SSL tab available. You can enable security for Testing (Client) or for Virtualization (Server) or both. |
Server certificates to trust | All available identity stores are displayed in the drop-down menu. You can select
one of the following menu items:
|
Client identities to give to server | All available identity stores are displayed in the drop-down menu. If you use
mutual authentication, a suitable identity is selected from the chosen identity store. You
can select one of the following menu items:
|
Certificate source | All available identity stores are displayed in the drop-down menu. You can select
one of the following menu items:
|
Signed by | If you chose Generated in the Certificate source field, this field holds the location of a certificate within the Rational Integration Tester installation directory that is used to generate the new certificate. This is a read-only field. |
Identity | If you specified an identity store in the Certificate source field, use this field to specify the alias of a key in that identity store. |
Certificate Authorities a stub will trust | All available identity stores are displayed in the drop-down menu. You can select
one of the following menu items:
|
Override default protocols | If you are required to use a specific version of the secure sockets protocol, such as SSLv2 or TLSv1.2, enter that algorithm name here. For a complete list of algorithms, see Standard Algorithm Name Documentation. |
Field | Description |
---|---|
Recording mode | The following options are available:
|
The new physical TCP server resource is added to your Rational Integration Tester project.
The following tables show the interaction of the length delimiter type, Length includes prefix option, and Propagate prefix option. For Fixed Length delimiter type, the packetizer makes no changes in the data from the stream.
Length includes prefix | Propagate prefix | Incoming stream | Data received |
---|---|---|---|
false | false | abcd05Hello | Hello |
false | true | abcd05Hello | abcd05Hello |
true | false | abcd11Hello | Hello |
true | true | abcd11Hello | abcd11Hello |
Length includes prefix | Propagate prefix | Incoming stream | Data received |
---|---|---|---|
false | false | len=05Hello | Hello |
false | true | token1=xxxlen=05Hello | token1=xxxlen=05Hello |
true | false | len=11Hello | Hello |
true | true | token1=xxxlen=21Hello | token1=xxxlen=21Hello |
Length includes prefix | Propagate prefix | Incoming stream | Data received |
---|---|---|---|
false | false | 05Hello | Hello |
false | true | 05Hello | 05Hello |
true | false | 11Hello | Hello |
true | true | 11Hello | 11Hello |
Length includes prefix | Propagate prefix | Data in stream | Outbound message |
---|---|---|---|
false | false | Hello | \0\0\0\005Hello |
false | true | abcd00Hello | abcd05Hello |
true | false | Hello | \0\0\0\005Hello |
true | true | abcd00Hello | abcd11Hello |
Length includes prefix | Propagate prefix | Data in stream | Outbound message |
---|---|---|---|
false | false | Hello | len=05Hello |
false | true | token1=xxxlen=00Hello | token1=xxxlen=05Hello |
true | false | Hello | len=11Hello |
true | true | token1=xxxlen=00Hello | token1=xxxlen=21Hello |
Length includes prefix | Propagate prefix | Data in stream | Outbound message |
---|---|---|---|
false | false | Hello | 05Hello |
false | true | 00Hello | 05Hello |
true | false | Hello | 11Hello |
true | true | 00Hello | 11Hello |