Installation overview WebSphere Business Process Management WebSphere Process Server V7.0 WebSphere Enterprise Service Bus V7.0 Installation overview This module covers the installation process for the WebSphere® Process Server V7. Installation Installation V7 installer uses Installation Manager You can install, uninstall, and maintain WebSphere Application Server** WebSphere Process Server Feature packs and maintenance†† Supports interactive and ‘silent’ installation Common installation process WebSphere Enterprise Service Bus WebSphere Process Server Steps involved in installation Install the WebSphere Application Server Import installation into Installation Manager Use Installation Manager to install WebSphere Process Server Optionally create new profiles for WebSphere Process Server and Enterprise Service Bus **Installation not supported by Installation Manager. Only un installation of WebSphere Application Server ††Not applicable for WebSphere Application Server interim fixes, Fix packs The WebSphere Enterprise Service Bus installation is a subset of the installation process but follows the same flow as the installation of the WebSphere Process Server. In version 7.0 the installer for WebSphere Process Server is not an Install Shield Multiplatform based installer. It is an Installation Manager based installer that supports interactive and silent installs. You install the software interactively from the launch pad program, invoke installation manger graphical user interface or silently by running Installation Manager in silent installation mode. In silent mode, the installation wizard does not display a graphical interface, but reads your responses from a response file. The installation process will run the profile management tool as part of the installation and will provide an option to create a stand-alone profile. The steps involved in the installation of the process server are shown on the slide. The first step is to install the WebSphere Application Server. Once the installation is done, import the installation into Installation Manager. Then use the Installation Manager to install WebSphere Process Server. You can also use the Installation Manager to install any features packs and maintenance packs. Installation using launch pad Installation using launch pad This slide shows the screen capture of the options available in launch pad application when you choose the new installation option. You can also see the steps are outlined in the previous slide listed on the launch pad. The first step is the installation of WebSphere Application server. More details on step 1 are provided in the next slide. Install WebSphere Application Server and Installation Manager Install WebSphere Application Server and Installation Manager Step 1: Make sure that another instance of Installation Manager is not running Specify the path where you want to install the WebSphere Application Server Specified directory cannot already exist Click the link in step 1b “Install WebSphere Application Server” Installs IBM Installation Manager to its default install location, if not already installed. If IBM Installation Manager is not at the required level, the launch pad application updates it to the correct level ( V1.3.3) Installs WebSphere Application Server Network Deployment into the directory you specify Imports WebSphere Application Server into Installation Manager automatically Installation process is done silently and can take several minutes. Wait until you get a message indicating success or failure Before you start the installation, make sure that no other instance of Installation Manager is active to ensure proper installation. Provide the directory path where you want to install WebSphere Application Server in the textbox provided in the launch pad listed in step 1a. Click the link “Install WebSphere Application Server” in step 1b. This will initiate the process of installing the WebSphere Application Server silently. This can take several minutes. The progress bar on the bottom of the launch pad will give you an estimate of the progress in installation . The script will install IBM Installation Manager to its default install location, if not already installed. If IBM Installation Manager is not at the required level, the launch pad application updates it to the correct level (V1.3.3). The script will also import the WebSphere Application Server installation information into Installation Manager. Do not proceed until a message indicates a successful installation and import into Installation Manager. Instead of a success message, you can receive a failure to import or failure in installation message. Troubleshooting information is covered in the problem determination section. Launch pad step 1 Launch pad step 1 This slide shows the screen capture of the warning message when you click the link in step 1b to check for any running instances of Installation Manager Install WebSphere Process Server Install WebSphere Process Server Step2 Click “Install WebSphere Process Server” link Launches Installation manager with pre selected options that include WebSphere Application Server Feature Pack for XML, WebSphere Application Server Feature Pack for Service Component Architecture (SCA), and WebSphere Process Server Step 2 is the installation of WebSphere Process Server. Launch pad will invoke the Installation Manager, which provides you with a set of recommended options that are already selected. You need to have WebSphere Application Server Feature Pack for XML, WebSphere Application Server Feature Pack for Service Component Architecture (SCA), and WebSphere Process Server options selected. Select package group Select package group Select the package group on which you want to install the features packs and the WebSphere Process Server. The panel displays a list of all the package groups you have installed. A package group represents a directory in which packages share a common user interface or workbench with other packages in the same group. Select package features Select package features In the next panel after you select the package group you are provided with the option to select various features of the packages you are installing. You can select the option to create a default stand-alone development WebSphere Process Server or WebSphere Enterprise Service Bus profile. Profile properties and summary Profile properties and summary Based on the feature options you selected, you will be presented with profile specific panels like the administrator username passwords and then the summary panel which lists all the options you chose to install. Click Install. When the installation is complete, a page displays the status of the installation and which packages have been successfully installed. Silent installation Silent installation Use the run_templates or run_template.bat script Located under product_unzip/responsefiles/wbi/ Edit template_response.xml and the script file run_template Option to create default profile by editing the response file You can also install WebSphere Process server silently using the response files. You need to edit the response file to customize the options you want in the response file. You start the installation process by running the run_templates or run_template.bat script, which you can also edit. Optionally you can also edit the files to create a stand-alone server profile. Update WebSphere Process Server and underlying WebSphere Application Server Update WebSphere Process Server and underlying WebSphere Application Server Section The next section covers details on how you can use the Installation Manager graphical user interface or silently update the WebSphere Process Server and the underlying WebSphere Application Server. Update WebSphere Process Server Update WebSphere Process Server Update WebSphere Process Server interactively Use the Installation Manager to apply any interim fixes, fix packs and maintenance packs If there is a dependency on WebSphere Application Server level fixes, you are notified can also download the fixes and point Installation Manager to the repository Update WebSphere Process Server silently Use IBMIM script for UNIX® and IBMIMc.exe for windows IBMIMc.exe --launcher.ini silent-install.ini -updateAll -log log_file Links to information center: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wps.doc/doc/tins_updating_silently.html http://publib.boulder.ibm.com/infocenter/install/v1r2/topic/com.ibm.silentinstall12.doc/topics/c_silent_install_over_IM.html There are certain limitations on installation manger when updating the WebSphere Application Server. The next couple of slides will cover the details on how you can update the WebSphere Process server interactively or silently using the Installation Manager. Installation manager can be used to apply any interim fixes, fix packs and feature packs. If there is a dependency on any WebSphere Application Server fixes, you are notified to install that fix first. You can configure the Installation Manager to look for any updates by pointing to the repositories. The repository can be a local one or point to live link on a server. Once the repositories are set up, click the update icon on the home page of the Installation Manager. Installation manager will look for any updates to the products installed in the configured repositories and make them available for you to select. You can select the appropriate fixes or features and install them. Alternatively to interactively installing the maintenance, you can install fixes and features using silent installation. You still need to configure the repositories either local or on a server. Use the IBMIM script available with the Installation Manager to install the fixes on UNIX environments. For windows use the IBMIMc command instead of IBMIM. Update WebSphere Process Server interactively (1 of 2) Update WebSphere Process Server interactively (1 of 2) This slide shows the panel in Installation Manager where you can click update. In the update Packages wizard, select the package group containing the product package you want to update or select the Update all check box, and then click Next. Installation manager searches for updates in its repositories and the predefined update sites for the software you are updating. Update WebSphere Process Server interactively (2 of 2) Update WebSphere Process Server interactively (2 of 2) If updates for a package are found, then they are displayed in the Updates list on the Update Packages page below their corresponding package. Only the latest recommended updates are displayed by default. Click Show all to display all updates found for the available packages. To learn more about an update, click the update and review its description under Details. If additional information about the update is available, a More info link is included at the end of the description text. Click the link to display the information in a browser. Review this information before installing the update. Select the updates that you want to install or click Select Recommended to restore the default selections, and click Next. Updates that have a dependency relationship are automatically selected and cleared together. If there is a dependency on a WebSphere Application Server fix, a prerequisite check failure reports the WebSphere Application Server fix that is required. You must run the IBM WebSphere Update Installer tool to apply the WebSphere Application Server fix. After you apply the fix, click the Recheck button to verify that the prerequisite has been fulfilled and proceed. Note: During the update process, Installation Manager might prompt you for the location of the repository for the base version of the package. If you installed the product from DVDs or other media, they must be available when you use the update feature Update WebSphere Application Server Update WebSphere Application Server WebSphere Application Server Cannot use Installation Manager to update Use update installer If you apply fix pack to WebSphere Application Server import the application server installation again into Installation manager No need to re-import if you apply interim fixes You cannot use IBM Installation Manager to apply interim fixes, fix packs for WebSphere Application Server. You must run the IBM WebSphere Update Installer tool to apply the WebSphere Application Server fix. WebSphere update installer is packaged with the product. You need to install it separately as it is not installed with WebSphere Process Server installation. If you apply fix pack to WebSphere Application Server, import the application server installation again into Installation Manager. There is no need to re-import if you apply interim fixes. Uninstall WebSphere Process Server Uninstall WebSphere Process Server Section The next section covers the details on how you can uninstall the WebSphere Process Server and the underlying WebSphere Application Server. Uninstall WebSphere Process Server Uninstall WebSphere Process Server Use the Installation Manager to uninstall Stop all server instances Launch Installation Manager Click the uninstall button A panel with the list of all the installed packages is listed Select the package you want to uninstall or just WebSphere Process Server Uninstall WebSphere Application Server using Installation Manager and not the InstallShield MultiPlatform wizard provided with the installation If there is dependency, you need to uninstall all the products with dependencies before removing the dependency product Use the Installation Manager to uninstall the WebSphere Process Server and the underlying WebSphere Application Server. A package cannot be uninstalled when another package has a dependency on it, unless the dependent package is also selected to be uninstalled. For example, you can uninstall the WebSphere Application Server Network Deployment installation underlying WebSphere Process Server, as long as other products are not dependent on WebSphere Application Server Network Deployment. Troubleshooting and logs Troubleshooting and logs Section The next section covers the details on some of the known issues and log files Troubleshooting and logs (1 of 2) Troubleshooting and logs (1 of 2) Make sure that another instance of Installation Manager is not running Import of installation into Installation Manager will fail. Manually import the installation into Installation Manager directory for the WebSphere Application Server Network Deployment installation should not already exist on file system, even if empty. If you install fix packs on WebSphere Application Server used for WebSphere Process Server, Re-import the WebSphere Application Server installation into Installation Manager: http://publib.boulder.ibm.com/infocenter/install/v1r2/topic/com.ibm.cic.agent.ui.doc/topics/t_import_pkg.html Default profile created set for development mode Installation manager will always try to launch the profile management tool. Profile management tool is not supported on 64 platforms. Uncheck the option Ignore these errors from Installation Manager: This slide lists some of the most common issues. If another instance of Installation Manager is active while the launch pad application script tries to import installation of WebSphere Application Server into Installation Manager, the import will fail. You can invoke the Installation Manager manually and then import the installation using the import function. The directory name that you provide for the installation of WebSphere Application Server should not exist already in your file system. If it does, even if it is empty, the installation of WebSphere Application Server will fail If you install fix pack on WebSphere Application Server, re import the installation again into Installation Manager using the import function. If you install interim fixes, re import is not required. If you choose to install a default profile while installing the product, the profile mode is set to development. Troubleshooting and logs (2 of 2) Troubleshooting and logs (2 of 2) If you get a message that WebSphere Application Server installation failed, check \logs\install\log.txt, or if this doesn’t exist \waslogs\log.txt \logs\wps\silent_install.log For import issues, check \logs\launchpad_import.txt List of all log files documented in information center for installation and profile creation http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wps.doc/doc/rins_logfiles.html Known issues http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wps.doc/doc/iins_errinstall.html This slide lists the log file locations and the scenarios in which you can check them. There are different sets of logs based on situation as shown here. Summary Summary IBM Installation Manager used to install and manage WebSphere Process Server Steps involved in the installation Limitations of installation manger related to WebSphere Application Server Update done using update installer Uninstall Troubleshooting and logs In summary, this presentation discusses how you can install and manage WebSphere Process Server using Installation Manager. It provides details on the various steps in the installation process, how you can install interactively using the launch pad and how to silently install the product. Details on how to update the WebSphere Process server and the underlying WebSphere Application Server are also covered along with uninstall and information on the most common issues and log files. Feedback Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send e-mail feedback: mailto:iea@us.ibm.com?subject=Feedback_about_WBPMv70_WPS_Installation.ppt This module is also available in PDF format at: ../WBPMv70_WPS_Installation.pdf You can help improve the quality of IBM Education Assistant content by providing feedback. Trademarks