IBM Integration Test Report
for
IBM WorkSpace On-Demand

15 November 1997

Software Servers Integration Test (SSIT)

©. Copyright IBM Corp. 1997

Contents

1 Purpose
2 Software Servers Integration Test (SSIT)
3 Test Objectives

4 IBM WorkSpace On-Demand

  • 4.1 General Product Information
  • 4.2 Overview of Scenarios Tested
  • 4.3 Test Environment
  • 4.4 Test Results
  • 4.4.1 System Environment
  • 4.4.2 Installation of IBM WorkSpace On-Demand
  • 4.4.3 Administration
  • 4.4.4 Installation and Configuration of IBM Software Server clients
  • 4.4.4.1 Installation and Configuration of IBM CICS OS/2 Client V1.1
  • 4.4.4.2 Installation and Configuration of IBM Communication Server OS/2 Access Feature V5.0
  • 4.4.4.3 Installation and Configuration of IBM Universal Database OS/2 Client Application Enabler V5.0
  • 4.4.4.4 Considerations for Lotus Notes OS/2 Client V4.51
  • 4.4.5 Interaction and Coexistence
    • Attachments
  • Samples
  • Sample Response Files
  • Public Application Definitions
  • Example of Configuring Adapters
    •
  • SSIT Environment Configuration Matrix
  • Scenario and Test Case Detail
  • Notices

    • 1 Purpose

    This report describes the integration testing results of the Software Servers Integration Test (SSIT) laboratory. The report highlights cross-product testing and pinpoints any cross-product dependencies. It supplements product information and publications, and assumes familiarity with the products involved.

    Back to Contents

    2 Software Servers Integration Test (SSIT)

    This document is produced by the IBM Software Servers Integration Test team.

    IBM's integration testing of AIX, NT, and OS/2 products focuses on customer requirements and provides synergy between the SSIT lab and the various product development organizations.

    To contact the Software Servers Integration Test organization
    SSIT external address SSIT@raleigh.ibm.com
    Alternative address rtaliafe@us.ibm.com

    The Software Servers Integration Test reports are available on the Internet at:

    New reports are continually being made available for your convenience in the installation and use of our products.

    Back to Contents

    3 Test Objectives

    The purpose of the Software Server Integration Test is to test the IBM Software Servers family of servers to ensure that they work together and integrate smoothly as an IBM family of offerings.

    The objectives of the IBM WorkSpace On-Demand testing were:

    Back to Contents

    4 IBM WorkSpace On-Demand

    4.1 General Product Information

    IBM WorkSpace On-Demand

    Back to Contents

    4.2 Overview of Scenarios Tested

    The IBM WorkSpace On-Demand Test Objectives were verified through the execution of the following types of tests. The location of the Scenario and Test Case Detail is included in the Attachments section of this document.

    Back to Contents

    4.3 Test Environment

    The Software Servers Integration Test team used a single test environment, SSIT Environment Configuration Matrix, to achieve the test objectives.

    Back to Contents

    4.4 Test Results

    4.4.1 System Environment

    Prior to the installation of IBM WorkSpace On-Demand Server on the Warp Server 4 systems, Fixpak 29 from the IBM WorkSpace On-Demand CD was installed. No additional Fixpak was applied to the Warp Server SMP Version 4 system.

    4.4.2 Installation of IBM WorkSpace On-Demand

    4.4.2.1 General Installation Recommendations

    IBM WorkSpace On-Demand must be installed on the Domain Controller in order for the required changes to the domain controller database to be applied. In addition, IBM WorkSpace On-Demand may also be installed on Backup Domain Controllers and Additional Servers in the same domain.

    4.4.2.2 Attended Installations or Removals

    4.4.2.3 Remote Installations using a Software Distribution Manager

    4.4.3 Administration of IBM WorkSpace On-Demand

    Administration of IBM WorkSpace On-Demand was performed using the available hardcopy publications.

    Hints and Tips for Administrators

    Following are a series of hints and tips for administrators of IBM WorkSpace On-Demand:

    4.4.4 Installation/Configuration of IBM Software Server clients

    Installation and configuration of selected IBM Software Server clients was completed before further testing was performed against these selected clients. Because of the nature of the IBM WorkSpace On-Demand product, traditional installation and configuration of these products cannot be performed. Following are the detailed installation and configuration instructions for each IBM Software Server client:

    4.4.4.1 Installation and Configuration of IBM CICS OS/2 Client V1.1

    OVERVIEW

    These instructions are based on the SSIT Lab's analysis of the OS/2 CICS version 1.1 setup on a WorkSpace On-Demand (WSOD) Client. They assume the following server configurations:

    Domain Controller
    On which the public application definitions are maintained.
    IBM WorkSpace On-Demand Server
    From which the Client machines are RIPL'ed.
    Application Source Server
    Used to store the application specific binaries and user specific files.

    Note: All of the above servers are required, but they may be all resident on the same physical machine.

    SETUP STEPS

    Following are the steps necessary to establish CICS 1.1:

    1. CICS Client Installation
    2. CICS Access Control Profile Setup
    3. CICS Requesters
    4. CICS FIT File Updates
    5. CICS Application Definitions
    1. CICS Client Installation
      2.         [CICS Steps]

      Install CICS client on a Merlin Workstation in order to create the following directory structures and files required for the product. Then copy the directory/file structures to the Application Source Server:

      \CICS\-+-BIN |-BOOKS |-CIG\----+-ADMIN | |-BIN | |-CGI | +-HTML // .................. Note: the following directories are not // needed unless CICS development is to // take place on the workstation. |-COPYBOOK |-INCLUDE |-LIB |-LOTUS |-PLIHDR +-SAMPLES\+-C |-COBOL |-LOTUS |-PLI |-REXX +-SERVER

      This is done by executing the following (with c: representing the client where CICS is installed and with x: representing the target Application Source Server):

      XCOPY C:\CICS\*.* X:\CICS /S /E /V

      Note: If desired, this directory structure may be maintained on the IBM WorkSpace On-Demand Server, instead of a separate Application Source Server. In this case, the directory structure must be created in the "\IBMLAN\RPL\BB10.US" directory of the IBM WorkSpace On-Demand server.

    2. CICS Access Control Profile Setup
      3.         [CICS Steps]

      Alias and access control profiles must be established:

      Notes:

      Alias:

    3. CICS Client Requesters
      4.         [CICS Steps]

      The IBM WorkSpace On-Demand client requesters must be established. This is best done via the LAN Server Graphical User Interface, but may be created via the "NET RIPLMACH ..." command line interface. The process that creates each requester also creates client specific FIT files and client specific work file directories on the IBM WorkSpace On-Demand RIPL server:

      \IBMLAN\RPLUSER\client_name
    4. CICS FIT File Updates
      5.   [CICS Steps]

      The following FIT alternatives were used during SSIT testing, but other alternatives are valid.

    5. CICS Application Definitions
      6.         [CICS Steps]

      The following application icons installed on a standard CICS OS/2 Client desktop were created as Network Applications on the IBM WorkSpace On-Demand client desktop.

    6. CICS Start
    7. CICS Stop
    8. CICS Terminal
    9. CICS Status
    10. CICS Internet Gateway
    11. CICS Printer
    12. CICS Client Messages
    13. CICS Clients Administration
    14. CICS Clients Gateway
      15. Notes:

      After the Applications are created they must be assigned to the "RPLGROUP" or to individual users, as required.

    4.4.4.2 Installation and Configuration of IBM Communication Server OS/2 Access Feature V5.0

    OVERVIEW:

    These instructions are based on the SSIT Lab's analysis of the IBM Communications Server OS/2 Access Feature Version 5.0 (from now on referred to as Access Feature) setup on an IBM WorkSpace On-Demand (WSOD) Client.

    The instructions are also based on Appendix B - Installing on a RIPL Workstation in the Communications Server V5 Quick Beginnings Manual. They utilize the following server configurations:

    Domain Controller
    On which the public application definitions are maintained.
    IBM WorkSpace On-Demand Server
    From which the Client machines are RIPL'ed. Client specific files are also stored and updated on the IBM WorkSpace On-Demand Server.
    Application Source Server
    Used to store the application specific binaries.

    Note: All of the above servers are required, but they may be all resident on the same physical machine.
    SETUP STEPS

    Following are the steps necessary to enable Access Feature:

    1. Access Feature Installation
    2. Access Feature Access Control Profile Setup
    3. Access Feature Client Requesters
    4. Access Feature FIT File Updates
    5. Access Feature Application Definitions
    1. Access Feature Installation  [Access Feature Steps]

      Install Access Feature on a Merlin Workstation in order to create the following directory structures and files required for the product. Then copy the directory/file structures to the Application Source Server:

      \CMLIB\-+\DLL | +-\EN_US\BOOK

      This is done by executing the following (with c: representing the client where Access Feature is installed and with x: representing the target application server):

      XCOPY C:\CMLIB\*.* X:\CMACC\CMLIB /S /E /V

      Note: This directory structure may be maintained on the IBM WorkSpace On-Demand Server, instead of on a separate Application Source Server. In this case, the directory structure would be created in the "\IBMLAN\RPL\BB10.US" directory of the IBM WorkSpace On-Demand server.

      Access Feature requires that certain device drivers are loaded during client system start. Because the client application code is on an Application Source Server, these device drivers have to be added to the IBM WorkSpace On-Demand Server. Therefore the following directory is created on the IBM WorkSpace On-Demand Server:

      \IBMLAN\RPL\BB10.US\CMLIB With c: representing the client where the Access Feature is installed and with x: representing the IBM WorkSpace On-Demand Server, the following files were copied: COPY C:\CMLIB\CMKFMDE.SYS X:\IBMLAN\RPL\BB10.US\CMLIB COPY C:\CMLIB\ACSLANDD.SYS X:\IBMLAN\RPL\BB10.US\CMLIB COPY C:\CMLIB\ACSHPRDD.SYS X:\IBMLAN\RPL\BB10.US\CMLIB

      Access Feature requires First Failure Support Technology (FFST) be installed once on the IBM WorkSpace On-Demand Server into the client operating system's directory tree. To achieve this, the following files were copied from the original Access Feature client to the IBM WorkSpace On-Demand Server. With c: representing the client where the Access Feature is installed and with x: representing the IBM WorkSpace On-Demand Server, the following files were copied:

      ; epw files copied to os2 directories COPY C:\OS2\EPW.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWCONS.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWDDR3.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWDF.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWDFOLD.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWICON.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWINST.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWMP.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWMUX.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWPCT.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWPSI.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWROUT.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\MSGLOGF.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\MSGWRT.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPW.MSG X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWH.MSG X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWFOLD.ICO X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\SYSLEVEL.EPW X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWDD.SYS X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWCUA.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWELG01.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWINIT.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWNL001.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPRO.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPROB.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPROB2.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPSI16.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPSI32.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWSVC16.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWSVC32.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWNL001.HLP X:\IBMLAN\RPL\BB10.US\OS2\HELP\*.* COPY C:\OS2\EPWDFOLD.EXE X:\IBMLAN\RPL\BB10.US\OS2\INSTALL\*.* COPY C:\OS2\EPWICON.EXE X:\IBMLAN\RPL\BB10.US\OS2\INSTALL\*.* COPY C:\OS2\EPWINST.EXE X:\IBMLAN\RPL\BB10.US\OS2\INSTALL\*.*
    2. Access Feature Access Control Profile Setup  [Access Feature Steps]

      Alias and access control profile(s) must be established:

      Notes:

      Alias:

      Note: The example above assumes that all client specific files will be stored on the Application Source Server in the following directory structure:

      \CMLIB--+ +--CLIENTS--+ +--client_name_1 | +--client_name_2

      However, if you elect to maintain client specific information on the Domain Controller (as is done in this application) the CMLIBCLI alias and access profile is not required.

    3. Access Feature Client Requesters  [Access Feature Steps]

      The IBM WorkSpace On-Demand client requesters must be created. This is best done via the LAN Server Graphical User Interface, but may be created via the "NET RIPLMACH ..." command line interface. The process that creates each requester also creates client specific FIT files and client specific work file directories on the IBM WorkSpace On-Demand Server:

      \IBMLAN\RPLUSER\client_name
    4. Access Feature FIT File Updates  [Access Feature Steps]

      The FIT table is used to map application file references to the physical location of the file. At least two options are available during setup. One stores the client specific files on the Application Source Server. The other stores client specific files on the IBM WorkSpace On-Demand Server.

      The following portion of a client FIT file maps all Access Feature "ini" files and log/trace output files to specific client directories on the IBM WorkSpace On-Demand server. This portion of the FIT file must be added to the end of the client FIT file created when the IBM WorkSpace On-Demand client is set up, in the \IBMLAN\RPL\FITS directory in the client_name.FIT file (for a specific client) or in the DFBB10US.FIT file (if all clients are to be enabled for Access Feature):

      ; ********************************************************** ; * Access Feature - read and read/write files ; ********************************************************** ; Following required for device driver files (see note below) Z:\CMLIB\*.SYS BB10.US\CMLIB ; Required to support FFST Z:\OS2\MSGLOGF.EXE BB10.US\OS2\MSGLOGF.EXE Z:\OS2\SYSLEVEL.EPW BB10.US\OS2\SYSLEVEL.EPW Z:\OS2\EPW.* BB10.US\OS2 Z:\OS2\DLL\EPW*.DLL BB10.US\OS2\DLL Z:\OS2\EPW\EPW* BB10.US\OS2\EPW Z:\OS2\HELP\EPW* BB10.US\OS2\HELP Z:\OS2\EPW.INI \\ripl_server\WRKFILES\client_name\OS2\EPW.INI Z:\OS2\EPW.!!! \\ripl_server\WRKFILES\client_name\OS2\EPW.!!! Z:\OS2\EPW.### \\ripl_server\WRKFILES\client_name\OS2\EPW.### Z:\OS2\VPD.INI \\ripl_server\WRKFILES\client_name\OS2\VPD.INI Z:\OS2\VPD.!!! \\ripl_server\WRKFILES\client_name\OS2\VPD.!!! Z:\OS2\VPD.### \\ripl_server\WRKFILES\client_name\OS2\VPD.### Z:\OS2\SYSTEM\LOG0001.DAT \\ripl_server\WRKFILES\client_name\OS2\SYSTEM\LOG0001.DAT Z:\OS2\SYSTEM\LOG0001.BAK \\ripl_server\WRKFILES\client_name\OS2\SYSTEM\LOG0001.BAK Z:\IBMCOM\RPL.INI \\ripl_server\WRKFILES\client_name\IBMCOM\RPL.INI Z:\IBMCOM\PROTOCOL.INI \\ripl_server\WRKFILES\client_name\IBMCOM\PROTOCOL.INI Z:\OS2\INSTALL\ZIP.ERR \\ripl_server\WRKFILES\client_name\CMLIB Z:\OS2\*.ICO \\ripl_server\WRKFILES\client_name\OS2 Z:\OS2\SYSTEM\*.DMP \\ripl_server\WRKFILES\client_name\OS2\SYSTEM Z:\OS2\SYSTEM\OS2MLOG.DAT \\ripl_server\WRKFILES\client_name\OS2\SYSTEM\OS2MLOG.DAT ; Following required to access the Access Feature binaries I:\CMLIB\ \\app_server\CMLIB\CMLIB ; Following required to update Access Feature client specific files I:\CMLIB\CMRI \\ripl_server\WRKFILES\client_name\CMLIB\CMRI I:\CMLIB\CM2.INI \\ripl_server\WRKFILES\client_name\CMLIB\CM2.INI I:\CMLIB\CM2.!!! \\ripl_server\WRKFILES\client_name\CMLIB\CM2.!!! I:\CMLIB\CM2.### \\ripl_server\WRKFILES\client_name\CMLIB\CM2.### I:\CMLIB\CM.LOG \\ripl_server\WRKFILES\client_name\CMLIB\CM.LOG I:\CMLIB\*.DAT \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\LOG$ \\ripl_server\WRKFILES\client_name\CMLIB\LOG$ I:\CMLIB\*.CFG \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\*.NDF \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\*.CF2 \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\*.SEC \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\*.LOG \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\*.ZZZ \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\*.000 \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\*.RSP \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\*.0$$ \\ripl_server\WRKFILES\client_name\CMLIB I:\CMLIB\NETWORK.INI \\ripl_server\WRKFILES\client_name\CMLIB\NETWORK.INI I:\CMLIB\LTCONFIG.WRK \\ripl_server\WRKFILES\client_name\CMLIB\LTCONFIG.WRK I:\CMLIB\CONFIG.SYS \\ripl_server\WRKFILES\client_name\CMLIB\CONFIG.SYS I:\CMLIB\ACSRASTD.INI \\ripl_server\WRKFILES\client_name\CMLIB\ACSRASTD.INI I:\CMLIB\ACSRASTD.!!! \\ripl_server\WRKFILES\client_name\CMLIB\ACSRASTD.!!! I:\CMLIB\ACSRASTD.### \\ripl_server\WRKFILES\client_name\CMLIB\ACSRASTD.### I:\CMLIB\CM.INI \\ripl_server\WRKFILES\client_name\CMLIB\CM.INI I:\CMLIB\ALRTNPDP.TXT \\ripl_server\WRKFILES\client_name\CMLIB\ALRTNPDP.TXT I:\CMLIB\SXSTART.CMD \\ripl_server\WRKFILES\client_name\CMLIB\SXSTART.CMD I:\CMLIB\ACSSXST.CMD \\ripl_server\WRKFILES\client_name\CMLIB\ACSSXST.CMD

      Note: The FIT file above assumes that the user specific files are maintained on the IBM WorkSpace On-Demand Server within the following directory structure:

      \IBMLAN\RPLUSER\--+--<client_name_1>\CMLIB | : +--<client_name_2>\CMLIB
    5. Access Feature Application Definitions  [Access Feature Steps]

      The following application icons installed on a standard Access Feature OS/2 Client desktop were created as Network Applications.

    6. Display Active Configurations
    7. Communications Server Information
    8. Replace Default Configuration
    9. Access Feature Setup
    10. Access Feature Start
    11. Access Feature Stop
    12. Access Feature Stop Abnormal
    13. Access Feature Subsystem Management

      14. Notes:

      After the Applications are created they must be assigned to the "RPLGROUP" or to individual users, as required.

      After successfully starting the IBM WorkSpace On-Demand clients, the "CM Setup" application must be executed to setup the Access Feature on the IBM WorkSpace On-Demand client. Alternatively, Access Feature Setup can be executed on a single client for all other client systems individually and the following configuration files copied to each client's \IBMLAN\RPLUSER\client_name\CMLIB directory.

      client_name.CFG client_name.CF2 client_name.NDF client_name.RSP client_name.SEC

    4.4.4.3 Installation and Configuration of IBM Universal Database OS/2 Client Application Enabler V5.0

    These instructions are based on the SSIT Lab's analysis of the IBM DB2 Client Application Enabler Version 5.0 (from now on referred to as DB2 CAE) setup on an IBM WorkSpace On-Demand (WSOD) Client.

    These instructions identify how to setup the DB2 Client Application Enabler Version 5.0 within the IBM WorkSpace On-Demand Manager environment in order to use a IBM WorkSpace On-Demand client supporting DB2 CAE as a network application.

    The SSIT lab setup and instructions utilize the following server configurations:

    Domain Controller
    Domain Controller on which the public application definitions are maintained.
    IBM WorkSpace On-Demand Server
    From which the Client machines are RIPL'ed.
    Application Source Server (i.e; "Additional Server")
    used to store the application specific binaries and user specific files.

    Note: All of the above servers are required, but they may be all resident on the same physical machine.

    SETUP STEPS

    Following are the steps necessary to establish DB2 CAE:

    1. DB2 Client Application Enabler Installation
    2. DB2 CAE Access Control Profile Setup
    3. DB2 CAE Client Requesters
    4. DB2 CAE FIT File Updates
    5. DB2 CAE Application definitions
    1. DB2 Client Application Enabler Installation  [DB2 Steps]

      Install DB2 CAE on a Merlin Workstation in order to create the following directory structures and files required for the product. Then copy the directory/file structures to the Application Source Server:

      \DB2CAE\--+-ODBC\[client_name]\ODBC | |-NETQOS2\[client_name]\DATA |-NETQOS2\{client_name[\WORK | |-SQLLIB\[client_name]\DB2 where [client_name] is the IBM WorkSpace On-Demand client name on which DB2 CAE is to be installed.

      DB2 CAE was installed on a Merlin Workstation and then the DB2 CAE binaries were copied to the Application Source Server. This was done by executing the following (with c: representing the client where DB2 CAE was installed and with x: representing the target application server):

      xcopy c:\odbc\*.* x:\db2cae\odbc /s /e /v xcopy c:\odbc\*.ini x:\db2cae\odbc\client_name\odbc /s /e /v xcopy c:\netqos2\*.* x:\db2cae\netqos2 /s /e /v xcopy c:\netqos2\data\*.* x:\db2cae\netqos2\client_name\data /s /e /v xcopy c:\netqos2\work\*.* x:\db2cae\netqos2\client_name\work /s /e /v xcopy c:\sqllib\*.* x:\db2cae\sqllib /s /e /v xcopy c:\sqllib\db2\*.* x:\db2cae\sqllib\client_name\db2 /s /e /v

      DB2 CAE requires First Failure Support Technology (FFST) be installed once on the IBM WorkSpace On-Demand Server into the client operating system's directory tree. To achieve this, the following files were copied from the original DB2 CAE client to the IBM WorkSpace On-Demand Server. With c: representing the client where DB2 CAE is installed and with x: representing the IBM WorkSpace On-Demand Server, the following files were copied:

      ; epw files copied to os2 directories COPY C:\OS2\EPW.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWCONS.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWDDR3.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWDF.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWDFOLD.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWICON.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWINST.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWMP.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWMUX.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWPCT.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWPSI.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWROUT.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\MSGLOGF.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\MSGWRT.EXE X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPW.MSG X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWH.MSG X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWFOLD.ICO X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\SYSLEVEL.EPW X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWDD.SYS X:\IBMLAN\RPL\BB10.US\OS2\*.* COPY C:\OS2\EPWCUA.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWELG01.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWINIT.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWNL001.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPRO.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPROB.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPROB2.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPSI16.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWPSI32.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWSVC16.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWSVC32.DLL X:\IBMLAN\RPL\BB10.US\OS2\DLL\*.* COPY C:\OS2\EPWNL001.HLP X:\IBMLAN\RPL\BB10.US\OS2\HELP\*.* COPY C:\OS2\EPWDFOLD.EXE X:\IBMLAN\RPL\BB10.US\OS2\INSTALL\*.* COPY C:\OS2\EPWICON.EXE X:\IBMLAN\RPL\BB10.US\OS2\INSTALL\*.* COPY C:\OS2\EPWINST.EXE X:\IBMLAN\RPL\BB10.US\OS2\INSTALL\*.*

    2. DB2 CAE Access Control Profile Setup  [DB2 Steps]

      An access control profile must be established:

      DB2CAE - utilized to access the DB2 CAE read/execute only files.

      Note: The example above assumes that all client specific files will be stored on the Application Source Server.

    3. DB2 CAE Client Requesters  [DB2 Steps]

      The IBM WorkSpace On-Demand client requesters must be created. This is best done via the LAN Server Graphical User Interface, but may be created via the "NET RIPLMACH ..." command line interface. The process that creates each requester also creates client specific FIT files and client specific work file directories on the IBM WorkSpace On-Demand RIPL server:

      \IBMLAN\RPLUSER\client_name

    4. DB2 CAE FIT File Updates  [DB2 Steps]

      The following FIT file maps all DB2 CAE "ini" files and log/trace and data output files to specific client directories on the Application Source Server, in the \IBMLAN\RPL\FITS directory in the client_name file:


      ; ********************************************************** ; * DB2 CAE - read/write files ; ********************************************************** ; Following required to access FFST Z:\OS2\MSGLOGF.EXE BB10.US\OS2\MSGLOGF.EXE Z:\OS2\SYSLEVEL.EPW BB10.US\OS2\SYSLEVEL.EPW Z:\OS2\EPW.* BB10.US\OS2 Z:\OS2\DLL\EPW*.DLL BB10.US\OS2\DLL Z:\OS2\EPW\EPW* BB10.US\OS2\EPW Z:\OS2\HELP\EPW* BB10.US\OS2\HELP Z:\OS2\EPW.INI \\ripl_server\WRKFILES\client_name\OS2\EPW.INI Z:\OS2\EPW.!!! \\ripl_server\WRKFILES\client_name\OS2\EPW.!!! Z:\OS2\EPW.### \\ripl_server\WRKFILES\client_name\OS2\EPW.### Z:\OS2\VPD.INI \\ripl_server\WRKFILES\client_name\OS2\VPD.INI Z:\OS2\VPD.!!! \\ripl_server\WRKFILES\client_name\OS2\VPD.!!! Z:\OS2\VPD.### \\ripl_server\WRKFILES\client_name\OS2\VPD.### Z:\OS2\SYSTEM\LOG0001.DAT \\ripl_server\WRKFILES\client_name\OS2\SYSTEM\LOG0001.DAT Z:\OS2\SYSTEM\LOG0001.BAK \\ripl_server\WRKFILES\client_name\OS2\SYSTEM\LOG0001.BAK Z:\IBMCOM\RPL.INI \\ripl_server\WRKFILES\client_name\IBMCOM\RPL.INI Z:\IBMCOM\PROTOCOL.INI \\ripl_server\WRKFILES\client_name\IBMCOM\PROTOCOL.INI Z:\OS2\*.ICO \\ripl_server\WRKFILES\client_name\OS2 Z:\OS2\SYSTEM\*.DMP \\ripl_server\WRKFILES\client_name\OS2\SYSTEM Z:\OS2\SYSTEM\OS2MLOG.DAT \\ripl_server\WRKFILES\client_name\OS2\SYSTEM\OS2MLOG.DAT ; Following required to access the DB2 CAE binaries H:\SQLLIB \\app_server\DB2CAE\SQLLIB H:\NETQOS2 \\app_server\DB2CAE\NETQOS2 ; Following required to update DB2 CAE client specific files H:\ODBC\*.ini \\app_server\DB2CAE\ODBC\client_name\ODBC H:\SQLLIB\*.log \\app_server\DB2CAE\SQLLIB\client_name\DB2 H:\SQLLIB\*.ini \\app_server\DB2CAE\SQLLIB\client_name\DB2 H:\SQLLIB\*.!!! \\app_server\DB2CAE\SQLLIB\client_name\DB2 H:\SQLLIB\BIN\*.log \\app_server\DB2CAE\SQLLIB\client_name\DB2\BIN H:\SQLLIB\BIN\*.ini \\app_server\DB2CAE\SQLLIB\client_name\DB2\BIN H:\SQLLIB\BIN\*.!!! \\app_server\DB2CAE\SQLLIB\client_name\DB2\BIN H:\SQLLIB\DB2 \\app_server\DB2CAE\SQLLIB\client_name\DB2 H:\NETQOS2\WORK\ \\app_server\DB2CAE\NETQOS2\client_name\WORK H:\NETQOS2\DATA\ \\app_server\DB2CAE\NETQOS2\client_name\DATA

      Note: The FIT file above assumes that the user specific files are maintained on the Application Source Server within the following directory structure:

      \DB2CAE\--+-ODBC\[client_name]\ODBC | |-NETQOS2\[client_name]\DATA |-NETQOS2\[client_name]\WORK | |-SQLLIB\[client_name]\DB2 where [client_name] is the actual IBM WorkSpace On-Demand client name.

    5. DB2 CAE Application Definitions  [DB2 Steps]

      The following application icons installed on a standard DB2 CAE OS/2 Client desktop were created as Network Applications on the IBM WorkSpace On-Demand client desktop.

    6. DB2 Alert Center
    7. DB2 Client Config
    8. DB2 Command
    9. DB2 Command Center
    10. DB2 Control Center
    11. DB2 Event Analyzer
    12. DB2 Info Center
    13. DB2 Journal
    14. DB2 Search Server
    15. DB2 Script Center
    16. DB2 Tools Settings

      17. Notes:

      Once the applications are defined then they must be assigned to the "RPLGROUP", or to individual users as required.

      4.4.4.4 Considerations for Lotus Notes OS/2 Client V4.51

      The installation instructions that were used by the SSIT lab to install and configure the Lotus Notes 4.51 client are the instructions that will be included in an updated version of the IBM WorkSpace On-Demand Handbook (SG24-2028) published by the IBM International Technical Support Organization.

      These instructions support the traditional features of the Notes Client such as mail, Notes database creation and access, etc. However, a test that the SSIT ran from the IBM WorkSpace On-Demand client was one which accessed an IBM Universal Database from the Notes client. This access requires the IBM Universal Database OS/2 Client Application Enabler be installed on the same system as the Notes client. It also requires access to ODBC from the Notes client. In order for access to ODBC to be enabled from the Notes client, the following additions must be made to the Notes public application:

      Redirection: H:DB2CAE Parameters: Name: DB2INSTANCE Value: DB2 Position: Beginning Name: DB2PATH Value: h:\sqllib Position: Beginning Name: LIB Value: ; Position: Beginning Name: LIBPATH Value: h:\odbc\drivers;h:\odbc\dll Position: Beginning Name: LIBPATH Value: h:\sqllib\dll;h:\sqllib\alt Position: End Name: ODBC_PATH Value: h:\odbc Position: Beginning Name: PATH Value: h:\odbc\bin; Position: Beginning Name: PATH Value: h:\sqllib\bin;h:\sqllib\alt Position: End Name: WSOD_LAUNCH_MINIMIZED Value: 1 Position: Beginning Name: WSOD_LAUNCH_NODROP Value: 1 Position: Beginning Notes:

      Public Application Definitions

      The Detailed Application Definitions section provides more information on application characteristics and additionally permits the download of files containing the command line calls necessary to establish the Network applications described within this document.

      Example of Configuring Adapters

      During the Integration test the "3Com Fast EtherLink/EtherLink XL Family OS/2" PCI adapter (3C90-TX) was utilized in several of the client machines. This adapter was not fully supported (i.e; the required nif files, protocol.ini's, map table entries, etc. were not part of the IBM WorkSpace On-Demand product release).

      In order to utilize this adapter it had to be configured and established within the IBM WorkSpace On-Demand environment. The Configuring Unsupported Adapter section documents the steps necessary to enable this adapter to work within an IBM WorkSpace On-Demand environment.

      Back to Contents

      SSIT Environment Configuration Matrix

      Current Test Configuration

      The hardware/software/Software Server configurations for this test are defined in the IBM WorkSpace On-Demand Configuration matrix.

      Back to Contents

      Scenario and Test Case Detail

      Scenario and test case detail resides in the AUSDB009 Lotus Notes database on a Lotus Domino server and can be accessed with the appropriate authority. Please contact your SSIT representative if access is denied and further information is required.

      Back to Contents

      Notices

      The information contained in this document is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. Customers attempting to adapt these techniques to their own environments do so at their own risk. IBM will accept no liability for consequences resulting from the use of this information.

      This report is to be used solely for the purpose of installing and supporting the product(s) discussed. This material must not be used for other purposes without the written consent of IBM. In addition, this material must not be redistributed outside your company.

      The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries. Those trademarks followed by an asterisk (*) are registered trademarks of the International Business Machines Corporation.

      The following terms are trademarks or registered trademarks of Microsoft Corporation.

      The following terms are trademarks or registered trademarks of Lotus Development Corporation.

      The following terms are trademarks or registered trademarks of Netscape Communications Corporation.

      The following terms are trademarks or registered trademarks of the 3Com Corporation.

      The following terms are trademarks or registered trademarks of the Digital Equipment Corporation

      The following terms are trademarks or registered trademarks of Intel Corporation

      Other company, product and service names may be trademarks of service marks of others.

      Back to Top