Working with Integration Layer Processes (IJCT)
Purpose: Use this menu option to work with the processes that transmit data between CWDirect and CWIntegrate, such as batch and on-line credit card authorizations, deposits, and merged customers.
Note: The integration layer processes are not restricted by company; when you work with or change a process, it affects all companies.
In this topic:
• Heartbeat Request and Response
• Work with Integration Layer Process Screen
• Create Integration Layer Process Screen
• Change Integration Layer Process Screen
• Display Integration Layer Process Screen
• Work with Integration Layer Process Queues Screen
• Starting or Stopping Process Queues
• Integration Layer Process Queue Screen
• MQSeries Work with Messages Screen (Reviewing Messages)
• Work with Integration Process Control Screen
• Display Integration Process Control Screen
• Defining Outbound Interface Trigger Rules
• Defining Trigger Rule Values
• Select Trigger Rules File Window
• Outbound Interface Trigger Rules Screen
• Outbound Interface XML Inclusion Screen
• Select XML Message Version Screen
• Troubleshooting Integration Layer Processes
• Are the Processes Out of Sync?
• Translating Special Characters in Outbound Messages
• Summary of XML Messages and CWIntegrate Sites
As data is processed in CWDirect, MQSeries sends messages to the CWIntegrate processes for processing. For example, when you process a customer merge/purge in CWDirect, a message is sent to CWIntegrate (outbound process); or, when the CWIntegrate site forwards an email message into CWDirect, the CWIntegrate process interprets the email and assigns it to a customer, order, and so on (inbound process). Processes can also be bi-directional if a response is received (for an outbound process) or generated (for an inbound process).
All messages are processed in the sequence in which they arrive at the message queue.
Inbound process structure: Underneath each inbound process at the Work with Integration Layer Process Screen are one or more process queues. Multiple process queues are useful for inbound messages, so that you can receive and process messages from more than one remote system. For example, you might receive inventory transactions from both a warehouse management system and a POS system.
When there are multiple process queues, each queue is an instance of the Inbound program for the process; however, each queue should have a unique Inbound job name so that you can identify and troubleshoot each process separately.
The # inbound sessions for each process queue can be one or more. For example, you might set the number of inbound sessions higher for the process queue that processes orders from your web storefront, to prevent delays; however, you might require only one inbound session for orders you receive from a remote order entry service, because you receive these orders at a scheduled time, and an immediate response is not required.
Inbound process example:
1. A remote system sends a message to CWIntegrate.
2. CWIntegrate translates the message into the format required by the process in Integration Layer Job Control, and sends it to the Inbound queue specified for the process queue.
3. The process:
• receives and identifies the message
• parses (interprets) the XML
• performs any required actions, such as building CWDirect records or submitting records to a background job for additional processing
4. Optionally, the process sends a response using the Outbound queue specified.
Outbound process structure: Underneath each outbound process at the Work with Integration Layer Process Screen are one or more outbound queues. Multiple outbound queues allow you to send outbound messages to more than one remote system. For example, you might send item information to your POS system and warehouse management system. If you define more than one outbound queue, the system creates a copy of the outbound message for each additional queue whose Enabled field is selected.
Note: You can create more than one outbound queue for the Item Outbound process, Invoice Outbound process, and Vendor Outbound process; for any other outbound process you can define only one outbound queue.
An outbound process requires an inbound session only when a response from the remote system is expected.
Configuration options: The ITEM_OUT, INVOIC_OUT, PICK_OUT, SVC_REMOTE, and STORE_PKUP processes require additional configuration options to generate an outbound message.
For outbound processes requiring additional configuration options you must define:
• an outbound MQSeries message queue manager and queue where the system can generate and send a CWMessageBuilder XML message when a download trigger is processed. The CWMessageBuilder XML message provides the message builder the information required to generate an XML message for the specific outbound trigger. For example, if the trigger is an item download trigger, the CWMessageBuilder XML message provides the key (company, item number, and SKU code) associated with the item download trigger.
• an iSeries user ID and password used to access the CWDirect database where the download information required to generate the outbound message is located. The system includes the user ID and password and the value defined in the Data Base Library (A37) system control value in the CWMessageBuilder XML message. The message builder uses this information to access the CWDirect database. Note: For security reasons, the system scrambles the password in the Integration Layer Process file and on the Integration Layer Process screen. The system unscrambles the password when it is passed in the CWMessageBuilder XML message.
• the location of the programs used to process the additional configuration options. If you leave this field blank, the system uses the default location /CWJava/prod, where CWJava is a folder located at the root directory on the iSeries.
Outbound process example:
1. Activity in CWDirect:
• generates an outbound message and sends the message to the outbound queue defined for the outbound process, Or
• creates outbound triggers in the IL Outbound Trigger file, based on the trigger rules defined for the outbound process. You can create outbound triggers for the ITEM_OUT process, INVOIC_OUT process, INV_DOWNLD process, VENDOR_OUT process, SVC_REMOTE, and PICK_OUT process. See Defining Outbound Interface Trigger Rules.
Note: The STORE_PKUP process uses outbound trigger records, but you cannot generate them on-demand and there are no trigger rule options. Instead, the system creates a trigger record automatically when you accept an order that includes an item flagged for store fulfillment. See Merchandise Locator and Store Fulfillment API through .NET for more information.
• When active, the outbound process looks for outbound triggers to process at defined intervals, based on the value defined in the Outbound delay time field.
• For each outbound trigger, the outbound process determines which elements to include in the outbound message, based on XML inclusion rules; see Outbound Interface XML Inclusion Screen.
• For outbound processes requiring additional configuration options, the outbound process creates a CWMessageBuilder XML message containing the trigger key and CWDirect database access information the message builder associated with the process requires to generate an outbound message.
• The system then sends the generated message to the outbound queue defined for the outbound process. If more than one outbound queue is defined, the system creates a copy of the message to send to the additional queues that are active (the Enabled field is set to Y).
2. CWIntegrate translates the message into the format required by the remote system and sends the formatted message to the remote system.
3. Optionally, the remote system sends a response using the inbound queue specified.
Overview: As new elements and attributes are added to existing system-delivered XML messages processed through Integration Layer Job Control, each new version of a message is tagged with a version number. The first version of an XML message is always tagged as version 1.0, but if the next release of CWDirect adds any new attributes or elements to this XML message, this next version of the message is tagged as version 2.0.
Version compatibility: Each new attribute or element is always optional, or implied, so that the integration layer process can always process previous versions of the message.
XML version numbers vs. CWDirect release numbers: The XML version number is independent of the CWDirect release number. For example, version 2.0 of a message might be introduced in CWDirect release 8.0, while version 1.0 of another message might be introduced in CWDirect release 8.5.
About inbound XML messages: Since the integration layer processes can process any previous versions of the related inbound message, the highest version of an inbound XML message supported by an integration layer process is indicated by the Version in field at the Work with Integration Layer Process Screen. For example, if this field is set to 2.0, the integration layer process can process the message in version 1.0 and 2.0.
Not all integration layer processes receive inbound messages. The Version in field is blank for any integration layer processes that are outbound-only.
About outbound XML messages: You use the Select XML Message Version Screen to indicate which version of the outbound message the integration layer process should generate. For example, if version 1.0 and 2.0 are available for an outbound message, you could have the process generate either version. By default, the integration layer process generates version 1.0. Whichever version of the message you select will be sent to all process queues running under the integration layer process.
Outbound XML version for SVC Reversal process: The SVC Reversal process (SVC_REVRSL) uses the outbound XML version defined for the SVC Activation process (SVC_OUT) to generate a stored value card authorization reversal request message. If you define an outbound XML version for the SVC Reversal process, the system will ignore the version you define and continue to use the outbound XML version defined for the SVC Activation process. Typically, you would want to generate a same outbound message version for both stored value card activations and stored value card authorization reversals.
Outbound XML version for CC_TOKEN process: Because the CC_TOKEN integration layer process is an interactive job, you must define its outbound XML version in the CCAUTH_BTH (Batch Authorization) and CCAUTH_ONL (Online Authorization) integration layer processes. To include the tokenized tag in the Authorization Request XML Message (CWAuthorizationRequest), set the outbound XML version for the CCAUTH_BTH and CCAUTH_ONL processes to version 5.0 or later.
How does the system identify the current version of a message? The XML Message Version file lists the latest available version of each inbound and outbound XML message. This file is updated each time you apply a new PTF upgrade.
Need to update CWIntegrate sites? You do not need to upgrade your CWIntegrate site just because the related integration layer process can receive a higher version inbound message. Similarly, you do not need to update your CWIntegrate site to generate a higher version outbound message, as long as you do not use the Select XML Message Version Screen to select a higher version outbound message. The site and integration layer process will continue to work together using the current version of your message(s). However, any new functionality added in the recent version will not be available in your integration until you upgrade the CWIntegrate site and make any other upgrades to mapping logic.
Which version does your site use? Unless otherwise indicated in your site manual, your site uses version 1.0 of each XML message. You would not normally use a higher version of an XML message unless you are notified by a MICROS representative.
Identifying when new attributes or elements were added to a message: Unless otherwise indicated in the XML layout, each element and attribute was included in version 1.0 of the message. See Summary of XML Messages and CWIntegrate Sites for a listing of inbound and outbound messages processed through Working with Integration Layer Processes (IJCT), including links to the XML layouts.
Versions assigned to system-delivered messages only: Only system-delivered XML messages processed through integration layer processes support this version functionality. For example, e-commerce XML messages and unique XML messages do not support versions. See the Summary of XML Messages and CWIntegrate Sites for a listing of system-delivered messages processed by the integration layer processes under Working with Integration Layer Processes (IJCT).
Note: The e-commerce item availability message, generated by EC_ITEMAVL, does not support versions.
Heartbeat Request and Response
Purpose: Some of the integration layer processes automatically return a heartbeat response to a simple heartbeat request message. This heartbeat response provides a way for an external system to confirm the status of an integration layer process. For example, if you set up your web storefront to send periodic heartbeat request messages to an integration layer process in CWDirect, the lack of a heartbeat response tells you that operator intervention is required to restart the process or troubleshoot any communication difficulty (such as network or MQ interruptions).
How does heartbeat request and response work? The heartbeat request message is simply a text string consisting of the words HEARTBEAT REQUEST; it is not an XML message. When the integration layer process receives the request message, it returns the heartbeat response message, which specifies the integration layer job that is responding, and the time and date when the response was generated. For example, when the ORDER_IN job generates a heartbeat response at 5:11:43 p.m. on April 11, 2008, the response reads: HEARTBEAT RESPONSE FROM ORDER_IN ON 04112008 AT 171143.
Which processes support heartbeat request and response? The following integration layer processes return a heartbeat response when they receive the heartbeat request:
• ORDER_IN
• CUST_HIST
• CUST_SRCH
• CUSTOMR_IN
• INV_INQURY
The heartbeat request and response is not supported by any other integration layer process.
What if the process is not running? If an inactive process continues to receive heartbeat request messages, the messages remain on the process queue until the process restarts. At that point, the process generates a heartbeat response for each heartbeat request waiting on the queue. For example, if an external system sends a heartbeat request to an inactive process every five minutes and the process restarts after a half an hour, the process generates six heartbeat response messages as soon as it begins working through the queue.
This table describes:
• the integration layer processes
• their functions
• the jobs they initiate
• the messages they handle
For more information: See Summary of XML Messages and CWIntegrate Sites for a summary of each of the inbound and outbound XML messages. Also, see the related CWDirect integration manual for more information on the translation process CWIntegrate performs on generic CWIntegrate XML messages.
Note:
• The default input queues (for processing messages to CWDirect) and, in certain cases, remote queues and queue managers (to enable sending information from CWDirect) vary, depending on the configuration of the remote service. See the appropriate integration manual for more information.
• The Java(TM) programming language is used by the Item Outbound, Invoice Outbound, Store Shipment and Pick Outbound processes only.
Process |
Function |
Submitted Job(s) (outbound) or program (inbound) |
Messages |
A/R batch payments |
CWDirect receives batch A/R payments against open items. See Uploading A/R Batch Payments for an overview. |
ARBTCHP_IN (ILO0018) |
ARPayment (to iSeries) |
Order Broker request |
CWDirect sends a request to the Order Broker module in Locate to select a remote (store) location to fulfill a backordered line and receives confirmation from the Order Broker. See Order Broker Integration for an overview. |
BROKER_ORD (ILO0029) |
CWOrderBroker Request (from iSeries) CWOrderBroker Response (to iSeries) |
Order Broker status update |
CWDirect inquires on the current status of an order line assigned to the Order Broker for fulfillment, or requests that the Order Broker cancel fulfillment of the order line from the remote (store) location. See Order Broker Integration for an overview. |
BROKER_STS (ILO0029) |
CWOrderBroker Request (from iSeries) CWOrderBroker Response (to iSeries) Note: Although this job uses the same message formats as the BROKER_ORD job, the messages serve different functions. |
Customer history, order inquiry (inbound/ outbound) |
CWDirect receives a request for customer order history or information on a specific order, and generates a response. See Generic Customer History API for an overview. |
CUST_HIST (ILO0012) |
CustHistRequest (to iSeries) CWCUSTHISTOUT (from iSeries) CWORDEROUT (from iSeries) CWCUSTHISTOUT STORE21 (from iSeries) |
Customer inquiry/search (inbound/ outbound) |
CWDirect receives a request for information on one or more customers matching specific search criteria, and generates a response. See Generic Customer Inquiry (Search) API for an overview. |
CUST_SRCH (ILO0012) |
CWCustomerInq Request (to iSeries)
CWCustomerInq Response (from iSeries) |
Customer API (inbound) |
CWDirect receives a new customer, change to an existing customer, or a delete customer message. See Generic Customer API for an overview. |
CUSTOMR_IN (ILO0019) |
CWCustomerIn (to iSeries) |
E-Commerce Item Availability (outbound) |
CWDirect sends an item availability message to the web storefront via CWIntegrate. The E-Commerce Item Availability Download Method (I10) system control value must be set to XML to generate an item availability message to send to CWIntegrate. See that system control value for information on how to generate the message. Note: This message does not support XML Versions. |
This process does not submit a job; it is used to determine the XML message format and the queue used to transmit the message. You do not need to start or end this job. |
CWAvailResponse (from iSeries) |
(inbound) |
CWDirect receives email messages and creates Correspondence History and Correspondence History Detail records; attempts to assign the emails to customers; flags the emails as being in error if they cannot be assigned, or include inconsistent or invalid information. See Email Repository Overview. |
(ILO0001) |
CWEmail (to iSeries) |
Email (outbound) |
CWDirect generates the a generic outbound XML message rather than an actual email, so that you can you can use the information to produce a reformatted HTML email that includes promotional material. See Outbound Email API. |
EMAIL_OUT |
CWEmailOut (from iSeries) |
Inventory download (outbound) |
CWDirect sends inventory availability information to another system, such as Locate. See Generic Inventory Download API for an overview. |
INV_DOWNLD (ILR0022) |
CWInventory Download (from iSeries) |
Inventory inquiry (inbound/ outbound) |
CWDirect receives a request for inventory availability on a specific item/SKU and generates a response. See Generic Inventory Inquiry API for an overview. |
INV_INQURY (ILO0013) |
CWInventoryInquiry (to iSeries) CWInventoryInquiryResponse (from iSeries) |
Invoice Outbound (outbound) |
CWDirect sends invoice information to another system, such as a retail store or warehouse management system. |
INVOICE_OUT (ILR0022) |
CWInvoiceOut (from iSeries) |
Inventory transaction processor (inbound) |
CWDirect receives inventory transactions and updates inventory information, such as in the Item Location and Item Warehouse files. Any errors create Item Transaction Error records. See Generic Inventory Transaction Upload for an overview. |
INVTRAN_IN (ILO0008) |
inCreateInvXaction (to iSeries) |
Item Transaction History Outbound (outbound) |
CWDirect sends item transaction history information to another system. See Generic Item Transaction History Outbound API. |
INVTRANOUT (ILR0022) |
CWInvXActionOut (from iSeries) |
Item Outbound (outbound) |
CWDirect sends item and SKU information to another system, such as a retail store or warehouse management system. See Generic Item Download API. |
ITEM_OUT (ILR0022) |
CWItemOut (from iSeries) |
Merchandise locator (outbound/ inbound) |
CWDirect sends a request for inventory information to an external system, such as Locate, and receives a response listing external warehouse and store locations where the specified item is available. See Merchandise Locator and Store Fulfillment API through .NET for an overview. Note: This function is used for merchandise locator searches only when you integrate with Locate through the cw_locate site, not when you integrate directly with version 5.1, 5.3, or later of Locate. Controlled by the Locate Platform setting. |
MERCH_LOC |
CWMerchLocRequest (from iSeries) CWMerchLoc Response (to iSeries) |
CC Application Process (outbound/ inbound) |
CWDirect sends credit card application requests to CWIntegrate; CWIntegrate translates and transmits the message to the credit card service. The credit card service sends a credit card application response to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Credit Card Applications Overview and Setup and Processing Credit Card Applications. |
CREDIT_APP |
CWCreditCard ApplicationRequest (from iSeries)
CWCreditCard ApplicationResponse (to iSeries) |
CC Token Process (outbound/ inbound) |
CWDirect sends credit card token requests to CWIntegrate; CWIntegrate translates and transmits the message to the tokenization service. The tokenization service sends a credit card token response to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Credit Card Tokenization. Note: This process is an interactive job; you cannot change, start or stop this process. Related SCV: Enter this job in the Tokenization IJCT Job (L41) system control value. |
CC_TOKEN |
RegisterTokenRequest (from iSeries)
RegisterToken Response (to iSeries) |
On-line CC authorization (outbound/ inbound) |
CWDirect sends on-line authorization requests for credit cards, debit (Switch) cards, stored value cards, and Bill Me Later transactions to CWIntegrate; CWIntegrate translates and transmits the message to the service bureau. The service bureau sends an authorization response to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Processing Authorizations and Deposits using CWIntegrate. |
MQAUTH_IN |
CWAuthorization Request (from iSeries)
CWAuthorization Response (to iSeries) |
Batch CC authorization (outbound/ inbound) |
CWDirect sends batch authorization requests for credit cards, debit (Switch) cards, stored value cards, and Bill Me Later transactions to CWIntegrate; CWIntegrate translates and transmits the message to the service bureau. The service bureau sends an authorization response to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Processing Authorizations and Deposits using CWIntegrate. |
MQCCBTH_IN |
CWAuthorization Request (from iSeries)
CWAuthorization Response (to iSeries) |
Batch deposits / settlement (outbound/ inbound) |
CWDirect sends batch deposit requests for credit cards, debit (Switch) cards, stored value cards, and Bill Me Later transactions to CWIntegrate; CWIntegrate translates and transmits the message to the service bureau. The service bureau sends a deposit response to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Processing Authorizations and Deposits using CWIntegrate. |
MQDPBTH_IN |
CWDepositRequest (from iSeries)
CWDepositResponse (to iSeries) |
Order processor (inbound/ outbound) |
CWDirect receives new orders through a generic order interface and optionally generates detailed or simple acknowledgments, as requested in the inbound order message. See Generic Order Interface (Order API) for an overview. |
ORDER_IN (ILO0003) |
CWOrderIn (to iSeries) CWOrderOut (from iSeries) |
Order Line History |
CWDirect receives an Order Line History In Message (CWORDLNHSTIN) to create an order line history records for a specified order line. See Order Line History In API for an overview. |
CW_OLH (ILO0025) |
CWORDLNHISTIN (to iSeries) |
Order Transaction History |
CWDirect receives an Order Transaction History In Message (CWORDTRANSHSTIN) to create order transaction history records for a specified order ship to. See Order Transaction History In API for an overview. |
CW_OTH (ILO0027) |
CWORDTRANSHSTIN (to iSeries) |
Payment Approval |
CWDirect sends an Online Cash Payment Approval Request (CWPaymentApprovalRequest) to an online bill pay service to determine if a customer is eligible to pay for an order using online cash payment. The online bill pay service sends an Online Cash Payment Approval Response (CWPaymentApprovalResponse) back to CWDirect indicating if the customer has been approved or declined. |
PAYAPPROVE (ILR0034) |
CWPaymentApproval Request (from iSeries)
CWPaymentApproval Response (to iSeries) |
Payment Confirmation |
The online bill pay service sends an Online Cash Payment Confirmation Response (CWPaymentConfirmationResponse) to CWDirect when a customer has paid for an order using funds from his bank account. |
PAYMENT_IN (ILO0035) |
CWPayment ConfirmationResponse (to iSeries) |
Pick Outbound |
CWDirect sends a Pick Message from CWDirect (CWPickOut) for each pick slip generated. See Generic Pick Out API for an overview. |
PICK_OUT (ILR0022) |
CWPickOut (from iSeries) |
Promotional Pricing |
CWDirect receives a Promotional Pricing Request Message (CWPromotionalRequest) to determine if the web order qualifies for any promotional pricing. The process sends a Promotional Pricing Response Message (CWPromotionalResponse) back to the web storefront indicating the promotional pricing that is eligible for the web order. See E-Commerce Promotional Pricing for an overview. |
PROMO_IN (ILO0024) |
CWPromotional Request (to iSeries)
CWPromotional Response (from iSeries) |
Return Inbound |
CWDirect receives a Return Request Message (CWReturnIn) to create and process a return against a specified order line. Optionally, the process sends a Return Response Message (CWReturnOut) to the external system, indicating if the return processed successfully or if an error occurred. See Generic Return API for an overview. |
RETURN_IN (ILO0021) |
CWReturnIn (to iSeries)
CWReturnOut (from iSeries) |
Store Fulfillment Request (outbound) |
CWDirect sends a request to a store to prepare one or more items for customer pickup or to ship directly to the customer. The request can be forwarded via an intermediate site, such as the cw_store POS integration site. See Merchandise Locator and Store Fulfillment API through .NET for an overview. |
STORE_PKUP (ILR0022) |
StoreFulfillment Request (from iSeries) |
Single Use Promo Code Check |
CWDirect receives a CWSingleUsePromoCodeCheckRequest XML Message inquiring on whether a single-use promotion code is valid and unredeemed, and returns a CWSingleUsePromoCodeCheckResponse XML Message providing information on the single-use code, the related promotion, and the order on which the code was redeemed, if any. |
SUP_INQURY (ILO0037) |
CWSingleUsePromo CodeCheckRequest (to iSeries) CWSingleUsePromo CodeCheckResponse (from iSeries) |
Stored Value Card Balance Inquiry (outbound/ inbound) |
CWDirect sends a Stored Value Card Balance Inquiry Request to CWIntegrate; CWIntegrate translates and transmits the message to the service bureau. The service bureau sends a Stored Value Card Balance Inquiry Response to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Stored Value Card Balance Inquiry. Note: If the Perform Balance Inquiry during Batch Authorizations (J19) system control value is set to N in any company, this process is an interactive job; you cannot change, start or stop this process. |
SVC_BALANC |
CWAuthorization Request (from iSeries)
CWAuthorization Response (to iSeries) |
Stored Value Card Activation (outbound/ inbound) |
CWDirect sends a Stored Value Card Activation Request to CWIntegrate; CWIntegrate translates and transmits the message to the service bureau. The service bureau sends a Stored Value Card Activation Response to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Stored Value Card Purchase and Activation. |
SVC_OUT (inbound: AAO0001) (outbound: ILR0022) |
CWAuthorization Request (from iSeries)
CWAuthorization Response (to iSeries) |
Stored Value Card Remote Fulfillment (outbound/ inbound) |
CWDirect sends a Stored Value Card Remote Fulfillment Request to CWIntegrate; CWIntegrate translates and transmits the message to the gift card fulfillment system. The gift card fulfillment system activates and fulfills the card and sends a Stored Value Card Remote Fulfillment Confirmation to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Stored Value Card Remote Fulfillment. |
SVC_REMOTE (inbound: AAO0004) (outbound: ILR0022) |
CWSVCRemoteOut (from iSeries)
CWSVCRemoteIn (to iSeries) |
Stored Value Card Authorization Reversal (outbound/ inbound) |
CWDirect sends a Stored Value Card Authorization Reversal to CWIntegrate; CWIntegrate translates and transmits the message to the service bureau. The service bureau sends a Stored Value Card Authorization Reversal Response to CWIntegrate; CWIntegrate translates and transmits the message to CWDirect. See Stored Value Card Authorization Reversal. Note: You cannot create multiple Stored Value Card Authorization Reversal jobs; CWDirect always uses the job named SVC_REVRSL to process authorization reversals. In addition, the Stored Value Card Authorization Reversal job uses the outbound XML version defined for the Stored Value Card Activation job for the service bureau. |
SVCREV_OUT (AAO0001) |
CWAuthorization Request (from iSeries)
CWAuthorization Response (to iSeries) |
File download trigger (customer merge) (outbound) |
CWDirect sends an e-commerce customer merge message to the web storefront indicating customers have been merged in CWDirect and the customer information on the web may now be inaccurate. It is the web storefront’s responsibility to retrieve the records in the EC Customer Sold To Merge Staging file, EC Customer Bill To Merge Staging file, and EC Customer Individual Merge Staging file. These files are updated when you process a merge/purge if the Generate E-Commerce Customer Merge Staging Files (H86) system control value is set to Y. See E-Commerce File Download Trigger Process (TRIGGER_DL). |
This process does not submit a job; it is used to determine the XML message format and the queue used to transmit the message. You do not need to start or end this job. |
CW File Transfer (from iSeries) |
Tax Request (inbound / outbound) |
CWDirect sends a request for tax information for an order to an external system, and then receives the response. See the Tax Interface Values (J29) screen and the Generic Tax Interface Messages for more information. |
This process does not submit a job; it is used to determine the XML message format and the queue used to transmit the message. You do not need to start or end this job. |
CWTaxRequest (from iSeries) CWTaxResponse (to iSeries) |
Vendor Outbound (outbound) |
CWDirect sends vendor information to another system, such as a retail store or warehouse management system. |
VENDOR_OUT (ILR0022) |
CWVendorOut (from iSeries) |
Workflow processing (inbound) |
CWDirect receives the CWWorkflow XML message from an outside source and creates a tickler, based on the information in the message. This process does not process any message other than CWWorkflow. See Workflow Management Overview and Setup and WF (Remote Workflow) Event Processing. |
WORKFLOW (ILO0002) |
CWWorkflow (to iSeries) |
Work with Integration Layer Process Screen
Purpose: Use this screen to review the integration layer message queues for integration layer processes. At this screen you can also start or end all queues for a process at once.
When you first enter this screen, the system automatically creates the base delivered integration layer processes. The communication type defaults to MQ and the inbound and/or outbound XML messages and job names are populated.
How to display this screen: Enter IJCT in the Fast path field at the top of a menu or select Integration Layer Job Control from a menu.
MSX1285 DISPLAY Work with Integration Layer Process 8/23/12 17:11:41
Version Actv Opt Process Description In Out Type Status Sess
Type options, press Enter. 2=Change 4=Delete 5=Display 7=Start 8=End 9=Work with Queues 11=Change Status 14=Trigger Rules 15=XML Inclusion 16=Outbound XML Ver
ARBATCH_IN A/R Batch Payment Inbound 1.0 MQ Inactive 0 Start: 1/14/04 14:20:53 EKAPLAN End..: 1/13/04 9:49:51 LWARREN CCAUTH_BTH Batch CC Authorization 1.0 1.0 MQ Starting 0 Start: KBOTTGER End..: 2/13/04 10:53:03 KBOTTGER CCAUTH_ONL On-Line CC Authorization 1.0 1.0 MQ Inactive 0 Start: 9/16/03 13:35:06 JNAVONI End..: JNAVONI CUST_HIST Customer History Outbound 1.0 MQ Inactive 0 Start: 1/13/04 11:31:47 EKAPLAN End..: JNAVONI +
F3=Exit F6=Create F7=Start All F8=End All F12=Cancel F15=Ecomm Jobs |
Field |
Description |
Process |
A code for an integration layer process. Alphanumeric, 10 positions; optional. |
Description |
A description of the process. Alphanumeric, 30 positions; optional. |
Version in |
The latest version of the inbound XML message that the process is capable of processing. For example, if the Version in is 2.0, this indicates that the process works with version 1.0 or 2.0 of the inbound XML message. See XML Versions for an overview. This field is blank if the process does not process inbound XML messages. Numeric, 3 positions with a 1-place decimal; display-only. |
Version out |
The version of the outbound XML message that the process generates. You can select the outbound XML version at the Select XML Message Version Screen. See XML Versions for an overview. This field is blank if the process does not generate outbound XML messages. Numeric, 3 positions with a 1-place decimal; display-only. |
Type |
The type of queue or queues used to receive or send messages. Value values: MQ = Message queue DQ = Data queue (not currently implemented) Alphanumeric, 2 positions; optional. |
Status |
The status of the queue. Possible statuses are: • Active • Inactive • Starting • Ending • Interact: The MERCH_LOC, EMAIL_OUT, SVC_BALANC, and TAX_INT process always have this status because they do not use a batch job, but processes requests and responses interactively. It is not possible to change the status of these processes. Note: The status is Active if any of the process queues is currently active. See the Work with Integration Layer Process Queues Screen for more information. Alphanumeric, 9 positions; display-only. |
Active sessions |
The number of separate sessions that are active for all process queues. You might set up multiple sessions for each process queue of an inbound process to prevent delays in communication. Numeric, 5 positions; display-only. |
The date and time the process, or any of the process queues, was most recently started. The user ID of the person who started the process or any of its queues is also displayed. Date: numeric, 6 positions (MM/DD/YY format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. User: alphanumeric, 10 positions; display-only. |
|
The date and time the process, or any of the process queues, was most recently ended. The user ID of the person who ended the process or any of its queues is also displayed. Date: numeric, 6 positions (MM/DD/YY format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. User: alphanumeric, 10 positions; display-only. |
Screen Option |
Procedure |
Create an integration layer queue |
Press F6 to advance to the Create Integration Layer Process Screen. |
Change the number of sessions for an integration layer process |
Enter 2 next to a process to advance to the Change Integration Layer Process Screen. Note: This option is not available for the MERCH_LOC, EMAIL_OUT, SVC_BALANC, CC_TOKEN and TAX_INT because they are interactive rather than batch processes. |
Delete an integration layer process |
Enter 4 next to a process to delete it. |
Review the details of an integration layer process |
Enter 5 next to a process to advance to the Display Integration Layer Process Screen. |
Start a process |
Enter 7 next to a process to start all process queues for the process. See Changing Process Status. Note: This option is not available for the MERCH_LOC, EMAIL_OUT, SVC_BALANC, CC_TOKEN and TAX_INT because they are interactive rather than batch processes. |
End a process |
Enter 8 next to a process to end all process queues. See Changing Process Status. Note: This option is not available for the MERCH_LOC, EMAIL_OUT, SVC_BALANC, CC_TOKEN and TAX_INT because they are interactive rather than batch processes. |
Work with the queues for a process |
Enter 9 next to a process to advance to the Work with Integration Layer Process Queues Screen, where you can start, end, or work with individual process queues. |
Change the status of a process |
Enter 11 next to a process to advance to the Change Status Window if you are not able to start or end it normally. Note: This option is not available for the MERCH_LOC, EMAIL_OUT, SVC_BALANC, CC_TOKEN and TAX_INT because they are interactive rather than batch processes. |
Define trigger rules for an outbound process |
Enter 14 next to a process to advance to the Outbound Interface Trigger Rules Screen or the Select Trigger Rules File Window. This option is not available for processes that do not use trigger rules. |
Define XML inclusion rules for an outbound process |
Enter 15 next to a process to advance to the Outbound Interface XML Inclusion Screen. This option is not available for processes that do not use XML inclusion. |
Select the XML version to use for outbound messages |
Enter 16 next to a process to advance to the Select XML Message Version Screen. This option is not available for processes that do not generate outbound messages. |
Start all processes |
Press F7 to submit all of the processes. See Changing Process Status. |
End all processes |
Press F8 to end all of the processes. See Changing Process Status. |
Work with e-commerce jobs |
Press F15 to advance to the Work with E-Commerce Job Control screen. See Working with E-Commerce Job Control (EJCT). |
Create Integration Layer Process Screen
Purpose: Use this screen to create an integration layer process. For example, you might create a new process similar to a system-delivered process in order to communicate with multiple authorization services.
How to display this screen: Press F6 at the Work with Integration Layer Process Screen.
MSX1287 ENTER Integration Layer Process 10/20/03 15:28:02 CREATE Process ID Communication type MQ=Message Queue DQ=DataQueue
Inbound Processing: Inbound program Active session(s) 0 Inbound XML message
Outbound Processing: Outbound job name Outbound program Outbound job queue Outbound delay time Outbound XML message
Configuration Options: Outbound Queue Mgr Outbound Queue Classpath User ID Password
F3=Exit F12=Cancel |
Field |
Description |
A code for the job that performs integration layer updates between CWDirect and CWIntegrate. See CWIntegrate Processes for a description of each. Alphanumeric, 10 positions; required. |
|
Description (unlabeled field next to Process ID) |
A description of the subsystem job that is used when the integration layer process is active. Alphanumeric, 30 positions; required. |
Communication type |
The type of communication queue. The only type supported is MQ (Message queue). Alphanumeric, 2 positions; required. |
Inbound Processing: |
|
For an inbound process, the name of the job that receives and interprets the XML message from CWIntegrate to CWDirect, and performs any additional processing in CWDirect. Alphanumeric, 10 positions; optional. |
|
Active session(s) |
Zero (0) displays on the Create screen; otherwise, the total number of active sessions from the Work with Integration Layer Process Queues Screen displays. Numeric, 3 positions; display-only. |
Inbound XML message |
The inbound message for the integration layer process to read and process. Note: You cannot change the inbound XML message for a system-delivered integration layer process. See Summary of XML Messages and CWIntegrate Sites for a listing of system-delivered XML messages. Alphanumeric, 50 positions; optional. |
Outbound Processing: |
|
Outbound job name |
For an outbound process, the name of the job that generates the outbound XML message. Alphanumeric, 10 positions; optional. |
Outbound program |
For an outbound process, the name of the program that the job uses to build the XML message and send it to CWIntegrate. Alphanumeric, 10 positions; optional. |
Outbound job queue |
The job queue where the outbound job resides. Alphanumeric, 10 positions; optional. |
For an outbound process the number of seconds to wait before checking the IL Outbound Trigger file for triggers in a ready (R) status. For outbound processes requiring additional configuration options, the system also uses the outbound delay time to determine the length of time to wait before performing a delete transaction, giving the system time to generate a delete download message. Note: For outbound processes that require additional configuration options, you must enter an outbound delay time. Numeric, 5 positions; optional. |
|
Outbound XML message |
The outbound message for the integration layer process to generate. Note: You cannot change the outbound XML message for a system-delivered integration layer process. See Summary of XML Messages and CWIntegrate Sites for a listing of system-delivered XML messages. Alphanumeric, 50 positions; optional. |
|
Note: Additional configuration options are currently implemented and required for ITEM_OUT, INVOIC_OUT, PICK_OUT, SVC_REMOTE and STORE_PKUP. You cannot define additional configuration options for any other process. |
|
Outbound queue mgr |
The MQSeries message queue manager containing the queue where the system generates and sends a CWMessageBuilder XML message when an item, store fulfillment, or pick download trigger is processed. The CWMessageBuilder XML message provides the message builder the information required to generate an XML message for the specific outbound trigger. For example, if the trigger is an item download trigger, the CWMessageBuilder XML message provides the key (company, item number, and SKU code) associated with the item download trigger. Note: This field is used by the Item Outbound, Invoice Outbound, Pick Outbound, SVC Remote Outbound, and Store Pickup processes only. Alphanumeric, 50 positions; required for outbound messages that required java configuration. |
Outbound queue |
The MQSeries message queue where the system generates and sends a CWMessageBuilder XML message when an item, store fulfillment, or pick download trigger is processed. The CWMessageBuilder XML message provides the message builder the information required to generate an XML message for the specific outbound trigger. For example, if the trigger is an item download trigger, the CWJavaHelper XML message provides the key (company, item number, and SKU code) associated with the item download trigger. Note: This field is used by the Item Outbound, Invoice Outbound, Pick Outbound, SVC Remote Outbound, and Store Fulfillment processes only. Alphanumeric, 50 positions; required for outbound messages that required java configuration. |
Classpath |
The location of the programs used to process integration layer jobs that are set up with additional configuration options. Valid default locations, where CWJava is a folder located at the root directory on the iSeries, are: /CWJava/prod /CWJava/test If this field is blank, the system uses the default location /CWJava/prod. You may wish to define a location if you have both a test and production environment. For example, define location /CWJava/prod for your production environment and define location /CWJava/test for your test environment. To create an additional valid classpath location on the iSeries, you must copy all of the files located at /CWJava/prod and paste the files in the new location. Note: The system does not validate that the location you enter is a valid location on the iSeries. If the location is invalid, the Java program that is submitted when you start the integration layer job will end abruptly. You will need to end the integration layer job, clear any messages that are stranded in the Configuration option outbound queue, define a valid classpath location, and resubmit the integration layer job. Note: This field is used by the Item Outbound, Invoice Outbound, Pick Outbound, SVC Remote Outbound, and Store Fulfillment processes only. Alphanumeric, 50 positions; optional. |
User ID |
The iSeries user ID used to access the CWDirect database during XML message generation. The system must access the CWDirect database in order to retrieve the information required to generate an XML message to send to another system. The system uses the value defined in the Data Base Library (A37) system control value to determine the location of the CWDirect database. The user ID and password you define must be a valid user ID and password for the data base library or the system does not generate an XML message. Note: This field is used by the Item Outbound, Invoice Outbound, Pick Outbound, SVC Remote Outbound, and Store Fulfillment processes only. Alphanumeric, 10 positions; required for outbound messages that required java configuration. |
Password |
The iSeries password for the user ID used to access the CWDirect database during XML message generation. The system must access the CWDirect database in order to retrieve the information required to generate an XML message to send to another system. The system uses the value defined in the Data Base Library (A37) system control value to determine the location of the CWDirect database. The user ID and password you define must be a valid user ID and password for the data base library or the system does not generate an XML message. Note: For security reasons, the system scrambles the password in the Integration Layer Process file and on the Integration Layer Process screen. The system unscrambles the password when it is passed in the CWMessageBuilder XML message. Note: This field is used by the Item Outbound, Invoice Outbound, Pick Outbound, SVC Remote Outbound, and Store Fulfillment processes only. Alphanumeric, 10 positions; required for outbound messages that required java configuration. |
Change Integration Layer Process Screen
To change: Enter 2 next to an integration layer process at the Work with Integration Layer Process Screen to advance to the Change Integration Layer Process screen. See Create Integration Layer Process Screen for field descriptions.
Note: This option is not available for the MERCH_LOC, EMAIL_OUT, SVC_BALANC, CC_TOKEN and TAX_INT because they are interactive rather than batch processes.
Display Integration Layer Process Screen
To display: Enter 5 next to an integration layer process at the Work with Integration Layer Process Screen to advance to the Display Integration Layer Process screen. You cannot update any information on this screen. See Create Integration Layer Process Screen for field descriptions.
Overview: You can start or stop the Integration Layer processes individually or as a group from the Work with Integration Layer Process Screen:
• press F7 to start all processes
• press F8 to end all processes
• enter 7 next to a process to start it
• enter 8 next to a process to end it
When you start one or more processes, their status changes from Inactive to Starting to Active. When you end one or more processes, their status changes from Active to Ending to Inactive.
Normally, you would leave the Integration Layer processes running except to perform backup, system maintenance, and so on.
For information on how to start or end individual process queues for a process, see the Work with Integration Layer Process Queues Screen.
Purging records in the IL Process Control file: When you start an integration layer job that is associated with records in the IL Process Control file, the system purges completed records in the IL Process Control file that are older than 7 days and purges records in any other status that are older than 30 days. See the Work with Integration Process Control Screen for more information.
Note: This option is not available for the MERCH_LOC, EMAIL_OUT, SVC_BALANC, CC_TOKEN and TAX_INT because they are interactive rather than batch processes.
Change status: You can also change the status of a process if it does not start or stop normally in a reasonable amount of time. Enter 11 next to a process to display the Change Status window.
Change status
Inactive . . . Active . . . .
F3=Exit |
At this window, enter 1 next to the desired status, Inactive or Active.
Note: This option is not available for the MERCH_LOC, EMAIL_OUT, SVC_BALANC, CC_TOKEN and TAX_INT because they are interactive rather than batch processes.
Work with Integration Layer Process Queues Screen
Purpose: Use this screen to work with the process queues that run for each process displayed at the Work with Integration Layer Process Screen. Inbound processes might have multiple process queues if you receive messages from multiple remote systems; similarly, outbound processes might have multiple process queues if you broadcast messages to multiple remote systems. See Process Overview for more information on how processes relate to process queues.
Setting up queues for integration with a service bureau: To avoid conflict, make sure you set up each integration layer process that sends messages to a CWIntegrate service bureau site (such as Paymentech, NPC, or Chase FDMS) with a unique queue so that the site can identify the different types of messages it is receiving. The integration layer processes that can send messages to a CWIntegrate service bureau site are:
• CC Token Process
• Batch CC Auth Process
• Online CC Auth Process
• Batch Deposit Process
• SVC Balance Inquiry
• SVC Activation
• SVC Reversal
Note: You cannot create multiple process queues for the CCAUTH_BTH, CCAUTH_ONL, DEPOSITS, CC_TOKEN, SVC_OUT, SVC_BALANC, SVC_REVRSL, PAYAPPROVE, MERCH_LOC, EMAIL_OUT, or EC_ITEMAVL processes. If you create multiple process queues for any of these processes, the system will only process messages for the queue with a sequence number of 1.
Setting up queues for integration with Locate or CWStore: The iSeries Interface Setup (ISUP) menu option automatically creates process queues for integration with either of these products.
How to display this screen: Enter 9 next to a process at the Work with Integration Layer Process Screen.
ILX0006 DISPLAY W/w Integration Layer Process Queues 2/19/03 11:45:58
Process ID: ORDER_IN Order Processor
Opt Seq Description Active Sessions
Type options, press Enter. 2=Change 4=Delete 5=Display 7=Start 8=End 10=View Local Queue Msgs 14=Clear Queue 15=View Batch status
1 EHOLM.TO.CWIAS400.CWORDERIN.70 1 Start: 2/19/03 10:40:40 EHOLM End..: 2/19/03 10:40:38 EHOLM 2 RDC.GENERIC.ORDERIN.QA 0 Start: 2/19/03 10:40:40 EHOLM End..: 2/19/03 10:40:38 EHOLM 3 OPSWEB.TO.CWIAS400 1 Start: 2/19/03 11:34:48 EHOLM End..: 0:00:00
F3=Exit F6=Create F7=Start All F8=End All F12=Cancel |
Field |
Description |
Process ID |
The process you selected at the Work with Integration Layer Process Screen. The description displays to the right. Alphanumeric, 10 positions; display-only. |
Sequence |
A unique sequence number to identify a queue for a process. You cannot create multiple process queues for the CCAUTH_BTH, CCAUTH_ONL, CC_TOKEN, DEPOSITS, SVC_OUT, SVC_BALANC, SVC_REVRSL, PAYAPPROVE, MERCH_LOC, EMAIL_OUT, or EC_ITEMAVL processes. If you create multiple process queues for any of these processes, the system will only process messages for the queue with a sequence number of 1. Numeric, 3 positions; optional. |
Description |
The description of the process queue. Alphanumeric, 30 positions; optional. |
Active sessions |
The number of inbound sessions that are currently active for each process queue. You might have more than one active session for a process queue to prevent delays in responses; for example, you might have multiple active sessions for the process queue that receives new orders from your web storefront. Note: Active sessions do not apply to outbound processing. Numeric, 5 positions; display-only. |
Start |
The date and time the process queue was most recently started. The user ID of the person who started the process queue is also displayed. Note: This field does not display for outbound queues. Date: numeric, 6 positions (MM/DD/YY format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. User: alphanumeric, 10 positions; display-only. |
End |
The date and time the process queue was most recently ended. The user ID of the person who ended the process queue is also displayed. Note: This field does not display for outbound queues. Date: numeric, 6 positions (MM/DD/YY format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. User: alphanumeric, 10 positions; display-only. |
Option |
Procedure |
Create a new process queue |
Press F6 to create a new queue for the selected process. You advance to the Integration Layer Process Queue Screen in Create mode. Note: You cannot create multiple process queues for the Batch CC Auth Process, Online CC Auth Process, Batch Deposit Process, CC Token Process, SVC Activation, SVC Balance Inquiry, SVC Reversal, PAYAPPROVE, MERCH_LOC, EMAIL_OUT, or EC_ITEMAVL processes. |
Change a process queue |
Enter 2 next to a process queue to work with it. You advance to the Integration Layer Process Queue Screen in Change mode. |
Delete a process queue |
Enter 4 next to a process queue to delete it. |
Display a process queue |
Enter 5 next to a process queue to advance to the Integration Layer Process Queue Screen in Display mode; all fields will be display-only. |
Start a process queue |
Enter 7 next to a process queue to start it. If none of the other process queues were currently active, the status of the process at the Work with Integration Layer Process Screen changes to Active. The Start date, time, and user indicated for the process are also updated. Note: The Enabled flag for the process queue must be set to Y for you to be able to start it. |
End a process queue |
Enter 8 next to a process queue to end it. If none of the other process queues were currently active, the status of the process at the Work with Integration Layer Process Screen changes to Inactive. The End date, time, and user indicated for the process are also updated. |
View local queue messages |
Enter 10 next to a process queue to advance to the MQSeries Work with Messages Screen (Reviewing Messages). |
Clear the messages in a queue |
Enter 14 next to a process queue to clear all messages in the queue. See Clearing Queues. |
View status of a batch of messages in a queue |
Enter 15 next to a process queue to advance to the Work with Integration Process Control Screen. |
Start all process queues for the process |
Press F7 to start all process queues for the selected process. The status of the process at the Work with Integration Layer Process Screen changes to Active. The Start date, time, and user indicated for the process are also updated. Note: Only process queues whose Enabled flag is set to Y will start. |
End all process queues for the process |
Press F8 to end all process queues for the selected process. The status of the process at the Work with Integration Layer Process Screen changes to Inactive. The End date, time, and user indicated for the process are also updated. |
Starting or Stopping Process Queues
You can start or stop processes in two ways:
• All existing process queues for a process:
• At the Work with Integration Layer Process Screen: see Changing Process Status.
• At the Work with Integration Layer Process Queues Screen: see below.
• Individual process queues for a process: At the Work with Integration Layer Process Queues Screen:
• Starting a process queue: Enter 7 next to a process queue to start it. If none of the other process queues were currently active, the status of the process at the Work with Integration Layer Process Screen changes to Active. The Start date, time, and user indicated for the process are also updated. Note: The Enabled flag for the process queue must be set to Y for you to be able to start it.
Note: This option is not available for the MERCH_LOC, EMAIL_OUT, CC_TOKEN and SVC_BALANC because they are interactive rather than batch processes.
• Ending a process queue: Enter 8 next to a process queue to end it. If none of the other process queues were currently active, the status of the process at the Work with Integration Layer Process Screen changes to Inactive. The End date, time, and user indicated for the process are also updated.
Note: This option is not available for the MERCH_LOC, EMAIL_OUT, CC_TOKEN, SVC_BALANC and TAX_INT because they are interactive rather than batch processes.
System started: The system automatically starts a process queue for the Batch CC Auth, Online CC Auth, Batch Deposit, SVC Activation, and SVC Reversal processes if a message is requested or received and the process is not currently running.
Starting or stopping all process queues for a process at the Work with Integration Layer Process Queues Screen:
• Starting all process queues for a process: Press F7 to start all process queues for the selected process. The status of the process at the Work with Integration Layer Process Screen changes to Active. The Start date, time, and user indicated for the process are also updated. Note: Only process queues whose Enabled flag is set to Y will start.
Note: This option is not available for the MERCH_LOC, EMAIL_OUT, CC_TOKEN, SVC_BALANC, and TAX_INT because they are interactive rather than batch processes.
• Ending all process queues for a process: Press F8 to end all process queues for the selected process. The status of the process at the Work with Integration Layer Process Screen changes to Inactive. The End date, time, and user indicated for the process are also updated.
Note: This option is not available for the MERCH_LOC, EMAIL_OUT, CC_TOKEN, SVC_BALANC, and TAX_INT because they are interactive rather than batch processes.
Integration Layer Process Queue Screen
Purpose: Use this screen to create, change, or display a process queue for an integration layer process.
How to display this screen: At the Work with Integration Layer Process Queues Screen:
• Press F6 to advance to this screen in Create mode.
Note: You cannot create multiple process queues for the CCAUTH_BTH, CCAUTH_ONL, DEPOSITS, CC_TOKEN, SVC_OUT, SVC_BALANC, SVC_REVRSL, PAYAPPROVE, MERCH_LOC, EMAIL_OUT, or EC_ITEMAVL processes.
• Enter 2 next to a process queue to advance to this screen in Change mode.
• Enter 5 next to a process queue to advance to this screen in Display mode. All fields will be display-only.
ILX0007 ENTER Integration Layer Process Queue 2/19/03 12:02:30 CREATE Process ID: EC_ITEMAVL E-Commerce Item Availability
Desc . . . Enabled . . (Y/N) # Inbound Sessions Wait Time Job Queue . Library
Inbound Processing: Inbound Queue Mgr . . Inbound Queue . . . . Inbound XML Message . Inbound Job Name . .
Outbound Processing: Outbound Queue Mgr . Outbound Queue . . . Outbound XML Message.
F3=Exit F12=Cancel |
Field |
Description |
Process ID |
The Process ID for the selected process. The description of the process displays to the right. Process ID: alphanumeric, 10 positions; display-only. Process description: alphanumeric, 30 positions; display-only. |
Description |
The description of the process queue to run for the integration layer process. For example, for an inbound process, you might use this field to indicate the source of the messages. Alphanumeric, 30 positions; required. |
Indicates whether the process queue can process messages. Valid values are: • Y = You can start the process queue. • N = You cannot start the process queue. Note: If this field is set to N for all process queues, you will not be able to start the process. For outbound processing, the system sends the outbound message only to queues whose Enabled field is set to Y. Alphanumeric, 1 position; required. |
|
The number of sessions to run under this process queue. You might run multiple sessions for process queues that require an immediate response, such as the process queue that receives new order messages from the web storefront. Multiple sessions are used only for inbound process queues; outbound processes should have this field set to 1 for their process queues. Note: If you leave this field blank, you will not be able to start the process queue. If this field is blank for all process queues for a process, you will not be able to start the process. Numeric, 5 positions; required. |
|
Wait time |
The number of seconds CWDirect waits for a response from CWIntegrate. Used only for two-way interfaces (outbound/inbound). If the message waits on the target queue longer than this number of seconds (for example, if the message is sent to a CWIntegrate site on a remote server, and the site is not currently running), the message is automatically deleted. Numeric, 6 positions; optional. |
Job queue |
The job queue where the system submits the integration layer process queue. If this field is blank, the system submits the process to the QSYSWRK job queue. See the iSeries documentation for more information. Alphanumeric, 10 positions; optional. |
Library |
The library where the job queue, if specified, is located. Alphanumeric, 10 positions; optional. |
Inbound Processing: |
|
Active session (s) |
Indicates the number of sessions that are currently active for this process queue. This field displays in Change or Display mode only. Numeric, 5 positions; display-only. |
Inbound queue manager |
The MQSeries message queue manager on your local application server. Required for inbound process queues. Alphanumeric, 48 positions; optional. |
The MQSeries message queue, on the iSeries, from which this process queue receives messages originating from the remote server. Required for inbound process queues. The queue you specify here must match the name of the outbound queue on the remote server. You can prompt (F4) on this field to advance to the Select MQ Queue Screen, where you can select a local queue that is associated with the default message queue manager. Alphanumeric, 48 positions; optional. |
|
Inbound XML message |
This field is not currently implemented. Alphanumeric, 50 positions; optional. |
The name of the job that interprets the XML message from CWIntegrate to CWDirect. If there are multiple process queues for a process, each instance of the job should have a unique name. Required for inbound process queues. Alphanumeric, 10 positions; optional. |
|
Outbound Processing: |
|
Outbound queue manager |
The MQSeries message queue manager on the machine where the remote queue is located. Required for outbound process queues. Alphanumeric, 48 positions; optional. |
The MQSeries message queue to which this process queue sends messages to the remote server. The queue you specify here must match the name of the inbound queue on the remote server. Required for outbound process queues. You can prompt (F4) on this field to advance to the Select MQ Queue Screen, where you can select a remote or local queue that is associated with the default message queue manager. Alphanumeric, 48 positions; optional. |
|
Outbound XML message |
This field is not currently implemented. Alphanumeric, 50 positions; optional. |
Note: You cannot create multiple process queues for the CCAUTH_BTH, CCAUTH_ONL, DEPOSITS, CC_TOKEN, SVC_OUT, SVC_BALANC, SVC_REVRSL, PAYAPPROVE, MERCH_LOC, EMAIL_OUT, or EC_ITEMAVL processes.
1. At the Work with Integration Layer Process Queues Screen, press F6 to advance to this screen in Create mode.
2. Complete the Desc and set the Enabled flag, and then any additional fields required for the process queue. Press Enter to accept your entries.
1. At the Work with Integration Layer Process Queues Screen, enter 2 next to a process queue to advance to this screen in Change mode.
2. Change any fields as needed and press Enter to accept your changes.
At the Work with Integration Layer Process Queues Screen, enter 5 next to a process queue to advance to this screen in Display mode. You cannot change any information.
Purpose: Use this screen to select a queue that is associated with the default message queue manager and default it to the Inbound queue field or Outbound queue field on the Integration Layer Process Queue Screen in create mode or change mode.
When you first advance to the Work with Integration Layer Process menu option, the system builds the MQ Queues work file to store the queues that are currently defined and associated with the default message queue manager. However, if MQ is down when you access the Work with Integration Layer Process menu option, the system does not rebuild the MQ Queues work file and instead displays the queues that were defined the last time someone accessed the menu option.
How to display this screen: Prompt (F4) on the Inbound queue field or Outbound queue field on the Integration Layer Process Queue Screen in create mode or change mode.
• If you prompt on the Inbound queue field, the system displays local queues only.
• If you prompt on the Outbound queue field, the system displays remote and local queues.
MQX0005 SELECT Select MQ Queue 7/20/05 9:02:16
Opt Queue Type CWINT
Type options, press Enter. 1=Select
CWINT_DOC.DATAVANTAGE.SVCACT.REQUEST.Q.95 *RMTQ CWINT_DOC.DATAVANTAGE.SVCACT.RESPONSE.Q.95 *LCLQ CWINT_DOC.DATAVANTAGE.SVCAUT.ONL.REQUEST.Q.95 *RMTQ CWINT_DOC.DATAVANTAGE.SVCAUT.ONL.RESPONSE.Q.95 *LCLQ CWINT_DOC.DATAVANTAGE.SVCAUT.REQUEST.Q.95 *RMTQ CWINT_DOC.DATAVANTAGE.SVCAUT.RESPONSE.Q.95 *LCLQ CWINT_DOC.DATAVANTAGE.SVCBAL.REQUEST.Q.95 *RMTQ CWINT_DOC.DATAVANTAGE.SVCBAL.RESPONSE.Q.95 *LCLQ CWINT_DOC.DATAVANTAGE.SVCDEP.REQUEST.Q.95 *RMTQ CWINT_DOC.DATAVANTAGE.SVCDEP.RESPONSE.Q.95 *LCLQ CWINT_DOC.DATAVANTAGE.SVCREV.REQUEST.Q.95 *RMTQ CWINT_DOC.DATAVANTAGE.SVCREV.RESPONSE.Q.95 *LCLQ CWINT_QA.DATAVANTAGE.SVCACT.REQUEST.Q.85.JAB *RMTQ +
F3=Exit F12=Cancel |
To select:
1. Enter a full or partial queue name in the Queue field and press Enter to scan for a queue. The system displays queues in alphanumeric order.
2. Enter 1 next to the queue you wish to select and press Enter. The system returns you to the Integration Layer Process Queue Screen and defaults the queue to the Inbound queue field or Outbound queue field.
Field |
Description |
Queue |
The name of an MQSeries message queue that is associated with the default message queue manager. • If you prompt on the Inbound queue field, the system displays local queues only. • If you prompt on the Outbound queue field, the system displays remote and local queues. To scan for a queue, enter a full or partial queue name and press Enter to display queues in alphanumeric order. Note: If you prompt on a field that already has a message queue defined, the system advances you to the Select MQ Queue screen and only displays the specified queue; however, you can clear the queue name and enter search criteria to scan for a queue. Note: The system does not validate that the queue you select is a valid queue. Alphanumeric, 50 positions; optional. |
Type |
Indicates if the queue is a remote or local queue. *LCLQ = Local queue. *RMTQ = Remote queue. Alphanumeric, 5 positions; optional. |
MQSeries Work with Messages Screen (Reviewing Messages)
Purpose: Use this screen to review the messages in the queue for a particular Integration Layer process. This option is available for inbound processes only.
How to display this screen: Enter 10 next to a process queue at the Work with Integration Layer Process Queues Screen.
MQSeries Work with Messages
Queue Manager Name . . : CWIAS400 Queue name . . . . . . . RDC.60.Q.CHASE.ONLINE.CCAUTH.RESPONSE
Type options, press Enter. 5=Display Description 8=Display Data
Opt Date Time Type UserId Format Size 20020102 16532113 DATAGRAM CMCNICHOLA MQSTR 1024+ 20020102 16532141 DATAGRAM CMCNICHOLA MQSTR 1024+ 20020102 16532166 DATAGRAM CMCNICHOLA MQSTR 1024+ 20020102 16532187 DATAGRAM CMCNICHOLA MQSTR 1024+ 20020102 16532234 DATAGRAM CMCNICHOLA MQSTR 1024+ 20020102 16532260 DATAGRAM CMCNICHOLA MQSTR 1024+ 20020102 16532279 DATAGRAM CMCNICHOLA MQSTR 1024+ 20020102 16532304 DATAGRAM CMCNICHOLA MQSTR 1024+ More... Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel F16=Repeat position to F17=Position to F21=Print |
If an inbound XML transaction exceeds the maximum message length: The maximum number of characters, including spaces, that an XML message can contain is 65,000.
If an inbound XML message exceeds the maximum message length, the system:
• Clears the XML message from the queue.
• Writes the truncated message to the integration layer process log file (ECLG or MQJAVALOG; see Working with XML Log Files). You will not be able to view the entire XML message, only the truncated contents.
• Creates a spool file containing the message: MQGET ended with reason code 000002079. The description of reason code 2079 is: Truncated message returned (processing completed). Note: You cannot view this spool file until you end the Integration Layer job.
• Processes the next XML message (unless it also exceeds the maximum message length).
If the XML message was for an order (Inbound Order XML Message (CWORDERIN)), the system will place the order in an error status and the order will contain no order detail lines. Note: An order received through the Generic Order Interface (Order API) can contain between 176 and 200 lines before the maximum message length is reached.
Purpose: From the Work with Integration Layer Process Queues Screen, you can clear the messages from a particular queue for an Integration Layer process if it becomes necessary for any reason. To do so, enter 14 next to a process queue. The system displays the Queue Clear Warning window.
Queue Clear Warning
Queue RDC.50.D.ORDER.CCAUTH.RESPONSE is about to be cleared. Press F9 to clear the queue, or F12 to return and not clear the queue.
F9=Accept Clear Request F12=Cancel |
To clear: Press F9 to clear the message queue.
Work with Integration Process Control Screen
Purpose: Use this screen to review the status of a batch of messages. This screen is useful if you need to troubleshoot the location of a batch message.
For example, for the CCAUTH_BTH integration layer job, you can review the status of a batch of authorizations; see Authorization Integration Summary for more information on how the system processes batch credit card authorizations via CWIntegrate.
Each batch status represents a record in the Integration Process Control file. The system creates a record in the Integration Process Control file when the system sends or receives a batch of messages via CWIntegrate.
The integration layer jobs that send a batch of messages via CWIntegrate are:
• CC Token Process
• Batch CC Auth Process
• Batch Deposit Process
• SVC Activation
• SVC Reversal
• SVC Balance Inquiry (only if the Perform Balance Inquiry during Batch Authorizations (J19) system control value is set to Y and you process balance inquiries before batch authorization)
Purging records in the IL Process Control file: When you start an integration layer job that is associated with records in the IL Process Control file, the system purges completed records in the IL Process Control file that are older than 7 days and purges records in any other status that are older than 30 days. See the Changing Process Status for more information on starting an integration layer job.
Reprocessing authorizations or deposits: Before you use the Reprocess Authorizations Screen (RPAA), Reprocess Drop Ship Authorizations Screen (RPDS), or Auto Deposit Screen (Send or Receive Deposits) to recover failed authorization or deposit transactions, you should first review the status of the records on the Work with Integration Process Control screen and verify that the only records that are in a status other than Complete are the records that require reprocessing.
How to display this screen: Enter 15 next to a process queue at the Work with Integration Layer Process Queues Screen.
MSX1366 DISPLAY Work with Integration Process Control 2/19/03 11:55:21
Process: CCAUTH_BTH Batch CC Authorization Queue: 1 Batch CC Authorization
Opt Job Status Date Time Reference ID
Type options, press Enter. 4=Delete 5=Display 11=Change status
PICK_GEN TRF Unknown status 2/12/03 21:13:03 2 PICK_GEN TRF Unknown status 2/13/03 9:55:55 3 PICK_GEN TRF Unknown status 2/13/03 10:23:10 4 PICK_GEN TRF Unknown status 2/13/03 10:41:31 5 PICK_GEN TRF Unknown status 2/13/03 11:02:11 6 PICK_GEN RCV Received (IDC Server) 2/14/03 10:44:09 7 PICK_GEN RCV Received (IDC Server) 2/14/03 9:24:52 8 PICK_GEN RCV Received (IDC Server) 2/13/03 16:39:41 9 PICK_GEN TRF Unknown status 2/14/03 11:04:06 10 PICK_GEN TRF Unknown status 2/14/03 11:05:29 11
F3=Exit F12=Cancel |
Field |
Description |
Process |
The name and description of the batch integration layer process whose integration process control records you are reviewing. Code: Alphanumeric, 10 positions; display-only. Description: Alphanumeric, 30 positions; display-only. |
Job |
The job name for the process associated with the integration process control record. For example, PICK_GEN displays for the integration process control records created for the Batch CC Authorization integration layer process; these records represent a batch of credit card authorizations sent to the authorization service via CWIntegrate. Alphanumeric, 10 positions; optional. |
Status |
The status of the integration process control record. CMP Complete indicates the batch message has been completed. FLD Error (Sending) indicates the batch message transmission has failed. SNT Sent indicates the batch message transmission has been sent to CWIntegrate. RCV Received (IDC Server) indicates the batch message transmission has been received from CWIntegrate and all background processing for the batch is complete. A batch may remain in a received status if the associated job, such as pick slip generation, has timed out or moved on before the batch could be updated to Complete. No further action is required for a batch that remains in a Received status; however, if the associated process was pick slip generation or deposits, you should verify that no records remain in a Sent status in the CC Authorization Transaction or CC Deposit Transaction file. RIN Receiving indicates the batch message transmission is in the process of being received. TRF Unknown status indicates the batch message is unknown and has not been transmitted. Note: • If the Immediate response field for the service bureau is set to Y, completed records remain in a RCV status and never update to CMP. • If the integration process control record is in a sent or error status, the system will continue to wait for a response for that record. You must resolve any errors before receiving the next transaction. Status code: Alphanumeric, 3 positions; optional. Status description: Alphanumeric, 24 positions; display-only. |
Date |
The date the batch message transmission was sent to or received from CWIntegrate. Numeric, 6 positions (MM/DD/YY format); display-only. |
Time |
The time the batch message transmission was sent to or received from CWIntegrate. Numeric, 6 positions (HH/MM/SS format); display-only. |
Reference ID |
The next available number from the Batch Auth File Trace Number number assignment value. Numeric, 16 positions; display-only. |
Screen Option |
Procedure |
Delete an integration process control record |
Enter 4 next to an integration process control record to delete it. |
Review an integration process control record |
Enter 5 next to an integration process control record to advance to the Display Integration Process Control Screen. |
Change the status of an integration process control record that is not yet complete |
Enter 11 next to an integration process control record to advance to the Change Status window. You cannot change the status of an integration process control record that is in a CMP complete status. |
Display Integration Process Control Screen
Purpose: Use this screen to review the details of an integration process control record.
This screen is useful if you need to troubleshoot the location of a batch message.
How to display this screen: Enter 5 next to an integration process control record at the Work with Integration Process Control Screen.
MSX1367 DISPLAY Display Integration Process Control 2/24/03 10:44:41
Process . . : CCAUTH_BTH Batch CC Authoriation Queue . . . : 1 Batch CC Authoriation Job # . . . : 704737 Job Name . . : PICK_GEN User . . . . : TBOTTGER
Status . . . : TRF Unknown status Date . . . . : 2/12/03 Time . . . . : 21:13:03 Reference ID : 2 Comment . . :
F3=Exit F12=Cancel |
Field |
Description |
Process |
The name and description of the batch integration layer process whose integration process control records you are reviewing. Code: Alphanumeric, 10 positions; display-only. Description: Alphanumeric, 30 positions; display-only. |
Job # |
The job number for the process associated with the integration process control record; this is the process that sent the batch message. Alphanumeric, 6 positions; display-only. |
Job name |
The job name for the process associated with the integration process control record. For example, PICK_GEN displays for the integration process control records created for the Batch CC Authorization integration layer process; these records represent a batch of credit card authorizations sent to the authorization service via CWIntegrate. Alphanumeric, 10 positions; display-only. |
User |
The user ID of the person who submitted the process associated with the batch messages. Alphanumeric, 10 positions; display-only. |
Status |
The status of the integration process control record. RDY indicates the batch message is ready for transmission. CMP Complete indicates the batch message has been completed. FLD Error (Sending) indicates the batch message transmission has failed. SNT Sent indicates the batch message transmission has been sent to CWIntegrate. RCV Received (IDC Server) indicates the batch message transmission has been received from CWIntegrate. RIN Receiving indicates the batch message transmission is in the process of being received. TRF Unknown status indicates the batch message is unknown and has not been transmitted. Note: If the integration process control record is in a sent or error status, the system will continue to wait for a response for that record. You must resolve any errors before receiving the next transaction. Status code: Alphanumeric, 3 positions; optional. Status description: Alphanumeric, 24 positions; display-only. |
Date |
The date the batch message transmission was sent to or received from CWIntegrate. Numeric, 6 positions (MM/DD/YY format); display-only. |
Time |
The time the batch message transmission was sent to or received from CWIntegrate. Numeric, 6 positions (HH/MM/SS format); display-only. |
Reference ID |
The next available number from the Batch Auth File Trace Number number assignment value. Numeric, 16 positions; display-only. |
Comment |
Informational error message regarding the batch message transmission, indicating an FTP transmission error has occurred. Alphanumeric, 60 positions; display-only. |
Change Status Window (Integration Process Control)
Purpose: Use this window to change the status of an integration process control record. You may wish to change the status of a record if you experienced communication problems and need to re-send or receive transactions.
You cannot change an integration process control record that is already in a CMP Complete status: Status Already Complete.
How to display this screen: Enter 11 next to an integration layer process control record at the Work with Integration Layer Process Queues Screen.
Change Status
1=Select
Complete Confirm (Deposits) Failed Ready Received Sent Transferred
F3=Exit |
To change: Enter 1 next to a status and press Enter to update the integration process control record to that status.
• Complete indicates the batch message has been completed.
• Confirm (Deposits) indicates the batch message has been confirmed.
• Failed indicates the batch message transmission has failed.
• Ready indicates the batch message is ready for transmission.
• Received indicates the batch message transmission has been received from CWIntegrate.
• Sent indicates the batch message transmission has been sent to CWIntegrate.
• Transferred indicates the batch message has been transmitted.
Defining Outbound Interface Trigger Rules
Outbound interface trigger rules define the criteria a record must meet in order for the system to create an IL outbound trigger. For each outbound process, you can define trigger rules for certain files, for example the Item Outbound job allows you to define trigger rules for the Item file and SKU file. If you define more than one criterion, the record must meet all of the criteria defined in order to generate a trigger.
• if the record meets the outbound process trigger rule criteria, the system creates a download trigger.
• if the record does not meet the outbound process trigger rule criteria, the system does not create a download trigger.
Example: For the ITEM_OUT process, you can specify to only create item download triggers for company 555, items that are SKUed and whose SKUs are located in warehouse 20. To do this, for the Item file trigger rules, enter EQ and 555 next to the Company trigger field and EQ and ’Y’ next to the Allow SKU’s trigger field. For the SKU file trigger rules, enter EQ and 20 next to the Warehouse trigger field.
Item file criteria |
SKU file criteria |
Results |
The Company field must equal 27 or 555. The Allow SKUs field must equal ’Y’. |
The Warehouse field must equal 20. |
The system generates a SKU trigger only if the item/SKU being created, updated, or deleted is in company 27 or company 555 and the item is SKU’d and the SKU is located in warehouse 20. If the item/SKU does not meet all of the criteria defined, a trigger is not created. |
You can define trigger rules for the following outbound processes.
For IL Process job: |
you can create trigger rules for: |
Example: |
BROKER_ ORD |
Item (INITEM) SKU (INSKU) |
You can specify to exclude drop ship items, non-inventory items, and membership items. To do this, enter NE and ’Y’ next to the Drop ship item, Non-inventory, and Membership trigger fields. This option is available regarudless of the version of Locate that you integrate with. See Order Broker Integration for background. |
ITEM_OUT |
Item (INITEM) SKU (INSKU) |
You can specify to only create item download triggers for company 555, items that are SKU’d and whose SKUs are located in warehouse 20. To do this: • in the Item file trigger rules, enter EQ and 555 next to the Company trigger field and EQ and ’Y’ next to the Allow SKU’s trigger field. • In the SKU file trigger rules, enter EQ and 20 next to the Warehouse trigger field. |
INVOIC_ OUT |
Invoice Header (OEINHD) Order Header (OEORDR) |
You can specify to only create invoice download triggers for debit invoices and not credit invoices. To do this, enter EQ and ’I’ next to the Invoice type trigger field. |
INV_ DOWNLD |
Item (INITEM) Item Warehouse (INIWRE) SKU (INSKU) Warehouse (INWRHS Item UPC (ITMUPC) |
You can specify to exclude drop ship items, non-inventory items, and membership items. To do this, enter NE and ’Y’ next to the Drop ship item, Non-inventory, and Membership trigger fields. |
PICK_OUT |
Pick Control Header (FLPCTH) |
You can specify by company only. |
SVC_ REMOTE |
Pick Control Header (FLPCTH) |
You can specify by company only. |
VENDOR_ OUT |
Vendor (POVEND) |
You can specify to create vendor download triggers only for companies 27 and 555 and vendor 202. To do this, enter LIST and 27 555 next to the Company trigger field and EQ and 202 next to the Vendor # trigger field. |
INVTRAN OUT |
Item Transaction History (INITHS) |
You can specify to create item transaction history triggers for companies 27 and 555 and warehouse 1. To do this, enter LIST and 27 555 next to the Company trigger field and EQ and 1 next to the Warehouse trigger field. |
To create a trigger rule, select the fields in the file for which you wish to define qualifications. These fields determine if an IL outbound trigger is created, based on the criteria defined. For each trigger field, you must define:
• a Test value: this value indicates how the system compares the record against the trigger rule criteria.
• a Value: this value defines the trigger rule criterion.
Example: For the Company trigger field, enter EQ in the Test field and 555 in the Value field. This indicates the system creates IL outbound triggers only for company 555.
Field type: The Type field indicates if the value you enter must be numeric or alphanumeric.
• N = the Value must be numeric.
• A = The Value is alphanumeric.
Note:
• When entering alphanumeric values, you must enter the value between single quotes: for example, ’Y’.
• When entering a list or range of values, separate each value with a space: for example, 27 555 or ’S F V’.
• If you define a Test value for a field you must also define a Value and vice versa.
• The system does not validate that the value you define for a trigger field is valid (if the field requires valid values) or is within the maximum field positions (for example, the Company field is 3 positions). Refer to your Field/File Listing to review field attributes for a file.
• Fields that exist in the file but are not included in the XML message are not included as a trigger field.
If the test value is: |
The value you define indicates: |
blank |
A trigger rule is not specified for the field. |
EQ (equal) |
The field must equal the trigger rule value. For example, the Company field must equal 555. |
GT (greater than) |
The field must be greater than the trigger rule value. For example, the Cost field must be greater than 5.00. |
GE (greater than or equal to) |
The field must be greater than or equal to the trigger rule value. For example, the Cost field must be greater than or equal to 5.00. |
LEFT (starting characters) |
The starting characters of the field must begin with the trigger rule value. For example, the Item number field must begin with A. Note: You can only use the LEFT test value with an alphanumeric field. |
LT (less than) |
The field must be less than the trigger rule value. For example, the Cost field must be less than 500.00. |
LE (less than or equal to) |
The field must be less than or equal to the trigger rule value. For example, the Cost field must be less than or equal to 500.00. |
LIST (equal to a listed value) |
The field must match a trigger rule value. For example, the Company field must match 27, 409, or 555. |
NE (not equal to) |
The field must not be equal to the trigger rule value. For example, the Company field must not be 25. |
NLEFT (ending characters) |
The starting characters of the field must not begin with the trigger rule value. For example, the Item number field must begin with a value other than *. Note: You can only use the NLEFT test value with an alphanumeric field. |
NLIST (not equal to a listed value) |
The field must not match a trigger rule value. For example, the Company field must not be 25 or 444. |
RANGE (falls within a defined range) |
The field must fall within the trigger rule value range. For example, the Ship via must fall within 1 and 5. |
Select Trigger Rules File Window
Purpose: This window displays if you can define trigger rules for more than one file.
You can define trigger rules for more than one file for the Item Outbound job and Invoice Outbound job. If you can only define trigger rules for one file, the system advances you directly to the Outbound Interface Trigger Rules Screen.
To select: Enter 1 next to a file to advance to the Defining Outbound Interface Trigger Rules, where you can define trigger rules for the file.
How to display this screen: Enter 14 next to an outbound process for which you can create trigger rules for more than one file.
Select Trigger Rules File
Process ITEM_OUT Item Outbound
Multiple Files exist for this process. Please select which one to use.
Opt File
Type options, press Enter. 1=Select
INITEM INSKU
F3=Exit F12=Cancel |
Field |
Description |
Process |
The code and name of the process for which you wish to create trigger rules. Alphanumeric, 10 positions; display-only. |
File |
The file for which you with to create trigger rules. Enter 1 next to a file to advance to the Defining Outbound Interface Trigger Rules. Alphanumeric, 10 positions; optional. |
Outbound Interface Trigger Rules Screen
Purpose: Use this screen to define trigger rules for an outbound job.
This screen appears different based on the outbound process for which you wish to define outbound trigger rules.
How to display this screen:
• Enter 14 next to an outbound process at the Work with Integration Layer Process Screen.
• Enter 1 next to a file at the Select Trigger Rules File Window.
ILX0012 CHANGE Outbound Interface Trigger Rules 1/30/03 12:36:52
Process ID . : ITEM_OUT Item Outbound File . . . . : INITEM
Field Test Value T Company LIST 6 713 555 N Item Number NLEFT '**' A Allow SKU's EQ 'Y' A Item avg cst N Cubing value N Drop ship item A FIFO cost N Item height N Kit type A Item length N Long SKU style A Long SKU vendor A Lot # tracking A Non-inventory A Partial units A +
F3=Exit F12=Cancel |
Field |
Description |
Process ID |
The code and name of the outbound process for which you wish to create trigger rules. Alphanumeric, 10 positions; display-only. |
File |
The file for which you wish to create trigger rules. Alphanumeric, 10 positions; display-only. |
Field |
The field in the file for which you can create a trigger rule. When evaluating a record to determine if an IL outbound trigger is created, the system compares the record’s field value against the trigger rule defined for the field. Alphanumeric, 15 positions; display-only. |
Test |
Indicates how the system compares the record against the trigger rule criteria. blank = A trigger rule is not specified for the field. EQ = The field must equal the trigger rule value. GT = The field must be greater than the trigger rule value. GE = The field must be greater than or equal to the trigger rule value. LEFT = The starting characters of the field must begin with the trigger rule value. You can only use the LEFT test value with an alphanumeric field. LT = The field must be less than the trigger rule value. LE = The field must be less than or equal to the trigger rule value. LIST = The field must match a trigger rule value. NE = The field must not be equal to the trigger rule value. NLEFT = The starting characters of the field must not begin with the trigger rule value. You can only use the NLEFT test value with an alphanumeric field. NLIST = The field must not match a trigger rule value. RANGE = The field must fall within the trigger rule value range. If you define a Test value you must also define a Value. Alphanumeric, 5 positions; optional. |
Value |
Defines the trigger rule criterion. The system compares the trigger field value against the value defined for the field in the record. • If the record meets the trigger rule criteria, the system creates an IL outbound trigger. • If the record does not meet the trigger rule criteria, the system does not create an IL outbound trigger. When entering alphanumeric values, you must enter the value between single quotes; for example ’Y’. When entering a list or range of values, separate each value with a space; for example, 27 555 or ’S F V’. If you define a Value you must also define a Test value. Alphanumeric, 50 positions; optional. |
T (field type) |
Indicates if the value you enter must be numeric or alphanumeric. N = the Value must be numeric. A = The Value must be alphanumeric. Note: When entering alphanumeric values, you must enter the value between single quotes; for example ’Y’. Alphanumeric, 1 position; display-only. |
Outbound Interface XML Inclusion Screen
XML inclusion defines which elements to include in a download message.
• If the element is included, that element and its parents are included in the generated download XML message.
• If the element is excluded, that element and its children are excluded from the generated download message.
Remember: Parent elements are those elements that nest other elements; any elements nested underneath the parent element are its children.
Example: Some of the elements in the generic item download message are displayed below. In this example: Item is the parent of ItemInformation and ItemInformationDetail. ItemInformation is the parent of ItemInformationDetail and the child of Item. ItemInformationDetail is the child of ItemInformation and Item.
IItem
SKU
UPC
Warehouse
ItemWarehouse
• If you include the Item element, you can still exclude the SKU element. If you exclude the Item element, the SKU element and its children (UPC, Warehouse, and ItemWarehouse) are also excluded.
• If you include the UPC element, the system automatically includes the SKU element. You can still exclude the Warehouse element.
• If you exclude the Item element, the process still generates an “empty” message with just the top element information. For example, if you exclude the entire message for the INV_DOWNLD process, the resulting “empty” message would resemble:
<Message source="CWDirect" target="CWIntegrate" type="CWInventoryDownload" date="02112005" time="10:38:10">
</Message>
This screen appears different based on the outbound process for which you wish to define XML inclusion rules.
You can define XML inclusion rules for the following outbound processes:
When you first advance to the screen, all elements are included.
How to display this screen: Enter 15 next to an outbound process at the Work with Integration Layer Process Screen.
ILX0018 DISPLAY Outbound Interface XML Inclusion 1/30/03 15:21:26
Process ID: ITEM_OUT Item Outbound
Opt I Element
Type options, press Enter. 7=Include 8=Exclude
Y Item Y ItemInformation Y ItemInformationDetail N ItemComment N ItemAttribute N SourcePrice N Coordinate N Keyword N Image N Upsell N Restriction +
F3=Exit F12=Cancel |
Field |
Description |
Process ID |
The code and name of the outbound process for which you wish to create XML inclusion rules. Alphanumeric, 10 positions; display-only. |
I (include?) |
Indicates whether the element is included in the download XML message. Y = the element and its parent(s) are included in the XML message. N = the element and its children are not included in the XML message. Enter 7 next to an element to include it and its parents in the generated XML messages. The system updates this field for the element and its parents to Y. Enter 8 next to an element to exclude it and its children in the generated XML messages. The system updates this field for the element and its children to N. Alphanumeric, 1 position; optional. |
Element |
The name of an element tag to include or exclude in the download XML message. Alphanumeric, 30 positions; optional. |
Screen Option |
Procedure |
Include the element tag and its parents |
Enter 7 next to an element. The Include field for the element and its parents updates to Y. |
Exclude the element tag and its children |
Enter 8 next to an element. The Include field for the element and its children updates to N. |
Select XML Message Version Screen
Purpose: Use this screen to select the version of an outbound XML message to be generated by a system-delivered integration layer job. By default, each process generates version 1.0, but you can select a higher version if it is available. See XML Versions for an overview.
How to display this screen: Enter 16 next to a process at the Work with Integration Process Control Screen. This option is not available for processes that do not generate outbound XML messages.
XMX0023 SELECT Select XML Message Version 2/17/04 17:15:24
Message CWCUSTHISTOUT
Version 1.0
Type options, press Enter. 1=Select
1.0
F3=Exit |
Completing this screen: Enter 1 next to the XML version you would like to generate. Afterward, stop and restart the process at the Work with Integration Process Control Screen to have your change take effect.
Note:
• The SVC_REVRSL process uses the outbound XML version for the Stored Value Card Activation integration layer process defined for the service bureau, not the outbound XML version you define for the SVC_REVRSL process. For example, if you enter SVC_OUT in the SVC activation field for the service bureau, the system uses the outbound XML version defined for this process when generating the SVC Authorization Reversal Request Message.
• The CUST_HIST process uses the outbound XML version for the Detailed Order XML Response (CWORDEROUT) generated by the ORDER_IN process, since the ORDER_IN process also generates this response message. See Generic Customer History API for a discussion of when the CUST_HIST process generates the Detailed Order XML Response (CWORDEROUT) and when it generates a different response message.
• The outbound XML version for the EMAIL_OUT process must be at least 2.0 in order to generate the credit card credit, backorder, soldout, or stored value card notices through the Outbound Email API. If the outbound XML version is not set correctly and you attempt to generate these notices based on the Use email API setting for the related email template, the system does not generate the XML messages or the email notifications. See the Outbound Email API for background.
Troubleshooting Integration Layer Processes
Purpose: Use the steps described below to help troubleshoot any problems with the integration layer processes.
• Are the Processes Out of Sync?
Are the Processes Out of Sync?
The integration layer processes can get out of sync if, for example, your iSeries is stopped and restarted for any reason while the process is active. In this situation, the process might not actually be running, even though the status displayed at the Work with Integration Layer Process Screen is Active.
Is the process really active? To determine if particular process is actually active, check whether the Start date at the Work with Integration Layer Process screen is the current date. If not, check whether there has been an IPL (initial program load) of the iSeries since the displayed Start date.
If you are the user who started the process initially, use the Work with Submitted Jobs screen (F14 from a menu) to see if the process is Active at this screen.
Correcting an out-of-sync process: If a process’s Start date is not consistent with the current date or is earlier than the last IPL, enter 11 next to a process to advance to the Change Status Window and change the status to Inactive. Once the status changes, enter 7 next to a process to restart it.
Note: Do not enter 8 next to a process in this situation. However, if you have already attempted to end a process by entering 8 next to the process, the process will end again shortly after you restart it. If you have attempted to end it several times by entering 8 next to it, you will need to restart it again for each time you selected to end it. The reason is that, by entering 8 next to a process, you add an END command to the queue for the process. Each time you restart the process, it processes each END command waiting in the queue until all of the END commands are completed.
Correcting an out-of-sync process that uses a Java program: Certain processes use a Java program to build outbound messages. These processes require three active jobs, displayed at the Work with Submitted Jobs screen:
• a job identifying the integration layer process (for example, ITEM_OUT or STORE_PKUP)
• a QBATCH job running the function CMD-RUNJAVA
• a QJVACMDSRV job
If all of these three jobs are not actually active, the process cannot run correctly. If only one or two of these jobs are active, you need to end them at the Work with Submitted Jobs screen. Once all jobs are ended, return to the Work with Integration Layer Process screen. If the status of the process here is Active, change it to Inactive as described above, and then restart the process. Return to the Work with Submitted Jobs screen and make sure that all three of the jobs have restarted and remained active. If the two additional jobs repeatedly end shortly after you start the process, try changing the status to inactive rather than ending the process, and then restart the process again.
Once you have restarted the process that uses a Java program, check to make sure that all messages generated while the process was out of sync were sent correctly to their destinations.
Illegal characters: One reason that a process and its Java programs might be out of sync is if one of the fields that the process is attempting to send in the message contains illegal characters. In this situation, the system writes records to the daily ECLG file, but the process is unable to generate the outbound message. See the contents of individual outbound messages (Summary of XML Messages and CWIntegrate Sites) to troubleshoot.
Every day, the system creates a new log file to track all XML messages generated or received by CWDirect, including all of those related to the integration layer processes and the e-commerce jobs. You can use this file to confirm that you are receiving or generating messages correctly, to isolate communication problems, or to recover information.
How to display the file: The file name consists of the prefix ECLG and the current date in YYMMDD format. At a command line, while you are logged into CWDirect, enter DSPPFM ECLG080628 to display the contents of the file for June 28, 2008 (080628). To see the most recently written messages, enter B in the Control field to advance to the bottom of the file.
Display Physical File Member File . . . . . . : ECLG080411 Library . . . . : CWMC0QDTA Member . . . . . : ECLOGF Record . . . . . : 12 Control . . . . . B Column . . . . . : 1 Find . . . . . . . *...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+... 2008-04-1112.37.58QPADEV000KSCARTER 361018R<Message source="CWINTEGRATE 2008-04-1112.40.19QPADEV000KSCARTER 361018S<Message source="CWDIRECT" t 2008-04-1112.40.21INVINQ_12 SCARTER 360256R<Message source="193" target 2008-04-1112.40.21INVINQ_12 SCARTER 360256S<Message source="CWDirect" t 2008-04-1112.40.23QPADEV000KSCARTER 361018R<Message source="CWINTEGRATE 2008-04-1114.39.13QPADEV000KSCARTER 361018S<Message source="CWDIRECT" t 2008-04-1114.39.20INVINQ_12 SCARTER 360256R<Message source="193" target 2008-04-1114.39.22INVINQ_12 SCARTER 360256S<Message source="CWDirect" t 2008-04-1114.40.41QPADEV000KSCARTER 361018S<Message source="CWDIRECT" t 2008-04-1114.40.42INVINQ_12 SCARTER 360256R<Message source="193" target 2008-04-1114.40.42INVINQ_12 SCARTER 360256S<Message source="CWDirect" t 2008-04-1114.40.44QPADEV000KSCARTER 361018R<Message source="CWINTEGRATE 2008-04-1114.42.22QPADEV002NEKAPLAN 361273S<Message source="CWDIRECT" t 2008-04-1114.42.22QPADEV000KSCARTER 361018S<Message source="CWDIRECT" t 2008-04-1114.42.27QPADEV002NEKAPLAN 361273R<Message source="CWINTEGRATE More... F3=Exit F12=Cancel F19=Left F20=Right F24=More keys |
By advancing to the right, you can review the entire contents of an XML message.
If no message is generated for a particular integration layer process: One thing to check if a single integration layer process is not writing a message to the current ECLG file is whether the outbound MQSeries queue specified for the process was created correctly on the iSeries.
How is the date for the file determined? If a process runs for more than one day, it writes to the ECLG file for the current date, not the date when you started the job. For example, if you start the ORDER_IN process on August 26, 2008, and it is still running on August 27, it writes new log entries in the ECLG080827 file rather than the ECLG080826 file.
If the ECLG file is empty: The ECLOGFMQMSG data area controls whether you write log messages to the daily ECLG file. To check or change the setting:
• While you are logged into CWDirect, enter WRKDTAARA at a command line. You advance to the Work with Data Areas screen.
• Enter ECLOGMQMSG in the Data area field. The ECLOGMQMSG data area and its library are displayed. You can:
• Review: Enter 5 next to ECLOGMQMSG to determine if writing to a daily ECLG file is currently selected. A value of ’1’ indicates that writing to a daily ECLG file is selected, while a setting of ’0’ indicates that it is not.
• Change: Enter 2 next to ECLOGMQMSG to change the setting.
Purging outdated ECLG files: Use the Purging ECLG Files (PECF) menu option to delete outdated ECLG files.
Logs for processes that use a Java program: As described above, certain integration layer processes use a Java program to generate outbound messages. For example, the ITEM_OUT process uses a Java program, reading trigger records and generating outbound XML messages based on the key information indicated by each trigger.
Unlike the other integration layer processes, these processes use both the daily ECLG file and a separate log file, available in the MQJAVALOGS folder:
• the ECLG record indicates the particular trigger used to generate the full outbound message. In addition, if the message contains credit card data and you are using credit card encryption, the system includes the key encryption key, in a scrambled format, in order to encrypt and decrypt the credit card data in the message correctly. For example, the ECLG record might consist of the following, based on the Key information, such as company, item, and SKU, for the trigger:
<?xml version='1.0' encoding='ISO-8859-1'?>
<Message source="CWDIRECT" target="CWINTEGRATE" type="CWMessageBuilder">
<Parameter>ITEM_OUT SKU "005KABSKU1 GRN " C CWIAS400 CWMPDTA CWMPDTA EMOZART EMOZART LOCAL "0000000000325"
</Parameter>
</Message>
• the MQJAVALOGS record provides the full contents of the outbound XML message
How to display records in the MQJAVALOGS folder: This folder is available under the root folder of the iSeries. To display this folder, you can:
• map a network drive: Using Windows Explorer, select Tools > Map Network Drive and specify a folder of \\as400\root\, where as400 represents the name of your iSeries
• specify the IP address of the iSeries: Using Windows Explorer, enter \\123.45.67.8\root in the Address field, where 123.45.67.8 represents the IP address of your iSeries
You might need to specify a user ID and password for access to the iSeries. Be sure to specify the user ID and password for the iSeries rather than for regular network access if these two are different. For example, you might need to specify a user ID of CWIAS400\TJONES if the name of your iSeries is CWIAS400. Enter your user ID and password in all capital letters.
Once you have displayed the root folder, open the MQJAVALOGS folder to review the detailed logs for each process that uses a Java program. The log files in this folder use the naming convention of ITEM_OUT2003-12-01, where:
• ITEM_OUT represents the integration layer process that generated the outbound message
• 2003-12-01 represents the year, month and day of the log in YYYY-MM-DD format
A new log file is generated for each integration layer process and date.
To view the contents of a log file, open it with a text editor. If the message is difficult to read, you can copy just the XML message itself and save it as a separate file with the .xml extension: this allows you to open and view the message in the browser.
Masking sensitive data: CWDirect masks sensitive data, such as credit card number, CID number, account number, and all personal data (such as person or company name, mailing address, email address, and phone number) in the ECLG and MQJAVALOGS files. The system uses the XML Removed by Logger table to determine which message tags are masked in the log files. This table lists all message tags that contain sensitive data. If a tag in a message matches a message tag in this table, CWDirect masks the value in the tag; otherwise, the actual value displays.
Note: Masking applies only to XML tags, or attributes, in the message. You cannot mask an XML element.
Translating Special Characters in Outbound Messages
CWDirect replaces special characters as follows in outbound XML messages:
Special Character |
Description |
Replaced with: |
’ |
single quote |
' |
" |
double quote |
" |
> |
greater than |
> |
< |
less than |
< |
& |
ampersand |
& |
Other special characters (such as $ or !) are not replaced.
Summary of XML Messages and CWIntegrate Sites
Overview: The following table presents the XML messages processed through CWDirect, including the base CWIntegrate site(s), if any, that use the message.
Not included in table: This table does not include unique CWIntegrate sites.
Message |
Process(es) |
Direction |
CWIntegrate Site(s) |
CWIntegrate Processes The following XML messages are processed through the Working with Integration Layer Processes (IJCT) menu option. See CWIntegrate Processes for a description of each process. |
|||
ARBATCH_IN |
inbound |
cw_arpayments |
|
BROKER_ORD BROKER_STS |
outbound |
cw_locate (if the Locate Platform is set to .NET) |
|
inbound |
|||
Credit Card Application Request Message (CWCreditCardApplicationRequest) |
CREDIT_APP |
outbound |
|
Credit Card Application Response Message (CWCreditCardApplicationResponse) |
inbound |
|
|
CC_TOKEN |
outbound |
cw_litle |
|
inbound |
cw_litle |
||
CCAUTH_BTH CCAUTH_ONL SVC_BALANC SVC_OUT SVC_REVSL |
outbound |
cw_chase_fdms cw_paymentech cw_npc_multilink cw_datavantage cw_valuecard cw_cybersource cw_litle |
|
Authorization Response XML Message (CWAuthorizationResponse) |
inbound |
cw_chase_fdms cw_paymentech cw_npc_multilink cw_datavantage cw_valuecard cw_cybersource cw_litle |
|
DEPOSITS |
outbound |
cw_chase_fdms cw_paymentech cw_npc_multilink cw_datavantage cw_valuecard cw_cybersource cw_litle |
|
inbound |
cw_chase_fdms cw_paymentech cw_npc_multilink cw_datavantage cw_valuecard cw_cybersource cw_litle |
||
Stored Value Card Remote Fulfillment Request (CWSVCRemoteOut) |
SVC_REMOTE |
outbound |
|
Stored Value Card Remote Fulfillment Confirmation (CWSVCRemoteIn) |
inbound |
|
|
CUSTOMR_IN |
inbound |
|
|
CUST_SRCH |
inbound |
|
|
outbound |
|
||
CUST_HIST |
inbound |
cw_store |
|
outbound |
cw_store |
||
Detailed Customer History Response XML Message (CWORDEROUT) or Summary Order Inquiry Response XML Message (CWORDEROUT) (see also Detailed Order XML Response (CWORDEROUT) and Order Acknowledgement XML Message (CWORDEROUT)) |
CUST_HIST ORDER_IN |
outbound |
cw_store |
inbound |
cw_email |
||
EMAIL_OUT |
outbound |
|
|
INV_DOWNLD |
outbound |
cw_store cw_merch locator |
|
INV_INQURY |
inbound |
cw_merch locator |
|
Inventory Inquiry Response XML Message (CWInventoryInquiryResponse) |
outbound |
cw_merch locator |
|
INVOICE_OUT |
outbound |
cw_store |
|
Inventory Transaction Upload XML Message (inCreateInvXaction) |
INVTRANS_IN |
inbound |
cw_store |
Item Transaction History Outbound XML Message (CWInvXActionOut) |
INVTRANOUT |
outbound |
|
ITEM_OUT |
outbound |
cw_store cw_merch locator |
|
Merchandise Locator Request XML Message (CWMerchLocRequest) (.NET) |
MERCH_LOC |
outbound |
cw_merch locator |
Merchandise Locator Response XML Message (CWMerchLocResponse) |
inbound |
cw_merch locator |
|
ORDER_IN |
inbound |
cw_store |
|
CW_OLH |
inbound |
|
|
CW_OTH |
inbound |
|
|
Online Cash Payment Approval Request (CWPaymentApprovalRequest) |
PAYAPPROVE |
outbound |
cw_ebillme |
Online Cash Payment Approval Response (CWPaymentApprovalResponse) |
inbound |
cw_ebillme |
|
Online Cash Payment Confirmation Response (CWPaymentConfirmationResponse) |
PAYMENT_IN |
inbound |
cw_ebillme |
PICK_OUT |
outbound |
cw_scancode |
|
PROMOTION |
inbound |
|
|
Promotional Pricing Response Message (CWPromotionalResponse) |
outbound |
|
|
RETURN_IN |
inbound |
|
|
outbound |
|||
Store Fulfillment Request XML Message (StoreFulfillmentRequest) (.NET) |
STORE_PKUP |
outbound |
cw_store |
SUP_INQURY |
inbound |
|
|
outbound |
|
||
TRIGGER_DL |
outbound |
|
|
TAX_INT |
outbound |
|
|
TAX_INT |
inbound |
|
|
VENDOR_OUT |
outbound |
cw_store |
|
WORKFLOW |
inbound |
cw_workflow |
|
E-Commerce Processes The following XML messages are processed through the Working with E-Commerce Job Control (EJCT) menu option. See E-Commerce Processes for a description of each process. |
|||
CUSTOMER UPDATES |
inbound |
|
|
E-Commerce Name/Address Change Response Message (CWCchgResponse) |
outbound |
|
|
ITEM AVAILABILITY |
inbound |
|
|
E-Commerce Item Availability Response Message (CWAvailResponse) |
outbound |
|
|
CANCELS |
inbound |
|
|
CATALOG REQUESTS |
inbound |
|
|
E-Commerce Catalog Request Response Message (CWCatreqResponse) |
outbound |
|
|
ORDER PROCESSING |
inbound |
|
|
ORDER PAYMENT/ ACCEPT |
inbound |
|
|
ORDER PROCESSING ORDER PAYMENT/ ACCEPT |
outbound |
|
|
ORDER REJECT/ CANCEL |
inbound |
|
|
ORDER INQUIRY BY CUSTOMER |
inbound |
|
|
outbound |
|
||
MAINTENANCE |
inbound |
|
|
outbound |
|
||
RETURNS |
inbound |
|
|
outbound |
|
||
ORDER STATUS/ INQUIRY |
inbound |
|
|
outbound |
|
||
WMS Processes The following XML messages are processed through the Working with WMS MQ Job Control (WMJC) menu option. See WMS Processes for a description of each process. |
|||
CUSTOMER RETURNS EXPORT |
outbound |
cw_pkms |
|
outbound |
cw_pkms |
||
IMMDIATE NEEDS EXPORT |
outbound |
cw_pkms |
|
outbound |
cw_pkms |
||
INVOICES |
inbound |
cw_pkms |
|
GENERIC INVOICES |
inbound |
cw_pkms |
|
ITEM EXPORT |
outbound |
cw_pkms |
|
outbound |
cw_pkms |
||
ITEM NOTES EXPORT |
outbound |
cw_pkms |
|
PICK TICKET EXPORT STOP SHIPMENTS |
outbound |
cw_pkms |
|
PICK TICKET EXPORT |
outbound |
cw_pkms |
|
PIX_PKMS |
inbound |
cw_pkms |
|
GENERIC PIX TRANSACTION |
inbound |
cw_pkms |
|
PURCHASE ORDERS EXPORT |
outbound |
cw_pkms |
|
outbound |
cw_pkms |
||
Generic WMS Stop Shipment Request XML Message (CWStopShipment) |
STOP SHIPMENTS |
outbound |
cw_pkms |
PkMS Vendor XML Message (VendorMaster_1_0, VendorContact_1_0) |
VENDOR EXPORT |
outbound |
cw_pkms |
outbound |
cw_pkms |
||
VENDOR CONTACTS EXPORT |
outbound |
cw_pkms |
|
VENDOR NOTES EXPORT |
outbound |
cw_pkms |
|
Retail Integration Processes The following XML messages are processed through the Retail Integration Job Control (RIJC) menu option. See ASYNC Processes for the Retail Integration (from an External System into CWDirect) for a description of each process. |
|||
ITEM UPLOAD |
inbound |
|
|
outbound |
|
||
RETAIL PRICE CHANGE UPLD |
inbound |
|
|
| Purging Active Procedures | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Purging ECLG Files (PECF) |
SO01_10 CWDirect 18.0.x 2018 OTN