MIMIX Director. Version 8.1 MIMIX Director Installation and Migration Guide

Transcription

1 MIMIX Director Version 8.1 MIMIX Director Installation and Migration Guide

2 September, 2011 MIMIX Director Installation and Migration Guide Version 8.1 Copyright Vision Solutions, Inc All rights reserved. The information in this document is subject to change without notice and is furnished under a license agreement. This document is proprietary to Vision Solutions, Inc., and may be used only as authorized in our license agreement. No portion of this manual may be copied or otherwise reproduced without the express written consent of Vision Solutions, Inc. Vision Solutions provides no expressed or implied warranty with this manual. The following are trademarks or registered trademarks of their respective organizations or companies: MIMIX and Vision Solutions are registered trademarks and Integrator, MIMIX Director, Data Manager, Vision Suite, ECS/400, OMS/ODS, SAM/400, MIMIX RecoverNow, GeoCluster, and itera Availability are trademarks of Vision Solutions, Inc. Double-Take Share, Double-Take Availability, and Double-Take RecoverNow DoubleTake Inc. DB2, IBM, i5/os, iseries, System i, System i5, AIX5L, Informix, System p, System x, and System z, and WebSphere International Business Machines Corporation. Adobe and Acrobat Reader Adobe Systems, Inc. HP-UX Hewlett-Packard Company. Teradata Teradata Corporation. Intel Intel Corporation. Java, all Java-based trademarks, and Solaris Sun Microsystems, Inc. Linux Linus Torvalds. Microsoft and Windows Microsoft Corporation. Mozilla and Firefox Mozilla Foundation. Netscape Netscape Communications Corporation. Oracle Oracle Corporation. Red Hat Red Hat, Inc. Sybase Sybase, Inc. Symantec and NetBackup Symantec Corporation. UNIX and UNIXWare the Open Group. All other brands and product names are trademarks or registered trademarks of their respective owners. If you need assistance, please contact Vision Solutions CustomerCare team at: CustomerCare Vision Solutions, Inc. Telephone: or support@visionsolutions.com Web Site:

3 Contents Chapter 1 Introduction About MIMIX Director How to Proceed Chapter 2 Requirements Requirement Checklists OS Requirements MIMIX Director Requirements Web Browser Requirements PC Requirements for the Installation Wizard Chapter 3 Installation About Installing MIMIX Director Migrate to MIMIX Director v Director Setups Starting the Installation Installing Using the MIMIX Director Installation Wizard Installing Using the 5250 Emulator Obtaining and Applying License Keys Verifying Your License Key What to Do Next Chapter 4 Migration to MIMIX Director v About Migrating to MIMIX Director v User Defined Enquiries (UDEs) Web Interface Configuration Before Migrating Backing Up Director Ending Director v8.0 and v Verifying No Locks Starting the Migration MIMIX Director Installation and Migration Guide v8.1 3

4 Contents Chapter 5 Access MIMIX Director Starting MIMIX Director Chapter 6 Access MIMIX Director Portal Application About the MIMIX Director Portal Application Make the MIMIX Director Portal Application Available to Vision Solutions Portal Chapter 7 Uninstall MIMIX Director MIMIX Director Installation and Migration Guide v8.1

5 Introduction 1 About MIMIX Director How to Proceed MIMIX Director is a powerful solution for i5/os environments that can optimize systems, including those running high availability solutions, and provides unprecedented systems management. Director includes a highly integrated set of applications to automate and pro-actively monitor, manage, and optimize IBM i servers, databases, and application environments. In addition, the Director portal application for Vision Solutions Portal is automatically installed as part of the Director v8.1 product installation process. Vision Solutions Portal is a new, browser-based, graphical interface that presents Vision Solutions product portal applications for management and monitoring in a single, unified view. The Director portal application is configured as an instance in the Vision Solutions Portal. The Director portal application is an interface that is quick to configure and easy to customize. The Director portal application provides a comprehensive view of the health of your system and provides information useful for system tuning and optimization. Through the Director portal application, you can define monitors for events that are critical to the operation and management of your systems and for which you want to provide status or alerts. This guide provides procedures to complete an install of Director v8.1. Read and understand the requirements and the installation procedures before beginning. If you currently have a version of Director installed and will migrate it to Director v8.1, read and understand the migration procedure. See Chapter 2, Requirements for requirements for migrating earlier version of Director to Director v8.1. MIMIX Director Installation and Migration Guide v8.1 5

