Server Installation and Administration Guide

Transcription

1 NetApp Connect 5.1 Server Installation and Administration Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA U.S. Telephone: +1 (408) Fax: +1 (408) Support telephone: +1 (888) Web: Feedback: Part number: _A0 November 2014

2

3 Table of Contents 3 Contents Product overview... 6 What you can do with NetApp Connect... 7 Languages supported in NetApp Connect files... 7 How NetApp Connect works... 7 Where to find more information about NetApp Connect... 8 NetApp Connect information on the web... 8 Planning your deployment NetApp Connect architecture NetApp Connect server requirements reference System memory requirements for NetApp Connect components NetApp Connect supporting software Licensing information NetApp Connect security features Access control in NetApp Connect NetApp Connect installation checklist NetApp Connect installation data worksheet Deployment examples Single NetApp Connect server in a monolithic deployment Distributed satellite NetApp Connect servers Installing the NetApp Connect server and components Downloading the NetApp Connect software Installing the NetApp Connect server Installing the Microsoft SQL Server JDBC driver Configuring essential NetApp Connect components Setting up certificates, database options, and component engines with the Quick Start Configuration wizard Starting and stopping the NetApp Connect server Accessing the NetApp Connect Dashboard Configuring NetApp Connect to use Active Directory Adding repositories Viewing license information Creating a certificate for SAML message signing... 46

4 4 NetApp Connect 5.1 Server Installation and Administration Guide Configuring SAML for authentication and authorization Configuring HTTP Relay for authentication and authorization Configuring partner information Configuring the reverse proxy Provisioning user access Upgrading NetApp Connect Uninstalling NetApp Connect Configuring advanced NetApp Connect options Installing satellite Domain Storage Engine components Advanced NetApp Connect Application Boot Manager configuration options Accessing NetApp Connect Application Boot Manager Changing your NetApp Connect Application Boot Manager password Starting and stopping the NetApp Connect server Viewing license information Accessing the Dashboard from the Application Boot Manager Viewing server identity using Application Boot Manager Configuring the NetApp Connect Message Broker Configuring the NetApp Connect Policy Engine Configuring the NetApp Connect Domain Storage Engine Configuring for cluster environments by exporting data Changing NetApp Connect ports Configuring the session timeout Viewing NetApp Connect server status logs Advanced NetApp Connect Dashboard configuration options Accessing the NetApp Connect Dashboard Changing your NetApp Connect Dashboard password Reviewing recent NetApp Connect events in the Dashboard log Viewing users with active sessions Configuring users' home folders Setting filters to govern file access Configuring NetApp Connect policies Configuring LDAP for NetApp Connect Troubleshooting on the NetApp Connect server Troubleshooting with NetApp Connect logs Creating a trace-level NetApp Connect log Application Boot Manager not running... 84

5 Table of Contents 5 NetApp Connect server not running Unable to log in to NetApp Connect Error message 1: Internal server error Error message 12: Invalid login Error message 15: Undeliverable Copyright information Trademark information How to send your comments Index... 91

6 6 NetApp Connect 5.1 Server Installation and Administration Guide Product overview NetApp Connect enables users to access on-premises data from existing enterprise collaboration, file synchronization, and share applications quickly and securely, across devices they choose to use. Enterprise information remains managed by your company and stored on premises. NetApp technology partners already offer software on mobile devices, desktops, and web browsers that enables access to public cloud resources. With NetApp Connect, partners can now integrate access to on-premises data and applications. To safeguard corporate data, you can set policies in the NetApp Connect server, which is deployed behind your enterprise firewall. You determine which groups can access which repositories of data and specify whether they can change or delete that data. NetApp Connect provides you with the following benefits: Secure access to business files, even files that are accessed via public or private cloud file sharing applications, making collaboration with colleagues and external partners safe and easy Ability to leverage existing investments in servers, networking, and storage infrastructures Enterprise-class security, authentication, and access controls Support for Windows home directories, other CIFS file shares, and data in SharePoint 2010 Support across the devices that employees use, including mobile clients, desktop access, or partner-enabled, browser-based access

7 Product overview 7 What you can do with NetApp Connect NetApp Connect uses a combination of cloud-sharing or mobile applications already provided by technology partners, a connection to a NetApp Connect server, and documents and files stored on the enterprise server. Using cloud-sharing or mobile applications and the NetApp Connect server, you can accomplish a variety of user goals. Using the NetApp Connect server and cloud sharing or collaboration partner applications, you can accomplish the following: Access your on-premise files securely and reliably, even files in public or private clouds. Display Microsoft Office files, SharePoint files, or file shares using a mobile device, desktop, or browser. Securely browse the Internet and your intranet with enterprise policies that govern access. Save files locally for offline viewing (access governed by server policies). Send files to and receive files from other applications (access governed by server policies). Using the NetApp Connect server, you can accomplish the following: Configure the server and enterprise repositories for cloud sharing and mobile access. View license information. Configure identities and authentication. Create and manage repositories and provision user access to those repositories. Configure filters to allow or prevent access to specific file formats. Languages supported in NetApp Connect files You can use non-english (Unicode) characters as content within documents, file names, folder names, and realm names. There is no limitation on the character sets used within documents. As you implement NetApp Connect in your environment, it is helpful to understand supported languages. How NetApp Connect works NetApp Connect uses a combination of interfaces provided by technology partners, an API connection to a NetApp Connect server, and access to on-premise files and applications through the interface. You can use the server to manage the system and its users. The following image shows the high-level NetApp Connect architecture:

8 8 NetApp Connect 5.1 Server Installation and Administration Guide The NetApp Connect server provides the following: A module for handling API requests from partners over an HTTP (or HTTPS) connection A module that enables users to log in using corporate credentials Sample code that partners can use Modules to handle provisioning and tracking of third-party partner applications When a user accesses the interface, it connects to a messaging broker through the API and begins communicating with the NetApp Connect server. The server analyzes information such as file formats, policies governing user file access, and rules governing the processing of different types of files. The server then serves file information back to the interface through the API. Where to find more information about NetApp Connect You can find more information about NetApp Connect on the NetApp Support Site at mysupport.netapp.com and in other NetApp Connect documentation. NetApp Connect information on the web For additional information about NetApp Connect, you can use the NetApp web site resources. The NetApp Connect product web site at

9 Product overview 9 The NetApp Support Site at mysupport.netapp.com The Interoperability Matrix at mysupport.netapp.com/matrix

10 10 NetApp Connect 5.1 Server Installation and Administration Guide Planning your deployment To ensure a successful deployment, you should review architectural information and system requirements before you install NetApp Connect. Planning your deployment involves reviewing the following NetApp Connect information: Architectural information Server components Server requirements Memory requirements for components Supporting software Licensing information Deployment examples You might also benefit from using the installation checklist and data worksheet. Related references NetApp Connect installation checklist on page 17 NetApp Connect installation data worksheet on page 18 NetApp Connect architecture NetApp Connect employs an architecture that consists of a NetApp Connect server, a third-party interface, and an API connection. Together, these components enable users to view files from their hybrid clouds, collaborative applications, or mobile devices while administrators control that user experience. NetApp Connect uses the following architecture: Server that handles business logic Enables administrators to configure server options, provision users, set business policies, and provide access to files through HTTP API requests to the interface. Administrators use the NetApp Connect server Dashboard to configure these options. Third-party interface Enables users to view their enterprise files on multiple devices easily and securely. The interface receives a compressed and encrypted format of users' files. Reverse proxy in DMZ

11 Planning your deployment 11 Enables cloud applications to access the on-premises NetApp Connect server. API connection Storage Enables RESTful HTTP or HTTPS requests to be sent from the interface to the server. HTTP responses return the status to the interface. Stores CIFS file shares and SharePoint data. The following image shows the architecture components: The software services are typically deployed on a single virtual or physical server. All components are connected using an Advanced Message Queuing Protocol (AMQP) message bus, an open-standard application-layer protocol for message-oriented middleware. Server administration components Administrators use the following web applications for NetApp Connect server administration: Component Application Boot Manager (ABM) Administrator Dashboard (AD) Description Enables you to stop and start the server engine, access logs, manage broker certificates, and manage messaging. Every NetApp Connect node in a server configuration includes one Application Boot Manager (ABM) for local node management. Is the primary interface for server administrators. Administrators use the Dashboard to configure the source locations of files that become available for remote users and to configure the policies that govern access to those files. Only one NetApp Connect server node includes the Dashboard, and it is typically the same node on which the Policy Engine (PE) resides.

12 12 NetApp Connect 5.1 Server Installation and Administration Guide Server components The NetApp Connect server includes the following components: Component Policy Engine (PE) Domain Storage Engine (DSE) Internal Broker (IB) HTTP Relay SAML Bridge Reverse Proxy Description Handles authentication and enforces the business rules that apply to users and documents. By default, PE extends the existing document policy to client application users; however, PE can also accommodate custom business logic. This is a stand-alone Java application. Provides an interface to the authentication directory. Integrates file repositories, SharePoint repositories, and CIFS shares to a repository for all users' storage needs. Often, deployments include multiple DSEs. This is a stand-alone Java application. Passes messages among the internal components (PE, DSE). Every NetApp Connect server has at least one IB: usually, one per node. This is a stand-alone Erlang application that is not accessible by external users. Provides a RESTful API gateway. Provides a Security Assertion Markup Language (SAML) authentication interface. Provides a hosted web server in your corporate DMZ that forwards HTTPS traffic to the HTTP Relay or authentication SAML component. Enables the cloud applications to access the onpremises NetApp Connect server. You should configure SSL on the reverse proxy and use a signed SSL certificate. NetApp Connect server requirements reference The NetApp Connect server, a computer running Microsoft Windows, requires a specific operating system, minimum amounts of memory, minimum CPU cores, and minimum disk space. Memory shortages or not meeting these requirements can significantly impact the performance and application user experience. The following are general requirement guidelines. For specific guidance for your environment, you should contact your Sales Engineer.

