You can use Installation Manager to install this feature pack silently.
Perform the following actions before you install the feature pack.
Perform this procedure to install the feature pack silently.
<?xml version="1.0" encoding="UTF-8"?> <!-- ##### Copyright ###################################################### # Licensed Materials - Property of IBM # 5724-H88, 5724-J08, 5724-I63, 5724-H89 (c) Copyright IBM Corp. 2010. # All Rights Reserved. US Government Users Restricted Rights-Use, duplication # or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ####################################################################### --> <!-- ##### Frequently Asked Questions ##################################### # The latest information about using Installation Manager is # located in the online Information Center. There you can find # information about the commands and attributes used in # silent installation response files. # # Installation Manager Information Center can be found at: # http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp # # Question 1. How do I record a response file using Installation Manager? # Answer 1. Start Installation Manager from the command line with the # record parameter and it will generate a response file containing actions # it performed, repositories it used, and its preferences settings. # Optionally use the -skipInstall parameter if you do not want the product # to be installed to the machine. Specify a new agentDataLocation location # value when doing a new installation. Do not use an existing # agentDataLocation for an installation because it might damage the # installation data and prevent you from modifying, updating, rolling back, # or uninstalling the installed packages. # # Windows: IBMIM -record <responseFile> -skipInstall <agentDataLocation> # Linux or UNIX: ./IBMIM -record <responseFile> -skipInstall <agentDataLocation> # # For example: # Windows = IBMIM.exe -record c:\temp\responsefiles\FEP.install.xml # -skipInstall c:\temp\skipInstall\WebSphere_Feature_Pack # Linux or UNIX = ./IBMIM -record /home/user/responsefiles/FEP.install.xml # -skipInstall c:\temp\skipInstall\WebSphere_Feature_Pack # # Question 2. How do I run Installation Manager silently? # Answer 2. Create a silent installation response file and submit it to # Installation Manager on the command line: # # Windows = IBMIMc.exe -silent -input <path and file name of response file> # Linux or UNIX = ./IBMIM -silent -input <path and file name of response file> # # For example: # Windows = IBMIMc.exe -silent -input c:\temp\responsefile\FEP.install.xml # Linux or UNIX = ./IBMIM -silent -input /home/user/responsefile/FEP.install.xml # # Note that Windows uses IBMIMc.exe, whereas Linux and UNIX uses IBMIM.exe. # Do not use the command IBMIM.exe on Windows systems for silent installations. # Do not use the command IBMIMc.exe on Linux and UNIX operating systems. # # Question 3. How do I store and pass credentials to repositories that # require authentication? # Answer 3. Installation Manager uses a key ring file to store encrypted # credentials for authenticating with repositories. Follow this two-step # process for creating and using a key ring file with Installation Manager. # # First, create a key ring file with your credentials by starting # Installation Manager from the command line with the keyring parameter. # Use the optional password parameter to password protect your file. # # Windows = IBMIM.exe -keyring <path and file name> -password <password> # Linux or UNIX = ./IBMIM.exe -keyring <path and file name> -password <password> # # Installation Manager will start in graphical mode. Verify that the # repositories to which you need to authenticate are included in the # preferences, File / Preferences / Repositories. If they are not # listed, then click Add Repositories to add the URL or UNC path. # Installation Manager will prompt for your credentials. If the repository # is already in the list, then any attempt to access the repository location, # such as clicking the Test Connections button, will also prompt for your # credentials. Enter the correct credential and check the Save password # checkbox. The credentials are saved to the key ring file you specified. # # Second, when you start a silent installation, provide Installation # Manager with the location of the key ring file and the password if # the file is protected. For example: # # Windows = IBMIMc.exe -silent -input <path and file name of response file> # -keyring <path and name of key ring file> -password <password> # Linux / UNIX = ./IBMIM -silent -input <path and file name of response file> # -keyring <path and name of key ring file> -password <password> # ####################################################################### --> <!-- ##### License Agreement ############################################## # By changing the acceptLicense attribute in this response file to true, # you agree that you reviewed and agree to the terms of the IBM # International Program License Agreement accompanying this program. # If you do not agree to these terms, do not change the value or otherwise # download, install, copy, access, or use the program and promptly return # the program and proof of entitlement to the party from whom you acquired # it to obtain a refund of the amount you paid. # # Valid values for acceptLicense: # true = Accepts the license and product installation will occur. # false = Declines the license and product installation will not occur. # # The clean and temporary attributes specify the repositories and other # preferences Installation Manager uses and whether those settings # should persist after the installation finishes. # # Valid values for clean: # true = only use the repositories and other preferences that are # specified in the response file. # false = use the repositories and other preferences that are specified # in the response file and Installation Manager. # # Valid values for temporary: # true = repositories and other preferences specified in the response # file do not persist in Installation Manager. # false = repositories and other preferences specified in the response # file persist in Installation Manager. # ####################################################################### --> <agent-input acceptLicense='false' clean='true' temporary='true'> <!-- ##### Repositories ################################################### # Repositories are locations that Installation Manager queries for # installable packages. Repositories can be local (on the machine # with Installation Manager) or remote (on a corporate intranet or # hosted elsewhere on the internet). # # If the machine using this response file has access to the internet, # then include the IBM WebSphere Live Update Repositories in the list # of repository locations. # # If the machine using this response file cannot access the internet, # then comment out the IBM WebSphere Live Update Repositories and # specify the URL or UNC path to any intranet repositories and # directory paths to local repositories to use. # ####################################################################### --> <server> <!-- ##### IBM WebSphere Live Update Repositories #################### # These repositories contain WebSphere Application Server Feature Packs, # updates for those feature packs, and import repositories for # WebSphere Application Server version 7. # # To use the secure repository (https), you must have an IBM ID, # which can be obtained by registering at: http://www.ibm.com/account # # And, you must use a key ring file with your response file. ################################################################## --> <repository location='http://public.dhe.ibm.com/software/websphere/repositories'/> <repository location='https://www.ibm.com/software/rational/repositorymanager/repositories/websphere'/> <!-- ##### Custom Repositories ####################################### # Uncomment and update the repository location keys below # to specify URLs or UNC paths to any intranet repositories # and directory paths to local repositories to use. ################################################################## --> <!--<repository location='/home/user/repositories/ariesjpa_and_import_repositories/local-repositories'/> --> <!-- ############################################################ # Uncomment and update this line when using a local repository # containing WebSphere Application Server Feature Pack for OSGi Applicaitons and # Java Persistence API 2.0 fixpacks. ############################################################# --> <!-- <repository location=''/> --> </server> <!-- ##### Import IBM WebSphere Application Server version 7 ############## # Because WebSphere Application Server version 7 is installed using # a different installation technology, it has to be imported into # Installation Manager before any feature packs can be installed. # # If the installation of WebSphere Application Server version 7 # that will be the target of this feature pack installation # has not been imported, then you must uncomment the profile command # below to register it with Installation Manager and then update the # import command with a profile id that matches the id created in the # profile command. If the specified profile ID exists, you must also # change the profile ID. Profile IDs are listed in 'installed.xml' in # the 'IBM Installation Manager Application Data' folder. # # If the installation of WebSphere Application Server version 7 # was imported previously, then registering it with Installation # Manager is not required. However, the target installation should # be imported again to ensure that the current state of WebSphere # Application Server installation matches exactly with what is # in the list of installed packages. # # The installationLocation attribute specifies the directory path to # an existing installation of WebSphere Application Server. # # The profile id attribute specifies the package group name assigned # to the imported installation of WebSphere Application Server. The # example below illustrates a profile id for Network Deployment edition, # but the id should be customized for your installation. Profile ids # must be unique within the instance of Installation Manager using # the response file. # # The eclipseLocation data key should use the same directory path to # WebSphere Application Server as the installationLocation attribute. # # Set the user.import.profile data key to true to import # the installation of WebSphere Application Server version 7. # # The user.cic.imported data key must be paired with the offering ID # key that matches the edition of WebSphere Application Server to import. # Valid WebSphere Application Server offering ID values are: # com.ibm.websphere.EXPRESS.v70 # com.ibm.websphere.EXPRESSTRIAL.v70 # com.ibm.websphere.BASE.v70 # com.ibm.websphere.BASETRIAL.v70 # com.ibm.websphere.ND.v70 # # Other feature packs that were previously installed should be # imported as well. Add each existing feature pack that needs to # be imported as a new data key in the profile command. # Several feature pack offering ID values are: # com.ibm.websphere.SCA.v10 # com.ibm.websphere.XML.v10 # com.ibm.websphere.CEA.v10 # com.ibm.websphere.ARIESJPA.v10 # # In the import command, the profile attribute must match the # profile id for the targeted installation of WebSphere Application # Server. If the installation was imported previously, then its # profile id can be found in the installed.xml file located in # the application data location for Installation Manager. # ####################################################################### --> <!-- <profile installLocation='/home/user/IBM/WebSphere/AppServer' id='IBM WebSphere Application Server - ND'> <data key='eclipseLocation' value='/home/user/IBM/WebSphere/AppServer'/> <data key='user.import.profile' value='true'/> <data key='user.cic.imported,com.ibm.websphere.ND.v70' value='WAS'/> <data key='user.cic.imported,com.ibm.websphere.featurepackID.v10' value='WAS'/> </profile> --> <import type='WAS' profile='IBM WebSphere Application Server - ND'/> <!-- ##### Installation Packages ########################################## # Use the install command to inform Installation Manager of the # installation packages to install. # # The offering ID attribute is required because it specifies the # offering to be installed. The offering listed must be present in # at least one of the repositories listed earlier. The example # command below contains the offering ID for this feature pack. # # The profile attribute is required and must match the profile ID # of the targeted installation of WebSphere Application Server # version 7 used earlier. # # The version attribute is optional. If a version number is provided, # then the offering will be installed at the version level specified # as long as it is available in the repositories. If the version # attribute is not provided, then the default behavior is to install # the highest version available in the repositories. # # The features attribute is optional. Offerings always have at least # one feature; a required core feature which is installed regardless # of whether it is explicitly specified. If other feature names # are provided, then only those features will be installed. # The default setting is installing all of them together. # # The possible feature values of WebSphere Application Server Feature # Pack for JPA/OSGi could be: # 'fep.eba.core.feature', # 'fep.jpa.core.feature', # or both. # # Interim fixes for offerings can also be installed while they # are being installed by including the offering ID for the interim # fix and specifying the profile ID. # ####################################################################### --> <install modify='false'> <offering id='com.ibm.websphere.ARIESJPA.v10' profile='IBM WebSphere Application Server - ND' features='fep.eba.core.feature,fep.jpa.core.feature'/> <!-- <offering id='PM12345_FEATUREPACK' profile='IBM WebSphere Application Server - ND'/> --> </install> <!-- ##### Shared Data Location ########################################### # Uncomment the preference for eclipseCache to set the shared # data location the first time you use Installation Manager # to do an installation. # # Eclipse cache location can be obtained from the installed.xml file found in # Linux/Unix: /var/ibm/InstallationManager # Windows: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager # from the following property: # <property name='cacheLocation' value='C:\Program Files\IBM\AppServer-Shared'/> # # Open in a text editor, it has a style sheet which will hide this value if opened in a browser. # For further information on how to edit preferences, please refer to the public liabrary at: # http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp?topic=/com.ibm.silentinstall12.doc/topics/r_silent_prefs.html # # After the shared data location is set, it cannot be changed # using a response file or the graphical wizard. # # Ensure that the shared data location is a location that can be written # to by all user accounts that are expected to use Installation Manager. # ####################################################################### --> <!-- <preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='/home/user/IBM/WebSphere/IMShared'/> --> <!-- ##### Preferences Settings ########################################### # Additional preferences for Installation Manager can be specified. # These preference correspond to those that are located in the graphical # interface under File / Preferences. # # If a preference command is omitted from or commented out of the response # file, then Installation Manager uses the preference value that was # previously set or the default value for the preference. # # Preference settings might be added or deprecated in new versions of # Installation Manager. Consult the online Installation Manager # Information Center for the latest set of preferences and # descriptions about how to use them. # # http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp # ####################################################################### --> <!-- <preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/> <preference name='com.ibm.cic.common.core.preferences.readTimeout' value='30'/> <preference name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount' value='0'/> <preference name='offering.service.repositories.areUsed' value='true'/> <preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode' value='false'/> <preference name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication' value='false'/> <preference name='http.ntlm.auth.kind' value='NTLM'/> <preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/> <preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/> <preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles' value='false'/> <preference name='PassportAdvantageIsEnabled' value='false'/> <preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/> --> </agent-input>
You must create a new profile with OSGi Applications or Java Persistence API 2.0 feature functionality or augment an existing profile with the feature in order to use the feature's functionality. In addition, the deployment manager for a feature-enabled managed node must be augmented with the feature.
In this information ...Related information
| IBM Redbooks, demos, education, and more(Index) |