6 Chapter 1: Introduction After the installation and migration (if required) is completed, this guide provides information and procedures for: Learning how to navigate in Director. Configuring and accessing the Director portal application. Proceed now to Chapter 2, Requirements on page 7. 6 MIMIX Director Installation and Migration Guide v8.1

7 Requirements 2 Requirement Checklists Before installing Director, read and understand the requirements described in the following sections. Ensure compliance before proceeding to the installation section. OS Requirements i5/os of V5R4MO or higher (compatible with V7R1) It is strongly recommended to apply any IBM PTFs (or their supersedes) associated with IBM i releases as they pertain to your environment. Refer to the Technical Documents page on Vision Solutions Support Central for a list of required and recommended IBM PTFs. Apply MIMIX Director PTFs Permanently Before you upgrade the operating system on your IBM i, you must apply all Director PTFs permanently. Failure to do so may result in losing some or all of the those PTFs. Note the following: Once a PTF has been permanently applied, it cannot be removed. Do not permanently or temporarily apply Director PTFs via an IPL. Permanently or temporarily applying Director PTFs during an IPL could result in the IPL hanging because the Director libraries may not be in the library list. Temporarily applied PTFs use additional disk space, so once you have verified the functionality you should permanently apply the PTFs. Do the following to permanently apply PTFs: 1. Have all Director users sign off 2. End the Director subsystems: ITID81/ENDID *ALL MIMIX Director Installation and Migration Guide v8.1 7

8 Chapter 2: Requirements 3. Sign back on to the system. 4. Enter the following command: APYPTF LICPGM(7PA2K40) RLS(V8R1M0) APY(*PERM) DELAYED(*NO) 5. After the upgrade, do the following to remove the save files for the permanently applied PTFs using the following parameters (the Vision product ID and product release parameters are automatically populated): a. Prompt (F4) the command ITID81/IDINSTPTF. The Install Vision PTFs screen is displayed. b. Enter the following: Location of PTF files as *Vision. Get PTF list *NO Display PTFs not on system *NO Get PTF Save Files *NO Load and apply PTFs *NO Remove save files for perm apy *YES Execute DSPPTF *YES or *NO, per your choice Ensure that the user profile you will use to install or migrate Director has one of the following permissions: Security Officer (*QSECOFR) A user profile that is defined, at a minimum, with the authorities of *ALLOBJ, *SECADM, *SPLCTL, *JOBCTL, IOSYSCFG, *AUDIT, *SAVSYS, and *SERVICE. NOTE If you do not have the minimum authorities specified above, Director displays a message after the installation or migration process starts informing you that your authority is not adequate to proceed. Ensure that the Limit Capabilities field of the user profile for install or migration is set to *NO. This field limits the ability of the user to enter commands and to override the initial program, initial menu, current library, and attention-key-handling program specified in the user profile. Ensure that the System Value QALWOBJRST is set to *ALL. This value allows the restore of security-sensitive objects. 8 MIMIX Director Installation and Migration Guide v8.1

