I'm doing a REST service for integration between 2 systems. The system that invokes me expects a response object where only one of its attributes changes. It could be something like this:
We are trying to feed in HTTP request & get HTTP Response in ensemble production.
From the below link we got the code for HTTP Request/Response Example. while executing the code we are getting following error: "ERROR <Ens>ErrFailureTimeout: FailureTimeout of 30 seconds exceeded in Test.HTTP.Operation; status from last attempt was ERROR #5922: Timed out waiting for response"
In our last lesson, we implemented a linkage to our WidgetAccessory class, and debugged some errors we encountered along the way. We now have our data being returned by REST, but what if we want to update or add new data to our application?
We left our application over the weekend, secure in the knowledge that it was returning data from our primary persistent class, User.Widget. However, Widgets Direct are the premier supplier of both Widgets AND Widget Accessories, so we should really start working on adding these Accessories to our application.
In SOAP Wizard, whatever WSDL I pass, I m getting the following error in the SOAP Response. Even If I create my own SOAP Web-Service and pass its WSDL, I am getting the same.
Hi - I created a custom extension to the SDA3 Allergy class, but can't figure out how to access the actual data to plug it into the SDA in the OnAllergy method.
The method (in my extension of the HL7ToSDA class) has a method like this:
I am trying to generate a custom error-code using the following code
Class ISG.CommonBilling.Service.Test1 Extends EnsLib.HL7.Operation.TCPOperation
{
ClassMethod khalid() As %Status
{
Set tSC=$$$ERROR("10001","I am here")
write $$$GETERRORCODE(tSC)_$char(13,10)
write $SYSTEM.Status.GetErrorText(tSC)
}
}
During a Caché system management training course today we discussed structural database integrity (a.k.a. physical integrity) and the tools InterSystems provides for checking integrity and fixing problems.
is it possible to ZW variables in stack frames above the current one? I am calling a custom logging method, and would like to log variables from the point of call.
Cache Studio's inspector window can show me a Cache class's properties,methods parameters, XDATA blocks, Triggers, Foreign Keys, Queries and more, in a table in the Inspector window. Additionally, for properties, where the property accepts parameters, these parameters are listed together with possible value choices.
I am facing an issue after upgrading from Ensemble version 2015.1 to 2017.1. On 2015.1, I was testing a Rest operation using a https mock-server. But now on 2017.1, the same Rest operation throws me the following exception on testing...
In HealthShare clinician user specifications (as well as in the the clinical viewer), there are locations for specifying "proxy" user(s), but there doesn't seem to be anything in any of the documentation that explains what this actually means/enables.
Is there any methods/ways through which will get to know whether any of the Unit Test cases is/are failing in the Terminal with status as either 0 or False in case of Failure & 1 or Ture in case of Test Passes (we are getting an url of the csp page with the report which has the passed failed status) as we need to send this failure status to Jenkins for the Build to Fail (where in we have acheived this part in making the build failure/success based on harcoded boolean)
i have a problem with the "ExecuteUpdateParmArray()" methode from the "EnsLib.SQL.OutboundAdapter" adaptater when i try to update a sql server 2008 table with JDBC connection.
I need to execute a single csession command which calls a multi-parameter routine, such as ^SECURITY. This will be to do things such as create databases, resources, etc. (see below). When I run the command all at once, I get a PARAMETER error.
Today I helped someone solve a mystery. He had been trying to use the -U namespace argument of a csession command to specify the namespace in which to run a particular routine, and was puzzled when the routine could not be found.