IBM Support

Readme file for Dynamic Workload Console Fix Pack 2, Version 9.4

Product Readmes


Abstract

This readme file provides important information about Fix Pack 2 for Dynamic Workload Console version 9.4.0.

Content

The attached pdf file contains the Readme in the English language. To view a translated version of the Readme in a language of your choice, scroll to the end of the page and select the language in the Translate this page: field.

9.4.0-IWS-DWC-FP0002.pdf9.4.0-IWS-DWC-FP0002.pdf

 

Note

Before using this information and the product it supports, read the information in Notices.

This edition applies to Fix Pack 1 for version 9, release 4, modification level 0 of IBM® Dynamic Workload Console.

IBM Dynamic Workload Console Readme File for Fix Pack 2 for Version 9.4.0

Date
14 November 2017
Fix Pack Name
9.4.0-IBM-DWC-FP0002
Product
IBM Dynamic Workload Console version 9.4.0
General Description
IBM Dynamic Workload Console 9.4.0 Fix Pack 2

This readme file provides important information about Fix Pack 2 for IBM Dynamic Workload Console version 9.4.0.

This readme file is the most current information for the fix pack and takes precedence over all other documentation for Dynamic Workload Console version 9.4.0.

It is divided into the following sections:

IBM Dynamic Workload Console version 9.4.0 Fix Pack 2 supports all product versions indicated in the IBM Dynamic Workload Console version 9.4 Release Notes which can be accessed at the following link: http://www-01.ibm.com/support/docview.wss?uid=swg27048864#interoptable.

For the most up-to-date information about supported operating systems, software and hardware requirements, see the Detailed system requirements document at the following URL: http://www-01.ibm.com/support/docview.wss?uid=swg27048859.

Review the following sections thoroughly before installing or using this fix pack.

About this fix pack

This section contains information specific for this fix pack including what has been modified or introduced, what has been fixed, product versions or components to which the fix pack applies, and compatibility issues, if any.

Product versions and components to which the fix pack applies
This fix pack can only be applied on top of Dynamic Workload Console version 9.4 and V9.4.1.

This section includes the following subsections:

Features introduced with Fix Pack 2

Mixed pricing models

Easily define different pricing models on workstations in your environment.

According to your IBM Workload Scheduler license, IBM® License Metric Tool helps you maintain your license compliance. By using License Metric Tool, you can generate reports that summarize your license consumption. The generated reports are maintained on the License Metric Tool server and should be periodically reviewed and signed, creating a history for audit purposes in the process. If you are contacted by a third-party software compliance auditor who plans to visit your enterprise to carry out a software audit, ensure that all reports are up-to-date and signed, and then supply copies of reports that cover the time periods that the auditor requests.

You can now take advantage of improved flexibility when defining your pricing model. For each single workstation in your environment, you can define the pricing model to be applied.

When you set the license Type keyword to by Workstation in optman, you can define for each single workstation the pricing model to be applied to it at the workstation creation time.

Replying to messages for IBM i child jobs
Support for replying to messages for an IBM i parent job was introduced in a previous release. With this release, the same support is extended to IBM i child jobs. When an IBM i job is in SUSP (suspended) status, waiting for a reply to a message, you can reply to the message for parent and child jobs from the Dynamic Workload Console when monitoring the parent job.
Specifying dependencies that link a job to a job stream or a job stream to a job
Dynamic Workload Console enhanced for z/OS users with application dependencies support.
Setting the Manually Hold, NOP, and Critical options in the AD database
You can now set the Manually Hold, NOP, and Critical options for a job directly in the Application Description database, from either the Options or Variable Duration and Deadline section
REST API for z/OS users
Already available in the distributed environment and now available in a z/OS environment, a set of fully functional APIs that are implemented based on Representational State Transfer (REST) services. The REST API helps you easily integrate workload scheduling capabilities with external products and solutions.
The following are requests for enhancements (RFEs) introduced in Fix Pack 2:
RFE 179819: Database job executor handles stored procedure errors
Enhance the database job executor to handle stored procedure errors.
RFE 109287: Rerun multiple jobs with a single confirmation prompt

