In order for the SRP HTTP Framework to operate properly with Revelation Software's OECGI4.exe, a well-formed Registry Key needs to be created. For straight forward configurations, the full path looks like this:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\RevSoft\OECGI4
Here are the key/value pairs:
"ProcedureName"="HTTP_MCP""QueueName"="""ServerName"="localhost""SysDownPage"="""UserName"="EXAMPLES""UserPassword"="""WorkingDirectory"="C:\Revsoft\OInsight""ServerPort"="8088""ApplicationName"="EXAMPLES""ShutdownFlags"="1""StartupFlags"="1""FileMode"="1""AdditionalValues"="HTTP_AUTHORIZATION,HTTP_MEDIA_TYPE,HTTP_ACCEPT_ENCODING,HTTP_ACCEPT_CHARSET,HTTP_ACCEPT_LANGUAGE"
Obviously, the UserName, WorkingDirectory, and ApplicationName values should be modified to suit your environment.
The ProcedureName value normally refers to the RUN_OECGI_REQUEST stored procedure. It needs to refer to HTTP_MCP (a procedure that ships with the SRP HTTP Framework) in order to properly handle RESTful HTTP requests.
The AdditionalValues value is how the OECGI is taught to look for HTTP request header fields that it does not monitor by default. These header fields are not required but they are commonly used. If HTTP Basic Authentication will be used (since it is a common form of authentication with REST APIs), then HTTP_AUTHORIZATION is necessary.