13 Planning your deployment 13 Component Operating system Minimum requirement Computer running Microsoft Windows Server 2008 R2 with the latest service pack Run on a dedicated server. This includes the required Active Directory feature. SharePoint SharePoint version 2010 Virtual machine (VM) Available memory and CPU Available disk space Network The server can also be run on a virtual machine. Run on a dedicated server with no other management utilities other than those required for your Windows environment. 6.0 GB of available memory If you are using a distributed cluster with different identities on different machines, 3.5 GB suffices. If several services are installed and consuming memory on a server with 4 GB of installed memory, the NetApp Connect system might not have enough free memory to run the service. 100 GB of free disk space Requirements vary, depending on whether you are installing on a single or multiple servers and on the components you enable per machine or node. If you are deploying NetApp Connect in production, reserve 500 GB or larger of cache on external storage. Ethernet connection and ports: 1 Gbps Ethernet connection with dedicated (static) IP address is required. Ideally, the host name should be registered in DNS. Available ports for NetApp Connect are 80, 443, 8080, 4369, and Databases NetApp Connect supports PostgreSQL or Microsoft SQL Server and includes an embedded database. You might want to use the embedded database for testing or labs; however, you should use the external databases for production. If you want to use a different external database than the embedded one, you must set up databases prior to installation.

14 14 NetApp Connect 5.1 Server Installation and Administration Guide Component Dashboard browser Permissions Remote connectivity Accessibility Virus scan Security Minimum requirement You must use a browser other than Internet Explorer 9 in enhanced security mode (which Windows Server 2008 R2 runs by default). For installation, you should use Firefox; however, for administration, you can use Firefox, Chrome, or Internet Explorer. Local administrator permissions are required to install NetApp Connect. Internet connectivity must be available to allow WebEx access or a remote desktop connection to facilitate installation and postinstallation support. HTTP, HTTPS, or FTP access to the Internet is highly recommended. The NetApp Connect folders and subfolders should be excluded from any virus scan applications. The dedicated NetApp Connect server must meet your company's security standards. System memory requirements for NetApp Connect components When you are planning your server configuration, you must consider the minimum system memory requirements for NetApp Connect components, including those for the NetApp Connect Application Boot Manager (ABM) component. Node NetApp Connect components Minimum system memory required Monolith (all engines on one server and no clustering) Broker, ABM, PE, DSE, Dashboard, HTTP Relay, SAML 6 GB Policy Engine (PE) Broker, ABM, PE 3 GB Domain Storage Engine (DSE) Broker, ABM, DSE 3.5 GB Satellite DSE Satellite DSE 3.5 GB

15 Planning your deployment 15 NetApp Connect supporting software Using NetApp Connect requires you to use several third-party software components. The NetApp Connect server installation provides these components. Depending on your requirements, you might require additional software such as an external database and reverse proxy OS (for example, Linux or Windows) that are not part of this software installation. Apache Tomcat Erlang Apache Tomcat is an enterprise Java application container used to host components, including the Dashboard, Application Boot Manager (ABM), HTTP Relay, and the Security Assertion Markup Language (SAML) authentication bridge. Both the Dashboard and Application Boot Manager (ABM) applications are deployed as web application resource (WAR) files. While the Dashboard can be hosted in a central Tomcat installation, ABM and thus Tomcat must run on each node in the system. Neither component relies on proprietary Tomcat extensions, so they can run under other application containers. Only Tomcat has been tested. It is not included in the installation. Erlang is a programming language typically used to develop highly scalable and reliable distributed applications. RabbitMQ is written in Erlang, so Erlang is required on each node. Erlang R15B03 is supported and is not included in the installation. Java Runtime Environment (JRE) JRE v7 must be installed on every node in the system. It is included with the installation. If needed, you can obtain JRE at downloads/index.html. You should perform regular security updates for Java. Databases Apache Derby database is included in the installation package; it should be used for evaluation or demo purposes only. For production databases, NetApp Connect works with either PostgreSQL or Microsoft SQL Server. They are not included in the installation. PostgreSQL stores two data collections: system configuration information and perdocument information. NetApp Connect uses PostgreSQL for data storage and can work either in a local installation or on a remote server in a shared infrastructure. NetApp Connect provides the PostgreSQL JDBC driver as part of its installation package. NetApp Connect has been tested using PostgreSQL and If you use Microsoft SQL Server, you do not need PostgreSQL. MSVC redistributable package

16 16 NetApp Connect 5.1 Server Installation and Administration Guide NetApp Connect requires the MSVC redistributable package. Install the 64-bit version of this package. MSVC 2010 is included in the installation. RabbitMQ RabbitMQ is the Advanced Message Queuing Protocol (AMQP) message broker that enables all nodes within the system to communicate. It is required on every node. RabbitMQ Server v3.1.x is supported and is not included in the installation. Licensing information NetApp Connect is licensed for use with Data ONTAP CIFS shares (Windows file shares) that run on NetApp FAS storage or Data ONTAP cloud deployments. An optional license supports CIFS shares from any type of storage, called mixed. NetApp Connect software includes a 90-day evaluation license. When deciding upon user access, you might find it helpful to understand that licensing. NetApp Connect employs server-based, per-user licensing. In addition, NetApp Connect can access Windows-based repositories and intranet web content (running on whatever storage powers those applications). You can obtain your licenses from NetApp Support. NetApp Connect security features NetApp Connect employs strict security and authentication features, which are helpful to know before using the product. NetApp Connect includes the following security features: NetApp Connect server is installed inside the firewall to enable access to existing servers. Communication between the partner application and NetApp Connect is encrypted using SSL. Although communications between nodes in a scale-out configuration are usually encrypted with SSL, they can be encrypted with other methods. The NetApp Connect administrator chooses which servers, features, and data to enable (for example, user authentication systems, file shares and home directories, and Microsoft SharePoint sites). NetApp Connect is not a proxy and not a direct tunnel to data. The server is a bridge between the protocol used by cloud sharing and collaboration applications and that used by the servers, and authorization and protection are applied before any traffic to intranet systems occurs. No VPN is required.

17 Planning your deployment 17 NetApp Connect uses AMQP, a binary message-passing protocol, internally for communication. Access control in NetApp Connect Access control includes user authentication and file access authorization. When you are setting up NetApp Connect, you might find it helpful to know the authentication and authorization strategies. User authentication NetApp Connect uses the following methods for user authentication: Microsoft Active Directory Domain Services (AD DS) Open standard Lightweight Directory Access Protocol (LDAP) Users are authenticated when they log in to a server from a client application to access the content. The NetApp Connect server typically uses Active Directory for authentication. External users employ the same credentials they use from the internal system so that IT has one directory to maintain. AD groups govern which users are allowed access to the NetApp Connect server. File access authorization NetApp Connect uses standard Windows file and share-level permissions. NetApp Connect adheres to existing permissions configured by administrators or users. NetApp Connect provides access to shares using explicit configuration. For a user to access a share externally, an administrator must configure it as a repository. NetApp Connect installation checklist NetApp Connect depends on several supporting components to operate successfully. Consider using this at-a-glance checklist to help you install NetApp Connect. You might want to use this checklist to capture information that you need during the installation and configuration. 1. Select a deployment template. Write the template name here: 2. From your Active Directory or LDAP administrator, obtain the following information: Account with query privilege (legacy NT account name of domain\user, the user principal name, or the full LDAP distinguished name): Password to query account:

18 18 NetApp Connect 5.1 Server Installation and Administration Guide Security group for NetApp Connect administrators: If you are using Active Directory authentication, use the NT group name or the full LDAP distinguished name. If you are using LDAP authentication, use only the LDAP distinguished name. Security group for NetApp Connect users: Path to other security groups to be used for setting policy rules: 3. Verify the database configuration. Production environments should use an external database and obtain the JDBC connect string from your database administrator. NetApp Connect supports PostgreSQL or Microsoft SQL Server. 4. Create Policy Engine (PE) and Storage Engine (SE) accounts in the database. Write the account names and passwords here: 5. Create the PE and SE databases. The PE requires a 5 MB database, while the SE database size depends on the file cache size. A reasonable start is 50 MB plus 100 KB per user. 6. Verify that any automated antivirus scans are set to the lowest priority. If this cannot be controlled, schedule the scan for periods of low user activity. It is best if you exclude the NetApp Connect installation directory from virus scanning. 7. For access to the Application Boot Manager and the Dashboard from a remote administration system, verify that the firewall rules allow inbound HTTP access to the port on which Tomcat is set to run (usually 8080). Firewall for remote access to ABM needs to allow ports 8080 (HTTP) and 443 (HTTPS) on the NetApp Connect Server (trusted network). NetApp Connect installation data worksheet You can use the provided worksheet to help you during installation and to identify user names. Enter your own values, unless otherwise stated. Preinstallation configuration of Microsoft Active Directory Setting Active Directory domain name Value

19 Planning your deployment 19 Setting Query account Query account password NetApp Connect Users group NetApp Connect Admins group NetApp Connect service account NetApp Connect service account password Value ncs_query (Recommended value, although you can enter any value) ncs_users (Recommended value, although you can enter any value) ncs_admins (Recommended value, although you can enter any value) ncs_srv (Recommended value, although you can enter any value) Primary NetApp Connect Node: Installer Setting Tomcat administrator user account Tomcat administrator password NetApp Connect user Value admin (Recommended value, although you can enter any value) Primary NetApp Connect Node: Application Boot Manager (ABM) Quick Start Setting Organization Engine Token Database encryption string Root Keystore password Identify Keystore password Value Use default Use default Message Broker Setting Host name Network Token Join hostname Value Use default Use default

