In-Depth Notes on Inventory Jobs and Scanner Process

Overview of Inventory Jobs
  • Objective: Understanding the key components and steps involved in the inventory scanning process, specifically the six jobs related to the full scan execution.
Overview of the Six Jobs
  • Essential to performing successful inventory checks.
  • Detailed examination of each job aids in identifying and resolving potential issues during execution.
Job 1: Remove Local Scan Log File
  • Action: Delete the latest scan log on the local machine.
  • Importance: Ensures that the scan begins with a clean slate, avoiding discrepancies in log data.
Job 2: Scanner Connection
  • Action: Establish a connection with the scanner.
  • Result: Confirms the scanner's operational status before proceeding to the next job.
Job 3: Engine to Java Mode Check
  • Purpose: Verify if the scanner is running in ADID mode.
  • Parameters:
    • Parameter 1: User med DB
    • Parameter 2: AI option as a file on the target machine.
  • Outcome: Confirms readiness for scanning if in the correct mode.
Job 4: Log Scan the Node
  • Action: Check if the target machine is logged.
  • Importance: Reports an error log if the machine is logged; otherwise, logs the machine for scanning.
Job 5: Check UUID Consistency
  • Key Step: Validate the UUID of the target machine against the stored UUID.
  • Result: Confirms that the machine is properly registered and can be scanned.
Job 6: Acceptance Check
  • Condition: Dependence on the parameter set to 2 for execution.
  • Flowchart Reference: Additional details provided in the flowchart.
Additional Steps in Job Execution
  • Upgrade the Scanner: Uploads the scanner and modifies file permissions for security. Requires SSH account permission.
  • Launch Scanner: Converts user DB parameters into scanner commands; checks for successful scan completion.
  • Download Scan File: Downloading the scan log based on the log level settings (debug or chest).
  • Delete Results: Determines whether to delete previous scan results on the target machine.
XML in Virtual Processing
  • Purpose: SCAD file processing.
  • Procedure: Retrieve the processed scan file and verify that it’s prepared for analysis using XML in virtual.
Final Steps
  • Data Passing: Writing data into user med DB and generating CIC (Continuous Integration) outputs.
  • Lock Management: Understanding lock acquisition and release timing relevant to the scanning process.
Common Query: Lock Handling
  • Question: How and when does the lock release occur?
  • Response: Lock releases after the scaffold download is complete. Ability to terminate the process manually via the target machine is available.
Considerations for Optimization
  • Timeout Settings: Adjustment of timeout configurations in the SCANA configuration file could enhance efficiency.
  • Resource Allocation: Additional CPU resources may be required for optimal scanner performance on the target machine.
Conclusion
  • Documentation: More detailed instructions available in related documents.
  • Contact: Availability for further questions via Teams.