Integration Developer Version 7.0 Version 7.0. Installation Guide

Integration Developer Version 7.0 Version 7.0 Installation Guide

Note Before using this information and the product it supports, be sure to read the general information under Notices on page 67. This edition applies to version 7 of WebSphere Integration Developer. Copyright IBM Corporation 2009. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Quick links Welcome to the Advanced Installation Guide for WebSphere Integration Developer. For your convenience, here are some quick links to our most popular install topics: Table 1. WebSphere Integration Developer quick links Chapter Installing with IBM Installation Manager Installing from the product launchpad program Installing Lotus Forms software on page 59 Installing Asset Repository on page 61 Modifying installations and Updating WebSphere Integration Developer Topics included in chapter Instructions on how to install WebSphere Integration Developer using the IBM Installation Manager. Instructions on how to use the launchpad program to install WebSphere Integration Developer. Installation of the following options: v IBM Lotus Forms Designer 3.5.1 v IBM Lotus Forms Viewer 3.5.1 v IBM Lotus Forms Server - API 3.5.1 Asset Manager is an optional feature that can be installed with WebSphere Integration Developer to manage the sharing of business artifacts. These topics provide instructions on how to modify your installation as well as keep your version of WebSphere Integration Developer up to date. Copyright IBM Corp. 2009 iii

iv WebSphere Integration Developer: Installation Guide

Contents Quick links............. iii Chapter 1. Overview......... 1 IBM Installation Manager.......... 1 Installation quick reference......... 2 Chapter 2. Installation requirements.. 7 Hardware requirements........... 7 Software requirements........... 7 Operating systems........... 7 Other software requirements........ 8 User privileges requirements......... 9 Chapter 3. Planning to install..... 11 Typical installation configurations....... 11 Installation scenarios........... 12 Deciding which features to install....... 13 Features.............. 13 Security considerations.......... 15 Coexistence considerations......... 16 Offering coexistence considerations..... 16 Coexisting installations of WebSphere Integration Developer.............. 16 Installation repositories.......... 16 Setting repository preferences in Installation Manager.............. 17 Package groups and the shared resources directory 17 Chapter 4. Preinstallation tasks.... 19 Chapter 5. Installation overview.... 21 Installing from DVD........... 21 Installing from an installation image on your workstation.............. 22 Installing from an installation image..... 22 Installing from an installation image on a shared drive................ 23 Chapter 6. Installing from the product launchpad program......... 25 Starting the launchpad program....... 26 Chapter 7. Installing with IBM Installation Manager......... 27 Installation log files............ 29 Chapter 8. Installing silently..... 31 Installing and running Installation Manager in silent mode................ 31 Searching for and silently installing all available products.............. 32 Silently installing updates to all currently installed products........... 33 Creating a response file with Installation Manager.............. 33 Recording a response file with the Installation Manager installer.......... 34 Recording a product install with the installer............. 34 Response file commands......... 34 Silent installation preference commands... 34 Reference: Sample response file....... 35 Silent installation commands....... 35 Silent install log files.......... 35 Working with IBM Installation Manager..... 36 Installing Installation Manager on Windows.. 36 Installing Installation Manager on Linux.... 36 Starting Installation Manager on Windows... 36 Starting Installation Manager on Linux.... 37 Uninstalling Installation Manager on Windows 37 Uninstalling Installation Manager on Linux... 37 Updating Installation Manager through a proxy server............... 37 Silently installing and uninstalling Installation Manager.............. 37 Silently installing Installation Manager... 37 Silently uninstalling Installation Manager from Windows............. 38 Silently uninstalling Installation Manager on Linux.............. 38 Chapter 9. Installing the WebSphere test environment using the launchpad. 39 Installing optional documentation....... 40 Chapter 10. Increasing the number of file handles on Linux workstations.. 41 Chapter 11. Installing - advanced options.............. 43 Installing as a non-root user......... 43 Install a WebSphere test environment: launchpad is not detecting the WebSphere Integration Developer installation.............. 44 Chapter 12. Starting WebSphere Integration Developer........ 45 Using the "-clean" option when starting WebSphere Integration Developer........... 45 Enabling the WebSphere test environment for testing from WebSphere Business Modeler...... 46 Chapter 13. Installing on Citrix Presentation Server......... 49 Configuring the Citrix Presentation Server.... 49 Copyright IBM Corp. 2009 v

Chapter 14. Modifying installations.. 51 Chapter 15. Updating WebSphere Integration Developer........ 53 Chapter 16. Uninstalling the product.. 55 Uninstalling the WebSphere test environment... 55 Preparing to reinstall WebSphere Integration Developer after a failed uninstallation..... 56 Chapter 17. Rolling back updates... 57 Chapter 18. Installing optional software 59 Installing Lotus Forms software....... 59 Notes for Lotus Forms Viewer and Lotus Forms Server installations........... 60 Downloading Lotus Forms Server 3.5.1 Fix Pack 1................. 60 Installing Asset Repository......... 61 Chapter 19. Troubleshooting the installation process......... 63 Notices.............. 67 Terms of use............ 71 vi WebSphere Integration Developer: Installation Guide

