Build 30204 and $serverport in Desktop runtime.

Reg Paling reg.paling at lokanet.com
Tue Jun 1 12:26:04 UTC 2021


Hi Andrew,

Thanks so much - that was it!

Regards,
Reg


On 1/6/21 10:16 pm, Andrew McVeigh wrote:
> Reg there was something that Vik helped me out with in the config.json 
> file that needs to be configured
>
> This rings a bell and should be set to false
>
> {
>     "server": {
>         "disableInRuntime": true
>     },
>
> He said it was an Omnis bug that the installer sets this to true when 
> it should be false when using a server runtime code
>
> Andrew McVeigh
> Surfway Real Solutions
> Phone 02 44412679 Mobile 0418428016
> www.surfway.com.au <http://www.surfway.com.au>
> www.berrarabeach.com.au <http://www.berrarabeach.com.au>
>
>
> <http://www.surfway.com.au/>
> <http://www.surfway.com.au/>
>
>> On 1 Jun 2021, at 9:55 pm, Reg Paling <Reg.Paling at Lokanet.com 
>> <mailto:Reg.Paling at Lokanet.com>> wrote:
>>
>> Hi all,
>>
>> My users can click on a calendar entry in their web browser, and it 
>> opens the patient record in their Omnis desktop app.  The browser 
>> link looks like this:
>> http://127.0.0.1:5195/ultra?OmnisServer=127.0.0.1:5195&OmnisLibrary=Mx&OmnisClass=rtPatient&bkSeq=80379 
>> <http://127.0.0.1:5195/ultra?OmnisServer=127.0.0.1:5195&OmnisLibrary=Mx&OmnisClass=rtPatient&bkSeq=80379>
>>
>> The Omnis desktop app is listening on port 5195 and the remote task 
>> rtPatient simply opens the Patient window.
>>
>> Now I have upgraded a couple of users to build 30204 of the Studio 10 
>> runtime, and they are reporting that this is not working any more - 
>> it seems Omnis may not be listening...
>>
>> Has anyone else noticed this, and hopefully worked out how to avoid it?
>>
>> Thanks,
>> Reg
>>
>> _____________________________________________________________
>> 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