{"id":8388,"date":"2020-09-10T14:37:48","date_gmt":"2020-09-10T21:37:48","guid":{"rendered":"https:\/\/minisoft.com\/support\/?p=8388"},"modified":"2020-09-24T11:12:11","modified_gmt":"2020-09-24T18:12:11","slug":"director-endpoint-with-serviceconfiguration","status":"publish","type":"post","link":"https:\/\/c002.minisoft.com\/support\/director-endpoint-with-serviceconfiguration\/","title":{"rendered":"Director Endpoint with ServiceConfiguration (API\/Web Service Call)"},"content":{"rendered":"\n

Please refer to the following post for more details: eFORMz API Management (Developer Resources)<\/a><\/p>\n\n\n\n

There are two primary endpoints available to eFORMz customers. These are the \u2018director\u2019 and \u2018output\u2019 endpoints. For more on the ‘output’ endpoint, consult the following post: Output Endpoint with ServiceConfiguration (API\/Web Service Call)<\/a><\/p>\n\n\n\n

An “endpoint” is one end of a communication channel. When an API interacts with another system<\/a>, the touchpoints of this communication are considered endpoints. For APIs, an endpoint can include a URL of a server or service. The place that APIs send requests and where the resource lives is called an endpoint.<\/p>\n\n\n\n

The \u2018director\u2019 endpoint returns success or failure only. It processes data in the background. The \u2018output\u2019 endpoint processes data during the call and returns the results as part of the web service call. Both of these endpoints can take parameters either through the URL or in the data.<\/p>\n\n\n\n

While the portion of the URL with authentication is encrypted for transmission, many people have policies restricting this practice. Passing the parameters in the data, including authentication, is possible using either XML or JSON. The order or sequence of elements in either format is not relevant to the processing.<\/p>\n\n\n\n

URL<\/h2>\n\n\n\n

http:\/\/localhost:8001\/servlet\/com.minisoft.AppServer.AppServer?APP=com.minisoft.eformz.eFORMzApp<\/p>\n\n\n\n

XML<\/h2>\n\n\n\n
<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<ServiceConfiguration ServiceType=\"director\" Host=\"localhost\" Port=\"9996\" ConfigurationName=\"accessible.cfg\" QueueName=\"Accessible\" NameTemplate=\"data_.xml\" ProcessData=\"true\" UseParmsAsData=\"false\">\n  <InputData usepostdata=\"false\" format=\"XML\" encoding=\"none\">\n    <Data>\n      <AdditionalInfo>\n                <misc>info<\/misc>\n      <\/AdditionalInfo>\n    <\/Data>\n  <\/InputData>\n<\/ServiceConfiguration>\n<\/code><\/pre>\n\n\n\n
JSON<\/h2>\n\n\n\n
{\n    \"ServiceConfiguration\":\n          {\n             \"ServiceType\":\"director\",\n             \"Port\":9996,\n             \"NameTemplate\":\"data_.json\",\n             \"Host\":\"localhost\",\n             \"UseParmsAsData\":false,\n             \"ConfigurationName\":\"accessible.cfg\",\n             \"InputData\":\n             {\n                    \"usepostdata\":false,\n                    \"format\":\"JSON\",\n                    \"Data\":\n                    {\n                          \"AdditionalInfo\":\n                               {\n                               \u201cmisc\u201d:\u201dinfo\u201d\n                               },\n                    },\n                    \"encoding\":\"none\"\n             },\n             \"QueueName\":\"Accessible\",\n             \"ProcessData\":true\n          }\n}\n<\/code><\/pre>\n\n\n\n
References<\/h2>\n\n\n\n
For more details on the eFORMz API, consult the following posts:<\/p>\n\n\n\n
eFORMz API .NET Web Service Call<\/a>
eFORMz API URL Parameters<\/a>
Web Service POST call to \u201cWake Up\u201d a \u201cSleeping\u201d Queue: Part 1<\/a>
Web Service POST call to \u201cWake Up\u201d a \u201cSleeping\u201d Queue: Part 2<\/a>
Web Service POST call to \u201cWake Up\u201d a \u201cSleeping\u201d Queue: Part 3<\/a>
Web Service POST Call Output Advantages<\/a>
Web Service POST Call Output<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Please refer to the following post for more details: eFORMz API Management (Developer Resources) There are two primary endpoints available to eFORMz customers. These are the \u2018director\u2019 and \u2018output\u2019 endpoints. For more on the ‘output’ endpoint, consult the following post: Output Endpoint with ServiceConfiguration (API\/Web Service Call) An “endpoint” is one end of a communication […]<\/p>\n","protected":false},"author":75,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[454],"tags":[584,583,633,346,342],"_links":{"self":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/8388"}],"collection":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/users\/75"}],"replies":[{"embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/comments?post=8388"}],"version-history":[{"count":9,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/8388\/revisions"}],"predecessor-version":[{"id":8487,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/8388\/revisions\/8487"}],"wp:attachment":[{"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/media?parent=8388"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/categories?post=8388"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c002.minisoft.com\/support\/wp-json\/wp\/v2\/tags?post=8388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}