Best Practices for Installing WebSphere Application Server V7 Feature Packs

Transcription

1 IBM Software Group Best Practices for Installing WebSphere Application Server V7 Feature Packs Joseph Mertzlufft Vishavpal Shergill WebSphere Application Server L2 Support 27 October 2011 WebSphere Support Technical Exchange

2 Agenda Introduction Repositories Import Graphical Interface Silent Install Important Directories Best Practices WebSphere Support Technical Exchange 2 of 58

3 INTRODUCTION WebSphere Support Technical Exchange 3 of 58

4 Introduction to Installation Manager IBM Installation Manager (IM) is an application that simplifies downloading, installing, updating, and uninstalling many IBM software products from a single user interface Starting with WebSphere Application Server v7.0, Feature Pack install and update is performed using Installation Manager V7.0 Application Server and Java TM SDK updates continue to be performed with Update Installer WebSphere Support Technical Exchange 4 of 58

5 ISMP vs. Installation Manager ISMP former installation technology Install, Uninstall and Update processes required different programs Each Feature Pack required separate install program Fix pack in.pak format Obtaining Feature Pack or fix pack downloads is separate process IBM Installation Manager (IM) Single interface to install, update, uninstall many IBM software products Use local or Web repositories Ability to download packages integrated into IM Single IM instance can manage multiple products Replaces dedicated installers and uninstallers and maintenance tools Simplifies product maintenance WebSphere Support Technical Exchange 5 of 58

6 REPOSITORIES WebSphere Support Technical Exchange 6 of 58

7 Repositories Repositories are locations that Installation Manager queries for installable packages Web Repositories Internet access required Feature Pack Fix pack for Feature Packs Note that those URLs are input into IM, not your web browser Local Repositories download from IBM.com and store locally Download from Support Site as.zip format Feature Pack Fix Pack WebSphere Support Technical Exchange 7 of 58

8 IMPORT WebSphere Support Technical Exchange 8 of 58

9 Import Must use Import feature for Installation Manager to recognize WebSphere Application Server V7.0 Must do this before installing a feature pack for the first time The Import button is only visible after a WebSphere repository has been added to the repository list Application Server fix pack and Java SDK fix pack level must match before performing Import Example: Application Server has been updated with Fix Pack 17 (V ), so Java SDK must also be updated with Fix Pack 17. WebSphere Support Technical Exchange 9 of 58

10 NOTE: You can only select the shared resources directory the first time you install a package with the IBM Installation Manager. All other installations of WSAS X on the same system will use the same Shared Resources directory. WebSphere Support Technical Exchange 10 of 58

11 GRAPHICAL INTERFACE: INSTALL, UPDATE, UNINSTALL, and ROLLBACK WebSphere Support Technical Exchange 11 of 58

12 Installation Manager graphical options WebSphere Support Technical Exchange 12 of 58

13 Installation Manager graphical options WebSphere Support Technical Exchange 13 of 58

14 Install IBM Software Group With Web Repositories With Local Repositories If checked will list all available offerings WebSphere Support Technical Exchange 14 of 58

15 Update IBM Software Group With Web Repositories With Local Repositories Select recommended is checked in both cases above. WebSphere Support Technical Exchange 15 of 58

16 Rollback IBM Software Group Example: XML is installed and Rollback option is chosen. Install Sequence was: XML XML XML Will Roll back to (last installed) Will Roll back to (GA version) WebSphere Support Technical Exchange 16 of 58

17 Uninstall IBM Software Group Example: XML was previously installed. Choosing Uninstall option and selecting XML option will uninstall entire Feature Pack. If checked will uninstall Application Server Will uninstall complete Feature Pack WebSphere Support Technical Exchange 17 of 58

18 PERFORMING SILENT OPERATIONS WebSphere Support Technical Exchange 18 of 58

19 Silent Install Silent install is performed using a response file Sample response file from Information Center are available Response file can also be recorded Response file is xml format Same command (such as imcl ) is used for installing, uninstalling, updating, or rolling back Only need to change options in the response file in order to perform different operations A single response file can perform multiple operations; i.e., Import WSAS, install two feature packs, install fix packs on feature packs all in a single session WebSphere Support Technical Exchange 19 of 58

20 Silent Install Sample command (v1.4.4) from INSTALL_LOCATION\eclipse\tools UNIX :./imcl -input /temp/install.xml -acceptlicense -showprogress WINDOWS : imcl -input C:\install.xml -acceptlicense -showprogress imcl -help will list options available with imcl command An interactive console mode is available in Installation Manager; however, it is not supported WSAS V7 Feature Packs Learn to use response files with WSAS V7 Feature Packs WebSphere Support Technical Exchange 20 of 58

