Pls has anyone packaged SAP GUI 6.2 before?. I actually need some guide lines on how to start.

Giz
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Sap uses an installer of it's own. I don't know if it's a good idea to package this.
What we did: package a GUI around the original installer, so people "see" something is being installed and do not turn off the workstation or try to start SAP. Looking at the amount of upgrades on SAP (over here anyways.. [;)]) we decided on not to package SAP. Updates are being deployed with a GUI in the form of an MSI, which calls the original installer and commandline. The GUI tells people the setup/update is being run. Tells them to close SAP during the install/update. Makes patching a lot easier and highly reduces the amount of failed installations. Might be something to consider.
Answered 02/20/2006 by: neo2000
Purple Belt

Please log in to comment
0
@neo2000 - "snap" [8D]
Answered 02/21/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
Am not actually packaging the while SAP GUI 6.2. i only check two of the features. The problem is while packaging, the merge module involved (SQLSVR.MSM) is always giving problems. Don't know if to remove it from the package or leave it. If the msm is included in the package, it brings out an error during installation but if the msm is excluded the package is fine.

Pls any suggestions?

Giz
Answered 02/22/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Let me guess: when installing it's prompting that the version of Internet Explorer is not up-to-date?
Answered 02/22/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
I got around that error already but the error am talking about is always saying "

A STRONG PASSWORD IS REQUIRED FOR SECURITY RESONS. PLEASE USE SAPWD SWITCH TO SUPPLY THE SAME. REFER TO README FOE MORE DETAILS. SETUP WILL NOW EXIT."

Giz
Answered 02/22/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Ahh, you must be using the SP3 merge module of MSDE.

This error is happening because the public property BLANKSAPWD (or something similar) is not set. And therefore you just specify a public property SAPWD with the sa password for the MSDE installation.
Answered 02/22/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
Tnx 4 ur help. Pls how do i resolve this pls. Do i need to download SP4 merge module of MSDE? If u can gimme a link to to download, i wld appreciate.

Giz
Answered 02/22/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Well, the easiest method would be to just add a new row to the Property table:
SAPWD = sa

Otherwise, if you want to deploy a more secure MSDE you should download the latest setup from http://www.microsoft.com/downloads/details.aspx?FamilyID=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en and follow the instructions in the readme.
Answered 02/22/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
Tnx. Am i adding that new property to the resulting msi or the msm itself? and which msm should i use sqlsvr.msm?

Giz
Answered 02/22/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Because merge modules MERGE with your existing MSI, you will place this public property into the MSI package.

As you probably read in that link I sent you, there are several different SQL/MSDE merge modules available. The 'sqlsvr.msm' merge module is the core sql files.
Answered 02/22/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
i'ved added the SAPWD to the PROPERTY TABLE but still getting the

"A STRONG PASSWORD IS REQUIRED FOR SECURITY RESONS. PLEASE USE SAPWD SWITCH TO SUPPLY THE SAME. REFER TO README FOE MORE DETAILS. SETUP WILL NOW EXIT."

Giz
Answered 02/22/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Can you open up the merge module and ensure that it is not just a wrapper that calls the MSDE setup.exe?
Answered 02/22/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
Even this SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE when finished downloading and u want to run the setup it extracted will also bring up that same error.

The funny thing is when i used installshield, i had no probs with the merge modules but iwth Wise package studio 5, loads of problem. We are only allowed to package with Wise package studio.

Giz
Answered 02/22/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
TMX BHUNTER. U'VE BEEN OF GREAT HELP.

GIZ
Answered 02/23/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Snap..? [8|]
Answered 03/14/2006 by: neo2000
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity