4.5ebMS Processing Mode

4.5.1

Outline of processing mode

Figure 4.5.1 shows outline of ebMS processing mode in NACCS.
When using this processing mode, it is necessary to incorporate server certificate and certificate forelectronic signature which are provided by the NACCS Center into the user’s ebMS server.
For sending e-mail, refer to "4.6.1 e-mail".

Data 1
Data 2
Data 3(1) ebMS2.0
Processing request message

User’sebMS server

NACCS EDImessage(2) ebMS2.0
Processing result message

Data 1Core
processingsystem

NACCS’sebMS server

Data 2

NACCS EDImessage

Data 3

NACCS Center server

User system

Figure 4.5.1 Outline of ebMS Processing Mode
(1) A user creates and sends a NACCS EDI message or a XML message that contains necessary
data segments for a transaction from the user system to the NACCS’s ebMS server overHTTPS protocol.
(2) The message transmitted to the NACCS’s ebMS server is transferred to the core processingsystem. The message is processed and a response message is sent to the NACCS’s ebMS
server once again. NACCS’s ebMS server returns a processing result message to the usersystem over HTTPS protocol. Therefore, the user system should always be activated.

4-5-1

In addition, Figure 4.5.2 shows outline of ebMS function.
By d ivid ing a message, this ena bles p rocessing req uest messag es to b esent one by one to the core processing system. In addition to that, whena processi ng request message is a XML message, the message will beconverted to a NA CCS-EDI messa ge.

Multiple p ayl oad function e nables multiple processin grequest messages to be combined as one message tosent.

Processing R equest
Message 1
Processing R equest
Message 2
Processing R equest
Message 3

Processing R equest
Message 1

ebMS2.0

Messag e con trol pro cessing mode used in
NACCS uses inte ractive processin g mod e.

NACCS EDI Message
Processing R equest

Message 1

Processing R equest
Message 2
Processing R equest

Processing R equest
Message 3

Message 2

Processing R equest
Message 3

This mode en able processi ng resu lt messag es to b e
received one by o ne fro m NACCS at real time.

NACCS EDI Message

ebMS2.0
Processing R esult
Message 1

Processing R esult
Message 2

Processing R esultMessage 1

Processing R esult
Message 1

Processing R esult
Message 2

Processing R esult
Message 2

Processing R esult
Message 3

Processing R esult
Message 3

Processing R esult
Message 3

ebMS server

Core processing systemebMS processing mo deUser system

NACCS Center server

Figure 4.5.2 Outline of ebMS Processing Mode

4.5.2

Details of the communications protocol

