EN
Dieser Inhalt ist in Ihrer Sprache leider nicht verfügbar. Im Folgenden finden Sie die englische Version.
Dieser Artikel wurde noch nicht bewertet - Dieses Thema bewerten.

Service Bus EAI and EDI Labs Project System

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

You use the Service Bus EAI and EDI Labs project system to create a part or all of a Service Bus EAI and EDI Labs solution. The core element of any such solution is an Enterprise Application Integration project—a collection of items such as XML bridges, Service Bus Connect component, transforms, and schemas that you can build and deploy to Service Bus.

When you create an Enterprise Application Integration project, you generally include one or more of the components from the following list. These components play specific roles in creating your solution:

  • Bridge Configuration : Bridge Configuration represents a ‘rich messaging endpoint’ on the cloud that processes the message after it is received by a Service Bus endpoint. An Enterprise Application Integration project project typically starts with a Bridge Configuration, which is then connected to other Service Bus entities, denoting a typical message flow. For more information, see The Enterprise Application Integration Project Design Surface.

  • XML bridges: XML bridges are message mediation patterns that process the message as it is relayed by the Service Bus from the client to the destination endpoint. As part of the message mediation, bridges also extract/promote properties that can be used for message routing/processing. The information about the following properties is stored in a bridge config file.

    • Properties that get their values from a message header.

    • Properties that are extracted from a message body, as the message is processed by the XML bridge.

    • Lookup providers that act as the data source from which a message property value can be retrieved, while the message is being processed by the XML bridge.

    For more information, see Message-Processing Bridges

  • Service Bus Connect : Provides connectivity from Service Bus to on-premise LOB applications like SQL Server, SAP, Oracle, Siebel, etc. For more information, see Service Bus Connect.

  • Schemas: A schema describes the structure of an XML document. Schemas exchange information among applications within an organization or among trading partners.

  • Transforms: A transform maps data from one format to another. Transforms present source schemas and destination schemas side-by-side and enable you to define mapping between data elements of different messages. For more information, see Transforms.

Service Bus EAI and EDI Labs Project Templates

When you install Service Bus EAI and EDI Labs, the installation process adds the Service Bus category under the Templates area in the Visual Studio New Project dialog box. The Service Bus category contains the following templates:

 

Project Template Description

Enterprise Application Integration

Use this template to create a new Enterprise Application Integration project project for configuring rich messaging endpoints. The Enterprise Application Integration project template can contain the following project items:

  • Schemas

  • Transforms

EDI Project (artifacts)

Use this template to create a project that contains only the artifacts, namely transforms and schemas. There are a couple of reasons why we have this project type.

  • Firstly, you can use this project type to only create a transform or a schema without having it part of an Enterprise Application Integration project and then later add it to an Enterprise Application Integration project.

  • Secondly, you might need to create a transform or a schema that you want to upload to the TPM portal for creating your agreements.

See Also

© 2011 Microsoft Corporation. All rights reserved.
Fanden Sie dies hilfreich?
(1500 verbleibende Zeichen)
© 2013 Microsoft. Alle Rechte vorbehalten.
facebook page visit twitter rss feed newsletter