20 20 NetApp Connect 5.1 Server Installation and Administration Guide Policy Engine (PE) Setting Database Connection string Username Password Value Domain Storage Engine (DSE) Setting Realm Artifact cache (VFS) Mapped path (vfs) Pre-launch script Database Connection string Username Password Value Internal Use default Use default You should use a CIFS share for the cache. The CIFS share should be a minimum of 500 GB and might need adjustment based on your requirements. It is not possible to move the internal (local) cache to an external CIFS location, so you should set up the CIFS share as part of the installation. Postinstallation Setting ABM administrator password Dashboard administrator password Default realm administrator password Value Reverse Proxy node: DNS configuration Setting Reverse Proxy host name (fully qualified) Value

21 Planning your deployment 21 Setting Internal and external IP Value Reverse Proxy node: External firewall port configuration Setting Value Public side port 443 Deployment examples NetApp Connect can scale from a single machine servicing a small user population to a large, multiserver installation with thousands of concurrent users. It can be deployed differently, depending on performance goals, flexibility goals, and different data pathways. You can use sample NetApp Connect models to help you plan your deployment. You can use the following deployment models as examples of how NetApp Connect can be implemented in different environments: Single NetApp Connect server Distributed NetApp Connect servers You can begin with a single server and later change to a distributed server deployment model. Single NetApp Connect server in a monolithic deployment A monolithic deployment requires a single NetApp Connect server and another for reverse proxy for external access, with all components on site. All traffic, both internal and external, flows through servers that are located in the enterprise data center. You might want to use this deployment if you use a single machine with a small user population. NetApp Connect and cloud application interfaces connect to the hosted reverse proxy. This configuration requires two servers: one for NetApp Connect internal components and another for reverse proxy for external access to NetApp Connect. You should place the NetApp Connect server in the same company data center as the storage. The following image illustrates this model:

22 22 NetApp Connect 5.1 Server Installation and Administration Guide The following table lists which components reside on each server: Server Location Components Server 1 Server 2 Internal LAN DMZ Policy Engine Domain Storage Engine Internal broker Administration Dashboard HTTP Relay SAML components Customer-supplied reverse proxy server Configured to allow connections from the internal LAN and inbound access to port 443 from the Internet. This model is appropriate in the following environments: There are just a few users. Users access a small set of documents. Files are not frequently modified. Using this deployment model is an excellent way to get the system configured and operating quickly. However, if files are modified frequently, this model could result in traffic throughput issues.

23 Planning your deployment 23 Distributed satellite NetApp Connect servers You can improve throughput by adding multiple satellite NetApp Connect servers, each with its own Domain Storage Engine (DSE), allowing for many users across multiple groups. This deployment model uses a local server to host the external broker. This model improves the handling capacity, enabling the system to convert multiple documents simultaneously. The following image illustrates this model: The following table shows how components reside on multiple servers: Server Location Components Server 1 Server 2 Other servers Trusted network, internal LAN DMZ Satellite servers Internal Dashboard Policy Engine (PE) Internal Broker Customer-supplied reverse proxy Configured to allow connections from the internal LAN and inbound access to port 443 from the Internet Multiple instances of the Domain Storage Engine per group, function, or geography This model is appropriate in the following environments: There are many users. Users connect to a larger set of documents.

24 24 NetApp Connect 5.1 Server Installation and Administration Guide Files are frequently modified. Using this deployment model yields the following benefits: Focuses on smaller, self-contained DSEs that serve different functions, teams, or geographies. Includes administrator and user groups for each DSE. Improves scaling, with fewer users per server and a wider set of administrators managing different groups. Provides a simple setup for satellite servers. Related tasks Installing satellite Domain Storage Engine components on page 56 Configuring for cluster environments by exporting data on page 67

25 25 Installing the NetApp Connect server and components You install NetApp Connect as an on-premise deployment within your enterprise. You can install NetApp Connect on a single VM or can configure it across multiple machines, co-located with corporate file repositories such as Windows File Shares (CIFS), SharePoint servers, or internal web sites. About this task The installation process involves the following major tasks: Downloading NetApp Connect software Installing NetApp Connect server Performing basic configuration on the server Connecting to Active Directory Adding repositories Configuring Security Assertion Markup Language (SAML) for authentication and authorization Configuring HTTP Relay Configuring partner identification Provisioning user access to cloud sharing and collaboration interfaces and mobile app repositories Related concepts Configuring essential NetApp Connect components on page 31 Deployment examples on page 21 Related tasks Configuring NetApp Connect to use Active Directory on page 39 Adding repositories on page 41 Related references NetApp Connect architecture on page 10 NetApp Connect supporting software on page 15

26 26 NetApp Connect 5.1 Server Installation and Administration Guide Downloading the NetApp Connect software Before you can use NetApp Connect features, you must download the software from the NetApp Support Site for installation on the NetApp Connect server. Before you begin You must have already set up the databases and database user before installing NetApp Connect. Steps 1. Access the NetApp Support Site at mysupport.netapp.com. 2. From the NetApp Support Site, download the NetApp Connect server installation executable file (for example, NetAppConnectServer<version>.exe) to the Windows Server or VM. The server software is provided as a Windows installer executable and installed to the program files folder by default. Related references NetApp Connect supporting software on page 15 Installing the NetApp Connect server You must install the NetApp Connect server software to be able to run the Dashboard and Application Boot Manager (ABM) and to configure application access. Later, you might use the installation software to update only some components. Before you begin You must have a Windows user account under which the product can be installed. The user account must have local administrator permissions to install the NetApp Connect server software. It might be beneficial to use a service account for installations. Ensure that Firefox is configured as your default browser for the installation, because Internet Explorer security might disable the JavaScript libraries leaving the buttons disabled. About this task The default installation places all of the NetApp Connect engines on one server, referred to as the monolithic deployment model. In this model, all of the NetApp Connect software runs on one server. For details about the monolithic installation, see deployment model information.

27 Installing the NetApp Connect server and components 27 You can also use the installation software to update specific NetApp Connect components later; for example, a Policy Engine component. Steps 1. Copy the installation file NetAppConnectServer-<version>.exe to a local directory on the primary NetApp Connect server node. 2. To begin the installation, double-click NetAppConnectServer-<version>.exe. 3. In the NetApp Connect installer wizard, click Next. 4. Accept the license agreement and click I Agree. 5. Select an install location or accept the default and click Next. 6. Select one of the following and click Next: Express Installs all components and dependencies in default locations. Choose this for monolithic installations. If you are using the installation to update a node with a Policy Storage Engine (PE) or Domain Storage Engine (DSE) component using Express mode, NetApp Connect detects and updates only the resident components. Custom Installs selected components and dependencies. Choose this if you want to install specific components, a custom monolithic deployment, or a satellite deployment. 7. If you chose Express mode, go to the next step; if not, select among the following components.

28 28 NetApp Connect 5.1 Server Installation and Administration Guide For custom-mode monolithic deployments, check these components: Policy Engine, Domain Storage Engine, HTTP Relay, and SAML. For a full description of each component, see the information about server components. Policy Engine (PE) Enforces the business rules that apply to users and documents. By default, it extends the existing document policy to cloud application users. However, it can also accommodate custom business logic. Domain Storage Engine (DSE) Integrates file repositories, SharePoint repositories, and CIFS shares to a repository for users' storage needs. Often, deployments include multiple DSEs. HTTP Relay Translates RESTful HTTPS to AMQP, the protocol that NetApp Connect uses for communication. At least one HTTP relay is required. If you are installing in a clustered environment, select this and install on only one node. SAML The Security Assertion Markup Language (SAML) is a standards-based identity exchange framework from the Organization for the Advancement of Structured Information Standards (OASIS). The SAML specification defines roles for a service provider (SP), an identity provider (IdP) and a principal. NetApp Connect functions as an identity provider, using either Microsoft Active Directory or LDAP as the directory service against which a user is authenticated. SAML is needed for the login process and grants client application access to NetApp Connect. At least one SAML component is required. If you are installing in a clustered environment, select this and install on only one node. Satellite DSE For custom satellite deployments on the satellite nodes, check this. Otherwise, do not check this. 8. Click Install.

29 Installing the NetApp Connect server and components In the Prerequisite Software page, either click Install All to install all components, or click Install next to each of software components that you want to install. For a description of each component, see the information about supporting software. Several windows open and close as each software package is installed. A message indicates that all software has been installed. 10. Click OK in response to the prompt, and click Next. A prompt appears, requesting Tomcat user information. If no Tomcat user accounts exist, a prompt asks if you want to create a Tomcat account. 11. Do one of the following: If you have a Tomcat user account, enter the user name and password, typically admin and admin. To create a Tomcat user account, enter the new account's Tomcat user name and password and click Next. 12. Click Next. 13. In the prompt that indicates that the component is installed, click Next. A list of installed components appears.

