Once again on the topic of performance testing Business Objects, when executing a benchmark for a web intelligence report with goal being to see how many concurrent users it could support, the following error mesage was being generated in the vuser log:
Connection failed. The server has reached the maximum number of simultaneous connections. (Error: RWI 00239) (Error: INF )
What to do?
Read MoreI find when testing I need to archive copious amounts of data. Occasionally I need to create a bootable disk image for use in the creation of virtual machines or impromptu test labs. Storing this information and images in the ISO format is quite handy.
Most people will already know how to make an ISO image using their favourite disk tool. Nero & MagicISO are two popular programs that come to mind. But for those that like to keep it free, try the following from your terminal instead …
Read MoreIf you have the requirement to manipulate multitudes of input messages / log files / data templates with dynamic variables, you may be left wondering what is the best approach. One could argue in a friendly way for hours about which language is the best to achieve this outcome (almost like pc vs. mac), but since I often find myself working on mixed environments, you can’t go past perl one liners…
Read MoreI have been working on some template LoadRunner scripts for Business Objects Web Intelligence / Crystal Reports which require good ole fashioned manual correlation.
Before writing this post, in the background I have been working on a tool comparison between LoadRunner and my increasing favourite JMeter with a simple (?) scripting exercise that goes through recording, replaying and correlating data for Business Objects. Common to both tools, is the requirement to correlate essential run time data. As my good Dutch friend Desiderius Erasmus once told us in 1466 …
In the land of the blind, the one-eyed man is king.
[In regione caecorum rex est luscus.]
Knowing how to correlate is key …
But how?
Read MoreFor an internet facing SSH server, it is probably common practice to have sshd listening on a non-standard port. Coupled with key pair authentication, this reduces the profile you present to simple brute force attacks.
Connecting to a SSH server on a non standard port is relatively simple:
ssh -p
You may however need to copy files from the SSH server on an alternate port. Easy:
scp -P
But what happens if you’re using a proprietary client other than scp from the console that won’t support non standard ports?
Read More
