Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Administration and Development Process Flow

Updated: November 21, 2013

Getting Started

When working with Windows Azure BizTalk Services, there are several on-premise and cloud-based components to consider. To get started, consider the following process flow:

  1. Administrator task: Create the Windows Azure Subscription using the Windows Azure Management Portal.

    When the BizTalk Service is provisioned, the following requirements are automatically created:

    • Windows Azure SQL Database

    • Windows Azure Access Control namespace (ACS)

    • Windows Azure Storage Account

    BizTalk Services: Provisioning Using Windows Azure Management Portal provides information on the components used by a BizTalk Service deployment.

  2. Administrator task: When the Windows Azure requirements are created, provision a BizTalk Service on the Windows Azure Management Portal using the steps at BizTalk Services: Provisioning Using Windows Azure Management Portal.

    When you provision a BizTalk Service, you also select the edition that meets your needs. BizTalk Services: Developer, Basic, Standard and Premium Editions Chart compares the differences with the editions.

  3. Administrator task: Register you or your company’s BizTalk Service deployment. After the BizTalk Service is provisioned, open the Windows Azure BizTalk Services Portal and add your BizTalk Service deployment details, including the ACS Issuer Name and Issuer Key.

    The steps to register your BizTalk Service are available at Registering and Updating a BizTalk Service Deployment on the BizTalk Services Portal.

  4. Administrator task: If the developer uses BizTalk Adapter Service to connect to an on-premise Line-of-Business (LOB) system or uses a Queue or Topic Destination, then a Windows Azure Service Bus Namespace, Windows Azure Service Bus Issuer Name, and Windows Azure Service Bus Issuer Key are needed.

    On the Windows Azure Management Portal, create the Windows Azure Service Bus Namespace using the steps at How to: Create or Modify a Service Bus Service Namespace. You can retrieve the Windows Azure Service Bus Issuer Name and Windows Azure Service Bus Issuer Key using the steps at BizTalk Services: Issuer Name and Issuer Key.

  5. Developer task: On the Development computer, create the BizTalk Service project in Visual Studio:

    1. Run the Windows Azure BizTalk Services setup. The Developer SDK setup option includes the Visual Studio to create the BizTalk Service project. Install Windows Azure BizTalk Services SDK lists the steps.

    2. Install the BizTalk Adapter Service. If your application uses a Line-Of-Business (LOB) system, then install BizTalk Adapter Service. Install Windows Azure BizTalk Services SDK lists the steps.

    3. In Visual Studio, create the BizTalk Service project with a bridge.

      Rich Messaging Endpoints describes the bridge and Configure Rich Messaging Endpoints on Windows Azure lists the steps to create a bridge.

    4. In Visual Studio, create the Transform to manipulate your message data.

      Message Transforms guides you in creating a separate BizTalk Service Artifacts (Transform) project or adding a Transform to a BizTalk Service project.

    5. Use the BizTalk Adapter Service to connect to an on-premise LOB system. Using the BizTalk Adapter Pack, you create a LOB Target to query the on-premise LOB system from your BizTalk Service project.

      BizTalk Adapter Service provides more information on the Development and Runtime components and the steps to connect to your on-premise LOB system.

  6. Developer task: On the Development computer, deploy your BizTalk Service project to your BizTalk Service hosted on Windows Azure.

    Deploying the BizTalk Service Project lists the details to deploy your BizTalk Service project.

  7. Administrator task: If you are using EDI, you can add Partners and create Agreements on the Windows Azure BizTalk Services Portal. When you create an Agreement, you can add the bridge and/or Transforms created by the developer to your Agreement settings.

    Business to Business Messaging provides information on EDI and provides links to adding partners and creating agreements in the BizTalk Services Portal.

  8. Administrator task: Using the Windows Azure Management Portal, monitor the health of your BizTalk Service, including performance metrics.

    BizTalk Services: Dashboard, Monitor and Scale tabs describes the performance metrics.

  9. Administrator task: Using the Windows Azure BizTalk Services Portal, manage the artifacts used by BizTalk Services and track messages as they are processed by the bridge files. For more information, see Using the BizTalk Services Portal.

  10. Administrator task: Create a backup plan to back up the BizTalk Service. For more information, see Business Continuity in BizTalk Services.

Next

See Also

© 2013 Microsoft Corporation. All rights reserved.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.