Caching it as a temp-table will run circles around having it in the either of the buffer pools. Especially if you have client server connections. TT access can be 5x to 20x faster than db access - even when the db data is in the buffer pool.
If your application just happens to have an include...
That is awfully vague.
Surely the "requirement" specifies what sorts of events you must audit. From the rest of your post it almost sounds like you only need to be keeping track of certain events like "access to the Progress editor". If that is true and the if number of events is fairly limited...
I might be flogging a dead horse but just to clarify... do you mean that you lack a key to decrypt the xcoded files back to clear text?
(That's normal. There is no Progress provided utility to convert xcoded source back to clear text. Obviously the compiler knows how to do it. There are also a...
There are really only two platforms that you should consider migrating to -- Linux or Windows. Of the two Linux will be far less likely to be a problem, since you are already on AIX Linux ought to be much more familiar.
In either case you will need to dump & load for the platform change. AIX...
The reported error might be related to this kbase: Progress Customer Community
Note that the recommended resolution is to upgrade to at least 10.2b04. 10.2b08 is the last release of OpenEdge 10 and that is what I would target.
I see what look like additional error messages hidden behind other...
Aside from waiting on appserver calls you could also be waiting on other things like record locks, reads from sockets, operating system commands and a plethora of other things. So don't bet everything on it being an app server problem until you have some hard evidence that that is true.
How does one manage to "login to the database" without running a QAD menu? Doesn't the QAD main menu appear as a result of successfully logging in? Are you just saying that the idea is to just login and not select anything from that menu?
This comment is also interesting:
I do not understand this comment:
What does that mean?
The fact that appservers are running is not, in itself, a problem. They are, presumably, doing something of value for the users of the application.
The bit about taking 5 minutes to "clear" is also not obviously a problem. Is there some...
It is probably the other way around. Your vendor has likely "rebranded" some of the Progress tooling and, quite possibly, added some additional tooling to simplify maintenance tasks (like archiving audit logs). Maybe even some reporting.
As far as "a DBA login is backdoor to..." well, duh. Do...
This seems like a very odd comparison to be making. Perhaps you could elaborate on why you are comparing these two?
As James says, one tool (OE Auditing) is explicitly designed for that purpose and is known to deliver those results reliably with a modest amount of initial configuration and...
You could always create a symbolic link to a shorter path. For instance, if /opt/java/jdk does not exist:
# mkdir -p /opt/java
# ln -s /usr/lib/jvm/java-1.8.0-openjdk-18.104.22.1682.b05-1.el7_9.x86_64 /opt/java/jdk
Those are the example directories. You do have /usr/lib/jvm/java-1.8.0-openjdk-22.214.171.1242.b05-1.el7_9.x86_64 etc. So, as you indicated above, you should change java_env to be:
The article is saying that you should put your actual path to Java in java_env and providing a simple example.
You must also adjust: "The new value of the JAVA_HOME environment variable in <DLC>/properties/java.properties"
There are some "interesting" patterns with ENCODE(), for instance:
define variable rr as character no-undo.
define variable ii as integer no-undo.
define variable jj as integer no-undo.
do ii = 1 to 10:
rr = "".
do jj = 1 to 16:
rr = rr + chr( random( 32, 126 )).
I wasn't thinking that the plaintext password would be stored, that's a grave sin, but in my mind I was certain that ENCODE() just ignored everything after the 16th character.
I should have tested that :(
Aside from being ancient and supposedly easy to crack, the other reason that the ENCODE function is inadequate is that it only considers the first 16 characters - so your ability to require long passwords is compromised. (strike out for posterity...)
Also "requirements" #1 & #2 are junk...
Sorry, there is no magic pixie dust that will add support for OpenEdge to SonarCloud. (I said as much is the first reply to this thread.)
You might as well ask when Oracle will start supporting OpenEdge.
If you want Sonar style code analysis of OpenEdge, CABL is the solution. I'm terribly...