Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Transcription

1 IBM InfoSphere Information Server Version 8 Release 5 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5 SC

2

3 IBM InfoSphere Information Server Version 8 Release 5 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5 SC

4 Note Before using this information and the product that it supports, read the information in Notices and trademarks on page 53. Copyright IBM Corporation 2006, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Part 1. Overview of migration Chapter 1. Migrating to IBM InfoSphere Information Server, Version Migration strategies Part 2. Version and earlier migrations Chapter 2. Migrations from Version and earlier Chapter 3. Migration from DataStage and earlier versions Exporting projects Exporting projects from the DataStage Manager client Exporting projects from the command line Saving DataStage settings files Saving settings files (UNIX and Linux) Saving the DSParams file (Windows) Move job dependency objects Migrating hashed files Remove previous versions of DataStage Removing a DataStage server (Windows) Removing a DataStage server (Linux, UNIX).. 14 Removing DataStage clients Importing DataStage projects Restoring contents of DataStage or earlier settings files Restoring DataStage job dependencies Restoring hashed files Recompiling jobs Updating jobs that use the QualityStage 7.5 plug-in 18 Switching between different versions of clients.. 18 Multiple server method (Linux and UNIX only).. 19 Installing Version 8.5 in addition to existing DataStage servers Installing IBM InfoSphere DataStage, Version 8.5 clients in addition to existing clients Starting and stopping multiple DataStage servers 21 Connecting to multiple DataStage servers Chapter 4. Migration from QualityStage 7.5 and earlier releases Job migration in legacy operational mode QualityStage job migration in expanded form Rule set migration Match specification migration Installing the WebSphere QualityStage migration utility Running the QualityStage migration utility Importing the migrated files into the Version 8.5 Designer client Preparing migrated QualityStage jobs for operation Migrating real-time QualityStage jobs from Release 7 to Version Replace InfoSphere QualityStage 7 data quality stages Chapter 5. Migration from IBM WebSphere RTI 7.5, 7.5.1, and installations Migrating RTIX files to Version Part 3. Client-only upgrades Chapter 6. Upgrading a client tier-only installation to Version Part 4. Appendixes Product accessibility Accessing product documentation Reading command-line syntax Links to non-ibm Web sites Notices and trademarks Contacting IBM Index Copyright IBM Corp. 2006, 2010 iii

6 iv Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

7 Part 1. Overview of migration Copyright IBM Corp. 2006,

8 2 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

9 Chapter 1. Migrating to IBM InfoSphere Information Server, Version 8.5 Migration strategies Migration enables you to move existing source installations to new IBM InfoSphere Information Server, Version 8.5, installations. The current version and the translated versions of this information are on the Web at com.ibm.swg.im.iis.productization.iisinfsv.migrate.doc/topics/migr_container.html. The version of your existing installation determines how you migrate to a new IBM InfoSphere Information Server, Version 8.5 installation. You will use different migration strategies and methods to migrate to Version 8.5 from existing installations. Plan your strategy and choose your migration method based on the version of your existing installation. Successful migration requires that you understand your IBM InfoSphere Information Server installation topology on the source computers and your InfoSphere Information Server installation topology on the target computers. You must use one of the following methods to migrate your source installation to a new Version 8.5 installation: Table 1. Supported migrations to Version 8.5 Existing installation (source) Information Server, Version and later DataStage, releases from and earlier QualityStage, release 7.5 and earlier IBM WebSphere RTI 7.5, 7.5.2, and Migration method If you want to do this type of migration, see docview.wss?uid=swg Export projects and save the settings files from the existing installation. Then import the projects and move the settings files to the Version 8.5 installation. See Chapter 3, Migration from DataStage and earlier versions, on page 9. Use the QualityStage migration utility. See Chapter 4, Migration from QualityStage 7.5 and earlier releases, on page 25. Use the WebSphere RTI Export Wizard. See Chapter 5, Migration from IBM WebSphere RTI 7.5, 7.5.1, and installations, on page 35. Note: You do not migrate computers that only have the client tier installed on them. Computers that only have client tier software installed do not contain installation information or data that requires migration. To upgrade these computers to Version 8.5, you run the InfoSphere Information Server suite installation program. Copyright IBM Corp. 2006,

10 4 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

11 Part 2. Version and earlier migrations Copyright IBM Corp. 2006,

12 6 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

13 Chapter 2. Migrations from Version and earlier You can migrate from previous versions of DataStage, QualityStage, and WebSphere RTI to a new IBM InfoSphere Information Server, Version 8.5 installation. Export projects and jobs from release and earlier versions of DataStage and QualityStage and then import the projects and jobs to an InfoSphere Information Server, Version 8.5 installation. You can also migrate from IBM WebSphere RTI 7.5, 7.5.1, and to IBM InfoSphere Information Services Director, Version 8.5 and subsequent releases. DataStage Version 6 is the earliest release that is supported for migration to Version 8.5. Note: This export and import migration method for release and earlier versions of DataStage, QualityStage, and WebSphere RTI does not use the ismigration tool. The DataStage Version Control component is not supported by InfoSphere Information Server, Version 8.5. Instead, use Information Server Manager to integrate a supported source control system. Copyright IBM Corp. 2006,

