Web Applications Installation. version 12.17

Transcription

1 version 12.17

2 Disclaimer This document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is likely to be unique in their requirements in the use of such software and their business processes, users of this document are always advised to discuss the content of this document with their Epicor account manager. All information contained herein is subject to change without notice and changes to this document since printing and other important information about the software product are made or published in release notes, and you are urged to obtain the current release notes for the software product. We welcome user comments and reserve the right to revise this publication and/or make improvements or changes to the products or programs described in this publication at any time, without notice. The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage of the solution(s) described in this document with other Epicor software or third party products may require the purchase of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of platform and product compatibility in this document shall be considered individually in relation to the products referred to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible with both of the products running at the same time on the same platform or environment. Additionally platform or product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs released by third parties after the date of publication of this document. Epicor is a registered trademark and/or trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other trademarks mentioned are the property of their respective owners. Copyright Epicor Software Corporation All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of Epicor Software Corporation

3 Revision History Date Description of Update Page 7/31/2015 Beta Release N/A - 3 -

4 Table of Contents Before You Begin 5 Using this Guide 6 Requirements 7 SSL Configuration for Prophet 21 Web Applications 8 Primary Domain and Subdomains 8 SSL Recommendations 8 SSL Certificates in IIS 8 Supported Browsers 10 Configure Server Roles 11 Configure Server Roles Using Windows Server 2008 R2 12 Configure Application Server Roles 12 Configure File Services Role 13 Configure Web Server Role 13 Configure Server Roles Using Windows Installing Web Applications 19 Configuring Prophet 21 Web Applications

5 Before You Begin Before You Begin Before using any of the Prophet 21 Web Applications, including Prophet 21 Mobile Sales, DynaChange Mobile Portals (via EMA), and Customer Profitability Analyzer (CPA), you must install the applications. All three of the Web Applications use the same installation wizard. The wizard identifies which applications you hold licenses for and installs only those components

6 Before You Begin Using this Guide This manual describes the process of installing and configuring your Prophet 21 Web Applications, and is divided into the following sections: Configuring Server Roles This section walks you through the steps to configure application server roles, file services roles, and web server roles. Installing Prophet 21 Web Applications This section walks you through the Web Applications Installation Wizard. Configuring Prophet 21 Web Applications This section walks you through configuring your Web Applications

7 Before You Begin Requirements You should review the hardware and size requirements for your server: Intel E5-2643v3 (6 core) processor or better 12GB memory 4 SAS (15,000 rpm) or 2 SSDs drives 4 drives in RAID10 / 2 SSDs in RAID1 RAID controller with 1+GB cache memory (e.g. Dell s H730P) Windows Server 2008 R2 or later Prophet 21 Middleware Tip: For information on installing the Middleware framework, please refer to the Middleware Installation Guide - 7 -

8 Before You Begin SSL Configuration for Prophet 21 Web Applications There are several approaches to configuring security in your Web Applications. There are many different variables involved in requesting an SSL certificate from a Certificate Authority (CA) such as Verisign or GoDaddy. Review this section for information on security your Web Applications. Primary Domain and Subdomains More than likely, your company already has a domain (i.e. epicor.com) registered with a valid domain registrar. This is your primary domain, which you can use for your corporate website and . A subdomain is a method to further organize web site content under your primary domain. Subdomains add a new level onto the front of your domain where a URL can rout traffic to either another website or directory under a website. For example, you could provide external access to the Prophet 21 API using a subdomain such as: This requires that you configure this subdomain to route to your Prophet 21 Middleware API server via the external port configuration on which the API in running. SSL Recommendations Epicor recommends purchasing a valid SSL certificate from a trusted Certificate Authority rather than using a self-signed certificate. Self-signed certificate are fine for internal testing, but not for external public consumption, Epicor recommends purchasing a wildcard SSL certificate so that you can configure multiple websites with SSL. A wildcard SSL certificate protects your primary domain and an unlimited number of its subdomains. For example, a single wildcard certificate can secure mobile.mycompany.com, and This will allow you to configure subdomains with a single certificate. SSL Certificates in IIS Prophet 21 Web Applications are hosted in Microsoft Internet Explorer (IIS). Documentation on how to generate an SSL certificate for IIS is available from Microsoft. In addition, Certificate Authorities, such - 8 -

