|
From: Tomas G. <to...@pr...> - 2017-05-02 10:38:13
|
Hi Christian, I tested the script on CentOS 7. Worked well and was up and running in no time The things I had to figure out: 1. script must be run as user "ejbca". I started running as user "user" and it went on until trying to build EJBCA when it failed. Could be checked/warned for in the beginning. 2. CentOS has curl installed by default I think, so if the script used curl, the additional wget package would be needed to install. As a side-note, in my default installs I usually don't configure log4j-jboss6.xml, I just let wildfly log to server.log as default and enable/disable EJBCA debug logging dynamically with: /subsystem=logging/logger=org.ejbca:add /subsystem=logging/logger=org.ejbca:write-attribute(name=level, value=DEBUG) /subsystem=logging/logger=org.cesecore:add /subsystem=logging/logger=org.cesecore:write-attribute(name=level, value=DEBUG) Cheers, Tomas On 2017-04-28 13:11, Christian Felsing wrote: > Hello, > > hopefully useful if you want to set up EJBCA on Wildfly 10: > > https://gist.github.com/ip6li/9801a5ed958feb7de6136ea175572bdf > > That script assumes an existing database (MariaDB). It installs required > packages (supports Debian and CentOS versions with systemd) and requests > Wildfly and EJBCA from their download URLs. > Creates required config files and does all stuff to get a running EJBCA > on Wildfly 10. > Systemd will care about start/stop that. > > Regards > Christian > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > |