O4W debug (O4W) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{tag>category:"O4W" author:"Barry Stevens" author:"bshumsky"}}

[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]


==== O4W debug (O4W) ====
=== At 17 APR 2023 03:16:11AM Barry Stevens wrote: ===
 
 
<QUOTE>
I run a WYSIWYG form as test->mobile which has an O4W procreedure 'attached' 

I have the engine server running in debug mode.



I put a DEBUG in the O4W proc and the form just displays, not debug.



should I be seeing a debug screen, or have I missed a setting somewhere?
</QUOTE>
----

=== At 17 APR 2023 09:45AM bshumsky wrote:  ===

<QUOTE>
<QUOTE>I run a WYSIWYG form as test->mobile which has an O4W procreedure 'attached' 

I have the engine server running in debug mode.



I put a DEBUG in the O4W proc and the form just displays, not debug.



should I be seeing a debug screen, or have I missed a setting somewhere?</QUOTE>



Hi, Barry.  The O4W form runs without an OpenInsight, only using an OEngine.  So by default it won't know what to do with a DEBUG statement.  However, if you start up your engines with startup and shutdown flags of "1" (instead of the default 65 and 1), you'll get a visible OEngine and it will then be able to drop to the debugger.  Note that you'll only see the debugger screen on the server where your engine server is running (in case that's a different machine than you're using for your browser).



Hope that helps,



- Bryan Shumsky

