Running Peer-to-Peer Applications
8-13
8
The DCS 300 supports only requester (client) connections. The remote application
initiates both sockets.
For help, see the
DCS 300 Technical Reference Manual
.
How the DCS 300 Communicates With Applications
To use the NetComms, you must first configure the DCS 300 for TCP/IP
communications. For help, see “Configuring the Ehternet Card for TCP/IP” in
Chapter 3.
Applications acknowledge the DCS 300 directly by placing data in an ACK transaction
and by using the Inter system transaction to control their interactivity with the
DCS 300.
•
The server send NetComm is responsible for creating the application IPC channel
and forwarding any data in that channel to the application.
•
The server receive NetComm is responsible for opening the Receive (input)
channels of the message handler and for sending data that is received from the
application through the network connection to the message handler.
When the DCS 300 is turned on, it detects when TCP/IP is being used and it starts the
appropriate NetComms.
If you use the wrong syntax or do not supply all the required startup arguments, an error
message appears in the error log.
The following figure shows the NetComms communicating directly with applications.
NetComms use IPC channels to exchange data with other server components and they
use sockets to exchange data with a TCP/IP application.
Summary of Contents for DCS 300
Page 1: ...P N 067296 005 User s Manual DCS300 ...
Page 4: ...DCS 300 User s Manual blank ...
Page 16: ...DCS 300 User s Manual ...
Page 22: ...DCS 300 User s Manual ...
Page 23: ...Getting Started 1 ...
Page 24: ...DCS 300 System Manual blank ...
Page 42: ...blank ...
Page 43: ...Learning About the DCS 300 2 ...
Page 44: ...DCS 300 User s Manual blank ...
Page 68: ...blank ...
Page 69: ...Connecting to the Upline Network 3 ...
Page 70: ...DCS 300 System Manual 3 2 blank ...
Page 94: ...blank ...
Page 95: ...Connecting to the Intermec RF Network 4 ...
Page 96: ...DCS 300 System Manual blank ...
Page 134: ...blank ...
Page 135: ...Connecting to the 9180 and the Intermec CrossBar Network 5 ...
Page 136: ...DCS 300 System Manual blank blank ...
Page 158: ...DCS 300 System Manual blank ...
Page 159: ...Running Data Collection Browser 6 ...
Page 160: ...DCS 300 System Manual blank ...
Page 171: ...Running Terminal Emulation 7 ...
Page 172: ...DCS 300 System Manual blank ...
Page 209: ...Running Peer to Peer Applications 8 ...
Page 210: ...DCS 300 System Manual blank ...
Page 232: ...blank ...
Page 233: ...Running Terminal Sessions 9 ...
Page 234: ...DCS 300 System Manual blank ...
Page 258: ...DCS 300 System Manual 9 26 blank ...
Page 259: ...Running Screen Mapping 10 ...
Page 260: ...DCS 300 System Manual 10 2 blank ...
Page 269: ...Running Screen Mapping 10 11 10 Screen 3 Screen 4 Main Host Screen Screen 5 ...
Page 333: ...Troubleshooting 11 ...
Page 334: ...DCS 300 System Manual blank ...
Page 372: ...blank ...
Page 373: ...Specifications and Other Helpful Information A ...
Page 374: ...DCS 300 System Manual B 2 blank ...
Page 391: ...Upgrading the DCS 300 and Devices B ...
Page 392: ...DCS 300 System Manual blank ...
Page 411: ...How the DCS 300 Routes Transactions C ...
Page 412: ...DCS 300 System Manual blank ...
Page 430: ...blank ...
Page 431: ...Index I ...
Page 432: ...DCS 300 System Manual I 2 blank ...