9 MIMIX Director Requirements Set the system value QFRCCVNRST to 1. This value allow all objects to be restored during the install. The following IBM licensed programs must also be installed: On V5R4-5722SS1 Option 30 (Qshell) and 33 (Portable App Solutions Environment), 5722JV1 Option 8 (J2SE bit) On V6R1-5761SS1 Option 30 (Qshell) and 33 (Portable App Solutions Environment), 5761JV1 Option 8 (J2SE bit) On V7R1-5770SS1 Option 30 (Qshell) and 33 (Portable App Solutions Environment), 5761JV1 Option 8 (J2SE bit) On V5R4, ensure that you have the following IBM software fix installed: SF Java level 15. In addition, apply these PTFs: SI35731 SI35742 MIMIX Director Requirements The following are requirements that must be met in order to install and use Director: Director must be installed to System ASP1. Director v8.0 is the minimum release version that can be migrated to Director v8.1. Director v8.1 installs as a separate instance from any earlier installs of Director in your environment, allowing the instances to be run side-by-side. However, Director v8.0 is the minimum release version from which you can migrate existing data and configuration via the migrate tool to Director v8.1. Ensure that the Director user profile ITIDGUI is not blocked from running SQL commands (Select, Insert, Update, Delete) through JDBC. This can occur when running third party security products that use Exit Point controls. If you are running other products that use the same journals on the same system as Director, such as MIMIX, there may be considerations for journal receiver management. For details, see "Interaction with other products that manage receivers" in the MIMIX Administrator Reference book. MIMIX Director Installation and Migration Guide v8.1 9

10 Chapter 2: Requirements If Director is installed in the same partition as MIMIX V7, Director libraries must be excluded from replication by MIMIX, including the following: ITID81 IDSPLARC81 IDOBJARC81 In addition, you should also not replicate the Director authorization list IDAUTLST81. See the MIMIX Administrator Reference book for information on excluding libraries from replication. Web Browser Requirements Access the Director portal application for Vision Solutions Portal using the following browsers: Internet Explorer 7 or 8 and above Firefox 3.5 and above NOTE See the Getting Started with Vision Solutions Portal manual for additional installation requirements. PC Requirements for the Installation Wizard Before launching the wizard, ensure that your PC meets the following minimum requirements: 128 MB free RAM OS: Windows 2000, Windows XP, Windows Vista, Windows V7 8-bit color depth (256 colors) Monitor resolution of 1024 x 768 Adobe Acrobat Reader to view the Readme PDF Network access to IBM i where Director will be installed Internet access for uploading and retrieving license keys (either automatically using the Director install wizard or though 5250 emulator commands) 10 MIMIX Director Installation and Migration Guide v8.1

11 Installation 3 About Installing MIMIX Director The MIMIX Director installation wizard provides a simple method to complete a guided product installation and is the recommended method for installation. When the default of Director v8.1 is selected in the wizard for installation, the applications automatically installed are: Director Director portal application Vision Solutions Portal The Vision Solutions Portal and the Director portal application can be selected in the Director installation wizard to install independently of Director. If you are not able to use the Director installation wizard in your environment, you can use the 5250 emulator installer (see Installing Using the 5250 Emulator on page 13). With the 5250 emulator installer (LODRUN): Both Director and the Director portal application are installed. The portal application must be installed separately using an installation wizard (either Director installation wizard or Vision Solutions Portal installation wizard). See the Getting Started with Vision Solutions Portal manual for installation and use instructions. It is a manual procedure to make the Director portal application available to Vision Solutions Portal. See Chapter 6 Access MIMIX Director Portal Application on page 28. It is a manual procedure to obtain and apply license keys using the auto-validate process (see Obtaining and Applying License Keys on page 14). When using the Director installation wizard, the actions above that must be manually executed are automatically accomplished for you. MIMIX Director Installation and Migration Guide v8.1 11

12 Chapter 3: Installation Migrate to MIMIX Director v8.1 Director v8.1 installs as a separate product instance from any earlier installs of Director in your environment, allowing the instances to run side-by-side. If you choose to migrate data and configuration from an earlier install of Director to Director v8.1, go to Chapter 4, Migration to MIMIX Director v8.1 and follow the instructions. Director v8.0 is the minimum release version from which you can migrate existing data and configuration via the migrate tool to Director v8.1. Director Setups During the installation and general use of the product, Director completes the following setups that allow it to efficiently and effectively complete its system management functions. These setups are done automatically by the product and require no actions from you. Changes system values to allow QAUDJRN to be implemented (where not already implemented). This enables the dynamic cross-reference function of Director to work correctly. Sets the Object Auditing Value to *CHANGE (unless already set to *ALL) for all existing or new objects on the system (apart from files and excluded objects). This enables the dynamic cross-reference to function correctly. (See the MIMIX Director User Guide for information on the cross-reference capability.) If enabled, creates and maintains (via autonomics) the ITIDOWNER user profile so that Director can function correctly. (See the MIMIX Director User Guide to enable autonomics.) Creates Logical Files over the System Database Files to allow the cross reference to efficiently maintain its own information on Files. Creates the ITIDIASP library on all available iasps. This library contains the Logical Files described above for the iasp. Creates an HTTP Web Instance (VSISVR) that is available on port (See Access MIMIX Director Portal Application on page 28 for information on changing port 8410 if it is in use on your system.) After the first cross-reference is complete or a successful migration has occurred, a Domain, Library, Object and Profile collection runs. Creates the ITIDGUI profile which is used by IDETSJVM, IDGENREP and the Health Report to access the Director database. Creates the IDOBJARC81 and IDSPLARC81 libraries and sets them to *PUBLIC *EXCLUDE. 12 MIMIX Director Installation and Migration Guide v8.1