21 Recording mode and skipinstall mode Recording mode allows you to generate a response file by recording the actions taking place in the graphical interface skipinstall mode allows IM to operate in a mode where it does not actually install, update, or uninstall packages This mode maintains a dummy set of IM data (known as agent data ) which persists you can use the dummy data again later Does require an actual WSAS V7.0 install to be present, but Feature Packs are not actually installed or uninstalled Both modes can be combined Example command-line (Windows): IBMIM.exe -skipinstall C:\dummyIMdata -record C:\project\installXML.xml WebSphere Support Technical Exchange 21 of 58

22 Recording a response file IM graphical interface will indicate that it is recording response file Installation Manager In Record Mode Don t specify IM's true agent data directory with skipinstall recommend using a dummy repository instead Once response file is recorded, you can use it on another system Be sure to edit the response file so paths match those on the system where the install is taking place Keep the same dummy agent data directory to allow you to record response files for future updates, installs, or uninstalls for the same environment when using -skipinstall Sample response file on next page WebSphere Support Technical Exchange 22 of 58

23 Application Server Details IMPORT Repository Details Shared Resource Directory Install Options WebSphere Support Technical Exchange 23 of 58

24 <agent-input> section Purpose: Set global options for this IM session Example: Recommended for most circumstances <agent-input clean= true temporary= true > clean determines whether other preferences in response file are used true only use the repositories and other preferences specified in this response file false use the repositories and other preferences that are specified in this response file and Installation Manager's preferences temporary determines if settings are saved to persistent preferences 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 Versions prior to IM also used a required option named acceptlicense='true'. This option is deprecated as of IM and higher. Use command-line option -acceptlicense instead WebSphere Support Technical Exchange 24 of 58

25 <server> section Purpose: Provide locations for respositories Example: Local repositories for XML feature pack <server> <repository location='c:\imaix\xml_and_import_repositories\local-repositories'/> <repository location='c:\imaix\xml fp\xml fp'/> <repository location='c:\imaix\was.7.0.import'/> </server> When using same response file on different system, ensure the repository location specified in response file is correct WebSphere Support Technical Exchange 25 of 58

26 <profile> section Purpose: Provide details about product to be modified Example: Application server product installed on Linux <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'/> </profile> InstallationLocation specifies the directory path to an existing installation of WebSphere Application Server V7.0. Id package group name assigned to the imported installation of WebSphere Application Server. If the product is already imported, then use the same name that has been used previously. The installed.xml file under the agent data directory tracks which profile ID names are in use. Consult that file to determine which name is associated with an alreadyimported product. (More details about the agent data later.) WebSphere Support Technical Exchange 26 of 58

27 Data keys in <profile> section Example: Application server product installed on Linux <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'/> </profile> eclipselocation must set this to same value used for installlocation user.import.profile set to 'true' to perform Import of WebSphere product It is okay to set this to 'true' even if product has already been imported. user.cic.imported Set value to the offering ID key that matches the product edition: 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 WebSphere Support Technical Exchange 27 of 58

28 <import> section Purpose: Provide additional information for import process Example: Importing a Network Deployment installation <import profile='ibm WebSphere Application Server - ND' type='was'/> This data is required if performing an import, and has no effect (can be omitted) if not performing an import profile specifies the name of the package group you will associate with this product installation. Must set this to the same value used in the <profile> section. If the product has already been imported before, then this value must match the value used previously. (More details about this later this value can be retrieved from 'installed.xml'.) type always set to 'WAS'. WebSphere Support Technical Exchange 28 of 58

29 <install> section Purpose: Declare which packages to install or update Example: Install or update XML to V <install modify='false'> <offering id='com.ibm.websphere.xml.v10' version=' _1332' profile='ibm WebSphere Application Server - ND' features='fep.xml.core.feature' /> </install> modify option determines whether you are adding a sub-feature to an already-installed product; e.g., adding the SDO feature to an already-installed SCA feature pack. Note that feature packs themselves (CEA, SCA, XML, etc.) are not sub-features. Most of the time, you will use modify='false'. offering section each offering section instructs IM to install a package. The offerings determine which repositories (or parts of repositories) are installed. You can use these to install a new feature pack or upgrade an existing feature pack with a fix pack. Multiple offerings can be listed in an <install> section in order to install or update multiple feature packs in a single IM session. WebSphere Support Technical Exchange 29 of 58

30 <offering> section in <install> Purpose: Declare a single package to install Example: Install or update XML to V <install modify='false'> <offering id='com.ibm.websphere.xml.v10' version=' _1332' profile='ibm WebSphere Application Server - ND' features='fep.xml.core.feature' /> </install> id required parameter specifies the name of a package to be installed. The package needs to be part of at least one of the repositories declared in the <server> section. (How to determine the id of a package is explained later.) version optional parameter determines which version of the package is installed. If you have several repositories that all use the same ID (such as the XML Feature Pack offering, XML Fix Pack 3, XML Fix Pack 5, and XML Fix Pack 7), then specifying the version determines which of the packages get installed. If this parameter is omitted, then the newest (highest) version package (available from the repository list) is installed. WebSphere Support Technical Exchange 30 of 58

