1 2 Previous Next 17 Replies Latest reply on Oct 3, 2013 4:32 PM by Edwin Lindeman

    Grammar File for .iss response files

    Edwin Lindeman

      Hi working with customer and they are wanting to import an .iss reponse file as a configuration object.  The the closes grammar file to parse this file is Windows INI file.  However were seeing some unusual results or maybe its BSA not properly parsing the file. When we import the data into a BLPackage as a configuration object trying different grammar files to see if we can see all the data we lose some content.  When we attempt to deploy the package out to a target we lose some content and therefore fail on running our silent install. Any thoughts or suggestions on this?  Has anyone successfully imported and deployed an .iss response file via BSA/Configuration Object. Thank you

        • 1. Re: Grammar File for .iss response files
          Joe Piotrowski

          If I'm not mistaken, different installers use different response file formats. Can you post the contents of your ISS file?

           

          If there is no built-in grammar that will handle this file, I read a post a while ago about building your own grammar file. But I can't seem to find the reference for it. Does anyone know where that document is?

          • 2. Re: Grammar File for .iss response files
            Edwin Lindeman

            Hi Joe Below is the contents, as for creating your own I saw the document just haven't taken the time to fully review it so figured I would reach out to the community to see if someone already posted anything. Regards

             

             

            [InstallShield Silent]

            Version=v7.00

            File=Response File

            [File Transfer]

            OverwrittenReadOnly=NoToAll

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-DlgOrder]

            Dlg0={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdWelcome-0

            Count=13

            Dlg1={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskOptions-0

            Dlg2={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdLicense-0

            Dlg3={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdShowInfoList-0

            Dlg4={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdAskDestPath-0

            Dlg5={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskText-0

            Dlg6={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskOptions-1

            Dlg7={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskPath-0

            Dlg8={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskText-1

            Dlg9={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdShowInfoList-1

            Dlg10={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdShowDlgEdit3-0

            Dlg11={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-MessageBox-0

            Dlg12={1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdFinish-0

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdWelcome-0]

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskOptions-0]

            Result=1

            Sel-0=1

            Sel-1=0

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdLicense-0]

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdShowInfoList-0]

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdAskDestPath-0]

            szDir=C:\Program Files\New Atlanta\ServletExec AS

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskText-0]

            szText=testserver

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskOptions-1]

            Result=1

            Sel-0=1

            Sel-1=0

            Sel-2=0

            Sel-3=0

            Sel-4=0

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskPath-0]

            szPath=C:\InetPub\Scripts\

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-AskText-1]

            szText=8888

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdShowInfoList-1]

            Result=1

            [Application]

            Name=ServletExec AS

            Version=6.0

            Company=New Atlanta Communications

            Lang=0009

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdShowDlgEdit3-0]

            szEdit1=admin

            szEdit2=testpass

            szEdit3=testpass

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-MessageBox-0]

            Result=1

            [{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdFinish-0]

            Result=1

            bOpt1=0

            bOpt2=0

            • 3. Re: Grammar File for .iss response files
              Joe Piotrowski

              So my quick review would be that we want to parse the data within [] as an entry, and anything underneath that would be a sub-entry. So if we viewed this as a configuration file in BSA it would look like this:

              +[InstallShield Silent]

              +[File Transfer]

              +[{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-DlgOrder]

              +[{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdWelcome-0]

              ...

               

              And if we expand an entry we would see additional properties and values:

              -[InstallShield Silent]

                   +Version=v7.00

                   +File=Response File

              +[File Transfer]

              +[{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-DlgOrder]

              +[{1E48D4FA-D507-11D3-B4BF-00104B311D5E}-SdWelcome-0]

              ...


              Is that your expectation?

              • 4. Re: Grammar File for .iss response files
                Edwin Lindeman

                Hi Joe

                 

                That is the expectation.  We tried using the Windows INI grammar file and it looks close but something happens to the file when we deploy to the target where the executable wanting to read the file can no longer read it.

                 

                Regards

                • 5. Re: Grammar File for .iss response files
                  Joe Piotrowski

                  I'm hoping that we can leverage an existing grammar and we just have to find it. If not, find one that's close, and modify it for your needs. Unfortunately, I've never created or modified our grammar files, so I'm hoping someone who has will chime in. I will try to experiment with this when I have time today. What version of BSA is this?

                  • 6. Re: Re: Grammar File for .iss response files
                    Joe Piotrowski

                    I tried all of the grammar files and the Windows INI file grammar (ini.gm) works perfectly for me. What are you seeing?

                    response01.jpg

                    response02.jpg

                    • 7. Re: Grammar File for .iss response files
                      Joe Piotrowski

                      Keep in mind that Configuration Files always have to exist in the same location and have the same name. So if I create a Configuration File "C:\temp\response.iss" the name of the file and the location have to match this. If the response file is a different name or in a different location, it won't work.

                      • 8. Re: Grammar File for .iss response files
                        Bill Robinson

                        if you are trying to swap out values in the file, why not use the response files in the depot software for this - i believe that will swap out place holders in the file for property values before the install command runs.

                        • 9. Re: Re: Grammar File for .iss response files
                          Joe Piotrowski

                          I have not used the InstallShield software package before. I was not aware that you could pass it parameters to the response file. Is that what you mean Bill? It requires an Install and Uninstall response file to run.

                          installShield.jpg

                          • 10. Re: Grammar File for .iss response files
                            Edwin Lindeman

                            Joe, The data looks correct using the Windows.ini grammar file when I do a live browse and it seems to be OK but when I deploy the contents seem to get shifted and I lose some content. So when the setup.exe attempts to use the .iss (response file) it errors out. If I copy the data from its original file and copy it into the deployed .iss file (overwriting the content) it works. Bill I haven't tried what you mentioned. I will definitely look into it. Regards

                            • 11. Re: Grammar File for .iss response files
                              Joe Piotrowski

                              What does "deploy the contents" mean? Are you using a BLPackage to make configuration value changes to this response file before the installation?

                              • 12. Re: Grammar File for .iss response files
                                Edwin Lindeman

                                Hi Joe yes using a Bl Package with a configuration file and modifying those values before installation.

                                • 13. Re: Grammar File for .iss response files
                                  Joe Piotrowski

                                  Can you give me an example? What value(s) are you trying to deploy that aren't getting replaced properly?

                                  1 of 1 people found this helpful
                                  • 14. Re: Grammar File for .iss response files
                                    Edwin Lindeman

                                    Hi Joe Sorry for delay in response here. I'll get you that information here soon. Thank you

                                    1 2 Previous Next