You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Predefined Formulas for GitHub Copilot App Modernization for Java
2
+
title: Predefined Tasks for GitHub Copilot App Modernization for Java
3
3
titleSuffix: Azure
4
-
description: Provides an overview of predefined formulas.
4
+
description: Provides an overview of predefined tasks.
5
5
author: KarlErickson
6
6
ms.author: karler
7
7
ms.reviewer: xiading
@@ -11,11 +11,11 @@ ms.custom: devx-track-java
11
11
ms.service: azure-java
12
12
---
13
13
14
-
# Predefined formulas for GitHub Copilot App Modernization for Java
14
+
# Predefined tasks for GitHub Copilot App Modernization for Java
15
15
16
-
This article describes the predefined formulas available for GitHub Copilot App Modernization for Java.
16
+
This article describes the predefined tasks available for GitHub Copilot App Modernization for Java.
17
17
18
-
Predefined formulas capture industry best practices for using Azure services. Currently, App Modernization for Java offers predefined formulas that cover common migration scenarios. These formulas address the following subjects, and more:
18
+
Predefined tasks capture industry best practices for using Azure services. Currently, App Modernization for Java offers predefined tasks that cover common migration scenarios. These tasks address the following subjects, and more:
19
19
20
20
- Secret management
21
21
- Message queue integration
@@ -25,68 +25,68 @@ Predefined formulas capture industry best practices for using Azure services. Cu
25
25
> [!NOTE]
26
26
> This list will grow based on customer feedback and evolving cloud needs.
27
27
28
-
The following video demonstrates using GitHub Copilot App Modernization for Java to apply a predefined formula to migrate a Java project to Azure:
28
+
The following video demonstrates using GitHub Copilot App Modernization for Java to apply a predefined task to migrate a Java project to Azure:
App Modernization for Java currently supports the following predefined formulas:
36
+
App Modernization for Java currently supports the following predefined tasks:
37
37
38
38
- Spring RabbitMQ to Azure Service Bus
39
39
40
-
This formula converts an application that uses Spring messaging frameworks - including Spring Advanced Message Queuing Protocol (AMQP) and Spring Java Message Service (JMS) - with RabbitMQ, changing it to use the managed service Azure Service Bus instead. The message queue interaction logic is adapted to the Azure Service Bus equivalent, preserving the messaging patterns and semantics while enabling secure authentication mechanisms by default.
40
+
This task converts an application that uses Spring messaging frameworks - including Spring Advanced Message Queuing Protocol (AMQP) and Spring Java Message Service (JMS) - with RabbitMQ, changing it to use the managed service Azure Service Bus instead. The message queue interaction logic is adapted to the Azure Service Bus equivalent, preserving the messaging patterns and semantics while enabling secure authentication mechanisms by default.
41
41
42
42
- Managed Identities for Database migration to Azure
43
43
44
-
The Azure database offerings - Azure SQL Server, Azure Database for MySQL, Azure Database for PostgreSQL, Azure Cosmos DB for Cassandra API, and Azure Cosmos DB for MongoDB - support secure sign-in using Managed Identity. When you migrate an application from a local database to a managed Azure cloud database, this formula helps you prepare your codebase for Managed Identity authentication to the database.
44
+
The Azure database offerings - Azure SQL Server, Azure Database for MySQL, Azure Database for PostgreSQL, Azure Cosmos DB for Cassandra API, and Azure Cosmos DB for MongoDB - support secure sign-in using Managed Identity. When you migrate an application from a local database to a managed Azure cloud database, this task helps you prepare your codebase for Managed Identity authentication to the database.
45
45
46
46
- Managed Identities for Credential Migration on Azure
47
47
48
-
Authentication using connection strings introduces security vulnerabilities and maintenance overhead. This formula transforms your Java applications to use Azure's Managed Identity authentication for messaging services like Azure Event Hubs and Azure Service Bus. By integrating with Microsoft Identity client libraries, your code no longer needs to store sensitive connection strings or shared access signatures in configuration files.
48
+
Authentication using connection strings introduces security vulnerabilities and maintenance overhead. This task transforms your Java applications to use Azure's Managed Identity authentication for messaging services like Azure Event Hubs and Azure Service Bus. By integrating with Microsoft Identity client libraries, your code no longer needs to store sensitive connection strings or shared access signatures in configuration files.
49
49
50
50
- Amazon Web Services (AWS) S3 to Azure Storage Blob
51
51
52
-
When you migrate your service from AWS to Azure, you can transition from AWS S3 to Azure Storage Blob. This formula helps you convert the code logic that interacts with AWS S3 into code logic that operates with Azure Storage Blob, while maintaining the same semantics.
52
+
When you migrate your service from AWS to Azure, you can transition from AWS S3 to Azure Storage Blob. This task helps you convert the code logic that interacts with AWS S3 into code logic that operates with Azure Storage Blob, while maintaining the same semantics.
53
53
54
54
- Logging to local file
55
55
56
-
Azure hosting services integrate with Azure Monitor by default, collecting log output to the console and enabling you to query and monitor them. At the same time, logging to files in a cloud environment isn't recommended because it requires extra log rotation and transfer. This formula helps you convert file-based logging in your application to console-based logging, making it ready for integration with Azure Monitor.
56
+
Azure hosting services integrate with Azure Monitor by default, collecting log output to the console and enabling you to query and monitor them. At the same time, logging to files in a cloud environment isn't recommended because it requires extra log rotation and transfer. This task helps you convert file-based logging in your application to console-based logging, making it ready for integration with Azure Monitor.
57
57
58
58
- Local file I/O to Azure Storage File share mounts
59
59
60
-
Azure hosting services offer flexibility in provisioning, scaling, failover, and more. At the same time, the file system for a given application runtime is transient. If your application reads from or writes to a local file, this formula helps you identify such cases and convert them into unified mount path access. By doing so, you can mount an Azure Storage File share to the specified path, enabling your application to share and persist data across different replicas without concerns about relocation, failover, or similar issues.
60
+
Azure hosting services offer flexibility in provisioning, scaling, failover, and more. At the same time, the file system for a given application runtime is transient. If your application reads from or writes to a local file, this task helps you identify such cases and convert them into unified mount path access. By doing so, you can mount an Azure Storage File share to the specified path, enabling your application to share and persist data across different replicas without concerns about relocation, failover, or similar issues.
61
61
62
62
- Java Mail to Azure Communication Service
63
63
64
-
Migrating applications with Simple Mail Transfer Protocol (SMTP) dependencies can be challenging because not all Azure environments support outgoing requests on port 25. This formula helps convert an application that sends mail over SMTP to use Azure Communication Services, which is fully compatible with Azure hosting environments.
64
+
Migrating applications with Simple Mail Transfer Protocol (SMTP) dependencies can be challenging because not all Azure environments support outgoing requests on port 25. This task helps convert an application that sends mail over SMTP to use Azure Communication Services, which is fully compatible with Azure hosting environments.
65
65
66
66
- Secrets and Certificate Management to Azure Key Vault
67
67
68
-
This formula helps migrate sensitive security assets to Azure Key Vault. It supports both hardcoded secrets in your codebase and local TLS/mTLS certificates managed in Java KeyStores. For secrets, it identifies suspicious secret texts and converts them into logic that retrieves the data from Azure Key Vault. For certificates, it transitions your application from managing certificates locally to using Azure Key Vault's Java Cryptography Architecture (JCA) provider while maintaining the same functionality and security posture.
68
+
This task helps migrate sensitive security assets to Azure Key Vault. It supports both hardcoded secrets in your codebase and local TLS/mTLS certificates managed in Java KeyStores. For secrets, it identifies suspicious secret texts and converts them into logic that retrieves the data from Azure Key Vault. For certificates, it transitions your application from managing certificates locally to using Azure Key Vault's Java Cryptography Architecture (JCA) provider while maintaining the same functionality and security posture.
69
69
70
70
- User authentication to Microsoft Entra ID authentication
71
71
72
-
Java applications often use LDAP-based authentication solutions that aren't easily migrated to Azure. This formula helps you transition your local user authentication mechanism to one that uses Microsoft Entra ID for authentication.
72
+
Java applications often use LDAP-based authentication solutions that aren't easily migrated to Azure. This task helps you transition your local user authentication mechanism to one that uses Microsoft Entra ID for authentication.
73
73
74
74
- SQL Dialect: Oracle to PostgreSQL
75
75
76
-
When transitioning from Oracle to PostgreSQL, differences in SQL dialects can pose significant challenges. This formula converts Oracle-specific SQL queries, data types, and proprietary functions in your Java code to their PostgreSQL equivalents, ensuring a seamless integration with Azure Database for PostgreSQL.
76
+
When transitioning from Oracle to PostgreSQL, differences in SQL dialects can pose significant challenges. This task converts Oracle-specific SQL queries, data types, and proprietary functions in your Java code to their PostgreSQL equivalents, ensuring a seamless integration with Azure Database for PostgreSQL.
77
77
78
78
- AWS Secret Manager to Azure Key Vault
79
79
80
-
Moving from AWS Secret Manager to Azure Key Vault requires reconfiguring how your application handles sensitive information. This formula transforms all aspects of secret management in your code - from creation and retrieval to updating and deletion - and leverages Azure Key Vault's comprehensive security capabilities and authentication models.
80
+
Moving from AWS Secret Manager to Azure Key Vault requires reconfiguring how your application handles sensitive information. This task transforms all aspects of secret management in your code - from creation and retrieval to updating and deletion - and leverages Azure Key Vault's comprehensive security capabilities and authentication models.
81
81
82
82
- ActiveMQ to Azure Service Bus
83
83
84
-
Applications built on Apache ActiveMQ can be modernized to leverage Azure's managed messaging service. This formula converts your ActiveMQ message producers, consumers, connection factories, and queue/topic interactions to their Azure Service Bus equivalents, implementing best practices for reliability and authentication in cloud environments.
84
+
Applications built on Apache ActiveMQ can be modernized to leverage Azure's managed messaging service. This task converts your ActiveMQ message producers, consumers, connection factories, and queue/topic interactions to their Azure Service Bus equivalents, implementing best practices for reliability and authentication in cloud environments.
85
85
86
86
- Amazon Web Services (AWS) Simple Queue Service (SQS) to Azure Service Bus
87
87
88
-
Transitioning from AWS SQS to Azure Service Bus involves reimplementing queue operations and message handling patterns. This formula translates SQS-specific code constructs to their Azure Service Bus counterparts, preserving critical messaging semantics like at-least-once delivery, message batching, and visibility timeout behaviors while introducing Azure's enhanced security features.
88
+
Transitioning from AWS SQS to Azure Service Bus involves reimplementing queue operations and message handling patterns. This task translates SQS-specific code constructs to their Azure Service Bus counterparts, preserving critical messaging semantics like at-least-once delivery, message batching, and visibility timeout behaviors while introducing Azure's enhanced security features.
89
89
90
90
## See also
91
91
92
-
[Quickstart: create and apply your own formulas](migrate-github-copilot-app-modernization-for-java-quickstart-create-and-apply-your-own-formula.md)
92
+
[Quickstart: create and apply your own tasks](migrate-github-copilot-app-modernization-for-java-quickstart-create-and-apply-your-own-task.md)
Copy file name to clipboardExpand all lines: articles/java/migration/migrate-github-copilot-app-modernization-for-java-quickstart-assess-migrate.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ For more information, see [Install a VS Code extension](https://code.visualstudi
51
51
52
52
Use the following steps to start your migration process with solution assessment. This assessment helps you understand what your cloud readiness challenges are and how impactful they are, provides recommended solutions. A solution recommendation includes references to set up Azure resources, add configurations, and make code changes.
53
53
54
-
1. Clone the [Java migration copilot samples](https://github.com/Azure-Samples/java-migration-copilot-samples) repository.
54
+
1. Clone the [Java migration copilot samples](https://github.com/Azure-Samples/java-migration-copilot-samples) repository and then check out to the **source** branch.
55
55
56
56
1. In Visual Studio Code, open the **mi-sql-public-demo** project folder in the samples repository.
0 commit comments