14 8 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

15 Chapter 3. Migration from DataStage and earlier versions Exporting projects Migration involves exporting DataStage projects and saving the settings files from the existing installation, and then importing the projects and moving the settings files to the Version 8.5 installation. This migrate method applies to the development environment where the design-time information resides and moves all of your migrated projects to IBM InfoSphere Information Server, Version 8.5. Complete the following activities to migrate your source DataStage and earlier environment to your target Version 8.5 development environment: 1. Export projects. See Exporting projects. 2. Save the DataStage settings files. See Saving DataStage settings files on page Installing InfoSphere Information Server, Version 8.5, including IBM InfoSphere DataStage. See "Installing IBM InfoSphere Information Server software" in the IBM InfoSphere Information Server Planning, Installation, and Configuration Guide. 4. Integrating the contents of your saved settings and configuration files. a. Restore the settings files. See Restoring contents of DataStage or earlier settings files on page 15. b. Move job dependency objects such as flat files, libraries, schema files, and hashed files that your project uses. See Move job dependency objects on page Import projects. See Importing DataStage projects on page Recompile jobs in your projects. See Recompiling jobs on page 17. Note: Use the migration from DataStage and earlier method to migrate to different computers for your Version 8.5 installation, or to the same computers by using an ITAG installation. This migration method information applies to migration to different target computers or the same computers for source and target installations. ITAG installations exist when you install more than one instance of DataStage or InfoSphere Information Server on the same set of Linux or UNIX computers. You export your DataStage projects from your source installation before migrating the projects to your Version 8.5 target installation. Before you begin Ensure that nobody is using DataStage and that all clients are disconnected. You can export projects by using one of the following methods: v Export from the DataStage Manager client. v Export from the command line of a DataStage client computer. Copyright IBM Corp. 2006,

16 Exporting projects from the DataStage Manager client You can use the DataStage Manager client to export projects from your development environment. Note: The current version of your installation determines the name of the DataStage Manager client. Your installation might refer to the client as the DataStage client. Procedure 1. Open the DataStage Manager client, and attach to project that you want to export. 2. Ensure View Host View is selected. 3. Select Export DataStage Components. 4. In the Export window, specify details about the project that you want to export: a. In the Export to file field, type or browse for the path name of the file in which to store the project. By default, export files have the suffix.dsx. b. In the Components tab, select the Whole Project option. 5. Click OK. The project is exported to the file that you specified. 6. In the left pane of the DataStage Manager window, select the next project and repeat the export process from step 3, specifying a different name for the export file. Exporting projects from the command line You can use the command line on the client computer to export your projects from your development environment. You can create a script that runs these commands and exports all of your projects in a single operation. Export your projects from your source installation before you import the projects to your target installation. Procedure 1. Open a command line editor and go to the DataStage client directory (the default path is C:\Ascential\Program Files\Ascential\DataStageversion). 2. Enter the command: dscmdexport /H=hostname /U=username /P=password project_name export_file_path [/V] The arguments are as follows: v hostname is the name of the DataStage server computer where the project is located. v username is your user name on the server computer. v password is the password for that user name. v project_name is the name of the project that you are exporting. v export_file_path is the path name of the destination file. By convention, export files have the suffix.dsx. v /V is optional. Including /V turns the verbose option on so that you can follow the progress of the export procedure. 10 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

17 Example For example, the following command exports the project named monthlyaudit that is located on the DataStage server named R101 and writes the project to a file named monthlyaudit.dsx. The target file is located in a directory named migrated_projects on the client computer. dscmdexport /H=R101 /U=BillG /P=paddock monthlyaudit C:\migrated_projects\monthlyaudit.dsx What to do next You can enter a command for each project that you want to export, or you can create a script that contains commands for all of the projects on your DataStage server computer. Saving DataStage settings files Back up your settings files on your existing DataStage server. After you install IBM InfoSphere Information Server, Version 8.5, you can compare each of your saved settings files with the equivalent new file. You can then integrate the two files. You must not replace the new files with the files that you saved from your existing installation, because you will overwrite new settings. The files that you copy depend on whether your DataStage server is on a Windows computer, or a UNIX or Linux computer. Saving settings files (UNIX and Linux) If you are migrating an existing DataStage server on a UNIX or Linux computer, you must save copies of certain settings files. Before you begin The environment variable $DSHOME identifies the engine directory of your DataStage installation. By default the engine directory is /user_home/ascential/datastage/dsengine, where user_home is the home directory of the DataStage administrator who originally installed DataStage (by default, dsadm). Each project is in its own directory in the /user_home/ascential/datastage/projects directory. Procedure 1. Copy the $DSHOME/dsenv file to a location outside of the DataStage file structure. 2. To keep a record of the existing configuration and the configuration of your ODBC drivers, copy the following files to a location outside of the DataStage file structure: v $DSHOME/.odbc.ini v $DSHOME/uvodbc.config v The uvodbc.config file located in each project directory Chapter 3. Migration from DataStage and earlier versions 11