9 Before You Begin as Verisign, GoDaddy, Network Solutions, all provide documentation and assistance for installing your SSL certificate. Epicor recommends following the instructions provided by your chosen CA. Once you have a valid SSL certificate generated and installed into IIS, the Web Applications installation wizards will prompt you for which SSL certificate you wish to use. You can select the appropriate certificate and the installation will bind that SSL certificate to the appropriate HTTPS port

10 Before You Begin Supported Browsers Prophet 21 Mobile Sales and DynaChange Mobile Portals support use across multiple browsers, including: Microsoft Internet Explorer 10 or later Mozilla Firefox Apple Safari Google Chrome You can run any of the above browsers on any operating system or mobile device. Customer Profitability Analyzer (CPA) supports use across multiple browsers, including: Microsoft Internet Explorer 10 or later Mozilla Firefox Google Chrome CPA is designed for desktop use, so while it is possible to access from mobile devices, the screens are not optimized for mobile viewing and navigation

11 Configure Server Roles Configure Server Roles Before installing or upgrading Prophet 21 Web Applications, you must configure server roles, including the Application Server, File Services, and Web Server. Use the following steps to configure Server Roles. Note that these steps may differ based on your environment. If the server roles already exist, you can still review the list of role features to verify that your roles are configured properly

12 Configure Server Roles Configure Server Roles Using Windows Server 2008 R2 Complete the steps in this section only if you are using Windows Server 2008 R2. If you use Windows Server 2012, refer to the steps in Configure Server Roles Using Windows 2012 on page 15. Configure Application Server Roles Complete these steps to configure the Application Server Role. 1. On the server, open Server Manager, and then select the Roles note. 2. In the Roles Summary section, verify that the Application Server role lists. a. If the role is listed, click Add Role Services and use the following steps to verify that the required Application Server role services are installed. b. If the role is not listed, click Add Roles, and then click Next. 3. On the Select Server Roles window, select Application Server. a. If the Add Roles Wizard opens, click Add Required Features to add any required, listed features. For example, you may need.net framework and Window Process Activation Services. Click Next. 4. On the Introduction to Application Server window, review the noted comments, and then click Next. 5. On the Select Role Services window,.net is already selected. Select any of the addition options, including any of the following, and then click Next. 6. TCP Port Sharing Windows Process Activation Service Support Message Queuing Activation TCP Activation Named Pipes Activation Distributed Transactions Incoming Remote Transactions Outgoing Remote Transactions COM+ Network Access 7. Click Next, and then click Install. The Application Server Role and features install. 8. Once the installation completes, click Close

13 Configure Server Roles Configure File Services Role Complete the following steps to configure the File Services role. 1. On the server, open Server Manager, and then select the Roles node. 2. In the Roles Summary section, verify that Files Services lists. a. If the role is listed, click Add Role Services and use the following steps to verify that the required File Services role services are installed. b. If the role is not listed, click Add Roles, and then click Next. 3. On the Introduction to File Services window, review the notes, and then click Next. 4. On the Select Server Roles window, select File Services, and then click Next. 5. On the Select Roles Services window, enable the File Server check box, and then click Next. 6. Click Next, then click Install. The roles, role services, and features install. 7. Once the installation completes, click Close. Configure Web Server Role Complete the following steps to configure the Web Server role. 1. On the server, open Server Manager, and then select the Roles node. 2. In the Roles Summary section, verify if the Web Server role is listed. a. If this role is not listed, use the following steps to add the roles services. b. If the role is listed, click the Add Role Services link on the right side. Then use the step below regarding the Web Server dialog to verify that the required Web Server role services have been installed. 3. Click Add Roles, and then click Next. 4. On the Select Server Roles window, select Web Server (IIS), and then click Next. 5. On the Introduction to Web Services (IIS) window, review the noted comments and click Next. 6. On the Select Role Services window, select following options: Common HTTP Features: Static Content Default Document Directory Browsing HTTP Errors HTTP Redirection