31 <offering> section in <install> Purpose: Declare a single package to install Example: Install or update XML to V <install modify='false'> <offering id='com.ibm.websphere.xml.v10' version=' _1332' profile='ibm WebSphere Application Server - ND' features='fep.xml.core.feature'/> </install> features optional parameter specifies the name of a feature to be installed from the offering. All feature pack offerings have at least one feature (the core feature), and some have additional features (such as the SDO feature in the SCA feature pack). If you specify this option, be sure to at least specify the core feature. If you omit this option, all features are installed. profile required parameter specifies the profile ID of a product to be updated. This must match the profile ID specified in the <profile> section. WebSphere Support Technical Exchange 31 of 58

32 <preferences> - Shared resources location Purpose: Sets the location of shared resources directory Example: Setting shared resources directory on Windows <preference value='c:\ibm\websphere\appserver-shared' name='com.ibm.cic.common.core.preferences.eclipsecache'/> name there are many <preferences>. The name of this particular setting is com.ibm.cic.common.core.preferences.eclipsecache. You must use that value when setting the shared resources directory. value specify the full path of the shared resources directory here Same rules apply for shared directory as discussed earlier shared directory can only be set for IM the first time a product is imported, and must be the same for all products afterward. All other <preference> values should remain at the default values recorded in response file or copied from sample response file, unless there is a specific need to change an option WebSphere Support Technical Exchange 32 of 58

33 Finding data for response file To verify which profile ID was used for a previous import, consult the installed.xml in the agent data directory open in browser A feature pack's Offering ID and fix pack version number are listed in repository.xml in a feature pack's main or local-repositories directory WebSphere Support Technical Exchange 33 of 58

34 Sample: Updating XML to In this example, we have obtained the XML Feature Pack repository, the WAS Import Repository, and XML Fix Pack 5 repository This will either install a fresh copy of XML Feature Pack and update it to V , or it will update an existing XML Feature Pack to Fix Pack 5. It does this because Fix Pack 5 is the highest level repository in the repository location list. Specify necessary repositories in <server> section <server> <repository location='c:\ibm\silentrep\xml_and_import_repositories\local-repositories\xml'/> <repository location='c:\ibm\silentrep\was.7.0.import'/> <repository location='c:\ibm\silentrep\xml fp'/> </server> Then, specify the feature pack to be updated in <install> section <install modify='false'> <offering id='com.ibm.websphere.xml.v10' profile='ibm WebSphere Application Server - ND' /> </install> WebSphere Support Technical Exchange 34 of 58

35 Sample: Updating XML to Alternative example: We happen to have Fix Packs 3, 5, and 7, but we really want to update XML to fix pack 5 Specify necessary repositories in <server> section <server> <repository location='c:\ibm\silentrep\xml_and_import_repositories\local-repositories\xml'/> <repository location='c:\ibm\silentrep\was.7.0.import'/> <repository location='c:\ibm\silentrep\xml fp'/> <repository location='c:\ibm\silentrep\xml fp'/> <repository location='c:\ibm\silentrep\xml fp'/> </server> Then, specify the feature pack to be updated in <install> section, being sure to specify the exact version number to install <install modify='false'> <offering id='com.ibm.websphere.xml.v10' version=' _1332' profile='ibm WebSphere Application Server - ND' features='fep.xml.core.feature'/> </install> WebSphere Support Technical Exchange 35 of 58

36 Sample: ifix install Updating product with interim fix generally follows the same pattern in the <install> section <install modify='false'> <offering id='pm12345_featurepack' profile='ibm WebSphere Application Server - ND'/> <install modify='false'> Generally, ID of interim fix is provided in readme file bundled with fix, or the ID matches the name of the interim fix repository.zip file provided by IBM Review repository.xml associated with fix for exact details WebSphere Support Technical Exchange 36 of 58

37 Sample: Uninstall of XML Feature Pack part 1 In this example, assume that XML Feature Pack is installed Update the <profile> section with a data key to indicate that profiles should be automatically unaugmented, removing data from a specific feature pack <profile id='ibm WebSphere Application Server ND'> <data key='user.confirm.unaugment,com.ibm.websphere.xml.v10' value='true'/> Note: If more than one feature pack is being uninstalled, then include a separate unaugment <data> key for each feature pack. Some 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 For example: <data key='user.confirm.unaugment,com.ibm.websphere.xml.v10' value='true'/> <data key='user.confirm.unaugment,com.ibm.websphere.sca.v10' value='true'/> WebSphere Support Technical Exchange 37 of 58

