Customs Declaration Processing System Detailed User and ...

DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS
AND USE-CASE MODELS
Ref: PHASE V
External Systems
Data Integration Tier
Service Interface
Service Interfaces
Integration Service Gateways
Service
Gateways
MQ Series
CCN/CSI
Web
Service
WS Client CCN/CSI
MQ Series
Integration Tier
Data
Aggregation
Data Integration
BC
Integration Connectors
Web
MQ Series
Service
Data Integration
Components
Entity
Translators
Configuration
Components
Data Persistence Tier
Figure 4. Logical architecture – Data Integration Tier.
Though the above diagram of the Integration Tier allows for existence of multiple integration
connectors (MQ Series, Web Service, CCN/CSI) we expect and recommend that Web Services
shall be the dominant mechanism for communication between CDPS and applications from the
National Domain, and the External Domain.
Number Description
IA-0000 CDPs shall have a separate Integration Tier which shall isolate the internal logic
of CDPS from other software applications that CDPS needs to integrate with.
IA-0010 Technical requirements for the SOAP protocol are as follows:
IA-0020
IA-0030
• SOAP version 1.2
• Support for SSL an HTTPS protocols
• Support for WSDL files
All web services, both the ones implemented in CDPS and the ones implemented
in applications from the National Domain, External Domain and Common
Domain will be described in WSDL.
CDPS should support the use of a business process management (BPM) server
to integrate with applications and to automate and integrate business processes
within the National Domain, External Domain or with other NCAs. A typical
BPM will support a variety of connectors to communicate with different
software systems in a large enterprise, or across company boundaries.
Connectors to Web Services are provided by all BPM servers.
5.3.3 CDPS modules
5.3.3.1 Transit Control System (TCS)
Table 18: Integration Architecture requirements.
Page 152/276