本篇承接上集,完成整個整合方案的最後一塊拼圖:製造商端的 Order Processing Service。
這是一個以 Java 撰寫的服務,負責承接分銷商送來的採購訂單。它的職責可以濃縮成三步:
製造商應用程式包含下列業務實體:
| 類別 | 說明 |
|---|---|
| AddressEntity | 客戶或企業地址 |
| CustomerOrderEntity | 客戶訂單(採購訂單) |
| CustomerOrderDetailEntity | 每筆客戶訂單(採購訂單)的商品明細 |
| MessageQueueEntity | 訊息佇列項目,即採購訂單或訂單匯總 |
| OrderSummaryEntity | 訂單出貨匯總 |
| OrderSummaryDetailEntity | 訂單出貨匯總的商品明細 |
所有資料庫操作都透過 JdbcQuery 這個 helper 類別完成,另外還有兩個輔助類別:DateUtil 負責日期格式化,AppConfig 負責讀取組態參數。Amazon SQS 的功能則由 SqsDataProvider 類別封裝。
OrderProcessingService 依 AppConfig.properties 中設定的輪詢間隔處理採購訂單:先取得尚未出貨的訂單清單,再逐一處理。以下示範如何用 Java 從指定 SQS 佇列取回訊息清單。
protected ArrayList<HashMap<String, String>> getMessageQueueItems(String queueName) {
ArrayList<HashMap<String, String>> results = new ArrayList<HashMap<String, String>>();
try {
String accessKeyId = AppConfig.getProperty("AmazonAccessKeyID");
String secretAccessKey = AppConfig.getProperty("AmazonSecretAccessKey");
AmazonSQS service = new AmazonSQSClient(accessKeyId, secretAccessKey);
// 從佇列取訊息
ReceiveMessageRequest request = new ReceiveMessageRequest();
request.setQueueName(queueName);
request.setVisibilityTimeout(1);
ReceiveMessageResponse response = service.receiveMessage(request);
if (response.isSetReceiveMessageResult()) {
ReceiveMessageResult receiveMessageResult = response.getReceiveMessageResult();
// 逐一走訪所有訊息
List<Message> messageList = receiveMessageResult.getMessage();
for (Message message : messageList) {
HashMap<String, String> row = new HashMap<String, String>();
if (message.isSetMessageId()) {
row.put(COLUMN_ID, message.getMessageId());
}
if (message.isSetReceiptHandle()) {
row.put(COLUMN_HANDLE, message.getReceiptHandle());
}
if (message.isSetBody()) {
row.put(COLUMN_MESSAGE, message.getBody());
}
results.add(row);
}
}
} catch (AmazonSQSException ex) {
System.out.println("Caught Exception: " + ex.getMessage());
System.out.println("Response Status Code: " + ex.getStatusCode());
System.out.println("Error Code: " + ex.getErrorCode());
System.out.println("Error Type: " + ex.getErrorType());
System.out.println("Request ID: " + ex.getRequestId());
System.out.println("XML: " + ex.getXML());
}
return results;
}
PurchaseOrderSerializer 負責把訊息中的 XML 還原成 Java 物件,這裡使用 JDOM 解析(對照上集清單 7 的採購訂單 schema 會更容易理解)。
public class PurchaseOrderSerializer {
public CustomerOrderEntity deserializePO(MessageQueueEntity message) {
CustomerOrderEntity order = null;
String xml = message.getMessageBody();
try {
// 以含 XML 的字串建立輸入來源
InputSource xmlIS = new InputSource();
xmlIS.setCharacterStream(new StringReader(xml));
SAXBuilder builder = new SAXBuilder();
Document doc = builder.build(xmlIS);
Element rootElem = doc.getRootElement();
// 訂單編號
String id = rootElem.getChildText("Id");
order = new CustomerOrderEntity(id);
// 訂單日期
String dateStr = rootElem.getChildText("OrderDate");
order.setOrderDate(DateUtil.getDate(dateStr));
// 客戶(公司)地址
this.setCompanyAddress(order, rootElem.getChild("Company"));
// 供應商地址
this.setVendorAddress(order, rootElem.getChild("Vendor"));
// 商品明細
this.setOrderItems(order, rootElem.getChild("Items"));
System.out.println(order.toString());
} catch (IOException e) {
e.printStackTrace();
} catch (NullPointerException e) {
e.printStackTrace();
} catch (JDOMException e) {
e.printStackTrace();
}
return order;
}
private void setVendorAddress(CustomerOrderEntity order, Element addrElem) {
String coName = addrElem.getChildText("CompanyName");
String streetAddress = addrElem.getChildText("StreetAddress");
String city = addrElem.getChildText("City");
String state = addrElem.getChildText("State");
String zipCode = addrElem.getChildText("ZipCode");
AddressEntity address = order.getVendorAddress();
address.setCompanyName(coName);
address.setStreetAddress(streetAddress);
address.setCity(city);
address.setState(state);
address.setZipCode(zipCode);
}
private void setCompanyAddress(CustomerOrderEntity order, Element addrElem) {
String coName = addrElem.getChildText("CompanyName");
String streetAddress = addrElem.getChildText("StreetAddress");
String city = addrElem.getChildText("City");
String state = addrElem.getChildText("State");
String zipCode = addrElem.getChildText("ZipCode");
AddressEntity address = order.getCompanyAddress();
address.setCompanyName(coName);
address.setStreetAddress(streetAddress);
address.setCity(city);
address.setState(state);
address.setZipCode(zipCode);
}
private void setOrderItems(CustomerOrderEntity order, Element itemsElem) {
List itemList = itemsElem.getChildren();
if (itemList == null) return;
for (int index = 0; index < itemList.size(); index++) {
Element curElem = (Element) itemList.get(index);
String itemId = curElem.getAttributeValue("Id");
String itemName = curElem.getAttributeValue("Name");
String quantity = curElem.getAttributeValue("Quantity");
CustomerOrderDetailEntity detail = new CustomerOrderDetailEntity();
detail.setItemId(itemId);
detail.setItemName(itemName);
detail.setQuantity(Integer.parseInt(quantity));
order.addItem(detail);
}
}
}
接著為採購訂單產生對應的訂單匯總。這裡有個容易混淆的細節值得留意:兩邊的位址角色剛好對調——採購訂單中的 Vendor 是製造商自己,彙總時要寫成 CompanyAddress;原本的 Company 則是下單的分銷商,改寫為 CustomerAddress。
public OrderSummaryEntity getOrderSummaryForCustomerOrder(CustomerOrderEntity customerOrder) {
if (customerOrder == null) return null;
OrderSummaryEntity orderSummary = new OrderSummaryEntity();
orderSummary.setOrderDate(new Date());
orderSummary.setReferenceId(customerOrder.getId());
// 位址角色對調
orderSummary.setCompanyAddress(customerOrder.getVendorAddress());
orderSummary.setCustomerAddress(customerOrder.getCompanyAddress());
// 搬移商品明細
Iterator<CustomerOrderDetailEntity> itemIter = customerOrder.getItems();
while (itemIter.hasNext()) {
CustomerOrderDetailEntity item = itemIter.next();
OrderSummaryDetailEntity detail = new OrderSummaryDetailEntity();
detail.setItemId(item.getItemId());
detail.setItemName(item.getItemName());
detail.setQuantity(item.getQuantity());
orderSummary.addItem(detail);
}
return orderSummary;
}
接著把 OrderSummaryEntity 序列化回 XML,同樣使用 JDOM(對照上集清單 8 的訂單匯總 schema)。
public class OrderSummarySerializer {
public String serializeOrder(OrderSummaryEntity order) {
Document doc = new Document();
Element rootElem = new Element("OrderSummary");
doc.addContent(rootElem);
Element idElem = new Element("OrderId");
idElem.setText(order.getOrderId());
rootElem.addContent(idElem);
Element referenceIdElem = new Element("ReferenceId");
referenceIdElem.setText(order.getReferenceId());
rootElem.addContent(referenceIdElem);
Element dateElem = new Element("OrderDate");
dateElem.setText(DateUtil.getDateString(new Date()));
rootElem.addContent(dateElem);
rootElem.addContent(this.getElementForAddress("CompanyAddress", order.getCompanyAddress()));
rootElem.addContent(this.getElementForAddress("CustomerAddress", order.getCustomerAddress()));
// 逐一加入商品
Element itemsElem = new Element("Items");
Iterator<OrderSummaryDetailEntity> itemIter = order.getItems();
while (itemIter.hasNext()) {
OrderSummaryDetailEntity item = itemIter.next();
Element itemElem = new Element("Item");
itemElem.setAttribute("ItemId", item.getItemId());
itemElem.setAttribute("ItemName", item.getItemName());
itemElem.setAttribute("Quantity", String.valueOf(item.getQuantity()));
itemsElem.addContent(itemElem);
}
rootElem.addContent(itemsElem);
// 轉成字串
XMLOutputter outp = new XMLOutputter();
StringWriter strWriter = new StringWriter();
try {
outp.output(doc, strWriter);
} catch (IOException e) {
e.printStackTrace();
}
return strWriter.toString();
}
private Element getElementForAddress(String elemName, AddressEntity address) {
Element addrElem = new Element(elemName);
Element coElem = new Element("CompanyName");
coElem.setText(address.getCompanyName());
addrElem.addContent(coElem);
Element streetElem = new Element("StreetAddress");
streetElem.setText(address.getStreetAddress());
addrElem.addContent(streetElem);
Element cityElem = new Element("City");
cityElem.setText(address.getCity());
addrElem.addContent(cityElem);
Element stateElem = new Element("State");
stateElem.setText(address.getState());
addrElem.addContent(stateElem);
Element zipCodeElem = new Element("ZipCode");
zipCodeElem.setText(address.getZipCode());
addrElem.addContent(zipCodeElem);
return addrElem;
}
}
完成後,透過 Amazon 的 Java API 把 XML 訊息投入 SQS 佇列:
protected boolean sendMessage(String queueName, String messageBody) {
boolean result = false;
try {
String accessKeyId = AppConfig.getProperty("AmazonAccessKeyID");
String secretAccessKey = AppConfig.getProperty("AmazonSecretAccessKey");
AmazonSQS service = new AmazonSQSClient(accessKeyId, secretAccessKey);
SendMessageRequest request = new SendMessageRequest();
request.setQueueName(queueName);
request.setMessageBody(messageBody);
SendMessageResponse response = service.sendMessage(request);
if (response.isSetSendMessageResult()) {
SendMessageResult sendMessageResult = response.getSendMessageResult();
if (sendMessageResult.isSetMessageId()) {
System.out.println("\t\tMessageId: " + sendMessageResult.getMessageId());
result = true;
}
}
} catch (AmazonSQSException ex) {
System.out.println("Caught Exception: " + ex.getMessage());
System.out.println("Response Status Code: " + ex.getStatusCode());
System.out.println("Error Code: " + ex.getErrorCode());
System.out.println("Error Type: " + ex.getErrorType());
System.out.println("Request ID: " + ex.getRequestId());
System.out.println("XML: " + ex.getXML());
}
return result;
}
最後一步是把處理完的採購訂單從佇列刪除。刪除時憑的不是 MessageId,而是接收時一併取得的 receipt handle——這是 SQS 實作上很值得記住的一點。
protected boolean deleteMessage(String queueName, String handle) {
boolean result = false;
try {
String accessKeyId = AppConfig.getProperty("AmazonAccessKeyID");
String secretAccessKey = AppConfig.getProperty("AmazonSecretAccessKey");
AmazonSQS service = new AmazonSQSClient(accessKeyId, secretAccessKey);
DeleteMessageRequest request = new DeleteMessageRequest();
request.setQueueName(queueName);
request.setReceiptHandle(handle);
DeleteMessageResponse response = service.deleteMessage(request);
if (response.isSetResponseMetadata()) {
ResponseMetadata responseMetadata = response.getResponseMetadata();
if (responseMetadata.isSetRequestId()) {
System.out.print("RequestId: " + responseMetadata.getRequestId());
result = true;
}
}
} catch (AmazonSQSException ex) {
System.out.println("Caught Exception: " + ex.getMessage());
System.out.println("Response Status Code: " + ex.getStatusCode());
System.out.println("Error Code: " + ex.getErrorCode());
System.out.println("Error Type: " + ex.getErrorType());
System.out.println("Request ID: " + ex.getRequestId());
System.out.println("XML: " + ex.getXML());
}
return result;
}
兩個端點都到位了,可以開始測試。做法是對一個庫存不足的商品下單,然後沿著這條鏈看訊息如何流動:
圖 6 是分銷商端在新增訂單前檢視庫存餘量的畫面。
圖 6. 瀏覽庫存

