| Oracle® Retail Warehouse Management System Operations Guide Release 15.0 E65925-01 |
|
 Previous |
 Next |
| Oracle® Retail Warehouse Management System Operations Guide Release 15.0 E65925-01 |
|
Previous |
Next |
Each system user must have a unique login ID to the operating system, Oracle, and RWMS. This chapter describes how you can create each of these accounts and contains the following sections:
Radio Frequency users must login to a terminal server through remote desktop on Radio Frequency (RF) devices to launch the RF application. The terminal server is configured for each user. When a user logs into to a terminal server, a web browser is launched in Kiosk Mode and RF device selection menu is displayed. The RF launch menu is configured for each user during installation and has these options:
Hand Held
Truck Mount
Wrist Mount
Close
Users must select an option configured for the type of device they are logging into. When an option is selected, an application URL is launched that is specific to an entry on the formsweb.cfg file (configured during installation). This allows users to set specific environment variables for the type of device that is being used during implementation.
The close option calls a web page with an active x control that executes the c:/WINDOWS/system32/shutdown.ex executable file and completely shuts down the session on the terminal server and returns the users to the RF devices operating screen.
|
Note:
|
The web browser controls the Kiosk Mode. For example, in Internet Explorer, Kiosk Mode is started as:
iexplore -k <URL>
iexplore -k http://<server>:<port>/forms/frmservlet?config=<rwms_device_config>
For additional information, refer to these documents:
How to use Kiosk Mode in Microsoft Internet Explorer at:
https://support.microsoft.com/en-us/kb/154780
Oracle Retail Warehouse Management System Wireless Device Configuration -- Note 578400.1 at:
This section describes the print queues, cron jobs, daemon process, and system parameters.
Create print queues in the operating system for reports and labels. RWMS does not embed any printer-specific commands in jobs being sent to report printers. Non-Label printer queues are typically defined as standard ASCII devices. For label printers, raw xml data is sent through a filter that converts it to ZPL (Zebra Programming Language). All label printers must be able to interpret ZPL text.
The names of the printer queues are specified on the System Parameters Editor screen. For more information on the SCPs, see the Oracle Retail Warehouse Management System Implementation Guide. The names of the parameters are listed here:
pick_audit_queue
pick_label_queue
pick_package_queue
recv_audit_queue
recv_label_queue
recv_receipt_queue
reprint_label_queue
ship_bol_queue
ship_label_queue
unit_pick_lbl_queue
This table describes the programs that should be run periodically to remove obsolete data from the system, schedule locations for cycle counting, close appointments, upload data, download data, and so forth. The user should run these programs using the operating system facility (cron) for scheduling jobs for unattended operation.
In the table, the name of the program to run is listed under the column heading Name. The programs are in the $RDM_BIN directory. For each routine, a system parameter exists that specifies the number of days of data to retain. These parameters are maintained on the System Parameter editor, which is described in the Oracle Retail Warehouse Management System User Guide.
The OS user's cron should first execute the .profile to set the environmental variables.
Table 2-1 Programs that must be run through cron job
| Name | Purpose | Parameters | Frequency |
|---|---|---|---|
|
capacity_replen.sh |
Releases on-hold replenishments destined for Forward Pick locations. |
facility_id |
Every several minutes |
|
insert_distribution_queue.sh |
Works with the Automate wave processing. |
facility_id |
Every several minutes or time that meets customer needs. |
|
inv_bal_upload_b.sh |
Create an inventory balance upload file for each facility id, part of the facility type. |
facility_id |
Once daily |
|
maintain_wave_stats.sh |
Updates wave statistics. |
Every 15 minutes |
|
|
run_distribution.sh |
Matches inventory to allocation requests, creates pick directives and prints picking packages (if applicable). |
Manually or every 15 minutes |
|
|
schedule_cycle_count_b.sh |
Schedules cycle counts (SS) for the DC. |
Cycle_count_period |
Once daily |
|
schedule_rop_distribution.sh |
Schedules a Re-Order Point distribution run. |
Every 5 minutes |
|
|
unreconciled_appt_monitor.sh |
Closes any unreconciled appointments that had all labels scanned or nulled. |
None |
Hourly |
|
purge_rwms_tables.sh |
Executes a number table purges. |
facility_id |
Once daily |
The following table discusses permissions and any file cleanup (purging needed for each directory).
Table 2-2 File Management
| Directory | Path | Purpose | Perm | Purging |
|---|---|---|---|---|
|
Base Directory |
$RDM |
This is the base directory that other directories branch from. |
775 |
None |
|
Reports |
$RDM/reports It is present on the application server where the Forms Server directory is located. (/u00/webadmin/product/10.3.3/WLS/user_projects/domains/ClassicDomain/servers/WLS_FORMS/tmp/_WL_user/formsapp_11.1.1/e18uoi/war/rwms/ reptemp/) |
Temporary holding area for reports. Only non label reports that are executed using the RWMS GUI application are sent here. All the other reports are routed and managed by BI Publisher processing and configurations. |
777 |
Occasional (weekly) |
|
Host Download |
$DOWNLOAD_DIR |
Temporary holding area for files to download and log files |
775 |
Occasional (weekly) |
|
Host Upload |
$UPLOAD_DIR |
Temporary holding area for files to upload. |
775 |
Occasional (weekly) |
|
Sortation |
$SORTATION_DIR |
Temporary holding area for files sent to a 3rd party sorter. |
775 |
Occasional (weekly) |
|
BIN |
$RDM/bin |
Holds all executables. |
755 |
None |
|
INSTALL |
$RDM_ADMIN/create |
Holds files used to build the system. |
755 |
None |