13 Starting the Installation Verifies that all required special values exist in the installing profile as described in Chapter 2, Requirements. If they do not, the installation is stopped. Creates an Authorization list IDAUTLST81 to control access to Director and related product libraries. Starting the Installation IMPORTANT Director must be installed to System ASP1. You cannot install it on a User ASP or an iasp. Select either the Director installation wizard or the 5250 emulation installer. Installation using the Director installation wizard is recommended. Installing Using the MIMIX Director Installation Wizard The Director installation wizard provides a simple method for downloading, distributing, and installing products on single or multiple Power Systems simultaneously. The wizard install process can also obtain and apply license keys for the installation. By default, the installation wizard installs Director, the Director portal application, and Vision Solutions Portal. You can also optionally install only the Vision Solutions Portal and the Director portal application from the Director installation wizard. Installing Using the 5250 Emulator The 5250 installer installs Director and the Director portal application. NOTE When completing a new install, it is recommended that the home directory for the user profile running the Director installation be set to the root directory. 1. Do one of the following: Download the Director installation software from the Vision Solutions website to an IBM i. (Create a physical CD-ROM from the downloaded ISO image when applicable or mount the downloaded ISO image into the image catalog). Insert the Director v8.1 CD-ROM into a CD-ROM drive. MIMIX Director Installation and Migration Guide v8.1 13

14 Chapter 3: Installation 2. At an i5/os command prompt, enter the following command: LODRUN xxxxx For xxxxx, type the name of the CD-ROM drive (for example, OPT01) where you inserted the Director CD-ROM or the location of the installation file. The Click License Agreement screen is displayed. When the installation is complete, it returns to a command prompt. You must now add license keys (see Obtaining and Applying License Keys on page 14). Obtaining and Applying License Keys License keys can be automatically obtained and applied using the Director installation wizard. If you are unable to use the Director installation wizard, you can obtain and apply the license keys using Director menu options. When license keys have been applied, you can optionally verify that the license keys are correct (see Verifying Your License Key on page 19). NOTE Qualify the STRID command with the library ITID81 when it is entered outside of the Director product. Otherwise, it is not necessary to qualify the STRID command. 1. Enter the following on a command line to start Director: ITID81/STRID 14 MIMIX Director Installation and Migration Guide v8.1

15 Starting the Installation 2. Do one of the following: If this is the first time you have started Director after an installation, go to step 3. If you previously started Director and are only updating your license keys, go to step Enter the following command: IDWRKSEC The Work with Security screen displays with your user name in the list. You define which areas of Director are available to a user in the Work with Security screen. 4. Add an X to the CFG field, then press Enter. NOTE You can add additional security privileges at this time or at a later time when performing administrative tasks (see the MIMIX Director User Guide for more information). 5. Exit the screen. 6. On the Director Main Menu, enter option 6 (Configuration) to display the Director Configuration Menu. 7. On the Director Configuration Menu, enter option 3 (License Maintenance), then do one of the following: If you are not immediately applying the license key after obtaining it, enter option 5 (Build Auto Validate Up-Load File) to build the license file. If you are completing the licensing process at one time, enter option 4 (Update License Key via Auto Validate) to display the Update License Keys screen. MIMIX Director Installation and Migration Guide v8.1 15