18 3. Copy the DSParams file from each project directory to a location outside of the DataStage file structure. 4. Also, copy the DSParams file from the Template project. $DSHOME/../Template/ DSParams Saving the DSParams file (Windows) If you are migrating an existing DataStage server on a Windows computer, save a copy of the DSParams file from each project directory. Before you begin Each project has its own directory located, by default, in the directory C:\Ascential\DataStage\Projects. Save the DSParams file so that you can move it to your target installation. Procedure 1. Copy the DSParams file from each project directory to a safe location. 2. Also, copy the DSParams file from the Template project. For example, save the C:\Ascential\DataStage\Template\DSParams file. 3. Copy the $DSHOME/uvodbc.config in the engine directory. 4. The uvodbc.config file located in each project directory. Move job dependency objects The jobs in your projects might depend on objects outside of DataStage. You must move these objects to the Version 8.5 target installation. You need to move job dependency objects in the following situations: v If the files are in the DataStage server or client directory structures, or v If you are installing InfoSphere DataStage on a different computer. Note: If you have flat files, hashed files, or other dependencies that are located in your DataStage directory structure, or if you are migrating to a different computer, then you must move these files yourself. These files are not saved as part of the export procedure. The DataStage export procedure exports DataStage objects, such as job designs, table definitions and custom routines. If the jobs in your projects have other dependencies, then you might need to move these dependencies. Dependencies include flat files, files containing schemas used by parallel jobs, and libraries that are called by parallel job custom routines. It does not include parallel job data sets or file sets. If you are using data sets or file sets to permanently store data, then you must design a job to write the data to a flat file or other data target. You can move flat files, libraries, and schema files by using normal operating system commands. You might need to modify job designs to identify the new locations of these files. If there are server jobs in your projects that use hashed files, then you must use a dedicated procedure to move the hashed files. 12 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

19 Migrating hashed files If your DataStage project contains server jobs that use hashed files, then you need to move the hashed files to a new location as part of the migration procedure. Before you begin Before moving the files, stop the DataStage server to ensure that dynamic hashed files are copied correctly. If you previously added indices to the hashed files, remove the indices. The hashed files from your source installation need to be saved and moved to the target installation. Procedure 1. Locate the hashed files in your directory structure: v Each static hashed file is represented by two operating system files. For example, a static hashed file named price_lookup is contained in the two files named price_lookup and d_price_lookup. v Each dynamic hashed file is represented by a directory with the same name as the hashed file and a file named D_hashed_file_name. For example, a dynamic hashed file named code_lookup is represented by the directory named code_lookup and the file named D_code_lookup. 2. Copy the files or directories that represent each of your hashed files to a safe location outside of the DataStage directory structure. What to do next You can restore these files after you install and configure InfoSphere DataStage. Remove previous versions of DataStage Removing DataStage completely removes your current version of DataStage from server and client computers. Ensure that your DataStage server computer is backed up before you remove DataStage, and that no one is using DataStage. There are separate procedures for removing DataStage clients and removing DataStage servers. Removing a DataStage server (Windows) You use Windows Add or Remove Programs to remove an existing DataStage server from a Windows computer. Before you begin Ensure that DataStage is not running and ensure that no clients are connected to the server. Removes the DataStage server. Chapter 3. Migration from DataStage and earlier versions 13

20 Procedure 1. Open the control panel. 2. In the control panel, select Add or Remove Programs. 3. In the list of installed programs, select DataStage server. 4. Click Change/Remove. Removing a DataStage server (Linux, UNIX) You run the uninstallation program to remove an existing DataStage server from a UNIX or Linux computer. Before you begin Mount the original installation CD, or copy the CD contents to your computer. Removes the DataStage server. Procedure 1. Log in as the root user. 2. Change directory to the top level directory of the CD, or the directory to which you copied the CD contents. 3. Type the relevant uninstallation command: Operating System Solaris AIX HP-UX LINUX Command uninstll.sh uninstll.sh UNINSTLL.SH;1 uninstll.sh The uninstallation program guides you through the procedure for removing the DataStage server. Removing DataStage clients You use Windows Add or Remove Programs to remove existing DataStage clients from a Windows computer. Before you begin Ensure that nobody is using DataStage and that no clients are connected to the DataStage server. Removes DataStage clients. Procedure 1. Open the Windows control panel. 2. In the control panel, select Add or Remove Programs. 3. In the list of installed programs, select DataStage Clients. 4. Click Change/Remove. 14 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