30 30 NetApp Connect 5.1 Server Installation and Administration Guide 14. Ensure that the Launch Application Boot Manager option is checked and click Finish to complete the installation and launch Application Boot Manager. After you finish If you are using Microsoft SQL Server rather than the PostgreSQL, continue by installing the Microsoft SQL Server JDBC driver. Otherwise, continue with configuring essential NetApp Connect components, starting with the Application Boot Manager configuration. It is best to restart Tomcat if necessary, verify that the required services are running, and back up the configuration. Related concepts Configuring essential NetApp Connect components on page 31 Troubleshooting on the NetApp Connect server on page 82 Installing the Microsoft SQL Server JDBC driver If you are using Microsoft SQL Server rather than the provided embedded database to enable database connectivity, you must have a copy of the Microsoft SQL Server Java Database Connectivity (JDBC) driver, which is available from Microsoft. You must obtain this file after installing but before configuring NetApp Connect. Before you begin You must have installed the NetApp Connect server.

31 Installing the NetApp Connect server and components 31 Steps 1. Using a browser, access the Microsoft download pages. 2. Locate the Microsoft SQL Server JDBC driver at aa aspx. 3. Place the sqljdbc4.jar file in the <Install path>\netapp\connect Server\jdbc folder: for example, C:\Program Files\NetApp\Connect Server\jdbc. 4. If you are implementing NetApp Connect in a satellite deployment, you must also copy the file to <Install_path>\ NetApp\Connect Satellite Server\jdbc. Configuring essential NetApp Connect components After installing NetApp Connects, the Application Boot Manager appears, in which you configure server components. You use the Dashboard to configure authentication, user access, and repositories. This process is essential to the initial setup. Use the following utilities to complete the configuration: Application Boot Manager Use to set server access, view license information, create root certificates, and create connections to components. Dashboard Use to configure Active Directory, authentication, repositories, and user access provisioning. Other utilities Use to configure SAML, HTTP Relay, and partner identification The following table shows the configuration tasks you must perform and which server utility you use: Configuration task Application Boot Manager Quick Start Wizard Dashboard Other utilities Define the organization's name Y Set up server access Y Create or update root certificates and paths Y Configure database options Y

32 32 NetApp Connect 5.1 Server Installation and Administration Guide Configuration task Application Boot Manager Quick Start Wizard Dashboard Other utilities Set up connections to components (Message Broker, Policy Engine, Domain Storage Engine) Y Configure Active Directory Y Add and configure repositories Y View license information Y Configure provisioning so that the third-party application recognizes the server Y Configure a server for provisioning Y Provision user access to third-party applications Y Configure SAML Y Configure HTTP Relay Y Configure partner identification Y Setting up certificates, database options, and component engines with the Quick Start Configuration wizard During initial setup, NetApp Connect launches the Application Boot Manager Quick Start Configuration wizard to help you with your configuration. You can set server access, view license information, create root certificates, and create connections to components. Before you begin The NetApp Connect server must be installed. Steps 1. When the Application Boot Manager login page appears, immediately following server installation, enter the user name and password and click Log In. The default user name and password are admin and admin.

33 Installing the NetApp Connect server and components 33 If the Application Boot Manager did not appear just after the installation, you can access it directly. From the ABM, select Boot Configuration > Quick Start. 2. Complete the Quick Start Configuration wizard using the information in the Install worksheet. 3. In the General Configuration section, complete the fields as follows:

34 34 NetApp Connect 5.1 Server Installation and Administration Guide In this field Organization Engine Token Database Encryption String Root Keystore Password Identify Keystore Passwords Type or do the following... Enter your organization, company, or group name: for example, NetApp. Leave as is. This is a character string that identifies the NetApp Connect engines running on this instance of the Windows server. This is automatically generated. Leave as is. This is a string used to access the database. This is not typically changed except when there is a shared database. Enter a password: for example, netapp1. This password accesses the store used for encryption keys. The password must contain seven or fewer characters; however, if the administrator installed the Oracle unlimited key strength JCE, this limit does not apply. Enter a password: for example, netapp1. This password accesses the store used for encryption keys. Note: The password must contain seven or fewer characters; however, if the administrator installed the Oracle unlimited key strength JCE, this limit no longer applies. 4. In the Message Broker section, complete the fields as follows: In this field Hostname Network Token Join hostname Type or do the following Type the name of the server to which the cloud-sharing or mobile application connects. The host name should match the host name of the NetApp Connect Server for the SSL certificate. It is the DNS host name of the server that clients use to access the NetApp Connect Server. It is used on the security certificates that are generated during installation. Leave as is. This is an identifier used by the message broker to enable access to broker configuration and the command interface. Leave as is. This is the host name of a message broker on a host (different than the one currently being installed) with which you would like to join this broker. 5. In the Policy Engine section, complete the fields as follows:

35 Installing the NetApp Connect server and components 35 In this field Database Type Connection String Username Password Type or do the following If you are using an embedded database provided during the installation, ensure that Embedded is selected; otherwise, select the type of database you are configuring. If you do not use an embedded database, ensure that this matches the Microsoft SQL Server or PostgreSQL database information; otherwise, leave as is. This is a database-dependent string of parameters used for communicating with the database server. See the documentation of the database server for specifics on JDBC connection string format. If you do not use an embedded database, ensure that this matches the Microsoft SQL Server or PostgreSQL database information. For example, enter sa; otherwise, leave as is. This is the name of the user required by the database server. If you do not use an embedded database, ensure that this matches the Microsoft SQL Server or PostgreSQL database information. For example, enter netapp1; otherwise, leave as is. 6. In the Policy Engine section, click Test Connection. 7. In the Domain Storage Engine section, complete the fields as follows: In this field Realm Artifact Cache (VFS) Mapped Path Pre-launch Script Type or do the following Enter the name of the realm: for example, CorpMedia. The realm should remain the same across all devices in a cluster. This is the type of storage to be used for the cache, either internal or on an external CIFS share. Leave as is. This is the path to the CIFS share when using an external storage location for cache. If you are using CIFS, delete the script; otherwise, leave as is. This script is executed before the NetApp Connect Server is started to define parameters for the server to use, such as log verbosity. It ensures that the cache is available when using an external cache.

36 36 NetApp Connect 5.1 Server Installation and Administration Guide In this field Database Type Connection String Username Password Type or do the following If you are using the embedded database, leave the default of Embedded selected; otherwise, choose the type of database: for example, Microsoft SQL Server. If you do not use an embedded database, ensure that this matches the Microsoft SQL Server or PostgreSQL database information; otherwise, leave as is. If you do not use an embedded database, ensure that this matches the Microsoft SQL Server or PostgreSQL database information. For example, enter sa; otherwise, leave as is. If you do not use an embedded database, ensure that this matches the Microsoft SQL Server or PostgreSQL database information. For example, enter netapp1; otherwise, leave as is. 8. In the Domain Storage Engine section, click Test Connection. 9. Click Submit to finish the quick start. As the configuration is performed, information about the steps is printed at the bottom of the page. When configuration is complete, a Continue button appears. 10. Click Continue. The browser opens Application Boot Manager. 11. In the Application Control section, click Start to start the NetApp Connect server. The server state shows as Running. After you finish Continue with configuring the Dashboard. Related concepts Realm and repository comparison on page 41 Troubleshooting on the NetApp Connect server on page 82 Related tasks Accessing NetApp Connect Application Boot Manager on page 59

37 Installing the NetApp Connect server and components 37 Starting and stopping the NetApp Connect server You can easily start the NetApp Connect server. When you change any information in Application Boot Manager (ABM), you must first stop the NetApp Connect server. Steps 1. Access Application Boot Manager by entering: 2. To start the server, in the Application Control section, click Start. Note: When the application is running, the Application Boot Manager shows a connection status of Connection Error, which is normal. After a few seconds, the Application Status changes from a state of Stop to Run in the Desired state field. 3. To stop the server, in the Application Control section, click Stop. After you finish After you finish, you can start the server again.

38 38 NetApp Connect 5.1 Server Installation and Administration Guide Accessing the NetApp Connect Dashboard You use the Dashboard to configure initial settings and later update those settings. Before you begin You must be using a browser other than Internet Explorer 9 in enhanced security mode (which Windows Server 2008 R2 runs by default). Steps 1. Do one of the following: If you are continuing from the Application Boot Manager (ABM), select Boot Configuration > Jump to Dashboard. Otherwise, log in to the Dashboard by entering the following address: 2. Type the name of the realm that you entered in the Application Boot Manager (ABM) Quick Start Configuration. The realm name is case sensitive. 3. Type the default user name: admin. 4. Click Login. The server validates the realm and user name and then prompts for a password.

39 Installing the NetApp Connect server and components Type the default password: admin. 6. Click Login again. The Dashboard appears: After you finish Continue configuring policies and repositories using the Dashboard. As soon as possible, you should customize the user name and password. Related tasks Changing your NetApp Connect Dashboard password on page 73 Configuring NetApp Connect to use Active Directory You can configure NetApp Connect to use Active Directory. You might want to use Active Directory over LDAP services because Active Directory provides robust and well-defined user administration, and using Active Directory with NetApp Connect provides a central location from which to manage user accounts and access. About this task In Active Directory mode, both administrative and end user access is controlled by Active Directory. Both the NetApp Connect server and user interfaces verify access with Active Directory in real time. Steps 1. Access the NetApp Connect Dashboard.