16 Chapter 3: Installation NOTE The LRP file name may not be identical to the one shown below. 8. Transfer the following file to a PC capable of connecting to the internet. /VISIONSOLUTIONS/LICENSEKEYS/<LRP file name> 9. From the PC, connect and log in to the following page on the Vision Solutions website: Once logged in, the LRP Upload page is displayed. 10. Click Browse, then navigate to the location on the PC that contains the License Request Package (LRP). 16 MIMIX Director Installation and Migration Guide v8.1

17 Starting the Installation 11. Click Add. The selected LRP is displayed on the page. 12. Repeat the previous steps for each LRP. 13. Once all the LRPs have been uploaded, click Generate License Keys to generate the license key package (LKP). This may take several seconds. When complete, a message is displayed. z MIMIX Director Installation and Migration Guide v8.1 17

18 Chapter 3: Installation 14. Click Download LKP to save the LKP to your PC. 15. Click Save, then select the location and save. 16. Transfer the LKP from your PC to your IBM i system. It is recommended that you save the LKP to the following IFS directory on your IBM i system: /VISIONSOLUTIONS/LICENSEKEYS/ NOTE Note the full path name when saving. 17. Do one of the following: If you started this process with option 5 (Build Auto Validate Upload File), when you are ready to apply the license key: a. On the MIMIX Director Main Menu, enter option 6 (Configuration) to display the Director Configuration Menu. b. On the Director Configuration Menu, enter option 3 (License Maintenance), then enter option 6 (Apply Auto Validate License Key) to display the Apply License Key (APYLICKEY) screen. If you started this process with option 4 (Update License Key via AutoValidate): a. Return to the Update License Key screen. If the screen is not currently displayed, enter the following command to display it: UPDLICKEY 18 MIMIX Director Installation and Migration Guide v8.1

19 Starting the Installation b. Press F16 to display the Apply License Key (APYLICKEY) screen. 18. For the LKP path and file name, enter the path and file name of the LKP file saved in step 16 (for example, /VISIONSOLUTIONS/LICENSEKEYS/<LKP name>). Verifying Your License Key 1. On the MIMIX Director Main Menu, enter option 6 (Configuration) to display the Director Configuration Menu. 2. On the Director Configuration Menu, enter option 3 (License Maintenance), then enter option 2 (Display License Key Information). The Display License Key Information screen is displayed. 3. Verify that a license key is displayed and valid. If a license key is not displayed, enter the license key previously supplied to you (see Obtaining and Applying License Keys on page 14 for instructions). MIMIX Director Installation and Migration Guide v8.1 19

20 Chapter 3: Installation What to Do Next After you have completed the installation: If you have another instance of Director installed on your system, go to Chapter 4, Migration to MIMIX Director v8.1 if you want to migrate your data and configuration to Director v8.1. Otherwise, go to Chapter 5, Access MIMIX Director to learn about Director. 20 MIMIX Director Installation and Migration Guide v8.1

21 Migration to MIMIX Director v8.1 4 About Migrating to MIMIX Director v8.1 You can migrate configuration and data from Director 8.0 to Director 8.1. If you have an earlier release of Director, you must migrate that to 8.0 before you can proceed. To migrate to Director v8.1, follow the migration procedures in this chapter. The migration process allows retention of all your parameters, archive data, historical data, and cross-reference data. User Defined Enquiries (UDEs) Due to the addition of fields and field name changes, the UDEs are replaced during a migration to v8.1. If you have created or modified UDEs, it is recommended that you record the changes so that you can reapply them once the migration is complete. As of v6.4 SR-1, the supplied UDEs were templates only. You cannot modify UDEs that start with the letter Z. Web Interface Configuration If you have made any alterations to the supplied configuration files (for example, caching), those web interface settings will not be carried over. For more information, see the Getting Started with Getting Started with Vision Solutions Portal manual. MIMIX Director Installation and Migration Guide v8.1 21