21 Importing DataStage projects Import the projects to your Version 8.5 installation. Import projects from earlier versions of DataStage to your Version 8.5 development environment. Procedure 1. Move the.dsx file or files that you created to the computer where the IBM InfoSphere DataStage and QualityStage, Version 8.5 clients are installed. 2. Open the Administrator client and create a project or projects to contain the objects from your exported projects: a. On the Projects page, click Add. b. In the Add Project window, type the name of the project that you want to create and specify a path name for it. You can use the names of the original projects if required. c. Click OK to create the project. d. Repeat these steps for each project that you want to create. You might want to create a project for each of the projects that you exported and give it the same name as the original project. 3. Open the Designer client and attach to the target project. 4. Select Import DataStage Components. 5. Specify the name of the.dsx file that you want to import, and click OK. 6. After you unit test the migrated components in your Version 8.5 development environment, you must export the DataStage components from your Version 8.5 environment and then import them to your Version 8.5 production environment. Restoring contents of DataStage or earlier settings files If you previously customized any of your DataStage 7.5 or earlier settings files, you might need to restore these customizations. Do not copy your saved versions over the new ones to restore the settings files. You must merge the contents of your saved files with the new files. You must only add or edit settings in the new files. Do not delete settings. Use this procedure with any of the settings files that you saved earlier. Procedure 1. Open the saved version of the settings file in a text editor. 2. Open the new version of the same file in a text editor. 3. Compare the contents of the saved file with the new file. 4. Add any required entries to the new file. 5. Save the new file and close the text editor. Restoring DataStage job dependencies You must restore any DataStage job dependencies that you saved. Chapter 3. Migration from DataStage and earlier versions 15

22 After you migrate to Version 8.5, restore job dependency files to your new installation. Procedure 1. For each file, find the location for the file in the new IBM InfoSphere Information Server directory structure. For example, if the file that you want to restore was in the project directory in your previous DataStage installation, find the project directory to which you imported the project contents. 2. Use operating system commands to copy the saved file to the required location. 3. Ensure that the jobs that reference these files can locate them. If the file is referred to directly, you must edit the path name in the job design. If the file is referred to by a job parameter, you might need to edit the default value of the parameter to reference the new location for the file. Restoring hashed files You need to restore the hashed files that you saved. To restore hashed files, use IBM InfoSphere DataStage to create empty hashed files for each of the files that you want to restore. You then replace the empty files with the saved files. To restore hashed files, follow one of the two procedures. Procedure 1. For jobs in your migrated project that create the hashed files, open the InfoSphere DataStage and QualityStage Director client, and attach to the migrated project that uses the hashed files. 2. Run or validate the job that creates the hashed files. 3. Close all InfoSphere DataStage clients and stop the DataStage services. 4. Locate the newly created files in your directory structure and copy the saved hashed files over the top of them. 5. Restart the DataStage services. What to do next Your hashed files are now available for use. Designing a job to create new hashed files To design a job to create the new hashed files. Procedure 1. Open the Designer client, and attach to the migrated project that uses the hashed files. 2. Create a new server job. 3. For each hashed file that you need to restore, add a Sequential File stage linked to a Hashed File stage. 16 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

23 Recompiling jobs 4. In the Sequential File stage, point to an empty text file and define one column in the Outputs page Columns tab. 5. In the Hashed File stage, specify the name of the hashed file that you are restoring, then select the Create File option and specify the file type of the hashed file that you are restoring. 6. When you have added stages for all the hashed files that you want to restore, compile and then validate or run the job to create the empty hashed files. 7. Close all InfoSphere DataStage clients and stop the DataStage services 8. Locate the newly-created files in your directory structure and copy your saved hash files over the top of them. 9. Restart the DataStage services. What to do next Your hashed files are now available for use. You must recompile the jobs and routines in the migrated projects to create new executable jobs. You can start the wizard from the Tools menu of the Designer client. Select Tools Multiple Job Compile. You can also select multiple items in the repository tree or Advanced Find window and use the shortcut menu to start the compiler wizard. Procedure 1. If you started the wizard from the Tools menu, specify the criteria for selecting jobs to compile. Choose one or more of: v Server v Parallel v Mainframe v Sequence v Custom server routines v Custom parallel stage types You can also specify that only currently uncompiled jobs will be compiled, and that you want to manually select the items to compile. 2. Click Next>. If you chose the Show manual selection page option, the Job Selection Override screen appears. Choose jobs in the left pane and add them to the right pane by using the Add buttons or remove them from the right pane by using the Remove buttons. Clicking Add while you have a folder selected selects all the items in that folder and moves them to the right pane. All the jobs in the right pane will be compiled. 3. Click Next>. If you are compiling parallel or mainframe jobs, the Compiler Options screen appears, allowing you to specify the following: v Force compile (for parallel jobs). v An upload profile for mainframe jobs you are generating code for. 4. Click Next>. The Compile Process screen appears, displaying the names of the selected items and their current compile status. Chapter 3. Migration from DataStage and earlier versions 17

