Disabling trace Events on an active Message Router requires the Router to be stoppen and started again. After That no trace events will be logged anymore. You also should have rule logging setting of Router in mind when doing so. When starting/stoppen the Message Router consider its pool size setting to avoid side effects such as stop of Ens.Actor queue.

Thanks for the hint, action "remove" didn´t work - switching to "clear" removes the field entirly.

best regards,
Sebastian

Hi,

you could also prepare the sql´s within an editor and in the SQL browser sqlect a dialect "MSSQL". The dialect field to choose from is only visible if you click the "more" button next to the max entries to return field.

Adter that you just place your inserts and you are good to go.

best regards,
sebastian

Hi Craig,

sry for the late response. Thank you this is what I was already thinking about. I´ve did some tests and the approach works for me. I´ve marked your as accepted.

Anyway I´am still highly interessted in InterSystems point of view on this.

best regards,

sebastian

Hi Craig,

thank you for your response. So first of all good to hear that I am not the only one with this kind of questions. I assume you don´t configured an OAuth Client via SMP directly but instead do the  invocation of the API endpoint to get the token directly in the operation - therefore you should not use any %OAuth... framework-functionalities from within the operation - am I correct?

It would be very interesting to here from InterSystems what would be the best practise here. Anyway this should work. Could you supply me with an example of how you implemented the GetBearerToken() method?

best regards,

sebastian

Thank you for that hint. Adding the xml schema definition to the studio-project would make transport to other system stages a lot more easier. One don´t need to remember where schemas are stored and doesn´t need to to organize schemas in seperated files floating around the file system. I guess I´ll end up adding the EnsEDI.XML.Schema global to my studio project. Thanks again for that hint.

Hi Robert,

my intention was to add the imported xsd schema to a studio project. However, I didn´t generated any classes explicitly. I´ve just imported a xsd schema in the management portal and expected (wich works fine) but expected to have xsd-schema availabe in studio just like with hl7-schema (*.HL7). So I guess there is no way for doing that directly and therefore I need to place the schema file in mit default csp location to be able to add it to a studio project. I see no other way to be able to have that schema to be available for comparision (diff).

kind regards,

sebastian

Hi Eduard,

already did this. the role %Developer should already include the %EnsRole ressources. Even assigning them to the created role manually gives me that error when logging in. Somehow as part of the login procedure, the cachelib db is accessed. Even if granting the ressources of cachelib the error remains.

kind regards,

sebastian