Communication Manager XML file

The CommunicationManager.xml file is a configuration file that defines which features can be accessed by the POS application.

The following timeout values can be adjusted to achieve an appropriate balance for the retailer’s bandwidth:

  • Channel Timeout—the number of seconds to wait for a response from a request message before timing out.
  • Application Timeout—the number of seconds to wait before retrying a channel that has experienced a channel timeout.

For default timeout values, refer to the CommunicationManager.xml file.

The following table describes the suggested Communication Manager XML timeout values. These values represent general guidelines, and retailers should work closely with their NCR Representative to determine the best combination for their specific environment.

Message typeChannel timeoutApplication timeoutDescription
Options451Pull down parameters at startup
PLU71Ring an item, looks locally
Hierarchies71
  • Department list
  • Item not on file
Product Group Details151
  • Coordinate items
  • Item Add-Ons
Product Search201Item lookup (type in “red wagon” and pull back all items that fit that description)
Store Tax Data301Used for loading the store’s tax files. Called on startup, or on Refresh Data Files manual request.
Associate251
  • Sign in
  • Manager Override
  • Commissioned Associate
  • Associate Discount
Validate Associate Exists151
  • Associate Discount
  • Commissioned Associate
Associate Maintenance71Adding Associates, and so on.
Role Maintenance71
  • Adding roles
  • Changing roles
POS System User Authorization201The user that the POS is signed on to the system is requesting an authorization token.
EnterpriseReports301Accessing enterprise reports, such as Store Totals reports.
Password151
  • Changing password
  • Creating a new user
POSLog45120
  • Locked during read or write.
  • File system can be locked.
  • Only being accessed and locked to read and write the file.
  • File is locked, read, unlocked, and record is transmitted.
ReturnTransaction201
  • Scan a return receipt.
  • Scan an item essentially every time a return happens.
ReturnPricePoint201Return lookup using one or more receipts, an item, and a specific price.
SearchTransaction201Order lookup through receipt scan
DisplayTransaction201When cashier scans return transaction, and selects Display Receipts
TrustedCustomer201Non-receipted return requests
Taxonomy201Used in conjunction with Order Management, such as store number validation for order numbers.
ISPU71Used for web order pickup
Inventory730Inventory-related requests
OMS730Order Management System
Order Create730Create a new order
Transaction Search301Search the electronic journal (EJ) database for transactions that match the criteria provided
Store State Maintenance71Used in Store Controller requests, such as Back Office
TransactionTypeCounts71Requested for Back Office reports that access counts of sales, returns, and so on.
Note

Local counts are updated after every transaction.

TransactionTypeCountsSync71Used on Store Controller requests, such as Back Office
PurgeTransactionTypeCounts71Used on Store Controller end of transaction, such as Back Office
OrderStatus71Retrieving the status of an order
OrderStatusUpdate71Updating the status of an order
OrderUpdate71Updating, such as to add notes and add customer information, to an order
OrderGet71Retrieve an order
OrderCancel71Cancel an order
OrderAddItem71Add an item to an order
OrderDeleteItem71Delete an item from an order