14 Configure Server Roles Application Development: ASP.NET.NET Extensibility ASP CGI ISAPI Extensions (if prompted to install dependencies, select Add Required Role Services and then continue) ISAPI Filters Server Side Includes Health and Diagnostics: Security: HTTP Logging Logging Tools Request Monitor Tracing Custom Logging ODBC logging Basic Authentication Windows Authentication Digest Authentication Client Certificate Mapping Authentication IIS Client Certificate Mapping Authentication URL Authorization Request Filtering IP and Domain Restrictions Performance Static Content Compression Management Tools IIS Management Console IIS 6 Management Compatibility 7. Click Next, and then, click Install. The roles, role services or features install. 8. Once the installation completes, click Close

15 Configure Server Roles Configure Server Roles Using Windows 2012 Complete the steps to configure the Application Server role and Web Server role using Windows If you use Windows Server 2008 R2, refer to the steps in Configure Server Roles Using Windows Server 2008 R2 on page 12. Note that if the roles already exist, you can still review the list of role features to verify that your roles are configured properly. 1. On the server, open Server Manager. 2. In the left pane, select App Server. 3. In the Roles and Features section verify that Application Server and Web Server (IIS) Support list. a. If the Server roles list in the same Roles and Features section, verify that the required Server roles have been installed. Skip to step 11. b. If the Server roles are not listed, from the Manage menu, select Add Roles and Features. 4. On the Add Roles and Features window, in the Before you Begin section, review the information, and then click Next. 5. On the Installation Type window, verify that the default Role-Based or Feature-Based Installation option is selected, and then click Next. 6. On the Server Selection window, verify that your server is selected in the Server Pool list, and then click Next. 7. On the Server Roles window, select the Application Server role, File and Storage Services role, and the Web Services (IIS) role. Note that the IIS Management Console is required for the Web Server role installation 8. Click Add Features, and then click Next. 9. On the Features window, verify that.net Framework 4.5 is selected, and then click Next. 10. On the Application Server window, click Next. 11. On the Roles Services window, select the following options, and then click Next. COM+ Network Access TCP Port Sharing Windows Process Activation Service Support Message Queuing Activation TCP Activation Named Pipes Activation Distributed Transactions Incoming Remote Transactions Outgoing remote Transactions 12. On the File and Storage Service window, click Next

16 Configure Server Roles 13. On the Role Service window, select File and iscsi Services, select the File Server service to install, and then click Next. 14. On the Web Server Role (IIS) window, click Next

17 Configure Server Roles 15. On the Role Service window, select the Web Server and any of the following services to install. Then click Next. Common HTTP Features Default Document Directory Browsing HTTP Errors HTTP Redirection Static Content Application Development.Net Extensibility 3.5.Net Extensibility 4.6 ASP ASP.NET 3.5 ASP.NET 4.6 CGI ISAPI Extensions ISAPI Features Server Side Includes Health and Diagnostics HTTP Logging Custom Logging Logging Tools ODBC Logging Request Monitor Tracing Performance Static Content Compression Dynamic Content Compression Management Tools IIS Management Console IIS 6 Management Compatability IIS Management Scripts and Tools

18 Configure Server Roles Security Request Filitering Basic Authentication Client Certification Mapping Authentication Digest Authentication IIS Client Certificate Mapping Authentication IP and Domain Restrictions URL Authorization Window Authentication 16. On the Confirmation window, click Install. The server roles and features install. 17. Once the installation completes, close the Server Manager