Chapter 1. Overview This installation guide provides instructions for installing, updating and uninstalling WebSphere Integration Developer using IBM Installation Manager. Refer to the WebSphere Integration Developer support site for updated documentation and troubleshooting information. IBM Installation Manager IBM Installation Manager is a program that helps you install the WebSphere Integration Developer packages on your workstation. It also helps you update, modify, and uninstall this and other packages that you install. A package can be a product, a group of components, or a single component that is designed to be installed by the Installation Manager. IBM Installation Manager offers a number of time-saving features. It keeps track of what you are about to install, software components that you have already installed, and components that are available for you to install. It searches for updates so you know that you are installing the latest version of a WebSphere Integration Developer product package. Installation Manager also provides tools for managing licenses for the product packages that it installs. It provides tools for updating and modifying packages. You can also use Installation Manager to uninstall product packages. Installation Manager comprises seven wizards that make it easy to maintain your product packages through their life cycles: v The Install Packages wizard walks you through the installation process. You can install a product package by simply accepting the defaults, or you can modify the default settings to create a custom installation. Before you install a product package, you are provided with a complete summary of the selections that you have made throughout the wizard. With the wizard you can install one or more product packages at the same time. v The Update Packages wizard searches for available updates to product packages that you have installed. An update might be a released fix, a new feature, or a new version of the product. Details of the contents of the update are provided in the wizard. You can choose whether to apply an update. v With the Modify Packages wizard, you can modify specific elements of a package that you have already installed. During your initial installation of the product package, you select the features you want to install. If you find later that you require other features, you can use the Modify Packages wizard to add them to your product package installation. You can also remove features, and add or remove languages. v The Manage Licenses wizard helps you to set up the licenses for your packages. Use this wizard to change your trial license to a full license, to set up your servers for floating licenses, and to select which type of license to use for each package. This wizard is not used for the WebSphere Integration Developer packages. v The Import wizard helps you to add existing packages that were installed using installation tools other than Installation Manager so that they can be managed by Installation Manager. v With the Roll Back Packages wizard you can revert to a previously installed version of an eligible package. v The Uninstall Packages wizard helps you to remove a product package from your computer. You can uninstall more than one package at a time. Copyright IBM Corp. 2009 1

Installation quick reference Managing your WebSphere Integration Developer package installation involves several different tasks, for example installing the package, applying updates, and adding additional features to the package. The following table presents a list of objectives related to managing your WebSphere Integration Developer package, a set of high-level steps for accomplishing each objective, and the result of performing those steps. Table 2. Summary of installation tasks. Installation objective Installation steps Result Install WebSphere Integration Developer as a stand-alone product. Install WebSphere Integration Developer into an existing package group of compatible products. Note: Installing WebSphere Integration Developer into an existing Eclipse-only workbench environment is not supported. Install the WebSphere Integration Developer package into its own package group: 1. Begin the installation following the steps in Chapter 6, Installing from the product launchpad program, on page 25 2. On the second Location panel of the Install Packages wizard, Select Create a new package group (default). 3. Follow the on-screen instructions on the Install Packages wizard to complete the installation. Install WebSphere Integration Developer into a package group with other compatible Eclipse-based products: 1. Begin the installation following the steps in Chapter 6, Installing from the product launchpad program, on page 25. 2. On the second Location panel of the Install Packages wizard, Select Use the existing package group. 3. Select the package group that you want to install into. For example, if you want to use WebSphere Integration Developer together with an existing compatible installation of WebSphere Business Modeler on your system, select the package group where you have installed WebSphere Business Modeler. 4. Follow the on-screen instructions on the Install Packages wizard to complete the installation. WebSphere Integration Developer product does not share a user interface or workbench with other Eclipse-based products. WebSphere Integration Developer shares a user interface, or workbench, with all products installed in the same package group. 2 WebSphere Integration Developer: Installation Guide

