Revolution R Enterprise DeployR 7.1 Installation Guide for Windows

Transcription

1 Revolution R Enterprise DeployR 7.1 Installation Guide for Windows

2 The correct bibliographic citation for this manual is as follows: Revolution Analytics, Inc Revolution R Enterprise DeployR Installation Guide for Windows. Revolution Analytics, Inc., Mountain View, CA. Revolution R Enterprise DeployR Installation Guide for Windows Copyright 2014 Revolution Analytics, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Revolution Analytics. U.S. Government Restricted Rights Notice: Use, duplication, or disclosure of this software and related documentation by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of The Rights in Technical Data and Computer Software clause at Revolution R, Revolution R Enterprise, RPE, RevoScaleR, DeployR, RevoTreeView, and Revolution Analytics are trademarks of Revolution Analytics. Other product names mentioned herein are used for identification purposes only and may be trademarks of their respective owners. Revolution Analytics 2570 West El Camino Real Suite 222 Mountain View, CA, USA We want our documentation to be useful, and we want it to address your needs. If you have comments on this or any Revolution document, write to [email protected].

3 Contents Chapter 1: Before You Begin...1 System Requirements...1 Migrating to DeployR Setting Up DeployR on Amazon Web Services...2 What s New in DeployR...2 Software Dependencies...4 DeployR Configurations...5 Chapter 2: Installing DeployR...7 Chapter 3: Post Installation Configuration...9 Updating Firewall with Non-Default Ports...9 Customizing Settings in the Administration Console...9 Configuring the DeployR Grid...10 Configuring External Directories for Big Data...11 DeployR s External Directory Structure Getting Files into the External Directory Share How to Reference Files in External Directories How to Write Data Files to External Directories Defining a SSL Certificate for Secure Communication...13 Configuring Enterprise Security...15 Chapter 4: Getting Started with DeployR...17 Accessing DeployR Home Page to Test Install...17 Exploring the API...17 [i]

4 Contents Exploring JavaScript Samples...18 Chapter 5: Stopping and Starting DeployR...19 Stopping Services...19 Starting Services...19 Chapter 6: Troubleshooting Tips...21 [ii]

5 Revolution R Enterprise DeployR Installation Guide for Windows Before You Begin 1 1 System Requirements Before you start the Revolution R Enterprise DeployR installation, make sure the computer meets the minimum hardware and software requirements. Operating system. Windows Server 2008 R2 (Service Pack 1) and Windows Server 2012 for 64-bit processors Hardware. Intel Pentium -class processor; 3.0 GHz recommended Free disk space. 250 GB or more recommended RAM. 4 GB or more is recommended Java JVM Heap Size. 1 GB or more in production Swap space. 8 GB or more for larger data sets is recommended Internet access and browser. To download DeployR and to interact with the Administration Console, API Explorer Tools, and samples. If using Microsoft Internet Explorer, use version 8 or later. Important! We recommend installing DeployR on a dedicated server machine. To install properly, you must have administrator privileges. Migrating to DeployR 7.1 If you are an existing customer, please carefully consult the Revolution R Enterprise DeployR Migration Guide before you install DeployR 7.1. This guide will explain how to migrate users, scripts, projects, and other data. Additionally, you can learn about troubleshooting as well as preserving and updating JavaScript application files.

6 2 Chapter 1: Before You Begin Setting Up DeployR on Amazon Web Services For each Amazon EC-2 instance, make sure you have: Have the minimum required disk space (or more) for the installation of DeployR software and its database Set the appropriate security permissions on the external and internal ports used by DeployR by performing the following: a. Disable iptables (Linux only) b. Open the DeployR external ports, which is 7100 by default, through the AWS console Change the passwords to the default DeployR user accounts immediately after installing DeployR, especially the admin account. What s New in DeployR Revolution R Enterprise DeployR 7.1 With this release, RevoDeployR is now called Revolution R Enterprise DeployR, or DeployR for short. We ve also introduced the DeployR Repository Manager, which is a tool that simplifies the task of managing repository files. Authenticated DeployR users can use the Repository Manager to manage repository files (R scripts, data files, and so on) as well as interact with their R scripts in a live debugging environment. Note that the script management functionality formerly found in the RevoDeployR Management Console is now contained in the Repository Manager. This tool can be accessed through the DeployR landing page. The Management Console has been renamed to the Administration Console. Other changes to that console include: o The Administration Console can only be accessed by the admin user. o All R script management functionality, other than import and export of R scripts, has been moved to the Repository Manager. o The user testmanager and the role SCRIPT_MANAGER were obsoleted and removed when script management functionality was moved to the DeployR Repository Manager.

