Connect to Siebel eBusiness Applications in a BizTalk Services Project


Updated: December 7, 2015


Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.

If you're brand new to Logic Apps, then we suggest getting started here:

There are three overall steps to connect to Siebel eBusiness Suite from a BizTalk Services project.

  • Create an LOB Target for Siebel eBusiness Suite.

    • To create an LOB Target for Siebel, you must be a member of the local Administrators group and have the System Administrator right on the on-premises Siebel system.

    • Visual Studio must be opened with Administrative privileges to use BizTalk Adapter Service.

  • Use the LOB Target

  • Generate schema for the operation to be performed on the Siebel application.


These steps assume you have a Service Bus namespace. Install Azure BizTalk Services SDK lists the requirements.

To add an LOB Target for Siebel eBusiness Application

  1. In Server Explorer, expand BizTalk Adapter Service, expand the Management URL, and then expand LOB Types.

  2. Right-click Siebel and select Add Siebel Target. The Add a Target wizard opens:

    1. In the Welcome window, select Next.

    2. In Connection Parameters, enter the following:

      • Siebel Gateway: The Siebel server name and optionally, the port number. If the port number is not entered, port 2321 is used. To use a different port, enter ComputerName:PortNumber.

      • Siebel Object Manager: The Siebel object manager on the enterprise server.

      • Siebel Enterprise Server: The Siebel Enterprise Server.

      • Advanced: Select this button to configure additional Connection Properties and any Binding Properties:


        Optional. The compression algorithm to use between the Siebel adapter and the Siebel system. Default is zlib. Supported values include:

        • none

        • zlib


        Optional. The type of encryption to use between the Siebel adapter and the Siebel system. Default is none. Supported values include:

        1. none

        2. mscrypto

        3. rsa


        Optional. The object manager language. Default is enu.


        Required. The Siebel Enterprise Server.


        Required. The Siebel server name.


        Required. The Siebel object manager on the enterprise server.


        Required if more than one Siebel repository exists on the server. Otherwise, it is optional.


        If there is more than one repository on the server, you must enter a target repository.


        Required for all Siebel 7.5 server connections. Otherwise, do not set this parameter.


        Optional. Only tcpip is supported. Default is tcpip.

        To configure these Binding Properties, refer to Working with BizTalk Adapter for Siebel Binding Properties.

        The following binding properties are also available:


        Required. Default is False. Options include:


        When setting field values in a business component, fields are not batched.


        When setting field values in a business component, fields are batched.

        The Siebel System Connection URI provides additional information on the Siebel adapter.

      • Specify the credentials: Enter the credentials to authenticate to the on-premises Siebel system. Options include:

        Use Windows Credentials

        The logged on user credentials are used to connect to the Siebel system.

        Use the following username and password

        Enter a User name and Password that can connect to the Siebel system.


        Not all options may be available for this LOB adapter.

        Select Next.

    3. In Operations, expand the node, select the database operation, and select the right arrow:

      Configure Siebel URI

      Browsing, Searching, and Retrieving Metadata for Siebel Operations provides additional details on selecting an operation.

      To see the operation’s generated WSDL, select the operation, and select Properties.

      Select Next.

    4. In Runtime Security, enter the security type. This security type determines how the client message is authenticated with the LOB Target. Options include:

      Fixed Username

      Select this option if you are using a username and password created locally on LOB system.

      Custom SOAP Header

      Select this option if you create a custom SOAP header to include the username and password.

      Message Credential

      Select this option if you are including the logon credentials in the WS-Security header of the message.

      Select Next.

    5. In Deployment, choose an existing LOB Relay or create a new LOB Relay.


      A single LOB Relay can be used with multiple LOB Targets. There are restrictions based on the security model. As a best practice, group the same security method in one LOB Relay. For example, use the same LOB Relay to host the LOB Targets that use the Message Credential or Fixed Windows security type.

      To create a new LOB Relay:


      Required. Enter your Service Bus namespace. The namespace name is available in the Azure classic portal.

      Issuer Name

      Required. A valid Service Bus Issuer Name is required.

      Issuer Secret

      Required. A valid Service Bus Issuer Secret key is required.

      Relay Path

      Required. Enter the desired name of the relay path. For example, if you use chose Fixed Windows credential option for Runtime Security, you can enter something like WindowsAuthRelay.

      Target Sub-path

      Required. Enter a sub-path to make this target unique. For example, you can enter GetOrder.

      Target runtime URL

      This is automatically populated with the namespace name, relay path and target sub-path entered. If using the examples above, it is populated with something like:

      Select Next.

    6. Summary shows your configured values. Select Create.

    7. When complete, select Finish. The following activities occur in the background:

      • The LOB Target is created in Server Explorer. It can be disabled, started, and deleted. Its configuration can also be exported.

      • The LOB Target is created as an application in IIS. This application uses the Runtime for this specific LOB Target. Runtime Components: BizTalk Adapter Service describes the IIS components.

To use the LOB Target

  1. Right-click anywhere on the BizTalk Service project design area, select Properties, and update the BizTalk Service URL property to include your BizTalk Services name. This is the name that you entered in Azure classic portal when creating the BizTalk Services.

  2. Set the security property for the relay endpoint:

    1. Right-click the relay endpoint in Server Explorer. and select Properties.

    2. In the Properties grid, select the ellipsis (…) next to the Runtime Security property.

    3. In the Edit Security dialog box, select the security method you want to use, and enter their values.

    4. Select OK.

  3. Drag and drop the LOB Target onto the design area. Note the Entity Name property of the LOB Target. The default value of the property is Relay-Path_target-sub-path.

  4. Open the .config file for the LOB target, which typically has the RelayPath_target-sub-path.config naming convention. Enter the Service Bus issuer name and issuer secret, as shown:

      <sharedSecret issuerName="owner" issuerSecret="issuer_secret" />

    Save changes to the config file.

Once a LOB Target is configured and added to the design area, add a XML One-Way Bridge or a XML Request-Reply Bridge to be the source. Use Connector in the Toolbox to connect the bridge to the LOB Target, similar to the following:

Bridge Connection

Create an XML One-Way Bridge and Create an XML Request-Reply Bridge provide more specific information on the XML bridge and any additional properties that must be configured.


The bridge uses the Relative Address property of the LOB Target to send messages to the on-premises LOB system.

To generate the schema

  1. In the BizTalk Service project, in the Server Explorer, right click the LOB Target you created, and then select Add schemas to <project_name>. The Schema Generation dialog opens.

  2. Enter a file name prefix. This value is prefixed with all the schema files that are generated. You can also enter the folder name under which the schemas are added in the Visual Studio Solution Explorer. The default value for the folder is LOB Schemas.

  3. Select a credential type to generate the schema, provided appropriate values for authentication, and then select OK.

    The schemas are added to the project under the folder name.