40 40 NetApp Connect 5.1 Server Installation and Administration Guide 2. From the Dashboard menu, click Policy & Configuration. 3. In the User Database field of the Authentication Configuration section, select Microsoft Active Directory. 4. Below the Authenticator Configuration section, click Stage Changes. The Active Directory Authentication section becomes visible just below the Authentication Configuration section. 5. In the Active Directory Authentication section, complete the following fields: Query Account Enter the user name of the account that is used to query Active Directory. The account should contain the domain name, in the format DOMAIN\user. Query Password Enter the account password. Administrator Group Enter the name of the security group that contains the list of NetApp Connect administrators. Only these people can log in to the Administrative Dashboard. User Group Enter the name of the security group that contains the list of NetApp Connect users. Only these people can log in to the NetApp Connect interfaces. Forest DNS Name Enter the DNS name (for example, corp.company.com) of a domain within the Active Directory forest that stores the NetApp Connect user accounts and groups. If not provided, NetApp Connect attempts to automatically detect the forest name using the fully qualified domain name of the NetApp Connect server. NetBIOS Domains Enables the use of NetBIOS over TCP for resolving legacy Windows NT domain names for user accounts. If WINS servers have not been configured for your network, this should be disabled. When disabled, only users within a single Active Directory domain can use NetApp Connect. The default is enabled. 6. Below the Active Directory Authentication section, click Stage Changes. You must click separate Stage Changes links: one in each section. A green check mark appears next to each setting to indicate that the setting is valid. If the server cannot connect, the error message typically describes the specific problem. Occasionally, if the server cannot identify the error, the server displays a message indicating that the details are in the system.log file in the installation directory. To see detailed error information, open this file in a text editor and look at the last line. 7. In the Admin Changes pane, click Execute Changes to commit all of the staged changes listed.

41 Installing the NetApp Connect server and components 41 A message appears, indicating that the server will be restarted. 8. Click Execute Changes again to save the changes and restart the server. The Admin Changes pane at the top of the page displays the changes. 9. Wait for the server to restart: typically, three minutes. After you finish To reconnect to the server, you must enter an Active Directory account that is a member of the NetApp Connect administrators group. The default admin account no longer works. Related concepts Troubleshooting on the NetApp Connect server on page 82 Adding repositories You can add different types of repositories, such as CIFS shared folders, Microsoft SharePoint sites, or local directories. After you configure these in the NetApp Connect server, users can browse directories and interact with the files on their cloud or mobile devices. About this task You can add the following types of repositories: CIFS shared folders Microsoft SharePoint sites Local directories A single NetApp Connect server can host multiple repositories, even of different types. When users connect, the server displays one folder that corresponds to each repository. For example, if the server is sharing a CIFS shared folder called Sales and a SharePoint site called Marketing, users see the two folders: Sales and Marketing. Although the server can host multiple repositories, it prompts for only one set of user credentials. This means that each repository must use the same authentication authority. In most environments, Active Directory acts as this authority across repositories. Realm and repository comparison During initial configuration of NetApp Connect, it might be helpful to understand the difference between realms and repositories. The realm in NetApp Connect is typically the NetApp Connect server. Within a realm, you can point to repositories, which could include CIFS shares, SharePoint sites, or users' home directories. Realm

42 42 NetApp Connect 5.1 Server Installation and Administration Guide Identifies a collection of resources, including documents, policies, and an authentication domain. A Domain Storage Engine (DSE) manages a single realm. You can create one realm for the entire company or one per department or group. Realms can share common NetApp Connect components. There is always a default realm, separate from domain storage engine realms, that is used to configure access to the message broker. In the simplest configuration, a NetApp Connect server hosts a single DSE with a single user realm. A more complex configuration could integrate multiple DSEs, each hosting a single realm. The complex configuration can employ one of two types of DSEs: Regular DSE The primary difference is that a regular DSE node has more components installed, including a local internal broker. Satellite DSE Repository A satellite DSE uses the internal broker of another node, such as the PE. Many satellite nodes can use the one broker running on the PE node, providing a simplified configuration to manage on each satellite node. The structure allows for many realms to be hosted by a centralized PE. Identifies locations of user data within a realm that are configured by the server administrator. The supported repository types include: CIFS share SharePoint document location (URL) Local directory For example, a Marketing realm could include mounted repositories that point to shared collateral on a SharePoint site, a CIFS share, and every member's home directory. Adding a CIFS share You can add a CIFS share so that NetApp Connect users can access CIFS shares on their cloud applications or mobile devices. Before you begin Application users must have permission to see the files on the CIFS share. You must already have set up Active Directory and be a member of its NetApp Connect Administrator group. Steps 1. Access the Dashboard by entering the following URL in your browser:

43 Installing the NetApp Connect server and components Log in as a member of the Administrator group in the Active Directory. 3. In the Dashboard, click the Repositories tab. 4. Click Add CIFS Network Share. 5. In the CIFS Network Share Settings section, enter the following values: Title Enter the name that represents this repository. This name appears to users on their cloud or mobile apps. Folder Path Enter the path to the CIFS share. Permit Modifications Select Enabled to allow users to modify content on this repository. 6. Verify that the configuration is working correctly by clicking Test Settings. 7. Click Add Repository. The new repository is available immediately to users who connect to the NetApp Connect server. Related tasks Configuring NetApp Connect to use Active Directory on page 39 Adding a SharePoint site You can add a SharePoint site so that NetApp Connect application users can access the site using their cloud applications or mobile devices and view the files and folders. Before you begin Cloud or mobile app users must already have permission to access these files and folders on the SharePoint site. You must already have set up Active Directory and be a member of its NetApp Connect Administrator group. Steps 1. Access the Dashboard by entering the following URL in your browser:

44 44 NetApp Connect 5.1 Server Installation and Administration Guide 2. Log in as a member of the Administrator group that you set up as part of configuring Active Directory. 3. In the Dashboard, click the Repositories tab. 4. Click Add Microsoft SharePoint. 5. In the Microsoft SharePoint Settings section, either specify values for the following or use the wizard: Server URL Enter the URL of the root site of the SharePoint web application. If the link includes a subsite, the URL you enter here refers to the site and not the subsite. Subsite Enter the path of the SharePoint site or site collection within the web application. Permit Modifications Select Enabled to allow users to modify content on this repository. Alternatively, you can use a wizard to automatically configure these fields. Copy a URL for a site or library from a web browser into the Server URL field, and leave the subsite information area empty. Click Test Settings to run the wizard. The NetApp Connect administrator must have permission to browse the SharePoint site for the wizard to succeed. 6. Verify that the configuration is working correctly by clicking Test Settings. 7. Click Add Repository. The new repository is available immediately to users who connect to the server. Related tasks Configuring NetApp Connect to use Active Directory on page 39 Adding a local directory You can add a local directory to the NetApp Connect server so that users can access the directory using their cloud or mobile apps. You should use this directory only for testing a new installation or troubleshooting, not for production use. Before you begin Cloud or mobile app users must already have permission to access these local directory files and folders. You must already have set up Active Directory and be a member of its NetApp Connect Administrator group.

45 Installing the NetApp Connect server and components 45 About this task If you want to include a local directory in a cluster configuration, ensure that the local directory is mapped to the same location on all nodes in the cluster. Steps 1. Access the Dashboard by entering the following URL in your browser: 2. Log in as a member of the Administrator group in the Active Directory. 3. In the Dashboard, click the Repositories tab. 4. Click Add Local Directory. 5. In the Local Directory Settings section, supply values for the following: Title Enter the name that represents this repository. This name appears to users. Folder Path Enter the path to the local directory that contains the files to be shared, such as c:\files directory. Permit Modifications Select Enabled to allow users to modify content on this repository. 6. Verify that the configuration is working correctly by clicking Test Settings. 7. Click Add Repository. The new repository is available immediately to users who connect to the NetApp Connect server. Related tasks Configuring NetApp Connect to use Active Directory on page 39 Viewing license information After you configure NetApp Connect, you can view license information to be sure that it is correct. Later, you might want to update this information if the license expires and you receive updated licensing. Steps 1. Locate the licensing information provided to you by NetApp when you purchased the product. 2. Access the Application Boot Manager (ABM).

46 46 NetApp Connect 5.1 Server Installation and Administration Guide 3. From the Application Boot Manager, click Boot Configuration. 4. View the license information in the License text box. Related tasks Accessing NetApp Connect Application Boot Manager on page 59 Creating a certificate for SAML message signing The Security Assertion Markup Language (SAML) is a standards-based identity exchange framework from the Organization for the Advancement of Structured Information Standards (OASIS). You must create a self-signed certificate for successful authentication and authorization processes and enable client applications access to NetApp Connect. Before you begin You must have already installed OpenSSL. Steps 1. On the server where NetApp Connect is installed, open a terminal or command prompt. 2. Create a directory to store the generated certificate files. 3. From this directory, generate the private key: $ openssl genrsa -des3 -out <key_name>.key 1024 For each of the commands in this task, enter a password, as needed. 4. Generate the Certificate Signing Request for creating the certificate: $ openssl req -new -key <key_name>.key -out <csr_name>.csr 5. Generate the self-signed certificate: $ openssl x509 -req -days 365 -in <csr_name>.csr -signkey <key_name>.key -out <server_cert>.cer A server certificate.cer file is created in this directory. 6. Export the key with the certificate: $ openssl pkcs12 -export -inkey <key_name>.key -in <server_cert>.cer - name <alias_name> -out <export_file_name>.p12 An export.p12 file is created in this directory. 7. Copy the server certificate.cer and export file.p12 files to this directory: \<installation directory>\netapp\connect Server\cert\.