[url=https://www.revelation.com]Revelation Software, Inc.[/url]

</QUOTE>

----

=== At 17 APR 2023 03:16PM Barry Stevens wrote:  ===

<QUOTE>Post removed by author

</QUOTE>

----

=== At 17 APR 2023 03:46PM Barry Stevens wrote:  ===

<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>I run a WYSIWYG form as test->mobile which has an O4W procreedure 'attached' 

I have the engine server running in debug mode.



I put a DEBUG in the O4W proc and the form just displays, not debug.



should I be seeing a debug screen, or have I missed a setting somewhere?</QUOTE>



Hi, Barry.  The O4W form runs without an OpenInsight, only using an OEngine.  So by default it won't know what to do with a DEBUG statement.  However, if you start up your engines with startup and shutdown flags of "1" (instead of the default 65 and 1), you'll get a visible OEngine and it will then be able to drop to the debugger.  Note that you'll only see the debugger screen on the server where your engine server is running (in case that's a different machine than you're using for your browser).



Hope that helps,



- Bryan Shumsky

[url=https://www.revelation.com]Revelation Software, Inc.[/url]</QUOTE>



Change in the eserver.cfg?



Run the EngineServerDebug.bat (.\jre\bin\java -jar oesocketserver.jar -d 3)?



I put a debug at the start of the O4W proc and it is still not showing

The O4W is showing as registered.

I put the debug in to check that it is actually getting called.



Is there maybe a message display function I can also try?</QUOTE>



</QUOTE>

----

=== At 17 APR 2023 03:58PM Barry Stevens wrote:  ===

<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>I run a WYSIWYG form as test->mobile which has an O4W procreedure 'attached' 

I have the engine server running in debug mode.



I put a DEBUG in the O4W proc and the form just displays, not debug.



should I be seeing a debug screen, or have I missed a setting somewhere?</QUOTE>



Hi, Barry.  The O4W form runs without an OpenInsight, only using an OEngine.  So by default it won't know what to do with a DEBUG statement.  However, if you start up your engines with startup and shutdown flags of "1" (instead of the default 65 and 1), you'll get a visible OEngine and it will then be able to drop to the debugger.  Note that you'll only see the debugger screen on the server where your engine server is running (in case that's a different machine than you're using for your browser).



Hope that helps,



- Bryan Shumsky

[url=https://www.revelation.com]Revelation Software, Inc.[/url]</QUOTE>



Change in the eserver.cfg?



Run the EngineServerDebug.bat (.\jre\bin\java -jar oesocketserver.jar -d 3)?



I put a debug at the start of the O4W proc and it is still not showing

The O4W is showing as registered.

I put the debug in to check that it is actually getting called.



Is there maybe a message display function I can also try?</QUOTE>

</QUOTE>



UPDATES TO MY QUESTIONS

Found debug info on page 476



[i]>>Change in the eserver.cfg?[/i]

Changed in registry for OECGI4



[i]>>Run the EngineServerDebug.bat (.\jre\bin\java -jar oesocketserver.jar -d 3)?[/i]

Doing that



[i]>>I put a debug at the start of the O4W proc and it is still not showing[/i]

When now run web page now goes blank, so assume debug hit.

BUT I do not see any engine spun up or the debug screen.



Maybe answer this:

I have a text field 'element4' and was testing to add text value 



tried:

controlHandle = O4WCommuterUtility(ctlEntID,  O4WUTILITY_FORMELEMENT_CONTROL$, ELEMENT_PREFIX$:'4')

o4wUpdate(controlHandle, "Job 123 details", O4WResponseOptions(1))



and this:

o4wUpdate('element4', "Job 123 details", O4WResponseOptions(1)) 



none work



On the form in the 'Text properties' I have ^ in the text: field

</QUOTE>

----

=== At 17 APR 2023 05:16PM Barry Stevens wrote:  ===

<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>I run a WYSIWYG form as test->mobile which has an O4W procreedure 'attached' 

I have the engine server running in debug mode.



I put a DEBUG in the O4W proc and the form just displays, not debug.



should I be seeing a debug screen, or have I missed a setting somewhere?</QUOTE>



Hi, Barry.  The O4W form runs without an OpenInsight, only using an OEngine.  So by default it won't know what to do with a DEBUG statement.  However, if you start up your engines with startup and shutdown flags of "1" (instead of the default 65 and 1), you'll get a visible OEngine and it will then be able to drop to the debugger.  Note that you'll only see the debugger screen on the server where your engine server is running (in case that's a different machine than you're using for your browser).



Hope that helps,



- Bryan Shumsky

[url=https://www.revelation.com]Revelation Software, Inc.[/url]</QUOTE>



Change in the eserver.cfg?



Run the EngineServerDebug.bat (.\jre\bin\java -jar oesocketserver.jar -d 3)?



I put a debug at the start of the O4W proc and it is still not showing

The O4W is showing as registered.

I put the debug in to check that it is actually getting called.



Is there maybe a message display function I can also try?</QUOTE>

</QUOTE>



UPDATES TO MY QUESTIONS

Found debug info on page 476



[i]>>Change in the eserver.cfg?[/i]

Changed in registry for OECGI4



[i]>>Run the EngineServerDebug.bat (.\jre\bin\java -jar oesocketserver.jar -d 3)?[/i]

Doing that



[i]>>I put a debug at the start of the O4W proc and it is still not showing[/i]

When now run web page now goes blank, so assume debug hit.

BUT I do not see any engine spun up or the debug screen.



Maybe answer this:

I have a text field 'element4' and was testing to add text value 



tried:

controlHandle = O4WCommuterUtility(ctlEntID,  O4WUTILITY_FORMELEMENT_CONTROL$, ELEMENT_PREFIX$:'4')

o4wUpdate(controlHandle, "Job 123 details", O4WResponseOptions(1))



and this:

o4wUpdate('element4', "Job 123 details", O4WResponseOptions(1)) 



none work



On the form in the 'Text properties' I have ^ in the text: field</QUOTE>

This is my registry settings




<code>
Windows Registry Editor Version 5.00



[HKEY_LOCAL_MACHINE\SOFTWARE\RevSoft\OECGI4\examples]

"ApplicationName"="EXAMPLES"

"EngineName"=""

"FileMode"="1"

"FilePath"=""

"OILocation"=""

"ProcedureName"="RUN_OECGI_REQUEST"

"ServerPort"="18088"

"ServerURL"="localhost"

"ShutdownFlags"="1"

"StartupFlags"="1"

"SysDownPage"=""

"UserName"="EXAMPLES"

"UserPassword"="EXAMPLES"


</code>






This is my url , using internal server.



http://localhost:18888/examples/oecgi4.exe/O4W_DESIGN_FORM

</QUOTE>

----

=== At 17 APR 2023 06:04PM Barry Stevens wrote:  ===

<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>
<QUOTE>I run a WYSIWYG form as test->mobile which has an O4W procreedure 'attached' 

I have the engine server running in debug mode.



I put a DEBUG in the O4W proc and the form just displays, not debug.



should I be seeing a debug screen, or have I missed a setting somewhere?</QUOTE>



Hi, Barry.  The O4W form runs without an OpenInsight, only using an OEngine.  So by default it won't know what to do with a DEBUG statement.  However, if you start up your engines with startup and shutdown flags of "1" (instead of the default 65 and 1), you'll get a visible OEngine and it will then be able to drop to the debugger.  Note that you'll only see the debugger screen on the server where your engine server is running (in case that's a different machine than you're using for your browser).



Hope that helps,



- Bryan Shumsky

[url=https://www.revelation.com]Revelation Software, Inc.[/url]</QUOTE>



Change in the eserver.cfg?



Run the EngineServerDebug.bat (.\jre\bin\java -jar oesocketserver.jar -d 3)?



I put a debug at the start of the O4W proc and it is still not showing

The O4W is showing as registered.

I put the debug in to check that it is actually getting called.



Is there maybe a message display function I can also try?</QUOTE>

</QUOTE>



UPDATES TO MY QUESTIONS

Found debug info on page 476



[i]>>Change in the eserver.cfg?[/i]

Changed in registry for OECGI4



[i]>>Run the EngineServerDebug.bat (.\jre\bin\java -jar oesocketserver.jar -d 3)?[/i]

Doing that



[i]>>I put a debug at the start of the O4W proc and it is still not showing[/i]

When now run web page now goes blank, so assume debug hit.

BUT I do not see any engine spun up or the debug screen.



Maybe answer this:

I have a text field 'element4' and was testing to add text value 



tried:

controlHandle = O4WCommuterUtility(ctlEntID,  O4WUTILITY_FORMELEMENT_CONTROL$, ELEMENT_PREFIX$:'4')

o4wUpdate(controlHandle, "Job 123 details", O4WResponseOptions(1))



and this:

o4wUpdate('element4', "Job 123 details", O4WResponseOptions(1)) 



none work



On the form in the 'Text properties' I have ^ in the text: field</QUOTE>

This is my registry settings




<code>
Windows Registry Editor Version 5.00



[HKEY_LOCAL_MACHINE\SOFTWARE\RevSoft\OECGI4\examples]

"ApplicationName"="EXAMPLES"

"EngineName"=""

"FileMode"="1"

"FilePath"=""

"OILocation"=""

"ProcedureName"="RUN_OECGI_REQUEST"

"ServerPort"="18088"

"ServerURL"="localhost"

"ShutdownFlags"="1"

"StartupFlags"="1"

"SysDownPage"=""

"UserName"="EXAMPLES"

"UserPassword"="EXAMPLES"


</code>






This is my url , using internal server.



http://localhost:18888/examples/oecgi4.exe/O4W_DESIGN_FORM</QUOTE>





I dont think my O4W proc is being executed.

I hove put in o4werror("We are here") and I get no message

</QUOTE>

----

=== At 18 APR 2023 08:49AM bshumsky wrote:  ===

<QUOTE>For "posterity" (in case anyone else is following this thread and needs answers) - Barry needed to change his startup/shutdown flags in the eserver.cfg, rather than the registry, since he is using the built in web server that's in the engine server, and that doesn't use the external oecgi4.exe or oecgi4p.php (nor their settings).  In addition, to have the commuter module invoked, Barry had to select one (or more) events in the form designer that he wanted to call the commuter module on - it's not called directly from the URL, but only from the form "runner" when there's an event that it needs to handle.



- Bryan Shumsky

[url=https://www.revelation.com]Revelation Software, Inc.[/url]

</QUOTE>

----

=== At 18 APR 2023 05:26PM Barry Stevens wrote:  ===

<QUOTE>
<QUOTE>For "posterity" (in case anyone else is following this thread and needs answers) - Barry needed to change his startup/shutdown flags in the eserver.cfg, rather than the registry, since he is using the built in web server that's in the engine server, and that doesn't use the external oecgi4.exe or oecgi4p.php (nor their settings).  In addition, to have the commuter module invoked, Barry had to select one (or more) events in the form designer that he wanted to call the commuter module on - it's not called directly from the URL, but only from the form "runner" when there's an event that it needs to handle.



- Bryan Shumsky

[url=https://www.revelation.com]Revelation Software, Inc.[/url]</QUOTE>





..and For further "posterity" ....



I was changing this

StartupFlags=65



I should have been changing the 'StartupFlag' in this

WebServerConnection_examples=EXAMPLES,EXAMPLESO4W,*,[b]1[/b],1,RUN_OECGI_REQUEST,,,1,,

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=D3E936AAF16DDB4CB8B54B81676DE010|View this thread on the Works forum...]]