Version Differences for Cloning an AnthillPro Instance

Revision as of 09 May 2012 09:30 m ← Previous diff

Revision as of 09 May 2012 09:39 (→File System Cloning) Next diff →

Line 5:
	= File System Cloning =		= File System Cloning =
	To clone the anthillpro server itself:		To clone the anthillpro server itself:
		+	== Installer Download & Extraction ==
	# On the machine you want to install the cloned server on, download the distributable archive that matches the current version of your AnthillPro Server (so if you are running 3.7.3_68926, you will want to download 3.7.3_68926).		# On the machine you want to install the cloned server on, download the distributable archive that matches the current version of your AnthillPro Server (so if you are running 3.7.3_68926, you will want to download 3.7.3_68926).
	# Extract the archive to an accessible folder.		# Extract the archive to an accessible folder.
		+	== Installation of Clone ==
	# From an Administrative Command Prompt, navigate to the extracted anthill3-install directory, and run install-server.bat.		# From an Administrative Command Prompt, navigate to the extracted anthill3-install directory, and run install-server.bat.
	# When prompted, provide the following information:		# When prompted, provide the following information:
-	## Directory: Directory where you would like the server installed on the new machine	+	## '''Directory''': Directory where you would like the server installed on the new machine
-	## Confirmation: Type ‘y’ if this was the correct directory to install to. Typing ‘n’ will fail the program out.	+	## '''Confirmation''': Type ‘y’ if this was the correct directory to install to. Typing ‘n’ will fail the program out.
-	## JDK: Home directory of the JDK	+	## '''JDK''': Home directory of the JDK
-	## Host: The hostname of the AnthillPro server (the agents will use this to connect to the server)	+	## '''Host''': The hostname of the AnthillPro server (the agents will use this to connect to the server)
-	## JMS: The port that the agents will be using for communication (Default is 7915)	+	## '''JMS''': The port that the agents will be using for communication (Default is 7915)
-	## Devilfish/Remoting: The port that will be used for remoting connections (Default is 4567)	+	## '''Devilfish/Remoting''': The port that will be used for remoting connections (Default is 4567)
-	## IP Address: Also known as the ‘Bind-IP’. This is the address the server will bind to (default is all [0.0.0.0]).	+	## '''IP Address''': Also known as the ‘Bind-IP’. This is the address the server will bind to (default is all [0.0.0.0]).
-	### HTTPS (optional): Type ‘y’ if you want to use HTTPS protocol to connect to the WebUI, else type ‘n’.	+	### '''HTTPS (optional)''': Type ‘y’ if you want to use HTTPS protocol to connect to the WebUI, else type ‘n’.
-	### HTTPS Port (optional): Input the secure port that you want the WebUI to listen on (Default is 8443).	+	### '''HTTPS Port (optional)''': Input the secure port that you want the WebUI to listen on (Default is 8443).
-	### HTTP Port: Input the port that you want the WebUI to listen on (Default is 8080).	+	### '''HTTP Port''': Input the port that you want the WebUI to listen on (Default is 8080).
-	### SSL (optional): Type ‘y’ if you want to use SSL between Server ? Agents. Else type ‘n’.	+	### '''SSL (optional)''': Type ‘y’ if you want to use SSL between Server ? Agents. Else type ‘n’.
-	### Mutual Authentication (optional): Type ‘y’ if you want to use mutual authentication. This will require a manual key exchange between server and each agent that will connect to it.	+	### '''Mutual Authentication (optional)''': Type ‘y’ if you want to use mutual authentication. This will require a manual key exchange between server and each agent that will connect to it.
	# When prompted for database type, specify derby or just press enter as we want to do a default Derby install.		# When prompted for database type, specify derby or just press enter as we want to do a default Derby install.
	# Press enter twice to accept defaults (anthill3/password) as the username/password combination.		# Press enter twice to accept defaults (anthill3/password) as the username/password combination.
	# Once file system installation finishes, select ‘N’ for the Windows Service install (this can always installed manually later).		# Once file system installation finishes, select ‘N’ for the Windows Service install (this can always installed manually later).
	# Once the database installation finishes, press enter a couple of times to exit the installer.		# Once the database installation finishes, press enter a couple of times to exit the installer.
		+	== Database Driver Configuration ==
	# Now that the server is installed, navigate to the server’s lib directory, and create a subdirectory called ‘ext’.		# Now that the server is installed, navigate to the server’s lib directory, and create a subdirectory called ‘ext’.
	# Place your database driver JAR file in this ext directory.		# Place your database driver JAR file in this ext directory.
		+
		+
Line 31:
-	## Installed.properties
		+	=== Installed.properties ===
	### Install.db.type should get the type of database you are going to (for example, mysql for MySQL, oracle for Oracle, sqlserver for SQL Server)		### Install.db.type should get the type of database you are going to (for example, mysql for MySQL, oracle for Oracle, sqlserver for SQL Server)
	### Install.db.url should get the connection string for your database (for example, one for Oracle might look like jdbc:oracle:thin:@oraclebox:1521/ORCL )		### Install.db.url should get the connection string for your database (for example, one for Oracle might look like jdbc:oracle:thin:@oraclebox:1521/ORCL )