38 Sample: Uninstall of XML Feature Pack part 2 Update the <uninstall> section with the offering ID of the feature packs to be uninstalled. The feature pack and all its fix packs will be uninstalled. <uninstall modify='false'> <offering id='com.ibm.websphere.xml.v10' profile='ibm WebSphere Application Server - ND'/> </uninstall> The id and profile attributes are required. Alternatively, specify a version and/or feature attribute to uninstall a specific fix pack or sub-feature instead of uninstalling the entire feature pack. This sample uninstalls Fix Pack 5: <uninstall modify='false'> <offering id='com.ibm.websphere.xml.v10' profile='ibm WebSphere Application Server - ND' version=' _1332'/> </uninstall> WebSphere Support Technical Exchange 38 of 58

39 Sample: Uninstall of XML Feature Pack part 3 Another alternative: Use rollback instead of uninstall. Works similarly to rollback described earlier. <rollback> <offering id='com.ibm.websphere.xml.v10' version=' _0443' profile='ibm WebSphere Application Server - ND' features=''/> </rollback> WebSphere Support Technical Exchange 39 of 58

40 Important Directories WebSphere Support Technical Exchange 40 of 58

41 Directories (Shared Resources Directory) This location acts as a cache for data retrieved from local repositories or web repositories. Improves performance on systems where frequent installs / uninstalls take place. Location is selected the first time a package is installed by Install Manager, or during Import Multiple products share this same directory Choose location with reasonable disk space free Deleting this directory is not recommended Cannot be changed or moved once selected Sample Shared Resource directory from Windows WebSphere Support Technical Exchange 41 of 58

42 Directories (appdatalocation) appdatalocation: also called Installation Manager Agent Data Directory or IM_DATA directory IBM Installation Manager uses this to track data associated with packages it has installed on the system This data is very important and should be backed-up regularly along with WebSphere products Location of data can be changed using -datalocation (or -dl ), but make sure to use -datalocation option every time Installation Manager programs are used Table of default locations for IM_DATA: WebSphere Support Technical Exchange 42 of 58

43 Directories (appdatalocation) The default appdatalocation is set by the cic.appdatalocation property in the config.ini file location depends on OS Windows: install_dir\ibm\installation Manager\eclipse\configuration Linux and UNIX: install_dir/ibm/installationmanager/eclipse/configuration IBM does not recommend changing this value in config.ini file To determine the location of Installation Manager, check in these locations: Windows Registry key: HKLM\SOFTWARE\IBM\Installation Manager\location Linux and UNIX: Open the /etc/.ibm/registry/installationmanager.dat file Look at the location entry. Example: location=/var/ibm/installationmanager WebSphere Support Technical Exchange 43 of 58

44 Viewing logs from Installation Manager WebSphere Support Technical Exchange 44 of 58

45 Install Manager GUI can be used to view Installed packages, Installation history and logs. WebSphere Support Technical Exchange 45 of 58

46 From the Logs folder under Data directory open index.xml in a browser WebSphere Support Technical Exchange 46 of 58

47 Best Practices and Common Problems WebSphere Support Technical Exchange 47 of 58

48 Best Practices Each of the following should have unique path Installation Manager Install Directory Shared Resources Directory Install Manager Data Directory IM can be installed and run as non-root user Highly recommended to use WSAS as non-root Use same user to install and update Feature Packs When installing multiple feature packs using silent mode, prepare the response file using record mode WebSphere Support Technical Exchange 48 of 58

49 Best Practices Repositories can be stored on a networked resource and accessed through a networked filesystem (or a UNC path on Windows) Multiple systems can access the same collection of local repositories simultaneously Augmentation Must augment profiles once a feature pack is installed Must unagument profiles if uninstalling a feature pack Keep copies of all local repositories Maintain a copy of the appdatalocation data used with -skipinstall WebSphere Support Technical Exchange 49 of 58

50 Problem: Synchronization Error When trying to install XML Feature pack on WSAS using Local Repositories, and getting the following error: Repositories in preferences Error On GUI WebSphere Support Technical Exchange 50 of 58

51 Problem: Synchronization Error XML Feature Pack Repository has Sync repositories for Application Server fix pack 7. WSAS v should synchronize fine, but if the product is upgraded to higher fix pack (like ) then latest WSAS Import Repositories are needed for product to synchronize with IM WSAS Sync repository with XML Feature Pack Repository Latest WSAS Import repository NOTE: Always keep a copy of the latest WSAS import repositories. WebSphere Support Technical Exchange 51 of 58

52 Problem: Java SDK fixpack version not same as WSAS fixpack Application Server is at but Java SDK is at Both fix packs have to be at same level for Import to succeed WebSphere Support Technical Exchange 52 of 58

53 Problem: What do I download to install latest version of XML feature pack? Base Code of Feature pack can be downloaded from Support page (requires IBM web site ID) Will download as <featurepack_name>_and_import_repositories.zip For XML, xml_and_import_repositories.zip Example from Fixpack download page: XML fixpack WSAS Import Repository XML Import or Mini XML only used if XML (GA) is installed and is being updated to WebSphere Support Technical Exchange 53 of 58

