OI10

In the 'OpenInsight 10 O4W 2.0 Quick Start Guide.pdf'

is this still valid. Is'nt this now built into OI10.

O4W Requirements

OpenInsight for Web (O4W) makes use of the OEngineServer which requires the Java Runtime Environment on the server where the OEngineServer is installed.  The Java Runtime Environment can be downloaded from Oracle at:



https://www.java.com/en/download/manual.jsp



OpenInsight 10.0 and above requires the 64-bit version of Java.



Make sure that java is in the system path in environment settings.

OI10

In the 'OpenInsight 10 O4W 2.0 Quick Start Guide.pdf'

is this still valid. Is'nt this now built into OI10.

O4W Requirements

OpenInsight for Web (O4W) makes use of the OEngineServer which requires the Java Runtime Environment on the server where the OEngineServer is installed.  The Java Runtime Environment can be downloaded from Oracle at:



https://www.java.com/en/download/manual.jsp



OpenInsight 10.0 and above requires the 64-bit version of Java.



Make sure that java is in the system path in environment settings.

Hi, Barry. The requirement is still correct, O4W in OI 10.x requires a 64bit java. However, during the installation process, you have the option of automatically installing an open-source one, and if you choose that option O4W and OI will "configure itself" because it "knows" where the installed java is located.

You aren't required to use the provided one - some companies may decide that they prefer a commercial (and commercially-supported) version instead, or wish to manually install their own so that they can enable auto-updates, for example.

Hope that clarifies things for you.

- Bryan Shumsky

Revelation Software, Inc.

OI10

In the 'OpenInsight 10 O4W 2.0 Quick Start Guide.pdf'

is this still valid. Is'nt this now built into OI10.

O4W Requirements

OpenInsight for Web (O4W) makes use of the OEngineServer which requires the Java Runtime Environment on the server where the OEngineServer is installed.  The Java Runtime Environment can be downloaded from Oracle at:



https://www.java.com/en/download/manual.jsp



OpenInsight 10.0 and above requires the 64-bit version of Java.



Make sure that java is in the system path in environment settings.

Hi, Barry. The requirement is still correct, O4W in OI 10.x requires a 64bit java. However, during the installation process, you have the option of automatically installing an open-source one, and if you choose that option O4W and OI will "configure itself" because it "knows" where the installed java is located.

You aren't required to use the provided one - some companies may decide that they prefer a commercial (and commercially-supported) version instead, or wish to manually install their own so that they can enable auto-updates, for example.

Hope that clarifies things for you.

- Bryan Shumsky

Revelation Software, Inc.

Thank you

Hi Bryan,

We are configuring a new virtual webserver and have configured an app server to run OI9.3.2, which also accesses AREV3.11 files on a Windows 2016 server.

Both the app server and the arev server are running UD4.7.2NUL. The webserver runs on Windows Server 2016.

We are using the app server to process website cart and other calls through OECGI. The OECGI4 Quick Start

indicates OECGI4 is backwards compatible to OECGI3, which is good news.

What versions of JRE are compatible with OECGI4.exe? I read in the Quick Start to use a 32 bit version of JRE, however the latest versions of JRE do not offer a 32 bit version, only 64 bit. I have also read that it is important to use the latest version of JRE, so I am hoping for Windows Server 2016 that the 64 bit version will work.

Thanks in advance!

Hi, Jim. I think there may be some confusion about the role that OECGI4 plays, versus the engine server.

OECGI4 is available to use with OpenInsight 9.4 (note that it's not been tested or used with OpenInsight 9.3.2, and I would of course suggest that upgrading to AT LEAST the latest version of OpenInsight 9 would be beneficial). However, while OECGI4 is the "communication channel" between the web server and the engine server, it does this communication via tcp/ip sockets, and thus isn't hooked "directly" to the engine server.

The engine server, on the other hand, is a java application that is tightly coupled with the OpenInsight OEngine. Therefore, it is the engine server that needs to have a JRE installed, and - because you're running a 32bit OpenInsight - the JRE has to be a 32bit one.

So before we continue, we have to make sure that you're running (or planning to run) the engine server (also called the OESocketServer) as a service or via a DOS CMD prompt. If you're not, I don't believe OECGI4 will benefit you.

If you ARE going to use an engine server, then you can download a JRE from "Adoptium.net" (previously known as AdoptOpenJDK) - they have 32bit JREs available, and I would suggest you use version 11. Here is a link to the download page.

Hope that helps,

- Bryan Shumsky

Revelation Software, Inc.

View this thread on the Works forum...