[ https://issues.jboss.org/browse/RTGOV-462?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-462: ---------------------------------- Previously discussed options for creating the server - possibly triggered by an EJB to leverage its lifecycle. However any Elasticsearch client will be dependent upon this being started. Wondering whether it is better to simplify this for now - for example in the ElasticsearchClient (https://github.com/Governance/rtgov/blob/master/modules/common/rtgov-elas...) the 'embedded' host value is creating an instance for use in testing - but can this be enhanced to start a properly configured (and potentially clustered) local node? Statically stored in this ElasticsearchClient to avoid multiple embedded servers being started up? Issues would be, where it obtains the configuration from - probably best in overlord-rtgov.properties - so that the individual components using Elasticsearch don't need to provide this config details, which may end up varying across components - so they just provide host name "embedded" and the common details are obtained from the properties file. Could change the current 'embedded' entry to 'test' - if a lightweight server is required for test purposes? -- This message was sent by Atlassian JIRA (v6.2.3#6260)