54 Mustgather data required by support Agent data directory (IM_DATA) Using Graphical Installation Manager Using Command line navigate to eclipse/tools subdirectory in the location where you installed Installation Manager Windows: imcl.exe exportinstalldata outputfilename Unix and Linux:./imcl exportinstalldata outputfilename z/os:./imcl exportinstalldata outputfilename Send the zip file created to support along with files listed on next slide WebSphere Support Technical Exchange 54 of 58

55 Mustgather data required by support In addition to this, we need Logs directory from Application Server All XML files from Application Server's properties/version/nif/backup directory Response file used for installation Only needed if performing a silent install Screenshot of error if using Graphical Interface If you are installing IM and the graphical interface does not appear, or if it appears but prints errors to the console, please copy and paste the console errors to us WebSphere Support Technical Exchange 55 of 58

56 Additional WebSphere Product Resources Learn about upcoming WebSphere Support Technical Exchange webcasts, and access previously recorded presentations at: Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Join the Global WebSphere Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: View a webcast replay with step-by-step instructions for using the Service Request (SR) tool for submitting problems electronically: Sign up to receive weekly technical My Notifications s: WebSphere Support Technical Exchange 56 of 58

57 Connect with us! 1. Get notified on upcoming webcasts Send an to with subject line wste subscribe to get a list of mailing lists and to subscribe 2. Tell us what you want to learn Send us suggestions for future topics or improvements about our webcasts to wsehelp@us.ibm.com 3. Be connected! Connect with us on Facebook Connect with us on Twitter WebSphere Support Technical Exchange 57 of 58

58 Questions and Answers WebSphere Support Technical Exchange 58 of 58

59 IBM Software Group Best Practices for Installing WebSphere Application Server V7 Feature Packs Joseph Mertzlufft Vishavpal Shergill WebSphere Application Server L2 Support 27 October 2011 WebSphere Support Technical Exchange Welcome to Best Practices for Installation of Feature Packs for WebSphere Application Server V7.0. This presentation is brought to you by the WebSphere Support Technical Exchange program. This material has been prepared and presented by Joe Mertzlufft and Visavpal Shergill of the WebSphere Application Server Level 2 support team. 1

60 Agenda Introduction Repositories Import Graphical Interface Silent Install Important Directories Best Practices WebSphere Support Technical Exchange 2 of 58 This presentation will cover the general process and outline best practices associated with the installation and upgrade process for Feature Packs available for WebSphere Application Server V7.0 on distributed operating systems: AIX, HP-UX, Linux, Solaris, and Windows. This process uses IBM Installation Manager, which has previously not been used with WebSphere Application Server V7.0. 2

61 INTRODUCTION WebSphere Support Technical Exchange 3 of 58

62 Introduction to Installation Manager IBM Installation Manager (IM) is an application that simplifies downloading, installing, updating, and uninstalling many IBM software products from a single user interface Starting with WebSphere Application Server v7.0, Feature Pack install and update is performed using Installation Manager V7.0 Application Server and Java TM SDK updates continue to be performed with Update Installer WebSphere Support Technical Exchange 4 of 58 Installation Manager is a single installation program that can use remote ( web ) or local software repositories to install, modify, or update new WebSphere Application Server (WSAS) products. Starting with WSAS version 7.0, feature packs must be installed by Installation Manager, rather than by programs based on InstallShield MultiPlatform (ISMP). ISMP-based programs are used to install, update, and uninstall previous versions of WebSphere Application Server. Fix pack updates to Application Server and the Java SDK should continue to be installed using the UpdateInstaller utility.

63 ISMP vs. Installation Manager ISMP former installation technology Install, Uninstall and Update processes required different programs Each Feature Pack required separate install program Fix pack in.pak format Obtaining Feature Pack or fix pack downloads is separate process IBM Installation Manager (IM) Single interface to install, update, uninstall many IBM software products Use local or Web repositories Ability to download packages integrated into IM Single IM instance can manage multiple products Replaces dedicated installers and uninstallers and maintenance tools Simplifies product maintenance WebSphere Support Technical Exchange 5 of 58 Earlier installation methods (in V6.1) for installing feature packs for WebSphere Application Server used ISMP-based tools. To install these feature packs, you had to locate and download the feature pack installation package and install each feature pack separately. For each feature pack, the required prerequisite WebSphere Application Server fix pack is bundled with the feature pack, even if the fix pack has already been applied to the existing installation. Also, the installation utilities could only install packages which were downloaded before the installation took place. The feature packs in v7.0 uses the new IBM Installation Manager solution. Installation Manager can use local or web repositories. Web repositories allow Installation Manager to connect directly to ibm.com (or another web server) and download necessary repositories automatically. One Installation Manager interface can handle installation, uninstallation, and updates for multiple products, and it can perform several operations from a single set of input.

