相关文章推荐
挂过科的企鹅  ·  LBound 函数 (Visual ...·  7 小时前    · 
仗义的凉茶  ·  【转】Spark ...·  11 月前    · 
苦恼的手套  ·  ESLint报错:Parsing ...·  1 年前    · 

To return expected results, you can:

  • Reduce the number of search terms. Each term you use focuses the search further.
  • Check your spelling. A single misspelled or incorrectly typed term can change your result.
  • Try substituting synonyms for your original terms. For example, instead of searching for "java classes", try "java training"
  • Did you search for an IBM acquired or sold product ? If so, follow the appropriate link below to find the content you need.
  • The Progress driver sends the request includes the "Accept-Encoding" header, which is set to "gzip, x-gzip, deflate". More information available here:
    When testing in Postman, it appears that when "x-gzip" header is included, the response from the Oracle Fusion endpoint causes a JSON response issue. Meaning, the driver attempts to parse the JSON response, but fails due to the data "'\u001F' at row 0, column 1, offset 1".
    Oracle imply that they support this type of encoding, (“The API Gateway supports HTTP content encoding for the gzip and deflate compressed content encodings”), so therefore this is an issue that should be raised to the datasource endpoint, in this case, Oracle Fusion team.
    https://docs.oracle.com/cd/E50612_01/doc.11122/user_guide/content/common_compress_encoding.html
    [{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTSF6","label":"IBM Cognos Analytics"},"ARM Category":[{"code":"a8m50000000Cl6nAAC","label":"Data Source"}],"ARM Case Number":"TS009886499","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]