Rerun multiple jobs without having to confirm the rerun action for each individual job.

You can now select multiple jobs from the Dynamic Workload Console and rerun all of them in a single action. Previously, a confirmation dialog prompted you to confirm the rerun for each job selected. When rerunning a large number of jobs this can be time consuming. With this enhancement, a confirmation dialog lists the jobs you want to rerun and prompts you a single time to confirm the rerun on all of the jobs.

A side effect of this new feature is a more responsive user interface with improved response times. The more frequently used actions such as, setting the priority or limit from the Dynamic Workload Console monitoring portlet, have been updated so that they run more smoothly.

RFE 102143: Lengthen text field for script path
Lengthen the size of the field related to a script to be run. When defining a job that runs a script as the task, the text field specifying the path to the script can now accommodate a much longer string. For example, if the path is quite long or if it contains numerous variables, they are now displayed in the text field when you view the job definition from both the Workload Designer and from the List Workload Definitions portlet.
RFE 15616: Actual workstation displayed when monitoring jobs

The name of the workstation where a job, scheduled to run on a pool or dynamic pool, actually ran.

When jobs are scheduled to run on pools or dynamic pools, you might want to monitor the job or the workstation where the job ran. Previously, this information was available only in the job log. With this enhancement, the name of the actual workstation where the job ran is also available in a new column in the monitor job query. This detail is available if the job has started or has already run. This information can also be output in reports.

This information can also be useful when you need to determine your license consumption and therefore need to know on which workstation in the pool the job actually ran.

For details about the actual workstation see the columns that can be defined when monitoring jobs in the Dynamic Workload Console. The runtime information contained in the composer showjobs command also contains this information.

RFE 108425: File monitor support for already created files
Normally the filemonitor utility runs an initial scan and then runs subsequent scans to detect any new or changed files since the initial scan that match specific criteria. This means that if there are any existing files matching the criteria when the initial scan runs, they are not considered. The utility has been updated with a new parameter to be able to discover existing files during the initial scan that match the criteria and can therefore generate an event. For more information see the -generateEventsOnFirstScan argument for the filemonitor utility in the User's Guide and Reference, and the description of the -generateEventsOnFirstScan argument.
RFE 106345: RUN PJP and PVU License Networks in the SAME Network
Easily define different pricing models on workstations in your environment

For more information about new features introduced with this fix pack, see Dynamic Workload Console version 9.4 Fix Pack 2 enhancements.

Helpful videos demonstrating new features for IBM Workload Scheduler is available on Workload Automation channel.

APARs and defects fixed in Dynamic Workload Console Fix Pack 2 for version 9.4.0

This fix pack includes a number of fixes for internal defects found by the verification team that mainly cover the following product capabilities: installation, auditing, and mirroring.

This section lists APARs solved by Fix Pack 2.

APAR ABSTRACT
IV99644 Job status mismatch between DWC & conman
IV94014 ERROR: AWSUI6172E IS DISPLAYED WHEN TRYING TO OPEN THE JOB DEFINITION INTO JOBSTREAM
IJ00450 CHECKSYNC ABENDS WITH ERROR: "NULL" ON MASTER WITH TZ=NO
IV95090 APPLICATIONS TEMPLATES CONTAINING VARTABLE WITH "\" ARE WRONGLY IMPORTED VIA TDWC
IV96661 INCORRECT FRENCH TRANSLATION FOR THE WORD "BLOCKED" WHEN VIEWINGMONITOR JOSBTREAMS. IT BADLY SHOWS GROUPé, SHOULD BE BLOQUé.
IV94432 ONOVERLAP DONOSTART AND ONOVERLAP ENQUEUE DOES NOT WORK IN CROSSDAY SCENARIO
IV98210 DEADLOCKS WITH CANCEL JS

Known limitations and workarounds

