Verifying Installation Introscope V8

[Former Member]

Hello I am installating the Introscope Enterprise manager and I got these message:

I edited the installer_properties the installer path = /user/sap/ccms/wilyintroscope, and the file eula.txt with accept, the file eula.txt and the osgiPackages.v1.2.unix.tar I copied in the this folder /user/sap/ccms/wilyintroscope.

1.-

sidadm> ./introscope8.2.2.0hpuxIA64SAP.bin

Preparing to install...

WARNING: /tmp does not have enough disk space!

Attempting to use /home/sidadm for install base and tmp dir.

WARNING: The amount of /home/sidadm disk space required to perform this installation is greater than what is available. Please free up at least 637724 Kilobytes in /home/sidadm and attempt this installation again. You way also set the IATEMPDIR environment variable to a directory on a disk partition with enough fress disk space. To se the variable enter one of de follewing commands al the unix comand line prompt befor running this installer again:

.....

So I setted the variable, my directory is /var/Introscope_agent_V8 and executed the installer again and I got this text.

server:sidadm 24> setenv IATEMPDIR /var/Introscope_agentV8

server:sidadm 25> ./introscope8.2.2.0hpuxIA64SAP.bin

Preparing to install...

Extracting the JRE from the installer archive...

Unpacking the JRE...

Extracting the installation resources from the installer archive...

Configuring the installer for this system's environment...

Launching installer...

Preparing SILENT Mode Installation...

===============================================================================

Introscope (created with InstallAnywhere by Macrovision)

-

---

server:sidadm 26>

I want to check if the installation was succesfully but I didnt find any file in this path /user/sap/ccms/wilyintroscope

How do I check the installation is OK ? because I dont find the Introscope_installLog.log fle on server

Any suggestion ??

thanks

danny

[Former Member]

hi

chk the article here for verify installation

[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d4ea4c-63bc-2a10-0f9e-98e895c61112?QuickLink=index&overridelayout=true|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d4ea4c-63bc-2a10-0f9e-98e895c61112?QuickLink=index&overridelayout=true],

The installer does not give confirmation of successful installation on the console. To

confirm installation was successful:

1. Verify that the Introscope directory exists at:

u2022 <drive>:usrsapccmswilyintroscope (Windows)

u2022 /usr/sap/ccms/wilyintroscope (Unix, i5/OS)

OR the location you specified.

2. Open the file,

/usr/sap/ccms/wilyintroscope/install/Introscope_InstallLog.log.

3. Verify that the following lines appear at the top of the file:

Installation: Successful.

166 SUCCESSES

0 WARNINGS

0 NONFATAL ERRORS

0 FATAL ERRORS

Note: The number of successes may be different than what is shown in this example.

Check and update us.

Jansi

[Former Member]

Hi Danny,

You goto Willyintroscope/bin directory check EMCtrl.sh status

Above will give you Enterprise Manager running Status

Regards

Chandra

[raguraman_c]

The path /user/sap/ccms/wilyintroscope is empty so there is no way that he can check the status with EMCtrl

@Danny try to install with the option that I have provided in my previous reply.

Feel free to revert back.

-=-Ragu

[raguraman_c]

Hi,

change the parameter INSTALLER_UI in installer.properties, set value to CONSOLE. Then start the installation. This will give you the status in your screen.

This should solve your problem.

Feel free to revert back.

-=-Ragu

[Former Member]

Thanks for your answers

The Enterprise Manager is installed, I copied the all files in inique place (/usr/sap/ccms/wilyintroscope) and excuted again the installer.

My installation was succesfully with 0 errors. Now i want to start the Enterprise Manger in this path:

/usr/sap/ccms/wilyintroscope/bin

server:sidadm 16> ./EMCtrl.sh

WILYHOME: Undefined variable.

server:sidadm 17> ./EMCtrl.sh start

WILYHOME: Undefined variable.

server:sidadm 18>

I got this message :

WILYHOME: Undefined variable.

Any idea about this message

Thanks

Danny

[Former Member]

Hi folks,

I am also getting the same error when trying to start the EM. Kindly share your thoughts.

./EMCtrl.sh start

WILYHOME: Undefined variable

[Former Member]

Hello avinash

you try this :

1.- down the sap system (solman)

2.- restart the server

3.- up the sap system

4.- run the EMCtrl.sh with root user

./EMCtrl.sh start

5.- Check that Introscope is running properly

Locate the Enterprise Manager log at <Introscope_home>/logs/IntroscopeEnterpriseManager.log.

5.1. Check that the Enterprise Manager has started. Look for the following line in the logfile:

03/28/10 10:54:36 AM CET [INFO] [Manager] Introscope Enterprise Manager started.

5.2. Check the TCP port that Introscope Enterprise Manager is using for agent connections.

Look for lines similar to the following in the logfile:

[INFO] [Manager.PostOfficeHub] Server listening for incoming defaultsocket connections on port 6001

I did this task and now tHe EM is running

I hope this help you

Regards

Danny

[Former Member]

Hi Danny,

I could start the EM too, but in a different way. I changed the EMCtrl.sh script itself.

In the script under start config section, I entered the below lines and removed the two if...then loops.

1. |||||||||||||||||||| START CONFIGURATION SECTION ||||||||||||||||||||

WILYHOME=/usr/sap/ccms/wilyintroscope

export WILYHOME

Thanks for the suggestion though.

Edited by: avinash ravut on Sep 8, 2010 12:34 PM

[Former Member]

I noticed that the first line contained a space:

I changed the first line from

1. !/bin/sh

to

#!/bin/sh

After that I was able to start the Enterprice manager.

Kind regards,

Richard Meijn

[Former Member]

thx for this

[tomas_lindberg]

The solution from Richard worked for me, Thanks.

Btw: I did not get the error when i installed it wirh root account, but when i installed with <sid>adm this appeared.

[former_member246069]

Thanks danny.. I too faced the same issue and was successful when tried with root user