Changes for 112950 & 112852

services/mobilefoundation/c_using_mfs_p1.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2016
-lastupdated:  "2016-09-12"
+lastupdated:  "2016-12-09"
 
 ---
 
@@ -49,6 +49,16 @@ For more information on MobileFirst Analytics you can refer to [MobileFirst Foun
 
 **Note:** The Mobile Analytics server is removed when you delete the {{site.data.keyword.mobilefoundation_short}} service instance or when you attempt to re-create the {{site.data.keyword.mfserver_short_notm}}.
 
+##  Deleting Mobile Analytics server
+{: #deleting_analytics_server_dev}
+
+You can now delete the Mobile Analytics server that was added to the {{site.data.keyword.mobilefoundation_short}} service instance, from the {{site.data.keyword.mobilefoundation_short}} service dashboard.
+
+* Click **Delete Analytics** to delete the  Mobile Analytics server that was added to the {{site.data.keyword.mobilefoundation_short}} service instance.
+
+ This will delete the analytics container group. The process of deleting analytics containers takes about 10 minutes. You can refresh the screen to view the updated status. Once the analytics containers are deleted, the **Add Analytics** button is re-enabled, you can use this to add the Mobile Analytics server again if you choose to.
+
+
 ## Re-creating the {{site.data.keyword.mobilefirst}} server
 {: #recreate_mobilefoundation_p1}
 

services/mobilefoundation/c_using_mfs_p2.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2016
-lastupdated:  "2016-09-12"
+lastupdated:  "2016-12-09"
 
 ---
 
@@ -34,23 +34,39 @@ After you create the {{site.data.keyword.mobilefoundation_short}}: Professional
 ### Setting up connection to {{site.data.keyword.dashdbshort_notm}} service instance
 {: #connect_dashdb_p2}
 
-After the {{site.data.keyword.mobilefoundation_short}}: Professional 1 Application service instance is created you will see the *Overview* page where you will need to specify the connection information for the {{site.data.keyword.dashdbshort_notm}}: Enterprise Transactional service instance.
+After the {{site.data.keyword.mobilefoundation_short}}: Professional 1 Application service instance is created you will see the *Overview* page where you will need to specify the connection information for the {{site.data.keyword.dashdbshort_notm}} for Transactions service instance, that the {{site.data.keyword.mobilefoundation_short}} service instance should connect to.
 
-1. Select the {{site.data.keyword.Bluemix_notm}} `Organization` where the {{site.data.keyword.dashdbshort_notm}} service instance exists.
+**Note:** If you already have a {{site.data.keyword.dashdbshort_notm}} for Analytics: Enterprise for Transactions service instance, you can configure to use the same to connect to the {{site.data.keyword.mobilefoundation_short}} service instance.
+
+You can also create a new {{site.data.keyword.dashdbshort_notm}} for Transactions service instance, if you do not have one already existing.
+
+Follow the steps below to create a new dashDB for Transactions service instance:
+
+1. In the *Overview* page select **Create New Service** section.
 
-+ Select the {{site.data.keyword.Bluemix_notm}} `Space` where the {{site.data.keyword.dashdbshort_notm}} service instance exists, from the list of spaces available in the selected `Organization`.
++ Select `Yes` on the **High availability configuration** option, if you want high available {{site.data.keyword.dashdbshort_notm}} for Transactions service instance.
 
-**Note:** If you do not see listed the `Organization` and `Space` where your {{site.data.keyword.dashdbshort_notm}} service instance exists then check if you are a member of that `Organization` and `Space`.
++ Review the plan details and click **Create**.
+
+A new {{site.data.keyword.dashdbshort_notm}} for Transactions: EnterpriseForTransactions2.8.500 service instance is created, which provides a dedicated {{site.data.keyword.dashdbshort_notm}} instance with 8GB RAM and 2 vCPUs, and 500 GB of storage.
+
+Follow the steps below to connect to an existing {{site.data.keyword.dashdbshort_notm}} service instance or to the {{site.data.keyword.dashdbshort_notm}} for Transactions service instance that you just created:
+
+1. Select the {{site.data.keyword.Bluemix_notm}} `Organization` where the {{site.data.keyword.dashdbshort_notm}} service instance exists.
+
++ Select the {{site.data.keyword.Bluemix_notm}} `Space` where the {{site.data.keyword.dashdbshort_notm}} service instance exists, from the list of spaces available in the selected `Organization`.   
+**Note:** If you do not see listed the `Organization` and `Space` where your {{site.data.keyword.dashdbshort_notm}} service instance exists then check if you are a member of that `Organization` and `Space`. You are required to have a *Developer* role access to the organization and space, as the {{site.data.keyword.mobilefoundation_short}} service accesses the credentials from the {{site.data.keyword.dashdbshort_notm}} service.
 
 + Select the {{site.data.keyword.dashdbshort_notm}} `Service Name` and `Credentials` to connect to the existing  {{site.data.keyword.dashdbshort_notm}} service instance.
 
-+  Test the connection to the specified {{site.data.keyword.dashdbshort_notm}}: Enterprise Transactional service instance.
++  Test the connection to the specified {{site.data.keyword.dashdbshort_notm}} service instance.
+
++  Click **Add**. This action creates the required tables in the configured {{site.data.keyword.dashdbshort_notm}} database service instance.
 
-+  Click **Continue**. This action creates the required tables in the configured {{site.data.keyword.dashdbshort_notm}} database service instance.
+In a few seconds, you can access the `Overview` page that provides you with  tutorials and videos to help you get started with the  {{site.data.keyword.mobilefoundation_short}} service.
 
 **Note**: You cannot change the {{site.data.keyword.dashdbshort_notm}} service instance that is configured to be used by your {{site.data.keyword.mobilefoundation_short}} service instance. However, you can use the same {{site.data.keyword.dashdbshort_notm}} service instance across multiple {{site.data.keyword.mobilefoundation_short}} service instances, as each {{site.data.keyword.mobilefoundation_short}} service instance creates its own schema in the selected {{site.data.keyword.dashdbshort_notm}} service instance.
 
-* In a few seconds, you can access the `Overview` page that provides you with  tutorials and videos to help you get started with the  {{site.data.keyword.mobilefoundation_short}} service.
 
 ## Starting the {{site.data.keyword.mobilefirst}} server
 {: #start_mobilefoundation_p2}
@@ -84,7 +100,7 @@ The process of provisioning your server starts. This process takes about 10 minu
 
  Users can also attach volumes to the containers to persist data. The volume once selected cannot be changed. 20 GB is the default file share space available to the user. If the user needs additional storage space to persist analytics data, he is required to buy additional file share and create a volume using this file share. He can then select this new volume while deploying the analytics server.
 
- For more information on adding volumes to {{site.data.keyword.containerlong}}, refer to [Storing persistent data in a volume by using the {{site.data.keyword.Bluemix_notm}} Dashboard  ](https://www.bluemix.net/docs/containers/container_volumes_ui.html){: new_window}.
+ For more information on adding volumes to {{site.data.keyword.containerlong}}, refer to [Storing persistent data in a volume by using the {{site.data.keyword.Bluemix_notm}} Dashboard](https://console.ng.bluemix.net/docs/containers/container_volumes_ui.html){: new_window}.
 
 * Click **Add Analytics** to add the Mobile Analytics server to the {{site.data.keyword.mobilefoundation_short}} service instance.
 
@@ -98,6 +114,16 @@ For more information on MobileFirst Analytics you can refer to [MobileFirst Foun
 
 **Note:** The Mobile Analytics server is removed when you delete the {{site.data.keyword.mobilefoundation_short}} service instance or when you attempt to re-create the {{site.data.keyword.mfserver_short_notm}}.
 
+##  Deleting Mobile Analytics server
+{: #deleting_analytics_server_prof}
+
+You can now delete the Mobile Analytics server that was added to the {{site.data.keyword.mobilefoundation_short}} service instance, from the {{site.data.keyword.mobilefoundation_short}} service dashboard.
+
+* Click **Delete Analytics** to delete the  Mobile Analytics server that has been added to the {{site.data.keyword.mobilefoundation_short}} service instance.
+
+ This will delete the analytics container group. The process of deleting analytics containers takes about 10 minutes. You can refresh the screen to view the updated status. Once the analytics containers are deleted, the **Add Analytics** button is re-enabled, you can use this to add the Mobile Analytics server again if you choose to.
+
+
 ## Re-creating the {{site.data.keyword.mobilefirst}} server
 {: #recreate_mobilefoundation_p2}
 

services/mobilefoundation/c_using_mfs_p3.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2016
-lastupdated:  "2016-10-14"
+lastupdated:  "2016-12-09"
 
 ---
 
@@ -35,23 +35,38 @@ After you create the {{site.data.keyword.mobilefoundation_short}}: Developer Pro
 ### Setting up connection to {{site.data.keyword.dashdbshort_notm}} service instance
 {: #connect_dashdb_p3}
 
-After the {{site.data.keyword.mobilefoundation_short}}: Developer Pro service instance is created you will see the *Overview* page where you will need to specify the connection information for the {{site.data.keyword.dashdbshort_notm}}: Enterprise Transactional service instance.
+After the {{site.data.keyword.mobilefoundation_short}}: Developer Pro service instance is created you will see the *Overview* page where you will need to specify the connection information for the {{site.data.keyword.dashdbshort_notm}} for Transactions service instance, that the {{site.data.keyword.mobilefoundation_short}} service instance should connect to.
 
-1. Select the {{site.data.keyword.Bluemix_notm}} `Organization` where the {{site.data.keyword.dashdbshort_notm}} service instance exists.
+**Note:** If you already have a {{site.data.keyword.dashdbshort_notm}} for Analytics: Enterprise for Transactions service instance, you can configure to use the same to connect to the {{site.data.keyword.mobilefoundation_short}} service instance.
+
+You can also create a new {{site.data.keyword.dashdbshort_notm}} for Transactions service instance, if you do not have one already existing.
+
+Follow the steps below to create a new dashDB for Transactions service instance:
+
+1. In the *Overview* page select **Create New Service** section.
 
-+ Select the {{site.data.keyword.Bluemix_notm}} `Space` where the {{site.data.keyword.dashdbshort_notm}} service instance exists, from the list of spaces available in the selected `Organization`.
++ Select `Yes` on the **High availability configuration** option, if you want high available {{site.data.keyword.dashdbshort_notm}} for Transactions service instance.
 
-**Note:** If you do not see listed the `Organization` and `Space` where your {{site.data.keyword.dashdbshort_notm}} service instance exists then check if you are a member of that `Organization` and `Space`.
++ Review the plan details and click **Create**.
+
+A new {{site.data.keyword.dashdbshort_notm}} for Transactions: EnterpriseForTransactions2.8.500 service instance is created, which provides a dedicated {{site.data.keyword.dashdbshort_notm}} instance with 8GB RAM and 2 vCPUs, and 500 GB of storage.
+
+Follow the steps below to connect to an existing {{site.data.keyword.dashdbshort_notm}} service instance or to the {{site.data.keyword.dashdbshort_notm}} for Transactions service instance that you just created:
+
+1. Select the {{site.data.keyword.Bluemix_notm}} `Organization` where the {{site.data.keyword.dashdbshort_notm}} service instance exists.
+
++ Select the {{site.data.keyword.Bluemix_notm}} `Space` where the {{site.data.keyword.dashdbshort_notm}} service instance exists, from the list of spaces available in the selected `Organization`.   
+**Note:** If you do not see listed the `Organization` and `Space` where your {{site.data.keyword.dashdbshort_notm}} service instance exists then check if you are a member of that `Organization` and `Space`. You are required to have a *Developer* role access to the organization and space, as the {{site.data.keyword.mobilefoundation_short}} service accesses the credentials from the {{site.data.keyword.dashdbshort_notm}} service.
 
 + Select the {{site.data.keyword.dashdbshort_notm}} `Service Name` and `Credentials` to connect to the existing  {{site.data.keyword.dashdbshort_notm}} service instance.
 
-+  Test the connection to the specified {{site.data.keyword.dashdbshort_notm}}: Enterprise Transactional service instance.
++  Test the connection to the specified {{site.data.keyword.dashdbshort_notm}} service instance.
 
 +  Click **Add**. This action creates the required tables in the configured {{site.data.keyword.dashdbshort_notm}} database service instance.
 
-**Note**: You cannot change the {{site.data.keyword.dashdbshort_notm}} service instance that is configured to be used by your {{site.data.keyword.mobilefoundation_short}} service instance. However, you can use the same {{site.data.keyword.dashdbshort_notm}} service instance across multiple {{site.data.keyword.mobilefoundation_short}} service instances, as each {{site.data.keyword.mobilefoundation_short}} service instance creates its own schema in the selected {{site.data.keyword.dashdbshort_notm}} service instance.
+In a few seconds, you can access the `Overview` page that provides you with  tutorials and videos to help you get started with the  {{site.data.keyword.mobilefoundation_short}} service.
 
-* In a few seconds, you can access the `Overview` page that provides you with  tutorials and videos to help you get started with the  {{site.data.keyword.mobilefoundation_short}} service.
+**Note**: You cannot change the {{site.data.keyword.dashdbshort_notm}} service instance that is configured to be used by your {{site.data.keyword.mobilefoundation_short}} service instance. However, you can use the same {{site.data.keyword.dashdbshort_notm}} service instance across multiple {{site.data.keyword.mobilefoundation_short}} service instances, as each {{site.data.keyword.mobilefoundation_short}} service instance creates its own schema in the selected {{site.data.keyword.dashdbshort_notm}} service instance.
 
 ## Starting the {{site.data.keyword.mobilefirst}} server
 {: #start_mobilefoundation_p3}
@@ -85,7 +100,7 @@ The process of provisioning your server starts. This process takes about 10 minu
 
  Users can also attach volumes to the containers to persist data. The volume once selected cannot be changed. 20 GB is the default file share space available to the user. If the user needs additional storage space to persist analytics data, he is required to buy additional file share and create a volume using this file share. He can then select this new volume while deploying the analytics server.
 
- For more information on adding volumes to {{site.data.keyword.containerlong}}, refer to [Storing persistent data in a volume by using the {{site.data.keyword.Bluemix_notm}} Dashboard  ](https://www.bluemix.net/docs/containers/container_volumes_ui.html){: new_window}.
+ For more information on adding volumes to {{site.data.keyword.containerlong}}, refer to [Storing persistent data in a volume by using the {{site.data.keyword.Bluemix_notm}} Dashboard](https://console.ng.bluemix.net/docs/containers/container_volumes_ui.html){: new_window}.
 
 * Click **Add Analytics** to add the Mobile Analytics server to the {{site.data.keyword.mobilefoundation_short}} service instance.
 
@@ -101,6 +116,15 @@ For more information on MobileFirst Analytics, you can refer to [MobileFirst Fou
 
 **Note:** The Mobile Analytics server is removed when you delete the {{site.data.keyword.mobilefoundation_short}} service instance or when you attempt to re-create the {{site.data.keyword.mfserver_short_notm}}.
 
+##  Deleting Mobile Analytics server
+{: #deleting_analytics_server_p3}
+
+You can now delete the Mobile Analytics server that was added to the {{site.data.keyword.mobilefoundation_short}} service instance, from the {{site.data.keyword.mobilefoundation_short}} service dashboard.
+
+* Click **Delete Analytics** to delete the  Mobile Analytics server that has been added to the {{site.data.keyword.mobilefoundation_short}} service instance.
+
+ This will delete the analytics container group. The process of deleting analytics containers takes about 10 minutes. You can refresh the screen to view the updated status. Once the analytics containers are deleted, the **Add Analytics** button is re-enabled, you can use this to add the Mobile Analytics server again if you choose to.
+
 ## Re-creating the {{site.data.keyword.mobilefirst}} server
 {: #recreate_mobilefoundation_p3}