Line 35:
	### Install.db.driver needs the class name of the driver (for example, Oracle’s is oracle.jdbc.driver.OracleDriver if using ojdbc6.jar)		### Install.db.driver needs the class name of the driver (for example, Oracle’s is oracle.jdbc.driver.OracleDriver if using ojdbc6.jar)
	### Install.db.user should be replaced with the database user’s username.		### Install.db.user should be replaced with the database user’s username.
-	## Spy.properties
		+	=== Spy.properties ===
	### Find line 42 (should say realdriver=org…) and change the class name of the driver to match with what you specified in the install.db.driver line in installed.properties file.		### Find line 42 (should say realdriver=org…) and change the class name of the driver to match with what you specified in the install.db.driver line in installed.properties file.
	# Navigate to the server’s conf\server\spring-server directory and modify the following files:		# Navigate to the server’s conf\server\spring-server directory and modify the following files:
-	## Base.xml
		+	=== Base.xml ===
	### url should get changed to the connection string specified in installed.properties		### url should get changed to the connection string specified in installed.properties
	### username should get changed to the database user’s username specified in installed.properties		### username should get changed to the database user’s username specified in installed.properties
Line 60:
	Either way, after the clone is complete, you are free to copy over the \var\ directory from the server to the new server’s \var\ directory. This will copy over all old artifacts, job logs, published reports, etc.		Either way, after the clone is complete, you are free to copy over the \var\ directory from the server to the new server’s \var\ directory. This will copy over all old artifacts, job logs, published reports, etc.
-	# Extract the archive to an accessible folder.
-	# From an Administrative Command Prompt, navigate to the extracted anthill3-install directory, and run install-server.bat.
-	# When prompted, provide the following information:
-	## Directory: Directory where you would like the server installed on the new machine
-	## Confirmation: Type ‘y’ if this was the correct directory to install to. Typing ‘n’ will fail the program out.
-	## JDK: Home directory of the JDK
-	## Host: The hostname of the AnthillPro server (the agents will use this to connect to the server)
-	## JMS: The port that the agents will be using for communication (Default is 7915)
-	## Devilfish/Remoting: The port that will be used for remoting connections (Default is 4567)
-	## IP Address: Also known as the ‘Bind-IP’. This is the address the server will bind to (default is all [0.0.0.0]).
-	### HTTPS (optional): Type ‘y’ if you want to use HTTPS protocol to connect to the WebUI, else type ‘n’.
-	### HTTPS Port (optional): Input the secure port that you want the WebUI to listen on (Default is 8443).
-	### HTTP Port: Input the port that you want the WebUI to listen on (Default is 8080).
-	### SSL (optional): Type ‘y’ if you want to use SSL between Server ? Agents. Else type ‘n’.
-	### Mutual Authentication (optional): Type ‘y’ if you want to use mutual authentication. This will require a manual key exchange between server and each agent that will connect to it.
-	# When prompted for database type, specify derby or just press enter as we want to do a default Derby install.
-	# Press enter twice to accept defaults (anthill3/password) as the username/password combination.
-	# Once file system installation finishes, select ‘N’ for the Windows Service install (this can always installed manually later).
-	# Once the database installation finishes, press enter a couple of times to exit the installer.
-	# Now that the server is installed, navigate to the server’s lib directory, and create a subdirectory called ‘ext’.
-	# Place your database driver JAR file in this ext directory.
-	# Ensure that your cloned database (or old database) is running, and you can connect to it.
-	# Navigate to the server’s conf\server directory and modify the following files:
-	## Installed.properties
-	### Install.db.type should get the type of database you are going to (for example, mysql for MySQL, oracle for Oracle, sqlserver for SQL Server)
-	### Install.db.url should get the connection string for your database (for example, one for Oracle might look like jdbc:oracle:thin:@oraclebox:1521/ORCL )
-	### Install.db.password should be replaced with the plaintext password of the database user.
-	### Install.db.driver needs the class name of the driver (for example, Oracle’s is oracle.jdbc.driver.OracleDriver if using ojdbc6.jar)
-	### Install.db.user should be replaced with the database user’s username.
-	## Spy.properties
-	### Find line 42 (should say realdriver=org…) and change the class name of the driver to match with what you specified in the install.db.driver line in installed.properties file.
-	# Navigate to the server’s conf\server\spring-server directory and modify the following files:
-	## Base.xml
-	### url should get changed to the connection string specified in installed.properties
-	### username should get changed to the database user’s username specified in installed.properties
-	### password should get changed to the plaintext database user’s password specified in installed.properties
-	# Finally, ensuring that all the correct values are specified, you should be able to start your server and have it connect to the cloned database (or old database depending if you cloned the database or not).
-	An alternative method (as found http://documentation.urbancode.com/anthill3-help-3.8/html/CloneAnthillpro.html) is available as well:
-	# Install the new AnthillPro server and instruct it to connect to a new empty database created specifically for the instance.
-	# Modify the production server to ensure that it is configured to bind to the address: 0.0.0.0 on startup. Go to System