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
Copy file name to clipboardExpand all lines: articles/aks/howto-deploy-java-liberty-app.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ The Open Liberty Operator simplifies the deployment and management of applicatio
23
23
24
24
For more information on Open Liberty, see [the Open Liberty project page](https://openliberty.io/). For more information on IBM WebSphere Liberty, see [the WebSphere Liberty product page](https://www.ibm.com/cloud/websphere-liberty).
25
25
26
-
This article uses the Azure Marketplace offer for Open/WebSphere Liberty to accelerate your journey to AKS. The offer automatically provisions a number of Azure resources including an Azure Container Registry (ACR) instance, an AKS cluster, an Azure App Gateway Ingress Controller (AGIC) instance, the Liberty Operator and optionally a container image including Liberty and your application. To see the offer visit the [portal](https://aka.ms/liberty-aks). If you prefer manual step-by-step guidance for running Liberty on AKS that doesn't utilize the automations enabled by the offer, see [Manually deploy a Java application with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/howto-deploy-java-liberty-app-manual).
26
+
This article uses the Azure Marketplace offer for Open/WebSphere Liberty to accelerate your journey to AKS. The offer automatically provisions a number of Azure resources including an Azure Container Registry (ACR) instance, an AKS cluster, an Azure App Gateway Ingress Controller (AGIC) instance, the Liberty Operator, and optionally a container image including Liberty and your application. To see the offer, visit the [Azure portal](https://aka.ms/liberty-aks). If you prefer manual step-by-step guidance for running Liberty on AKS that doesn't utilize the automation enabled by the offer, see [Manually deploy a Java application with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/howto-deploy-java-liberty-app-manual).
@@ -35,13 +35,13 @@ This article uses the Azure Marketplace offer for Open/WebSphere Liberty to acce
35
35
* Install a Java SE implementation (for example, [Eclipse Open J9](https://www.eclipse.org/openj9/)).
36
36
* Install [Maven](https://maven.apache.org/download.cgi) 3.5.0 or higher.
37
37
* Install [Docker](https://docs.docker.com/get-docker/) for your OS.
38
-
* Make sure you have been assigned either `Owner` role or `Contributor` and `User Access Administrator` roles in the subscription. You can verify it by following steps in [List role assignments for a user or group](../role-based-access-control/role-assignments-list-portal.md#list-role-assignments-for-a-user-or-group)
38
+
* Make sure you have been assigned either the `Owner` role or the `Contributor` and `User Access Administrator` roles in the subscription. You can verify it by following steps in [List role assignments for a user or group](../role-based-access-control/role-assignments-list-portal.md#list-role-assignments-for-a-user-or-group).
39
39
40
40
## Create a Liberty on AKS deployment using the portal
41
41
42
-
The steps in this section guide you to create a Liberty runtime on AKS. After completing these steps, you'll have an Azure Container Registry and an Azure Kubernetes Service cluster for the sample application.
42
+
The following steps guide you to create a Liberty runtime on AKS. After completing these steps, you'll have an Azure Container Registry and an Azure Kubernetes Service cluster for the sample application.
43
43
44
-
1. Visit the [Azure portal](https://portal.azure.com/). In the search box at the top of the page, type *IBM WebSphere Liberty and Open Liberty on Azure Kubernetes Service*. When the suggestions start appearing, select the one and only match that appears in the **Marketplace** section. If you prefer, you can go directly to the offer with this shortcut link,[https://aka.ms/liberty-aks](https://aka.ms/liberty-aks).
44
+
1. Visit the [Azure portal](https://portal.azure.com/). In the search box at the top of the page, type *IBM WebSphere Liberty and Open Liberty on Azure Kubernetes Service*. When the suggestions start appearing, select the one and only match that appears in the **Marketplace** section. If you prefer, you can go directly to the offer with this shortcut link:[https://aka.ms/liberty-aks](https://aka.ms/liberty-aks).
45
45
1. Select **Create**.
46
46
1. In the **Basics** pane, create a new resource group. Because resource groups must be unique within a subscription, pick a unique name. An easy way to have unique names is to use a combination of your initials, today's date, and some identifier. For example, `ejb0913-java-liberty-project-rg`.
47
47
1. Select *East US* as **Region**.
@@ -77,12 +77,12 @@ If you navigated away from the **Deployment is in progress** page, the following
77
77
78
78
## Create an Azure SQL Database
79
79
80
-
The steps in this section guide you through creating an Azure SQL Database single database for use with your app.
80
+
The following steps guide you through creating an Azure SQL Database single database for use with your app.
81
81
82
82
1. Create a single database in Azure SQL Database by following the steps in [Quickstart: Create an Azure SQL Database single database](/azure/azure-sql/database/single-database-create-quickstart), carefully noting the differences in the box below. Return to this article after creating and configuring the database server.
83
83
84
84
> [!NOTE]
85
-
> At the **Basics** step, write down **Resource group**, **Database name**, ***Server name**.database.windows.net*, **Server admin login** and **Password**. The database **Resource group** will be referred to as `<db-resource-group>` later in this article.
85
+
> At the **Basics** step, write down **Resource group**, **Database name**, **_<server-name>_.database.windows.net**, **Server admin login**, and **Password**. The database **Resource group** will be referred to as `<db-resource-group>` later in this article.
86
86
>
87
87
> At the **Networking** step, set **Connectivity method** to **Public endpoint**, **Allow Azure services and resources to access this server** to **Yes**, and **Add current client IP address** to **Yes**.
88
88
>
@@ -101,6 +101,7 @@ Follow the steps in this section to deploy the sample application on the Liberty
101
101
### Check out the application
102
102
103
103
Clone the sample code for this guide. The sample is on [GitHub](https://github.com/Azure-Samples/open-liberty-on-aks).
104
+
104
105
There are a few samples in the repository. We'll use *java-app/*. Here's the file structure of the application.
105
106
106
107
```
@@ -128,7 +129,7 @@ In the *aks* directory, we placed two deployment files. *db-secret.xml* is used
128
129
129
130
In the *docker* directory, we placed four Dockerfiles. *Dockerfile-local* is used for local debugging, and *Dockerfile* is used to build the image for an AKS deployment. These two files work with Open Liberty. *Dockerfile-wlp-local* and *Dockerfile-wlp* are also used for local debugging and to build the image for an AKS deployment respectively, but instead work with WebSphere Liberty.
130
131
131
-
In directory *liberty/config*, the *server.xml* is used to configure the DB connection for the Open Liberty and WebSphere Liberty cluster.
132
+
In directory *liberty/config*, the *server.xml*FILE is used to configure the DB connection for the Open Liberty and WebSphere Liberty cluster.
132
133
133
134
### Acquire necessary variables from AKS deployment
134
135
@@ -140,7 +141,7 @@ After the offer is successfully deployed, an AKS cluster will be generated autom
140
141
echo<appDeploymentTemplateYamlEncoded>| base64 -d
141
142
```
142
143
143
-
1. Save the `metadata.namespace` from this yaml output aside for later use in this article.
144
+
1. Save aside the `metadata.namespace` from this yaml output for later use in this article.
144
145
145
146
### Build the project
146
147
@@ -178,10 +179,10 @@ In the sample application, we've prepared *Dockerfile-local* and *Dockerfile-wlp
0 commit comments