Logistics Interface Connection Ways

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 14

Logistics Interface

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

Telephone: +49 (0) 40 6948-0


Fax: +49 (0) 40 6948-1777
www.jungheinrich.de

Logistics Interface | Connection Ways 01.10.2020

Page 2 of 14
Index
1 Characteristics of the logistics interface ...................................... 4

1.1 App installation on the radio data terminal ........................................ 4


1.2 Server installation with Modas Client Bridge ..................................... 5
1.3 Server installation ............................................................................. 5
1.4 WLAN infrastructure ......................................................................... 6

2 IT infrastructure .............................................................................. 7

2.1 Radio data terminals ......................................................................... 7


2.2 Server ............................................................................................... 8

3 Standard connection options ........................................................ 9

3.1 Technical connection options.......................................................... 10


3.1.1 TCP/IP ............................................................................................ 10
3.1.2 File transfer ..................................................................................... 10
3.1.3 Telnet.............................................................................................. 11
3.1.4 Database exchange table ............................................................... 11
3.1.5 Web service with WSDL ................................................................. 11
3.1.6 REST-Interface ............................................................................... 12
3.1.7 Keyboard buffer .............................................................................. 12
3.1.8 SAP-specific ................................................................................... 12

4 Extract of successfully connected systems ............................... 14

Logistics Interface | Connection Ways 01.10.2020

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.

Depending on which product is to be connected, the logistics interface can be installed


as a service on a server or as an app on a radio data transmission terminal.

1.1 App installation on the radio data terminal


In this case, a radio data terminal is mounted on the truck. It is assumed that an active
WLAN infrastructure exists, which can be used for the data transfer. It can thus be
ensured that the host system server can transmit data to the forklift truck via the
Jungheinrich Logistics Interface. The Jungheinrich Logistics Interface runs in the
background.

Installation of the Logistics Interface app on the radio data terminal

Logistics Interface | Connection Ways 01.10.2020

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.

Installation of the Logistics Interface app with Modas Client Bridge

Warehouse management Logistics Interface Client Bridge Devices


system (host system)

LAN
Hardware

WLAN
Software

Modas Host
Host system Logistics Interface Truck
Client system
server (installed as service) control
Bridge client

1.3 Server installation


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.

Installation of the Logistics Interface on a server

Warehouse management system (host system) Logistics Interface Device


LAN
Hardware

WLAN
Software

Logistics Interface
Host system server Control
(installed as a service)

Logistics Interface | Connection Ways 01.10.2020

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).

Logistics Interface | Connection Ways 01.10.2020

Page 6 of 14
2 IT infrastructure
The IT infrastructure requirements depend on the solution used.

2.1 Radio data terminals


In order to use the Logistics Interface as an app on a forklift truck, radio data terminals
must be available.

These terminals need to meet the following system requirements:

Technical requirements for radio data terminals

Microsoft Windows 10 (Pro, Enterprise), Windows 10


IoT Enterprise starting from version 1607
Operating system
On request: XP, XP Embedded, Windows 7, 8, 8.1., 10, Embedded
Standard 2009, 7, 8

Resolution of the display 1024 x 768 Pixel

Framework Microsoft .NET Framework 4.7.2

Interface Serial interface (RS232, with 9-pin D-sub connector)

Processor performance Min 1 GHz

RAM Min 1 GB

Min 1 GB free storage space for the Logistics


Free memory space
Interface, 2 GB recommended

An available USB port for installation and


Other requirements
maintenance

Logistics Interface | Connection Ways 01.10.2020

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:

Technical requirements of the server

Windows Server 2008 / RS2 SP1, 2012 / R2, 2016 or


Server
2019 (32 Bit or 64 Bit)

Framework Microsoft .NET Framework 3.5 and 4.7.2

Processor performance 3.2 GHz recommended (at least 2.4 GHz)

RAM 8 GB recommended (at least 4 GB)

Free memory space 20 GB recommended (at least 14 GB)

Via TCP to and from endpoints on ports to be specified


Network connection Separate subnet for server and warehousing
equipment is recommended

Remote access For installation, maintenance and support

Availability High-available

Full access rights in the file system


• for the user that is used to start the Logistics
Write permissions Interface
• to the Jungheinrich directory
• to optional data exchange directories

Logistics Interface | Connection Ways 01.10.2020

Page 8 of 14
3 Standard connection options

Automated Guided Vehicle -


Under Pallet Carrier - UPC

Lift/Paternoster racking -
liftNavigation - ETV, ETM

driveNavigation - ECE
warehouseNavigation

Mobile pallet racking


LRK/PRK

AGV
TCP/IP ● ● ● ●
File transfer ● ● ● ●
connection options

Database exchange
table
● ● ● ●
App

Web service with


WSDL
● ● ● ●
Telnet ● ● ● ●
REST-Interface ● ● ● ●
Keyboard buffer ● ● ● ●
TCP/IP ○ ○ ○ ○ ● ● ●
○ ○ ○ ○ ● ● ●
connection options

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

Logistics Interface | Connection Ways 01.10.2020

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.

3.1.2 File transfer


The host system and the Jungheinrich Logistics Interface exchange a text file.

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.

Logistics Interface | Connection Ways 01.10.2020

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.

3.1.4 Database exchange table


Information is exchanged between the host system and the Jungheinrich Logistics
Interface by use of a database table.

Supported database systems are MS-SQL, SQLite and MS-Access.

3.1.5 Web service with WSDL


The order data is exchanged via a WSDL service. Jungheinrich provides a standard
WSDL. In this WSDL a function call is defined which accepts any text and reports back
a call confirmation.

Logistics Interface | Connection Ways 01.10.2020

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.7 Keyboard buffer


Acknowledgements to the host system are carried out by means of a keyboard wedge.
The defined data content is written into the keyboard buffer and output at the current
position of the cursor. Please note that this option is not available in case of server
installations.

3.1.8 SAP-specific
Connection Description

All order data is transferred by using a synchronous


Remote Function Call (sRFC). The Logistics
Interface provides the available function calls. SAP
SAP sRFC calls these functions and transfers all necessary
data as parameters. Replies to the SAP can be
transferred in the same way, the difference being
that SAP has to provide the needed functions.

The integrated extension for SAP EWM uses a


LRKConnect for SAP EWM client-based TCP/IP connection, available from SAP
EWM version 9.4. The extension is imported via
SAP transport instruction into the customer system.

Logistics Interface | Connection Ways 01.10.2020

Page 12 of 14
Specific maintenance transactions are used for
configuring the extension.

TCP/IP, file transfer, WSDL web service, Telnet as


well as acknowledgements via keyboard buffer are
Other connections
available as technical connection options,
depending on the used SAP system.

Logistics Interface | Connection Ways 01.10.2020

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

Logistics Interface | Connection Ways 01.10.2020

Page 14 of 14

You might also like