22 Chapter 4: Migration to MIMIX Director v8.1 Before Migrating Complete the following sections before you begin a migration: Back up your current product libraries before you begin the migration (see Backing Up Director on page 22). Verify that Director v8.0 installed. Director v8.0 is the minimum version that can be migrated. If you have an earlier version of Director installed, you need to upgrade to v8.0 (and apply all the latest PTFs), before you can upgrade to v8.1. You can only upgrade to v8.0 from v7.1, so if you have a version prior to v7.1 installed, you must first upgrade to v7.1 before upgrading to v8.0, and then v8.1. Verify you are logged on using an authorized account. Verify that both the new and old versions of Director are currently installed (see Starting the Installation on page 13 to install the new software). Verify that all archived objects and spool files that are waiting to be archived have been archived to tape. Stop all Director activity (see Ending Director v8.0 and v8.1. ). Verify that no processes are locking Director objects (see Verifying No Locks on page 23) Backing Up Director As with all software migrations, it is recommended that you fully back up the product libraries before you begin. Do the following to back up libraries. NOTE If you end Director from outside of the product, ITID80 must be in the library list. 1. End Director v8.0 and Director v8.1 using the steps in Ending Director v8.0 and v8.1 on page Create a backup of library ITID80 before proceeding with the migration steps. 22 MIMIX Director Installation and Migration Guide v8.1

23 Starting the Migration Ending Director v8.0 and v Ensure that no users are logged into or using Director using the command: WRKOBJLCK ITID80 *LIB WRKOBJLCK ITID81 *LIB 2. Enter the following commands to ensure that Director is ended: ITID80/ENDID *ALL ITID81/ENDID *ALL The following message is displayed while Director is ending: Closing Subsystem, please wait... The following message is displayed when Director has successfully ended: End Director request ended normally. Starting the Migration Verifying No Locks Complete the following steps to ensure that no processes are locking Director objects: 1. Enter the following command to ensure that you are not locking any objects in your current job: RCLRSC *CALLER 2. Verify that there are no other locks on the object ITID81: WRKOBJLCK OBJ(ITID81) OBJTYPE(*LIB) 3. If there are locks, remove (end) all locks. Complete the following procedure to migrate Director to v8.1: 1. Add ITID81 to the library list. ADDLIBLE ITID81 MIMIX Director Installation and Migration Guide v8.1 23

24 Chapter 4: Migration to MIMIX Director v From a command line, prompt the following to display the Migrate Data & Configuration screen: IDMIG 3. Enter one of the following for the scope parameter: *CONFIG Copies configuration file data, map data areas, and map ACT* command defaults. *DATA Copies data file data and sets the CFINFO data area so that the Dynamic Cross Reference starts with existing data. *BOTH Does all actions for *DATA and *CONFIG 4. In From version, input 80 or *LAST. The job ID_MIGRATE runs in batch, and by default in QBATCH. 5. Once the batch job ID_MIGRATE has begun, sign off the IBM i and back on again (to release any locks on Director). 6. To remove a previous version of Director, see Chapter 7, Uninstall MIMIX Director on page MIMIX Director Installation and Migration Guide v8.1

25 Access MIMIX Director 5 Starting MIMIX Director Prior to starting Director, ensure that you have a user profile set up on the systems to which you require access. NOTE Qualify the STRID command with the library ITID81 when it is entered outside of the Director product. Otherwise, it is not necessary to qualify the STRID command. Do the following to start Director: NOTE If you did not add the license keys or the product was not migrated from v8.0, you may not have sufficient access to Director defined (see Obtaining and Applying License Keys on page 14 and Migration to MIMIX Director v8.1 on page 21 for more information). 1. Enter the following command at an OS command prompt: ITID81/STRID When Director starts, the MIMIX Director Main Menu is displayed: MIMIX Director Installation and Migration Guide v8.1 25

