How to manage SSH-based RF will be phased out beginning in January 2027

Starting January 2027, Oracle has announced SSH-based RF (Radio Frequency) access in Oracle Cloud WMS will be phased out and replaced entirely by HTTPS-based RF using handheld devices via web browsers or REST APIs. This shift is part of Oracle’s broader move to enhance security, performance, and mobile device compatibility.

Below is a detailed step-by-step implementation guide to help transition from SSH-based RF to HTTPS-based RF in Oracle Cloud WMS.

Objective:

Migrate all existing SSH-based RF functions, scripts, and user processes to HTTPS browser-based or REST API-based RF forms before January 2027.

Step-by-Step Implementation Guide:

Step 1: Assessment & Planning

1. Inventory RF Devices

·       List all devices currently using SSH-based RF (e.g., Telnet clients).

·       Capture device types, models, and OS versions.

 

2. Assess Existing RF Menus & Scripts

·       Document all current SSH-based RF flows (Receiving, Picking, Putaway, etc.).

·       Identify custom scripts, if any.

 

3. Evaluate Network & Wi-Fi

·       Ensure warehouse Wi-Fi is stable and covers all working areas.

·       Test HTTPS access from handheld devices.

 

4. Build a Project Plan

·       Include milestones, testing cycles, device procurement, training, and cutover date.

 

Step 2: Device Readiness & Software Compatibility

1. Device Requirement

·       HTTPS-based RF requires Android or iOS-based RF guns or mobile devices with modern browsers.

·       Ensure screen resolution is compatible (minimum 5" touch screen, 720p or better).

2. Install & Configure Browsers

·       Install Google Chrome or Edge on RF devices.

·       Bookmark Oracle WMS Cloud HTTPS URL.

 

3. Security Certificates

·       Ensure HTTPS access is secured with valid SSL certificates.

·       Test SSL handshake from all RF devices.

 

Step 3: RF Menu Rebuild in WMS Cloud

1. Navigate to RF Screens Configuration

·       WMS UI → Task Management → RF Screen Configuration

 

2. Recreate RF Menus

·       Convert all SSH-based screens to HTML5 browser-compatible RF Screens using WMS screen configuration.

·       Leverage HTML templates and standard WMS Web RF flows.

·       Customize using JavaScript-based logic where needed (Oracle allows controlled customization).

 

3. Role-Based Access Setup

·       Use role-based RF menus (different flows for inbound, outbound, inventory, etc.).

·       Configure RF menu permissions for different warehouse roles.

 

Step 4: Integration Rework (if applicable)

1. API Conversion

·       If old RF scripts triggered back-end services (e.g., telnet scripts), rewrite them using REST APIs.

·   

2. Middleware Updates

·       Update any middleware or MFT software triggering SSH commands.

·       Replace with HTTPS API calls or browser automation if needed.

 

Step 5: User Acceptance Testing (UAT)

1. Test Core Flows

·       Receiving, Picking, Cycle Count, Putaway, Replenishment, etc.

 

2. Simulate Real Warehouse Scenarios

·       Conduct mock shipments, inbound, and inventory transactions.

 

3. Feedback & Issue Resolution

·       Gather feedback from warehouse users.

·       Modify layouts for touchscreen usability (button sizes, screen flow, etc.).

 

Step 6: Training & Change Management

1. Train Warehouse Users

·       Provide hands-on training for touchscreen browser-based RF usage.

·       Share quick reference guides or videos.

 

2. Deploy Posters or QR Codes

·       Place QR codes in warehouse that open RF menu URLs when scanned.

 

Step 7: Go-Live & Post-Cutover Support

1. Parallel Run (Optional)

·       Run SSH-based and HTTPS-based RF systems in parallel (till Oracle disables SSH in 2027).

 

2. Cutover

·       Fully switch to HTTPS RF.

·       Decommission telnet services and remove SSH clients.

 

3. Post-Go-Live Monitoring

·       Monitor user performance, latency, and error logs.

·       Maintain support desk for 2-4 weeks post-cutover.

Thank You,

Pratip Chatterjee