Skip to content

Commit

Permalink
Merge pull request #4671 from Azure/DailyPub
Browse files Browse the repository at this point in the history
Daily pub
  • Loading branch information
pcw3187 committed Sep 8, 2014
2 parents 45ac5bd + c2f6f9e commit 82e02e0
Show file tree
Hide file tree
Showing 8 changed files with 32 additions and 9 deletions.
1 change: 0 additions & 1 deletion articles/integration-hybrid-connection-create-manage.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,6 @@ To manage your Hybrid Connections, you can:

- Use the Azure portal and go to your BizTalk Service.
- Use [REST APIs](http://msdn.microsoft.com/library/azure/dn232347.aspx).
<!-- - Use Windows PowerShell cmdlets **INSERT LINK**. -->

####Copy/regenerate the Hybrid Connection Strings

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ To complete this tutorial, you need the following:

[WACOM.INCLUDE [mobile-services-dotnet-backend-create-new-service-vs2013](../includes/mobile-services-dotnet-backend-create-new-service-vs2013.md)]

<ol start="8"><li><p>In Solution Explorer, open the App.xaml.cs code file in the GetStartedWithData.Shared project folder, and notice the new static field that was added to the <strong>App</strong> class inside a Windows Store app conditional compilation block, which looks like the following example:</p>
<ol start="7"><li><p>In Solution Explorer, open the App.xaml.cs code file in the GetStartedWithData.Shared project folder, and notice the new static field that was added to the <strong>App</strong> class inside a Windows Store app conditional compilation block, which looks like the following example:</p>

<pre><code>public static Microsoft.WindowsAzure.MobileServices.MobileServiceClient
todolistClient = new Microsoft.WindowsAzure.MobileServices.MobileServiceClient(
Expand Down
3 changes: 2 additions & 1 deletion articles/storage-monitoring-diagnosing-troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,9 +77,10 @@ The section "[Troubleshooting guidance]" provides troubleshooting guidance for s

The "[Appendices]" include information about using other tools such as Wireshark and Netmon for analyzing network packet data, Fiddler for analyzing HTTP/HTTPS messages, and Microsoft Message Analyzer for correlating log data.


## <a name="monitoring-your-storage-service"></a>Monitoring your storage service

If you are familiar with Windows performance monitoring, you can think of Storage Metrics as being an Azure Storage equivalent of Windows Performance Monitor counters. In Storage Metrics you will find a comprehensive set of metrics (counters in Windows Performance Monitor terminology) such as service availability, total number of requests to service, or percentage of successful requests to service (for a full list of the available metrics, see <a href="http://msdn.microsoft.com/en-us/library/azure/hh343264.aspx" target="_blank">Storage Analytics Metrics Table Schema</a> on MSDN). You can specify whether you want the storage service to collect and aggregate metrics every hour or every minute. For more information about how to enable metrics and monitor your storage accounts, see <a href="http://go.microsoft.com/fwlink/?LinkId=510865/" target="_blank">Enabling storage metrics</a> on MSDN.
If you are familiar with Windows performance monitoring, you can think of Storage Metrics as being an Azure Storage equivalent of Windows Performance Monitor counters. In Storage Metrics you will find a comprehensive set of metrics (counters in Windows Performance Monitor terminology) such as service availability, total number of requests to service, or percentage of successful requests to service (for a full list of the available metrics, see <a href="http://msdn.microsoft.com/en-us/library/azure/hh343264.aspx" target="_blank">Storage Analytics Metrics Table Schema</a> on MSDN). You can specify whether you want the storage service to collect and aggregate metrics every hour or every minute. For more information about how to enable metrics and monitor your storage accounts, see <a href="http://go.microsoft.com/fwlink/?LinkId=510865" target="_blank">Enabling storage metrics</a> on MSDN.

You can choose which hourly metrics you want to display in the Azure portal and configure rules that notify administrators by email whenever an hourly metric exceeds a particular threshold (for more information, see the page <a href="http://msdn.microsoft.com/library/azure/dn306638.aspx" target="_blank">How to: Receive Alert Notifications and Manage Alert Rules in Azure</a>). The storage service collects metrics using a best effort, but may not record every storage operation.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,27 @@ To use an on-premises SQL Server or SQL Server Express database with a hybrid co

The computer on which you install the on-premises Hybrid Connection Manager agent:

- Must be able to connect to Azure over port 5671
- Must have outbound connectivity to Azure over:

> <table border="1">
<tr>
<th><strong>Port</strong></th>
<th>Why</th>
</tr>
<tr>
<td>80</td>
<td><strong>Required</strong> for HTTP port for certificate validation and optionally for data connectivity.</td>
</tr>
<tr>
<td>443</td>
<td><strong>Optional</strong> for data connectivity. If outbound connectivity to 443 is unavailable, TCP port 80 is used.</td>
</tr>
<tr>
<td>5671 and 9352</td>
<td><strong>Recommended</strong> but Optional for data connectivity. Note this mode usually yields higher throughput. If outbound connectivity to these ports is unavailable, TCP port 443 is used.</td>
</tr>
</table>
- Must be able to reach the *hostname*:*portnumber* of your on-premises resource.

The steps in this article assume that you are using the browser from the computer that will host the on-premises hybrid connection agent.
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
10 changes: 6 additions & 4 deletions includes/mobile-services-dotnet-backend-create-custom-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@
4. Add the following code to the new controller:

// POST api/completeall
public Task<int> Post()
public async Task<int> Post()
{
using (todolistContext context = new todolistContext())
{
Expand All @@ -31,9 +31,9 @@

// Create a SQL statement that sets all uncompleted items
// to complete and execute the statement asynchronously.
var sql = @"UPDATE TodoItems SET Complete = 1 " +
var sql = @"UPDATE todolistService.TodoItems SET Complete = 1 " +
@"WHERE Complete = 0; SELECT @@ROWCOUNT as count";
var result = database.ExecuteSqlCommandAsync(sql);
var result = await database.ExecuteSqlCommandAsync(sql);

// Log the result.
Services.Log.Info(string.Format("{0} items set to 'complete'.",
Expand All @@ -43,7 +43,9 @@
}
}

In the above code, replace `todolistContext` with the name of the DbContext for your data model, which should be the mobile service name appended with `Context`. This code uses the [Database Class](http://msdn.microsoft.com/en-us/library/system.data.entity.database.aspx) to access the **TodoItems** table directly to set the completed flag on all items. This method supports a POST request, and the number of changed rows is returned to the client as an integer value.
In the above code, replace `todolistContext` with the name of the DbContext for your data model, which should be the mobile service name appended with `Context`. Also replace the schema name in the UPDATE statement with the name of your mobile service.

This code uses the [Database Class](http://msdn.microsoft.com/en-us/library/system.data.entity.database.aspx) to access the **TodoItems** table directly to set the completed flag on all items. This method supports a POST request, and the number of changed rows is returned to the client as an integer value.

> [WACOM.NOTE] Default permissions are set, which means that any user of the app can call the custom API. However, the application key is not distributed or stored securely and cannot be considered a secure credential. Because of this, you should consider restricting access to only authenticated users on operations that modify data or affect the mobile service.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,8 @@ The previous example showed a standard sign-in, which requires the client to con
1. In the MainPage.xaml.cs project file, add the following **using** statements:

using Windows.Security.Credentials;
using System.Linq;
using Windows.Security.Credentials;

2. Replace the **AuthenticateAsync** method with the following code:

Expand Down

0 comments on commit 82e02e0

Please sign in to comment.