MSI Verify

Imperial Joined: 14 Jun 2004 Posts: 13

Hi,

wie geht Ihr bei euch mit MSI Applikationen im Bezug auf den Verify um?

Im Vergleich zu Radia Snapshot Paketen dauert der Verify bei MSI Paketen erheblich länger.

Wenn man mehrer große Pakete zugewiesen hat wird der Connect richtig lästig Sad

Ich habe schon überlegt den Verify bei MSI Paketen komplett zu deaktivieren, indem ich den entsprechenden Eintag in der ZVERIFY Methode raus nehme.

Was macht Ihr um den Connect in verträglichem Rahmen zu halten?

CU
TMag

Piccolo Joined: 13 Mar 2005 Posts: 2

one thing to do is set the zdisconn on the service to free up the connection to the manager. what that does is the clients gets its orders from the manager and disconnects (freeing up the connection to the manager for another client) and gets the files it needs from the stager/radia proxy. when the client is finished installing the service it will reconnect to the manager.

Other thing that will speed things up is on the msi file in the package change the location variable (i think) from http:\\localhost... to http:\\127.0.0.1 this will speed things up because it will not have to do name resolution all the time.

other thing is you can write a verify dialog rexx ... it is done just like a install rexx but for verify. You can decide if you need to do a verify. since a msi app normally will do some checking by itself sometimes the verify is not needed.

zyard

Imperial Joined: 14 Jun 2004 Posts: 13

staples wrote:

one thing to do is set the zdisconn on the service to free up the connection to the manager. what that does is the clients gets its orders from the manager and disconnects (freeing up the connection to the manager for another client) and gets the files it needs from the stager/radia proxy. when the client is finished installing the service it will reconnect to the manager.

ZDISCONN is set to Y by default in our environment. So I think I have this improvement already ;-|

staples wrote:

Other thing that will speed things up is on the msi file in the package change the location variable (i think) from http:\\localhost... to http:\\127.0.0.1 this will speed things up because it will not have to do name resolution all the time.

Where do you set the location variable? Is this DATAURL? This is also set to http://127.0.0.1... by default.

staples wrote:

other thing is you can write a verify dialog rexx ... it is done just like a install rexx but for verify. You can decide if you need to do a verify. since a msi app normally will do some checking by itself sometimes the verify is not needed.

The verify REXX is a very interesting idea. How do you call RADIAMSI in your REXX script? Do I have to use the ADDRESS command to call RADIAMSI or is this implemented in radrexxw?

CU
TMag

Piccolo Joined: 04 Apr 2005 Posts: 1

How about

radskman .......,ver=n,...

Piccolo Joined: 13 Mar 2005 Posts: 2

Quote:

ZDISCONN is set to Y

Very good, the older implementations this was set to N.

Quote:

Is this DATAURL? This is also set to http://127.0.0.1...

Very good, the older implementations this was set to http://localhost...

Quote:

The verify REXX is a very interesting idea. How do you call RADIAMSI in your REXX script? Do I have to use the ADDRESS command to call RADIAMSI or is this implemented in radrexxw?

On Novadigm's (HP's) website Search for "Dialog" processing or Install.rex... it is setup the same way as a install rex but the rex is Verify.rex.

Basically on the service you set dialog processing to yes. and then it will run the install.rex verify.rex delete.rex during the method being used. You have to promote the rexx files as dialog instances and create dialog services for them. The Novadigm technote basically walks you through it.