26 Chapter 5: Access MIMIX Director IDMAIN Select one of the following: MIMIX Director V8.1 Main Menu System: AB Object analysis 2. Optimization 3. Job analysis 4. Performance 5. Operations 6. Configuration 7. Accounting code analysis 8. Health Report 15. Data Manager 90. Sign off Bottom Selection or command ===> F3=Exit F4=Prompt F7=Task Manager F9=Retrieve F12=Cancel F16=System i Main menu F23=Set initial menu (c) Copyright 1992, 2011 Vision Solutions Inc. All rights reserved. 2. From the Main Menu, complete the following: a. Type IDWRKSEC and press enter. b. If you have authorization, the Work with Security screen displays with your user name in the list. If you are not authorized, contact the person who configured Director. c. Add an X to the fields to which you require access (press F13 for a description of each field). d. Exit the screen. NOTE The next step is to run a full cross-reference. By default, the library cross-reference multi-threads libraries with the first cross-reference. Consequently, the first cross-reference submits many jobs, perhaps hundreds. 3. Do one of the following: a. To run the default cross-reference, run the command: STRID *ALL b. To modify the cross-reference, see the MIMIX Director User Guide to assist with making the necessary changes. Then run the command: STRID *ALL. 26 MIMIX Director Installation and Migration Guide v8.1

27 Starting MIMIX Director NOTE The cross-reference may take several hours depending on the system setup. Many Director inquiries depend on the completion of the initial cross-reference. Therefore, we recommend waiting until the cross-reference has completed before proceeding with further product or portal configuration. You can verify that the cross-reference is complete by checking the Cross-Reference Activity portlet in the Vision Solutions Portal (see MIMIX Director Portal Application User Guide for more information). MIMIX Director Installation and Migration Guide v8.1 27

28 Access MIMIX Director Portal 6 Application About the MIMIX Director Portal Application The MIMIX Director portal application and the Vision Solutions Portal are automatically installed via the Director v8.1 installation wizard as the default installation. The Vision Solutions Portal uses an instance node to communicate with and run actions for the Director portal application. The portal application shows the health of your system and gives you information useful for analyzing application performance, system tuning, and optimization. For information on the Vision Solutions Portal, see the Getting Started with Getting Started with Vision Solutions Portal manual. For information on configuring and accessing the portal application, see the MIMIX Director Portal Application User Guide. MIMIX Director Installation and Migration Guide v8.1 28

29 Make the MIMIX Director Portal Application Available to Vision Solutions Portal Make the MIMIX Director Portal Application Available to Vision Solutions Portal When installing Director, the Director portal application, and Vision Solutions Portal through the installation wizard, the Director portal application is automatically made available to Vision Solutions Portal after first installing and configuring Vision Solutions Portal. Use the procedures in the MIMIX Director Portal Application User Guide to complete this process. The default portal connection is always present for the local machine where Vision Solutions Portal is running. When installing Director and the Director portal application through a 5250 emulator installer, the Director portal application must be manually made available to Vision Solutions Portal (after Vision Solutions Portal is installed and configured). Use the procedures in the Getting Started with Getting Started with Vision Solutions Portal manual, the section on Making a portal application available to the server to complete this process. MIMIX Director Installation and Migration Guide v8.1 29

30 Uninstall MIMIX Director 7 MIMIX Director provides a command that allows the full removal of the product. The most typical use for this command is after a successful migration where you remove the older version of Director that you have migrated. Do the following: 1. Enter the following commands: ITID81/ENDID PROCESS(*ALL) RCLRSC *CALLER 2. If you are removing Director v8.1 or above, logout of Vision Solutions Portal. 3. Ensure that there are no locks on the library for the version of product that you will be removing. WRKOBJLCK OBJ(ITID81) OBJTYPE(*LIB) NOTE Always use the latest version of the removal command. For example, if you have installed Director v8.1 and are removing Director v8.0, then use the Director v8.1 command. 4. Enter the following command to remove the version of Director, where x is the number for a product release version (V8R0M0, as an example for V8.0): ITID81/IDRMVPRD 7PA2K40 VxRxMx 5. Display QSYSOPR messages and reply with a G to the following CPA2401 message: Director Product 7PA2K40,V8R1M0 uninstall process requested by user XXXXXX. Please respond with G to confirm product can be un-installed, C to cancel. Object Auditing Values will NOT be Re-Set. (G, C) MIMIX Director Installation and Migration Guide v8.1 30