Neither the Getting Started [2] nor the UIMA AS user manual [3] cover the practicalities of deploying asynchronous pipelines, so I'm relying on the README that comes with uima-as-2.3.1-bin.tar.gz. If there is a better document to work from, please let me know :-) UIMA is my first exposure to a Big Java Framework, so my knowledge & intuitions about it are not deep.
It looks to me as if there are two basic patterns:
(1) start the broker ('startBroker.sh'), and then
(2) use 'runRemoteAsyncAE.sh' to both connect the CR with the queue via the '-c'
argument and to deploy the AS AEs via the '-d' flag; or
(1) start the broker ('startBroker.sh');
(2) deploy one or more instances of the AS AE with 'deployAsyncService.sh', and
then
(3) use 'runRemoteAsyncAE.sh' to both connect the CR with the queue via the '-c'
argument.
Do I have this right?One challenge we face is that some essential third-part components are not thread-safe, and so it looks to me as if I'll have to scale out instances of those components by deploying them in their own JVMs and not by means of a single deployment with
<scaleout numberOfInstances="20"/> in the deployment descriptor. Thanks for any pointers; I have more questions to follow up with :-)[1] <https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/OHNLP_Documentation_and_Downloads>
[2] <http://uima.apache.org/doc-uimaas-what.html> [3] <http://uima.apache.org/d/uima-as-2.3.1/uima_async_scaleout.html> -- Chuck Bearden Programmer Analyst IV The University of Texas Health Science Center at Houston School of Biomedical Informatics Email: charles.f.bear...@uth.tmc.edu Phone: 713.500.9672
smime.p7s
Description: S/MIME Cryptographic Signature