24 5. Click Start Compile to start the compilation. As the compilation proceeds, the status changes from Queued to Compiling to Compiled OK or Failed and details about each job are displayed in the compilation output window as it compiles. Click the Cancel button to stop the compilation, although you can only cancel between compilations so the Designer client might take some time to respond. 6. Click Finish. If the Show compile report checkbox was selected, the job compilation report screen appears, displaying the report generated by the compilation. Updating jobs that use the QualityStage 7.5 plug-in If you have existing DataStage jobs that use the QualityStage plug-in stage to connect to QualityStage 7.5, and you want to continue running those jobs, then you must rewrite those jobs to use the parallel canvas and the Version 8.5 stages. You must rewrite the jobs that use the QualityStage 7.5 plug-ins. After you import the jobs to Version 8.5, rewrite the jobs to use the parallel canvas and the Version 8.5 stages. Switching between different versions of clients You can install different versions of DataStage clients on a single Windows computer and switch between them by using the Multi-client Manager. Before you begin The Multi-client Manager is installed on the Version 8.5 client tier. Note: The Multi-client Manager is not supported on DataStage releases earlier than 7.0. For DataStage releases earlier than 7.0, install each client version on a separate computer. When your organization is using different versions of DataStage, it is useful to have different client versions on your Windows computer. You can then switch between the clients according to which DataStage server you want to connect to. For example, if you are evaluating IBM InfoSphere DataStage, Version 8.5 on one of your installations, while still running WebSphere DataStage, Version on another installation, you can have the clients for both releases on a client tier computer, and switch between the clients as necessary. You can install multiple DataStage clients by running the client installer (versions earlier than WebSphere DataStage 8.0), or running the suite installer and selecting only the client tier (Version and later). You must install the Version 8.5 client after you install any earlier client versions, so that the Version 8.5 Multi-Client Manager is the latest version installed. Procedure 1. Start the Multi-client Manager by double-clicking the desktop shortcut. 18 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

25 2. In the Current installation field, check whether the currently selected version is the version that you want. v If the correct version is selected, you need take no further action. v If the correct version is not selected, select the correct client in the Known installations list and click Select. 3. Click Close to close the Multi-client Manager. Multiple server method (Linux and UNIX only) If your DataStage server is on a Linux or UNIX computer, you can keep that instance and install IBM InfoSphere Information Server, Version 8.5. You can also install multiple IBM InfoSphere DataStage engine tiers. Each engine tier must be registered to a different instance of the IBM InfoSphere Information Server services tier. Note: There is a change of terminology between DataStage 7 and InfoSphere DataStage, Version and later. In earlier versions the engine component was identified as the DataStage server, for release and later, the engine component is identified as the engine tier. If you maintain different releases of DataStage server, or multiple instances of the same server, you can keep all of those instances. You can also upgrade each of these servers to InfoSphere DataStage, Version 8.5 and keep their existing identity information. Each instance of a DataStage server is identified by a tag ID (an ITAG) and allocated a different port. You also specify a different home directory for each server. Each DataStage server has a different set of projects that you access through that server. You connect to different servers by specifying the port number in addition to the UNIX server ID. The existing DataStage server instance retains the default port number, 31538, and uses the default ITAG, ADE. If you already have multiple server instances, then you already have servers that use different ports and ITAGs. Each version of DataStage requires clients of the same version. You must use the Multi-Client Manager program to switch between different client versions on your Windows client computers. You can use the multi-server facility to install multiple instances of the InfoSphere DataStage, Version 8.5 engine tier on the same computer. When multiple instances of the engine tier are installed on the same computer, each engine tier requires a unique profile for IBM WebSphere Application Server. The following table shows a scenario of a multi-server installation, and illustrates the use of port numbers and ITAGs. Table 2. Scenario 1: InfoSphere DataStage, Version 8.5 server installed on the same computer as an existing DataStage server Engine tier instance Server details WebSphere DataStage, release server v Itag ADE v Port v /disk1/ascential/datastage Chapter 3. Migration from DataStage and earlier versions 19

