I just deployed my production from test to acceptance but I found that the deployment misses some Soap Webclient classes which are used by my business operation components. I have used the management portal to create the deployment (i.e. production settings -> Export) and I expected that all classes used by the production were automatically included. Apparantly, that is not the case. Is this default behaviour for Ensemble? And can I somehow force Ensemble to automatically include these classes?
I have a process in which i call a rest operation in a while loop, get a response in JSON format of 50 issues, with paging, meaning this call will happen until the total amount of issues will be returned. each JSON is parsed into a proxyObject, and inserted to a list. later the entire list will be sent to an SQL operation which will write the data in the appropriate tables.
When turning on the “Archive IO” option within the business operations, it provides us the capability of seeing the input and output communication with external systems. For instance, watching the messages sent out + ACK message sent back .
Our production has got a scheduled task that runs daily (by default I guess, as many others) and is in charge of purging “Errors and log files”. And this is likely to be linked to the “Archive IO” feature, right?
Is there a way to use a HL7 field value as part of the File Naming in the Business Operation FileOperation class. I know we can do this in a custom class, but I was wondering if it could be done the default FileOperation class?
Example:
MSH-4 contains the value 12345
We would like to name the file 12345_YYYYMMDDHHMMSS.HL7
MSH.4 value here_%Y%m%d%H%M%S.HL7
It may not be possible, but I just want to see if anyone has any information
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...
I am wondering if there any mechanism available in the Healhtshare where send a request from the service to the operation without storing the Data on CACHE.DAT?
My company going to receive ADT's and CCDA's from an external source (Hospital), The incoming data will have two kinds of patients, our patients, and not our patients. We do not want to keep the data on our servers of those patients that do not belongs to our company due to HIPPA complaint
Looking forward to hearing great ideas from this community.
Hi I'm hoping the community will once more help me out with a question!
Right I have a production that takes an attachment from an email and processes it, sending out a hl7 message at the end. This works ok.
Now I just need to take the email and send it back out to a 'backup' email address, basically giving a) A backup incase there is a problem with the email or something else further down the line. b) A log of the emails receieved.
So I thought the best thing to do is have an operation with an email adapter and to send that my message.
Call a web service to get an authorization key, comes back as a simple string
Create a request object with data from the HL7 message and send it to the Web Service
The main web method call requires that key I received as a Soap Header element. All I can pass to the SOAP Operation business class is the request object with the data I plucked from the HL7 payload. Nothing in that particular request message has anything in it that tells anything to send the header, too.
I have one Ensemble EnsLib.File.OutboundAdapter which has several methods, each writing a different file. In my Ensemble Production I have configured this FileAdapter to write to a certain directory, but i'd rather have each method write to a different (sub)directory instead of writing all files to the same directory. How can I achieve that without splitting the methods into different business operations?
The current code just sets the filename and the output:
I created Business Operation in my ENSDEMO namespace that will connect to an external REST endpoint to send data to this external REST Service.
I also created an http service in Home>Healthshare>Service Registry, under the Service Type: http. I entered the REST endpoint Name, Host, SSL Configuration, and URL.
My SOAP Operation is returning an error "ERROR ErrBusinessDispatchNameNotRegistered: Business dispatch name 'PKB_SOAP_Sender' is not registered to run"
maybe I am not looking in the correct spots, but how should one handle an Exception from a SOAP web service within the Business Process Language? For example I am sending a request to a Web Service to try to get information, but the response I am getting is an Exception like "Patient Not Found".
Is there a function I can call to check the response similar to what I do to check a SQL Snapshot to see if it is valued?
We're in the process of creating several courses for creating custom business components for productions. This includes custom business operations, BPL processes, and custom business services. Custom Business Operations and Custom Business Services are both aimed at software developers while BPL processes can be also be created by business analysts. What are some gotchas or best practices you've learned that you wish you knew when first building these components?
We'd love to include what you've learned into these courses so others can learn from them as well!
I have productions running in several different namespaces. They all use a common credentials ID for sending email, which is set up in only one of the namespaces. The documentation says that credentials are entered by namespace. When I ran a production in a second namespace, the error log said that credentials were not found (expected), but later attempts to send a file thorugh the production did successfully send an email. I'm wondering if Ensemble is able to look in other namespaces for the same credentials ID?
By update
