What's new in Service Bus 1.0
Mar 5, 2013
- New default HTTP Port for the Service Bus for Windows Server: the default HTTP port used by the Service Bus for Windows Server has been changed to 9355 (from 4446). Make sure to modify your applications accordingly.
- New helper class to build a Service Bus connection string: The Windows Azure SDK 1.7 introduced a way to connect to the Service Bus using connection strings. In order to match the cloud API, this release includes a new class to help build the Service Bus connection string. For more information, see see the Developing an Application section.
- New format for the Service Bus connection string: In order to connect to the Service Bus (either cloud or on-premises), use the connection string in a configuration file similar to the API in the Windows Azure SDK. For more information, see see the Developing an Application section.
- The Service Bus for Windows Server PowerShell cmdlets now use connection strings to configure databases. For more information, see the Service Bus for Windows Server PowerShell cmdlets reference
- The Service Bus for Windows Server now has a configuration wizard. You can use the Service Bus for Windows Server configuration wizard to perform basic operations, such as creating a farm and joining and leaving existing farms.
- The Service Bus for Windows Server now has support for SQL Authentication in addition to Windows Authentication.
- You can now host the Service Bus for Windows Server in a Windows Azure VM (IaaS) using SQL Server or SQL Database.
- A new System Center Management pack is now available for downloading.