26 Table 2. Scenario 1: InfoSphere DataStage, Version 8.5 server installed on the same computer as an existing DataStage server (continued) Engine tier instance Server details InfoSphere DataStage, Version 8.5 server v Itag 123 v Port v /opt/ibm/informationserver/server The following table shows a scenario of a multi-server installation with three servers, and illustrates the use of port numbers and ITAGs. Table 3. Scenario 2: InfoSphere DataStage, Version 8.5 server installed on the same computer as two existing DataStage servers Engine tier instance Server details WebSphere DataStage, release 7.2 server v Itag ADE v Port v /disk1/ascential/datastage WebSphere DataStage, release server v Itag A23 v Port v /disk2/ascential/datastage InfoSphere DataStage, Version 8.5 server v Itag 123 v Port v /opt/ibm/informationserver/server The following table shows a scenario of with three Version 8.5 servers, and illustrates the use of port numbers and ITAGs for Version 8.5 installations. Table 4. Scenario 3: Three instances of InfoSphere DataStage, Version 8.5 server installed on the same computer Engine tier instance Server details InfoSphere DataStage, Version 8.5 server v Itag ADE v Port v /opt/ibm/informationserver/server InfoSphere DataStage, Version 8.5 server v Itag BED v Port v /opt2/ibm/informationserver/server InfoSphere DataStage, Version 8.5 server v Itag 123 v Port v /opt3/ibm/informationserver/server Installing Version 8.5 in addition to existing DataStage servers You can maintain existing DataStage server instances while installing IBM InfoSphere Information Server, Version Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

27 The Version 8.5 installation wizard detects existing DataStage servers during installation. You must provide a unique ITAG value and port number to use for the Version 8.5 server. Installing IBM InfoSphere DataStage, Version 8.5 clients in addition to existing clients When you maintain multiple versions of the InfoSphere DataStage server on Linux or UNIX computers, you must maintain corresponding client versions on Windows computers. Before you begin You need the IBM InfoSphere Information Server, Version 8.5 client installation software and the IBM InfoSphere Information Server Planning, Installation, and Configuration Guide, which is in the top-level directory of the installation media. You can install clients for InfoSphere DataStage, Version 8.5 on the same Windows computer as your existing DataStage clients, and use the Multi-client Manager to switch between the different versions. You can also install InfoSphere DataStage, Version 8.5 clients on a separate Windows computer. If you are installing clients on a computer with existing clients, the client installation program detects their presence and installs the Multi-Client Manager program. Procedure 1. Log on to the Windows computer as an administrator. 2. Turn off any firewall software that is installed on the computer. 3. Optional: Turn off your antivirus software. 4. Go to the root directory on the InfoSphere Information Server, Version 8.5 installation media or downloaded installation image. 5. Double-click setup.exe. The installation program starts and guides you through the installation procedure. 6. When asked for an installation directory, select the New installation option and either use the default directory, or specify a new directory. 7. When asked to select the product modules and components, select InfoSphere DataStage and QualityStage. Select other components as required by your installation plan. Starting and stopping multiple DataStage servers When multiple DataStage servers are on a single computer, you must identify the server that you want to start or stop. You identify the DataStage server that you want to start or stop by setting the $DSHOME environment variable to reference the DSEngine subdirectory of the server. For example, there are two servers on the same computer with the following DSEngine subdirectories: v /disk1/ascential/datastage/dsengine (existing server) Chapter 3. Migration from DataStage and earlier versions 21

28 v /opt/ibm/informationserver/server/dsengine (IBM InfoSphere DataStage, Version 8.5 server) Procedure 1. Set the $DSHOME environment variable to point to the /opt/ibm/ InformationServer/Server/DSEngine directory. 2. Stop the server by using the following command: $DSHOME/bin/uv -admin -stop 3. Wait thirty seconds to give the server time to stop. 4. Start the server by using the following command: $DSHOME/bin/uv -admin -start Connecting to multiple DataStage servers To connect to a DataStage server from a client when you have multiple servers, you must specify the server port number in addition to the name of the computer where the server is located. You use a different procedure depending on the version of DataStage server and the client, and whether you are connecting from the command line. The clients for DataStage release 7 attach directly to the engine; the clients for InfoSphere DataStage, Version and later attach to the engine by way of the services tier, and so the default port numbers are different for each type of client. Use the Multi-Client Manager to switch between different versions of the clients. The client version must match the server version. Connecting to DataStage version or earlier Use this procedure to connect to a DataStage version or earlier server from any client other than the Administrator client. Before you begin If multiple versions of the DataStage clients are on your computer, ensure that the same version as the server version is currently selected in the Multi-Client Manager. Connects clients to DataStage servers. Procedure 1. Select the Manager, Designer, or Director client from the Start menu. 2. In the Host System field of the Attach to Project window, type the identity of the server computer in the form hostname:portnumber where portnumber is the port number that the server uses. For example, type R101:31538 in the Host System field. 3. Type your user name and password. 4. Specify the name of the project that you want to attach to. 22 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

