For enterprise implementations, due to storage requirements, you may
need to relocate your
CodeStation
files so that they are stored on a different machine than your
Deployment Automation
server. A good formula for determining
CodeStation
storage requirements is:
average artifact size * number of versions imported per day *
average number of days before cleanup.
File storage is organized as follows on a default
Deployment Automation
server installation:
- Execution log files are located in
.microfocus\da\logs folder
-
CodeStation
respository files are located in
.microfocus\da\var\repository
- Plugin files are located in
.microfocus\da\var\plugins
- This folder
.microfocus\da\var\db contains Derby database files if
Derby is used.
Relocate the
CodeStation
files as follows:
- Stop the server before moving the folder location.
- To relocate log files, you must relocate the
\logs folder.
- You can either relocate the whole
var folder, or if you want to relocate only the
repository files, you can relocate just the
\var\repository folder.
- Use the following to configure your network storage in an optimal
way:
- This data should be stored on robust network storage that is
regularly synchronized with an off-site disaster recovery facility.
- The
Deployment Automation
server should have a fast network connection to storage (agents do not need
access to the storage location).
- In Unix environments, you can use
symbolic links from the
var subdirectory to network storage.
- On Windows platforms there are several options for redirecting
logs and artifacts, including
mklink (supported in Windows 7 and later).
- Distributed teams should also take advantage of location-specific
CodeStation
proxies to improve performance and lower WAN usage.
Copyright © 2011–2017 Serena Software, Inc. All rights reserved.