7 Revolution R Enterprise DeployR Installation Guide for Windows 3 There is new and updated API support, including new directory support on the Repository APIs. Refer to the 7.1 Change History section in the API Reference Guide for details. The default installation port numbers have changed for this version. RevoDeployR 7.0 This release contains new features and improvements, including: New and updated API support including: o Support for user blackbox projects, which are a new type of secure temporary project for authenticated users o Support for HTTP blackbox projects, which are a new type of secure, stateful project for anonymous users o Support for creating pools of temporary projects on the /r/project/pool API o New standardized set of parameters across all execution APIs o New R script execution chaining support on all script execution APIs o New role-based restricted access control for files on the Repository APIs o For JavaScript developers, server-side events pushed on new /r/event/stream API o For an overview of additions and updates to the API for this release please refer to the section API Change History on the documentation landing page ( New Event Stream Console, which is a browser-based console window for viewing /r/event/stream events. This console is integrated into the management console, the API Explorer tool, and the JavaScript sample applications delivered with RevoDeployR. The management console was updated to include: o The creation and use of custom roles to restrict access to R scripts and event streams o Private, Restricted, Shared and Public access controls for R Scripts o Validation of grid node configurations upon creation, update, and import o New event stream access policies under Server Policies RevoDeployR 6.2 This release contains new features and improvements, including: New API support for: o Priority scheduling for asynchronous jobs

8 4 Chapter 1: Before You Begin o Executing scripts found on external URLs or file paths including scripts in GIT and SVN repositories o The lifecycle management of repository-managed files, including scripts o Enhanced file versioning for repository-managed files, including scripts New pre-authentication support for the users that have been reliably authenticated by an external system such as CA Siteminder A new high-performance, scalable persistence infrastructure, which is built on top of the MongoDB NoSQL database, to manage the reliable persistence of all user, project and repository data Updated documentation and accompanying sample applications Updated Javascript, Java,.NET client libraries A new RevoDeployR Deployment Planning Guide is now available to help administrators plan the provisioning of server and grid capacity Removed dependency on Apache HTTP Server Software Dependencies During the automated DeployR installation, the installer will install and configure the following software dependencies for you. For the DeployR main server, the dependencies are: o Rserve o Apache Tomcat o Java JRE 7 o MongoDB version For a DeployR grid node, the dependencies are: o Revolution R Enterprise 7.1 (and all of its dependencies) o Rserve Important! Revolution R Enterprise 7.1 (and all of its dependencies) must be installed on the main server machine and each node before installing DeployR as described in the section Installing DeployR.

9 Revolution R Enterprise DeployR Installation Guide for Windows 5 DeployR Configurations DeployR can be configured in several ways based on your organization s needs. ` Figure 1. DeployR Configurations Single Host Configuration The first configuration consists of a single host machine. To use this configuration, install the following components on one machine using the instructions in this guide: 1. Install Revolution R Enterprise. 2. Install DeployR. Note: The installation process includes the installation and configuration of some of the prerequisites for Revolution R Enterprise. Multiple Host Configuration The second configuration supports multiple hosts on which the components needed for DeployR are installed and configured. This configuration allows you to use a network of cooperating grid nodes configured on multiple hosts. This network of grid nodes supports the dynamic scaling of R processing resources in the server back-end.

10 6 Chapter 1: Before You Begin To use this configuration, install the following components in order using the information in this guide: 1. On the Host 1, install Revolution R Enterprise and then DeployR using the installation instructions presented in Chapter On each separate host, perform the following steps for each grid node: a. Install the dependencies listed in this guide for a DeployR grid node. b. Install the DeployR grid node using the instructions in Chapter 2. Notes: The installation process includes the installation and configuration of some of the prerequisites for Revolution R Enterprise. You can configure these nodes later in the Management Console after you have completed the installation. Learn how to manage and configure grid nodes in the Revolution R Enterprise DeployR Administration Console Guide.

11 Revolution R Enterprise DeployR Installation Guide for Windows Installing DeployR 2 7 Important! Run the installer once for the DeployR main server and then again on each machine on which you want a grid node. 1. Log into the operating system on which you will install as a user with administrator rights. 2. Install Revolution R Enterprise before installing DeployR. Contact Revolution Analytics for a link to the proper version of Revolution R Enterprise. If the recommended version of Revolution R Enterprise is already installed, skip forward to the next section to install DeployR. Note: For assistance during the installation, please refer to the Revolution R Enterprise installation instructions contained in the welcome letter you received. To install, do the following: a. Launch the Revolution R Enterprise installer file. b. Accept the default settings during the installation process. c. When prompted, enter the serial number included in the welcome letter you received from Revolution Analytics. 3. Using the links provided in your welcome letter from Revolution Analytics, download and execute the DeployR installer files: o For the main server, download DeployR exe. o For additional grid nodes, download DeployR-Node exe. 4. If a message appears onscreen during installation asking whether you want to allow the following program to make changes to this computer, click Continue. 5. During a main server install, you can choose to use the default installation directory or enter a unique directory path for this version of DeployR.

12 8 Chapter 2: Installing DeployR 6. Follow the onscreen prompts to complete the installation. 7. After the installation wizard completes, a configuration script is launched. This script begins by making backup copies of the files that will be changed. Each backup file uses the original name but with the suffix YYYY-MM-DD_HH-MM such as deployr.groovy _ Also, a log file %TEMP%\DeployR-configuration.log is generated to record the steps taken during this configuration process. This step can take a few minutes. 8. If configuring a grid node, enter the IP address to the main DeployR server. 9. When configuration is complete, press the Enter key to exit the configuration. Important! For the best results, respect the order in which information is presented in this chapter when configuring DeployR.

13 9 Revolution R Enterprise DeployR Installation Guide for Windows Post Installation 3 Configuration Updating Firewall with Non Default Ports During installation, the Windows Firewall was updated to allow inbound communications to DeployR on the ports listed in the following table. If you have made any changes to the port numbers designated for communications between DeployR and any of its dependencies, add those port numbers instead Customizing Settings in the Administration Console The DeployR Administration Console is used to manage the integration of Web or desktop client applications with the DeployR Web services API. 1. If you want the DeployR server to be publicly accessible outside the firewall, make the appropriate changes to your firewall. 2. Go to the DeployR Administration Console at: where <DEPLOYR_SERVER_IP> is the IP address of the DeployR machine. 3. Log in as the default administrator using the following: username: admin password: secret

14 10 Chapter 3: Post Installation Configuration 4. In the Users tab, change the default password for the admin account to a password of your choosing. We also recommend that you change the passwords to the other default user accounts. 5. Verify that the appropriate server IP address and port number are present in the Server web context setting in the Server Policies tab. Note: In some cases, the wrong IP address may be automatically assigned during installation or when the machine is rebooted, and that address may not be the only IP address for this machine or may not be publicly accessible. If this case, you must update the address here. a. In the Server Policies page, click Edit. b. Make sure the IP address and port number are correct in the Server web context setting. For example, c. Set the Disable IP auto-detection to true. 6. For each grid node you install as well as the DeployR Default Node that was installed for you, use the instructions in Configuring the DeployR Grid to define and configure each node. Configuring the DeployR Grid You can expand the Grid framework for load distribution by configuring each node you installed earlier in the DeployR Administration Console. Note: For detailed instructions on grid node configurations, refer to Revolution R Enterprise DeployR Administration Console Guide. 1. Go to the landing page at where <DEPLOYR_SERVER_IP> is the IP address of the DeployR machine. 2. Click the Administration Console link. 3. Login using the administrator account: username: admin default password: secret 4. Click The Grid in the main menu.

15 Revolution R Enterprise DeployR Installation Guide for Windows If any grid nodes were installed, besides the DeployR Default Node, click New Grid Node and configure the following settings for each node. For more information on these settings, refer to the Revolution R Enterprise DeployR Administration Console Guide. In particular, do the following: a. Select the Enabled checkbox to activate the node on the grid. b. Enter a name in the Name field. c. Enter an IP address in the Host field. Hostname or IP on which the node is configured. The DeployR Default Node is configured on localhost. d. Specify the Operating Type. The operating mode you define for a grid node has an impact on the operations you can perform on that node. e. Under External directory configuration, set the Storage Context to reflect the full path to the external data directory on that node s machine. The default path is: C:/Revolution/DeployR-Node-7.1/deployr/external/data Configuring External Directories for Big Data Whenever data is too big to be stored out on the Web or on a user s machine, those files can be stored in 'big data' external directories on the DeployR main server that are set up and managed by an administrator. These big data directories can then be referenced by projects without the overhead of replicating the big data itself for each individual project. Important! To use external directories, the administrator must install and mount NFS the following directory on both the DeployR main server and each grid node: <INSTALL_DIR>/deployr/external Where <INSTALL_DIR> is the directory into which you installed DeployR. By default, that directory on the main server is: C:\Revolution\DeployR-7.1. DeployR s External Directory Structure The external directory structure is really a tree of public and private directories hanging off a common base directory. For example, if the base directory on the main server is C:/Revolution/DeployR-7.1/deployr/external/data, then the base external directory structure might look: C:/Revolution/DeployR-7.1/deployr/external/data/public

16 12 Chapter 3: Post Installation Configuration C:/Revolution/DeployR-7.1/deployr/external/data/testuser C:/Revolution/DeployR-7.1/deployr/external/data/user1 Two directories are automatically created by the server the first time the corresponding user logs into the system. The first directory is called /public and contains the files that can be read by any authenticated users on the server. The second directory is the user s private directory. Each private external directory can be found at: C:/Revolution/DeployR- 7.1/deployr/external/data/{deployr_username}. Files in each private directory are available only to that authenticated user during a live session. The administrator can also manually create these subdirectories in advance. The names of the directories are case-sensitive. For example, the user testuser will have access to both the files under the private external directory, C:/Revolution/DeployR-7.1/deployr/external/data/testuser, as well as the files under the public directory, C:/Revolution/DeployR- 7.1/deployr/external/data/public. It is up to the administrator to inform each user of which files are available in the \public directory and which files are in their private directory. When referencing a file that is stored in the \public directory, the user must explicitly declare its public location in the call as described later in this section. Getting Files into the External Directory Share Files can be added to the external directories in one of two ways. Users can request that files be placed in their private external directories or the public directory by the administrator. Alternatively, users can execute code that will write files directly into their own directories. Ultimately, the administrator is responsible for moving and managing files in the external directories as well as informing users that the files exist and their whereabouts. To reference one of these files in the code, a user must declare and, therefore, know if the given file is stored in the public subdirectory or the user's private subdirectory. Note: Currently there is no user interface to display the names of the files in this directory. Additionally, due to the potentially large size of the data, we do not expose any API or other facility for moving data into the external directories. How to Reference Files in External Directories Whenever a user references a file in an external directory, that user must wrap the filename on a standard R call with the custom R function deployrexternal(). By default, it is assumed that the file is in the user s private directory. Here is an example of such a call: sampledata <- read.csv(file=deployrexternal("my_simple.csv"))

17 Revolution R Enterprise DeployR Installation Guide for Windows 13 However if the file is in the public external directory, the public nature of the file must be declared using the ispublic parameter set to true, as follows: sampledata <- read.csv(file=deployrexternal("shared_simple.csv", ispublic=true)) The following example references a big data (.XDF) file from ScaleR. In this example, the public file mydatafile.xdf is read and stored as a dataframe called mydataframe. mydataframe <-RxXdfData(deployrExternal('mydatafile.xdf')) How to Write Data Files to External Directories Whenever you want to write a file to your private external directory, you wrap the filename on a standard R call using the function write.csv as follows: write.csv(file=deployrexternal("my_simple.csv")) You cannot write a file to the public directory. The following is an example that takes a dataframe and writes it out into our big data format (.XDF). In this example, the data mydataframe, which is stored in memory, is written out to a file called mydatafile.xdf. rxdataframetoxdf(data=mydataframe, outfile=deployrexternal('mydatafile.xdf'), overwrite=true) Defining a SSL Certificate for Secure Communication To make APIs and the DeployR Administration Console publicly accessible, define an SSL certificate to secure the communications that use HTTPS. Important! The following instructions are for the DeployR main server only and are not needed for the grid node machines. 1. If you do not currently have a registered certificate, create a temporary keystore containing a self-signed certificate, for Tomcat SSL on the server machine for testing purposes. For more information on creating a certificate keystore, visit the apache.org website. We recommend using a registered certificate as soon as possible.

18 14 Chapter 3: Post Installation Configuration a. Launch a command window as administrator. b. At the DOS command prompt, type: "C:\Program Files\Java\jre7\bin\keytool" -genkey -alias tomcat - keyalg RSA -keystore "C:\Revolution\DeployR- 7.1\Apache_Tomcat\bin\.keystore" Important! Use the password changeit for this temporary keystore. 2. Copy the certificate keystore (registered or temporary self-signed) to the Tomcat directory so that the keystore can be deployed at startup. At the prompt, type: copy.keystore C:\Revolution\DeployR-7.1\Apache_Tomcat\bin\.keystore 3. Change directories. At the prompt, type: cd C:\Revolution\DeployR-7.1\installFiles\ 4. Define the configuration property by opening the file C:\Revolution\DeployR- 7.1\deployr.groovy. a. Locate the following line and change false to true: grails.plugins.springsecurity.auth.forcehttps = false b. Uncomment the following lines: grails.plugins.springsecurity.portmapper.httpsport=7101 grails.plugins.springsecurity.portmapper.httpport=7100 c. Save and close the file. 5. Edit the file C:\Revolution\DeployR-7.1\Apache_Tomcat\conf\server.xml to define and enable the port Apache should use to communicate with Tomcat. Locate the following lines and remove the comments surrounding this code:<!-- <Connector port="7101" protocol="org.apache.coyote.http11.http11nioprotoocol" compression="1024" compressablemimetype="text/html,text/xml,text/json,text/plain,application/x ml,application/json,image/svg+xml" SSLEnabled="true" maxthreads="150" scheme="https" secure="true" clientauth="false" sslprotocol="tls" keystorefile="c:\revolution\deployr-7.1\apache_tomcat\bin\.keystore" /> -->

19 Revolution R Enterprise DeployR Installation Guide for Windows Restart Tomcat for the change to take effect. net stop Apache-Tomcat-for-DeployR-7.1 net start Apache-Tomcat-for-DeployR Test these changes by visiting DeployR Administration Console at where <DEPLOYR_SERVER_IP> is the IP address of the DeployR machine and where <PORT> is the port number for tomcat. The default port for tomcat is Configuring Enterprise Security DeployR is a server framework that exposes the R platform as a service to allow the integration of R statistics, analytics, and visualizations inside Web, desktop, and mobile applications. In addition to providing a simple yet powerful Web services API, the framework also supports a highly-flexible, enterprise security model. Learn more about this model by reading the Revolution R Enterprise DeployR Enterprise Security Guide.

20 16 Chapter 3: Post Installation Configuration

21 17 Revolution R Enterprise DeployR Installation Guide for Windows Getting Started with 4 DeployR Accessing DeployR Home Page to Test Install After installing and configuring DeployR, verify that DeployR is accessible. 1. Make sure you can access the DeployR home page located here: where <DEPLOYR_SERVER_IP> is the IP address of the DeployR machine. 2. In this page, you can explore product documentation, the DeployR Administration Console, the API Explorer tool and some JavaScript examples. Exploring the API You can familiarize yourself with API using the API Explorer, which is a development tool to help the application developer test the APIs that make up DeployR. This tool is not intended as a sample application or an end-user application. For more information on the API Explorer tool, refer to API Explorer - Reference Documentation. Important! Adobe Flash Player is required on the machine accessing the API Explorer tool. 1. Before launching the API Explorer, we recommend that you clear your browser s cache. This is particularly useful after upgrading. 2. Make sure you can access the DeployR home page located here: where <DEPLOYR_SERVER_IP> is the IP address of the DeployR machine. 3. Click API Explorer. 4. Log into using the admin account.

22 18 Chapter 4: Getting Started with DeployR Exploring JavaScript Samples Learn more about creating your own applications and using the client libraries from the JavaScript samples installed with DeployR. 1. Make sure you can access the DeployR home page located here: where <DEPLOYR_SERVER_IP> is the IP address of the DeployR machine. 2. Click Examples. 3. Click the link to the sample you want to explore.

23 19 Revolution R Enterprise DeployR Installation Guide for Windows Stopping and Starting 5 DeployR Stopping Services To stop DeployR-related services, type the following at the DOS command prompt: net stop Apache-Tomcat-for-DeployR-7.1 net stop Rserve7.1 net stop MongoDB-DeployR-7.1 Starting Services To start DeployR-related services, type the following at the DOS command prompt: net start Apache-Tomcat-for-DeployR-7.1 net start Rserve7.1 net start MongoDB-DeployR-7.1

24 20 Chapter 5: Stopping and Starting DeployR

25 Revolution R Enterprise DeployR Installation Guide for Windows Troubleshooting Tips 6 21 Multiple User Sign-ins You cannot log into DeployR from two different accounts within the same brand of browser program. To use two or more different accounts, you'll need to log into each one in a separate brand of browser. For example, to log into the DeployR Administration Console with admin account and into the API explorer tool with another user account, open one in Google Chrome and the other in Mozilla Firefox. DeployR Doesn t Work after Reinstalling Revolution R Enterprise If DeployR stops working after you have uninstalled and then reinstalled Revolution R Enterprise, we recommend that you manually run the DeployR configuration step again as follows: 1. Open a command prompt window. 2. At the prompt, type: CD <DEPLOYR_INSTALL_DIRECTORY>\DeployR-7.1 Where <DEPLOYR_INSTALL_DIRECTORY> is C:\Revolution by default. 3. Reconfigure DeployR. At the prompt, type: DeployR-Config.exe -t server -a configure Cannot Access DeployR After Install During the installation of DeployR on Windows, the 'Domain' profile is used to create inbound exceptions for the ports used by DeployR. These settings may need to be adjusted after installing to meet the needs of your deployment.

26 22 Chapter 6: Troubleshooting Tips Access Denied to Tomcat If you reboot after installing and get an access error message for Tomcat, you can specify that Tomcat should be run as an administrator to stop the message from appearing. The error is related to Tomcat7w.exe, which is an application for monitoring and configuring Tomcat services. The error message is: Access is denied. Unable to open the service Tomcat To set Tomcat program to run as an administrator, do the following: 1. Right-click tomcat7w.exe and choose Properties from the shortcut menu. tomcat7w.exe is a GUI application for monitoring and configuring Tomcat services. 2. In the Properties dialog, select the checkbox Run this program as an administrator checkbox in the Privilege Level area. 3. Click OK. 4. Launch DeployR again. Cannot See Latest API Explorer Interface 1. Ensure Adobe Flash Player is installed and configured to work with your browser. 2. Clear your browser s cache before launching the API Explorer tool. This is particularly important if you are upgrading from a previous version of DeployR. Unable to Run Examples Unable to run the example applications accessible through the product landing page at /revolution/docs/examples/ where <DEPLOYR_SERVER_IP> is the IP address of the DeployR machine. This issue can occur in the following cases: If you attempt to run a sample in Microsoft Internet Explorer 7 and get a JSON is undefined browser error, then upgrade to Internet Explorer 8 or newer and try again. If you installed grid nodes for DeployR and you cannot run all of the samples delivered with the product, then the operating type of the grid node(s) might be incorrectly defined. The operating mode you define for a grid node has an impact on the operations you can perform on that node. To be able to run all samples delivered with this product or to run anonymous or asynchronous jobs, make sure you have one node configured for each required operating type or at least one grid node set to the Mixed mode operating type.

27 Revolution R Enterprise DeployR Installation Guide for Windows 23 For more information, please read the Revolution R Enterprise DeployR Administration Console Guide. No Plot Displayed for Code Execution Example If you ran the Code Execution example but no plot was returned, then the wrong IP address may be defined for DeployR. While, by default, an IP address is automatically detected during installation or any time the server is booted, there are cases where the IP that was automatically detected is not the correct for DeployR. This may be due to the fact that there are multiple IP addresses for the machine and the auto-detected IP is not publicly accessible or the IP address of the server has changed. To fix this issue, you can impose an IP temporarily or permanently in the Server Web Context in the Server Policies tab of the Administration Console. Changing Port Numbers for Tomcat If you run into conflicts with other applications, consider changing the port numbers. You only need to change the port numbers of those applications that are actively conflicting. Consequently, not all of the following steps may apply to your situation. 1. In the Tomcat 7.1 directory, open the file server.xml: a. Find the port= 7100 and change to a new port number such as port= b. Save the file. 2. Restart Tomcat for the changes to take effect. net stop Apache-Tomcat-for-DeployR-7.1 net start Apache-Tomcat-for-DeployR-7.1