29 Connecting to DataStage version or earlier from the Administrator client Use this procedure to connect to a DataStage version or earlier server from the Administrator client. Before you begin If multiple versions of the DataStage clients are on your computer, ensure that the same version as the server version is currently selected in the Multi-Client Manager. Connect Administrator clients to a DataStage version or earlier server. Procedure 1. Select the Administrator client from the Start menu. 2. In the Host System field of the Attach to DataStage window, type the identity of the server computer in the form hostname:portnumber where portnumber is the port number that the server uses. For example, type R101:31538 in the Host System field. 3. Type your user name and password. Connecting to IBM InfoSphere Information Server, Version 8.5 Use this procedure to connect to an IBM InfoSphere DataStage and QualityStage, Version 8.5 server from any client other than the Administrator client. Before you begin If multiple versions of the DataStage clients are on your computer, ensure that the same client version as the server version is currently selected in the Multi-Client Manager. Connects clients to Version 8.5 server. Procedure 1. Select the Designer client or Director client from the Start menu. 2. In the Domain field of the Attach to Project window, type the name of the domain to which your InfoSphere DataStage server belongs in the form DomainServer:9080. For example, type R101: Type your user name and password. 4. In the Project field, specify the identity of the project that you want to attach to in the form hostname:portnumber/project where portnumber is the port number that the server uses. For example, type R101:31348/datastage. Connecting to IBM InfoSphere DataStage and QualityStage, Version 8.5 from an Administrator client Use this procedure to connect to a Version 8.5 server from the Administrator client. Chapter 3. Migration from DataStage and earlier versions 23

30 Before you begin If multiple versions of the InfoSphere DataStage clients are installed on your computer, ensure that the same version as the server version is currently selected in the Multi-Client Manager. Connects Administrator clients to a Version 8.5 server. Procedure 1. Select the Administrator client from the Start menu. 2. In the Domain field of the Attach to DataStage window, type the name of the domain to which your InfoSphere DataStage server belongs in the form DomainServer:9080. For example, type R101:9080 in the Domain field or type R201:80 if you are using a front-end Web server. 3. Type your user name and password. 4. In the DataStage Server field, specify the identity of the computer where the server that you want to attach to is located in the form hostname:portnumber where portnumber is the port number that the server uses. For example, type R201:9080 or type R301:80 if you are using a front-end Web server. Connecting to a Version 8.5 DataStage server from the command line You can use the command line interface to control DataStage jobs in different projects. These instructions assume that you are logged in to the operating system as the user that runs the job. Procedure v To connect to a project from the command line, you specify the server name and port number of the required instance with the -server argument in the form -server server:portnumber for local computers. v For remote computers that run InfoSphere DataStage, Version 8.5 server instances, you must specify the domain and the server name in the form -domain domain:domain_portnumber -server server:portnumber. The default domain port number is For example, to run a job on the local computer on the server that uses port 31359, run this command: dsjob -server r101: run myproj myjob v To run a job on the local computer on the default server, run this command: dsjob -run myotherproj myotherjob v To run a job on a remote computer called R101 on the Version 8.5 server that uses port 31360, you must also specify the host computer, the domain, and supply the login information. For example, enter the following command: dsjob -domain mydomain:9080 -server r101: user billg -password paddock -run myproj myjob 24 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

31 Chapter 4. Migration from QualityStage 7.5 and earlier releases Required premigration tasks if your Version 7.5 or earlier source installation includes QualityStage. If QualityStage 7 is installed, you need to migrate your jobs to Version 8.5. (The term 'QualityStage 7' refers to all releases between 7.0 and 7.5.) If you were using the QualityStage plug-in stage in DataStage jobs, the jobs will need to be edited after they are migrated to the Version 8.5 installation. To run these jobs after migration, you must configure the jobs to use the available stages in Version 8.5. The QualityStage plug-in is not available or supported in Version 8.5. QualityStage 7 provides a method to migrate QualityStage 7 jobs, match specifications, and standardization rule sets to the InfoSphere DataStage and QualityStage Designer client in the Version 8.5 environment. In legacy mode your migrated job will use the QualityStage Legacy stage. In expanded form, your migrated job will make full use of all the specialized data quality stage types as well as the QualityStage Legacy stage. If you are migrating to a platform that was supported by QualityStage 7, then you can migrate by using legacy mode or expanded form. If the platform was not supported for QualityStage 7, then only expanded mode migration is available, and any QualityStage Legacy stage types in the migrated job must be replaced. The migration utility uses information in the QualityStage 7 server project directory to build the.dsx file format that InfoSphere DataStage and QualityStage requires to import jobs. The migration utility migrates the following QualityStage 7 objects: v Standardization rule set v Jobs in full legacy operational mode v Jobs in expanded form, in which some legacy operations are replaced by InfoSphere DataStage and QualityStage, Version 8.5 stages v Match specification You export projects to create a.dsx file that contains migrated jobs, rule sets, and match specifications in the Temp directory in the QualityStage 7 project directory. Job migration in legacy operational mode When you migrate QualityStage 7 jobs in full legacy operational mode, the original job is replaced with a single instance of a QualityStage Legacy stage and Sequential File stages linked as source and target stages. If you migrate a QualityStage 7 job in legacy operational mode, you can make only minor changes to the resulting QualityStage Legacy stage. Use this option only for stable jobs that will not be modified or jobs that are due to be replaced. Copyright IBM Corp. 2006,

