TSM:Preinstall Tasks for Linux - Revision history

Ebasso: /* Updating the /etc/issue file - Only for CentOS */

2013-02-05T23:42:14Z

Updating the /etc/issue file - Only for CentOS

← Older revision		Revision as of 23:42, 5 February 2013
Line 112:		Line 112:

	Logoff and Logon again.		Logoff and Logon again.

			== Ver também ==

			*[[Instalando o Tivoli Storage Manager no Linux]]
			*[[Install Tivoli Storage Manager on Linux]]
			*[[TSM: Removendo um Volume\|Removendo um Volume]]
			*[[TSM:Instalando o IBM Integrated Solution Console]]


			* [[Tivoli Storage Manager\| Mais Artigos sobre IBM Tivoli Storage Manager]]

			[[Category: Tivoli Storage Manager]]
			[[Category: TSM]]

Ebasso: /* Altere o /etc/issue - Somente CentOS */

2007-09-27T21:10:04Z

Altere o /etc/issue - Somente CentOS

← Older revision		Revision as of 21:10, 27 September 2007
Line 94:		Line 94:
	192.168.1.15 tsmserver.mycompany.com tsmserver		192.168.1.15 tsmserver.mycompany.com tsmserver

	== ~~Altere o~~ /etc/issue - ~~Somente~~ CentOS ==		== Updating the /etc/issue file - Only for CentOS ==

	O InstallShield ~~verifica pelo sistema operacional instalado para saber se o mesmo é compatível ou não~~.		InstallShield checks for Operation System installed to know for it's compatibility or not.
	~~Podemos mascarar isso alterando o arquivo~~ '''/etc/issue''' ~~para que o mesmo pense que estamos instalando no~~ Red Hat.		We can avoid/mask this check change the '''/etc/issue''' file. So the same thinks this OS is a trully Red Hat Enterprise


	O original ~~é o seguinte~~:		The original is the following one:

	CentOS release 5 (Final)		CentOS release 5 (Final)
	Kernel \r on an \m		Kernel \r on an \m

	~~altere para~~:		Update to:


Line 111:		Line 111:
	Kernel \r on an \m		Kernel \r on an \m

	~~Efetue um logoff e logon novamente~~.		Logoff and Logon again.

Ebasso: /* Setting the hostname as FQDN */

2007-09-27T21:05:45Z

Setting the hostname as FQDN

← Older revision		Revision as of 21:05, 27 September 2007
Line 84:		Line 84:
	== Setting the hostname as FQDN ==		== Setting the hostname as FQDN ==

	Check that the hostname is full hostname (Full Qualified Domain Name).~~Exemplo~~: tsmserver.mycompany.com		Check that the hostname is full hostname (Full Qualified Domain Name).

			Example: tsmserver.mycompany.com

			Another Example:

	~~Outro exemplo:~~
	> cat /etc/hosts		> cat /etc/hosts
	127.0.0.1 localhost.localdomain localhost		127.0.0.1 localhost.localdomain localhost

Ebasso: /* Confirme o hostname seja FQDN */

2007-09-27T21:04:48Z

Confirme o hostname seja FQDN

← Older revision		Revision as of 21:04, 27 September 2007
Line 82:		Line 82:
	This step can seem strange, but after some attempts, I verified that during installation one script made the following command: "''cd /opt/IBM/ISC/PortalServer/update; updatePortal.sh''", being that the correct one would be "''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". What we decide adding in the PATH.		This step can seem strange, but after some attempts, I verified that during installation one script made the following command: "''cd /opt/IBM/ISC/PortalServer/update; updatePortal.sh''", being that the correct one would be "''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". What we decide adding in the PATH.

	== ~~Confirme o~~ hostname ~~seja~~ FQDN ==		== Setting the hostname as FQDN ==

	~~Confirme que o nome do host esteja na forma completa~~ (Full Qualified Domain Name).Exemplo: tsmserver.~~minhaempresa~~.com~~.br~~		Check that the hostname is full hostname (Full Qualified Domain Name).Exemplo: tsmserver.mycompany.com

	Outro exemplo:		Outro exemplo:
	> cat /etc/hosts		> cat /etc/hosts
	127.0.0.1 localhost.localdomain localhost		127.0.0.1 localhost.localdomain localhost
	192.168.1.15 tsmserver.~~minhaempresa~~.com~~.br~~ tsmserver		192.168.1.15 tsmserver.mycompany.com tsmserver



	== Altere o /etc/issue - Somente CentOS ==		== Altere o /etc/issue - Somente CentOS ==

