ISEE on OpenVMS I64 reconfig

[Ulf Ohlsson Lidholm]

Hi!

Problem: Automated entitlement check wanted.

Scenario: Upgrade of OpenVMS from 8.2-1 to 8.3
The Upgrade is made by restoring a complete image from a reference system to a separate disk. Nodespecific data is saved and restored to the "new" system disk. Config data for ISEE and WEBES are saved:

profile.txt, webes_reg_common_info.txt, desta.reg, webes_reg_mail_info.txt, notifyca.txt, motprefs.

The directory-name of the reference server is renamed to same as
'F$GETSYI("NODENAME")'

The SPOP is defined.

ISEE Stopped

ISEE Started

Is there a way to get ISEE to start (and get full communication) with the SPOP without having to access the ISEE URL: http://'nodename':5060/start.html

Could this be solved by executing:
$ @SYS$SYSDEVICE:[VMS$COMMON.HPSERVICES._COMMON_.REMOTESUPPORT.BIN]ISEEHELLO.COM

We have a LARGE number of servers that will be upgraded, solving this in a way that it could be fully automated is prefferred.

Rgds.

Ulf Olsson-Lidholm
OpenVMS Product Responsible
IKEA IT
SWEDEN

[Liem Nguyen]

Hi,

Normally, if you just upgrade the OS then there is no need to do anything with ISEE & Webes.

However, since you do the upgrade from an image, I am not sure if ISEE is still working.

What you need to do to check:
1. Make sure ISEE and Webes exist on the Server:
$ PRODUCT SHOW PRODUCT ISEE
$ PRODUCT SHOW PRODUCT WEBES

NOTE: Current ISEE version is A.03.95.36 and WEBES 5.1

2. You can also issue this command:
$ DIR ISEE$HPSERVICES

If ISEE is properly installed, you can use either ISEEHELLO or reconnectToServer command to test the communication between a Server and SPOP.

You can also run "wsea test" command to generate a webes test incident.

If you see these incidents on your SPOP, then you're fine.

Question: Why can't you logon to ISEE GUI port 5060?

Hope this help,

[Ulf Ohlsson Lidholm]

Hi!

Both ISEE and WEBES are installed on the reference system (from whom we get the image).

I got a tip to trigger a test notification to the SPOP and HP with the command:

$ WSEA TES NOSYS

The reason for not wanting to use the Web Interface is that it takes a lot of time to log on, check contact info, resubmit data.

We have more than 200 systems world-wide that we will update.

To automate this could save many hours of installation time (during night) ...

Rgds.

>>> Ulf

[Ulf Ohlsson Lidholm]

Hi!

Both ISEE and WEBES are installed on the reference system (from whom we get the image).

I got a tip to trigger a test notification to the SPOP and HP with the command:

WSEA TES NOSYS

The reason for not wanting to use the Web Interface is that it takes a lot of time to log on, check contact info, resubmit data.

We have more than 200 systems world-wide that we will update.

To automate this could save many hours of installation time (during night) ...

Rgds.

>>> Ulf

[Liem Nguyen]

You've said:
Both ISEE and WEBES are installed on the reference system (from whom we get the image).
------

This is not supported and all of the Servers that got the same image will NOT work, you have to remove and reinstall ISEE Client software.

The reason being is:
When you install ISEE on a Server, this Server gets a unique key ID (GUID). If you take the image of this Server to create other Servers, all of them now have the same unique ID.

HP Backend thinks you only have ONE server since all of them share the same ID.

If you want to speed up the installation process, you can use the procedure "Installing ISEE in an Enterprise environment".

Hope this helps,