The following example illustrates invoking the AS4 light client and pushing a puchase order and associated
README external payload to a remote server.
\
\java -jar fmsclient.as4.jar -h http://remotehost.com:8080/as4 -sc sc.xml -e send -pm as4push.pmode \
\ -from POService.flame.business -to POService.flame.business \
\ -enc flameserver \
\ -a 'filename:README;content-id:id-29996-2011-10-07-15:45:38;mimetype:text/plain; \
\ description:Compressed README' ProcessPurchaseOrder.xml
\
\ |
A successful message push should return a receipt as follows
\
\<?xml version="1.0" encoding="UTF-8" standalone="no"?>
\<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
\ <env:Header>
\ <eb:Messaging xmlns:eb="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/">
\ <eb:SignalMessage>
\ <eb:MessageInfo>
\ <eb:Timestamp>2011-10-07T13:45:46.144Z</eb:Timestamp>
\ <eb:MessageId>FMS-A-20111007-154542.442-0.5731733724663212@POService.flame.business< \
\ /eb:MessageId>
\ <eb:RefToMessageId>AS4-132DEA1D1BB-6990F@POService.flame.business</eb:RefToMessageId>
\ </eb:MessageInfo>
\ <eb:Receipt>
\ <ebbpsig:NonRepudiationInformation xmlns:ebbpsig= \
\ "http://docs.oasis-open.org/ebxml-bp/ebbp-signals-2.0">
\ <ebbpsig:MessagePartNRInformation>
\ <ebbpsig:MessagePartIdentifier/>
\ </ebbpsig:MessagePartNRInformation>
\ </ebbpsig:NonRepudiationInformation>
\ </eb:Receipt>
\ </eb:SignalMessage>
\ </eb:Messaging>
\ </env:Header>
\ <env:Body/>
\</env:Envelope>
\
\ |
The following example illustrates invoking
the AS4 client and pulling an
acknowledge puchase order from a remote server.
\
\java -jar fmsclient.as4.jar -h http://remotehost.com:8080/as4 -e pull -from POService.flame.business \
\ -to POService.flame.business -pm as4pull.pmode
\
\ |