SYSENV Configuration [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.
====== SYSENV Configuration ======

O4W is built upon OpenInsight's OECGI processing, and thus the OpenInsight OECGI configuration settings must be modified to allow O4W requests.  OECGI security is controlled by a record located in the SYSENV table named CFG_INET. CFG_INET contains settings for which security, wrap up, and abort routines (if any) should be used in OECGI requests.

The first value of the first field of the CFG_INET record contains the name of the security routine; in normal, non-O4W use, it defaults to INET_SECURITY.  <del>For O4W requests to be allowed, this value must be modified to be INET_O4W_SECURITY.</del> //For OpenInsight 10+, the security routine need not be changed from INET_SECURITY.//

Some users may not wish to replace all OECGI security processing with INET_O4W_SECURITY calls.  The CFG_INET record can be set on a per-user, per-application, or system-wide basis.  OpenInsight first looks for a record named CFG_INET*<appname>*<username> (for example, CFG_INET*EXAMPLES*JOHNSMITH); if this record is found for the current application and user name, its contents are used.  If no CFG_INET*<appname>*<username> record is found, OpenInsight then searches for a record named CFG_INET%%**%%<username> (for example, CFG_INET%%**%%JOHNSMITH); if this record is not found, then CFG_INET*<appname> (for example, CFG_INET*EXAMPLES) is checked.  If no matching username or application specific records are found, then the system-wide CFG_INET record is used.  In this fashion, it is possible to have multiple independent OECGI configurations operating on a single system, and OpenInsight will use the most "specific" one it can find.

 

The Chain of Acceptance

CFG_INET*<appname>*<username>

CFG_INET%%**%%<username>

CFG_INET*<appname>

CFG_INET