The following are software limitations and workarounds that affect Dynamic Workload Console version 9.4.0 Fix Pack 1 and 2. For a list of known problems and limitations documented for the V9.4 General Availability release, refer to the Dynamic Workload Console V9.4 Release Notes.

9.4 Fix Pack 2:

Query parameter transmitted in SSL Request (177529)
A request, sent over SSL, contains parameters that are transmitted in the Query part of an HTTP request. When sending requests, the browser's history can be used to reveal the URLs that contain the query parameter names and values.
z/OS® engine connection does not work after updating the port number (184418)
If you run the script updateZosEngine.sh in DWC_Instdir/wastools to update the port number of a z/OS engine connection and then install fix pack 2, the engine connection from the Dynamic Workload Console fails because the port number has reverted back to the original value before running the updateZosEngine.sh script.

Workaround: After the fix pack installation, run the updateZosEngine.sh script again and then restart the WebSphere Application Server.

Monitor job properties panel - change date (185006)
In Monitor job properties panel, if you enter a wrong date format for the start of a job (earliest start - latest start), the system automatically replaces the value specified with the date of the current day without any alert.
From the job stream graphical view with a z/OS engine connection, a job is deleted but remains in the view (185124)
When monitoring a job stream from the job stream graphical view, if you define a dependency between two jobs (in two different job streams) or between a job stream and a job (in a different job stream), and then try to delete the successor job, the job is not deleted from the view although the dependency has been removed.
REST API z/OS (185139, 185140)
Queries related to critical jobs and critical path do not work for the REST API in a z/OS environment.
Close selected job streams object does not work after displaying job stream run cycle preview (185169)
In Workload Designer, if you click on Run Cycle Preview tab, select the job stream object in the Workload Designer Working List and click on Close Selected button, the job stream object does not close.
Software limitations related to Dashboard Application Services Hub (DASH)
[DASH 67674] Cross-site request vulnerability (184233)
A defect has been opened against DASH (67674) to address the issue of cross-site request forgery.
[Dash 67677] Cached content can be accessed via HTTPS (184403)
Browsers might store a local cached copy of content received from web servers. Few internet browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this might be retrieved by other users who have access to the same system in a future time. A defect has been opened against Dash (67677).

9.4 Fix Pack 1:

After a fresh installation of the Dynamic Workload Console version 9.4.0 Fix Pack 1 with WebSphere® Application Server 8.5.5 FP 11, the administrator cannot view or use any of the portlets
After a fresh installation of the Dynamic Workload Console version 9.4.0 Fix Pack 1 with WebSphere Application Server 8.5.5 FP 11, the administrator cannot view or use any of the portlets. From the Dynamic Workload Console, he can just assign manually one of the following roles to the logged in users:
  • TDWBAdministrator
  • TWSWEBUIAdministrator
  • Administrator
  • chartAdministrator
  • iscadmins
  • samples
To prevent this problem, run the following procedure:
  1. Install WebSphere Application Server 8.5.5 FP 11
  2. Apply WebSphere Application Server iFix 30449.999.744.8.5.5.10-WS-WAS-IFPI76481 available on IBM Fix Central.
  3. Install Jazz™ for Service Management 1.1.3 CP2
  4. Install the Dynamic Workload Console version 9.4.0 Fix Pack 1
The iFix enables Jazz for Service Management mapping between Dynamic Workload Console user roles and the administrator role.
If you install the iFix after installing the Dynamic Workload Console, you can manually map user roles and administrator role by running the following commands from the Dashboard Application Services Hub consolecli command line: 
Run [JazzSM_Install_path]/ui/bin/tipcli.sh MapUsersToRole   --username <TDWCadmin>   --password <TDWCadminpassword>   --roleName TWSWEBUIAdministrator   --usersList   uid=admin,o=defaultWIMFileBasedRealm  Run[JazzSM_Install_path]/ui/bin/tipcli.sh   --username <TDWCadmin>   --password <TDWCadminpassword>    --roleName TDWBAdministrator   --usersList   uid=admin,o=defaultWI
Job streams graphically overlap in the graphical view (178184)
When loading job stream B in the graphical view, and job stream B has a dependency on job stream A, if job stream B contains a large number of objects, it might happen that opening job stream B it can graphically overlap job stream A.

