PALMS is a web service-based SOA architecture that allows configurations for actions to be performed before and after calls to business components. It supports incoming interfaces through a daemon or web service calls, as well as outgoing interfaces. For incoming interfaces through the daemon, a protocol converter runs on the daemon and passes data to a business component. For web service incoming calls, the protocol conversion occurs on the caller side. Outgoing interfaces can be configured to run protocol converters and communicators after a business component to integrate with external systems like PLC devices.

1. Approach – PALMS WMS & ERP Integration

2. Agenda
• PALMS - Architectural Overview
• PALMS – Incoming Interface
• Integrated through Daemon
• Integrated through WebService Call
• PALMS – Outgoing Interface

3. PALMS - Architectural Overview
PALMS-WMS is based on Web Service Based SOA Architecture. System provides ability to define
configurations for Actions to be performed “Before” & “After” call of Business Component.
PALMS (WMS)
Daemon Web Service Bus
Web Web
Service-1 Service-2
Configuration for Actions to be performed
All Business Components are File Pre-Component Config.
System “Before” Component Call
instantiated through either
4.Web Service Call Business Components
5.Daemon Call (Polled Folder)
Compone Compone
nt - 1 nt - 2
Configuration for Actions to be performed
Post-Component Config. “After” Component Call
With this Architecture, we shall now look at a typical configuration for interfacing with an external ERP on
the “Before” side and with a PLC Device on the “After” side.

4. Incoming ERP Interface (through Daemon)
Pre Component Configuration for an incoming Data Interface through PALMS Daemon is depicted below:
Some ERP PALMS (WMS)
Create
Allocate Daemon Web Service Bus
Sales Some Data
Stock
Order WS/GeneratePickSlip
Interchange
Configuration for Actions to be performed
Format File Pre-Component Config.
System “Before” Component Call
Protocol Converter
Pre-Component Configuration
Business Components
System Provides a “Hook” to
easily interface with Business Component/GeneratePickSlip
Components without making any
changes to PALMS Solution Post-Component Config.
Component Name Pre Component Process Input Folder
GeneratePickingSlip SomeERP-PALMS-ProtocolConverterForGeneratePickingSlips.dll InputForPickingSlipGeneration

5. Incoming ERP Interface (through WebService)
Pre Component Configuration for an incoming Data Interface through Web Service is depicted below:
Some ERP
PALMS (WMS)
Protocol Converter
Create
Allocate
Daemon Web Service Bus Stock
Sales
PALMS Order
WS/GeneratePickSlip
Web Service
File Pre-Component Config. Protocol
System
Business Components
Component/GeneratePickSlip
System Provides a “Hook” to
easily interface with Web
Post-Component Config.
Services without making any
changes to PALMS Solution.
Note: For calling WebServices, Protocol Conversion must happen at the Caller End. Web
Services must be called using its specific Protocol.

6. Outgoing Interface to PLC
Post Component Configuration for an outgoing Data Interface is depicted below:
Some ERP Some ERP
PALMS (WMS)
Protocol Converter
Create
Allocate
Create
Allocate Daemon Web Service Bus Stock
Sales
Sales Some Data PALMS Order
Stock
Order WS/GeneratePickSlip
Interchange Web Service
Format File Pre-Component Config. Protocol
System
Protocol Converter
Business Components
System Provides a “Hook” to
easily interface Component Component/GeneratePickSlip
Outputs without making any Some PLC
changes to PALMS Solution Post-Component Config. To & Fro
PLC Communicator
Communication
Post-Component
Configuration
Component Name Post Component Process
GeneratePickingSlip PALMS-SomePLC-ProtocolConverterForGeneratePickingSlips.dll

7. Thank You