Issue 51 in direct-certificate-discovery-tool: VM Based - Configuration - State

[direct-certifica...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 51 by gan...@glenwoodsystems.com: VM Based - Configuration - State
http://code.google.com/p/direct-certificate-discovery-tool/issues/detail?id=51

Every time you release the VM Image we need to redo the entire
configuration. Is there a way to backup certain files and restore them.

[direct-certifica...@googlecode.com]

Updates:
Status: Accepted
Labels: -Type-Defect -Priority-Medium Type-Task Priority-Low

Comment #1 on issue 51 by michal.k...@esacinc.com: VM Based - Configuration
- State
http://code.google.com/p/direct-certificate-discovery-tool/issues/detail?id=51

Its likely possible to mount the VM image as a file system in a Linux
environment and just move files over, but it would be a time-consuming and
error-prone solution.

I am currently in the process of overhauling the
build/deployment/configuration workflows of the tool. At minimum, the tool
will soon be buildable/deployable straight from the Maven command line to
an existing environment (via the Tomcat manager). The archive-based (tar.gz
file) deployment option will also likely be resurrected.

In the meantime, I would suggest backing up the Direct config-service Derby
DB. By default it is in a directory called 'nhindconfig' Its location is
set in WEB-INF/beans.xml in the config-service webapp. The DB contains all
of the data you have inputted into the config-ui (domains, Agent settings,
certs/keys, DNS settings).

[direct-certifica...@googlecode.com]

Updates:
Owner: michal.k...@esacinc.com

Comment #2 on issue 51 by michal.k...@esacinc.com: VM Based - Configuration
- State
http://code.google.com/p/direct-certificate-discovery-tool/issues/detail?id=51

(No comment was entered for this change.)