Hi!

We would like to retry message so that it's restored to end of operation's queue. This is in situation where order of messages is not needed to be handled by Ensemble, there is version number in message data and receiving application can ignore incoming message if necessary.

We would try to send message until it's accepted (or manually suspended), but this should not block operation's queue.

We have already this in actions:

D - Disable the Operation, log an error and restore the message to the front of the Operation's queue.

Would be nice to have one like this:

Q - Disable the Operation, log an error and restore the message to the END of the Operation's queue.

Best Regards

Mauri

Last answer 10 October 2018
0   0 2
0

comments

145

views

0

rating

Hello!
We want an Integration that should be moving files from a FTP server in a DMZ zone into another FTP server on our local network.
I tried using EnsLib.FTP.PassthroughService(EnsLib.FTP.InboundAdapter, EnsLib.FTP.OutboundAdapter)
Using this approach ensamble write data to the database, causing the CACHE.DAT to grow for every file that is moved.
Looks like the entire file is written to the database, is this the case?
We are not really interested in storing any file content information in ensamble in this particular case.
Does anyone has a good suggestion on how to accomplish the file transfer using ensamble with another approach/configuration or arguments on why this would be a bad idea in the first place?
Best regards,
Magnus

Last answer 5 October 2017 Last comment 4 October 2017
0   0 4
416

views

0

rating

Does anyone have a good example of setting up an Inbound Email Adapter Service to retrieve an email? I am thinking of sending this email to a BPL to retrieve the Attachment that is in the email. Would that be the correct method to do that?

Thanks

Scott Roth

The Ohio State University Wexner Medical Center

Last answer 3 May 2017
0   0 3
0

comments

214

views

0

rating

I'm asking this best-practices question on behalf of a customer.

They have a Caché-based application, and an Ensemble production deployed in front as an ESB to provide web service API access to the back end application. They're looking for a best practice approach for the scenario where the Caché back end is calling a third-party web service. Should that go through Ensemble too? It's sort of a philosophical design question/debate.

The current approach without going through Ensemble would be for Caché to import the service WSDL into proxy classes and invoke those directly from the application code. If the answer to the above question is yes (third-party WS calls SHOULD go through the ESB), what is the best way? One option would be to invoke a restful service in Ensemble from the Caché app. Another would be to expose a web service from Ensemble. That would mean both Ensemble and the back-end application would have to import a WSDL.

Thank you,

Steve

Last answer 1 May 2017
0   0 2
0

comments

237

views

0

rating