Migrate Application [Airsonic-Advanced] to Azure

[seanli1988]

Your organization has discovered the application [Airsonic-Advanced] as a target for cloud modernization. See below for detected dependencies and next steps.

Azure Migration GitHub Issue: Airsonic Application Replatform/Refactor

Application Overview

• Application: Airsonic
• Owner: James Draper
• Type: COTS/ISV
• Business Critical: Yes
• Migration Strategy: Replatform/Refactor

Current Technologies and Target Azure Services

Java 8

• Current: Running on 5 servers (VM_158, VM_159, VM_154, VM_155, VM_1258)
• Target: Azure App Service

IIS

• Current: Running on 5 servers (VM_159, VM_154, VM_155, VM_160, VM_167)
• Target: Azure App Service

Local File Storage

• Current: Running on 5 servers (VM_159, VM_155, VM_160, VM_167)
• Target: Azure Files

PostgreSQL

• Current: Running on 2 servers (VM_154, VM_155)
• Target: Azure Database for PostgreSQL

SQL Server 2012

• Current: Running on 1 server (VM_1258)
• Target: Azure SQL

SQL Server Analysis Services

• Current: Running on 1 server (VM_1258)
• Target: Azure Analysis Services

SQL Server Integration Services

• Current: Running on 1 server (VM_1258)
• Target: Azure Data Factory

Access

• Current: Running on 1 server (VM_154)
• Target: Azure SQL

Server Details

Production Servers

• VM_159: Windows Server 2012, 6 cores, 40GB RAM, 170GB storage, 70% CPU usage
• VM_154: Windows Server 2012, 4 cores, 32GB RAM, 130GB storage
• VM_1258: Windows Server 2012, 2 cores, 8GB RAM, 141GB storage, 42% CPU usage

Development Servers

• VM_158: Windows Server 2012, 4 cores, 32GB RAM, 190GB storage, 23% CPU usage
• VM_155: Windows Server 2012, 4 cores, 32GB RAM, 130GB storage
• VM_160: Windows Server 2012, 8 cores, 48GB RAM, 130GB storage, 44% CPU usage
• VM_167: Windows Server 2012, 4 cores, 32GB RAM, 130GB storage

Migration Notes

• All servers are marked as "Ready" for Azure VM migration
• All servers are using Standard HDD disks (2 per server)
• Production server VM_159 has the highest resource utilization
• VM_1258 handles all SQL Server-related services and will require migration to multiple Azure services

[seanli1988]

Azure Migrate Application and Code Assessment for Java has discovered the following issues:

Upgrade to JDK 21
Migrate from local file system to Blob Storage
Migrate from logging in local file system to console
Migrate local credentials to Azure Key Valult
Migrate embedded cache to Azure Redis Cache

[seanli1988]

The following items have been changed by GitHub Copilot App Modernization to upgrade from JDK 11 to JDK 21.

[ x ] JDK dependencies changed from JDK 11 to JDK 21

[ x ] Build verified.

[ x ] Unit tests passed.

[seanli1988]

Migration Summary

Migration Scenario

Migrate the Airsonic Advanced project to handle local file mounting appropriately

Formula Used

mount-local-file

Changes Made

WebsocketConfiguration.java

The provided Java file does not contain any hard-coded local file paths for reading or writing files. Therefore, no changes were required to migrate to Azure Storage mounts.

Util.java

Added a private static final field AZURE_MOUNT_PATH to define the Azure mounted storage path.

• Updated the getDefaultMusicFolder, getDefaultPodcastFolder, and getDefaultPlaylistFolder methods to reference the AZURE_MOUNT_PATH field instead of hard-coded local paths.
• Ensured the functionality remains the same while migrating to Azure Storage mounts.

SettingsService.java

Added a private static final field AZURE_MOUNT_PATH to define the Azure mount path.

• Replaced hard-coded local file paths with references to the AZURE_MOUNT_PATH field.

SecurityServiceTestCase.java

The file is a test file (SecurityServiceTestCase.java) and does not involve reading or writing to hard-coded local file paths. As per the guideline, test files should not be modified.

• No changes were made because the code does not meet the conditions for migration to Azure Storage mounts.

PlayerTest.java

Added a private static final field AZURE_MOUNT_PATH to define the Azure mounted storage path.

• Replaced the hard-coded local file path in the FileInputStream constructor with a reference to the AZURE_MOUNT_PATH field.
• Ensured the new path maintains the same relative structure as the original path.

lgtm.yml

The provided file does not contain any local file paths that need to be migrated to Azure mounted storage paths as per the guideline.

• No changes were made because the file primarily contains configuration for JavaScript and Java extraction, and no file paths match the migration criteria.

schema35.xml

No changes were required in this file for the migration.

Build Status

Build completed successfully.

Next Steps

1. Review the changes to ensure they meet your requirements
2. Test the application with Azure mounted storage to verify functionality
3. Update any documentation to reflect the new file path approach
4. Consider implementing additional Azure storage features as needed

Thanks for using App Modernization for Java on Azure

[seanli1988]

Migration Summary

Migration Scenario

Modernize logging to improve console logging

Formula Used

log-to-console

Changes Made

WebsocketConfiguration.java

Added a Logger instance using java.util.logging.Logger to log messages to the console.

• Ensured that the logger does not output to a file by using the default console handler.
• Added a log statement in the configureMessageBroker method to log the configuration of the message broker.
• Added a log statement in the registerStompEndpoints method to log the registration of STOMP endpoints.

application.properties (main)

Removed the logging.pattern.file property to ensure logs are not output to a file.

• No changes were made to other properties to maintain the integrity of the configuration.

logback-spring.xml

Removed the reference to the FILE appender in the <root> logger to ensure logs are not output to a file.

• Added a reference to the CONSOLE appender in the <root> logger to ensure logs are output to the console.
• Kept the inclusion of file-appender.xml unchanged as per the guideline to minimize modifications.

application.properties (test)

Removed the logging.pattern.file property to ensure logs are not output to a file.

• Kept the logging.pattern.console property to ensure logs are output to the console.

Build Status

Build completed successfully.

Next Steps

1. Review the changes to ensure they meet your requirements
2. Test the application to verify that logs are successfully output to the console
3. Consider implementing additional log configuration as needed for specific environments
4. Update any documentation to reflect the new logging approach

Thanks for using App Modernization for Java on Azure