64 REPOSITORIES WebSphere Support Technical Exchange 6 of 58 Here are supplemental details for speaker notes on Slide To add a repository: Go to File > Preferences > Repositories menu Click the Add Repository... button. For local repositories, provide the repository path up to and including the repository.config file. For Web repositories, provide the URL. This is equivalent to the <server> section in a response file.

65 Repositories Repositories are locations that Installation Manager queries for installable packages Web Repositories Internet access required Feature Pack Fix pack for Feature Packs Note that those URLs are input into IM, not your web browser Local Repositories download from IBM.com and store locally Download from Support Site as.zip format Feature Pack Fix Pack WebSphere Support Technical Exchange 7 of 58 Repositories are locations that Installation Manager queries for installable packages. There are two types of repositories available for feature packs: Web repositories, and Local repositories. Web repositories are available if the system has access to internet. Installation Manager can connect to IBM.com directly and retrieve feature pack repositories. IM needs to be supplied with URLs to connect to, but the IM version available on the WebSphere support site are pre-configured with these URLs. An IBM ID is required for authentication and can be stored in Installation manager preferences. If direct internet access is not available, then local copies of repositories are available to download from the ibm.com support site separately. The same repositories can be used to install the feature pack or fix packs for all sites. Before installing a feature pack fix pack, you need to have the feature pack's initial repository. Best practice: If you are using local repositories, keep a copy of each repository that you have downloaded. IM may require data from the base install repository and fix pack repositories for subsequent upgrades and uninstall operations. For details on how to add a repository to the list, refer to the speaker notes on Slide 6.

66 IMPORT WebSphere Support Technical Exchange 8 of 58

67 Import Must use Import feature for Installation Manager to recognize WebSphere Application Server V7.0 Must do this before installing a feature pack for the first time The Import button is only visible after a WebSphere repository has been added to the repository list Application Server fix pack and Java SDK fix pack level must match before performing Import Example: Application Server has been updated with Fix Pack 17 (V ), so Java SDK must also be updated with Fix Pack 17. WebSphere Support Technical Exchange 9 of 58 Before you can use Installation Manager to install any packages on top of WebSphere Application Server V7, you need to import the application server into the Installation Manager. Click the Import button to open the import wizard. Note that the Import button is only visible after a WebSphere repository has been added to the repository list. So, if you do not see the Import button on the main Installation Manager, check your repository configuration to be sure you are pointing to a WebSphere repository. Note that there is an additional requirement imposed on the WSAS V7 product in order to use feature packs. The application server fix pack level and SDK fix pack level must be the same; i.e., if you install WSAS Fix Pack 17, then you must also install SDK Fix Pack 17 before importing WSAS into Installation Manager.

68 NOTE: You can only select the shared resources directory the first time you install a package with the IBM Installation Manager. All other installations of WSAS X on the same system will use the same Shared Resources directory. WebSphere Support Technical Exchange 10 of 58 To import an application server installation, you need to provide the installation directory for that instance of the application server. The screenshot on the left shows how this question is presented by the Import wizard. You can either browse to the location using a standard file selection window or type the full path into the Installation Directory field. After providing the path, click Next. The next panel, shown on the right, allows you to choose the Shared Resources directory for the Installation Manager. The Shared Resources directory contains files that can be shared by multiple packages. You can only select the shared resources directory the first time you install a package with the IBM Installation Manager. This directory caches data retrieved from repositories. It is a good practice to use the recommended shared resources directory. Click Next to proceed through through the import wizard. We will discuss more details for this directory later in the presentation.

69 GRAPHICAL INTERFACE: INSTALL, UPDATE, UNINSTALL, and ROLLBACK WebSphere Support Technical Exchange 11 of 58

70 Installation Manager graphical options WebSphere Support Technical Exchange 12 of 58 So far, we have discussed repositories and the import function. Let's give an overview of the other functions as they are represented on the main Installation Manager window. The Installation Manager includes several wizards that guide you through installing, updating, and uninstalling products. The Install wizard is the starting place for installing new software packages, including the first time you install a particular Feature Pack. The Install function will access the repositories you have configured, allow you to select specific packages to install from a list of packages available for installation, and step you through the installation process. The Update wizard discovers and installs updates and fixes to your software packages. This is the interface you use to apply software maintenance or update your products to a newer version. This wizard displays and recommends fixes and maintenance packages that are targeted to your operating system and set of installed products. You can also apply refresh packs to update your software to the latest version. Some products have optional sub-features which you can choose not to install when the product is initially installed. But, you can choose to install them Later. The Modify function allows you to select sub-features to add to an already-installed product or feature pack.

