This blog contains experience gained over the years of implementing (and de-implementing) large scale IT applications/software.

IBM WebSphere 6.1.0 GUI Install on RHEL 4.5

If you have been given the opportunity to install IBM WebSphere 6.1.0 on RedHat Enterprise Linux 4.5, then you may be wondering why you can’t get the GUI installer to launch using the X-Windows terminal you’ve painstakingly enabled.

Well, the answer is simple; unless you are on the console, then you can’t.  That is, you must be on DISPLAY “:0.0”.
If your sys admin is denying you access, or it’s a VM and you’re not allowed console access, then you’re also stuck.

The only other solution is to use the response files provided in the install directory of the installation media.
Customise the response file and then run the install.sh in silent mode.
There is a very helpful IBM help page on how to do all of this here: https://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.doc/info/aes/ae/tins_runSilent.html

Good luck.

ps. It presents a more systematic, repeatable approach to installing an environment if you use response files.  No mistakes, same every time.
What’s more, you can also silently install the “UpdateInstaller” and also the FixPacks.

Windows Batch File to Install Windows Task

@cls
@rem ######################################################################
@rem # Script:  install_task.bat
@rem # Params:  none.
@rem # Desc:    This script installs the task that will run the
@rem #           start.bat on the required schedule.  WinXP or Win2k3
@rem # Author:  D.Griffiths
@rem # Version: 1.0
@rem # History:
@rem #          09-June-2008 – DMG – Created.
@rem #
@rem ######################################################################

@set TN=My_TaskName
@set DAYS=MON,TUE,WED,THU,FRI,SAT
@set TR=C:start.bat
@set ST=05:50:00

@set /P conf=Press return to install task “%TN%”:

@echo Tasks currently scheduled…
@schtasks /Query /FO TABLE

@echo.
@echo Removing existing task if already present…
@schtasks /Delete /TN %TN% /F

@echo.
@echo Installing new task “%TN%”…
@schtasks /Create /RU SYSTEM /SC WEEKLY /D %DAYS% /TN %TN% /TR %TR% /ST %ST%
@IF ERRORLEVEL 1 goto invalid_task

@echo.
@echo Task “%TN%” now scheduled.
@echo.
@echo Tasks currently scheduled…
@schtasks /Query /FO TABLE
@echo.
@echo.
@set /P conf=Press return to exit.
@exit

:invalid_task
@echo.
@echo.
@echo ERROR: There was a problem installing the task.
@echo ERROR: Please try again or check the command syntax.
@set /P conf=Press return to exit.

SAP Language Pack Enabling for Login in R/3 Enterprise 4.7

In an SAP system you can see what language packs are installed using transaction SMLT.
Sometimes however, you may find that you are unable to log into the system using one of the languages that are installed.  You get prompted to select a valid language.
This is usually due to a miss-configuration of the zcsa/installed_languages profile parameter.

You can check the system language configuration using the report RSCPINST.
You should note that the zcsa/installed_languages parameter should be set in the DEFAULT profile *only*.

Some useful SAP notes on language packs:

73606 “Supported Languages and Code Pages”
352941 “Languages and Support Packages”
533888 “Example for Language Import and Errors”