For communications protocol used in ebMS processing mode, TCP/IP is used for the network andtransport layers, and HTTPS for the upper layers, and data transmission/receiving is carried out using
ebMS2.0. In addition, multiple blocks of data can be transmitted in a batch.1
In addition, in NACCS, when a ｓmultiple payload function is used, the maximum message length
should be 10 MB (the same as EDIFACT multiple B/L message length), and the maximum number ofmessages for payload should be 99 messages (according to NACCS EDIFACT protocol).
Also, when using a multiple payload function, avoid a mixture of NACCS-EDI messages and XML
messages.
(1) Outline of ebMS2.0
For ebMS processing mode used in ebMS server, ebXML Message Service v2.0 (ebMS2.0) andebXML CPPAv2.0 are used.
ebMS (ebXML Message Service) refers to specifications of transmission of messages used forelectronic commerce between companies via Internet. This is composed based on SOAP. In
ebMS processing mode, user carries out communication using CPA distributed by the NACCS
Center. (For details of CPA, refer to "4.5.4 (3) Setting of CPA")
For details of ebXML Message Service v2.0 (ebMS2.0) and ebXML CPPA v2.0, refer to thefollowing specifications opened to the public by OASIS2.
• ebXML Message Service Specification v2.0, OASIS Standard(http://www.oasis-open.org/committees/ebxml-msg/documents/ebMS_v2_0.pdf)• ebXML CPPA v2.0, OASIS Standard(http://www.oasis-open.org/committees/ebxml-cppa/documents/ebcpp-2.0.pdf)
Table 4.5.1 shows the list of functions of ebMS2.0 used in ebMS processing mode.

When sending multiple processes all together, the multiple payload function of ebMS2.0 is necessary.
Organization which carries out activities to promote standard technologies for XML (http://www.oasis -open.org/) and specified
ebXML.
124-5-2

Table 4.5.1 List of Functions of ebMS processing mode
Description of function
ebMS
Remarks
Processing
Mode
Security(TLS)
Is TLS used for
Used
Only server
communication?
authentication isused
Security(Signature)
Is digital signature used inUsed
XML signaturecommunication?
(digital signature inXML format)
Error HandlingIs error response returned
Used
Errorlist
during error?
SyncReply
For return ofNot used
Asynchronous(synchronized
Acknowledgment
response mode
response)(acknowledgment of receipt),(Acknowledgment
is it returned in the sameis sent in separate
session as that of ebXML
session)received?
Reliable messaging
Are systems such as
UsedHigh-reliability
acknowledgment of receipt,
messaging
retry, and de-duplication
used?
MessageStatusService Is inquiry about message
Not usedstatus used?
MSH Ping Service
Is inquiry about status of
Not usedebMS execution modules
used?
MessageOrderIs arrival order at message
Not used
sender side guaranteed?
(used when the sender'ssystem has multiple ebMSs)
Multi-HopIs data transfer between
Not used
multiple servers used?
ebMS function

4-5-3

4.5.3Messages used in ebMS processing mode

ebMS processing mode carries out transmission/receipt processes using high-reliability messaging
provided by ebMS2.0.
(1)

Messages used in ebMS processing mode
The following shows ebMS messages used in ebMS processing mode.
• Application messages
Processing request message and processing result messages, etc.
• ebMS receipt confirmation message (Acknowledgement)
Confirmation of receipt of messages in ebMS processing mode
• ebMS error notification message (ErrorList)
Notification of error in ebMS processing mode

4-5-4

(2) ebMS2.0 Message format
ebMS2.0 message format is regulations where SOAP message is extended. In addition,execution module which mounts ebXML Message Service specifications is called ebXML MSH(message service handler).
Figure 4.5.3 shows ebMS2.0 message format.
Communications protocol envelope (HTTP)MIME envelope (SOAP with appendix)
MIME part
SOAP envelope
SOAP header (XML document)
eb:MessageHeader element

eb:ErrorList element
eb:SyncReply element
ebXML header
container

eb:AckRequested element

eb: Acknowledgment element

Signature element

ebXML message

SOAP body (XML document)
eb:Mainfest element

MIME partPayload

ebXML payload
handler

Figure 4.5.3 ebMS2.0 message format

4-5-5

4.5.4

Setting for ebMS processing mode

(1) Message type
Table 4.5.2 shows message types used in ebMS processing mode, necessity of digital signature
and Acknowledgment /ErrorList.
Table 4.5.2 Message types used in ebMS processing mode
Message TypeDigital signature
Acknowledgment/ErrorList
Procedure message
Necessary
Necessary
NACCS EDI message
Procedure message
Necessary
Necessary
XML format message
Processing Result
Necessary
Necessary
MessageAcknowledgment
Necessary
Unnecessary
Errorlist
UnnecessaryUnnecessary(2) Service/Action element
Communication conditions (Message Type) which are according to CPA are specified bydefining Service elements and Action elements. In actual transactions, both elements are written
in SOAP header in the following manner.
<eb:Service eb:type="XXX">XXXXX</eb:Service><eb:Action>XXXXX</eb:Action>
When Service and Action are specified, each element in DeliveryChannel, Packaging, Transport,
and DocExchange, which are according to CPA, will be uniquely determined and communication
conditions will be identified based on those details.
( For details of each element, refer to "4.5.4 (3) Setting of CPA")
Table 4.5.3 shows Service elements and Action elements used in ebMS processing mode.
Table 4.5.3 Service/Action Used in ebMS Processing Mode
Message TypeServiceAction
Procedure message
urn:NACCS:ICS:BusinessService
NACCS-EDI
NACCS EDI message
Procedure message
urn:NACCS:ICS:BusinessService
NACCS-XMLXML format message
Processing Result
urn:NACCS:ICS:BusinessService
NACCS-Result
Message
Processing Result
urn:NACCS:ICS:BusinessService
NACCS-ResultReq
Request Message
Acknowledgment
urn:oasis:names:tc:ebxml-msg:service
Acknowledgment
Errorlisturn:oasis:names:tc:ebxml-msg:service
MessageError

4-5-6

(3) Setting of CPA
Table 4.5.4 shows an example of setting of CPA used in ebMS processing mode.

Cpaid

PartyInfopartyName

PartyId

Table 4.5.4 Setting of CPA Specified in ebMS Processing Mode (Example)
Item to be set
Details of setting
Setting value
CPA ID used fordesignated bycommunication
NACCS
CenterInformation of eachtransactor
Name of transactor
designated by(Unique in CPA)
NACCS
CenterTransactor's identification ID
designated by(Unique in CPA)NACCSCenter

CollaborationRole
ServiceBinding
ServiceCanSendCanReceive

This Party Action Binding
ActionBusiness Transaction Characteristics

is NonRepudiation Required

isNonRepudiationReceiptRequired
is Confidential
is Authenticatedis Authorization Required

Delivery Channel
Messaging Characteristics

Setting for messages used intransactions
Linking between services andcommunication conditions
Name of service

See Table
4.5.3.
Attribute of Action
Specified for(e.g.) For communications of each action.
Party 1 and Party 2, when
attribute of Action 1 is
specified as CanSend forParty 1 and CanRecieve forParty 2, in communication ofAction 1, Party 1 becomestransmission side and Party 2
becomes receipt side.
Linking between actions andcommunication conditions
Name of action
See Table
4.5.3.
Transaction characteristics
Whether using XML signaturewhen parent element ofaction is used ?
Whether adding XML
signature to acknowledgmentof receipt(Acknowledgment) ?
Whether encrypting
messages ?
Whether adding XML
signature to identify sender ?
Is authentication of sendernecessary?
Linking between actions andTransport / DocExchange
Characteristics in exchangeof messages

4-5-7

true

true

transienttransienttrueItem to be set
sync ReplyModeackRequested
ackSignature Requested

duplicate Elimination

Transport
Transport Protocol
VersionTransport Client Security
Transport Security Protocol
VersionDocExchange

Details of setting
Whether requesting
synchronous mode
response ?
Whether requesting
acknowledgment of receipt ?
Whether adding XML
signature to acknowledgmentof receipt ?
Whether carrying out
duplication of messages ?
Communications protocol anddestination URL
Name of communications
protocolVersion information
Security during forwarding
Name of security protocol fortransport layer
Version information

Retries

Conditions for exchange ofmessages(When there are multiple
Actions in one CPA seen thissystem, DocExchange is
specified for each conditions
for exchange)
Setting for sender andreceiver
Both DocExchanges directly
corresponding as sender /receiver of Action shouldhave the same setting)
Version information
Function to guarantee
messages
Number of retry

RetryIntervalInterval of retry

MessageOrderSemantics

Whether carrying out
guarantee of message
order ?
Retention period formessages

ebXMLSenderBinding
ebXMLReceiverBinding

versionReliableMessaging

PersistDuration

4-5-8

Setting valuenone

alwaysalwaysalways

HTTP
1.1
TLS
1.2

2.0

3 (standardvalue)
PT10M(standardvalue: every
10 minutes)
NotGuaranteed

PT1H(standardvalue: 1 hour)4.5.5

Message format and structure

When using ebMS processing mode, NACCS EDI messages and XML format messages which store
necessary information for procedures are stored in payload section. In addition, communications
protocol (HTTP) header, SOAP header, SOAP body, and communications protocol (HTTP) trailer areadded.
The message formats are outlined as follows:(1)

XML format message
Figure 4.5.4 shows outline of XML format messages (ebMS processing mode).

XML Format Message
Communications
Communications
protocol header
Protocol Trailer(HTTP Header)

SOAP header

SOAP body

XML message

Communications
Communications
protocol trailer
Protocol Trailer(HTTP header)Max. 700,000 bytes (Note)(Refer to "3 Message structure and format")

Figure 4.5.4 Outline of XML Format Message (ebMS Processing Mode)

For procedure subjected to XML format messages, refer to "Appendix Table 6.7 Subjected
Procedure List." In addition, message format / version are according to PAA (Pan Asiane-commerce Alliance) Standard/Superset Message Structure V2.0).

4-5-9

(2) NACCS EDI message
Figure 4.5.5 shows outline of the NACCS EDI message format (ebMS processing mode).

Communications
protocol header(HTTP header)

SOAPheader

SOAP body

Input (Output)
commo n field

Pro ced ure-by-proced ure fiel dCommunications
Communications
protocol trailer
Protocol Trailer(HTTP header)Max. 700,000 bytes (Note)(Refer to "3. Message structure and format")

Figure 4.5.5 Outline of NACCS EDI Message Format (ebMS Processing Mode)

Figure 4.5.6 shows the format of a message created when user of ebMS processing mode senda NACCS EDI message to the NACCS Center server.

Figure 4.5.6 Message Segmentation

4-5-10…

CR
LF

…

CR
LF

…

CR
LF

…

CR
LF

NACCS EDI Message
Input(Output)
Procedure-by-procedure fieldcommon field4.5.6

Procedure sequential processing

Figure 4.5.7 shows procedure processing sequence in ebMS processing mode.

User system

NACCS Center server

User’sebMS server

Procedure

NACCS’s ebMS
serverCore processing system

Transaction

Processing requestmessage(1) Sends a processing
request message.
Processing result
message(2) Returns a processing
result message.

Processing result message(transaction output message)(3) Returns a processing result message (forprinter) stored in the File Exchange Block.

File exchange
blockFigure 4.5.7 Example of Procedure Processing Sequence in ebMS Processing Mode
(1) User sends a processing request message where necessary fields for the procedure are input
to the NACCS Center server.
(2) A processing result message is returned from the NACCS Center server to the user system.
(3) When there is a transaction output message, the transaction output message will be returned
from the NACCS Center server to the user system.
In addition, when using multiple payload function, user receives processing result messages andtransaction output messages of the equivalent amount of procedures incorporated in Payload
section from the NACCS Center server in response to one processing request message (wheremultiple procedure messages are included in Payload section).

4-5-11