Field
Description
Settings
UI Timeout
The number of minutes that Order Broker Cloud Service should wait before timing out a user’s inactive session. When the session times out, the screen displays an error when the user next clicks an option or attempts to navigate in Order Broker Cloud Service, and needs to close the browser before logging back in to Order Broker Cloud Service.
Your entry can be 1 to 999 minutes. Required.
The default setting is 30 minutes.
Select this option to be able to use the Routing Engine and see related screens.
Required settings:
• If you select the Use Store Connect option but not this option, this option is selected automatically.
• Order Broker Cloud Service requires that at least this option or the Use Vendor Portal option are selected. If you don’t select any of the module use options, the Use Routing Engine option is selected automatically.
See the Home Screen for information on screen access controlled by this setting.
Note: This field is also available to a retailer user at the Tenant (retailer information) screen.
Lock Out
The number of unsuccessful, sequential login attempts that triggers Order Broker Cloud Service to disable a user account. When a user attempts to log in with a disabled account, Order Broker Cloud Service displays a general error indicating that the login failed.
Example: If you set this number to 4, a user account is disabled after the entry of 4 incorrect passwords in a row.
Reset: A user’s counter is reset:
• after a successful login (for example, if there are 3 unsuccessful login attempts, followed by a successful login, the counter is reset to 0
• when you re-enable the account at the User Profiles screen or the User Profile Configuration screen
Note: If you change the user account back to Active status, the account remains disabled until the Lockout Duration specified in the User Lockout options in WebLogic has passed.
LDAP user? If the user is flagged for LDAP authentication, the lockout counter does not apply, and the user’s Order Broker Cloud Service user account is not disabled, even if the login attempts exceeds the Lock Out number; however, the user’s general LDAP authority may be suspended based on the general LDAP settings, which effectively locks the user out of Order Broker Cloud Service.
Your entry can be 1 to 99 login attempts. The default setting is 5. Required.
Select this option to be able to have the Store Connect module available and to have a process poll for new delivery or pickup orders assigned to Store Connect locations. This option also requires the Routing Engine. If you select this option and don’t select Use Routing Engine, the Use Routing Engine option is selected automatically.
See the Home Screen for information on screen access controlled by this setting.
Note: This field is also available to a retailer user at the Tenant (retailer information) screen.
Tenant Logo
The URL for the logo to display at the Store Connect login page at a size of 254 x 33 pixels.
Preview the logo:
After entering the URL, click the preview icon (
) to preview the image at 254 x 33.
Note: This field is also available to a retailer user at the Tenant (retailer information) screen.
Select this option to have the Drop Ship (Supplier Direct Fulfillment) module available.
See the Home Screen for information on screen access controlled by this setting.
Note: This field is also available to a retailer user at the Tenant (retailer information) screen.
Account
The name of the Order Broker Cloud Service database. The destination specified in inbound XML messages must match this setting. The default setting is locate. Required.
Once you set the account, it should not ordinarily be changed.
Time Zone
The time zone to use when setting schedules and displaying dates and times on screens, in reports, and in email notifications. This is the retailer’s time zone, which can be different from the system time zone and the user’s time zone. See Time Zones for a discussion. Display-only.
Changing the time zone: When the time zone here is reset by the retailer, the following should also be reset:
• New order polling schedule at the Store Connect Preferences screen
• Report schedules, through the Schedule Reports screen
• Imports, through the Schedule Imports screen
• Incremental inventory import, probable quantity update and export, and fulfilled inventory export, at the System screen
Email Settings
Email Template Path
The folder on the Order Broker Cloud Service server where email templates are stored.
The template path should not ordinarily be changed. Required.
Email Interval
The number of minutes that Order Broker Cloud Service should wait before generating:
• an updated Order Broker Polling Status Email, providing a list of orders that have not yet been acknowledged by the assigned fulfilling location. Order Broker Cloud Service sends this email to the system’s System Ops Email address if:
• the system is flagged to Require Status Update, and
• there are any orders whose Poll Count exceeds the system’s Polling Retries setting
See Require Status Update for Assigned Orders? for a discussion.
• Supplier Direct Fulfillment notifications to the assigned vendor or the retailer. See Supplier Direct Fulfillment Module Email Notifications Summary for a listing.
• Store Connect notification emails to the assigned fulfilling store, the retailer, or to the customer. See the Store Connect Email Notifications Summary for a listing.
Up to 6 positions. The default setting is 15 minutes.
Note:
• If you set this interval to 0, no emails are generated.
• This field is also available to a retailer user at the Tenant (retailer information) screen.
Retention Settings
The following settings control the number of days to retain certain types of files on a server or records in the database.
If set to 0 days: If you set one of the following to 0 days, then all files or records are purged the day after creation.
Report Files
The number of days to retain records of generated reports. After this number of days, a time-based scheduler automatically deletes the database records, so it is no longer possible to print the reports. Can be from 0 to 30 days. Required.
The number of days to retain entries in log files on the server before a time-based scheduler automatically deletes them. Can be from 0 to 30 days. Required.
See the Clean Up Schedule setting for information on how log files are renamed or deleted.
Access to server logs is available only to the cloud operations team.
Product Import Files
The number of days to retain import files before a time-based scheduler automatically deletes them. Can be from 0 to 30 days. Required.
For more information: See Importing Items/Products, Inventory, Barcodes, and Locations into the Database and Incremental Inventory Import for background.
Pack Slip Files
The number of days to retain pack slip records for purchase orders that have been shipped through the Vendor Portal. After this number of days, a time-based scheduler automatically deletes the database records, so it is no longer possible for the vendor to print the pack slips. Can be from 0 to 30 days. Required.
Note:
• This setting does not control the retention of pack slip records generated through Store Connect. Order Broker Cloud Service automatically deletes these database records shortly after they are generated; the store associate cannot reprint pack slips using these records.
• Used only by the Supplier Direct Fulfillment module.
The time of day to rename the previous day’s log files or to delete outdated files based on the retention settings, above. Twenty-four hour time, HH:MM format. The default setting is 01:00. Required.
Example: The Server Logs setting is 7 days, and the Clean Up Schedule is 01:00. At 01:00 each day, the cleanup job:
• Renames the previous day’s log files using a date stamp (for example, if the current date is 04/02/15, the previous day’s server log is renamed server.log.2015-04-02.
• Deletes any retained log files older than 7 days.
• Deletes any records in the PRODUCT_LOCATION_TEMP table.
Note: The cleanup job can’t rename or delete any log file that is currently in use. In this case, it writes an error to the server.log: Log File delete failed.
Data Folder Settings
Product Import Files
Indicates where to place the pipe-delimited files containing:
• the location, product, product location (including attributes), and product barcode information for the import process.
• the interim product location updates for the incremental import process.
This must be a shared folder that is accessible through secure FTP. Once set, this should not ordinarily be changed.
The default is /usr/share/Locate/data/ProductUploadData. Subfolders are:
• archive: Includes a copy of each processed file
• error: Includes a copy of each file in error (error records only)
Optional, but required to import locations, products, product locations (including attributes), or product UPC barcodes.
For more information: See Importing Items/Products, Inventory, Barcodes, and Locations into the Database and Incremental Inventory Import.
Export Files
The folder on the Order Broker Cloud Service server where:
• Fulfilled Quantity export: The Fulfilled Inventory Export program writes the pipe-delimited file listing recently fulfilled order lines
• Probable quantity export: The probable quantity export writes a pipe-delimited file of updated product locations, including the probable quantity. See Updating and Exporting Probable Quantityfor more information.
The default is /usr/share/Locate/data/ExportData.
Optional, but required to export fulfilled quantities or probable quantities. You need to create this folder before using either of the export options. If you use multiple servers, the folder needs to be on all servers.
Proximity Upload Files
The folder on the Order Broker Cloud Service server where Order Broker Cloud Service places files you upload through the Proximity Uploads screen. You use this screen to upload the .CSV (comma-separated value) files. Once set, this should not ordinarily be changed. The default is /usr/share/Locate/data/ProximityUploadData. Required.
Miscellaneous Settings
ESB WSDL Location
The location of the wsdl that defines the launchDSOrders message used by an integrated vendor, such as https://SERVERNAME:7004/launchDSOrders/services/launchDSOrders?wsdl.
Not currently implemented.
Note: This field is also available to a retailer user at the Tenant (retailer information) screen.
Geocode Address
The URL to use when generating geocode requests to determine the latitude and longitude for:
• a location, when the location is created or has its address updated, either through the New Location or Edit Location screens, or through the import process
• a customer’s address, in order to calculate proximity for an order or inventory request, such as the SubmitOrder or the LocateItems request message
If a URL is specified here, Order Broker Cloud Service uses Oracle Maps Cloud Service to determine latitude or longitude. Otherwise, if this field is blank, Order Broker Cloud Service uses the proximity database.
Invalid URL? If the URL specified here is invalid, the error is logged in the error.log file based on your specified logging level. Also, web service request messages that require lookup of the customer address return an error indicating Customer Address not found.
Proxy required: Use of a proxy server is required to use Oracle Maps Cloud Service. See Proxy Server Settings below for more information.
For more information: See Proximity Locator Searching for background.
Proxy Address
If your network requires a proxy server to get to external IP addresses, enter the address of the proxy server.
Proxy Port
If your network requires a proxy server to get to external IP addresses, enter the port of the proxy server.