Ebasso: /* Changing PATH */

2007-09-27T21:02:36Z

Changing PATH

← Older revision		Revision as of 21:02, 27 September 2007
Line 79:		Line 79:


	'''Obs.:''' Pode parecer estranho este passo, mas após algumas tentativas, verifiquei que durante a instalação um script fazia o seguinte comando: "''cd /opt/IBM/ISC/PortalServer/update;updatePortal.sh''" sendo que o correto seria		'''Obs.:'''
	~~"''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". O que resolvemos adicionando no PATH.~~

	This step can seem strange, but after some attempts, I verified that during installation one script made the following command: "''cd /opt/IBM/ISC/PortalServer/update; updatePortal.sh''", being that the correct one would be "''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". What we decide adding in the PATH.		This step can seem strange, but after some attempts, I verified that during installation one script made the following command: "''cd /opt/IBM/ISC/PortalServer/update; updatePortal.sh''", being that the correct one would be "''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". What we decide adding in the PATH.

Ebasso: /* Crie o diretório de update do Portal e altere o PATH */

2007-09-27T21:02:15Z

Crie o diretório de update do Portal e altere o PATH

← Older revision		Revision as of 21:02, 27 September 2007
Line 52:		Line 52:
	Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20070708 (SR9) (JIT enabled: jitc))		Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20070708 (SR9) (JIT enabled: jitc))

	== ~~Crie o diretório de~~ update do Portal ~~e altere o~~ PATH ==		== Create the update Portal directory and change the PATH ==


	=== ~~Criando o Diretório de~~ update do Portal ===		=== Create the update Portal Directory ===

	'''Obs.:''' ~~Na minha instalação estou utilizando o diretório~~ '''/opt/IBM/ISC/''' ~~ao invés de~~ '''/opt/IBM/ISC601/'''.		'''Obs.:''' In this article, i'm using the '''/opt/IBM/ISC/''' directory instead of '''/opt/IBM/ISC601/'''.

	~~Crie o diretório~~ '''/opt/IBM/ISC/PortalServer/update''' ~~através do seguinte comando~~		Create the '''/opt/IBM/ISC/PortalServer/update''' directory through the follow command

	mkdir -p /opt/IBM/ISC/PortalServer/update		mkdir -p /opt/IBM/ISC/PortalServer/update
Line 65:		Line 65:


	=== ~~Altere o~~ PATH ===		=== Changing PATH ===

	~~Edite o arquivo~~ '''/etc/profile''' ~~e adicione as seguintes variaveis de ambiente~~		Modify the '''/etc/profile''' follow, updating the PATH variable:

	PATH=$PATH:/opt/IBM/ISC/PortalServer/update		PATH=$PATH:/opt/IBM/ISC/PortalServer/update
	export PATH		export PATH

	~~e salve o arquivo.~~		save and quit

	~~Faça o logoff e o logon~~, ~~após isso verifique como ficou o~~ PATH		Logoff and Logon, and check the PATH

	> echo $PATH		> echo $PATH
Line 82:		Line 82:
	"''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". O que resolvemos adicionando no PATH.		"''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". O que resolvemos adicionando no PATH.

			This step can seem strange, but after some attempts, I verified that during installation one script made the following command: "''cd /opt/IBM/ISC/PortalServer/update; updatePortal.sh''", being that the correct one would be "''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". What we decide adding in the PATH.

	== Confirme o hostname seja FQDN ==		== Confirme o hostname seja FQDN ==

Ebasso: /* Alterando as suas váriaveis de Ambiente para a IBM JVM */

2007-09-27T20:54:47Z

Alterando as suas váriaveis de Ambiente para a IBM JVM

← Older revision		Revision as of 20:54, 27 September 2007
Line 33:		Line 33:


	== ~~Alterando as suas váriaveis de Ambiente para a~~ IBM JVM ==		== Setting your environment for IBM JVM 1.4.2==
	~~Edite o arquivo~~ '''/etc/profile''' ~~e adicione as seguintes variaveis de ambiente~~		Modify your '''/etc/profile''' file, adding the following entries:

	PATH=$PATH:/opt/IBMJava2-142/jre/bin		PATH=$PATH:/opt/IBMJava2-142/jre/bin
Line 40:		Line 40:
	export PATH JAVA_HOME		export PATH JAVA_HOME

	~~e salve o arquivo~~.		save and quit.

	~~Faça o logoff e o logon~~, ~~após isso verifique a versão instalada da~~ JVM ~~da seguinte maneira~~:		Logoff and Logon again, after verify you JVM installed throw this command:

	> java -version		> java -version

	~~que no meu caso é~~		In my case:

	java version "1.4.2"		java version "1.4.2"
	Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)		Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
	Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20070708 (SR9) (JIT enabled: jitc))		Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20070708 (SR9) (JIT enabled: jitc))


	== Crie o diretório de update do Portal e altere o PATH ==		== Crie o diretório de update do Portal e altere o PATH ==

Ebasso: New page: Follow the next steps '''carefully''' for install Tivoli Storage Manager for Linux == Hardware == '''Have at least 1 GB of RAM for installation''' In my installation, i had problems w...

2007-09-27T20:49:56Z

New page: Follow the next steps '''carefully''' for install Tivoli Storage Manager for Linux == Hardware == '''Have at least 1 GB of RAM for installation''' In my installation, i had problems w...

New page

Follow the next steps '''carefully''' for install Tivoli Storage Manager for Linux

== Hardware ==
'''Have at least 1 GB of RAM for installation'''

In my installation, i had problems when my Virtual Machine (VM) has only 512MB of memory, ao give more memory, about 1 GB, the install happens without problems. When installer apply the required patchs, the ISC is startup and stopped many times, what generate many error in the all process.

== Installing requireds RPM packages ==

Install the following RPM packages in you Linux OS:

- compat-libstdc++-33
- compat-libstdc++-296
- libXp

if you are using yum, make as follow:

> '''yum -y install compat-libstdc++-33 compat-libstdc++-296 libXp'''

== Install IBM Java Virtual Machine ==

Download IBM Java 2 SDK version 1.4.2 and install in you system:

> rpm -ivh IBMJava2-142-ia32-SDK-1.4.2-9.0.i386.rpm

== Alterando as suas váriaveis de Ambiente para a IBM JVM ==
Edite o arquivo '''/etc/profile''' e adicione as seguintes variaveis de ambiente

PATH=$PATH:/opt/IBMJava2-142/jre/bin
JAVA_HOME=/opt/IBMJava2-142/jre
export PATH JAVA_HOME

e salve o arquivo.

Faça o logoff e o logon, após isso verifique a versão instalada da JVM da seguinte maneira:

> java -version

que no meu caso é

java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20070708 (SR9) (JIT enabled: jitc))

== Crie o diretório de update do Portal e altere o PATH ==

=== Criando o Diretório de update do Portal ===

'''Obs.:''' Na minha instalação estou utilizando o diretório '''/opt/IBM/ISC/''' ao invés de '''/opt/IBM/ISC601/'''.

Crie o diretório '''/opt/IBM/ISC/PortalServer/update''' através do seguinte comando

mkdir -p /opt/IBM/ISC/PortalServer/update

=== Altere o PATH ===

Edite o arquivo '''/etc/profile''' e adicione as seguintes variaveis de ambiente

PATH=$PATH:/opt/IBM/ISC/PortalServer/update
export PATH

e salve o arquivo.

Faça o logoff e o logon, após isso verifique como ficou o PATH

> echo $PATH

'''Obs.:''' Pode parecer estranho este passo, mas após algumas tentativas, verifiquei que durante a instalação um script fazia o seguinte comando: "''cd /opt/IBM/ISC/PortalServer/update;updatePortal.sh''" sendo que o correto seria
"''cd /opt/IBM/ISC/PortalServer/update;'''''./'''''updatePortal.sh''". O que resolvemos adicionando no PATH.

== Confirme o hostname seja FQDN ==

Confirme que o nome do host esteja na forma completa (Full Qualified Domain Name).Exemplo: tsmserver.minhaempresa.com.br

Outro exemplo:
> cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.15 tsmserver.minhaempresa.com.br tsmserver

== Altere o /etc/issue - Somente CentOS ==

O InstallShield verifica pelo sistema operacional instalado para saber se o mesmo é compatível ou não.
Podemos mascarar isso alterando o arquivo '''/etc/issue''' para que o mesmo pense que estamos instalando no Red Hat.

O original é o seguinte:

CentOS release 5 (Final)
Kernel \r on an \m

altere para:

Red Hat Enterprise Linux ES release 4 (Nahant Update 1)
Kernel \r on an \m

Efetue um logoff e logon novamente.