Installing DataStage Client

I think that many have encountered some problems when installing IBM DataStage on client workstations. Before installation, your system must pass a series of tests for compliance with the requirements that apply to the OS, the user, from which the installation is carried out, to the "hardware". Not always checking returns adequate results.
Here are some ways to circumvent the crookedly implemented checks of the next IBM installer, trying to install a client to Information Server 8.5, which includes clients for DataStage.

First problem

The first problem that arises is that the installer cannot understand that the user you are working in is part of an administrative group if there are Cyrillic characters in the group name or user name. For example, if a user is called “Administrator” and belongs to the local group “Administrators”, then it will be overwhelming for the installer to determine that this user is ... ahem ... administrator.
This is solved simply - it is necessary to rename both the user and the group. Give them names without Cyrillic characters. I don’t know if other values ​​will work (I won’t be surprised if not), but I tried to give the following names:
Username: Administrator (it can be, in principle, and others. For example, Nick)
Group Name: Administrators
You can change the corresponding parameters in My Computer-> Management-> Local Users and Groups.

Second problem

The installer requires that the computer on which the client is installed has at least 2 GB. random access memory. If it is less, it will not allow you to continue the installation. Well, it is necessary, it is necessary, given that I have just 2 GB of memory. He stubbornly claimed that I had “only 1Gb” ...
Knowing that the installer is a server application that runs from under the lifted Jetty server, I begin to vaguely understand that it is unlikely that it will be able to calculate the amount of RAM without the help of third-party utilities. Java machine, as far as I remember, does not allow to know the amount of RAM.
We begin to pick open the jar-nicks that the installer uses. We are interested in the file com.ibm.is.install.atlasinstaller.engine_1.0.0.jar, which is located in% DISTRIB_DIR% \ server \ webapps \ webui \ WEB-INF \ eclipse \ plugins, where% DISTRIB_DIR% is where the distribution is located . Open this file and look for the class com \ ibm \ is \ install \ core \ util \ SystemSize.class. That it determines the size of the RAM.
In the Windows branch, we can find the following line:

if(Platform.getInstance().isWindows()) { workingDir = (new StringBuilder()).append(installerRootDir).append(File.separator). append("tools").toString(); command = (new String[] { (new StringBuilder()).append(installerRootDir).append(File.separator). append("tools").append(File.separator).append("SystemSize.exe").toString() }); 

Those. To determine the size of the RAM, a separate SystemSize.exe EXE is launched, which is located in% DISTRIB_DIR% \ tools
')
(The amount of RAM in Linux in this script is defined as: / bin / sh "," -c "," free | head -2 | tail -1 | awk {'print $ 2 / (1024 * 1024)'})
Run this application and see that in my case it gives 1.98. Those. The installer "looks" only at the integer part of the return value.
Okay. We write your application. In this case, I wrote in C ++:

 #include <cstdlib> #include <iostream> using namespace std; int main(int argc, char *argv[]) { cout<<"2.0"; return EXIT_SUCCESS; } 

Compile, give the name SystemSize.exe and put in% DISTRIB_DIR% \ tools. Everything, now check passes successfully.