Table 2. Summary of installation tasks. (continued) Installation objective Installation steps Result Install WebSphere Integration Developer with the intention to install additional Eclipse-based products (for example, WebSphere Business Modeler) using Installation Manager in the future. Install the WebSphere Test Environment when you install WebSphere Integration Developer. Install additional WebSphere Integration Developer features into an existing installation of WebSphere Integration Developer Version 7.0, or remove already-installed features from the WebSphere Integration Developer package. Install WebSphere Integration Developer into its own package group: 1. Begin the installation following the steps in Chapter 6, Installing from the product launchpad program, on page 25. 2. On the second Location panel of the Install Packages wizard, Select Create a new package group (default). 3. Follow the on-screen instructions on the Install Packages wizard to complete the installation. 4. During subsequent installations of compatible Eclipse-based products, install additional product packages into the same package group where WebSphere Integration Developer is installed. Install the WebSphere Test Environment package: 1. Begin the installation following the steps in Chapter 6, Installing from the product launchpad program, on page 25. 2. Click Install WebSphere Application Server on the launchpad. This is a prerequisite for hosting a test environment. The installation of WebSphere Application Server proceeds without additional input. A message will appear when the installation is completed. 3. Click Install WebSphere Process Server on the launchpad to complete the installation of the test server. 4. Follow the instructions to complete the installation of the WebSphere Process Server test environment through the installation manager. Note: Unit test environments require a both a server installation and profile server instances. Ensure that you pick a suitable profile for your test environment on the feature panel of the server installation. Modify the installed WebSphere Integration Developer package: 1. From the Installation Manager Start page, click Modify Packages. 2. Follow the steps in the wizard to add the desired features. Deselecting features removes them from the package. WebSphere Integration Developer is installed first. Additional Eclipse-based product packages are installed later and share a user interface or workbench with WebSphere Integration Developer. The WebSphere Test Environment is added to the same package group as WebSphere Application Server ND, and both products share a common user interface, or workbench. The WebSphere Test Environment is installed to widhome_wte\runtimes\bi_v7. Note: On the Features panel, you must select to create a profile. Select WebSphere Business Monitor, WebSphere Enterprise Service Bus or WebSphere Process Server profiles. Additional WebSphere Integration Developer features are installed and are made available from the WebSphere Integration Developer workbench, for example, IBM WebSphere Adapters. Features which are deselected are removed. Chapter 1. Overview 3

Table 2. Summary of installation tasks. (continued) Installation objective Installation steps Result Install Updates to WebSphere Integration Developer Use WebSphere Integration Developer Version 7.0 in a different supported language. Windows 2000 Install WebSphere Integration Developer with the Monitor Model editor feature. Use the Update Packages wizard to update the WebSphere Integration Developer package: 1. From the Installation Manager Start page, click Update Packages. 2. Follow the steps in the wizard to add the recommended updates. Install the national language versions of the packages, and modify the language setting for the package group: 1. From the Installation Manager Start page, click Modify Packages. 2. Follow the steps in the wizard to change the language settings for the package group where WebSphere Integration Developer is installed. Install the WebSphere Integration Developer and select Monitor Model editor on the features panel: 1. Begin the installation following the steps in Chapter 6, Installing from the product launchpad program, on page 25 2. On the Features panel of the Install Packages wizard, Select Monitor Model editor. 3. Follow the on-screen instructions on the Install Packages wizard to complete the installation. Recommended fixes are downloaded and applied to the WebSphere Integration Developer package. Additional national language support is installed. This language setting applies to WebSphere Integration Developer and all packages installed in the same package group. The Monitor Model editor provides wizards, libraries, and a test environment to help you create and test monitor models. It will be installed in your WebSphere Integration Developer environment. It is recommended that you select WebSphere Business Monitor as one of your WebSphere Test environments so that you can test the monitor models that you create with Monitor Model editor. Uninstall WebSphere Integration Developer Use the Uninstall Packages wizard to uninstall the WebSphere Integration Developer package: 1. From the Installation Manager Start page, click Uninstall Packages. 2. Follow the steps in the wizard to complete the uninstall operation. Ensure that you create a WebSphere Business Monitor profile during your WebSphere test environment installation. WebSphere Integration Developer is uninstalled. Installation Manager and other products that were installed into the same package group remain installed. 4 WebSphere Integration Developer: Installation Guide

