Has anyone had success with triggering a workbench on server using SOAP? We are replicating an Oracle database using Informatica Power Exchange. For any spatial table, Power Exchange is going to send parameters to FME server to do the replication. I know you can do this with REST, but from the Informatica side it seems easier to do with SOAP, so I was curious if anyone had any luck.
Question
Using SOAP to run workbench
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+2Hi @colleenk_1
We don't have a SOAP API, so you would have to use REST or if you're just triggering a workspace to run, you could use the direct url.
You can find examples of how to do this via REST here.
I'll just add that SOAP is an old protocol that's fairly rapidly being replaced by simpler and more efficient protocols such as REST. I think it's safe to say that very few, if any, new services are developed using SOAP today.
For any new projects I'd try hard to avoid using SOAP, whenever possible.
Instruction on how to enable SOAP on FME Server 2017.
And 2018:
Instruction on how to enable SOAP on FME Server 2017.
And 2018:
Interesting, never seen that before. The documentation says "this is not a user-oriented service that delivers translation results." -- can you still use it to run workspaces though?
<xsd:element name="submitJob">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="subsection" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="workspacePath" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="publishedParameters" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="fmeEngineDirectives" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="transformationManagerDirectives" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Yes, there is the submitJob request for that:
<xsd:element name="submitJob">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="subsection" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="workspacePath" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="publishedParameters" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="fmeEngineDirectives" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="transformationManagerDirectives" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Cool, thanks for sharing!
Just to let you know, this is no longer available in 2018+. We've put in a request to remove it from the docs to avoid confusion.