Push Messaging and RESTful API on IIS

Gavin Foster omnislist at dataweaver.com
Fri Apr 13 09:49:12 EDT 2018

I found an accidental fix whilst trying to get SSL working.

I was using the following parameter in the omnisobject1:

I changed it to:

I also cleared the cache on the client and restarted the web server, just in case.

After that, I noticed that push messaging was working. Not sure which action had the desired effect.


> On 13 Apr 2018, at 11:25, Gavin Foster <omnislist at dataweaver.com> wrote:
> Hi $all,
> I’ve implemented push messaging as per pages 57-58 in the Omnis_Webdev81.pdf manual.
> It works fine when talking directly to Omnis directly via its serverport.
> However, it’s not working on IIS.
> In IIS Manager, I’ve installed both of the following and ensured Execute permissions are turned on as per TNJS0003 <http://www.omnis.net/technotes/tnjs0003.jsp>:
> - omnisapi.dll (this works and remote forms instantiate via the website URL)
> - omnisrestapi.dll (this seems to be failing or I haven’t configured something)
> I suspect I’m failing to understand the following section in the manual:
> For example, if your HTML page for the JavaScript client uses the URL:
> http://localhost:8080/omnisservlet
> then the client scripts will convert this to:
> http://localhost:8080/omnisrestservlet
> for the push connection. You can see the URL used for push connections by using browser debugging tools.  
> Does anyone have any experience in this and can help?
> Perhaps I need to add a parameter to the <div id=“omnisobject1”… line?
> Thanks vm,
> Gav
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com 

More information about the omnisdev-en mailing list