Workaround: To workaround this problem, click the auto-layout button to rearrange the graphical view, or manually adjust job stream B layout in the view.

In the Job Stream View, a job stream with hundreds of objects (jobs and dependencies) might not be saved in PNG format (179497)
In the Job Stream View, trying to save a job stream with hundreds of objects (jobs and dependencies), the image might look corrupted and might not be possible to save it.

Workaround: To workaround this problem, save the job stream in SVG format and then use the appropriate tool to convert it from SVG to PNG format.

Connecting the Dynamic Workload Console version 9.4.0 Fix Pack 1 to an engine machine running IBM Workload Scheduler version 9.3.0 Fix Pack 3 or earlier, some functions might be missing.
The product features available from the Dynamic Workload Console are fully supported when connecting to a version 9.4.x engine through the Representation State Transfer Services (REST) programming interface represented by port number 31116 (default port). However, this connection does not ensure a complete functionality when connecting to previous engine versions (version 9.3.0 Fix Pack 3 or earlier).

Workaround: When connecting the Dynamic Workload Console version 9.4.0 Fix Pack 1 to an engine running IBM Workload Scheduler version 9.3.0 Fix Pack 3 or earlier, modify the port number for your engine connections to the Enterprise JavaBeans (EJB) interface represented by port number 31117.

Disabling the plan mirroring on the engine and submitting a job stream into the current plan, the status of the internal jobs is not updated in the graphical view.
The limitation is due to the fact that, disabling the plan mirroring, the information stored in the IBM Workload Scheduler database are not available. The same problem happens if the IBM Workload Scheduler database is down.

Fix pack structure

This section describes the structure of the images contained in this fix pack.

Fix pack files available using Fix Central

This is the structure of the fix pack in Fix Central: 
+---9.4.0-IBM-DWC-FP0002.README.zip  |  +---9.4.0-IBM-DWC-AIX-FP0002.zip  |  +---9.4.0-IBM-DWC-LINUX390-FP0002.zip  |  +---9.4.0-IBM-DWC-LINUX_X86_64-FP0002.zip  |  +---9.4.0-IBM-DWC-WINDOWS_X86_64-FP0002.zip

Installing the fix pack

This section describes how to apply Fix Pack 2.

Before starting the installation, verify that:
  • The Dynamic Workload Console is active.
  • No user is connected to the Dynamic Workload Console to prevent the data related to their working session from being lost.
This section is divided into the following subsections:

Installation notes

Read this section thoroughly before installing this fix pack.

  • Before installing the fix pack, ensure you have installed the required prerequisite software. With the Dynamic Workload Console version 9.4 Fix Pack 2, a newer version of Jazz for Service Management is required, version 1.1.2.1.

    To obtain the latest information about software requirements for IBM Workload Scheduler , run the https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/prereqsForProduct?deliverableId=196702D00EBC11E58BF1AF9D8B1D437A&osPlatforms=AIX|HP|IBM%20i|Linux|Solaris|Windows|z/OS&duComponentIds=S002&mandatoryCapIds=30|9|13|121|25|26&optionalCapIds=130|132si ="(Opens in a new tab or window)">Software Requirements report and browse to the relevant section.

  • On UNIX systems only: Before installing either the Dynamic Workload Console version 9.4 or this fix pack, make sure that umask is set to 022. To verify that umask is set to the correct value, from a command prompt, run the umask command. If the value is different from 022, modify it by running the command: 
    umask 022
  • If you plan to connect the Dynamic Workload Console version 9.4 Fix Pack 2 to a z/OS engine, ensure the following APARs for the z/OS platform are installed to enable the new feature: Application Dependencies, NOP, MH, Critical Path Indicator and the compatibility with z/OS engine 8.6, 9.1 and 9.2:
    • PI85254 DWC Support for application dependencies
    • PI85255Compatibility APAR DWC 940 fix pack 2 with old release

