You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Sig Rinde <si...@rinde.com> on 2010/01/05 13:23:48 UTC
ESME in Thingamy - short report and a question
Hi everybody,
thanks to many members of this group, ESME now working nicely
inside/beside Thingamy using latest (untouched ;)) commit (Thanks
again Ethan, excellent and fast work!).
(Video coming, but have a flu/headachy thing today so head's too mushy)
In Thingamy:
- (our own) JS client incorporated using API2.
- Messages are tagged by one or more objects in Thingamy (tick box in
each object enables that).
- Messages are filtered by same method from tasks and/or reports.
- Multiple tags/relationships enabled - both adding and filtering, but
limited to the 50 last messages for now, need to include everything
(search?).
- Reply "button" in message client adds name (as in Twitter) in
response field and tags new message with same tags/relations.
- Enable/disable ESME for system in full and for each user role.
- Uses pools and names the pool by application name which is set in
Thingamy setup interface (under admin) allowing us to use one ESME
instance for multiple Thingamy instances.
- Messages also shows object(s) it's related to (cryptic name for now)
which are links to a graph display of the object and all it's
relations to other Thingamy objects.
ESME server:
- Adding one line to default.props to set admin user
- Sign up as that user
- Create a token, that's all
- In Thingamy setup one sets the application name (names pool) and add
the token.
- When adding users to Thingamy each will (tick box to enable) be
allocated a token and be added to pool
Question: After having set up the ESME server once we do not need the
8080 interface anymore. Anybody have an idea as how to disable the
ESME webinterface? Preferably without restarting it please :)
I might have missed this from earlier mails though... and just
"emptying" the default.html file does not cut it security-wise I would
think.
Next step from my side is to implement at our Amazon server (see some
image building coming up) for the current pilots.
When there, if anybody would fancy a pilot instance including the
whole generic Work Processor template gimme a shout and I'll give you
one. BTW, quite useful to run whatever group your working in, and as
IT consultant/department it's free use to boot.
Questions, demos, discussions are what I live for so any time - skype
or twitter or mail...
Cheers,
Sig
Re: ESME in Thingamy - short report and a question
Posted by Sig Rinde <si...@rinde.com>.
Here we are:
Ubuntu 9.04
Amazon Web Services small instance (1.7 GB RAM, 1 EC2 compute unit ~ 1 Ghz)
Java 1.6.0
apt-get install subversion / jetty / maven2
And your suggested commenting out the java compressor stuff.
Think that was all.
2010/1/5 Richard Hirsch <hi...@gmail.com>:
> @sig - could you describe the exact environment (versions, etc.) that
> you are using - I'd like to post the details in the wiki.
>
> On Tue, Jan 5, 2010 at 5:45 PM, Sig Rinde <si...@rinde.com> wrote:
>> Yay, that did the trick! Thanks!
>>
>> AWS and Ubuntu rules :)
>>
>> Now to build a Linux version and implement for first pilot... yummy
>>
>>
>> 2010/1/5 Richard Hirsch <hi...@gmail.com>:
>>> That is javascript compressor which you don't need.
>>>
>>> Look at the pom.xml and comment out the following plug-in
>>>
>>> <plugin>
>>> 288 <groupId>net.sf.alchim</groupId>
>>> 289 <artifactId>yuicompressor-maven-plugin</artifactId>
>>> 290 <executions>
>>> 291 <execution>
>>> 292 <goals>
>>> 293 <goal>compress</goal>
>>> 294 </goals>
>>> 295 </execution>
>>> 296 </executions>
>>> 297 <configuration>
>>> 298 <nosuffix>true</nosuffix>
>>> 299 <jswarn>false</jswarn>
>>> 300 </configuration>
>>> 301 </plugin>
>>>
>>> D,
>>>
>>> On Tue, Jan 5, 2010 at 5:13 PM, Sig Rinde <si...@rinde.com> wrote:
>>>> 2010/1/5 Richard Hirsch <hi...@gmail.com>:
>>>>
>>>>> Should be just as easy with linux. If you notice any diffs, just add a
>>>>> comment to the "Installation Guides" wiki page and I'll add the
>>>>> material to the wiki.
>>>>
>>>> Looked easy...
>>>>
>>>> Much apt-get first (Ubuntu this on Amazon Web Services) - maven2,
>>>> subversion and jetty - all went well including the esme svn.
>>>>
>>>> But when mvn jetty:run from esme/server I get this after a bit:
>>>>
>>>> [ERROR] FATAL ERROR
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] null
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Trace
>>>> java.lang.RuntimeException
>>>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>> at net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>> at net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>> at net.sf.alchim.mojo.yuicompressor.MojoSupport.execute(MojoSupport.java:105)
>>>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>
>>>> And java is:
>>>>
>>>> java version "1.6.0_0"
>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>
>>>> Hmm, where do I stumble?
>>>>
>>>> Sig
>>>>
>>>
>>
>
Re: ESME in Thingamy - short report and a question
Posted by Richard Hirsch <hi...@gmail.com>.
@sig - could you describe the exact environment (versions, etc.) that
you are using - I'd like to post the details in the wiki.
On Tue, Jan 5, 2010 at 5:45 PM, Sig Rinde <si...@rinde.com> wrote:
> Yay, that did the trick! Thanks!
>
> AWS and Ubuntu rules :)
>
> Now to build a Linux version and implement for first pilot... yummy
>
>
> 2010/1/5 Richard Hirsch <hi...@gmail.com>:
>> That is javascript compressor which you don't need.
>>
>> Look at the pom.xml and comment out the following plug-in
>>
>> <plugin>
>> 288 <groupId>net.sf.alchim</groupId>
>> 289 <artifactId>yuicompressor-maven-plugin</artifactId>
>> 290 <executions>
>> 291 <execution>
>> 292 <goals>
>> 293 <goal>compress</goal>
>> 294 </goals>
>> 295 </execution>
>> 296 </executions>
>> 297 <configuration>
>> 298 <nosuffix>true</nosuffix>
>> 299 <jswarn>false</jswarn>
>> 300 </configuration>
>> 301 </plugin>
>>
>> D,
>>
>> On Tue, Jan 5, 2010 at 5:13 PM, Sig Rinde <si...@rinde.com> wrote:
>>> 2010/1/5 Richard Hirsch <hi...@gmail.com>:
>>>
>>>> Should be just as easy with linux. If you notice any diffs, just add a
>>>> comment to the "Installation Guides" wiki page and I'll add the
>>>> material to the wiki.
>>>
>>> Looked easy...
>>>
>>> Much apt-get first (Ubuntu this on Amazon Web Services) - maven2,
>>> subversion and jetty - all went well including the esme svn.
>>>
>>> But when mvn jetty:run from esme/server I get this after a bit:
>>>
>>> [ERROR] FATAL ERROR
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] null
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Trace
>>> java.lang.RuntimeException
>>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>> at net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>> at net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>> at net.sf.alchim.mojo.yuicompressor.MojoSupport.execute(MojoSupport.java:105)
>>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>
>>> And java is:
>>>
>>> java version "1.6.0_0"
>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>
>>> Hmm, where do I stumble?
>>>
>>> Sig
>>>
>>
>
Re: ESME in Thingamy - short report and a question
Posted by Sig Rinde <si...@rinde.com>.
Yay, that did the trick! Thanks!
AWS and Ubuntu rules :)
Now to build a Linux version and implement for first pilot... yummy
2010/1/5 Richard Hirsch <hi...@gmail.com>:
> That is javascript compressor which you don't need.
>
> Look at the pom.xml and comment out the following plug-in
>
> <plugin>
> 288 <groupId>net.sf.alchim</groupId>
> 289 <artifactId>yuicompressor-maven-plugin</artifactId>
> 290 <executions>
> 291 <execution>
> 292 <goals>
> 293 <goal>compress</goal>
> 294 </goals>
> 295 </execution>
> 296 </executions>
> 297 <configuration>
> 298 <nosuffix>true</nosuffix>
> 299 <jswarn>false</jswarn>
> 300 </configuration>
> 301 </plugin>
>
> D,
>
> On Tue, Jan 5, 2010 at 5:13 PM, Sig Rinde <si...@rinde.com> wrote:
>> 2010/1/5 Richard Hirsch <hi...@gmail.com>:
>>
>>> Should be just as easy with linux. If you notice any diffs, just add a
>>> comment to the "Installation Guides" wiki page and I'll add the
>>> material to the wiki.
>>
>> Looked easy...
>>
>> Much apt-get first (Ubuntu this on Amazon Web Services) - maven2,
>> subversion and jetty - all went well including the esme svn.
>>
>> But when mvn jetty:run from esme/server I get this after a bit:
>>
>> [ERROR] FATAL ERROR
>> [INFO] ------------------------------------------------------------------------
>> [INFO] null
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Trace
>> java.lang.RuntimeException
>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>> at net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>> at net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>> at net.sf.alchim.mojo.yuicompressor.MojoSupport.execute(MojoSupport.java:105)
>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>
>> And java is:
>>
>> java version "1.6.0_0"
>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>
>> Hmm, where do I stumble?
>>
>> Sig
>>
>
Re: ESME in Thingamy - short report and a question
Posted by Richard Hirsch <hi...@gmail.com>.
That is javascript compressor which you don't need.
Look at the pom.xml and comment out the following plug-in
<plugin>
288 <groupId>net.sf.alchim</groupId>
289 <artifactId>yuicompressor-maven-plugin</artifactId>
290 <executions>
291 <execution>
292 <goals>
293 <goal>compress</goal>
294 </goals>
295 </execution>
296 </executions>
297 <configuration>
298 <nosuffix>true</nosuffix>
299 <jswarn>false</jswarn>
300 </configuration>
301 </plugin>
D,
On Tue, Jan 5, 2010 at 5:13 PM, Sig Rinde <si...@rinde.com> wrote:
> 2010/1/5 Richard Hirsch <hi...@gmail.com>:
>
>> Should be just as easy with linux. If you notice any diffs, just add a
>> comment to the "Installation Guides" wiki page and I'll add the
>> material to the wiki.
>
> Looked easy...
>
> Much apt-get first (Ubuntu this on Amazon Web Services) - maven2,
> subversion and jetty - all went well including the esme svn.
>
> But when mvn jetty:run from esme/server I get this after a bit:
>
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.RuntimeException
> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> at net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> at net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
> at net.sf.alchim.mojo.yuicompressor.MojoSupport.execute(MojoSupport.java:105)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>
> And java is:
>
> java version "1.6.0_0"
> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>
> Hmm, where do I stumble?
>
> Sig
>
Re: ESME in Thingamy - short report and a question
Posted by Sig Rinde <si...@rinde.com>.
2010/1/5 Richard Hirsch <hi...@gmail.com>:
> Should be just as easy with linux. If you notice any diffs, just add a
> comment to the "Installation Guides" wiki page and I'll add the
> material to the wiki.
Looked easy...
Much apt-get first (Ubuntu this on Amazon Web Services) - maven2,
subversion and jetty - all went well including the esme svn.
But when mvn jetty:run from esme/server I get this after a bit:
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.RuntimeException
at com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
at net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
at net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
at net.sf.alchim.mojo.yuicompressor.MojoSupport.execute(MojoSupport.java:105)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
And java is:
java version "1.6.0_0"
OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
Hmm, where do I stumble?
Sig
Re: ESME in Thingamy - short report and a question
Posted by Richard Hirsch <hi...@gmail.com>.
You may also be interested in the JMX interface
(http://cwiki.apache.org/confluence/display/ESME/JMX) - it is a work
in progress but it allows you keep track of things.
D.
On Tue, Jan 5, 2010 at 3:56 PM, Sig Rinde <si...@rinde.com> wrote:
> Tried a stunt renaming /server/src/main/webapp to webapp2 and it
> certainly cut off 8080 while still allowing the usual API2 stuff to
> happen.
>
> Was that too radical? Did I break something not obvious there? Does it
> keep all away from all interfaces even if they have the URL? Anyway,
> it was simple and allows me to revert in a jiffy :)
>
> BTW, forgot to mention that all programming on our side of the
> holidays was done by oldest son (20) who thought he'd spend his days
> off from Maths and Physics at Kings College in London eating and
> lazying :)
> But he knows his stuff and has helped out before having become quite
> proficient in Common Lisp, but Scala was all new to him (yech, that
> looks ugly was his first reaction - took him an hour before he had
> hacked it though).
>
> Ah, Ethan, saw your mail now: Yes, always good to have a simple way to
> turn off the interfaces, makes things easier for those who only wants
> the server using the API. Anything that I can flip on/off via SSH is
> good (renaming webapp folder works for me if I did not mess up
> something by that).
>
> Noticed another thing on the ESME site, under 'intallation guides' I
> did not find anything obvious for Linux. Is it as simple as 'apt-get
> install jetty' and then do as I did on OS X? (sorry for naive question
> here ;))
Should be just as easy with linux. If you notice any diffs, just add a
comment to the "Installation Guides" wiki page and I'll add the
material to the wiki.
>
> Sig
>
>
> 2010/1/5 Richard Hirsch <hi...@gmail.com>:
>
>>> Question: After having set up the ESME server once we do not need the
>>> 8080 interface anymore. Anybody have an idea as how to disable the
>>> ESME webinterface? Preferably without restarting it please :)
>>> I might have missed this from earlier mails though... and just
>>> "emptying" the default.html file does not cut it security-wise I would
>>> think.
>>
>> Either lift based changes (Boot.scala?) or just delete all the html
>> files from WEB-INF directory. The user trying to access via the web
>> would get an lift error but no access.
>
Re: ESME in Thingamy - short report and a question
Posted by Sig Rinde <si...@rinde.com>.
Tried a stunt renaming /server/src/main/webapp to webapp2 and it
certainly cut off 8080 while still allowing the usual API2 stuff to
happen.
Was that too radical? Did I break something not obvious there? Does it
keep all away from all interfaces even if they have the URL? Anyway,
it was simple and allows me to revert in a jiffy :)
BTW, forgot to mention that all programming on our side of the
holidays was done by oldest son (20) who thought he'd spend his days
off from Maths and Physics at Kings College in London eating and
lazying :)
But he knows his stuff and has helped out before having become quite
proficient in Common Lisp, but Scala was all new to him (yech, that
looks ugly was his first reaction - took him an hour before he had
hacked it though).
Ah, Ethan, saw your mail now: Yes, always good to have a simple way to
turn off the interfaces, makes things easier for those who only wants
the server using the API. Anything that I can flip on/off via SSH is
good (renaming webapp folder works for me if I did not mess up
something by that).
Noticed another thing on the ESME site, under 'intallation guides' I
did not find anything obvious for Linux. Is it as simple as 'apt-get
install jetty' and then do as I did on OS X? (sorry for naive question
here ;))
Sig
2010/1/5 Richard Hirsch <hi...@gmail.com>:
>> Question: After having set up the ESME server once we do not need the
>> 8080 interface anymore. Anybody have an idea as how to disable the
>> ESME webinterface? Preferably without restarting it please :)
>> I might have missed this from earlier mails though... and just
>> "emptying" the default.html file does not cut it security-wise I would
>> think.
>
> Either lift based changes (Boot.scala?) or just delete all the html
> files from WEB-INF directory. The user trying to access via the web
> would get an lift error but no access.
Re: ESME in Thingamy - short report and a question
Posted by Richard Hirsch <hi...@gmail.com>.
On Tue, Jan 5, 2010 at 3:50 PM, Ethan Jewett <es...@gmail.com> wrote:
> I think in the long run we need to make this stuff configurable via
> the property files.
I agree. If you add anything new to the configutarion files, don't
forget to add the information to the wiki:
http://cwiki.apache.org/confluence/display/ESME/Server+Configuration
The questions are what needs to be configurable
> and where is the Jira ticket? ;-)
>
> Sig, do you guys have a Jira account? You should probably get one set
> up if you don't. (https://issues.apache.org/jira/browse/ESME)
>
> My thoughts on what should be turned on and off via property:
>
> 1. Web interface (for Sig)
> 2. Twitter API
> 3. Original API
> 4. API2
>
> I think it's important that the availability of the APIs be
> configurable for security reasons.
>
> Ethan
>
> On Tue, Jan 5, 2010 at 9:38 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> On Tue, Jan 5, 2010 at 1:23 PM, Sig Rinde <si...@rinde.com> wrote:
>>> Hi everybody,
>>>
>>> thanks to many members of this group, ESME now working nicely
>>> inside/beside Thingamy using latest (untouched ;)) commit (Thanks
>>> again Ethan, excellent and fast work!).
>>>
>>> (Video coming, but have a flu/headachy thing today so head's too mushy)
>>>
>>> In Thingamy:
>>>
>>> - (our own) JS client incorporated using API2.
>>> - Messages are tagged by one or more objects in Thingamy (tick box in
>>> each object enables that).
>>> - Messages are filtered by same method from tasks and/or reports.
>>> - Multiple tags/relationships enabled - both adding and filtering, but
>>> limited to the 50 last messages for now, need to include everything
>>> (search?).
>>> - Reply "button" in message client adds name (as in Twitter) in
>>> response field and tags new message with same tags/relations.
>>> - Enable/disable ESME for system in full and for each user role.
>>> - Uses pools and names the pool by application name which is set in
>>> Thingamy setup interface (under admin) allowing us to use one ESME
>>> instance for multiple Thingamy instances.
>>> - Messages also shows object(s) it's related to (cryptic name for now)
>>> which are links to a graph display of the object and all it's
>>> relations to other Thingamy objects.
>>>
>>> ESME server:
>>>
>>> - Adding one line to default.props to set admin user
>>> - Sign up as that user
>>> - Create a token, that's all
>>> - In Thingamy setup one sets the application name (names pool) and add
>>> the token.
>>> - When adding users to Thingamy each will (tick box to enable) be
>>> allocated a token and be added to pool
>>>
>>> Question: After having set up the ESME server once we do not need the
>>> 8080 interface anymore. Anybody have an idea as how to disable the
>>> ESME webinterface? Preferably without restarting it please :)
>>> I might have missed this from earlier mails though... and just
>>> "emptying" the default.html file does not cut it security-wise I would
>>> think.
>>
>> Either lift based changes (Boot.scala?) or just delete all the html
>> files from WEB-INF directory. The user trying to access via the web
>> would get an lift error but no access.
>>
>>>
>>> Next step from my side is to implement at our Amazon server (see some
>>> image building coming up) for the current pilots.
>>>
>>> When there, if anybody would fancy a pilot instance including the
>>> whole generic Work Processor template gimme a shout and I'll give you
>>> one. BTW, quite useful to run whatever group your working in, and as
>>> IT consultant/department it's free use to boot.
>>>
>>> Questions, demos, discussions are what I live for so any time - skype
>>> or twitter or mail...
>>>
>>> Cheers,
>>> Sig
>>>
>>
>
Re: ESME in Thingamy - short report and a question
Posted by Ethan Jewett <es...@gmail.com>.
I think in the long run we need to make this stuff configurable via
the property files. The questions are what needs to be configurable
and where is the Jira ticket? ;-)
Sig, do you guys have a Jira account? You should probably get one set
up if you don't. (https://issues.apache.org/jira/browse/ESME)
My thoughts on what should be turned on and off via property:
1. Web interface (for Sig)
2. Twitter API
3. Original API
4. API2
I think it's important that the availability of the APIs be
configurable for security reasons.
Ethan
On Tue, Jan 5, 2010 at 9:38 AM, Richard Hirsch <hi...@gmail.com> wrote:
> On Tue, Jan 5, 2010 at 1:23 PM, Sig Rinde <si...@rinde.com> wrote:
>> Hi everybody,
>>
>> thanks to many members of this group, ESME now working nicely
>> inside/beside Thingamy using latest (untouched ;)) commit (Thanks
>> again Ethan, excellent and fast work!).
>>
>> (Video coming, but have a flu/headachy thing today so head's too mushy)
>>
>> In Thingamy:
>>
>> - (our own) JS client incorporated using API2.
>> - Messages are tagged by one or more objects in Thingamy (tick box in
>> each object enables that).
>> - Messages are filtered by same method from tasks and/or reports.
>> - Multiple tags/relationships enabled - both adding and filtering, but
>> limited to the 50 last messages for now, need to include everything
>> (search?).
>> - Reply "button" in message client adds name (as in Twitter) in
>> response field and tags new message with same tags/relations.
>> - Enable/disable ESME for system in full and for each user role.
>> - Uses pools and names the pool by application name which is set in
>> Thingamy setup interface (under admin) allowing us to use one ESME
>> instance for multiple Thingamy instances.
>> - Messages also shows object(s) it's related to (cryptic name for now)
>> which are links to a graph display of the object and all it's
>> relations to other Thingamy objects.
>>
>> ESME server:
>>
>> - Adding one line to default.props to set admin user
>> - Sign up as that user
>> - Create a token, that's all
>> - In Thingamy setup one sets the application name (names pool) and add
>> the token.
>> - When adding users to Thingamy each will (tick box to enable) be
>> allocated a token and be added to pool
>>
>> Question: After having set up the ESME server once we do not need the
>> 8080 interface anymore. Anybody have an idea as how to disable the
>> ESME webinterface? Preferably without restarting it please :)
>> I might have missed this from earlier mails though... and just
>> "emptying" the default.html file does not cut it security-wise I would
>> think.
>
> Either lift based changes (Boot.scala?) or just delete all the html
> files from WEB-INF directory. The user trying to access via the web
> would get an lift error but no access.
>
>>
>> Next step from my side is to implement at our Amazon server (see some
>> image building coming up) for the current pilots.
>>
>> When there, if anybody would fancy a pilot instance including the
>> whole generic Work Processor template gimme a shout and I'll give you
>> one. BTW, quite useful to run whatever group your working in, and as
>> IT consultant/department it's free use to boot.
>>
>> Questions, demos, discussions are what I live for so any time - skype
>> or twitter or mail...
>>
>> Cheers,
>> Sig
>>
>
Re: ESME in Thingamy - short report and a question
Posted by Richard Hirsch <hi...@gmail.com>.
On Tue, Jan 5, 2010 at 1:23 PM, Sig Rinde <si...@rinde.com> wrote:
> Hi everybody,
>
> thanks to many members of this group, ESME now working nicely
> inside/beside Thingamy using latest (untouched ;)) commit (Thanks
> again Ethan, excellent and fast work!).
>
> (Video coming, but have a flu/headachy thing today so head's too mushy)
>
> In Thingamy:
>
> - (our own) JS client incorporated using API2.
> - Messages are tagged by one or more objects in Thingamy (tick box in
> each object enables that).
> - Messages are filtered by same method from tasks and/or reports.
> - Multiple tags/relationships enabled - both adding and filtering, but
> limited to the 50 last messages for now, need to include everything
> (search?).
> - Reply "button" in message client adds name (as in Twitter) in
> response field and tags new message with same tags/relations.
> - Enable/disable ESME for system in full and for each user role.
> - Uses pools and names the pool by application name which is set in
> Thingamy setup interface (under admin) allowing us to use one ESME
> instance for multiple Thingamy instances.
> - Messages also shows object(s) it's related to (cryptic name for now)
> which are links to a graph display of the object and all it's
> relations to other Thingamy objects.
>
> ESME server:
>
> - Adding one line to default.props to set admin user
> - Sign up as that user
> - Create a token, that's all
> - In Thingamy setup one sets the application name (names pool) and add
> the token.
> - When adding users to Thingamy each will (tick box to enable) be
> allocated a token and be added to pool
>
> Question: After having set up the ESME server once we do not need the
> 8080 interface anymore. Anybody have an idea as how to disable the
> ESME webinterface? Preferably without restarting it please :)
> I might have missed this from earlier mails though... and just
> "emptying" the default.html file does not cut it security-wise I would
> think.
Either lift based changes (Boot.scala?) or just delete all the html
files from WEB-INF directory. The user trying to access via the web
would get an lift error but no access.
>
> Next step from my side is to implement at our Amazon server (see some
> image building coming up) for the current pilots.
>
> When there, if anybody would fancy a pilot instance including the
> whole generic Work Processor template gimme a shout and I'll give you
> one. BTW, quite useful to run whatever group your working in, and as
> IT consultant/department it's free use to boot.
>
> Questions, demos, discussions are what I live for so any time - skype
> or twitter or mail...
>
> Cheers,
> Sig
>
Re: ESME in Thingamy - short report and a question
Posted by Ethan Jewett <es...@gmail.com>.
Sig,
Wow, talk about fast work! I don't think I can keep up with you guys :-)
Multiple tag filtering using ESME's API (implemented using search
"under the hood") is next on my todo list. This will allow you to get
the last X messages with whatever combination of tags you specify.
Probably not until this weekend at the earliest, but who knows....
Ethan
On Tue, Jan 5, 2010 at 7:23 AM, Sig Rinde <si...@rinde.com> wrote:
> Hi everybody,
>
> thanks to many members of this group, ESME now working nicely
> inside/beside Thingamy using latest (untouched ;)) commit (Thanks
> again Ethan, excellent and fast work!).
>
> (Video coming, but have a flu/headachy thing today so head's too mushy)
>
> In Thingamy:
>
> - (our own) JS client incorporated using API2.
> - Messages are tagged by one or more objects in Thingamy (tick box in
> each object enables that).
> - Messages are filtered by same method from tasks and/or reports.
> - Multiple tags/relationships enabled - both adding and filtering, but
> limited to the 50 last messages for now, need to include everything
> (search?).
> - Reply "button" in message client adds name (as in Twitter) in
> response field and tags new message with same tags/relations.
> - Enable/disable ESME for system in full and for each user role.
> - Uses pools and names the pool by application name which is set in
> Thingamy setup interface (under admin) allowing us to use one ESME
> instance for multiple Thingamy instances.
> - Messages also shows object(s) it's related to (cryptic name for now)
> which are links to a graph display of the object and all it's
> relations to other Thingamy objects.
>
> ESME server:
>
> - Adding one line to default.props to set admin user
> - Sign up as that user
> - Create a token, that's all
> - In Thingamy setup one sets the application name (names pool) and add
> the token.
> - When adding users to Thingamy each will (tick box to enable) be
> allocated a token and be added to pool
>
> Question: After having set up the ESME server once we do not need the
> 8080 interface anymore. Anybody have an idea as how to disable the
> ESME webinterface? Preferably without restarting it please :)
> I might have missed this from earlier mails though... and just
> "emptying" the default.html file does not cut it security-wise I would
> think.
>
> Next step from my side is to implement at our Amazon server (see some
> image building coming up) for the current pilots.
>
> When there, if anybody would fancy a pilot instance including the
> whole generic Work Processor template gimme a shout and I'll give you
> one. BTW, quite useful to run whatever group your working in, and as
> IT consultant/department it's free use to boot.
>
> Questions, demos, discussions are what I live for so any time - skype
> or twitter or mail...
>
> Cheers,
> Sig
>