OECGI, IIS 5.x and Novell (OpenInsight 32-Bit) [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:"OpenInsight 32-Bit" author:"Warren Auyong" author:"Bob Carten" author:"support@sprezzatura.com"}}

[[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]]


==== OECGI, IIS 5.x and Novell (OpenInsight 32-Bit) ====
=== At 21 JUL 2004 03:37:09PM Warren Auyong wrote: ===
 
 
<QUOTE>
System: Win2K Server, IIS v5.x, Novell 3.x and OI 7.01 on the Novell server.



When running dynamic engine (CreateFlag=1 or 2, shutdownsessions=1) IIS creates netware connection each time an engine is created. The netware connection is not released when the engine session is destroyed. Maximun netware connections gets reached and OECGI will no longer connect.



I tried CreateFlag=2, ShutDownSessions=0 and using a named Engine/Piped connection. When doing this only one engine session and netware connection appears to be created. Will this support multiple requests though (simulated multi-threading)?



Otherwise, is there a way to limited the number dynamic engines and close the netware connection when the engine closes?



If using persistent engines, how would you close/shut down automatically and gracefully to run tape backups?
</QUOTE>
----

=== At 21 JUL 2004 06:07PM Bob Carten wrote:  ===

<QUOTE>Sprezz has tools that might take care of you, but here are some thoughts:



1. Instead of OECGI, use Xrev.dll. This will let you have each request choose from a list of engines, which OECGI cannot do. Make a vb dll that uses the external engine example from the 7.0 help. Then have an asp page that uses that dll.  You can write the dll so that it accepts a parameter which tells it which engine to connect to, or you can write it to round robin across a group of engines.  I think XREV.DLL will run in process with the asp server, so it may not even create new connections to the Novell server.  That is, you might find that creating and killing dynamic engines this way does not use up all your connections.





2. create a procedure called INET_SHUTDOWN. Have a shutdown method in your vb dll then use vbscript,or just use a batch file and OECGI to run the command. Use an 'AT' command in nt to trigger the shutdown.







HTH



Bob

</QUOTE>

----

=== At 22 JUL 2004 02:18AM support@sprezzatura.com wrote:  ===

<QUOTE>Also a licensing caveat - anytime you move away from OECGI and dynamic engines you still need a WDP. So persistent engines (Linux?) and XREV require a WDP.



support@sprezzatura.com

The Sprezzatura Group Web Site

[i]World Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>


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