Repository entities are prefixed with an application name which makes it difficult to copy items from one application to another. The SYSCOPYAPPS form is a handy tool to copy specific types of entities or a complete application from one application to another application.
Did you know…that you can create a custom login screen for your O4W application utilizing permission levels.
The creation of a custom O4W login process requires an understanding of O4W permission levels. A permissions number is assigned to each user. “0” is the highest permission, and can run anything; higher numbers (1, 2, 10, etc.) are lower permissions. Each O4W custom stored procedure, report, form, etc., are also assigned a permissions number, and if the logged-in user has a permission number that’s equal to or less than the permissions required for a report, form, etc., then the user is allowed to run the report, form, etc.
Read more about this topic in the OpenInsight knowledgebase.
Did you know…
That the INET Configuration form allows you to configure defaults, handlers, and allowed routines for RUN_OECGI_REQUEST.
When using RUN_OECGI_REQUEST as the “listener” routine for handling web requests, you can configure various routines to check security, handle errors, and do any post-processing. In addition, you can specify which INET routines should be processed.
The INET Configuration form can be accessed from the Application Manager, Tools, INET Configuration.
Did you know…That you can create a GeoMap with the O4W Dashboard wizard.
An effective way to create a graph using O4W is to start with a report. By creating a simple detail suppressed report, you can easily convert the report into a graph using the O4W Dashboard Wizard.
Did you know……That OECGI3 supports Failover and Load Balancing modes. These modes make OECGI3 a more robust connection object and allows for extra capacity and/or redundancy to be added to a web application. The OECGI3 registry setting, MultipleServers, controls whether OECGI3 operates in Failover or Load Balancing mode.
MultipleServers = 0 sets Failover mode
MultipleServers = 1 sets Load Balancing mode
Multiple URL’s and Port’s are entered as comma delimited fields into the ServerURL and ServerPort registry settings.
ServerURL = 192.168.0.1,192.168.0.2
ServerPort = 8088,8089
In Failover mode, you supply OECGI3 with a list of ServerURL’s and ServerPort’s that are available. OECGI3 attempts to connect to the first ServerURL/ServerPort in the list. If the connection is unsuccessful then OECGI3 will continue on to the next ServerURL/ServerPort in the list until a successful connection is made. If all connection attempts fail, then OECGI3 will return the SYSDOWNPAGE page.
In Load Balancing mode, you supply OECGI3 with a list of ServerURLs and ServerPorts that are available. OECGI3 will randomly choose a ServerURL/ServerPort from the list available, and then attempt to connect to that server. If the connection fails, OECGI3 will move to the next ServerURL/ServerPort in the list, looping through the list until it is back at the originally selected URL/Port combination, at which point OECGI3 will return the SYSDOWNPAGE page.
Complete details can be found in the OECGI3.EXE INSTALLATION AND CONFIGURATION QUICK START GUIDE.
Did you know…That OpenInsight’s database management system is based on pluggable storage implementations, called filing systems. The most common example is Linear Hash, which is implemented by the RTP57 filing system function. The configuration information for those filing systems, which primarily defines the set of tables available to an application, is stored persistently (i.e., is not lost when you log out of OpenInsight) in a .DBT file.
In OpenInsight terms, a table is available if it is attached, and thus can be opened. As a result, without additional coding, a table is not available unless it is in the application’s .DBT file. Click here to read further details…