On Mon, Jan 24, 2011 at 6:31 PM, Ethan Jewett <[email protected]> wrote: > Hi Jens, > > Very interesting that you are trying out ESME. Let us know what we can > do to help! Regarding the conversation issue you are seeing, clicking > on conversations seems to work for me on > http://esmecloudserverapache.dickhirsch.staxapps.net/ Can you confirm > that it works for you on the Stax deployment but not locally? > > Dick, > > I think I remember creating a Jira feature request (as you mention) > for configuration settings to turn menus on and off ... but I can't > find it. Did you see it? If not, I'll create a new one.
Found it: https://issues.apache.org/jira/browse/ESME-285 The first three options (Tracks, Actions, Tokens) might be easy to do with just Boot.Scala being affected. The pools change is more difficult. > > Thanks, > Ethan > > On Mon, Jan 24, 2011 at 4:37 PM, Richard Hirsch <[email protected]> wrote: >> On Mon, Jan 24, 2011 at 2:19 PM, <[email protected]> wrote: >>> Hi Anne Kathrine, >>> >>> Eik Sunke gave me your contact data. As he probably told you, I'm >>> responsible for deploying ESME on SAP NetWeaver Portal 7.3. >>> Unfortunately I have some questions. >>> >>> -- I checked out sources from svn (trunk folder) and was able to build the >>> war with Maven. The war is version 1.2. As far I know, you told Eik that >>> 1.1 is the current stable release. How do I get the stable version? >>> The current version I deployed has got some bugs (e.g. click to >>> conversation doesn't work). >> >> There is a 1.1 tagged version that is the stable version [1] but I'd >> suggest using the trunk in order to be able to get the fastest bug >> fixes. >> >>> >>> -- Additionally I would like to know, how I can adjust and configure ESME >>> in particular. >>> E.g I would like to make "My Token" and "My Action" invisible since we do >>> not need them. >>> I was not able to find corresponding documentation >> >> Currently, you have to remove these items manually via code changes. >> I'll try and create an wiki entry to describe the changes. >> >> We have a JIRA issue to make this change but we haven't had a chance >> to implement it yet. >> >>> >>> -- I only deployed the war file. How is ESME doing persistence? Are all >>> posts kept within ESME without an external database? >> >> ESME uses JDBC to store the messages in a database. You have to set >> the information in the properties file [2]. >> >> You need to set the following properties: >> * "db_driver" >> * "jdbc_connect_url" >> * "db_user >> * "db_pwd" >> >> ESME uses derby out-of-the-box if now other database is set. Or you >> can also use container-based authentication [3] >> >> You may wish to look at our wiki page for installing on SAP's CE [3] >> >>> >>> Hopefully you can help me out. Thank you very much! >> >> [1] http://svn.apache.org/repos/asf/esme/tags/apache-esme-1.1-incubating/ >> [2] http://esme.apache.org/server-configuration.html >> [3] https://cwiki.apache.org/confluence/display/ESME/CE+Installation+Guide >>> >>> Regards, >>> >>> Jens Drogi >>> >>> Deutsche Telekom AG >>> HR Demand & Vendor Management >>> Jens Drogi >>> Friedrich-Ebert-Allee 140, 53113 Bonn >>> +49 228 18 17 72 34 (Tel.) >>> +49 171 862 81 89 (Mobil) >>> E-Mail: [email protected] >>> www.telekom.com >>> >>> Erleben, was verbindet. >>> >>> Deutsche Telekom AG >>> Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) >>> Vorstand: René Obermann (Vorsitzender), >>> Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, >>> Timotheus Höttges, Guido Kerkhoff, Edward R. Kozel, Thomas Sattelberger >>> Handelsregister: Amtsgericht Bonn HRB 6794 >>> Sitz der Gesellschaft Bonn >>> WEEE-Reg.-Nr. DE50478376 >>> >>> Große Veränderungen fangen klein an - Ressourcen schonen und nicht jede >>> E-Mail drucken. >>> >>> >>> >>> >>> Hi again Eik, >>> >>> I just wanted to let you know that if you should run into problems >>> installing ESME on NW 7.3, please send an email to the team at >>> [email protected]. >>> >>> Thank you, >>> Anne Kathrine >>> >>> >>> >>> >> >