47 Installing the NetApp Connect server and components 47 After you finish After creating the certificate for SAML, you must configure SAML for successful authentication and authorization processes. Configuring SAML for authentication and authorization The Security Assertion Markup Language (SAML) is a standards-based identity exchange framework from the Organization for the Advancement of Structured Information Standards (OASIS). You must configure SAML for successful authentication and authorization processes and enable client applications access to NetApp Connect. Before you begin You must have already installed NetApp Connect. You must have already created a self-signed certificate for SAML message signing. About this task The SAML specification defines roles for a service provider (SP), an identity provider (IdP) and a principal, and they perform the following functions: The principal requests a service from the service provider. The service provider requests and obtains an identity assertion from the identity provider. On the basis of this assertion, the service provider decides whether to perform some service for the connected principal. NetApp Connect functions as an identity provider using either Microsoft Active Directory or LDAP as the directory service against which a user is authenticated. At least one SAML component is required. Steps 1. Generate the RSA certificate (.cer) and private key (.p12) using either an OpenSSL command line or keychain access. 2. Locate the <installation directory>\netapp\connect Server\setup\boot\ folder. 3. In this directory, open the saml.props file in a text editor. This file includes key value pairs in XML format that the SAML server uses. 4. Locate the <entry key="relay"> property and replace its contents with the URL where the HTTP Relay component is installed: <entry key="relay">

48 48 NetApp Connect 5.1 Server Installation and Administration Guide This could be the localhost8080:httprelay in a monolithic installation or the address of a server that is behind the network firewall. 5. Locate the <entry key="dest_url"> property and replace its contents with the external access URL of the current node. Example <entry key="dest_url"> This should be the URL where SAML is installed, which could be exposed behind a proxy or directly accessible from the public network. 6. In the RSA certificate (.cer) and private key (.p12) files that you generated, locate the following properties and change them according to the following: <entry key="rsa_cert"> Certificate name with.cer extension</entry> <entry key="rsa_private_key"> Private key with.p12 extension</entry> <entry key="p12_alias"> Alias name for the private key</entry> <entry key="p12_password"> Password for the private key</entry> Example <entry key="rsa_cert">test.cer</entry> <entry key="rsa_private_key">test.p12</entry> <entry key="p12_alias">mycertificatealias</entry> <entry key="p12_password">mycertificatepassword</entry> 7. Reload the SAML authentication bridge by doing the following: a. Open the Apache Tomcat Application by entering: b. Under the Administration area in the top left of the page, click Tomcat Manager. c. If prompted for a login and password, look for these in the installation checklist that you completed prior to installation. The default login is admin and default password is admin. d. In the Tomcat Web Application Manager, locate the row authbridge row and in the far right, click Reload to restart SAML.

49 Installing the NetApp Connect server and components 49 Configuring HTTP Relay for authentication and authorization HTTP Relay is a component of the NetApp Connect server that translates HTTPS Rest data to Advanced Messaging Queue Protocol (AMQP), which the server uses to communicate. For the server to communicate successfully, you must configure HTTP Relay. Before you begin You must have already installed NetApp Connect. You must have already created a self-signed certificate for SAML message signing. A self-signed SAML certificate is needed for successful authentication and authorization of HTTP Relay processes. You must have at least one HTTP component. About this task HTTP Relay receives client application requests forwarded or proxied from a gateway reverse proxy system through SSL REST HTTPS. Messages are then converted to a native protocol (AMQP for NetApp Connect), with which internal components (such as the Policy Engine and Data Storage Engine) use to communicate. Client applications need HTTP Relay to communicate with NetApp Connect. Steps 1. (Clustered system only) When where SAML and HTTP Relay are on separate nodes, copy the server certificate.cer and export file.p12 files from the SAML Message Signing section into the local server's directory: <Install_path>\NetApp\Connect Server\cert\ For monolithic installations where all NetApp Connect components (HTTP Relay, SAML, PE, DSE) are on same node, skip this step, because the certificate copy was completed during the SAML configuration. 2. In the server where NetApp Connect is installed, open a Firefox browser and type: One of the following types of messages appears: message Not Found, detail: Not supported, or code: Go to the following directory: <Install_path>\NetApp\Connect Server\setup\boot\ 4. In this directory, open the relay.props file in a text editor. This file includes key value pairs that the HTTP Relay server uses. 5. Locate the <entry key="dest_url"> property and replace its contents with the external access URL of the current node:

50 50 NetApp Connect 5.1 Server Installation and Administration Guide Example <entry key="dest_url"> This should be the URL where SAML is installed, which could be exposed behind a proxy or directly accessible from the public network. 6. Restart HTTP Relay by doing the following: a. Open the Apache Tomcat Application: b. Under the Administration area in the top left of the page, click Tomcat Manager. c. If prompted for a login and password, look for these in the installation checklist that you completed prior to installation. The default login is admin and default password is admin. d. In the Tomcat Web Application Manager, locate the httprelay row and in the far right, click Reload to restart HTTP Relay. Configuring partner information For a partner's servers to communicate with NetApp Connect, you must provide NetApp Connect with partner identification information. Before you begin You must have already installed NetApp Connect. You must have already created a self-signed certificate for SAML message signing and configured SAML. You must have already configured HTTP Relay. Steps 1. If you are a technology partner, obtain the ID associated with the partner name from a Support Site Knowledge Base (KB) article about NetApp Connect partner identification (KB # ). 2. Go to the following directory: <Install_path>\NetApp\Connect Server\setup\boot\ 3. In this directory, open the relay.props file in a text editor. This file includes key value pairs that the HTTP Relay server uses. 4. Locate the <entry key="partneridentificationenabled"> property and confirm that it is set to "True":

51 Installing the NetApp Connect server and components 51 <entry key="partneridentificationenabled">true</entry> 5. Locate the <entry key="partnerkeys"> property and replace its contents with the following information: Partner ID Provisioning status Partner name Key <entry key="partnerkeys"> partner1_id-field#1, Partner ID partner1_provision_status-field#2, Partner provisioning status partner1_name-field#3, Partner name partner1_key-field#4; Partner key partner2_id-field#1, partner2_provision_status-field#2, partner2_name-field#3, partner2_key-field#4;</entry> Separate fields with commas. Separate partners by placing a semicolon after the key. Example <entry key="partnerkeys"> 1001,true,NetApp,Z-$9f3@!n0; 2002,true,Partner,au87Hnb4J5</entry> 6. Restart HTTP Relay: a. Open the Apache Tomcat Application: b. Under the Administration area in the top left of the page, click Tomcat Manager. c. If prompted for a login and password, look for these in the installation checklist that you completed prior to installation. The default login is admin and default password is admin. d. In the Tomcat Web Application Manager, locate the row httprelay and in the far right, click Reload to restart HTTP Relay. Related information NetApp Knowledgebase

52 52 NetApp Connect 5.1 Server Installation and Administration Guide Configuring the reverse proxy The reverse proxy enables cloud applications to access the on-premises NetApp Connect server. The reverse proxy provides a hosted web server in your corporate DMZ that forwards HTTPS traffic to HTTP Relay or the Security Assertion Markup Language (SAML) authentication interface. You must set up a reverse proxy to use NetApp Connect. Before you begin You must have already installed NetApp Connect. About this task Although you should use the Apache web server, you can use other web servers. Also, you should configure SSL on that reverse proxy and use a signed SSL certificate, because traffic between the cloud product and the reverse proxy should be encrypted. Step 1. Set up the reverse proxy in your corporate DMZ. To view sample configuration files for HTTP and SAML, see the Knowledge Base (KB) article about how to set up a reverse proxy for Apache 2.4 on Linux with NetApp Connect 5.1. Related information NetApp KB Article : How to Set Up a Reverse Proxy for Apache 2.4 on Linux (HTTP Relay/SAML) with NetApp Connect 5.1 Provisioning user access To enable users to access files on repositories, you must provision user access on your application. Provisioning is implemented differently by each client application. Related tasks Configuring users' home folders on page 74

53 Installing the NetApp Connect server and components 53 Upgrading NetApp Connect You can upgrade NetApp Connect from one version to another. Before you begin You must have downloaded the NetApp Connect software. For details, see downloading information. You must have read the NetApp Connect 5.1 Release Notes. You must have opened a NetApp Support case. About this task If you are upgrading from v4.1 or earlier, you must first upgrade to v4.2.1 and then upgrade to v5.1. If upgrading from v4.2.1 or later, you can upgrade directly to v5.1. If you are upgrading from NetApp Connect v4.2.1, NetApp Connect clients no longer function and are not supported with the v5.1 server. Steps 1. Start with an existing installation. 2. Back up the system. 3. Install NetApp Connect. For details, see information on installing NetApp Connect. 4. Start the server using Application Boot Manager. For details, see the information on starting the server. Related tasks Downloading the NetApp Connect software on page 26 Installing the NetApp Connect server and components on page 25 Accessing NetApp Connect Application Boot Manager on page 59 Starting and stopping the NetApp Connect server on page 37

54 54 NetApp Connect 5.1 Server Installation and Administration Guide Uninstalling NetApp Connect You can uninstall the NetApp Connect server and supporting software if you no longer want to use NetApp Connect and you want to clean up unnecessary files. About this task When you uninstall the NetApp Connect server software, the following occurs: All NetApp Connect services are stopped. All NetApp Connect server software is removed. All NetApp Connect supporting software is removed, based on your removal selections. You can no longer connect the cloud or mobile app to the server; however, the mobile app still remains on your mobile device and you can use it to view offline content. Steps 1. From the Windows Start menu, select NetApp Connect > Uninstall Connect. 2. Complete the steps in the uninstall wizard and select the third-party supporting software components that you want to remove. When the software is removed, the final page displays Uninstallation Complete. 3. On the final page, click Close.

55 55 Configuring advanced NetApp Connect options After you finish the initial configuration of NetApp Connect, you might want to further customize it with optional advanced features in the Application Boot Manager and the Dashboard. These are not essential to the initial setup. About this task You can perform the following advanced tasks: Installing satellite Domain Storage Engine (DSE) components Configuring cluster environments Additionally, you can use the following components to perform administrative tasks: Application Boot Manager You can use this web application to manage software components required by the server, including the following tasks: Changing the Application Boot Manager password Setting up server access (set up during initial quick-start installation) Setting up root certificates (set up during initial quick-start installation) Setting up connections to components (set up during initial quick-start installation) Viewing license and server information Viewing log messages Using the log collection utility for troubleshooting issues Dashboard You can use this web application to perform the following tasks on the server: Changing the Dashboard password Viewing logs Viewing user names and online users Configuring repositories Configuring third-party application provisioning, plug-in access, authentication, Active Directory authentication, and secure web tunneling

