Omnis app server deployment

Martin Obongita martin.obongita at yahoo.com
Mon Aug 26 17:24:04 UTC 2024


 
 Hi Caroline,
I'm following this link from Omnis documentation:
https://www.omnis.net/developers/resources/technotes/tnjs0003.jsp
I am using Omnis app server connecting to postgresql database. I installed a separate runtime for the server.So I have both the server installation and the developer.And yes, the server configuration is setup and the synchronization server is connected to the database.
The remote forms open ok. The button objects are okay. The entry field displys the corrent number of record fetched from the server.The only issue is the datagrid is not displaying records fetched and yet I have assigned the $dataname property to a instance variable.
Regards, Martin.


 
 Dear Martin,

In theory, no - a form that runs in development should also run in 
deployment. However, bugs do happen and you might have found one. If so, 
you should report it to Omnis support.

Bugs and breakpoints are different matters. A bug is when the software 
does something it shouldn't. A breakpoint is something you place in the 
code - either in development mode (in which case, they disappear when 
you restart the library or Omnis) or as a "Breakpoint" line command in 
the code (this persists when you restart the library and/or Omnis). In 
runtime, breakpoints should be ignored. But I don't know how you are 
deploying this. If you have a development version on your server, then 
breakpoints will get hit. But you should be able to see that if you look 
at Omnis on the server.

How are you deploying this? What sort of server? Are you using a dev or 
runtime serial number? Do you have a visual interface to the server?

Bye for now

Caroline


On 26/08/2024 14:27, Martin Obongita via omnisdev-en wrote:
>  Thanks Caroline,
> Is it possible for a remote form to run perfectly okay in development environment but would fail in deployment? I thought the reason why we test the window in development mode is to ensure there are no bugs/breakpoints before rolling out to deployment? I'm wrong in my thinking?
> Martin.
>
>
>
>      On Monday, August 26, 2024 at 12:47:12 AM GMT+3, Dr Caroline Wilkins <caroline at ib2bsystems.com> wrote:
>  
>  It's hard to tell without getting in there and exploring the situation
> but these would be the first 2 things I would do:
>
> 1) Check you haven't got a breakpoint in there that has been hit and is
> preventing the methods from completing and providing data to the form.
>
> 2) Golden rule of Omnis: When it does mad stuff, restart it. You'd be
> amazed how many strange problems that has fixed for me over the years!
>
> If those 2 ideas don't resolve the problem, I would be placing a
> breakpoint and stepping through to check the data is being fetched for
> that datagrid.
>
> Good luck!
>
> Caroline
>
>
>
> On 25/08/2024 22:25, Martin Obongita via omnisdev-en wrote:
>> Hello $Omnis Gurus,
>>
>> I have copied the js htm files over in the html folder in the Omnis installation folder. I then edit the htm files <div id="omnisobject1" data parameters>. I copy the library I am testing into the startup folder. The server configuration is setup and the synchronization server is connected to the database. If I run the Omnis app server, the remote form opens okay. Buttons are visible and enabled. The datagrid object is visible and enable but it does not display data. Though the entry field object with iList.$linecount displays 216 records. $dataname property for the datagrid is iLine. If I test in the web dev environment, the datagrid displays all the 216 records. Only in deployment mode does the datagrid refuse to display the data. Any hints on where I could check for a solution?
>>
>> Kind regards, Martin Obongita.
>>
>> _____________________________________________________________
>> Manage your list subscriptions at https://lists.omnis-dev.com
>> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>    
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com


_____________________________________________________________
Manage your list subscriptions at https://lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com 
  


More information about the omnisdev-en mailing list