71 Installation Manager graphical options WebSphere Support Technical Exchange 13 of 58 The Import wizard allows you to point to an existing product installation on your system and link it to Installation Manager. In this presentation, we're concentrating on the WebSphere Application Server V7 product. As discussed earlier, before installing a feature pack, you need to import an installation of WebSphere Application Server V7. Note that the Import button is not present until you add a WebSphere repository to the list of available repositories. The Roll Back wizard allows you to move your product back to a previous version of service for example, moving a product from Fix Pack Y to lower Fix Pack X. This function lets you choose which version of the product you want to roll back to. The Uninstall wizard allows you to remove software packages from your system and remove links to products that you have imported. This function uninstalls a feature pack entirely. (Note that the Manage Licenses wizard is not used by WebSphere products at this time.) Import operations are only available with WebSphere Application Server V7. Do not try to use Installation Manager to import other products, like Rational Application Developer.

72 Install IBM Software Group With Web Repositories With Local Repositories If checked will list all available offerings WebSphere Support Technical Exchange 14 of 58 Here are some sample screenshots of what you see when using the Install function. When using Web Repositories, represented on the left, you will see a list of all available Feature Packs for the product. If the Show all versions option is selected, then you will also see all the possible fix pack levels. Otherwise, only the latest version of each feature pack is displayed. Note that you can use this function to initially install a specific version of a feature pack, instead of installing whatever the latest version is. When using local repositories, represented on the right, only the feature packs and fix packs represented in IM's repository list are displayed.

73 Update IBM Software Group With Web Repositories With Local Repositories Select recommended is checked in both cases above. WebSphere Support Technical Exchange 15 of 58 Similarly, here are some screenshots of what you see when using the Update function. Use the Update option to apply fix packs to existing, already-installed Feature packs. This option will only list available fix packs for feature packs which are installed. The list of fix packs available when using Web repositories is represented on the left. All available fixpacks for that feature pack will be listed. The list of fix packs available when using Local repositories is represented on the right. Only fix packs represented in IM's repository list which are eligible to be installed will be shown. If Show recommended Only is selected, then only the highest available fix pack for each feature pack is displayed. Note that if a feature pack is not yet installed, and only feature pack fix packs are available in the IM Repository List, then these views will show that no updates are available. The base Code of feature pack must be installed before a feature pack fix pack is installed. Note that when installing the base code, you can choose to install a fix pack as part of that initial installation process.

74 Rollback IBM Software Group Example: XML is installed and Rollback option is chosen. Install Sequence was: XML XML XML Will Roll back to (last installed) Will Roll back to (GA version) WebSphere Support Technical Exchange 16 of 58 Here we have an example screenshot from the Roll Back wizard. The Roll Back wizard allows you to move your product back to a previous version of service for example, moving a product from Fix Pack Y to lower Fix Pack X. The options presented to you allow you to choose which version you want to have when the roll back is complete. For example, consider a scenario where you have the XML base package along with XML Fix Packs 3 and 5. The Roll Back wizard will present you with options to roll back to either XML Fix Pack 3 or the base XML version. If you choose to roll back to XML Fix Pack 3, then XML Fix Pack 5 is uninstalled. If you choose to roll back to XML version , then both Fix Packs 3 and 5 are uninstalled. Note that you can only roll back to remove fix pack levels delivered by the Update function. if you chose to initially install a feature pack and fix pack in a single session without using the Update function, then you cannot roll back to an earlier level. For example, if you initially installed XML at version and you have not installed any other fix packs, then you cannot roll back to an earlier fix pack level nor can you roll back to version

75 Uninstall IBM Software Group Example: XML was previously installed. Choosing Uninstall option and selecting XML option will uninstall entire Feature Pack. If checked will uninstall Application Server Will uninstall complete Feature Pack WebSphere Support Technical Exchange 17 of 58 This is an example of using the Uninstall function. The Uninstall wizard allows you to remove software packages from your computer and remove links to products that you have imported. Take care when using this option. If the main WebSphere product option is selected, such as WebSphere Application Server ND, then the entire WebSphere Application Server product will be uninstalled. Using the Uninstall wizard, you can choose which feature packs are uninstalled. IMPORTANT: Once WebSphere Application Server V7.0 is Imported to IM, you should not use the product's standard uninstall program located in the WAS_HOME/uninstall directory. When you eventually decide to uninstall the product, please use the Uninstall function here in IM in order to remove the product from the system. If you do not do this, then IM may continue to indicate that the product is installed even when it has been uninstalled.

76 PERFORMING SILENT OPERATIONS WebSphere Support Technical Exchange 18 of 58