19 Installing Web Applications Installing Web Applications Important! You must install the Middleware framework before installing the Prophet 21 Web Applications. For information on installing the Middleware framework, please refer to the Middleware Installation Guide. 1. Download the P21.WebApps.Setup Web Applications Installer from the Downloads page of the Customer Web Site. 2. Navigate to the location that you save the installer. Right click the file name and select Run as administrator. The Wizard opens

20 Installing Web Applications 3. Click Next

21 Installing Web Applications 4. Select the instance name for your Web Applications, and then click Next. Tip: To enter a new instance name, select New and enter the new name

22 Installing Web Applications 5. Select the folder location in which you would like to install your Web Applications, or accept the default location, and then click Next. 6. If this is a new folder, a window pops up asking if you would like to create the folder. Click Yes to create the folder and continue the installation

23 Installing Web Applications 7. Select the components that you want to install, and then click Next. Important! This lists all components available for installation; it does not limit the list to only those components for which you hold a license

24 Installing Web Applications 8. Verify the installation destination location, and then click Install

25 Installing Web Applications 9. All necessary files copy to your destination location. Once complete, the Prophet 21 Web Applications setup wizard begins

26 Installing Web Applications Configuring Prophet 21 Web Applications The Prophet 21 Web Applications configuration tool automatically opens once the installation completes. This configures your Web Applications so that they can access your Prophet 21 database. 1. Click Next to begin the Web Applications configuration process

27 Installing Web Applications 2. Enter your domain name. This is the same name that you used with your Middleware installation. 3. If your organization uses a proxy server, enable the My Organization Uses a Proxy Server check box and enter your proxy server, user name, and password. 4. Click Next. The configuration tool verifies your licenses. 5. The web site name and application pool default based on the instance name. You can change these names if necessary; however, Epicor recommends that you accept the default names. 6. If this is the first instance of Web Applications that you've installed, accept the default port number. Each instance that you install requires a unique port number. If you are installing multiple instances, you must change the default port number for each subsequent instance. 7. Click the... button to select your SSL certificate. 8. Select the certificate to use for security, and then click OK to return to the App Configuration window. 9. Click Next

28 Installing Web Applications 10. Enter the fully qualified server name and HTTPS port for the server hosting your Prophet 21 API or Middleware. The API instance determines the Prophet 21 database to which the Web Applications connects. Tip: If you do not know your server name or port number, navigate to Internet Information Services (IIS) Manager. Expand the server and sites. Select your API site and find your port number on the right-hand side of the screen. 11. Enter your ERP user name and password for the API instance. 12. Click Next

29 Installing Web Applications 13. All Web Applications that you selected during the installation steps on page 23 list. You can have any combination of P21Mobile, EMA, and CPA. Click Next to continue the configuration. 14. If you are licensed for Prophet 21 Mobile Sales: Enable the Yes option to set up SMTP to send s through your server. You will be prompted to enter your SMTP server information. If you opt not to setup SMTP at this time, you can configure it at a later time. Click Next. 15. Configure your Prophet 21 Mobile Sales Settings:

30 Installing Web Applications Enter the amount of time, in seconds, to allow before timing out when sending and receiving information from Prophet 21. The timeout defaults to 180 seconds. Enter the amount of time, in seconds, to allow before authenticating user log ins. The timeout defaults to 120 seconds. Enter the amount of time, in minutes, to allow before timing out a user session. The timeout defaults to 15 minutes. Click Next. 16. If you are licensed for DynaChange Mobile Portals: Select the amount of time, in hours that a user session can remain idle before the user is automatically logged out. Click Next

31 Installing Web Applications 17. Review a summary of the setup selections, and then click Run Setup. As the setup runs, the wizard checks off each setup as it completes. If any step fails, the configuration stops. 18. Your Web Applications settings are now saved. Close the configuration wizard. Tip: Once the configuration completes, open or refresh your Internet Information Services (IIS) Manager to see your new installations. From here, click Browse on the installation to open your Web Applications in a browser. Save or bookmark each URL