You can use Ens.Response class for an empty response and you need to init it:
Method OnMessage(request As Ens.StreamContainer, Output response As Ens.Response) As %Status
{
set response = ##class(Ens.Response).%New()
quit $$$OK
}If you only want to see streams why not use <trace> in BP?
Postconditionals are to be used only for the most simple checks, for example:
set:a="" a=10
instead of
if a="" {
set a=10
}But several conditions (or several lines inside) should be as if, I agree.
For one-line if I prefer postconditionals:
set:a b=a
As for For - the option with braces. It's more readable. And one line inside For loop quickly and often becomes several lines, so braces become mandatory anyway.
Why do you need to check it at runtime? If source and target are from different but related classes you can copy by their common ancestor (or by specified ancestor class). Or do you copy properties between two unrelated classes?
Nice example of using method generators.
Why do you need ExistsProperty? Here's a check I usually employ for class properties in generators:
if prop.Internal || prop.Calculated || prop.ReadOnly || prop.Private || prop.Identity || prop.MultiDimensionalCONTINUE
It filters out all systems properties like Concurrency, %%OID and so on.
When talking about speed, one of the most important questions is what exactly do you need to speed up? You need to determine:
to fix it. Some ways to fix performance are (easy to hard):
Because in your case I see at least two request types which require different actions to speed them up:
Versioning for example. Temporal queries and so on.
Header itself is another layer because it's meta information for the BPL state machine, which you're inside of. So I don't see how you can get header Id from inside the state machine without violating abstractions in place.
Still, %Context, %Process and %LastError are documented and acceptable to use.
You can access %Ensemble("%Process") as ..%Process so:
..%Process.%PrimaryRequestHeader.%Id()
Reference WebDAV implementation for Caché.
Why would you want to do that?
Here's sample production class:
Class Test.Production Extends Ens.Production
{
XData ProductionDefinition
{
<Production Name="Test.Production" TestingEnabled="true" LogGeneralTraceEvents="true">
<Description></Description>
<ActorPoolSize>1</ActorPoolSize>
ion>
}
}Ens.Config.Production serialized is XData ProductionDefinition and not the class itself.
To create production class automatically you need to:
Check out Caché FileServer project for a sample of file upload/download.
Use any of the existing Git hooks for Studio or Atelier. They would work with GitHub and GitLab both.
Check EvaluateRules method of Ens.Rule.Definition class. It evaluates rule by name and context. You can call it from Studio or Terminal.
Got it. Usually after enabling HTTPS I add server-wide redirect from HTTP to HTTPS. So in cube I specify port 80 and it automatically redirects to HTTPS.
HTTPS access is implemented and easily configurable.
If Caché does not work through IIS, you need to configure it. On Windows you can configure Caché to work with IIS, Apache or Nginx.
After you have configured the web server to work with Caché, add https support. For example use Let's encrypt as a CA.
Learning.intersystems.com has a lot of courses you can access for free. They start right from the basics.
while i was using your code, i am getting this error in response, which says "read" method is unknown
You're getting this error because list of objects does not have this method. Check your list of objects for contents. Seems like json is already converted so you don't need to do that.
What do you mean?
If you have month and year just add 01 and produce the date.
For SQL, use LAST_DAY function - it's a date function that returns the date of the last day of the month for a date expression:
SELECTLAST_DAY('2004-02-25')
It's also available in Caché ObjectScript:
Write $SYSTEM.SQL.LASTDAY("2004-02-25")Convert json to proxy object (list of in your case) and iterate over it
set json = "[{""Name"":""bat""},{""Name"":""Cat""},{""Name"":""rat""},{""Name"":""mat""},{""Name"":""hat""},{""Name"":""chat""},{""Name"":""please""},{""Name"":""help""},{""Name"":""me""},{""Name"":""in""},{""Name"":""getting""},{""Name"":""the""},{""Name"":""value""},{""Name"":""of""},{""Name"":""nameFromObjectInsideArray""}]"
set sc = ##class(%ZEN.Auxiliary.jsonProvider).%ConvertJSONToObject(json,,.obj,1)
for i=1:1:obj.Count() {
write obj.GetAt(i).Name,!
}To get json string from request:
set json = %request.Content.Read($$$MaxStringLength)
You may also need to convert request into UTF8:
set json = $ZCVT(json,"I","UTF8")
Sorry I'm lost here. and not sure what you in 1,2 or 3 !?
It's an iterative process to pinpoint and remove errors. You start by establishing a channel which can send valid requests. For example using Postman. Next you compare valid request (which you can now consistently send) with your request which does not pass. Next you iteratively break valid request or fix failed request or send failed request via Postman. Sooner or later you understand what causes your request to fail and fix that.
the other difference is that Now they also require a Header, before they they only had a Body in their API.
You need to add all required headers via SetHeader method.
I think my date is already like that!? do you mean removing the double quotes or changing it to YYYY-DD-MM?
You're sending:
"PaymentRecordTransactionD":"PaymentRecordTransactionD"
But API expects:
PaymentRecordTransactionD": "2014-12-31"
Looks different for me.
The error says parse error, but in this case I think it means either datatype validation (probably) or fixed property order (less probable, but that can actually happen). My default advice in cases like this is as follows:
In your case the first modification I would do is replacing dates with real dates, for example with 2014-01-11.
Doubtful. Web browsers security policies probably forbid this kind of thing.
Why do you need that?
Well, yes, it returns the sender of the message. If you're sending message from BS to BO directly sender would be BS. If you're sending BS-BP-BO, for BO the sender would be BP because it is.
If you want to get BS from BO in BS-BP-BO you can implement it via several approaches:
I'd like to add that second approach without careful planning and optimizing may negatively impact performance if stored messages are in millions. Starting new SessionId for each new message sent from BS may help. (because BS MessageId would then be equal to SessionId in BO).
Use %RequestHeader property instead:
Set tSrcCfg = ..%RequestHeader.SourceConfigName
I think that's for services only. They store information about processed rows in: these 2 globals
$$$DoneRowTable(key) ^CacheTemp.Adapter.sqlrow(..BusinessHost.%ConfigName, ..%InstKey, key)
Where DoneRowTable macro is resolved into
^Ens.AppData(..BusinessHost.%ConfigName, "adapter.sqlrow", key)
You can check if there's anything for your BO.
The globals are set in OnTask method of inbound adapter.
What happens if you don't declare a Persistent value when you call ExecuteQuery()?
What is " Persistent value"?
What does Ensemble set as the key value for your query?
What is "key value"?
That said, if you execute the same query against external database, and the data in the external database does not change you should get the same results.
After you finish working with resultset the first time (and before creating it a second time) you can call:
Set sc = rs.Close()
Maybe that would help.