-
Type: Feature Request
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: CFA 2021R1
-
Component/s: None
-
INF Reference Number:INF-12257
- See: https://cfacorp.atlassian.net/l/c/9e1wuAfB
- A new row was added to tbTaskXSLTWebService for the AWS S3 bucket for backup orders. The WebserviceType is defined as “'OrderBackupDestination'”. After deploying this feature the consulting team will need to update the corresponding values for the record.
- select * from tbTaskXSLTWebService where WebServiceType = 'OrderBackupDestination'
- select * from tbAppSettings where SettingName = 'OrderDefaultDistribution'
- The configuration around the directory (for example, SyscoDir) were moved from the Mx.config file to tbAppSettings. They are added under SettingName “'OrderDefaultDistribution'”. The default schema change was added with the corresponding “OrderDefaultDistribution” in all CFA Environments with corresponding file paths from Mx.Config file.
- Consultants need to verify the paths are correct in the corresponding environments.
Non-Production S3 Details
- Ben has created a “order-backup” folder in the dev-bdapdev-us-east1-inform-ftp bucket where are other files go. (The credentials for this bucket should be available on Testing.
- "In terms of different folders for each distributor, if your “put” command just adds a prefix, S3 will automatically create sub directories based on prefix. So feel free to send each different distributor with the naming of your choice. For example: Martin Brower orders sent to “dev-bdapdev-us-east1-inform-ftp/order-backup/martin-brower/Filename” would then create a new martin-brower directory within the “order-backup” directory."
Request from CFA:
As an additional ordering contingency, all Order XML files should be placed in an S3 bucket. This action should happen successfully even if the AS2 server(s) are un-reachable/unavailable.
Business case
- Recently the AS2 server went down, and we had no way to transmit xml files, as the server (and files) could not be accessed for several hours. ("So having them in S3 gives us a bit of an insurance policy if primary AS2 goes down")
- Note: Yes the admin order history does provide the ability to download pdf and excel versions of the orders, but in the situation where the whole server went down, this was a labor intensive undertaking, and meant that normal order cut off times were missed
- The goal would be for us to have them readily available, and also for some of other hurricane/weather scenarios we’ve had recently where an already-placed order needed to be “given” to another Distributor for fulfillment.
Notes
- The process to send purchase orders works outside and independently of the normal data export framework
- The data export framework was enhanced to provide multi destination
- Purchase Order xml files are written directly to the AS2 server
- This is configured on the PO Setup Page: https://inform.jatesting.cfahome.com/MMS_HO_PurchaseOrderSetup.aspx
- the path configured on this page, is the final folder of the file path, the main path is defined in mxconfig (Sysco)
- Back in the day we implemented MX-21271 (MMS - Apply Changes to Order function to provide Order Report Autonomy, as implemented in MxC)
- From this ticket, and in reference to the order submission process:
- There are times when this process breaks down, such as when Reporting Services fails, used to generate the PDF send by the Auto Notification. When this happens the whole order fails, and as a result the order does not get submitted to the AS2 server.
- The purpose of this feature is to make each of these components, of submitting an order, autonomous, so that in the event that one piece fails, the others can still complete successfully.
- Segmentation of the components (Submit Order, Auto Notification with PDF, send order to AS2)
- From this ticket, and in reference to the order submission process:
Non-Production S3 Details
- Ben has created a “order-backup” folder in the dev-bdapdev-us-east1-inform-ftp bucket where our other files go. (The credentials for this bucket should be available on Testing.
- "In terms of different folders for each distributor, if your “put” command just adds a prefix, S3 will automatically create sub directories based on prefix. So feel free to send each different distributor with the naming of your choice. For example: Martin Brower orders sent to “dev-bdapdev-us-east1-inform-ftp/order-backup/martin-brower/Filename” would then create a new martin-brower directory within the “order-backup” directory."
- is implemented by
-
CFAMX-11529 Send Orders - Load Testing - Send Order Xml file to a secondary destination
- Closed
-
CFAMX-11534 Send Orders - Documentation - Send Order Xml file to a secondary destination
- Closed
-
CFAMX-11810 Send Order Xml file to a secondary destination
- Closed
-
CFAMX-11960 Order XML to AS2 Spike
- Closed
-
CFAMX-12071 Order XML Update: Hard-Coded Data
- Closed
-
CFAMX-12079 New Backup On Order Export Failure Auto Notification
- Closed
- relates to
-
CFAMX-12719 S3 Object is not being created per vendor
- Done