Return-Path: 
 <user-return-6010-apmail-uima-user-archive=uima.apache.org@uima.apache.org>
X-Original-To: apmail-uima-user-archive@www.apache.org
Delivered-To: apmail-uima-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C8730117E8
	for <apmail-uima-user-archive@www.apache.org>;
 Thu, 31 Jul 2014 13:02:45 +0000 (UTC)
Received: (qmail 10097 invoked by uid 500); 31 Jul 2014 13:02:45 -0000
Delivered-To: apmail-uima-user-archive@uima.apache.org
Received: (qmail 10056 invoked by uid 500); 31 Jul 2014 13:02:45 -0000
Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@uima.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@uima.apache.org>
List-Post: <mailto:user@uima.apache.org>
List-Id: <user.uima.apache.org>
Reply-To: user@uima.apache.org
Delivered-To: mailing list user@uima.apache.org
Received: (qmail 10043 invoked by uid 99); 31 Jul 2014 13:02:45 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2014 13:02:45 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of burnlewis@gmail.com
 designates 209.85.214.174 as permitted sender)
Received: from [209.85.214.174] (HELO mail-ob0-f174.google.com)
 (209.85.214.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2014 13:02:39 +0000
Received: by mail-ob0-f174.google.com with SMTP id vb8so1513815obc.19
        for <user@uima.apache.org>; Thu, 31 Jul 2014 06:02:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=EmMSBm4HV0acUoR4u2v0zlWKDRj4YVe7VPgTnHHVjqg=;
        b=fDtrCnwRDsJuHJ+y+lPu/doXJV7WlTwOAXcwbXChL9XhQ9z5kQZjb7aPVJpp9cD1kX
         VQ4CJGBavJkfNEsVDBB7ja64MU2iyLdA+41iPuWZUTeBYWv8d0RgZnldHtST3c7Htm9E
         RR0FX/lTun+zb5Lzaivnxr6SQTCT4lgEmonO0YOMt2xTfbyx9mhxBTK67lastxfvcAs8
         81zsEScQDgTym//tLjxEC9jhjzWv2D5ZXSEis1v7Ml/lgRI0nlpGEslo6TZtTwasWYQY
         ZZmZOmwcer8TC43u9np7oogJrKNkKzV2DGVf6GyuNFSHDGT2wP+Y+oetFgLj3g+t9IwD
         MG2w==
MIME-Version: 1.0
X-Received: by 10.182.246.232 with SMTP id xz8mr5948615obc.5.1406811737700;
 Thu, 31 Jul 2014 06:02:17 -0700 (PDT)
Received: by 10.60.171.203 with HTTP; Thu, 31 Jul 2014 06:02:17 -0700 (PDT)
In-Reply-To: <loom.20140731T050356-160@post.gmane.org>
References: <loom.20140731T030400-681@post.gmane.org>
	<loom.20140731T050356-160@post.gmane.org>
Date: Thu, 31 Jul 2014 09:02:17 -0400
Message-ID: 
 <CA+U9pLu8GRuTMwAhpSN-n72wQ2LWuVZP1O0XtzePOic16kh73A@mail.gmail.com>
Subject: Re: Deploy entire uima as service in multiple nodes
From: Burn Lewis <burnlewis@gmail.com>
To: user@uima.apache.org
Content-Type: multipart/alternative; boundary=001a11c1c39ee43f4204ff7ce1f3
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c1c39ee43f4204ff7ce1f3
Content-Type: text/plain; charset=UTF-8

Yes, sounds correct.  You can also get "in-process" scaleout on a
multi-core machine by asking UIMA-AS to create multiple instances of your
AE (assuming it is thread-safe) , e.g. <scaleout numberOfInstances="8"/>
If you use jconsole to monitor the broker to verify the number of
consumers, note that UIMA-AS creates 1 extra listener per deployment, for a
total of 9 per deployment in this example.

~Burn


On Wed, Jul 30, 2014 at 11:09 PM, Swirl <lriwswirl@gmail.com> wrote:

> Swirl <lriwswirl@...> writes:
>
> >
> > Hi,
> > I am trying to use Uima AS to deploy one of my UIMA Aggregate AE.
> > I wish to deploy it as a Uima AS Primitive, i.e. I do not need the
> delegates
> > of this AE to be scaled out. Instead I just want to scale out the Uima
> > aggregate AE only. I want to deploy the AE in multiple nodes.
> >
>
>
> OK, some answers from myself...
>
> I simply copy all required jars (of my AE) and descriptors to all machines
> that I want the AE deployed.
> I start the broker on one of the machines (it should be possible to use a
> dedicated machine to act as the broker).
> I do a "deployAsyncService" on all the machines, specifying the "brokerURL"
> as tcp://<brokerMachine>:61616.
>
>
> To test, I do "runRemoteAsyncAE" on a separate machine containing the input
> files to be passed to the AE, again specifying the "brokerURL" as
> tcp://<brokerMachine>:61616.
>
> From my logs on all the machines, I can see that some CASes are distributed
> to all the machines with the deployed services.
>
> Are the above steps correct?
>
>

--001a11c1c39ee43f4204ff7ce1f3--