Professional Documents
Culture Documents
Logistics Interface Connection Ways
Logistics Interface Connection Ways
Logistics Interface Connection Ways
Connection Ways
Date: 21.04.2022
Copyright
This work and its content (text, photos and drawings) are protected by copyright. The
copyright owner is Jungheinrich AG, headquartered in Hamburg, Germany.
Reproduction in any form (photocopying, scanning, etc.), editing, distribution,
translation or any other type of commercial exploitation is prohibited.
Jungheinrich Aktiengesellschaft
Friedrich-Ebert-Damm 129
22047 Hamburg
Page 2 of 14
Index
1 Characteristics of the logistics interface ...................................... 4
2 IT infrastructure .............................................................................. 7
Page 3 of 14
1 Characteristics of the logistics interface
The logistics interface is a versatile communication interface and thus connects your
machines and processes in the warehouse to intelligent systems. It enables simple
and efficient communication between Jungheinrich trucks, warehouse equipment and
warehouse management software, such as the Jungheinrich Warehouse Management
System (WMS) or alternatively any host system.
Page 4 of 14
1.2 Server installation with Modas Client Bridge
In that case, the Jungheinrich Logistics Interface runs on a server in the internal
customer network and transmits the driving instructions to the respective vehicles. For
the transmission, a WLAN-to-ethernet converter (client bridge) is installed on the
vehicle.
LAN
Hardware
WLAN
Software
Modas Host
Host system Logistics Interface Truck
Client system
server (installed as service) control
Bridge client
WLAN
Software
Logistics Interface
Host system server Control
(installed as a service)
Page 5 of 14
1.4 WLAN infrastructure
To connect the vehicles, a functioning WLAN infrastructure must be available in the
relevant areas.
If you have any questions or if you are interested in our services regarding WLAN
(analysis of existing infrastructure, implementing a new solution, etc.), please contact
our colleagues from system components WMS (LS-Sales-RDT@jungheinrich.de).
Page 6 of 14
2 IT infrastructure
The IT infrastructure requirements depend on the solution used.
RAM Min 1 GB
Page 7 of 14
2.2 Server
In order to use the Logistics Interface as a service on a server, the following system
requirements for the server must be met:
Availability High-available
Page 8 of 14
3 Standard connection options
Lift/Paternoster racking -
liftNavigation - ETV, ETM
driveNavigation - ECE
warehouseNavigation
AGV
TCP/IP ● ● ● ●
File transfer ● ● ● ●
connection options
Database exchange
table
● ● ● ●
App
File transfer
Database exchange
○ ○ ○ ○ ● ● ●
Server
table
Web service with
WSDL
○ ○ ○ ○ ● ● ●
REST-Interface ○ ○ ○ ○ ● ● ●
SAP-specific** ● ● ● ● ● ● ●
Symbols: = available, = only on request
Footnotes: *only for acknowledgements to the host system, **additional costs
Page 9 of 14
3.1 Technical connection options
For more information on the standard connection options including examples on
standard protocols, please refer to the corresponding detailed documentations. If
needed, we will gladly make these documents available to you and provide support
and advice.
3.1.1 TCP/IP
The host system (server or client) can transmit data to the Logistics Interface via a
standard socket connection. The port can be freely selected. The Jungheinrich
Logistics Interface confirms the incoming data.
There is a special type of file transfer with web-based host system clients. The files for
the data exchange are directly generated with a JavaScript command, which is
embedded in your websites. The command is executed on the radio data terminal
within the browser. There, the data of the Jungheinrich Logistics Interface is written
into a text file.
Page 10 of 14
3.1.3 Telnet
Telnet-based host systems can be connected to the Jungheinrich Logistics Interface
by reading the data stream.
For this option, the Ivanti TE Client is a prerequisite. Supported Telnet protocols are
IBM5250, VT220 and VT100. In addition, the storage location and the vehicle action
must be clearly identifiable from the data stream. Please note that this option is not
available in case of server installations.
Page 11 of 14
3.1.6 REST-Interface
The order data is exchanged via REST. Jungheinrich provides a REST endpoint, to
which multiple clients can connect.
3.1.8 SAP-specific
Connection Description
Page 12 of 14
Specific maintenance transactions are used for
configuring the extension.
Page 13 of 14
4 Extract of successfully connected systems
0-9 I P
20-20 Technologies - inSight IBM - ISeries POINT-ERP4
A ICZ - OSIRIS Proalpha
ABAS iFD-LVS proLogistik
AIVE Inconso Prosytec
AJE Info Nova - IFAS 3000 PSI
ALTESSE Infor Q
Appolo Inform Rack QAD
AUTAJON IBS - Dynaman Quantum - Qguar WMSpro
Axelot - 1C-Logistics ISAH - Komexo R
Axia ISTEC - PLS Reply - Click Reply
B J S
bb logistic systems - Accubo JDA - RedPrairie S&P - SuPCIS
BOB JOTA - Cassis S+R SILOG
C Jungheinrich SAFELOG
Centric - Locus K Sage Bäurer - WinCarat
Chainware Kallipso Salomon - Wamas
CIM - PROLAG World Kardex Mlog SAP - EWM
Compram systeemhuis - Cube2 Klug - iWACs SAP - TRM
Consafe Logistics - Astro Knapp - KeySoft SAP - WM
CWMS3000 L SIVAplan
D L-mobile Solvo
Dematic Distribution Director Log:IT - dilos SSI Schäfer - Noell
dsp Logiconcept T
E Logis - ITLS Tecsys
Ehrhardt+Partner Logistix - Logx TGW - C-ILOG
Eldicon Logos Tical
Exact Lunzer & Partner TSL LOG
G M U
GUS - Charisma Made4net - scexpert ULMA
H Manhattan V
Hades - Reflex Mantis - Logistic Vision Suite van Boxtel
HighJump MFG Pro VIGO Software
Microsoft - Navision Vitron - LXE
Mobisys W
O WANKO - PRAMAG
Optimum - Aberon Wizard
Wühler & Gebauer
X
XPPS
Page 14 of 14