Using the OpenNLP pear described in the DUCC sample app, this would be a UIMA-AS deployment descriptor, Deploy_OpenNLP.xml: <?xml version="1.0" encoding="UTF-8"?>
<analysisEngineDeploymentDescription xmlns="http://uima.apache.org/resourceSpecifier";> <name>OpenNLP Text Analyzer</name> <description>Deploys OpenNLP text analyzer.</description> <deployment protocol="jms" provider="activemq"> <service> <inputQueue endpoint="OpenNLP-service" brokerURL="${defaultBrokerURL}"/> <topDescriptor> <import location="opennlp.uima.OpenNlpTextAnalyzer_pear.xml"/> </topDescriptor> </service> </deployment> </analysisEngineDeploymentDescription> This descriptor assumes it is in the same directory as the pear descriptor in the import statement. Then, assuming the service is to be deployed from the same directory, that UIMA_HOME and PATH have been updated for the UIMA-AS SDK, and a JMS broker started with startBroker.sh, the command would be: UIMA_CLASSPATH=`pwd`/lib deployAsyncService.sh Deploy_OpenNLP.xml On Wed, Feb 12, 2014 at 3:53 PM, Bai Shen <[email protected]> wrote: > That would explain why it's not working. :) What command should I use to > deploy my pear? > > The documentation talks about merging, packaging, and installing the pear, > but I can't find any mention about deploying it. > > Is there a specific section that I should be looking at? > > Thanks. > > > On Wed, Feb 12, 2014 at 3:09 PM, Eddie Epstein <[email protected]> > wrote: > > > A pear is a packed UIMA analysis engine, or AE. UIMA-AS deploys services > > that contain AEs. The command deployAsyncService requires a UIMA-AS > > Deployment Descriptor. > > > > > > On Wed, Feb 12, 2014 at 10:52 AM, Bai Shen <[email protected]> > > wrote: > > > > > I'm running the following command to deploy my pear to UIMA-AS 2.4.2. > > > > > > deployAsyncService.sh test_pear.xml -brokerURL tcp://uima-broker:61616 > > > > > > I'm getting the following error. > > > > > > SEPM0004: When 'standalone' or 'doctype-system' is specified, the > > document > > > must be > > > well-formed; but this document contains a top-level text node > > > > > > It's a saxon error, but I can't tell what causing it. Any suggestions > > for > > > where to look? > > > > > > Thanks. > > > > > >