32 Note that, in a Japanese environment, the migrated job uses Data Set stages instead of Sequential File stages. In this case, you must create an additional job that reads the source data from the sequential file and writes it to a data set. The data set can then be read by the migrated job. If your original job wrote results to a sequential file, then you must create another job to write the results from the data set produced by the migrated job to a sequential file. Do not use the legacy operational mode option if you are migrating a job that contains the following QualityStage 7 stages because their functionality is not supported by the QualityStage Legacy stage: v Postal stages such as CASS and SERP v Program stage v Multinational Standardize stage v WAVES stage v Format Convert stage QualityStage job migration in expanded form Rule set migration When you migrate a QualityStage 7 job in expanded form, the QualityStage migration utility replaces the original job with one or more parallel job stages for each stage in the QualityStage 7 job, and with Sequential File stages that are linked together to represent the QualityStage 7 job flow. A job migrated in expanded form might have a mixture of data quality, processing, and Legacy stages when you open the job in the Designer client. For complex jobs, you can move the stages around on the canvas to make the job more intelligible. You can also replace a QualityStage Legacy stage with a data quality stage that has equivalent functions. The migration of a QualityStage 7 standardization rule set option migrates the rule sets explicitly by name. When a QualityStage 7 job is migrated, the migration utility detects the dependent rule sets and displays them. You can then choose to include the rule sets in the.dsx file with the job. The migration utility renames the rule sets within the.dsx file to prevent a naming duplication with a built-in IBM InfoSphere QualityStage, Version 8.5 rule set. The utility uses the following naming convention: QS-7-Ruleset-Name_QS-7-Project-Name Match specification migration When you migrate a QualityStage job that contains match and unduplicate stages, the Match specifications are migrated with the job. The QualityStage migration utility includes the match processing information in the.dsx file with the job, if you selected the option "plus dependencies" to migrate the job. Once the job is imported, you can locate the match specification in the IBM InfoSphere DataStage and QualityStage Repository Match Specifications folder. 26 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

33 As with rule sets, match specifications are renamed when the information is imported. The match specification name has the following form: QS-7-RefMatch-or-UndupMatch-Stage-Name_QS-7-Project-Name Installing the WebSphere QualityStage migration utility Use the WebSphere QualityStage migration utility to migrate QualityStage Version 7 to IBM InfoSphere QualityStage, Version 8.5. (The term 'QualityStage 7' refers to all releases between 7.0 and 7.5.) Installs the QualityStage migration utility on your source installation. Procedure 1. Choose one of the following options, depending on operating system type and whether you want to install the IBM InfoSphere DataStage and QualityStage server on the same computer as the QualityStage 7 server. Option Installing the InfoSphere DataStage and QualityStage server on the same computer as the QualityStage 7 server Installing the InfoSphere DataStage and QualityStage server on a different computer from the QualityStage 7 server (Windows or UNIX or Linux) Description Install IBM Information Server, installing the engine tier on the computer where the QualityStage 7 server is installed. The migration utility is installed with the engine tier. Install IBM Information Server on the target computer. The migration utility is installed with the engine tier. Before you run the migration utility on the target computer, make the QualityStage 7 project metadata available to the target computer. Make the metadata available by copying the entire QualityStage 7 project directory and all its contents to the target computer, or by making the directory available via the network (for example, by mapping a drive on Windows). 2. If you are migrating from a Unicode-enabled version of QualityStage Version 7, make the following changes to the qsmig.env file (located in the directory where the migration tool is installed). Make the changes before you use the migration utility. v Change the line, FLDEXTPR=0 to FLDEXTPR=1 v For the Japanese language, add the line, QSLCHARSET="CP932" v For the Chinese language, add the line QSLCHARSET="CP936" 3. On Windows, if the QualityStage Version 7 project directories are on a different drive from the migration utility, add the following line to the qsmig.env file: v APPCLIB=${PROJ}/Controls What to do next After you install the QualityStage migration utility, you can migrate QualityStage Version 7 jobs to InfoSphere DataStage and QualityStage, Version 8.5. Chapter 4. Migration from QualityStage 7.5 and earlier releases 27