Howto solve SoapUI scaling issues on a high DPI screen of a Windows 10 machine

I was fed up with SoapUI high dpi issues with my Dell XPS15 on Windows 10.

This trick is what I picked up from the SmartBear Community:

First add a registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest (DWORD) to 1

Then add a manifest file next to your exe
SoapUI-5.2.1.exe.manifest

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
    <description>eclipse</description>
    <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
        <security>
            <requestedPrivileges>
                <requestedExecutionLevel xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3"
                               level="asInvoker"
                               ms_asmv3:uiAccess="false">
                </requestedExecutionLevel>
            </requestedPrivileges>
        </security>
    </trustInfo>
    <asmv3:application>
        <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
            <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</ms_windowsSettings:dpiAware>
        </asmv3:windowsSettings>
    </asmv3:application>
</assembly>

Invoking a OAuth2 REST API with the TIBCO BusinessWorks 5.x plug-in for REST and JSON

In this post I will show you some pointers on how to invoke a OAuth2.0 REST service with the TIBCO ActiveMatrix BusinessWorks plug-in for REST and JSON plugged into TIBCOActiveMatrix BusinessWorks™. OAuth2.0 is an authorization framework that enables applications to obtain limited access to user accounts on an HTTP service, such as Facebook, GitHub, Google, Twitter and Trakt.tv. It works by delegating user authentication to the service that hosts the user account, and authorizing third-party applications to access the user account.

For this demo I'm using the Trakt.tv add-to-watchlist API. Trakt.tv is a website that collects lots of interesting information about what TV shows and movies that everyone is watching by scrobbling media players or by manual input from its users. They've exposed their movie watchlist capabilities with their OAuth secured API.

General process definition

The REST and JSON plug-in allows you to invoke RESTful Web Service APIs and translate data between JSON format and XML format (and vice versa) very easily. In this demo, the source of the movie watchlist data comes from my IMDB watchlist which I exported to a CSV file using the export web tool.

The simple BW Process Definition flow:

• Parse Data - Use a Data Format shared resource to be able to parse the data from the file. 
• Map Data - Use this to prepare for JSON rendering. You can also use a XSD generated from a sample JSON tekst using the "Generate XML schema from JSON" tool.
• Render JSON - Render the XML output from Map Data to JSON format.
• Invoke REST API - invoke the Trakt.tv API using the JSON data as the payload.
  

JSON conversion

The XML output from Map Data will be converted to JSON using the the Render JSON activity. Looking at the Input Editor config, the chosen cardinality of movies and shows might look odd but this is the only way to get a proper JSON rendering.

The output of Render JSON will be like in below image. You can see three movies and two TV series (shows).

Invoke REST API using OAuth2.0

Obtaining the Access Token

This part can be a bit tricky. You can for example write your own oauth client program using libraries from Google or some other open source initiative. Or you can follow the manual approach below:

1. First, create a client_id and client_secret by registering a Trakt.tv app. Click here for some helpful links to get you started.
2. Grab the code parameter value which you need to obtain from your Trakt.tv app redirect url querystring. You will use this in step 3.
3. Open SoapUI (by SmartBear) and use the Access Token Retrieval tool. Fill in the obtained code from step 2 in the Client Identification field. The Redirect URI could be the same as what you have used in Step 1. For OAuth 2 Flow, choose Implicit Grant as we don't need web browser interaction. After you have clicked Get Access Token button, a access_token should be presented to you.

Configure the Invoke REST API activity

Make sure to leave Protocol to None. Add the Resourc URI which you can get from the Trakt API page. 

Add two header fields: trakt-api-version and trakt-api-key.

Finalize the input mapping. The OAuth2TokenValue is the Access Token we just obtained.

Final

After running the process, the Invoke REST API activity should output something like this:

Go to your Trakt.tv Watchlist page (http://trakt.tv/users/[username]/watchlist) to see the result:

Happy watching!