Installation methods

When you install the fix pack, you can choose one of the following methods:

Disk space requirements

Before starting the fix pack installation, ensure that you have the following space available in the file system. The values indicated in the table show the disk space required by the Dynamic Workload Console alone. For the disk space required by other components, see the relevant documentation. For the most up-to-date information about disk space and memory requirements, generate a dynamic hardware requirements report from the IBM Software Product Compatibility Reports web site at the following URL: http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/hardwareReqsForProduct?deliverableId=196702D00EBC11E58BF1AF9D8B1D437A&osPlatforms=AIX|HP|IBM%20i|Linux|Solaris|Windows|z/OS&duComponentIds=S002|S001|A005|A003|A004.

Table 1. Disk space requirements for installing a Dynamic Workload Console fix pack
Operating System Installation directory Temporary directory
AIX® 2 GB 800 MB
Linux s390x 2 GB 800 MB
Linux x86-64 2 GB 800 MB
Windows 64 2,5 GB 1 GB
Note: In addition to the above disk space, the installation requires further 579 MB on /usr file system.

If the installation fails because of lack of free disk space, you must stop the installation, free space on your disk, and start the installation again.

Before Installing

Before installing the fix pack using any of the methods described in the following sections, complete the following actions:
  1. Download the appropriate ZIP files for the operating system from IBM Fix Central.
  2. Extract the content of the ZIP files into a directory, using one of the extraction tools available on your system or downloadable from the internet . The tool you use must be able to keep the file permissions on the extracted files, for example, infozip. On Windows systems, ensure that you extract the image into a path that is not very long, otherwise, the file name might be truncated. The maximum length allowed is 255 characters. If you are installing on a UNIX operating system, run the following command: 
     chmod -R 755 <imagesDir>
Note: To extract the .zip file onto a Windows 64-bit system, ensure that the eImage is not located on the desktop because the Windows operating system extract tool has a problem. Choose another directory into which to extract the fix pack eImage.

Installing Dynamic Workload Console prerequisites

Before installing this fix pack, you must upgrade:
  • Jazz for Service Management from 1.1.2.0 to 1.1.2.1
  • Dashboard Application Services Hub from 3.1.2.0 to 3.1.2.1)
You can run a silent installation of Jazz for Service Management 1.1.2.1 that includes Dashboard Application Services Hub 3.1.2.1:
  1. Download the Jazz for Service Management install package.
  2. Edit the response file: 
    <JAZZSM_INSTALLATION_MEDIA>/responsefiles/<windows|unix>/  update_jazzsm_fullprofile_response.xml
  3. In the section: 
    <install modify='false'>
    remove or comment all the packages with the exception of the following packages:
    <!-- JazzSM extension for WebSphere Application Server offering   selected for installation -->  <offering id='com.ibm.tivoli.tacct.psc.install.was85.extension'   profile='IBM WebSphere Application Server V8.5' features='main.feature'   installFixes='none'/>
    <!-- IBM Dashboard Application Services offering   selected for installation -->  <offering id='com.ibm.tivoli.tacct.psc.tip.install'   profile='Core services in Jazz for Service Management'   features='com.ibm.tivoli.tacct.psc.install.server.feature.tip.install,  com.ibm.tivoli.tacct.psc.install.server.feature.tip.config'   installFixes='none'/>
  4. Run the silent installation of Jazz for Service Management.
  5. Now, you can proceed with the upgrade of the Dynamic Workload Console.

Installing the Dynamic Workload Console for the first time using the IBM Installation Manager wizard

