I'm seeing two separate issues here...
Issue #1
Since you are speaking of "Processor" and "WebApp.Start" you are still not using SmartConnector's "REST Extension Framework" as I referred to in my prior post on this thread. Instead, you are taking over all apsects of the endpoint and standing it up from within a Processor. While this is certainly a valid approach, it has many downsides as you now see. Besides not having configuration, provisioning, auth, licensing, throttling, etc done for you by the framework (or perhaps you even duplicated effort in one or more of these areas), you also need to always have a Processor running for the sole purpose of keeping the endpoint alive.
I do realize that authoring your own REST Extension isn't well documented at this point. This is why I inquired as to your timeframe and whether this was for a real job or not. I was trying to gauge the urgency for posting an example to GitHub.
For now, you can continue the approach you are on but please make sure your Proccessor code looks like this:
protected override IEnumerable<Prompt> Execute_Subclass()
{
using (WebApp.Start(url, configurationAction)) // url and configurationAction are as you have them now
{
do
{
NoBusyWait(10, false);
} while (!IsCancellationRequested); // This will allow the Processor to respond to STOP requests
}
return new List<Prompt>();
}
Also, make sure that your Processor implements ILongRunningProcess. Failure to do that, will result in the WorkerManager attempting to "kill" the Proccessor.
Issue #2
I read your question to mean you have data in some SQL DB/Tables that you want to serve as EWS data back to SBO. There are two approaches you can use for this.
- Custom EWS Server. By implementing a custom EWS Server you can serve data directly from your database and not the one that comes with SmartConnector. This is discussed in the SmartConnector Developers Guide section 4.2 as a "synchronous" custom server but the source is a database. See also section 5.7 for an example on creating a custom EWS Server Extension.
- Standard EWS Server. In order to leverage the included standard EWS Server, you would need to take over pushing the data into the SmartConnector SQL tables yourself. Using the EwsServerDataAdapter wouldn't work in this scenario because it handles aspects such as creating history automatically for you.
