Release Notes for SDP - Helix Server Deployment Package Helix Server Components Introduction This document notes changes to the SDP. There are two flavors of the SDP, Unix and Windows. At a high level, the core function of the SDP is similar on Unix and Windows: To maintain an offline copy of the Helix databases, and perform routine offline checkpoints in preparation for backups. At a detailed level, there are differences in both implementation and behavior on the various platforms. Enhancements are needs-driven, and not necessarily applied across Unix and Windows platforms. -------------------------------------------------------------------------- Upgrading the SDP on Unix To incorporate a new version of the SDP into an existing SDP installation, first stage the deployment as in this example, assuming you have put the SDP distribution tar file in /depotdata. Working as user root on a Perforce server: cd /depotdata # If an sdp folder exists here, move it aside, e.g. to # sdp.MOVED_2014-09-11 tar -xzpf sdp.Unix.2014.2.10649.tgz chown -R perforce:perforce sdp.Unix.2014.2.10649.tgz /depotdata/sdp cd /depotdata/sdp/Server/Unix/p4/common/bin # Copy 'p4', 'p4d', 'p4broker', 'p4web', 'p4p', etc. (only # those currently used) into this 'bin' folder. cd /depotdata/sdp/Server/Unix/setup vi mkdirs.sh # Review and adjustments to mkdirs.sh suit your environment. ./mkdirs.sh 1 -test Using 'mkdirs.sh' script with the '-test' flag as illustrated above will deploy to the SDP to /tmp/p4 rather than /p4 area. If working on the Production server directly, DO NOT forget to use the '-test' flag. -------------------------------------------------------------------------- Upgrading the SDP on Windows: Install the SDP onto a different machine - configure sdp_master_config.ini - run create_env.py Manually copy resulting files to the appropriate places in your existing installation. -------------------------------------------------------------------------- Versioning the SDP: We strongly recommend that files in the following locations are versioned in your local Helix server: On Unix: /p4/1/bin /p4/common On Windows: C:\p4\1\bin C:\p4\common C:\p4\config COMING SOON: Helix DVCS and Streams features enable a new method for updating the SDP long-term, greatly simplifying the process of bringing in updates from The Workshop into your environment, and then merging into your local as-deployed SDP (as configured and possibly customized). A simple 'p4 fetch' and 'p4 merge' process. The setup and mechancis will be documented in Q1 2016. -------------------------------------------------------------------------- CHANGE HISTORY: job000434 - Add documentation for sdp_sync.sh to SDP Guide. job000436 - Support $MAILTO values with'#' char in gen_default_broker_cfg.sh. Released: SDP/MultiArch/2016.1/16784 (2016/01/12) -------------------------------------------------------------------------- For more information on jobs, change history details, etc, see: https://swarm.workshop.perforce.com/projects/perforce-software-sdp