Table 2. Summary of installation tasks. (continued) Installation objective Installation steps Result Install a set of Eclipse features and plug-ins into an existing installation of WebSphere Integration Developer Version 7.0 (for example, using Eclipse Update Manager) Install Eclipse features and plug-ins into an existing WebSphere Integration Developer installation: 1. Add the Eclipse features into the \features directory and the plug-ins into the \plugins directory in the package group containing WebSphere Integration Developer, for example, Windows 2000 C:\Program Files\IBM\WID7 or 2000 Linux /opt/ibm/wid7. 2. Restart WebSphere Integration Developer with the -clean option (see Using the "-clean" option when starting WebSphere Integration Developer on page 45. Eclipse plug-ins are installed into the same package group as WebSphere Integration Developer and share the user interface or workbench with all products installed in the same package group. Chapter 1. Overview 5

6 WebSphere Integration Developer: Installation Guide

Chapter 2. Installation requirements This section details hardware, software, and user privilege requirements that must be met in order to successfully install and run your software. For the most up-to-date, detailed system requirements, see WebSphere Integration Developer detailed system requirements. Previous versions of WebSphere Integration Developer cannot be upgraded to version 7.0. Different versions of WebSphere Integration Developer can coexist on your workstation, but they must not be installed in the same directory. Hardware requirements Hardware requirements for installing WebSphere Integration Developer are described. The following hardware must be installed before you install WebSphere Integration Developer: v Intel Pentium III 1 GHz processor minimum (Higher is recommended). v 1 GB RAM minimum (2 GB RAM is recommended). v Disk space: For a default installation, a minimum 2.81 GB of available disk space is required. This includes the temporary disk space required during installation. For a full installation, excluding the test environment, a minimum 4.76 GB of available disk space is required. This includes the temporary disk space required during installation. For a full installation, including the test environment, a minimum of 6.76 GB of available disk space is required. Note that this assumes you are installing only one test environment profile. If you install more than one profile the disk space requirement will be higher. v Display resolution: Minimum 1024 x 768 display resolution (1280 x 1024 is recommended). For the most up-to-date, detailed system requirements, see WebSphere Integration Developer detailed system requirements. Software requirements Software and operating system requirements for installing WebSphere Integration Developer are described. Operating systems The following software must be installed before you install WebSphere Integration Developer v One of the following operating systems must be installed: Windows Server 2003, Enterprise Edition SP2 Windows Server 2003, Standard Edition SP2 Windows Server 2008, Enterprise Edition Windows Server 2008, Standard Edition Windows Vista Business Edition Windows Vista Enterprise Edition Windows XP Professional SP1, SP2 and SP3 Copyright IBM Corp. 2009 7

Windows XP Professional x64 SP2 (in 32-bit mode) Red Hat Enterprise Linux (RHEL) 4 WS - Update 6 Red Hat Enterprise Linux (RHEL) 5 WS - Update 1 Red Hat Enterprise Linux (RHEL) 4 Desktop Red Hat Enterprise Linux (RHEL) 5 Desktop - Update 1 SUSE Linux Enterprise Server 9 SP4 SUSE Linux Enterprise Server 10 SP1 SUSE Linux Enterprise Desktop 9 SP1 to SP4 SUSE Linux Enterprise Desktop 10 v The above listed Windows and Linux operating systems support all of the national languages that WebSphere Integration Developer supports. Note: RHEL 4.0 requires libxp-1.0.0-8.i386.rpm and compat-libstdc++-33-3.2.3-55.fc5.i386.rpm For the most up-to-date, detailed system requirements, see WebSphere Integration Developer detailed system requirements. Other software requirements Additional software requirements for installing WebSphere Integration Developer are described. v You will need a Web browser to view the release notes and the installation guide. v 2000 Linux You will need the GTK, Version 2.2.1 or later. v 2000 Linux You must have Mozilla 1.4 GTK2, Mozilla 1.5 GTK2 or Mozilla 1.6 GTK2 installed before you can run WebSphere Integration Developer. The version of Mozilla installed on your system varies with your Linux distribution. v You will need Adobe Flash Player 9. 2000 Linux In order to view certain product overview information, links to tutorials, samples and migration information, a compatible browser must be installed. Follow the steps below to install a compatible version of Mozilla that can be used with WebSphere Integration Developer. These changes will not replace your existing browser. If you are using SUSE LINUX Enterprise Server, the following environment variable settings are required: v export MOZILLA_FIVE_HOME=/opt/mozilla/lib v export LD_LIBRARY_PATH=$LD_LIBRARY:/opt/mozilla/lib These can be set at the system level, user level, or within a script to launch the product. To set these environment variables at the user level, add the above lines to your.profile file. In order for this to take effect you will need to logout and login again. If this does not work or you are using another Linux distribution, use the following steps to install a compatible version of Mozilla that can be used with WebSphere Integration Developer; these changes will not replace your existing browser. 1. Download a precompiled version of the Mozilla browser from the following site: http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.12/contrib/mozilla-i686-pclinux-gnu-1.7.12-gtk2+xft.tar.gz If this link does not work, look for a Linux (x86) for GTK2 and Xft build from the following site: http://www.mozilla.org/releases/ 2. Extract this file to a location on your workstation, for example, as /opt/mozilla-1.7.12-gtk2+xft. 3. From a command prompt, run the following commands: 8 WebSphere Integration Developer: Installation Guide

cd /opt/mozilla-1.7.12-gtk2+xft./mozilla 4. Exit WebSphere Integration Developer and restart it with the same workspace directory. 5. Update your.profile file to set these environment variables at the user level. In order for this to take effect you will need to logout and login again. export MOZILLA_FIVE_HOME=/opt/mozilla-1.7.12-gtk2+xft export LD_LIBRARY_PATH=$LD_LIBRARY:/opt/mozilla-1.7.12-gtk2+xft 6. When the Welcome is displayed, press the Home icon to refresh the content. If the Welcome is not displayed, open it using Help > Welcome. Note: If Mozilla is located in the /usr/lib path, use /usr/../usr/lib instead of /usr/lib when setting the LD_LIBRARY_PATH and MOZILLA_FIVE_HOME variables. For more technical information on compatible browser versions, see http://www.eclipse.org/swt/ faq.php#whatisbrowser User privileges requirements You must have a user ID that meets the following requirements before you can install WebSphere Integration Developer. v Your user ID must not contain double-byte characters. v Your user ID must not contain letters from the Cyrillic alphabet. v You do not need to be an administrator to install WebSphere Integration Developer. v You must be an administrator (root) to install from the product launchpad. v You can install using the Installation Manager as a non-administrator. v If you want to install as a non-administrator see the information on using the userinst command in the topics Installing from DVD and Installing from an installation image on your workstation. v If you do want to install as an administrator your user credentials need the following properties. Windows 2000 The user privileges required for installing depend on the version of Windows on your computer: You must log in to the Administrator account (or run as Administrator; right-click the program file or shortcut and select Run as Administrator) to perform the following tasks: - Install or update IBM Installation Manager (the application that installs and updates WebSphere Integration Developer) - Install or update a product offering For other supported Windows versions, you must have a user ID that belongs to the Administrators group. Chapter 2. Installation requirements 9

10 WebSphere Integration Developer: Installation Guide

Chapter 3. Planning to install Read all the topics in this section before you begin to install any of the product features. Effective planning and an understanding of the key aspects of the installation process can help ensure a successful installation. One very important point to consider is the amount of disk space that you will require. If you are installing a test environment it must be installed to the same location (actually to a peer directory) as WebSphere Integration Developer. Use the largest disk you have available. Typical installation configurations This document lists some common ways of working and the necessary installation steps to achieve the necessary configurations.. Using Lotus Forms You can use WebSphere Integration Developer to build business applications that involve human tasks. These tasks are performed by people and thus require user interfaces. There are a variety of technologies that can be used for these user interfaces, one option is to use IBM Lotus Forms. To install an appropriate configuration do the following: 1. Start the installation of WebSphere Integration Developer using the product launchpad. See Chapter 6, Installing from the product launchpad program, on page 25. Note: You can achieve the same configuration using Installation Manager (see Chapter 7, Installing with IBM Installation Manager, on page 27) directly or silently (see Chapter 8, Installing silently, on page 31) using a response file (see Creating a response file with Installation Manager on page 33). 2. On the first Install Packages page of the Installation Manager select IBM Lotus Forms Designer. 3. When finished with the WebSphere Integration Developer installation return to the product launchpad and install a WebSphere test environment (see Chapter 9, Installing the WebSphere test environment using the launchpad, on page 39). You can choose a WebSphere Process Server or WebSphere Business Monitor installation to act as your test environment. Note: You could also use a WebSphere Enterprise Service Bus profile on your WebSphere Process Server installation, but since human tasks are not supported on WebSphere Enterprise Service Bus this choice is not relevant to this scheme. 4. When finished with the WebSphere test environment installation return to the product launchpad and click Additional Product Installation in the left-hand navigation pane and select Install Lotus Forms Server 3.5.1 and on Windows 2000 Install Lotus Forms Viewer 3.5.1. See Chapter 18, Installing optional software, on page 59 for details. This will deploy all of the software you require to view, create and edit Lotus Forms. WebSphere Business Monitor as your test environment You have a choice of runtime environments that you can employ as your WebSphere test environment. Follow these instructions to deploy a WebSphere Business Monitor test environment. 1. Start the installation of WebSphere Integration Developer using the product launchpad. See Chapter 6, Installing from the product launchpad program, on page 25. Copyright IBM Corp. 2009 11

Note: You can achieve the same configuration using Installation Manager (see Chapter 7, Installing with IBM Installation Manager, on page 27) directly or silently (see Chapter 8, Installing silently, on page 31) using a response file (see Creating a response file with Installation Manager on page 33). 2. On the Features page of the Installation Manager select Monitor Model editor. 3. When finished with the WebSphere Integration Developer installation return to the product launchpad and start the installation of a WebSphere test environment (see Chapter 9, Installing the WebSphere test environment using the launchpad, on page 39). 4. On the first Install Packages page of the Installation Manager select WebSphere Business Monitor as your test environment. You can select just WebSphere Business Monitor or both WebSphere Business Monitor and WebSphere Process Server. If you already have a WebSphere Process Server test environment select WebSphere Business Monitor to install it into the existing test environment. 5. On the Features panel, ensure that you select to create a WebSphere Business Monitor profile. 6. This pathway provides you with the tools you need to build monitor models into your applications and monitor them in your test environment. Installation scenarios There are a number of scenarios that you can follow when installing WebSphere Integration Developer. The following are some of the factors that might determine your installation scenario: v The format and method by which you access your installation files (for example, from DVD or files downloaded from IBM Passport Advantage ). v The location for your installation (for example, you can install the product onto your own workstation, or make the installation files available to your enterprise). v The type of installation (for example, you can use the Installation Manager wizard, or install silently). These are the typical installation scenarios you might follow: v Installing from DVD. v Installing from a downloaded electronic installation image on your workstation. v Installing from an electronic installation image on a shared drive. Note that in the latter three scenarios you can choose to run the Installation Manager program in silent mode to install WebSphere Integration Developer. For details on running Installation Manager in silent mode, see Chapter 8, Installing silently, on page 31. Note also that you can install updates at the same time that you install the base product package. Installing from DVD In this installation scenario, you have the DVDs that contains the product package files, and typically you are installing WebSphere Integration Developer on your own workstation. Refer to Installing from DVD on page 21 for an overview of the steps. Installing from a downloaded electronic installation image on your workstation In this scenario, you have downloaded the installation files from IBM Passport Advantage and you will install WebSphere Integration Developer on your own workstation. Refer to Installing from an installation image on your workstation on page 22 for an overview of the steps. Installing from an electronic installation image on a shared drive In this scenario, you will place the electronic installation image on a shared drive so that users in your enterprise can access the installation files for WebSphere Integration Developer from a single location. 12 WebSphere Integration Developer: Installation Guide

Refer to Installing from an installation image on a shared drive on page 23 for an overview of the steps. Deciding which features to install You can customize your software product by selecting which features of WebSphere Integration Developer to install. When you install the WebSphere Integration Developer product package using IBM Installation Manager, the installation wizard displays the features available in the product package. From the features list, you can select which features to install. A default set of features is selected for you (including any required features). Installation Manager automatically enforces any dependencies between features and prevents you from clearing any required features. Adapters can be individually selected. Only install the adapters that you will require. Note: After you finish installing the package, you can still add or remove features from your software product by running the Modify Packages wizard in Installation Manager. See Chapter 14, Modifying installations, on page 51 for more information. Features The following table shows the features of WebSphere Integration Developer that you can choose to install. Default selections of features to install may vary. If a feature has already been installed, it will not be selected by default and will not be installed again. Table 3. Features of WebSphere Integration Developer that you can choose to install. Feature group Feature Description Selected by default IBM Installation Manager 1.3.3 IBM Lotus Forms Designer 3.5.1 Fixpack 1 IBM WebSphere Integrated Developer 7.0.0.0 E-mail, Flat File, FTP and JDBC IBM WebSphere Adapters The Installation Manager helps you to install WebSphere Integration Developer and related tools. Lotus Forms Designer allows you to create and edit Lotus Forms to use as user interfaces to your human tasks. The core functionality of WebSphere Integration Developer. Provides tools in a comprehensive development environment to build integrated solutions. Send and receive e-mail to and from an e-mail server using WebSphere Adapter for Email. Read from, and write to, a file on a local file system using the WebSphere Adapter for Flat Files. Read from, and write to a file on remote system using the WebSphere Adapter for File Transfer Protocol (FTP). Yes (mandatory) Yes (This option is not displayed if you did not select to install Lotus Forms on the first Install panel of the Installation Manager). Yes (mandatory) Yes Chapter 3. Planning to install 13

Table 3. Features of WebSphere Integration Developer that you can choose to install. (continued) Feature group Feature Description Selected by default Additional IBM WebSphere Adapters Local help contents Windows 2000 Monitor Model editor Domino adapter CICS Adapter IMS Adapter iseries Adapter J D Edwards Adapter JDBC Adapter Oracle Adapter PeopleSoft Adapter SAP Adapter Siebel Adapter Adapters access programs and data on Enterprise Information Systems (EISs). Create a service that exchanges information with a Lotus Domino server. Create integrated processes, which can create and access Domino documents, without special coding. During outbound processing the adapter supports Create, Retrieve, Update, Delete, Exists and RetrieveAll operations. The adapter receives a request in the form of a business object from a service, it processes the request and sends the response back to the calling component, during inbound processing, the adapter polls the Domino server at intervals for Domino documents that are ready for processing. Create and access services to exchange information with COBOL, C, PL/I programs and data on Customer Information Control Systems (CICS) transaction systems. Create and access services to exchange information with COBOL, C, and PL/I programs and data on IBM Information Management System (IMS) transaction systems. Create and access services that use the program call markup language (PCML) standard to call an RPG, COBOL, and service programs on the target IBM i machine, and send or receive messages to an IBM i data queue. Create and access services with the JD Edwards EnterpriseOne Server using WebSphere Adapter for JD Edwards EnterpriseOne. Create and access services with the database system using WebSphere Adapter for JDBC. Create and access services to exchange information with the Oracle E-Business Suite. Create and access services to exchange information with WebSphere Adapter for PeopleSoft Enterprise. Create and access services to exchange information with the SAP server. Create and access services to exchange information with the Siebel Business Application Server. Installs a local version of the help contents, alternatively you can use the version that is available on the internet. Provides wizards, libraries, and a test environment to help you create and test monitor models. It will be installed in your WebSphere Integration Developer environment. No No No No No No No No No No No No Yes 14 WebSphere Integration Developer: Installation Guide

Table 3. Features of WebSphere Integration Developer that you can choose to install. (continued) Feature group Feature Description Selected by default Client development tools Lifecycle integration clients Additional development tools Web development tools Portlet and Portal tools Asset repository client Rational ClearCase SCM Adapter Rational Team Concert - Client Most applications require client interfaces through which customers or staff can enter data. This group of tools is provided to allow you to create customized clients for your applications. Provides tools for building Web 2.0 and Java EE Web applications using JavaServer Faces (JSF), JavaServer Pages (JSP), servlets, and HTML. Also provides the Apache Struts framework for developing Java EE Web applications. Provides tools to create, customize, test, debug, and deploy portal applications. The Portal development tools support IBM WebSphere Portal versions 6.0 and 6.1. Provides an asset repository and provides integrations and client plug-ins for the IBM Rational Team Unifying Platform. The asset repository client is a centrally accessible location for storing and sharing business process management (BPM) artifacts. IBM Rational Asset Manager V 7.1 must be installed and configured on a server so that the asset repository client can connect to it. Provides the IBM Rational ClearCase SCM and ClearCase MVFS plug-ins, which enable versioning of software artifacts in ClearCase versioned object bases (VOBs) using snapshot views and dynamic views when ClearCase VOB and view servers are also installed. The Rational Team Concert - Client contains everything you need to connect to the Rational Team Concert Server from your workstation and interact with your team. Provides relational database tools to work with tables, views, and filters. With these tools, you can create physical database models by means of reverse engineering database tables or using DDL scripts. You can also use the tools to create SQL statements, DB2 routines (such as stored procedures and user-defined functions), and various types of files. Additionally provides a graphical editing environment that you can use to depict Java classes, enterprise beans and other code elements and artifacts. No No No No No No No No Security considerations In WebSphere Integration Developer 7.0, both administrative security and application security are enabled by default. Server security, including administrative security and application security, is automatically enabled for those test environment servers that you choose to install with WebSphere Integration Developer 7.0. During installation of the test environment you are prompted for a user name and password to be used for administering server security. Chapter 3. Planning to install 15

Note that if you disable or enable server security in a server administrative console, you must ensure that these changes are also specified for the same server in the server configuration editor or the Window > Preferences > Server > Security preferences page of WebSphere Integration Developer. Information about changing the user ID and password, and about disabling or enabling server security, is found in the Security documentation in the WebSphere Integration Developer help: Help > Help Contents > WebSphere Integration Developer > Managing security. Coexistence considerations If you plan to install multiple IBM Eclipse-based products on the same workstation, review the information in this section. Offering coexistence considerations Some products are designed to coexist and share function when they are installed in the same package group. A package group is a location where you can install one or more software products or packages to share a common user interface or workbench. When you install each package, you select whether you want to install the package to an existing package group, or whether you want to create a new one. IBM Installation Manager will block products that are not designed to share a package group or do not meet version tolerance and other requirements. If you want to install more than one product at a time, the products must be able to share a package group. Any number of eligible products can be installed to a package group. When a product is installed, its function is shared with all of the other products in the package group. If you install a development product and a testing product into one package group, when you start either of the products, you have both the development and testing functionality available to you in your user interface. If you add a product with modeling tools, all of the products in the package group will have the development, testing, and modeling functionality available. If you want WebSphere Integration Developer 7.0 to coexist with a Rational software product (for example, Rational Application Developer for WebSphere Software), the Rational software product must be at version 7.5.4 or higher. When you have an earlier version of the Rational software product you must correct this incompatibility by updating the version to 7.5.4 or higher, or choose a new package group. When you want to add a Rational software product to the same package group as WebSphere Integration Developer 7.0, you must install it directly at the required 7.5.4 (or higher) level by searching for available updates during the Rational installation (using Check for Other Versions and Extensions), or by pointing to the 7.5.4 update repository location along with the base Rational repository location. For more information on coexisting with Eclipse-based products see Planning for WebSphere Integration Developer to coexist with other Eclipse-based products Note: Each product installed into a unique location may be associated with only one package group. A product must be installed into multiple locations in order to be associated with multiple package groups. Coexisting installations of WebSphere Integration Developer You can install WebSphere Integration Developer 7.0 on to a system with an existing installation of WebSphere Integration Developer 7.0, but the two cannot be part of the same package group. Similarly, you can install WebSphere Integration Developer 7.0 on to a system with an existing installation of WebSphere Integration Developer version 6.x, but the two cannot be part of the same package group. Installation repositories IBM Installation Manager retrieves product packages from specified repository locations. 16 WebSphere Integration Developer: Installation Guide

If the WebSphere Integration Developer launchpad is used to start Installation Manager, the default repository information is passed to Installation Manager. If the Installation Manager is started directly, for example from the Start menu, you must specify installation repositories that contain the product packages that you want to install. See Setting repository preferences in Installation Manager. By default, IBM Installation Manager uses an embedded URL in each software development product to connect to a repository server over the Internet. Installation Manager then searches for the product packages as well as new features. You can use the IBM Packaging Utility to: v Generate a new repository for packages v Copy packages to a new repository v Delete packages that are no longer needed. For more information see The IBM Packaging Utility. Setting repository preferences in Installation Manager When you start the installation of Installation Manager from the WebSphere Integration Developer launchpad program, the location of the repository that contains the product package you are installing is automatically defined in IBM Installation Manager when it starts. However, if you start Installation Manager directly (for example, installing Installation Manager from a repository located on a Web server) then you must specify the repository preference (the URL for the directory that contains the product package) in Installation Manager before you can install the product package. Specify these repository locations on the Repositories page of the Preferences window. By default, Installation Manager uses an embedded URL in each software development product to connect to a repository server through the Internet and search for installable packages and new features. Your organization may require you to redirect the repository to use intranet sites. Note: If not installing from DVD or a local installation image, be sure to obtain the installation package repository URL from your administrator before starting the installation process. To add, edit, or remove a repository location in Installation Manager: 1. Start Installation Manager. 2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens, showing any available repositories, their locations, and whether they are accessible. 3. On the Repositories page, click Add Repository. 4. In the Add repository window, type the URL of the repository location or browse to it and set a file path. 5. Click OK. The new or changed repository location is listed. If the repository is not accessible, a red x is displayed in the Accessible column. 6. Click OK to exit. Note: For Installation Manager to search the default repository locations for the installed packages, ensure the preference Search service repositories during installation and updates on the Repositories preference page is selected. This preference is selected by default. Package groups and the shared resources directory When you install the WebSphere Integration Developer package using IBM Installation Manager, you must choose a shared resources directory (if WebSphere Integration Developer is the first product to be installed using Installation Manager) and a package group. Chapter 3. Planning to install 17

Package groups During the installation process, you must specify a package group for the WebSphere Integration Developer package. A package group represents a directory in which packages share a common user interface or workbench with other packages in the same group. When you install the WebSphere Integration Developer package using Installation Manager, you can create a new package group or install the packages into an existing package group. Some packages might not be able to share a package group, in which case the option to use an existing package group will be disabled. Note that when you install multiple packages at the same time, all the packages are installed into the same package group. A package group is assigned a name automatically; however, you choose the installation directory for the package group. You can use the IBM Packaging Utility to: v Generate a new repository for packages v Copy packages to a new repository v Delete packages that are no longer needed. For more information see The IBM Packaging Utility. After you create the package group by successfully installing a product package, you cannot change the installation directory. The installation directory contains files and resources specific to the WebSphere Integration Developer package installed into that package group. Eclipse plug-ins in the product package that can potentially be used by other package groups are placed in the shared resources directory. Shared resources directory The shared resources directory is the directory where Eclipse plug-ins are located so that they can be used by one or more product package groups. Important: You can specify the shared resources directory once: the first time that you install a package. For best results, use your largest drive for this. You cannot change the directory location unless you uninstall all packages. 18 WebSphere Integration Developer: Installation Guide

Chapter 4. Preinstallation tasks There are a few tasks which should be completed before beginning the installation process. Before you install the product, complete these steps: 1. Confirm that your system meets the requirements described in the section Chapter 2, Installation requirements, on page 7. 2. Confirm that your user ID meets the required access privileges for installing the product. See User privileges requirements on page 9. 3. Read the section Chapter 3, Planning to install, on page 11 and give particular attention to the topic Coexistence considerations on page 16. 4. 2000 Linux If you want to enable the product for use by users other than root, then you must set the umask variable to 0022 before you install the product. To set this variable, log in as root user, start a terminal session, and type umask 0022. Copyright IBM Corp. 2009 19

20 WebSphere Integration Developer: Installation Guide

Chapter 5. Installation overview There are three installation scenarios depending on the manner in which you have access to the installable files. Overviews for each of these scenarios are provided in this section. There are two ways that you can graphically install WebSphere Integration Developer. The first path is using the product Launchpad. You can only install as a root or administrator through the launchpad. There are some advantages to using the launchpad, for instance the sequence of steps to install WebSphere Integration Developer and an associated test environment are presented sequentially. The second path is using the Installation Manager. If you want to install as a non-adminstrator, then you must use Installation Manager. Using Installation Manager you can install WebSphere Integration Developer and any other software you require. You can install without using these interfaces. Silent installation using response files is supported and is recommended when you are installing to a large set of servers. The response files provide a convenient way to automate your installation process. The following sections provide an overview of the installation scenarios that are described in the section Installation scenarios on page 12. You can access detailed instructions from links in the main steps. Installing from DVD In this installation scenario, you have the DVDs that contains the installation files, and typically you are installing WebSphere Integration Developer on your own workstation. The following are the general steps for installing from DVDs: 1. Complete the preinstallation steps listed in Chapter 4, Preinstallation tasks, on page 19. 2. Insert the first installation DVD into your DVD drive. 3. 2000 Linux Mount the DVD drive. a. Log in as a user with root authority. b. Enter the following command: mount -t iso9660 -o ro /dev/cdrom /cdrom where /cdrom represents the mount point of the disk. c. Log out. 4. If auto-run is enabled on your system, the WebSphere Integration Developer launchpad program automatically opens. If auto-run is not enabled and you are installing as an administrative user, start the launchpad program. Refer to Starting the launchpad program on page 26 for details. Note: If IBM Installation Manager is not detected on your workstation, then it is installed at the same time as the WebSphere Integration Developer package. 5. If you are installing as a non-administrative user and the launchpad program is running, stop the launchpad program. 6. If you are installing as a non-administrative user, launch the userinst program. In a command line, change to the root directory of DVD 1 and issue the following command: v Windows 2000 Run disk1\im_win32\userinst.exe v 2000 Linux Run disk1/im_linux/userinst 7. Follow the on-screen instructions in the Install Packages wizard to complete the installation. Copyright IBM Corp. 2009 21