Ha, I thought that subject would catch some attention..

I'm basically needing to capture a timeout, while communicating to a webservice. Is there any way to do that? We have an ingestion process that occurs on the backend were we load data into Magnify, but if our service times out when pulling data, we have no way to stop other processes that occur afterwards, which are not attached to the error'd process. We need to log that it failed so that other process will not continue.

This message has been edited. Last edited by: Tamra,

GavinL,

Have you looked into RESTful services ?

A RESTful web service (also called a RESTful web API) is a web service that is implemented using HTTP and the principles of REST. It is a collection of resources with four defined aspects:
◾Base URL for the web service, such as:http://example.com/resources

◾Internet media type of the data supported by the web service. This is usually XML, but can be any other valid Internet media type providing that it is a valid hypertext standard.
◾Set of operations supported by the web service using HTTP methods (for example, GET, PUT, POST, or DELETE).
◾The API must be hypertext driven.


REST-style architectures consist of clients and servers. Clients initiate requests to servers, servers process requests and return appropriate responses. Requests and responses are built around the transfer of representations of resources. A resource can be essentially any coherent and meaningful concept that may be addressed. A representation of a resource is typically a document that captures the current or intended state of a resource.

Thank you for participating in the Focal Point Forum.

Kindest regards,
Tamra Colangelo
Focal Point Moderator - Information Builders Inc.

Sorry, somehow I missed your response.. Our ingestion is a FEX that calls a Synonym that is connecting to an external restful service. If that times out, how does our fex know? Currently, it fails the fex and stops there, but we need a way to capture this error and log something that lets other Asynchronous calls to stop processing.

Error Trapping may be your solution... Check the value of &FOCERRNUM and branch accordingly...

Just FMI:

Posts: 1983 | Location: Goodlettsville, TN (DG WF8007) ~ In FOCUS since 1983 | Registered: February 23, 2005

That would be nice, but the Fex dies, how do I check &FOCERRNUM after a fex page just dies?

You should be able to add the following at the top of your focexec:
-SET &ECHO=ALL;

Or if running using AppStudio or Dev Studio RUN with the traces on.

You will see where it stops. What is the error message that appears? You can also add
wherever it stops -TYPE this is the error - &FOCERRNUM

Give that a try.

Thank you for participating in the Focal Point Forum

Kind Regards,
Tamra Colangelo
IBI Focal Point Moderator