bug4811: moved default rules for env variables into env-default-rules.sh which is now executed after env.sh

cp -v $PROJECT_HOME/java/target/refreshInstance.sh $ACDIR/

cp -v $PROJECT_HOME/java/target/env.sh $ACDIR/

cp -v $p2PluginRepository/configuration/config.ini configuration/

cp -v $PROJECT_HOME/java/target/configuration/jetty/etc/jetty.xml configuration/jetty/etc

SSH_CMD="ssh $REMOTE_SERVER_LOGIN"

SCP_CMD="scp -r"

echo "Checking the remote connection..."

REMOTE_HOME=`ssh $REMOTE_SERVER_LOGIN 'echo $HOME/releases'`

if [ ! -f "$ACDIR/env.sh" ]; then

cp -v $PROJECT_HOME/java/target/env.sh $ACDIR/

cp -v $PROJECT_HOME/java/target/configuration/monitoring.properties $ACDIR/configuration/

cp -v $PROJECT_HOME/java/target/configuration/mail.properties $ACDIR/configuration/

cp -v $PROJECT_HOME/java/target/configuration/logging.properties $ACDIR/configuration/

# make sure to read the information from env.sh

. $ACDIR/env.sh

echo "$VERSION_INFO System:" > $ACDIR/configuration/jetty/version.txt

$SCP_CMD $PROJECT_HOME/java/target/configuration/mail.properties $REMOTE_SERVER_LOGIN:$REMOTE_SERVER/configuration/

$SCP_CMD $PROJECT_HOME/java/target/env.sh $REMOTE_SERVER_LOGIN:$REMOTE_SERVER/

$SCP_CMD $PROJECT_HOME/java/target/start $REMOTE_SERVER_LOGIN:$REMOTE_SERVER/

$SCP_CMD $PROJECT_HOME/java/target/stop $REMOTE_SERVER_LOGIN:$REMOTE_SERVER/

$SCP_CMD $PROJECT_HOME/java/target/status $REMOTE_SERVER_LOGIN:$REMOTE_SERVER/

# Example: start_server server

start_server() {

local conf="$1"

}

# Call with the server directory name (not the full path, just a single element from ${JAVA_START_INSTANCE}) as parameter

# of this file as there could be overwritten ones!

# *******************************************************

# To start replication upon startup provide the fully-qualified names of the Replicable service classes

# for which to trigger replication. If you activate this make sure to

# set the REPLICATE_MASTER_EXCHANGE_NAME variable to the

if [ -n "$AUTO_REPLICATE" ]; then

REPLICATE_ON_START=com.sap.sailing.server.impl.RacingEventServiceImpl,com.sap.sse.security.impl.SecurityServiceImpl,com.sap.sse.filestorage.impl.FileStorageManagementServiceImpl,com.sap.sse.mail.impl.MailServiceImpl,com.sap.sailing.polars.impl.PolarDataServiceImpl,com.sap.sailing.domain.racelogtracking.impl.fixtracker.RegattaLogFixTrackerRegattaListener,com.sap.sailing.windestimation.integration.WindEstimationFactoryServiceImpl,com.sap.sailing.server.impl.com.sap.sailing.shared.server.impl.SharedSailingDataImpl

fi

# Make sure firewall configurations allow access

#

# REPLICATE_MASTER_SERVLET_HOST=

# REPLICATE_MASTER_SERVLET_PORT=

# Exchange name that the master from which to auto-replicate is using as

# its REPLICATION_CHANNEL variable, mapping to the master's replication.exchangeName

# system property.

#ADDITIONAL_JAVA_ARGS="$ADDITIONAL_JAVA_ARGS -Dcom.sap.sse.debranding=true"

ADDITIONAL_JAVA_ARGS="$JAVA_VERSION_SPECIFIC_ARGS $ADDITIONAL_JAVA_ARGS -Dpersistentcompetitors.clear=false -Drestore.tracked.races=true -Dpolardata.source.url=https://www.sapsailing.com -Dwindestimation.source.url=https://www.sapsailing.com -XX:MaxGCPauseMillis=500"

#ADDITIONAL_JAVA_ARGS="$ADDITIONAL_JAVA_ARGS -Dcom.sap.sailing.eventmanagement.url=https://dev.sapsailing.com"

# To enable the use of the shared SecurityService and SharedSailingData from security-service.sapsailing.com, uncomment and fill in the following:

#REPLICATE_MASTER_BEARER_TOKEN="..."

echo ADDITIONAL_JAVA_ARGS=${ADDITIONAL_JAVA_ARGS}

echo ""

return 0

fi

if [ ! -d "$1/.git" ]; then

PARENT_DIR=`cd $1/..;pwd`

OUTPUT=$(find_project_home $PARENT_DIR)

if [ "$OUTPUT" = "" ] && [ -d "$PARENT_DIR/$CODE_DIRECTORY" ] && [ -d "$PARENT_DIR/$CODE_DIRECTORY/.git" ]; then

OUTPUT="$PARENT_DIR/$CODE_DIRECTORY"

fi

echo $OUTPUT

return 0

fi

echo $1 | sed -e 's/\/cygdrive\/\([a-zA-Z]\)/\1:/'

}

INSTANCE_ID="$INSTANCE_NAME ($INSTANCE_IP4)"

}

append_user_data_to_envsh ()

{

mkdir -p $SERVER_HOME/environment 2>/dev/null >/dev/null

echo "# Environment ($USE_ENVIRONMENT): START ($DATE_OF_EXECUTION)" >> $SERVER_HOME/env.sh

cat $SERVER_HOME/environment/$USE_ENVIRONMENT >> $SERVER_HOME/env.sh

echo "# Environment: END" >> $SERVER_HOME/env.sh

echo "Updated env.sh with data from environment file!"

else

echo "No environment file specified!"

fi

# then download and install environment and append to env.sh

install_environment

append_user_data_to_envsh

# make sure to reload data, this time including defaults from release's env.sh, environment settings and user data

source `pwd`/env.sh

fi

PWD=`pwd`

. "$PWD/env.sh"

PARAM=$@

Using a release, set the following in the instance's user data, replacing `myspecificevent` by a unique name of the event or series you'll be running on that instance, such as `kielerwoche2014` or similar. Note that when you select to install an environment using the `USE_ENVIRONMENT` variable, any other variable that you specify in the user data, such as the `MONGODB_URI` or `REPLICATION_CHANNEL` properties in the example above, these additional user data properties will override whatever comes from the environment specified by the `USE_ENVIRONMENT` parameter.

```

INSTALL_FROM_RELEASE=(name-of-release)

USE_ENVIRONMENT=live-master-server