To install the Dynamic Workload Console for the first time using the interactive wizard, complete the following steps:
  1. Perform the actions described in section Before Installing.
  2. Download the version 9.4 General Availability eImage from Passport Advantage Online specific for the operating system and extract it into a path of your choice.
  3. Download the version 9.4 Fix Pack 2 TAR or ZIP file from IBM Fix Central specific for the operating system and extract it. To extract the .tar file, ensure that you use the GNU version of the TAR command. Otherwise, if you extract the file using a version other than GNU, your fix pack installation fails. If you are installing on a UNIX operating system, run the following command: 
     chmod -R 755 <imagesDir>
  4. Depending on the type of operating system, run the following command:
    On Windows operating systems:
    From the directory where you extracted the files, run setupDWC.cmd -gapath <extraction_path>.
    On UNIX and Linux operating systems:
    From the directory where you extracted the files, run setupDWC.sh -gapath <extraction_path>.
    where <extraction_path> is the path into which you extracted the IBM Workload Scheduler General Availability eImage.

    The IBM Installation Manager window opens.

  5. Select the packages you want to install and the click Next to continue.
  6. In the Validating Results page, check that all the prerequisites are fulfilled and then click Next to continue.
  7. In the Licenses page, read the license agreement for the selected package. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and then click Next.
  8. In the Install Packages page, type the directory where you want to install the product and then click Next to continue.
  9. In the Summary page, review your choices before upgrading the product package. To change any choices that you made on previous pages, click Back and make the changes. When you are satisfied with your installation choices, click Install to install the packages.
  10. Click Finish to complete the installation.

Installing the fix pack on the Dynamic Workload Console General Availability version 9.4 using the IBM Installation Manager wizard

To install the fix pack using the interactive wizard, complete the following steps:
  1. Perform the actions described in section Before Installing.
  2. Download the TAR or ZIP file specific for the operating system and extract it. To extract the .tar file, ensure that you use the GNU version of the TAR command. Otherwise, if you extract the file using a version other than GNU, your fix pack installation fails. If you are installing on a UNIX operating system, run the following command: 
     chmod -R 755 <imagesDir>
  3. You can start the installation process by using one of the following methods: the:
    IBM Installation Manager program
    1. Start the Installation Manager.
    2. In the menu bar, click File > Preferences.
    3. The Repositories window opens. Click Add Repository.
    4. In the Select a Repository window, in the Filter pane, type the path to the directory where the fix pack files are located.
    5. In the Directories pane, select the directory containing the fix pack files and click OK.
    The scripts update.bat or update.sh
    Depending on the type of operating system, run the following command:
    On Windows operating systems:
    On Windows platforms, you must use only the 32-bit version of IBM Installation Manager. From the root directory of the eImages, run update.bat.
    On UNIX and Linux operating systems:
    From the root directory of the eImages, run update.sh.
    The IBM Installation Manager window opens.
  4. Verify that the check box Search service repositories during installation and updates is not selected, then click OK in the Repositories window.
  5. Click Update.
  6. In the Installation Packages page, select the "Dynamic Workload Console" > "Version 9.4.0.2" product package. Click Next to continue.
  7. In the Licenses page, read the license agreement for the selected package. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and then click Next.
  8. In the Summary page, review your choices before upgrading the product package. To change any choices that you made on previous pages, click Back and make the changes. When you are satisfied with your installation choices, click Update to install the update packages.
  9. Click Finish to complete the installation.

Upgrading Dynamic Workload Console version 9.1 or later

To upgrade Dynamic Workload Console version 9.1 or later, complete the following steps:
  1. Perform the actions described in the section Installing the Dynamic Workload Console for the first time using the IBM Installation Manager wizard. Be sure to install the product in a directory different from the one where the version earlier than 9.4 is installed.
  2. Follow the instructions in Upgrading Dynamic Workload Console V9.1 or later, in the Planning and Installation guide.

Upgrading Dynamic Workload Console version 8.6

To upgrade Dynamic Workload Console version 8.6, complete the following steps:
  1. Complete the actions described in the section Installing the Dynamic Workload Console for the first time using the IBM Installation Manager wizard. Be sure to install the product in a directory different from the one where version 8.6 is installed.
  2. Follow the instructions in Upgrading Dynamic Workload Console V8.6 single instance on the same workstation, in the Planning and Installation guide.

Installing the fix pack using IBM Installation Manager silent installation

Before you begin

