Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2013-09-05T18:15:08Z by RavikanthChavali
RavikanthChavali
RavikanthChavali
16 Posts
ACCEPTED ANSWER

Pinned topic Installation command executed for Push-to-client product upgrades & response file

‏2013-09-04T19:51:28Z |

For Product upgrades using push-to-client, what are the arguments that are executed with the install command. Is silent mode used? What is needed in the response file?

Updated on 2013-09-12T14:58:19Z at 2013-09-12T14:58:19Z by RavikanthChavali
  • RavikanthChavali
    RavikanthChavali
    16 Posts
    ACCEPTED ANSWER

    Re: What Installation command is executed for Push-to-client product upgrades

    ‏2013-09-05T18:15:08Z  in response to RavikanthChavali

    From Support team...

    RDz push-to-client launches Installation Manager in silent mode. It  obtains path for Installation Manager launcher program using  Installation Manager API, and pass the following arguments to the launcher:                                                              
                                                                           
    --launcher.ini <installation manager path>/silent-install.ini          
    -showprogress                                                          
    -input <response file name>                                            
    -acceptLicense                                                         
    -log <log file name>                                                   
                                                                           
    These arguments will be logged in the trace file if tracing is enabled and push-to-client launched the installation.

    When it comes to the response files, it is much easier to start with the most basic one that only has the "repository location" and the "offering id" and then add more requirements if needed. When the  Installation Manager (IM) generates the response file, it adds more information that is based on the local environment of that client machine. It is better not to have those since this is for push-to-client  across many users and machines, the less of the specific requirements mentioned in the response file, the easier it would be to make the upgrade across different machines because if the environment on each machine is not exactly the same, it will not work. For example if your machine has the 32-bit RDz version installed and you use IM to create the response file, it would add that information to the response file. And that response file would not work for another client that has 64-bit installed and needs an upgrade. But when that attribute is not in the response file, IM can handle it and just pass the upgrade whether it is for the 32-bit one or the 64-bit one. 

    You will notice in response1.xml, there are 2  "repository locations" and the "offering ids". This is because if you want to install and iFix for RDz 8.5.1.1, you must have had 8.5.1.1 installed on all client machines otherwise it will not do it. In this response file, if 8.5.1.1 is not installed, it will add that as well.

    There is no documentation that would show the relation between the silent mode install with nosplash and push-to-client. As you already know, What you need to have is:                                        
    - create a very simple response file                                   
    - add the silent mode with nospalsh attribute to it                    
    - use that response file for the push-to-client as this would be part of the "push-to-client metadata"                                          
                                                                           
    It is recommended to use imcl.exe command and pass parameters to it for updating/modifying packages.              

    Updated on 2013-09-12T14:53:55Z at 2013-09-12T14:53:55Z by RavikanthChavali