56 56 NetApp Connect 5.1 Server Installation and Administration Guide Setting administrative policies, such as offline support, offline access time, and ondevice caching Installing satellite Domain Storage Engine components You can install the NetApp Connect Domain Storage Engine (DSE) component on different Windows Servers or VMs to create a scalable or clustered installation. You might want to do this if you are implementing a large-scale system with many satellite servers managed by a central server. Before you begin You must have installed and configured a Policy Engine (PE) that includes signing authority configuration by providing the path of the root or an intermediate certificate. You must have a Windows user account under which the DSE can be installed. The user account must have local administrator permissions to install the NetApp Connect server software. Ensure that Firefox is configured as your default browser, because Internet Explorer security might disable the JavaScript libraries leaving the buttons disabled. Steps 1. Copy the installation file NetAppConnectServer-<version>.exe to a local directory on the primary NetApp Connect server node. 2. To begin the installation, double-click NetAppConnectServer-<version>.exe. 3. In the NetApp Connect installer wizard, click Next. 4. Accept the license agreement and click I Agree. 5. Select an install location or accept the default and click Next. 6. Select the Custom install method and click Next. 7. For satellite deployments, check this component: Satellite DSE. For a full description of each component, see the information about server components.

57 Configuring advanced NetApp Connect options Click Install: 9. Click OK in response to the prompt, and click Next. A prompt appears, requesting Tomcat user information. If no Tomcat user accounts exist, a prompt asks if you want to create a Tomcat account. 10. Do one of the following: If you have a Tomcat user account, enter the user name and password, typically admin and admin. To create a Tomcat user account, enter the new account's Tomcat user name and password and click Next.

58 58 NetApp Connect 5.1 Server Installation and Administration Guide 11. Click Next. 12. In the prompt that indicates that the component is installed, click Next. 13. Ensure that the Launch Application Boot Manager option is checked and click Finish to complete the installation and launch Application Boot Manager. Note that when installing a satellite DSE, ABM runs as a service and listens on port 4253 (rather than on port 8080 as it would with a full installation that employs Tomcat). 14. Log in to ABM by using the default user name and password (admin and admin). The Server Registration form is displayed. 15. Complete the relevant information to register this DSE: Provisioning URL The URL to the Dashboard that was set up in the NetApp Connect options set using the Dashboard. Organization Name The name of the company or organization. User name and password Credentials authorizing registration. Use the credentials for the default realm, which are admin/admin. Engine Token Identifier of Domain Storage Engine, needed for clustering DSEs. Use the default value. 16. Click Register and wait for a success message. 17. Click Application Control, in the left navigation pane of ABM, and click Start. Advanced NetApp Connect Application Boot Manager configuration options You might want to further customize NetApp Connect with optional advanced features that you configure with the Application Boot Manager (ABM). Some of these tasks are performed during the quick start initial installation. Accessing these features separately is typically not essential to the initial setup. You can perform the following tasks with the Application Boot Manager: Configure the server as part of the initial installation process. Change your Application Boot Manager password. Start or shut down the server.

59 Configuring advanced NetApp Connect options 59 View license information. View server information. Manage certificates for SSL broker communication. Manage the brokers. Manage the Policy and Storage engines. View log messages. Use the log collection utility for troubleshooting issues. Accessing NetApp Connect Application Boot Manager You can use Application Boot Manager (ABM) to configure realms and view licensing. Steps 1. Log in to Application Boot Manager by entering Connect server>:8080/ abm. 2. Enter the user name and password. You can use the default user credentials: User name: admin Password: admin As soon as possible, you should customize the user name and password. The Application Boot Manager appears:

60 60 NetApp Connect 5.1 Server Installation and Administration Guide Related tasks Changing your NetApp Connect Application Boot Manager password on page 60 Changing your NetApp Connect Application Boot Manager password The NetApp Connect server uses two passwords: one for Application Boot Manager and one for the Dashboard. You can change either password anytime and you should change your password frequently for security purposes. Steps 1. Log in to Application Boot Manager: Connect server>:8080/abm. 2. Enter your current user name and password. Application Boot Manager appears: 3. Click Change Password. 4. Enter your former password once and your new password twice. 5. Click Change.

61 Configuring advanced NetApp Connect options 61 Starting and stopping the NetApp Connect server You can easily start the NetApp Connect server. When you change any information in Application Boot Manager (ABM), you must first stop the NetApp Connect server. Steps 1. Access Application Boot Manager by entering: 2. To start the server, in the Application Control section, click Start. Note: When the application is running, the Application Boot Manager shows a connection status of Connection Error, which is normal. After a few seconds, the Application Status changes from a state of Stop to Run in the Desired state field. 3. To stop the server, in the Application Control section, click Stop. After you finish After you finish, you can start the server again.

62 62 NetApp Connect 5.1 Server Installation and Administration Guide Viewing license information After you configure NetApp Connect, you can view license information to be sure that it is correct. Later, you might want to update this information if the license expires and you receive updated licensing. Steps 1. Locate the licensing information provided to you by NetApp when you purchased the product. 2. Access the Application Boot Manager (ABM). 3. From the Application Boot Manager, click Boot Configuration. 4. View the license information in the License text box. Related tasks Accessing NetApp Connect Application Boot Manager on page 59 Accessing the Dashboard from the Application Boot Manager From the Application Boot Manager (ABM), you can quickly access the Dashboard by using an embedded link to the Dashboard. You might want to access the Dashboard to change policies or update repositories. Steps 1. From the Application Boot Manager select Boot Configuration. 2. Click Jump to Dashboard. Viewing server identity using Application Boot Manager You can obtain important information about the NetApp Connect server by using Application Boot Manager. For example, you can learn the location of the server installation, the realm name of the server, the version of the software that is currently running, and the license information. Steps 1. Access Application Boot Manager. 2. Select Boot Configuration > Identity Management. 3. Take note of the realm name. You need to know the realm name when you log into the Dashboard.

63 Configuring advanced NetApp Connect options 63 Configuring the NetApp Connect Message Broker You can configure the internal or external Message Broker in the NetApp Connect server by using Application Boot Manager. For example, you can set the location where your Erlang and RabbitMQ files are stored, identify the virtual host, and enter the value of the virtual host's trust location. You must do this to establish secure communication among components. About this task NetApp Connect uses two types of message brokers. The following procedure updates the broker that you are accessing. For example, if you are accessing the internal message broker, then you update the internal one. Internal message broker Passes messages among the internal components (Policy Engine and Storage Engine). External message broker Connects external users to the Policy Engine (PE). It accepts connections from the thirdparty applications and the PE. Steps 1. Access the Application Boot Manager. 2. Stop the server before proceeding with the configuration. 3. Select Boot Configuration > Message Broker. 4. In the Message Broker section, complete the fields as follows: In this field ERLANG Home RABBITMQ Home Type or do the following To change the Erlang location from the installation location, enter the path here. Erlang is a programming language typically used to develop highly scalable and reliable distributed applications. RabbitMQ is written in Erlang, so Erlang is required on each node. Erlang is included in the installation. To change the RabbitMQ location from the installation location, enter the path here. RabbitMQ is the Advanced Message Queuing Protocol (AMQP) message broker that enables all nodes within the system to communicate. It is required on every node. RabbitMQ Server is included in the installation.

64 64 NetApp Connect 5.1 Server Installation and Administration Guide In this field Virtual Host Virtual Host Trust Location Type or do the following Use this field only for multitenant brokers, meaning the Policy Engine connecting to multiple brokers, and only under the supervision of support services. Use this field only for multitenant brokers, meaning the Policy Engine connecting to multiple brokers, and only under the supervision of support services. 5. In the RabbitMQ Configuration section, view or complete the fields as follows: In this field Plug-ins Certificates Network token This network node Join network node Policies: HA queues RabbitMQ Log rotation Type or do the following The plug-ins are included in the installation. If you must update them, use this option. Certifications are made in the Identify Management page and plugged in on this page. If you must update them, use this option. Use this field if you are clustering machines. All machines in the cluster should use the same network token that you define. View the name of the current network node. Enter the name of the other machine in this cluster. Enable the High Availability queues once per machine. You can verify this by looking at the RabbitMQ policies; if you see ha-ntap in the box, the queues are enabled. Using ha-ntap is recommended for clustered systems. Log files have a tendency to grow. This option schedules a task to archive old log files by renaming them and creating a new file where future entries are listed. This option sets how often the logs are rotated. By default, it is scheduled to run once per month. By default, RabbitMQ logs are located in \RabbitMQ\log. 6. If you are setting the network token, click Set Token. 7. If you are configuring clusters, enter the network node and click one of the following: Option Join Network Cluster Description Joins the current RabbitMQ node to the network cluster.