After you complete the actions described in the section Before Installing, if you want to install the fix pack in silent mode use the silent installation. When you run a silent installation, you must create a response file to use as input to the IBM Installation Manager silent installation commands. The response file includes all the information required to run the installation without user intervention.

As a prerequisite step, specifically for the Dynamic Workload Console silent installation, you can run a script that checks the system against the product system requirements to ensure a successful installation without delays or complications. The prerequisite check script checks requirements such as:
  • Supported operating system.
  • Sufficient RAM.
  • Sufficient swap file space.
  • Disk space for the creation of the installation, Jazz for Service Management, and temporary directories passed in input to the script.
For specific details about the product system requirements see Disk space requirements.
To run the prerequisite check script, copy the script dwcPrereqcheck.bat or dwcPrereqCheck.sh and the Prerequisites folder from the fix pack image to a folder on the system where you plan to run the installation and ensure you have read, write, and execute permissions on the Prerequisites folder. If the fix pack image is already on this system then you can run the script directly from the fix pack image location. Submit the script to run as follows:
On Windows operating systems:
Run the following command: 
dwcPrereqCheck.bat -instdir <DWC_HOME> -jazzdir <JAZZDIR> -tmpdir <tmp>
On UNIX or Linux operating systems:
Run the following command: 
dwcPrereqCheck.sh -instdir <DWC_HOME> -jazzdir <JAZZDIR> -tmpdir <tmp>
where,
<DWC_HOME>
Represents the Dynamic Workload Console installation path, for example, on Windows, this path is C:\Program Files\IBM\TWAUI.
<JAZZDIR>
Represents the directory where the Jazz for Service Management extension for WebSphere is installed.
<tmp>
Represents the temporary folder on the system where you are running the installation.
The results of the prerequisite check are written to a text file named, result.txt, located in the Prerequisites folder.
You are provided with several sample response files located in the \response_files\ directory. Depending on the initial version of your components, select the appropriate response file, determine the eImages you need to download and extract, and then customize the properties in the response file including the settings for the repository location of the eImages before performing the silent installation.
Important: During the silent installation, if the location specified for a repository is not found, then correct the location and before rerunning the installation, clear the repository locations from IBM Installation Manager:
  1. Open the Preferences panel in Installation Manager.
  2. From the Repositories page, select and remove the repository location in error.
  3. Correct the repository location in the response file.
  4. Rerun the silent installation.
Table 2. Response files for fix pack installation
Response File Name Description Required Images and Repository Location
IWS94_UPDATE_DWC_<os_name>.xml
 This response file applies the fix pack to a version 9.4 console bringing it to the 9.4 FP2 level. 9.4 FP2
IWS94_UPGRADE_DWC_<os_name>.xml This response file upgrades a version 9.1 or later console to the 9.4 FP2 level.
  • 9.4 FP2
  • 9.4 GA
IWS94_FRESH_DWC_<os_name>.xml This response file performs a fresh installation of the version 9.4 GA console plus fix pack 2. Use this installation if you have WebSphere Application Server and Installation Manager already installed.
  • 9.4 FP1
  • 9.4 GA
IWS94_FRESH_FULL_DWC_<os_name>.xml This response file performs a first time fresh installation of the version 9.4 GA console, fix pack 2, WebSphere Application Server, Jazz for Service Management, Dashboard Application Services Hub, and Installation Manager. WebSphere Application Server, Jazz for Service Management, Dashboard Application Services Hub must be purchased separately.
  • 9.4 FP1
  • 9.4 GA
  • WebSphere Application Server
  • Jazz for Service Management extension for IBM WebSphere with Dashboard Application Services
  • Installation Manager
IWS94_FRESH_IntegrationWorkbench_
<os_name>.xml
 This response file performs a fresh installation of the version 9.4 GA Integration Workbench plus fix pack 1. Use this installation if you have WebSphere Application Server and Installation Manager already installed.
  • 9.4 FP1
  • 9.4 GA
