Starting StreamBase Studio on macOS Sierra

Important

The workarounds described on this page apply ONLY to TIBCO StreamBase release 10.3.x and earlier.

On TIBCO Streaming 10.4 and later, you can double-click to open the StreamBase Studio and StreamBase Manager icons normally.

Introduction

MacOS releases 10.12 Sierra and later have a security model that is stricter than previous releases. As part of their security model, these releases automatically block unsigned, downloaded application bundles with .app extension from being able to run. The symptom is that you double-click an icon such as StreamBase Studio 10.3, and nothing happens.

Unfortunately, this issue affects the application bundles for StreamBase Studio 10.1 through 10.3 and StreamBase Manager 10.1 through 10.3.

Only on those StreamBase releases, you can use ONE of the options described in the next section to have StreamBase Studio and StreamBase Manager open normally in response to a double-click on macOS 10.12 Sierra and later.

Workarounds for StreamBase 10.1, 10.2, or 10.3

The double-click workarounds in this section are not required for StreamBase Studio or StreamBase Manager shipped as part of TIBCO Streaming 10.4+ or TIBCO Spotfire Data Streams 10.4+.

Remove the Quarantine Attribute

Note

This method is recommended because it only needs to be done once for each TIBCO Streaming installation. These steps must be repeated if you install a maintenance update or new release.

MacOS automatically flags downloaded application bundles that are unsigned, adding the extended attribute com.apple.quarantine. Removing this attribute allows you to double-click to run your application bundles normally. Use commands like the following.

  1. At a Terminal prompt, navigate to your StreamBase installation directory. For example:

    cd ~/Applications/TIBCO StreamBase 10.3.0
  2. Run the xattr command to display the extended attributes of the Studio .app bundle:

    xattr "StreamBase Studio 10.3.app"

    On a new installation, this returns:

    com.apple.FinderInfo
    com.apple.quarantine
  3. Run the following command to remove the quarantine attribute from Studio:

    sudo xattr -r -d com.apple.quarantine "StreamBase Studio 10.3.app"
  4. Re-run the xattr command from step 2 to see the results, which should be:

    com.apple.FinderInfo
  5. Next, remove the quarantine attribute from StreamBase Manager's .app bundle as well:

    sudo xattr -r -d com.apple.quarantine "StreamBase Manager 10.3.app"

Start Studio from a Shell Prompt

You can always start Studio from a Terminal shell prompt by typing:

sbstudio &

This command example presumes that you have configured your Terminal shell environment as described in the macOS section of the StreamBsae-Configured Shells page.

If you choose this option instead of removing the quarantine attribute, you must start Studio this way every time.

Start Studio from Inside the .app Bundle

You can start Studio by navigating into the application bundle:

  • In a Finder window, navigate to your StreamBase installation folder.

  • Right-click StreamBase Studio 10.3.app, and select Show Package Contents.

  • Navigate to Contents>MacOS.

  • Double-click sbstudio. (Do NOT run _sbstudio, the file whose name begins with an underscore.)

If you choose this option instead of removing the quarantine attribute, you must start Studio this way every time.

Restore the Pre-Sierra Security Model

Note

This method is not recommended because it opens your Mac to safety issues from downloaded apps and utilities from other vendors.

You can return your macOS installation to the way applications launched before macOS 10.12 Sierra. Doing this restores the Anywhere option for the Allow apps downloaded from section of the Security and Privacy control panel.

To do this, run the following command:

sudo spctl --master-disable

If you have already tried to run Studio by double-clicking its app bundle icon, then you must still remove its quarantine flag as described above in Remove the Quarantine Attribute.

To reverse this setting and return to the as-shipped Sierra or High Sierra security model, run:

sudo spctl --master-enable