(https://imcvsoffice.azurewebsites.net/Account/Index?wmsmerakilogin=TrBUi0iJobTxvyt7Ep1boJJIHXXPMksIGRaWRmLd7ZP68BaEhxr3Xj%2F%2Fsf8fTaLJkE97FMYDpElBeXbmoJM6cgOIqFnnLZ%2F4ebmt53rPbGnLwwGzTfBVInIwA2BwHGWl)

Meraki Preparation For Meraki Site

Source code for the Call API

1. Main -URL(https://imcvsoffice.azurewebsites.net/Dashboard) - Dashboard →from WMS system click button to access it

2. API - URL(https://imcvsapiupdaterack.azurewebsites.net/api/)- Function (MerakiLocationAPI) - Meraki will post data to us → to update the Zebra Scanner Location and then will update to the Meraki Dashboard Floor Map there.

3. API - URL(https://imcvsapiupdaterack.azurewebsites.net/api/) - Function (UpdateRackStatus) - WMS will call to this API → to update the rack occupancy status and then will update to the Meraki Dashboard Floor Map there.

4. Engine - Currently the engine is inside a VM → to call the meraki api in order to grab the data → run schedule → interval time → 5 minus

5. App Services - Host Dashboard

   • Service: Azure App Service
   • Purpose: Hosts the website .
   • Details: This App Service is configured to host the website at the Azure cloud Services

6. App Services - Host API

   • Service: Azure App Service
   • Purpose: Hosts the API that allows WMS to update client's rack status and update on Meraki Dashboard Floor map there.
   • Details: This API is critical for real-time updates from the WMS systems, ensuring that the dashboard displays the most current information of the rack status.

7. SQL Services - Host Data

   • Service: Virtual Machine for MySQL
   • Database Type: MySQL
   • Details: The MySQL database stores all necessary data for the dashboard and APIs, including WMS device information and Meraki device information.

8. Engine / Executables

• Service: Virtual Machine (VM) with Task Scheduler
• Purpose: Runs an executable program that grabs API data from Meraki, inserts the data into the database, and performs scheduled tasks.
• Details:
  • Executable: A custom executable script (e.g., a .exe file) designed to fetch data from the Meraki API and insert it into the MySQL database.
  • Task Scheduler: Windows Task Scheduler is configured to run the executable daily at a specific time.

1. Microsoft Entra ID (Azure AD) - Required for SSO Login
   • Service: Microsoft Entra ID
   • Purpose: Provides Single Sign-On (SSO) capabilities for user authentication .
   • Details: This configuration allows users to authenticate using their corporate credentials via Azure AD. The app registration includes necessary permissions, redirect URIs, and configurations for secure authentication and authorization to access the meraki website.
2. Azure Maps Account - Host for Dashboard Map Plot
   • Service: Azure Maps
   • Purpose: Provides mapping services for plotting devices and floor plans on the dashboard.
   • Details: The Azure Maps account is used to render maps within the dashboard, including device locations, floor plan overlays