So strange query. But anyway if you want to get double single quotes, should double each one. So, it should be ''''

Something like this.

Call USER.SP('select * from Sample.Person where SSN=''''aaaaa'''' ','0','S')

Very simple way to check is everything configured well. Just open this url in any browser.

http://localhost:[port]/api/atelier/

It should return some JSON

If it does not work, you should look at Apache configuration.

Can you put here your apache config file?

Just for debugging, you can use this command

Do LOG^%ETN("some message")

It will collect all variables, on every stack level. And you can find this logs in SMP by  System > System Logs > View Application Error Log > Application Error Dates > Application Errors.

But be careful, this is only for debugging, because creating a log, may take a long time.

I would suggest that you working on frontend side in the browser, and call some REST API written in Caché or not, it does not matter. So, your code in JavaScript.

var data = getDateFromRest(); // you got some data from server, no so matter how you did it.

I suggest that your data is array, so, you could use map function and it contains something like this [{ "title": "car", "currency": "USD", "cost": "10000" }]

var newData = data.map(el => { return { name: el.title, value: el.cost + el.currency } })

will give you new array [{ "name": "car", "value": "10000USD" }]

I have not used UnitTests before but looks like, you can just analyze ^UnitTest.Result global, by latest index.

USER>set sc=##class(%UnitTest.Manager).DebugRunTestCase("", "MyPackage.Tests","","TestAdd")

===============================================================================
Directory: /opt/cache/dev/tutorials/UnitTestEx/
===============================================================================
  (root) begins ...
    MyPackage.Tests begins ...
      TestAdd() begins ...
        AssertEquals:Test Add(2,2)=4 (passed)
AssertNotEquals:Test Add(2,2)'=5 (failed)  <<==== **FAILED**
(root):MyPackage.Tests:TestAdd:
        LogMessage:Duration of execution: .000045 sec.
      TestAdd failed
    MyPackage.Tests failed
  Skipping deleting classes
  (root) failed

Use the following URL to view the result:
http://192.168.56.140:57774/csp/sys/%25UnitTest.Portal.Indices.cls?Index=5&$NAMESPACE=USER
Some tests FAILED in suites:

USER>zw ^UnitTest.Result(^UnitTest.Result)
^UnitTest.Result(5)=$lb("2017-05-31 12:08:01",.0013,"MacBook-Pro.local","CACHE","Cache for UNIX (Apple Mac OS X for x86-64) 2016.2 (Build 736U) Fri Sep 30 2016 11:56:58 EDT","USER","","")
^UnitTest.Result(5,"(root)")=$lb(0,.001218,"","There are failed TestCases")
^UnitTest.Result(5,"(root)","MyPackage.Tests")=$lb(0,.000554,"","There are failed TestMethods")
^UnitTest.Result(5,"(root)","MyPackage.Tests","TestAdd")=$lb(0,.000045,"","There are failed TestAsserts")
^UnitTest.Result(5,"(root)","MyPackage.Tests","TestAdd",1)=$lb(1,"AssertEquals","Test Add(2,2)=4")
^UnitTest.Result(5,"(root)","MyPackage.Tests","TestAdd",2)=$lb(0,"AssertNotEquals","Test Add(2,2)'=5")
^UnitTest.Result(5,"(root)","MyPackage.Tests","TestAdd",3)=$lb(1,"LogMessage","Duration of execution: .000045 sec.")

I think from this global, will be quite easy to extract needed information to any format.

I don't know how you call Caché method from Jenkins, but anyway you can use $SYSTEM.Process.Terminate in Caché script to exit with an exit status. Something like this.

set tSC=##class(%UnitTest.Manager).DebugRunTestCase(....)
if 'tSC do $SYSTEM.Process.Terminate(,1)
halt

I suggest that you may use csession or cterm to call Caché code, then you should get exit code and send it to Jenkins, which will be recognized by Jenkins as an error and will fail the job.

I would give you a list from fastest to slowest.

• Local variables. Yes, this sort of variables is limited by memory, but currently, memory cost not so much and if you need only 1GB per server, it should be quite easy to get. By default, the process has only 256MB of memory for local variables, but you can extend it on a fly with special variable $zstorage, and maximum level is 2TB.
• Process private globals (^||Global), it is already globals but works faster than any other types of globals, but slower than local variables. It is not limited by memory per process, but stored in memory, and could be moved to the disk if you exceed global buffer size.
• Globals mapped to CACHETEMP (e.g. ^CacheTemp*, ^mtmp), such globals faster than usual globals because in this database journaling of any changes is switched off. 
• Every other Globals, but still depends on is this database used journaling changes or if changes were made in a transaction.