...
I used ISDA-IST1 as the target machine for testing.
- unpacked the software into /usr/local, creating /usr/local/cd-1.00.13 (the content deploy home directory, aka $CDHOME).
- made the following changes in the files:
...
- set executable bits on three scripts in bin: cda, wrapper, and deploy
...
- set the location of the Java binary in bin/wrapper.conf:
wrapper.java.command=/usr/local/jdk1.5.0_11/bin/java
- set the location of the Java binary in bin/wrapper.conf:
...
- configured the agent (aka listener) by modifying etc/cda.xml:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8" ?>
<agent-config>
<admin bind-address="localhost" bind-port="21008" />
<server bind-address="18.92.0.199" bind-port="21009">
<permit host="18.92.1.223" key="">
<path location="/root/sturner/contentdeploy" />
</permit>
</server>
</agent-config>
|
...
- The agent/listener is started by typing:
{$CDHOME/bin/cda start}
- The agent is stopped by:
{$CDHOME/bin/cda stop}
Source Configuration:
I used ISDA-CS2 as the source machine for testing.
...
- tweaked the $CDHOME/bin/deploy script so that the location of the java binary was correct:
JAVA_EXE=/usr/local/jdk1.5.0_11/bin/java
- moved the avm-remote context config from $CDHOME/conf/tests to $CDHOME/conf. I didn't make any changes to this config file, as I wanted to deploy from the local machine.
...
Finally, to deploy content, I issued these command:
cd $CDHOME/bin
./deploy ../conf/ist1-test.xml
This copies files from the staging sandbox of the "steveweb" web project on isda-cs2 into the file system on isda-ist1 under the directory /root/sturner/contentdeploy.