none
Connector for WebServices and Web Service Configuration Tool RRS feed

  • Question

  • I am trying to play around with the Web Service Configuration Tool. I know that it only officially supports Oracle, Sap, and Ps but has anyone else had any luck with other web service based systems? When I use the configuration tool to create an import workflow the "web service call" activity doesn't contain anything in the drop down boxes. The discovered service, endpoint, etc are all blank.

    Is there something else that needs to be configured?

    Saturday, September 15, 2012 11:57 PM

Answers

  • Please feel free to get in touch regarding licensing, as the Salesforce MA is priced to be very affordable relative to the core SFDC Professional and Enterprise platform.  (If you're a non-profit, governmental, or academic institution, MA pricing would effectively scale proportionally to SFDC itself.)  Even if you're set on writing one from scratch, we'd love to have your input on this.

    • Marked as answer by B3NT_0 Monday, November 26, 2012 4:13 PM
    Wednesday, September 19, 2012 5:17 PM

All replies

  • If it helps I'm using the enterprise WSDL from SalesForce and this was the error from the config tool:

    2012-09-15T20:24:15 [4120:6212] Error   - Workspace:PrepareDiscovery : The Enumeration constraining facet is invalid - 'fns' is an undeclared prefix.
    --------- Outer Exception Data ---------
    Message: The Enumeration constraining facet is invalid - 'fns' is an undeclared prefix.
    Exception root Exception type: System.Xml.Schema.XmlSchemaException
    Source: System.Xml
    Stack Trace:    at System.Xml.Schema.XmlSchemaSet.InternalValidationCallback(Object sender, ValidationEventArgs e)
       at System.Xml.Schema.Compiler.CompileSimpleType(XmlSchemaSimpleType simpleType)
       at System.Xml.Schema.Compiler.Compile()
       at System.Xml.Schema.Compiler.Execute(XmlSchemaSet schemaSet, SchemaInfo schemaCompiledInfo)
       at System.Xml.Schema.XmlSchemaSet.Compile()
       at System.Xml.Serialization.XmlSchemas.Compile(ValidationEventHandler handler, Boolean fullCompile)
       at Microsoft.IdentityManagement.MA.WebServices.WebServices.ServiceDescriptionProvider.Initialize(Boolean downloaded)
       at Microsoft.IdentityManagement.MA.WebServices.WebServices.ServiceDescriptionProvider..ctor(XmlNode serializedNode)
       at Microsoft.IdentityManagement.MA.WebServices.WebServices.WsdlDiscovery..ctor(XmlReader reader)
       at Microsoft.IdentityManagement.MA.WebServices.ConfigurationTool.Misc.Workspace.PrepareDiscovery(String discovery)
    Target Site: InternalValidationCallback
     --------- Inner Exception Data ---------
     Message: 'fns' is an undeclared prefix.
     Exception root Exception type: System.Xml.XmlException
     Source: System.Xml
     Stack Trace:    at System.Xml.Schema.Datatype_QName.TryParseValue(String s, XmlNameTable nameTable, IXmlNamespaceResolver nsmgr, Object& typedValue)
     Target Site: TryParseValue

    Anyone have a workaround? BTW, this would have been a great tool to open source...hint, hint, nudge, nudge.


    • Edited by B3NT_0 Sunday, September 16, 2012 12:27 AM
    Sunday, September 16, 2012 12:26 AM
  • Wow. The silence is deafening.

    I'm currently developing an ECMA 2.0 connector for SalesForce, but the webservice connector would be a better way to go. Having looked over the default projects for some of the other systems that shipped with it, I really like the approach that was taken.

    Monday, September 17, 2012 6:39 PM
  • I'm in the same boat. I'm going to have to talk with Axapta pretty soon and I'm still wondering whether going ECMA 2.O or this webservice connector.

    I'll definately give the webservice connector a chance. Whilst it might seem "fun" coding an ECMA, if there's a framework out there...


    http://setspn.blogspot.com

    Monday, September 17, 2012 9:06 PM
  • For Salesforce and FIM, I'd direct you to take a look at Zetetic's Management Agent for Salesforce.  There are many aspects to the Salesforce API, including but not limited to special requirements for authentication, paging, special datatypes, custom XML-based updates, etc., that are incompatible with the generic webservice MA.
    Tuesday, September 18, 2012 3:02 AM
  • I actually looked at that, but the licensing is prohibitive for us.

    Yeah, Salesforce has been a real challenge. It seems counter-intuitive to me in a lot of ways. Not being able to delete users being the biggest one. 

    I have gotten to the point where I have a solid working ECMA 2.0 MA for User objects. I gave up on trying to take a generic approach that might be applicable to more scenarios and ended up just coding it directly for our scenario. I would like to open source it and get input from other devs that have more experience with SF. I'm waiting on permission for that right now. It's not likely, but hey...it was worth a shot.

    Wednesday, September 19, 2012 1:54 PM
  • Please feel free to get in touch regarding licensing, as the Salesforce MA is priced to be very affordable relative to the core SFDC Professional and Enterprise platform.  (If you're a non-profit, governmental, or academic institution, MA pricing would effectively scale proportionally to SFDC itself.)  Even if you're set on writing one from scratch, we'd love to have your input on this.

    • Marked as answer by B3NT_0 Monday, November 26, 2012 4:13 PM
    Wednesday, September 19, 2012 5:17 PM
  • Hi,

    Did you ever get this working? I am facing difficulties getting it to work with even a very simple web service scenario. Please let me know. Thanks.

    Ali

    Tuesday, May 14, 2013 9:11 AM
  • Hi,

    I tried this to connect with Workday [HR SaaS App], and was able to connect and get the Workday API/Methods, but I'm having issues with the Full Import/Export Configuration section where it shows me that Add-In components not found. I opened a case with Microsoft to resolve this. Once it is fixed i can complete the web service project and can try via Web Service Connector.

    Tuesday, May 14, 2013 8:41 PM
  • Having done a couple of Workday integrations, I would not expect the out-of-the-box Web Service Connector to be a good match; there are special technical requirements for Workday's HTTP binding, and the Workday API itself is largely a mirror of the system's complex XML structures.

    Steve Kradel, Zetetic LLC

    Tuesday, May 14, 2013 8:47 PM
  • Thanks for the update. I think I may end up contacting Microsoft as well. 
    Wednesday, May 15, 2013 6:30 AM
  • Steve, you are right. Workday native APIs are complex and requires custom bindings, custom object and types. we built FIM custom Workflows to transact the data. we also have few custom workday APIs for reporting , data extract which are straight forward, and am trying to experiment that with OOTB web service connectors.

    Thursday, May 16, 2013 12:13 AM