圖片看不清楚?請點擊這裡查看原圖(大圖)。
圖 7 是訂單提交視窗。
圖 7. 提交訂單

圖片看不清楚?請點擊這裡查看原圖(大圖)。
圖 8 則是瀏覽訂單的視窗。
圖 8. 瀏覽訂單

圖片看不清楚?請點擊這裡查看原圖(大圖)。
新增訂單後,若庫存不足以出貨,分銷商端訂單履行服務的輸出如圖 9。
圖 9. 分銷商訂單履行與庫存管理服務

圖片看不清楚?請點擊這裡查看原圖(大圖)。
同一時間,POQueue 裡應該能看到剛送出的採購訂單訊息,如圖 10。
圖 10. 查看訊息佇列

圖片看不清楚?請點擊這裡查看原圖(大圖)。
製造商從佇列取得採購訂單並處理,其訂單處理服務的輸出如圖 11。
圖 11. 製造商訂單管理服務

圖片看不清楚?請點擊這裡查看原圖(大圖)。
本文示範了如何以 XML 搭配 Amazon SQS 整合企業間的業務應用。XML 的通用性加上 SQS 的雲端佇列,換來一個擴充性良好、整合門檻低的方案,而且不必自行處理防火牆與安全設定。最後一項好處或許最具關鍵,也正是 Web 服務的核心價值:它是跨平台的,與雙方採用什麼技術無關。製造商與分銷商在整合流程、提升營運效率與投資報酬的同時,各自的技術平台都能原封不動地保留。
當然,這個方案也有邊界:
最後一點實務建議:既然訊息本文以 XML 承載,就該認真執行 XSD 驗證。這與其他 XML 整合專案的道理相同——送方與收方必須對同一份 schema 達成共識,否則跨語言、跨平台的優勢反而會變成災難。
| 內容 | 檔名 | 大小 | 方式 |
|---|---|---|---|
| 分銷商應用程式(C# 專案) | NETSolution.zip | 223KB | HTTP |
| 製造商應用程式(Java 專案) | JavaSolution.zip | 24KB | HTTP |
| 組態腳本 | DbScripts.zip | 1KB | HTTP |