none
Calling an RFC RRS feed

  • Question

  • Is it possible, using the adapter pack, to create a web service that allows users to call BAPI or RFC's by passing in the name of the RFC or BAPI (along with parameters) that they would like to call?

     

    If have created an orchestration that calls an RFC that is known at design time by generating the schema.  But what I need to do is call an RFC that is not known.

     

    It seems that this post is touching on what I need to do, however I need a more complete idea on how to accomplish this.

     

    Thanks.

    Tuesday, January 22, 2008 6:20 PM

Answers

  • Hi!

    The proxies and schemas generated are just "helpers" - the proxy allows you to pass in .NET objects, and WCF takes care of the serialization; the schemas in BizTalk are present so that you can use BizTalk to perform some basic schema validation. The disadvantage of both (which you have figure out) is that the RFC name needs to be know at design time.

    You can always ignore schema validation in BizTalk, and just send XML messages directly to the Send Port. As long as the Action property is initialized correctly, and the XML format in your message is correct (as the adapter expects it), you should be fine. You will ofcourse lose the ability for BizTalk to validate your message against the schema, since you don't have a schema.
    Saturday, January 26, 2008 7:29 AM

All replies

  • At least if you know the RFC at runtime then you can create dynamic proxy or wsdl to execute the webservice. Just clarify when do you know the RFC name?

    Thanks

    Taruna

     

    Wednesday, January 23, 2008 3:29 PM
  • Yes, they know the RFC name at runtime.

    Wednesday, January 23, 2008 6:54 PM
  • You can view my post how to generate dynamic proxy:

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2646369&SiteID=1

     

    Thursday, January 24, 2008 2:49 AM
  • Hi!

    The proxies and schemas generated are just "helpers" - the proxy allows you to pass in .NET objects, and WCF takes care of the serialization; the schemas in BizTalk are present so that you can use BizTalk to perform some basic schema validation. The disadvantage of both (which you have figure out) is that the RFC name needs to be know at design time.

    You can always ignore schema validation in BizTalk, and just send XML messages directly to the Send Port. As long as the Action property is initialized correctly, and the XML format in your message is correct (as the adapter expects it), you should be fine. You will ofcourse lose the ability for BizTalk to validate your message against the schema, since you don't have a schema.
    Saturday, January 26, 2008 7:29 AM