IWS94_FRESH_FULL_IntegrationWorkbench_
<os_name>.xml
 This response file performs a first time fresh installation of the version 9.4 GA Integration Workbench, fix pack 1, WebSphere Application Server, and Installation Manager. WebSphere Application Server must be purchased separately.
  • 9.4 FP2
  • 9.4 GA
  • WebSphere Application Server
  • Installation Manager

About this task

Create your own response file or customize a sample response file to include the options required to complete the installation you want to perform. Complete the following steps:

Procedure

  1. Copy the relevant response file to a local directory.
  2. Edit the Dynamic Workload Console section. For details about the response file properties, see the topic about the Dynamic Workload Console response file properties in the Planning and Installation guide.
  3. Save the file with your changes.
  4. Open a command-line prompt.
  5. Change to the Installation Manager tools directory. The default path for the tools directory is:
    • On Windows operating systems: 
      C:\Program Files\IBM\Installation Manager\eclipse\tools
    • On UNIX and Linux operating systems: 
       /opt/IBM/InstallationManager/eclipse/tools
  6. To run the Installation Manager in silent mode, run the following command:
    • On Windows operating systems: 
      imcl.exe -c
    • On UNIX and Linux operating systems: 
      ./imcl -c
  7. Type P and press the Enter key to access the Preferences menu.
  8. Type 1 and press the Enter key to access the Repositories menu.
  9. Remove all the listed repositories by typing the number beside each repository to edit it and then type 2 to remove the repository. Complete these actions for each of the listed repositories.
  10. If there is an X beside the S menu item related to Search service repositories, type S and press the Enter key to deselect it.
  11. Type A and press the Enter key to apply the changes.
  12. Type R and press the Enter key to return to the main menu.
  13. Type X and press the Enter key to exit.
  14. Go to the Installation Manager tools directory. The default tools directory is:
    • On Windows operating systems: 
      C:\Program Files\IBM\Installation Manager\eclipse\tools
    • On UNIX and Linux operating systems: 
       /opt/IBM/InstallationManager/eclipse/tools
  15. Run the following command:
    • On Windows operating systems: 
      imcl.exe input <local_dir>\response_file.xml  -log <local_dir>\log_file.xml  -acceptLicense -nosplash
    • On UNIX and Linux operating systems: 
       ./imcl input /<local_dir>/response_file.xml  -log /<local_dir>/log_file.xml  -acceptLicense -nosplash
      where response_file is the name of the response file to be used for the installation, and log_file is the name of the file that records the output of the silent installation. For information about the installation log files see Installation log files.

Installation log files

This section describes the log files created by the installation process using the IBM Installation Manager wizard.
  • Log file for Installation Manager:
    On Windows operating systems:
    C:\ProgramData\IBM\InstallationManager\logs\<YYYYMMDD_HHMM>.xml
    Note: The folder ProgramData is a hidden folder.
    On UNIX and Linux operating systems:
    /var/ibm/InstallationManager/logs/<YYYYMMDD_HHMM>.xml
    where <YYYYMMDD> is the date and <HHMM> is the time when the log file is created.

Documentation updates for IBM Dynamic Workload Console Fix Pack 2, version 9.4.0

Any additions or changes to the documentation as a result of these fix packs have been integrated into the online product documentation available in IBM Knowledge Center.

Contacting IBM Software Support

Before contacting IBM Software Support with a problem, refer to the IBM Software Support site by accessing the following Web address:

http://www.ibm.com/software/support

To access IBM support, click the IBM support link at the bottom right of the page.

If you want to contact IBM Software Support, see the IBM Software Support Handbook at the following website:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information:
  • Registration and eligibility.
  • Telephone numbers, depending on the country in which you are located.
  • Information you must have before contacting IBM Software Support.

Notices

This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
USA
For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
USA

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions. Actual results may vary.

The client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.

The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “http://www.ibm.com/legal/copytrade.shtml." Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript and the Postscript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc., in the United States, other countries, or both and is used under license therefrom.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.

ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.

 Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

Copyright Date

© Copyright

[{"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Tivoli Dynamic Workload Console","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"9.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 February 2020

UID

swg27050257

Page Feedback