77 Silent Install Silent install is performed using a response file Sample response file from Information Center are available Response file can also be recorded Response file is xml format Same command (such as imcl ) is used for installing, uninstalling, updating, or rolling back Only need to change options in the response file in order to perform different operations A single response file can perform multiple operations; i.e., Import WSAS, install two feature packs, install fix packs on feature packs all in a single session WebSphere Support Technical Exchange 19 of 58 If Graphical capabilities are not available on the system, then the silent mode can be used to install and maintain feature packs. Note that Installation Manager itself can be installed in silent mode, and then subsequent operations (such as installing feature packs) can also be performed in silent mode. Silent mode uses XML-formatted response files as input. Sample response files for various activities are available in the WSAS V7 Information Center. Also, it is possible to record your own response file, customized to whatever operations you want to perform. A single Installation Manager program takes the response file as input, and that response file drives all activity. A single response file can instruct Installation Manager to perform multiple actions.

78 Silent Install Sample command (v1.4.4) from INSTALL_LOCATION\eclipse\tools UNIX :./imcl -input /temp/install.xml -acceptlicense -showprogress WINDOWS : imcl -input C:\install.xml -acceptlicense -showprogress imcl -help will list options available with imcl command An interactive console mode is available in Installation Manager; however, it is not supported WSAS V7 Feature Packs Learn to use response files with WSAS V7 Feature Packs WebSphere Support Technical Exchange 20 of 58 Example commands for invoking Installation Manager to use a response file are listed on this slide. The -input parameter indicates which response file should be used. The -acceptlicense parameter indicates that you accept the license agreements associated with the products being installed, and is a required parameter for Installation Manager to proceed. The -showprogress parameter gives a progress indicator on the console to show operations in progress. This is an optional parameter. Note that newer version of Installation Manager, introduced after Feature Packs came to WSAS V7.0, have features that can be used as an alternative to silent mode. However, those features are only available to new IBM products, and not to WSAS V7.0 feature packs. So, please familiarize yourself with silent mode for use with WSAS V7 Feature Packs.

79 Recording mode and skipinstall mode Recording mode allows you to generate a response file by recording the actions taking place in the graphical interface skipinstall mode allows IM to operate in a mode where it does not actually install, update, or uninstall packages This mode maintains a dummy set of IM data (known as agent data ) which persists you can use the dummy data again later Does require an actual WSAS V7.0 install to be present, but Feature Packs are not actually installed or uninstalled Both modes can be combined Example command-line (Windows): IBMIM.exe -skipinstall C:\dummyIMdata -record C:\project\installXML.xml WebSphere Support Technical Exchange 21 of 58 IM has two modes which are useful for preparing silent mode response files: Recording Mode and skipinstall Mode. Recording mode runs IM in graphical mode, and it records the actions that take place during that session. These actions are saved to a response file. We very strongly recommend using record mode to learn how response files are generated. It is much easier to learn how to do something in graphical mode then see the equivalent commands generated to a response file. skipinstall mode is a useful companion to recording mode. The skipinstall mode causes IM to perform a dry run of all actions. No software is installed, unintalled, or modified in skipinstall mode. Also, skipinstall mode maintains a dummy set of agent data -- it is able to keep track of a fake set of software, which allows you to emulate complex installations without actually installing any software at all. (Note that you do need to install WebSphere Application Server V7 in order to use skipinstall mode, however you do not need to install actual feature packs.) You can combine both record mode and skipinstall mode in order to generate response files without having to devote time or filesystem space normally required for installing products.

80 Recording a response file IM graphical interface will indicate that it is recording response file Installation Manager In Record Mode Don t specify IM's true agent data directory with skipinstall recommend using a dummy repository instead Once response file is recorded, you can use it on another system Be sure to edit the response file so paths match those on the system where the install is taking place Keep the same dummy agent data directory to allow you to record response files for future updates, installs, or uninstalls for the same environment when using -skipinstall Sample response file on next page WebSphere Support Technical Exchange 22 of 58 When running IM in recording mode, the graphical interface will indicate the mode on the title bar. As mentioned previously, skipinstall mode allows IM to simulate installations without actually installing IBM software products. By using the -skipinstall agentdatalocation argument along with the -record responsefile.xml argument, you can create a response file for an installation process without performing the installation. The agentdatalocation location stores the data for the dummy installation data. You can use that same agentdatalocation later to perform subsequent operations such as simulating fix pack installs or uninstalling products. Important: Do not specify the current directory for a new agentdatalocation location. Also, do not specify IM's default agent data directory for the agentdatalocation with -skipinstall, because this will cause dummy data to be added (or removed) from the agent data which keeps track of real product installations on the system. Once you have created the response file, keep that same dummy agent data directory for future use. As mentioned above, you can simulate other operations such as fix pack installs or product uninstalls with that data.

81 Application Server Details IMPORT Repository Details Shared Resource Directory Install Options WebSphere Support Technical Exchange 23 of 58 Here is a sample response file. This response file will Import WebSphere Application Server V7.0 on Windows, then install the base package of the XML Feature Pack along with XML Feature Pack Fix Pack 5. Each relevant section (including the option striped in cyan coloring at the top) is discussed in the subsequent slides.