Purpose: Use the Tenant - Cloud screen to define enterprise-level settings for Order Broker, including those related to:
• the Order Broker module(s) used
• the number of minutes that Order Broker should wait before generating emails
• the retailer’s logo
• the location of the WSDL used for the vendor integration
• the timeout interval for Order Broker user sessions
• the number of unsuccessful login attempts before Order Broker disables a user ID
• email settings, including the location of templates and generation interval
• cleanup of logs, generated documents such as reports and pack slips, and product import files
• paths for folders used for uploads, import, and export
• proxy server for communication with ADSI, or with an integrated system for interactive inventory update requests
About tenant settings: Tenant settings are enterprise-level attributes in Order Broker at a level higher than the organization. Tenant-level settings apply to all the retailer’s organizations in Order Broker.
How to display this screen: Select Tenant from the Systems Menu.
Note: Only an admin user can display this screen. Retailer users with Tenant authority advance instead to the Tenant (retailer information) screen.
Update any of the enterable fields described below and click Save, or click Cancel to exit the screen without making any changes.
Only the default admin user has access to fields related to administering Order Broker on the cloud server.
Field |
Description |
---|---|
Settings |
|
The number of minutes that Order Broker 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, and needs to close the browser before logging back in to Order Broker. 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 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. |
|
The number of unsuccessful, sequential login attempts that triggers Order Broker to disable a user account. When a user attempts to log in with a disabled account, Order Broker 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 LDAP user? If the user is flagged for LDAP authentication, the lockout counter does not apply, and the user’s Order Broker 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. 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 ( 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 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. |
Email Settings |
|
Email Template Path |
The folder on the Order Broker server where email templates are stored. The template path should not ordinarily be changed. The default is /usr/share/apache-tomcat/conf/emailtemplates. Required. |
Email Interval |
The number of minutes that Order Broker 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 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 team. |
|
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 Order Broker 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 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. 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 |
|
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 /home/dev/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 Order Broker Database and Incremental Inventory Import. |
|
Export Files |
The folder on the Order Broker 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 /home/dev/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 server where Order Broker 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 /home/dev/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:8443/launchDSOrders/services/launchDSOrders?wsdl. This setting might be required for an integrated vendor if the retailer does not use a vendor integration created and configured by Oracle, because the launchDSOrders message is defined in a separate wsdl (web service description language), while the remaining integrated vendor messages use JSON, and are defined in a wadl (web application description language) on the Order Broker server. Optional, but required to support integrated vendors. Used only by the Supplier Direct Fulfillment module. Note: This field is also available to a retailer user at the Tenant (retailer information) screen. |
Geocode Address |
Geocode integration is not currently implemented. |
Proxy Address |
The address of the proxy server to use for communication with ADSI for interactive shipping in the Vendor Portal and Store Connect, or with an integrated system for inventory update requests. ADSI The system sends the request to the proxy server, which communicates with ADSI through the Shipper URL specified at the Drop Ship Preferences screen or the Store Connect Preferences screen, and returns the response to Order Broker. When Order Broker runs in the cloud, both the proxy address and the proxy port are required for integration with ADSI for either the Vendor Portal or Store Connect. if you enter information in one field, you must also complete the other field. ADSI error? If a vendor or store associate attempts to ship through integration with ADSI and both the proxy address and port are not correct, the Vendor Portal or Store Connect screen opens a pop-up window indicating an unhandled ADSI error. Also, an error message is written to the server log. Inventory update request to integrated system If the Connection Type for a system is set to URL, and the Use Proxy Server flag is selected, interactive inventory requests for an online system are relayed through the proxy server. See the Interface Information area of the System screen for more information. |
Proxy Port |
The port on the proxy server to use for communication with ADSI or for sending interactive inventory requests. See the discussion above for the proxy address. |
________________________________
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
Legal
Notices