Installing IBM Engineering Workflow Management Shell

Engineering Workflow Management Shell is distributed as a downloadable file through IBM® Installation Manager.

Before you begin

  • Engineering Workflow Management Shell requires Microsoft Visual C++ 2022 x64 Redistributable package or later for 64-bit systems. The .NET Framework 4.7.2 is also required. The supported operating systems are Windows 10 (64-bit) and Windows 11.
  • Ensure that you have Microsoft Edge Chromium Evergreen Runtime installed on your machine. You can install the most recent Microsoft Edge Chromium Evergreen Runtime from here.
  • Start this task with an empty sandbox.
  • You must have administrator privileges to run the launchpad.
  • To run the web installation, an Internet connection is required.
Note:
  • Windows 10 (all editions) includes the .NET Framework 4.6 and Windows 11 includes the .NET Framework 4.8 as an OS component and it is installed by default.
  • When you are facing any issue with Microsoft Edge WebView2 Runtime installation, check whether you have any previous versions of Microsoft Edge WebView2 Runtime that are downloaded by Windows Update, which are pending installation. If so, install those updates first before installing the Microsoft Edge WebView2 Runtime through the evergreen installer.

Procedure

  1. Download the following installation package. There are three methods to install the Engineering Workflow Management Shell:
    • Client CD Contents .zip file - IBM Installation Manager local install for client: This archive file contains the IBM Installation Manager launchpad and a local copy of the Engineering Workflow Management Shell. The benefit of using the local installation package is that it allows the installation to proceed without an Internet connection. This is a .zip file that is not self-extracting.
    • IBM Installation Manager web installation for client, server, and optional components: This archive file contains the IBM Installation Manager launchpad program and the predefined installation repository locations. The file is self-extracting file. After it extracts the contents, the file starts the IBM Installation Manager launchpad program. If you use the web installation package, the initial download is reduced, and the installation process downloads only the resources that you choose to install.
    • Full DVD Contents .zip file: This archive file contains the IBM Installation Manager launchpad and a local copy of all the installable resources. The benefit of using the local install package is that it allows the installation to proceed without an Internet connection. This is a .zip file that is not self-extracting.
  2. Optional: Open a command prompt and change to the directory where you extracted the .zip file to, and enter launchpad.
  3. Click Install client tools.
  4. Click IBM Engineering Workflow Management - Windows Shell.
    The IBM Installation Manager wizard opens. Follow the instructions in the wizard to install the client.
  5. Connect to the server by using the Team Invitation. If you do not have an invitation, you can connect manually.
    • To connect to the server by using a team invitation:
    1. On the Engineering Workflow Management Shell Control Panel page, click Accept team invitation. The wizard guides you through the process.
    2. Follow the instructions in the wizard to set up your connection.
    • To connect to the server manually:
    1. Ask your server administrator for the URI or URL of the server, such as https://example.com:9443/jazz.
    2. On the Engineering Workflow Management Control Panel page, click Accept team invitation.
    3. In the Accept Team Invitation window, click the connecting to an existing project area link and follow the instructions in the wizard to set up your connection.
    Note: Engineering Workflow Management supports TLS v1.2 and TLS v1.3, you can change the TLS configuration from the Engineering Workflow Management Shell preferences.

Example

Troubleshooting: If problems occur when you try to install Engineering Workflow Management Shell, try these problem management techniques:
  • Check that the client and server versions match.
  • Check that the server is running. You can confirm that the server is running by using the status URL. For example, https://example.com:9443/jts.