Hi @Aziz Cotrim,
Like @Robert Barbiaux pointed, the recommended way to handle long running calls outside the IRIS, is Deferred Responses.
 

Hi @Aziz Cotrim,

During development, to debug the entire BS->BP-BO integration flow, I set the INVOCATION parameter of both BP and BO to InProc. This way, execution occurs in the process that created the first message sent, in this case, BS.

I create a debugging routine or class method where I instantiate BS and continue debugging from there.

Below is a code snippet to start the debugging process from a BS.
 

ClassMethod Debug()
{
    Break
    #Dim bs As Ens.BusinessService = ""
    #Dim statuscode As %Status = ##Class(Ens.Director).CreateBusinessService("BS Name", .bs)
    If ($System.Status.IsError(statuCode))
    {
        Write "Error creating a BS instance: ", $System.Status.GetErrorText(statusCode)
        Return
    }
    Set statusCode = bs.ProcessInput(input, .output)
    If ($System.Status.IsError(statuCode))
    {
        Write "Error returned form ProcessInput method: ", $System.Status.GetErrorText(statusCode),  !
        Return
    }
}

For more information:
Invoking a Business Service Directly
Defining a Business Operation Class
 

Hi @Rodolfo Pscheidt Jr,

Create a GetMethod to return the value of the property and use it in the expression. 

Hi Alon,

Have you look at the Interopway XDBC. It's a module that I developed to support xDBC Integratoins, has examples of CRUD operations and call Stored Procedures.

Regards.

Hi @Scott Roth 

You can do in the BS, but in my opinion use the common approach sending a message from the BS to a BO. In the BO you insert the data into internal table, with this approach you have how to trace data if some error occur.

Hi Isayas,

You need to use TCP Client Server Communications (commands Open, Use, Read, Write) you can get information about this in the documentation https://docs.intersystems.com/iris20243/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_tcp.

In the OpenExchange exists a simple sample developed  by @Robert Cemper . Follow https://openexchange.intersystems.com/package/Simple-remote-server-control

Regards.

@maxime keltsma 

You can traverse the entire global with a loop and $Order function.

A simple routine to traverse your global can be:

Teste
    Set ^DataTest = 3
    Set ^DataTest(1) = $lb("","1329","JMMK-G1D6")
    Set ^DataTest(2) = $lb("","1516","AMEV-GVPF")
    Set ^DataTest(3) = $lb("","2333","4QC6-4HW3")
    Set key = ""
    // Print the header filds
    Write "Reference", $Char(9), "Code"	, !	
    For   
    {
        // first parameter is global and key, 
        // second parameter opredr to travers globa. 1 = ascending subscript order (the default) or –1 = descending
        // third is target that receives the value if the key is defined
        Set key = $Order(^DataTest(key),  1, data)
        If (key = "")
        {
            Quit // Exit for loop
        }
        Set reference = $ListGet(data, 2)
        Set code = $ListGet(data, 3)
        //
        Write reference, $Char(9), code, !
        
    }

Output o execution:

> Do Teste^Teste
> Reference Code
> 1329 JMMK-G1D6
> 1516 AMEV-GVPF
> 2333 4QC6-4HW3

See Using Globals Object Script Tutorial , $Order Function for more examples e details.

Hi William,

In SMP go to Interoperability->Interoperate->ASTM->ASTM Schemas Structures

Via Studio go to File->OpenFile, filter by AST Document "*.ast"