| Parameter Name | +Explanation | +|
_artifactsLocation |
+ See below for details. | +|
elkSettings |
+ Optional. JSON object type. You can specify this parameters for Elasticsearch and Kibana(ELK) connection. If enable is true, must specify other properties. See the page WebLogic with Elastic on Azure for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the elkSettings. |
+ |
elasticsearchEndpoint |
+ Endpoint of the Elasticsearch instance. | +|
elasticsearchPassword |
+ Password for Elasticsearch account. | +|
elasticsearchUserName |
+ User name for Elasticsearch account. | +|
logIndex |
+ Must be the same value output at ELK deployment time. | +|
logsToIntegrate |
+ Array with string value. Specify the expeted logs to integrate, you must input at least one log. | +|
adminPasswordOrKey |
+ Password of administration account for the new Virtual Machine that host new nodes. | +|
adminVMName |
+ Virtual machine name of which hosts the {{ site.data.var.wlsFullBrandName }} admin server, for example: adminVM. |
+ enableCoherenceWebLocalStorage |
+ Specifies whether Local Storage is enabled for the Coherence*Web cluster tier. | + +
location |
+ Must be the same region into which the server was initially deployed. | +|
managedServerPrefix |
+ Must be the same prefix with which the cluster was initially deployed. | +|
numberOfExistingCacheNodes |
+ Number of existing Coherence cache servers, used to name new virtual machines and new managed server. | +|
numberOfNewCacheNodes |
+ Number of new Coherence cahce servers, used to create Virtual Machines and Managed Server. | +|
skuUrnVersion |
+ Must be the same urn with which the cluster was initially deployed. | +|
storageAccountName |
+ The name of an existing storage account. | +|
vmSizeSelectForCoherence |
+ Select appropriate VM Size for Coherence cache servers. | +|
wlsDomainName |
+ Must be the same value provided at deployment time. | +|
wlsPassword |
+ Must be the same value provided at deployment time. | +|
wlsUserName |
+ Must be the same value provided at deployment time. | +|
base64 /my/path/your-certificate.cer -w 0 >temp.txt+ + +## Prepare the Parameters JSON file + +You must construct a parameters JSON file containing the parameters to the add-node ARM template. See [Create Resource Manager parameter file](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/parameter-files) for background information about parameter files. You must specify the information of the existing {{ site.data.var.wlsFullBrandName }} and nodes that to be added. This section shows how to obtain the values for the following required properties. + +
| Parameter Name | +Explanation | +|
_artifactsLocation |
+ See below for details. | +|
aadsSettings |
+ Optional. JSON object type. You can specify this parameters for Azure Active Directory integration. If enable is true, must specify other properties. See the page WebLogic to Azure with AAD via LDAP for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the aadSettings. |
+ |
publicIP |
+ The public IP address of Azure Active Directory LDAP server. | +|
serverHost |
+ The server host of Azure Active Directory LDAP server. | +|
certificateBase64String |
+ The based64 string of LADP client certificate that will be imported to trust store of WebLogic Server to enable SSL connection of AD provider. | +|
adminPasswordOrKey |
+ Password of administration account for the new Virtual Machine that host new nodes. | +|
adminURL |
+ The URL of WebLogic Administration Server, usually made up with Virtual Machine name and port, for example: adminVM:7001. |
+ |
appGatewaySettings |
+ Optional. JSON object type. You can specify these parameters for application gateway configuration. If enable is true, you must specify other properties. If enable is false, the other properties are ignored. See the page Migrate a WebLogic Server cluster to Azure with Azure Application Gateway as a load balancer for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the appGatewaySettings. |
+ |
publicIPName |
+ Azure resource name of application gateway public IP, default value is gwip |
+ |
certificateBase64String |
+ Base64 string of server certificate for application gateway. | +|
certificatePassword |
+ Password of server certificate. | +|
elkSettings |
+ Optional. JSON object type. You can specify this parameters for Elasticsearch and Kibana(ELK) connection. If enable is true, must specify other properties. See the page WebLogic with Elastic on Azure for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the elkSettings. |
+ |
elasticsearchEndpoint |
+ Endpoint of the Elasticsearch instance. | +|
elasticsearchPassword |
+ Password for Elasticsearch account. | +|
elasticsearchUserName |
+ User name for Elasticsearch account. | +|
logIndex |
+ Must be the same value output at ELK deployment time. | +|
logsToIntegrate |
+ Array with string value. Specify the expeted logs to integrate, you must input at least one log. | +|
enableCoherence |
+ If true, create application managed server and add to the Coherence cluster application tier. | +|
numberOfExistingNodes |
+ The number of existing managed application servers, used to generate new virtual machine name. | +|
numberOfNewNodes |
+ The number of application managed server to add. | +|
storageAccountName |
+ The name of an existing storage account. | +|
wlsDomainName |
+ Must be the same value provided at deployment time. | +|
wlsUserName |
+ Must be the same value provided at deployment time. | +|
wlsPassword |
+ Must be the same value provided at deployment time. | +|
customSSLSettings |
+ Optional. JSON object type. You can specify this parameters for configuring Custom SSL Settings for WebLogic Administration Server. If enable is true, must specify other properties. See the page Administering Security for Oracle WebLogic Server and Configuring Keystores for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the customSSLSettings.
+ Set to false by default. |
+ |
customIdentityKeyStoreBase64String |
+ The based64 string of the custom identity keystore file that will be configured in the WebLogic Administration Server to enable SSL connection. | +|
customIdentityKeyStorePassPhrase |
+ The identity keystore pass phrase | +|
customIdentityKeyStoreType |
+ Identity Key Store Type. This can be either JKS or PKCS12 | +|
customTrustKeyStoreBase64String |
+ The based64 string of the custom trust keystore file that will be configured in the WebLogic Administration Server to enable SSL connection. | +|
customTrustKeyStorePassPhrase |
+ The trust keystore pass phrase | +|
customTrustKeyStoreType |
+ Trust Key Store Type. This can be either JKS or PKCS12 | +|
privateKeyAlias |
+ The private key alias | +|
privateKeyPassPhrase |
+ The private Key Pass phrase. | +|
| Parameter Name | +Explanation | +|
_artifactsLocation |
+ See below for details. | +|
elkSettings |
+ Optional. JSON object type. You can specify this parameters for Elasticsearch and Kibana(ELK) connection. If enable is true, must specify other properties. See the page WebLogic with Elastic on Azure for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the elkSettings. |
+ |
elasticsearchEndpoint |
+ Endpoint of the Elasticsearch instance. | +|
elasticsearchPassword |
+ Password for Elasticsearch account. | +|
elasticsearchUserName |
+ User name for Elasticsearch account. | +|
logIndex |
+ Must be the same value output at ELK deployment time. | +|
logsToIntegrate |
+ Array with string value. Specify the expeted logs to integrate, you must input at least one log. | +|
adminPasswordOrKey |
+ Password of administration account for the new Virtual Machine that host new nodes. | +|
adminVMName |
+ Virtual machine name of which hosts the {{ site.data.var.wlsFullBrandName }} admin server, for example: adminVM. |
+ enableCoherenceWebLocalStorage |
+ Specifies whether Local Storage is enabled for the Coherence*Web cluster tier. | + +
location |
+ Must be the same region into which the server was initially deployed. | +|
managedServerPrefix |
+ Must be the same prefix with which the cluster was initially deployed. | +|
numberOfExistingCacheNodes |
+ Number of existing Coherence cache servers, used to name new virtual machines and new managed server. | +|
numberOfNewCacheNodes |
+ Number of new Coherence cahce servers, used to create Virtual Machines and Managed Server. | +|
skuUrnVersion |
+ Must be the same urn with which the cluster was initially deployed. | +|
storageAccountName |
+ The name of an existing storage account. | +|
vmSizeSelectForCoherence |
+ Select appropriate VM Size for Coherence cache servers. | +|
wlsDomainName |
+ Must be the same value provided at deployment time. | +|
wlsPassword |
+ Must be the same value provided at deployment time. | +|
wlsUserName |
+ Must be the same value provided at deployment time. | +|
base64 /my/path/your-certificate.cer -w 0 >temp.txt+ + +## Prepare the Parameters JSON file + +You must construct a parameters JSON file containing the parameters to the add-node ARM template. See [Create Resource Manager parameter file](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/parameter-files) for background information about parameter files. You must specify the information of the existing {{ site.data.var.wlsFullBrandName }} and nodes that to be added. This section shows how to obtain the values for the following required properties. + +
| Parameter Name | +Explanation | +|
_artifactsLocation |
+ See below for details. | +|
aadsSettings |
+ Optional. JSON object type. You can specify this parameters for Azure Active Directory integration. If enable is true, must specify other properties. See the page WebLogic to Azure with AAD via LDAP for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the aadSettings. |
+ |
publicIP |
+ The public IP address of Azure Active Directory LDAP server. | +|
serverHost |
+ The server host of Azure Active Directory LDAP server. | +|
certificateBase64String |
+ The based64 string of LADP client certificate that will be imported to trust store of WebLogic Server to enable SSL connection of AD provider. | +|
adminPasswordOrKey |
+ Password of administration account for the new Virtual Machine that host new nodes. | +|
adminURL |
+ The URL of WebLogic Administration Server, usually made up with Virtual Machine name and port, for example: adminVM:7001. |
+ |
elkSettings |
+ Optional. JSON object type. You can specify this parameters for Elasticsearch and Kibana(ELK) connection. If enable is true, must specify other properties. See the page WebLogic with Elastic on Azure for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the elkSettings. |
+ |
elasticsearchEndpoint |
+ Endpoint of the Elasticsearch instance. | +|
elasticsearchPassword |
+ Password for Elasticsearch account. | +|
elasticsearchUserName |
+ User name for Elasticsearch account. | +|
logIndex |
+ Must be the same value output at ELK deployment time. | +|
logsToIntegrate |
+ Array with string value. Specify the expeted logs to integrate, you must input at least one log. | +|
numberOfExistingNodes |
+ The number of existing managed application nodes, used to generate new virtual machine name,. | +|
numberOfNewNodes |
+ The number of nodes to add. | +|
storageAccountName |
+ The name of an existing storage account. | +|
wlsDomainName |
+ Must be the same value provided at deployment time. | +|
wlsUserName |
+ Must be the same value provided at deployment time. | +|
wlsPassword |
+ Must be the same value provided at deployment time. | +|
customSSLSettings |
+ Optional. JSON object type. You can specify this parameters for configuring Custom SSL Settings for WebLogic Administration Server. If enable is true, must specify other properties. See the page Administering Security for Oracle WebLogic Server and Configuring Keystores for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the customSSLSettings.
+ Set to false by default. |
+ |
customIdentityKeyStoreBase64String |
+ The based64 string of the custom identity keystore file that will be configured in the WebLogic Administration Server to enable SSL connection. | +|
customIdentityKeyStorePassPhrase |
+ The identity keystore pass phrase | +|
customIdentityKeyStoreType |
+ Identity Key Store Type. This can be either JKS or PKCS12 | +|
customTrustKeyStoreBase64String |
+ The based64 string of the custom trust keystore file that will be configured in the WebLogic Administration Server to enable SSL connection. | +|
customTrustKeyStorePassPhrase |
+ The trust keystore pass phrase | +|
customTrustKeyStoreType |
+ Trust Key Store Type. This can be either JKS or PKCS12 | +|
privateKeyAlias |
+ The private key alias | +|
privateKeyPassPhrase |
+ The private Key Pass phrase. | +|
base64 your-JKS/PKCS12-certificate-contents -w 0 > temp.txt
+
+Use temp.txt contents to set the value for ohsSSLKeystoreData
+
+#### Example Parameters JSON
+
+Here is a fully filled out parameters file. Note that we did not include any optional parameters, assuming the {{ site.data.var.wlsFullBrandName }} was deployed accepting the default values.
+
+{{ site.data.var.passwordInFileNote }}
+
+```json
+{
+ "_artifactsLocation": {
+ "value": "{{ armTemplateBasePath }}"
+ },
+ "adminPasswordOrKey": {
+ "value": "Azure123456!"
+ },
+ "adminRestMgmtURL": {
+ "value": "http://adminVM:7001/management/weblogic/latest"
+ },
+ "adminUsername": {
+ "value": "azureuser"
+ },
+ "dnsLabelPrefix": {
+ "value": "wls"
+ },
+ "keyType": {
+ "value": "JKS"
+ },
+ "location": {
+ "value": "eastus"
+ },
+ "ohsComponentName": {
+ "value": "ohs_component"
+ },
+ "ohsDomainName": {
+ "value": "ohsStandaloneDomain"
+ },
+ "ohsNMPassword": {
+ "value": "Nmpswd1234567"
+ },
+ "ohsNMUser": {
+ "value": "weblogic"
+ },
+ "ohsSSLKeystoreData": {
+ "value": "/u3+7QAAAAIAAAABAAAAAQAKc2VsZnNpZ25lZAAAAX ...."
+ },
+ "ohsSSLKeystorePassword": {
+ "value": "azure123!"
+ },
+ "ohsSkuUrnVersion": {
+ "value": "ohs-122140-jdk8-ol76;ohs-122140-jdk8-ol76;latest"
+ },
+ "ohsVMName": {
+ "value": "ohsVM"
+ },
+ "ohshttpPort": {
+ "value": "7777"
+ },
+ "ohshttpsPort": {
+ "value": "4444"
+ },
+ "oracleVaultPswd": {
+ "value": "Welcome1234567"
+ },
+ "storageAccountName": {
+ "value": "6be282olvm"
+ },
+ "virtualNetworkName": {
+ "value": "wlsd_VNET"
+ },
+ "wlsPassword": {
+ "value": "Welcome1234567"
+ },
+ "wlsUserName": {
+ "value": "weblogic"
+ }
+}
+```
+
+### Invoke the ARM template
+Assume your parameters file is available in the current directory and is named parameters.json. This section shows the commands to configure your {{ site.data.var.wlsFullBrandName }} deployment with a Oracle HTTP Server. Replace yourResourceGroup with the Azure resource group in which the {{ site.data.var.wlsFullBrandName }} is deployed.
+
+### First, validate your parameters file
+The `az deployment group validate` command is very useful to validate your parameters file is syntactically correct.
+
+```bash
+az deployment group validate --verbose --resource-group `yourResourceGroup` --parameters @parameters.json --template-uri {{ armTemplateBasePath }}nestedtemplates/ohsNestedTemplate.json
+```
+If the command returns with an exit status other than `0`, inspect the output and resolve the problem before proceeding. You can check the exit status by executing the commad `echo $?` immediately after the `az` command.
+
+### Next, execute the template
+After successfully validating the template invocation, change `validate` to `create` to invoke the template.
+
+```bash
+az deployment group create --verbose --resource-group `yourResourceGroup` --parameters @parameters.json --template-uri {{ armTemplateBasePath }}nestedtemplates/ohsNestedTemplate.json
+```
+As with the validate command, if the command returns with an exit status other than 0, inspect the output and resolve the problem.
+
+This is an example output of successful deployment. Look for `"provisioningState": "Succeeded"` in your output.
+
+```bash
+ "provisioningState": "Succeeded",
+ "template": null,
+ "templateHash": "13760326614657528322",
+```
+
+## Verify Oracle HTTP Server setup
+
+Successful deployment provides Oracle HTTP Server access url in your output, similar to below.
+
+```json
+ "ohsAccessURL": {
+ "type": "String",
+ "value": "http://wls-5ff4cab395-loadbalancer.eastus.cloudapp.azure.com:7777"
+ },
+ "ohsSecureAccessURL": {
+ "type": "String",
+ "value": "https://wls-5ff4cab395-loadbalancer.eastus.cloudapp.azure.com:4444"
+ }
+```
+
+Follow the steps to verify Oracle HTTP Server.
+* Visit the {{ site.data.var.wlsFullBrandName }} Admin console.
+* In the left navigator, expand the tree to select **Deployments**, install some sample application targeted to WebLogic Cluster and start the service.
+* Access your application using ohsAccessURL/application
+* Access your application using ohsSecureAccessURL/application
+
diff --git a/index.html b/index.html
new file mode 100644
index 000000000..a21e7ef4f
--- /dev/null
+++ b/index.html
@@ -0,0 +1,5 @@
+
+
+| Parameter Name | +Explanation | +|
_artifactsLocation |
+ See below for details. | +|
elkSettings |
+ Optional. JSON object type. You can specify this parameters for Elasticsearch and Kibana(ELK) connection. If enable is true, must specify other properties. See the page WebLogic with Elastic on Azure for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the elkSettings. |
+ |
elasticsearchEndpoint |
+ Endpoint of the Elasticsearch instance. | +|
elasticsearchPassword |
+ Password for Elasticsearch account. | +|
elasticsearchUserName |
+ User name for Elasticsearch account. | +|
logIndex |
+ Must be the same value output at ELK deployment time. | +|
logsToIntegrate |
+ Array with string value. Specify the expeted logs to integrate, you must input at least one log. | +|
adminPasswordOrKey |
+ Password of administration account for the new Virtual Machine that host new nodes. | +|
adminVMName |
+ Virtual machine name of which hosts the {{ site.data.var.wlsFullBrandName }} admin server, for example: adminVM. |
+ enableCoherenceWebLocalStorage |
+ Specifies whether Local Storage is enabled for the Coherence*Web cluster tier. | + +
location |
+ Must be the same region into which the server was initially deployed. | +|
managedServerPrefix |
+ Must be the same prefix with which the cluster was initially deployed. | +|
numberOfExistingCacheNodes |
+ Number of existing Coherence cache servers, used to name new virtual machines and new managed server. | +|
numberOfNewCacheNodes |
+ Number of new Coherence cahce servers, used to create Virtual Machines and Managed Server. | +|
skuUrnVersion |
+ Must be the same urn with which the cluster was initially deployed. | +|
storageAccountName |
+ The name of an existing storage account. | +|
vmSizeSelectForCoherence |
+ Select appropriate VM Size for Coherence cache servers. | +|
wlsDomainName |
+ Must be the same value provided at deployment time. | +|
wlsPassword |
+ Must be the same value provided at deployment time. | +|
wlsUserName |
+ Must be the same value provided at deployment time. | +|
base64 /my/path/your-certificate.cer -w 0 >temp.txt+ + +## Prepare the Parameters JSON file + +You must construct a parameters JSON file containing the parameters to the add-node ARM template. See [Create Resource Manager parameter file](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/parameter-files) for background information about parameter files. You must specify the information of the existing {{ site.data.var.wlsFullBrandName }} and nodes that to be added. This section shows how to obtain the values for the following required properties. + +
| Parameter Name | +Explanation | +|
_artifactsLocation |
+ See below for details. | +|
aadsSettings |
+ Optional. JSON object type. You can specify this parameters for Azure Active Directory integration. If enable is true, must specify other properties. See the page WebLogic to Azure with AAD via LDAP for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the aadSettings. |
+ |
publicIP |
+ The public IP address of Azure Active Directory LDAP server. | +|
serverHost |
+ The server host of Azure Active Directory LDAP server. | +|
certificateBase64String |
+ The based64 string of LADP client certificate that will be imported to trust store of WebLogic Server to enable SSL connection of AD provider. | +|
adminPasswordOrKey |
+ Password of administration account for the new Virtual Machine that host new nodes. | +|
adminURL |
+ The URL of WebLogic Administration Server, usually made up with Virtual Machine name and port, for example: adminVM:7001. |
+ |
appGatewaySettings |
+ Optional. JSON object type. You can specify these parameters for application gateway configuration. If enable is true, you must specify other properties. If enable is false, the other properties are ignored. See the page Migrate a WebLogic Server cluster to Azure with Azure Application Gateway as a load balancer for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the appGatewaySettings. |
+ |
publicIPName |
+ Azure resource name of application gateway public IP, default value is gwip |
+ |
certificateBase64String |
+ Base64 string of server certificate for application gateway. | +|
certificatePassword |
+ Password of server certificate. | +|
elkSettings |
+ Optional. JSON object type. You can specify this parameters for Elasticsearch and Kibana(ELK) connection. If enable is true, must specify other properties. See the page WebLogic with Elastic on Azure for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the elkSettings. |
+ |
elasticsearchEndpoint |
+ Endpoint of the Elasticsearch instance. | +|
elasticsearchPassword |
+ Password for Elasticsearch account. | +|
elasticsearchUserName |
+ User name for Elasticsearch account. | +|
logIndex |
+ Must be the same value output at ELK deployment time. | +|
logsToIntegrate |
+ Array with string value. Specify the expeted logs to integrate, you must input at least one log. | +|
enableCoherence |
+ If true, create application managed server and add to the Coherence cluster application tier. | +|
numberOfExistingNodes |
+ The number of existing managed application servers, used to generate new virtual machine name. | +|
numberOfNewNodes |
+ The number of application managed server to add. | +|
storageAccountName |
+ The name of an existing storage account. | +|
wlsDomainName |
+ Must be the same value provided at deployment time. | +|
wlsUserName |
+ Must be the same value provided at deployment time. | +|
wlsPassword |
+ Must be the same value provided at deployment time. | +|
customSSLSettings |
+ Optional. JSON object type. You can specify this parameters for configuring Custom SSL Settings for WebLogic Administration Server. If enable is true, must specify other properties. See the page Administering Security for Oracle WebLogic Server and Configuring Keystores for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the customSSLSettings.
+ Set to false by default. |
+ |
customIdentityKeyStoreBase64String |
+ The based64 string of the custom identity keystore file that will be configured in the WebLogic Administration Server to enable SSL connection. | +|
customIdentityKeyStorePassPhrase |
+ The identity keystore pass phrase | +|
customIdentityKeyStoreType |
+ Identity Key Store Type. This can be either JKS or PKCS12 | +|
customTrustKeyStoreBase64String |
+ The based64 string of the custom trust keystore file that will be configured in the WebLogic Administration Server to enable SSL connection. | +|
customTrustKeyStorePassPhrase |
+ The trust keystore pass phrase | +|
customTrustKeyStoreType |
+ Trust Key Store Type. This can be either JKS or PKCS12 | +|
privateKeyAlias |
+ The private key alias | +|
privateKeyPassPhrase |
+ The private Key Pass phrase. | +|
base64 /my/path/your-certificate.cer -w 0 >temp.txt+ + +## Prepare the Parameters JSON file + +You must construct a parameters JSON file containing the parameters to the add-node ARM template. See [Create Resource Manager parameter file](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/parameter-files) for background information about parameter files. You must specify the information of the existing {{ site.data.var.wlsFullBrandName }} and nodes that to be added. This section shows how to obtain the values for the following required properties. + +
| Parameter Name | +Explanation | +|
_artifactsLocation |
+ See below for details. | +|
aadsSettings |
+ Optional. JSON object type. You can specify this parameters for Azure Active Directory integration. If enable is true, must specify other properties. See the page WebLogic to Azure with AAD via LDAP for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the aadSettings. |
+ |
publicIP |
+ The public IP address of Azure Active Directory LDAP server. | +|
serverHost |
+ The server host of Azure Active Directory LDAP server. | +|
certificateBase64String |
+ The based64 string of LADP client certificate that will be imported to trust store of WebLogic Server to enable SSL connection of AD provider. | +|
adminPasswordOrKey |
+ Password of administration account for the new Virtual Machine that host new nodes. | +|
adminURL |
+ The URL of WebLogic Administration Server, usually made up with Virtual Machine name and port, for example: adminVM:7001. |
+ |
elkSettings |
+ Optional. JSON object type. You can specify this parameters for Elasticsearch and Kibana(ELK) connection. If enable is true, must specify other properties. See the page WebLogic with Elastic on Azure for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the elkSettings. |
+ |
elasticsearchEndpoint |
+ Endpoint of the Elasticsearch instance. | +|
elasticsearchPassword |
+ Password for Elasticsearch account. | +|
elasticsearchUserName |
+ User name for Elasticsearch account. | +|
logIndex |
+ Must be the same value output at ELK deployment time. | +|
logsToIntegrate |
+ Array with string value. Specify the expeted logs to integrate, you must input at least one log. | +|
numberOfExistingNodes |
+ The number of existing managed application nodes, used to generate new virtual machine name,. | +|
numberOfNewNodes |
+ The number of nodes to add. | +|
storageAccountName |
+ The name of an existing storage account. | +|
wlsDomainName |
+ Must be the same value provided at deployment time. | +|
wlsUserName |
+ Must be the same value provided at deployment time. | +|
wlsPassword |
+ Must be the same value provided at deployment time. | +|
customSSLSettings |
+ Optional. JSON object type. You can specify this parameters for configuring Custom SSL Settings for WebLogic Administration Server. If enable is true, must specify other properties. See the page Administering Security for Oracle WebLogic Server and Configuring Keystores for further information. |
+ |
enable |
+ If enable is true, must specify all properties of the customSSLSettings.
+ Set to false by default. |
+ |
customIdentityKeyStoreBase64String |
+ The based64 string of the custom identity keystore file that will be configured in the WebLogic Administration Server to enable SSL connection. | +|
customIdentityKeyStorePassPhrase |
+ The identity keystore pass phrase | +|
customIdentityKeyStoreType |
+ Identity Key Store Type. This can be either JKS or PKCS12 | +|
customTrustKeyStoreBase64String |
+ The based64 string of the custom trust keystore file that will be configured in the WebLogic Administration Server to enable SSL connection. | +|
customTrustKeyStorePassPhrase |
+ The trust keystore pass phrase | +|
customTrustKeyStoreType |
+ Trust Key Store Type. This can be either JKS or PKCS12 | +|
privateKeyAlias |
+ The private key alias | +|
privateKeyPassPhrase |
+ The private Key Pass phrase. | +|
base64 your-JKS/PKCS12-certificate-contents -w 0 > temp.txt
+
+Use temp.txt contents to set the value for ohsSSLKeystoreData
+
+#### Example Parameters JSON
+
+Here is a fully filled out parameters file. Note that we did not include any optional parameters, assuming the {{ site.data.var.wlsFullBrandName }} was deployed accepting the default values.
+
+{{ site.data.var.passwordInFileNote }}
+
+```json
+{
+ "_artifactsLocation": {
+ "value": "{{ armTemplateBasePath }}"
+ },
+ "adminPasswordOrKey": {
+ "value": "Azure123456!"
+ },
+ "adminRestMgmtURL": {
+ "value": "http://adminVM:7001/management/weblogic/latest"
+ },
+ "adminUsername": {
+ "value": "azureuser"
+ },
+ "dnsLabelPrefix": {
+ "value": "wls"
+ },
+ "keyType": {
+ "value": "JKS"
+ },
+ "location": {
+ "value": "eastus"
+ },
+ "ohsComponentName": {
+ "value": "ohs_component"
+ },
+ "ohsDomainName": {
+ "value": "ohsStandaloneDomain"
+ },
+ "ohsNMPassword": {
+ "value": "Nmpswd1234567"
+ },
+ "ohsNMUser": {
+ "value": "weblogic"
+ },
+ "ohsSSLKeystoreData": {
+ "value": "/u3+7QAAAAIAAAABAAAAAQAKc2VsZnNpZ25lZAAAAX ...."
+ },
+ "ohsSSLKeystorePassword": {
+ "value": "azure123!"
+ },
+ "ohsSkuUrnVersion": {
+ "value": "ohs-122140-jdk8-ol76;ohs-122140-jdk8-ol76;latest"
+ },
+ "ohsVMName": {
+ "value": "ohsVM"
+ },
+ "ohshttpPort": {
+ "value": "7777"
+ },
+ "ohshttpsPort": {
+ "value": "4444"
+ },
+ "oracleVaultPswd": {
+ "value": "Welcome1234567"
+ },
+ "storageAccountName": {
+ "value": "6be282olvm"
+ },
+ "virtualNetworkName": {
+ "value": "wlsd_VNET"
+ },
+ "wlsPassword": {
+ "value": "Welcome1234567"
+ },
+ "wlsUserName": {
+ "value": "weblogic"
+ }
+}
+```
+
+### Invoke the ARM template
+Assume your parameters file is available in the current directory and is named parameters.json. This section shows the commands to configure your {{ site.data.var.wlsFullBrandName }} deployment with a Oracle HTTP Server. Replace yourResourceGroup with the Azure resource group in which the {{ site.data.var.wlsFullBrandName }} is deployed.
+
+### First, validate your parameters file
+The `az deployment group validate` command is very useful to validate your parameters file is syntactically correct.
+
+```bash
+az deployment group validate --verbose --resource-group `yourResourceGroup` --parameters @parameters.json --template-uri {{ armTemplateBasePath }}nestedtemplates/ohsNestedTemplate.json
+```
+If the command returns with an exit status other than `0`, inspect the output and resolve the problem before proceeding. You can check the exit status by executing the commad `echo $?` immediately after the `az` command.
+
+### Next, execute the template
+After successfully validating the template invocation, change `validate` to `create` to invoke the template.
+
+```bash
+az deployment group create --verbose --resource-group `yourResourceGroup` --parameters @parameters.json --template-uri {{ armTemplateBasePath }}nestedtemplates/ohsNestedTemplate.json
+```
+As with the validate command, if the command returns with an exit status other than 0, inspect the output and resolve the problem.
+
+This is an example output of successful deployment. Look for `"provisioningState": "Succeeded"` in your output.
+
+```bash
+ "provisioningState": "Succeeded",
+ "template": null,
+ "templateHash": "13760326614657528322",
+```
+
+## Verify Oracle HTTP Server setup
+
+Successful deployment provides Oracle HTTP Server access url in your output, similar to below.
+
+```json
+ "ohsAccessURL": {
+ "type": "String",
+ "value": "http://wls-5ff4cab395-loadbalancer.eastus.cloudapp.azure.com:7777"
+ },
+ "ohsSecureAccessURL": {
+ "type": "String",
+ "value": "https://wls-5ff4cab395-loadbalancer.eastus.cloudapp.azure.com:4444"
+ }
+```
+
+Follow the steps to verify Oracle HTTP Server.
+* Visit the {{ site.data.var.wlsFullBrandName }} Admin console.
+* In the left navigator, expand the tree to select **Deployments**, install some sample application targeted to WebLogic Cluster and start the service.
+* Access your application using ohsAccessURL/application
+* Access your application using ohsSecureAccessURL/application
+
diff --git a/subtemplate-src/dynamic-customDNSTemplate.md b/subtemplate-src/dynamic-customDNSTemplate.md
new file mode 100644
index 000000000..5e6921581
--- /dev/null
+++ b/subtemplate-src/dynamic-customDNSTemplate.md
@@ -0,0 +1,177 @@
+{% include variables.md %}
+
+# Configure DNS alias to {{ site.data.var.wlsFullBrandName }}
+
+This page documents how to configure an existing deployment of {{ site.data.var.wlsFullBrandName }} with a custom DNS alias.
+
+## Prerequisites
+
+### Environment for Setup
+
+* [Azure CLI](https://docs.microsoft.com/en-us/cli/azure), use `az --version` to test if `az` works.
+
+### WebLogic Server Instance
+
+The DNS Configuraton ARM template will be applied to an existing {{ site.data.var.wlsFullBrandName }} instance. If you don't have one, please create a new instance from the Azure portal, by following the link to the offer [in the index](index.md).
+
+### Registered Domain Name
+
+You need to buy a domain name to create a custom DNS alias.
+
+### Azure DNS Zone
+
+If you create the DNS alias on an existing [Azure DNS Zone](https://docs.microsoft.com/en-us/azure/dns/dns-overview), make sure you have perfomed the [Azure DNS Delegation](https://docs.microsoft.com/en-us/azure/dns/dns-domain-delegation). Once you have completed the delegation, you can verify it with `nslookup`. For example, assuming your domain name is **contoso.com**, this output shows a correct delegation.
+
+```bash
+$ nslookup -type=SOA contoso.com
+Server: 172.29.80.1
+Address: 172.29.80.1#53
+
+Non-authoritative answer:
+contoso.com
+ origin = ns1-01.azure-dns.com
+ mail addr = azuredns-hostmaster.microsoft.com
+ serial = 1
+ refresh = 3600
+ retry = 300
+ expire = 2419200
+ minimum = 300
+Name: ns1-01.azure-dns.com
+Address: 40.90.4.1
+Name: ns1-01.azure-dns.com
+Address: 2603:1061::1
+```
+
+We strongly recommand you create an Azure DNS Zone for domain management and reuse it for other perpose. Follow the [guide](https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal) to create an Azure DNS Zone.
+
+### Azure Managed Indentify
+
+If you are going to configure DNS alias based on an existing DNS Zone, you are required to input the ID of a user-assigned managed identity.
+
+Follow this [guide](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-portal) to create a user-assigned managed identity.
+
+To obtain ID of the indentify: go to Azure Portal; open the identity **Overview** page; click **JSON View** and copy the **Resource ID**.
+
+
+## Prepare the Parameters
+
+We provide an automation shell script for DNS configuration. You must specify the information of the existing Oracle WebLogic Server. This section shows how to obtain the values for the following required properties.
+
+| Parameter Name | Explanation |
+|----------------|-------------|
+| `--admin-vm-name`| Required. Name of vitual machine that hosts {{ site.data.var.wlsFullBrandName }} admin server. Must be the same value provided at initial deployment time.|
+| `--admin-console-label` | Required. Label for {{ site.data.var.wlsFullBrandName }} admin console. Used to generate subdomain of admin console. |
+| `--artifact-location`| Required. See below for details. |
+| `--resource-group` | Required. Name of resource group that has WebLogic cluster deployed. |
+| `--location` | Required. Must be the same region into which the server was initially deployed. |
+| `--zone-name` | Required. Azure DNS Zone name. |
+| `--ohs-vm-name` | Optional. Specify name of the VM that hosts the Oracle HTTP Server Load Balancer. |
+| `--loadbalancer-label` | Optional. Label for Load Balancer. Used to generate subdomain of application gateway. The parameter is only required if you want to create DNS alias for application gateway.|
+| `--identity-id` | Optional. ID of Azure user-assigned managed identity. The parameter is only required if you are creating DNS alias on an existing DNS Zone.|
+| `--zone-resource-group` | Optional. Name of resource group that has Azure DNS Zone deployed. The parameter is only required if you are creating DNS alias on an existing DNS Zone. |
+| `--help` | Help. |
+
+### Artifacts location
+
+This value must be the following.
+
+```bash
+{{ armTemplateBasePath }}
+```
+
+## Invoke the Automation Script
+
+We provide an automation script to configure a custom DNS alias. The script lets you do the following:
+
+ * If you have an Azure DNS Zone, it will create a DNS alias for the admin console and application gateway on the existing DNS Zone.
+ * If you don't have an Azure DNS Zone, it will create the DNS Zone in the same resource group as the WebLogic cluster, then create the DNS alias for the admin console and application gateway.
+
+### Configure DNS Alias on an Existing Azure DNS Zone
+
+To configure a DNS alias on an existing Azure DNS Zone, in addition to the required parameters, you must also specify an Azure user-assigned managed identity ID and the resource group name in which your DNS Zone is deployed.
+
+This is an example to create a DNS alias `admin.contoso.com` for the admin console and `applciations.contoso.com` for the application gateway on an existing Azure DNS Zone.
+
+```bash
+$ curl -fsSL {{ site.data.var.artifactsLocationBase }}{{ pageDir }}/{{ site.data.var.artifactsLocationTag }}/cli-scripts/custom-dns-alias-cli.sh \
+ | /bin/bash -s -- \
+ --resource-group `yourResourceGroup` \
+ --admin-vm-name adminVM \
+ --admin-console-label admin \
+ --artifact-location {{ armTemplateBasePath }} \
+ --location eastus \
+ --zone-name contoso.com \
+ --ohs-vm-name ohsVM \
+ --loadbalancer-label applications \
+ --identity-id `yourIndentityID` \
+ --zone-resource-group `yourDNSZoneResourceGroup`
+```
+
+An example output:
+
+```text
+Done!
+
+Custom DNS alias:
+ Resource group: haiche-dns-doc
+ WebLogic Server Administration Console URL: http://admin.contoso.com:7001/console
+ WebLogic Server Administration Console secured URL: https://admin.contoso.com:7002/console
+
+
+ Application Gateway URL: http://applications.contoso.com:7777
+ Application Gateway secured URL: https://applications.contoso.com:4444
+```
+
+
+### Configure DNS Alias on a New Azure DNS Zone
+
+To configure a DNS alias on a new Azure DNS Zone, you must specify the required parameters.
+
+This is an example of creating an Azure DNS Zone, then creating a DNS alias `admin.contoso.com` for the admin console and `applications.contoso.com` for application gateway.
+
+```bash
+$ curl -fsSL {{ site.data.var.artifactsLocationBase }}{{ pageDir }}/{{ site.data.var.artifactsLocationTag }}/cli-scripts/custom-dns-alias-cli.sh \
+ | /bin/bash -s -- \
+ --resource-group `yourResourceGroup` \
+ --admin-vm-name adminVM \
+ --admin-console-label admin \
+ --artifact-location {{ armTemplateBasePath }} \
+ --location eastus \
+ --zone-name contoso.com \
+ --ohs-vm-name ohsVM \
+ --loadbalancer-label applications
+```
+
+An example output:
+
+```text
+DONE!
+
+
+Action required:
+ Complete Azure DNS delegation to make the alias accessible.
+ Reference: https://aka.ms/dns-domain-delegation
+ Name servers:
+ [
+ "ns1-02.azure-dns.com.",
+ "ns2-02.azure-dns.net.",
+ "ns3-02.azure-dns.org.",
+ "ns4-02.azure-dns.info."
+ ]
+
+Custom DNS alias:
+ Resource group: haiche-dns-doc
+ WebLogic Server Administration Console URL: http://admin.contoso.com:7001/console
+ WebLogic Server Administration Console secured URL: https://admin.contoso.com:7002/console
+
+
+ Application Gateway URL: http://applications.contoso.com:7777
+ Application Gateway secured URL: https://applications.contoso.com:4444
+```
+
+**Note:** The DNS aliases are not accessible now, you must perform Azure DNS delegation after the deployment. Follow [Delegation of DNS zones with Azure DNS](https://aka.ms/dns-domain-delegation) to complete the Azure DNS delegation.
+
+
+## Verify the Custom Alias
+
+Access the URL from output to verify if the custom alias works.