65 Configuring advanced NetApp Connect options 65 Option Join Engine Cluster Description Joins the current node to the engine cluster. This restarts the broker to join the cluster and sends the messages to the other members of the cluster. Related tasks Configuring for cluster environments by exporting data on page 67 Starting and stopping the NetApp Connect server on page 37 Configuring the NetApp Connect Policy Engine After installation, you might need to change database connection information or reset credentials. You can do this using the Application Boot Manager. Steps 1. Access the Application Boot Manager. 2. To stop the server, from the Application Boot Manager, select Application Control > Stop. 3. Select Boot Configuration > Policy Engine. 4. In the Database Configuration section, complete the fields as follows: In this field Database Type Connection String Username Password Type or do the following If you are using an embedded database provided during the installation, ensure that Embedded is selected. Otherwise, select the type of database you are configuring. Type a string that identifies the database connection. If you do not use an embedded database, this must match the Microsoft or Postgres database information; otherwise, leave the default value. Type a user name to log in to the database; for example, type sa. If you do not use an embedded database, the user name must match the Microsoft or Postgres database information; otherwise, leave the default value. Type a password required to log in to the database; for example, type netapp1. If you do not use an embedded database, the password must match the Microsoft or Postgres database information; otherwise, leave as is. 5. If you changed any information in the Database Configuration section, click Test Connection and then click Initialize Tables.

66 66 NetApp Connect 5.1 Server Installation and Administration Guide 6. In the Engine Clustering section, click Enabled. Use this option when you want to cluster two or more Policy Engine components. When you import settings from one node to another, this option is automatically set. See information about clustering using the import and export option. 7. To reset Policy Engine credentials (credentials of the default realm) to the default state, in the Reset Authentication section, click Reset Credentials. 8. To start the server, from Application Boot Manager, select Application Control > Start. Related tasks Configuring for cluster environments by exporting data on page 67 Configuring the NetApp Connect Domain Storage Engine After installation, you might need to change database connection information or reset credentials. You can do this using the Application Boot Manager. Steps 1. Access the Application Boot Manager. 2. To stop the server, from the Application Boot Manager, select Application Control > Stop. 3. Select Boot Configuration > Domain Storage Engine. 4. In the Database Configuration section, complete the fields as follows: In this field Database Type Connection String Username Type or do the following If you are using an embedded database provided during the installation, ensure that Embedded is selected. Otherwise, select the type of database you are configuring. Enter a string used to identify the database connection. If you do not use an embedded database, this must match the Microsoft or Postgres database information. Otherwise, leave as is. Enter a user name required to log in to the database. If you do not use an embedded database, this must match the Microsoft or Postgres database information. For example, enter sa. Otherwise, leave as is.

67 Configuring advanced NetApp Connect options 67 In this field Password Type or do the following Enter a password required to log in to the database. If you do not use an embedded database, this must match the Microsoft or Postgres database information. For example, enter netapp1. Otherwise, leave as is. 5. If you changed any information in the Database Configuration section, click Test Connection and then Initialize Tables. 6. In the Engine Clustering section, click Enabled. Use this option when you want to cluster two or more Domain Storage Engine components. When you import settings from one node to another, this option is automatically set. See Related links for information about clustering using the import and export option. 7. To reset Domain Storage Engine credentials to their original states, in the Reset Authentication section, click Reset Credentials. 8. To start the server, from the Application Boot Manager, select Application Control > Start. Related tasks Configuring for cluster environments by exporting data on page 67 Configuring for cluster environments by exporting data You can use NetApp Connect in a cluster environment. To do so, you must configure some options to set up the system for a cluster environment. About this task When you use NetApp Connect in a cluster environment, the following issues impact the operation of NetApp Connect: The NetApp Connect Dashboard itself cannot be clustered. Although you can install two or more Dashboards on different machines in the cluster, they are not clustered. Because local folders are not visible to all nodes in a cluster, local folders cannot be shared with cloud or mobile app users. The Application Boot Manager for each cluster should be started sequentially so that each one becomes visible to the others. Clustered Policy Engines and Domain Storage Engines require the use of common external databases rather than embedded databases.

68 68 NetApp Connect 5.1 Server Installation and Administration Guide Clustered Domain Storage Engines require an external common file share for Vulcan File System (VFS), which is a file-based cache. Steps 1. Draft a design, including role assignments and host name assignments to nodes. 2. Using the installation procedure, install NetApp Connect on the first node. 3. On the first node, access the Application Boot Manager. 4. On the first node, select Boot Configuration > Import/Export. 5. Click Export Node. 6. Copy the generated XML from the text box. 7. Using the installation software, install NetApp Connect on the second node. 8. On the second node, select Boot Configuration > Import/Export. 9. On the second node, paste the XML copied in Step 7 into the Payload box in the Import Node Settings section. 10. Enter the root keystore password, which is the password created in the Identify Manager. 11. Click Import and wait for the operation to finish. 12. Click Continue. 13. To start the server, from the Application Boot Manager, select Application Control > Start. Related concepts Distributed satellite NetApp Connect servers on page 23 Validating the cluster environment configuration You should verify that the cluster environment is configured correctly. For example, you might find that the multiple nodes do not appear. Steps 1. Access Application Boot Manager. 2. From the Application Control screen, note the existence of both nodes. 3. If both nodes do not appear, perform the following tasks: a. Check to see whether the RabbitMQ nodes are clustered.

69 Configuring advanced NetApp Connect options 69 RabbitMQ is impacted by high latency between nodes and might lose connectivity. For details, see the RabbitMQ clustering guide. b. If one of the two nodes shut down, look at the node's system log. This typically indicates an incorrect database encryption string. 4. To start the server, from Application Boot Manager, select Application Control > Start. 5. Start the server on the next node by repeating the steps. Changing NetApp Connect ports You can change inbound and outbound ports for NetApp Connect. You might want to change ports if another application is using the port. Steps 1. Access the Application Boot Manager. 2. To stop the server, from the Application Boot Manager, select Application Control > Stop. 3. Select Boot Configuration > Miscellaneous. 4. Change one or both of the following: Inbound Port Changes the port number for incoming requests or messages. Outbound Port Changes the port number for outgoing requests or messages. 5. Click Set. 6. To start the server, from the Application Boot Manager, select Application Control > Start. Configuring the session timeout From the Application Boot Manager (ABM), you can set the number of minutes that elapse without user activity before a user is logged out of the ABM or the Dashboard. Configuring the session timeout improves security. Steps 1. Access Application Boot Manager. 2. Select Miscellaneous. 3. In the ABM/Dashboard Settings section, enter the number of minutes in the Session Timeout field.

70 70 NetApp Connect 5.1 Server Installation and Administration Guide Viewing NetApp Connect server status logs You might find it helpful to use NetApp Connect logs when you are troubleshooting an issue. Steps 1. Access the Application Boot Manager and select System Log. This option displays the Application Boot Manager System Log, Dashboard System Log, and NetApp Connect Server System Log. 2. If you cannot access the Application Boot Manager, locate the system log in this directory: \install_directory\netapp\connect Server\system.log. Advanced NetApp Connect Dashboard configuration options You might want to further customize NetApp Connect with optional advanced features that you configure using the Dashboard. You can configure logs, user information, repository information, and policies. These are not essential to the initial setup. The Dashboard is the primary administration interface. Similar to the Application Boot Manager, the Dashboard is a web application that you can access from other hosts to perform management tasks. The difference is that while you use the Application Boot Manager to manage software components required by the server, you use the Dashboard to manage the server itself. You can set the following configuration options: Logs Enables you to view recent log entries, such as user login, logout, and server start messages. User settings Enables you to view the list of names and roles of currently online users. Enables you to identify which users are currently online. Repository settings Enables you to add, update, and delete repositories. (Set up during initial installation.) Enables you to provision user access in each repository. (Set up during initial installation.) Enables you to set user home folders on the cloud or mobile app interfaces.

71 Enables you to set filtering rules to govern file access on the cloud or mobile app interfaces. Enables you to reindex repository contents for successful rendering on the cloud or mobile app interfaces. Policy and configuration settings Configuring advanced NetApp Connect options 71 Enables you to configure provisioning so that the cloud or mobile app interfaces recognize the server. (Set up during initial installation.) Enables you to set secure web tunneling options. (Set up during initial installation.) Enables you to set up authentication, Active Directory authentication, and RSA SecurID configuration. (Set up during initial installation.) Enables you to set administrative policies, such as offline support for users, on-device caching, and offline access time. Related tasks Adding repositories on page 41 Accessing the NetApp Connect Dashboard You use the Dashboard to configure initial settings and later update those settings. Before you begin You must be using a browser other than Internet Explorer 9 in enhanced security mode (which Windows Server 2008 R2 runs by default). Steps 1. Do one of the following: If you are continuing from the Application Boot Manager (ABM), select Boot Configuration > Jump to Dashboard.

72 72 NetApp Connect 5.1 Server Installation and Administration Guide Otherwise, log in to the Dashboard by entering the following address: 2. Type the name of the realm that you entered in the Application Boot Manager (ABM) Quick Start Configuration. The realm name is case sensitive. 3. Type the default user name: admin. 4. Click Login. The server validates the realm and user name and then prompts for a password. 5. Type the default password: admin. 6. Click Login again. The Dashboard appears:

73 Configuring advanced NetApp Connect options 73 After you finish Continue configuring policies and repositories using the Dashboard. As soon as possible, you should customize the user name and password. Related tasks Changing your NetApp Connect Dashboard password on page 73 Changing your NetApp Connect Dashboard password The NetApp Connect server uses two passwords: one for the Application Boot Manager and one for the Dashboard. You can change either password anytime. About this task Changing your Dashboard password applies only for the internal database authentication. If you use a different database, the passwords are controlled by that system. If Active Directory has been configured, you cannot change your Dashboard password. You should change the password of the default realm; you should not use the default password. Steps 1. Access the Dashboard by entering the following URL in your browser: your_netapp_connect_server:8080/dashboard. 2. Log in as a member of the Administrator group. 3. In the Dashboard, select <user login name> > Account Setting in the top right corner of the page.