locked
BizTalk Logic App Adapter Configuration RRS feed

Answers

  • I am very sorry for the inconvenience of the issue, I have updated our documentation to reflect the changes in the RTM build (I just did and it does take some time for the documentation to be updated).

    the old BizTalkWcfService is now called ReceiveService and BizTalkManagementService is now called Management.

    Please follow the following article:

    https://msdn.microsoft.com/en-us/library/mt787163.aspx

    Best regards,

    Tord Glad Nordahl
    Program Manager BizTalk

    Monday, January 9, 2017 11:56 PM

All replies

  • Hi, 

    I am also facing the same issue today. I have created a BizTalk Server 2016 Azure VM which now has the GA verison of BTS 2016. 

    1.Installed and configured On-premises data gateway successfully
    2.Installed the Logic App Adapter which created following folders under C:\Program Files (x86)\Microsoft BizTalk Server 2016\LogicApp Adapter
        - Management
        - ReceiveService

    Now as per the doumentation (https://msdn.microsoft.com/en-us/library/mt787163.aspx)
    when I try to create IIS applications to use the BizTalkManagementService and BizTalkWcfService services I don't find these named folder any more.
    So I used   C:\Program Files (x86)\Microsoft BizTalk Server 2016\LogicApp Adapter\Management instead of  C:\Program Files (x86)\Microsoft BizTalk Server 2016\LogicApp Adapter\BizTalkManagementService to set the physical path.

    But this seems there is something missing in GA as when I am trying to browse schemas (http://localhost/YourApplicationAlias/schemas) I get the error - HTTP 404 Not Found. 

    This was working in CTP version of Logic App Adapter - https://social.technet.microsoft.com/wiki/contents/articles/36001.hybrid-integration-with-logic-apps-and-biztalk-server-2016.aspx 

    Thanks!
    Gautam



    Thanks! Regards, Gautam

    Thursday, January 5, 2017 10:26 AM
  • Hi Gautam and Jozef,

    I think issue is with Logic App configuration and on-premises BizTalk instance . 

    I can see that you are unable to browse the schema with 404 error after you set up IIS for Management service . You can try http://MyHostName/IISLogicApp/schemas?api-version=2016-10-26.

    Thanks

    Abhishek


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply


    Friday, January 6, 2017 1:59 AM
  • I am very sorry for the inconvenience of the issue, I have updated our documentation to reflect the changes in the RTM build (I just did and it does take some time for the documentation to be updated).

    the old BizTalkWcfService is now called ReceiveService and BizTalkManagementService is now called Management.

    Please follow the following article:

    https://msdn.microsoft.com/en-us/library/mt787163.aspx

    Best regards,

    Tord Glad Nordahl
    Program Manager BizTalk

    Monday, January 9, 2017 11:56 PM
  • Something else is wrong. I also receive 404 even if apppool identity is member of BizTalk Isolated hosts group.


    Antti

    Tuesday, January 10, 2017 2:55 PM
  • Hi!

    I have the same problem as Antti. I can't get the Management service to work.

    The Biztalk Logic App Adapter download page says:  

    Supported Operating System

    Windows Server 2016

    Microsoft BizTalk Server 2016

    Is that correct? I'm using Windows 10. Could this be the cause of my problem?

    /Johan

    Tuesday, January 10, 2017 4:09 PM
  • Hi,

    Also just set this up according to the articles and browsing to the Management service "/schemas" for example just returns a 404.

    Richard




    http://www.richardhallgren.com


    Wednesday, January 11, 2017 6:52 AM
  • Rickard, which Windows version are you using?

    Wednesday, January 11, 2017 8:42 AM
  • Windows Server 2016

    http://www.richardhallgren.com

    Wednesday, January 11, 2017 10:16 AM
  • Got this working now. Adding "

    ?api-version=2016-10-26" to the url did it. Thanks


    http://www.richardhallgren.com

    Wednesday, January 11, 2017 12:00 PM
  • Hi Richard ,

    I will be update the technet wiki and see how it goes . Now you can browse the schema with http://localhost/IISLogicApp/schemas?api-version=2016-10-26 by appending the api version


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply

    Wednesday, January 11, 2017 12:08 PM
  • Hi All,

    I have tried this and can confirm the logic App adapter is working .i can browse the schema from BizTalk sitting on-premise . 

    Thank

    Abhishek


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply

    Wednesday, January 11, 2017 3:21 PM
  • Hi All!

    I'm now also able to browse the Biztalk schemas with the URL: http://MyHostName/IISLogicApp/schemas?api-version=2016-10-26. Thanks!

    But I still have problems using this URL to browse the schemas from my Logic App. I get:

    Could not retrieve values. Error: IIS 10.0 Detailed Error - 404.0 - Not Found

    I'm able to sucessfully run the Logic App in the example after having manually entered the schema name and the receive URL. So I have a good connection with the On Premises Gateway and the message is successfully sent to Biztalk.

    My On Premises host is running Windows 10.

    Any thoughts on possible causes to this error?

    /Johan

    Wednesday, January 11, 2017 6:24 PM
  • Hi Johan,

    Can you tell step by step process how you are trying to configure On-premise DataGateway in Azure .

    Based on your step I can able to suggest what is missing 


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply

    Thursday, January 12, 2017 12:38 AM
  • Hi!

    I configured my On-Premises DataGateway exactly as described here: https://docs.microsoft.com/sv-se/azure/app-service-logic/app-service-logic-gateway-connection

    When specifying the URL of the API Connection I used: http://johans_mbp/IISLogicApp/schemas?api-version=2016-10-26. johans_mbp is my hostname.

    Authentication is set to: Windows

    When specifying the username of the API Connection I used the format <hostname>\<application pool account>. Eg. myhost\BizTalk. This seem to work since the gateway successfully calls the receive service that deliver the message to Biztalk.

    The on premises gateway is running under account: NT SERVICE\PBIEgwService

    As I said, everything except for the schema and receive port browsing is working fine.

    Is there a way to test the On premises gateway locally?

    Thursday, January 12, 2017 10:24 AM
  • Hi Johan ,

    Please find the changes which you need to do :

    • Configure proper connection with your On-premise Data gateway with url properties and userId and password.

    • On IIS Side modify the authentication scheme to use windows authentication 

    • Next built your sample Logic Apps using BizTalk connectors and verify the run .I have done it again now 

    • In my case i was using postman to test the service through HTTP,you can use another available connectors as well

    Hope this thread will clear now to configure Logic App adapter receive location to get request from logic Apps workflow.


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply

    Friday, January 13, 2017 2:46 AM
  • Hi Abhishek!

    It's working! I thought I had to append "schemas?api-version=2016-10-26" to the BIZTALK SERVER URL when configuring the API Connection. After removing it everything is working fine. Didn't realize the gateway would append to the URL.

    Thank you Abhishek!

    Friday, January 13, 2017 2:51 PM