Intermec CK31 ユーザーガイド

ページ / 114
Chapter 2 — Using the Intermec Gateway in a Native Environment 
Intermec Gateway User’s Guide 
25 
How the Native environment works: 
1
 
A Native client sends data to the Intermec Gateway on the 
Intermec Application Server. 
2
 
The Intermec Gateway forwards this data to the Native host 
(serial or socket). 
3
 
Information from the Native host is sent back to the device 
via the Intermec Gateway. 
Native applications are proprietary TE applications. The 
Intermec Gateway can communicate with a Native async serial 
host and with other IP hosts through the Native sockets 
interface. 
Determining the Maximum Number of Sessions Supported 
The Intermec Gateway supports up to 300 simultaneous 
connections, which may be a combination of UDP Plus and 
WTP devices connecting to a combination of the Native async 
serial host or IP hosts through the Native sockets interface. You 
can configure more than 300 devices, but only the first 300 
attempting to connect will be allowed to connect.  
These restrictions apply: 
•  The Intermec Gateway supports up to 127 simultaneous 
WTP connections. If a WTP device is configured to support 
two sessions (for example, connecting to two hosts), it uses 
two of the 127 possible connections. 
•  The Native async serial host supports a maximum of 127 
connections. 
About the Native Async Serial Host 
If your host application was written to work with WNAS or 
legacy serially-connected controllers (RD(B)4030, RC3250, 
6910 IGAP), it should also work with the Intermec Gateway. 
That is, you do not need to make any changes to your existing 
Native TE host applications.  
For help updating your Native applications, see the Native 
Terminal Emulation Programmer’s Guide
 (P/N 977-055-006).