To build a %Library.DynamicObject or %Library.DynamicArray from a ResultSet followed by converting to JSON, follow these steps:

1. Loop through the ResultSet, constructing either a %Library.DynamicObject or %Library.DynamicArray as needed.
2. Use the %ToJSON() method to convert the constructed dynamic object or array into JSON format.

Below is an example code snippet illustrating this process:

ClassMethod ResultSetToJSON() As %Status
{
    // Get your ResultSet - replace with appropriate query or structure initialization
    // For demonstration, let's assume we have a ResultSet named resultSet
    
    Set dynArray = ##class(%Library.DynamicArray).%New()

    // Example loop to process resultSet rows
    While resultSet.%Next()
    {
        // Extract data from the ResultSet row
        Set dynObj = ##class(%Library.DynamicObject).%New()
        Do dynObj.%Set("Column1", resultSet.Column1)
        Do dynObj.%Set("Column2", resultSet.Column2)
        Do dynArray.%Push(dynObj)
    }

    // Convert to JSON string
    Write dynArray.%ToJSON()
    
    Quit $$$OK
}

In this example:

• Data is processed row by row from resultSet.
• A %Library.DynamicObject is created for each row, and properties are populated with column data.
• Each dynamic object is added to a %Library.DynamicArray.
• The %Library.DynamicArray is converted to JSON using its %ToJSON() method.

Remember, similar steps can be followed for a %Library.DynamicObject if your JSON structure requires objects instead of arrays 1.

Sources:

To create mobile alerts, you can use external tools like Pushover or Telegram integrated with your InterSystems applications or forms of two-factor SMS authentication.

1. For Pushover-based alerts:

   • Create an account on pushover.net, which has a one-time fee of $5 (after a prior free trial).
   • Set up your device and obtain the required User Key and API Token/Key.
   • Use the provided sample class for integrating alert operations. Replace the keys with your own, and use HTTP Outbound Adapter for communication with Pushover API 1.

2. For Telegram-based alerts (recommended for notification services):

   • Set up a Telegram bot using the BotFather on Telegram.
   • Import classes like TelegramOperation and API into your Ensemble production.
   • Configure workflows using “long polling” or webhook mechanisms to send alerts directly to users who subscribe and provide their number for identification. Ensure SSL is configured when using webhooks 2.

3. For SMS alerts:

   • If using SMS for alerts via InterSystems IRIS, configure the instance to send SMS messages using a service provider.
   • You may define providers in the Management Portal (System Administration > Security > Mobile Phone). Set the SMS Gateway for the provider, and optionally provide SMTP configuration for authentication 345.

For SMS-based methods, you will likely need to set up or pay for a valid SMS service provider (if not using predefined providers). Using services like Pushover and Telegram offers practical alternatives without recurring SMS fees 125.

Sources:

Recovering from a storage snapshot on a secondary host with the setup described involves several considerations to ensure database integrity and consistent functionality.

1. Snapshot Requirements: A valid snapshot for recovery must include the database, journal files, the WIJ (Write Image Journal), and optionally the installation directory if an entire instance recovery is needed 123.

2. Recovery Procedure:

   • Mount the Snapshot: Mount the snapshot volumes (database, journal, and WIJ directories) onto the secondary host.
   • Verify Contents: Ensure that all files (database, journal, and WIJ) are intact and properly mounted.
   • Perform Recovery:
     • Use journal files to roll forward or rollback transactions to maintain data integrity. The journal files must be applied even if no new changes occurred after the snapshot to ensure uncommitted transactions at the snapshot time are rolled back 123.
     • Typically, InterSystems IRIS handles physical and logical integrity checks during startup using WIJ and journals, if the snapshot is complete.

3. Journals and WIJ:

   • Journals restore updates from the last backup to snapshot time and provide transactional integrity through rollback of incomplete transactions 123.
   • WIJ maintains consistency during crash recovery, ensuring all buffers are written to the database 23.

4. Recommended Configuration:

   • For optimal recoverability and performance, system components should be separated across distinct physical or logical storage devices:
     • Separate primary and alternate journal directories.
     • Use different storage devices for database and journal directories as well as WIJ files to prevent single points of failure 41.
   • Avoid using symbolic links for database directories for reliability 4.

5. Testing and Best Practices:

   • Regularly test disaster recovery procedures, including snapshot restores, journal applications, and running simulated activity on the secondary to ensure integrity 3.
   • Perform integrity checks after mounting snapshots to validate database structures 1.

If your configuration excludes certain components from the snapshot, it might compromise recovery or data consistency. Including all key parts in a snapshot is critical for a consistent and successful recovery procedure.

Sources: