webapplicationsinstallation - epicor · revisionhistory date descriptionofupdate page 7/31/2015...

Web Applications Installation

version 2018.2

DisclaimerThis document is for informational purposes only and is subject to change without notice. This doc-ument and its contents, including the viewpoints, dates and functional content expressed herein arebelieved to be accurate as of its date of publication. However, Epicor Software Corporationmakes noguarantee, representations or warranties with regard to the enclosed information and specifically dis-claims any applicable implied warranties, such as fitness for a particular purpose, merchantability, sat-isfactory quality or reasonable skill and care. As each user of Epicor software is likely to be unique intheir requirements in the use of such software and their business processes, users of this document arealways advised to discuss the content of this document with their Epicor account manager. All inform-ation contained herein is subject to change without notice and changes to this document since printingand other important information about the software product aremade or published in release notes, andyou are urged to obtain the current release notes for the software product. Wewelcome user commentsand reserve the right to revise this publication and/or make improvements or changes to the products orprograms 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 theperformance of any consulting services by Epicor personnel shall be pursuant to Epicor's standard ser-vices terms and conditions. Usage of the solution(s) described in this document with other Epicor soft-ware or third party productsmay require the purchase of licenses for such other products. Where anysoftware is expressed to be compliant with local laws or requirements in this document, such com-pliance is not a warranty and is based solely on Epicor's current understanding of such laws and require-ments. All laws and requirements are subject to varying interpretations aswell as to change andaccordingly Epicor cannot guarantee that the software will be compliant and up to date with suchchanges. All statements of platform and product compatibility in this document shall be considered indi-vidually in relation to the products referred to in the relevant statement, i.e., where any Epicor softwareis stated to be compatible with one product and also stated to be compatible with another product, itshould not be interpreted that such Epicor software is compatible with both of the products running atthe same time on the same platform or environment. Additionally platform or product compatibilitymayrequire the application of Epicor or third-party updates, patches and/or service packs and Epicor has noresponsibility for compatibility issueswhichmay be caused by updates, patches and/or service packsreleased 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 UnitedStates, certain other countries and/or the EU. All other trademarksmentioned are the property of theirrespective owners.

Copyright © Epicor Software Corporation 2018.

All rights reserved. No part of this publicationmay be reproduced in any formwithout the prior writtenconsent of Epicor Software Corporation.


- 2 -

Revision HistoryDate Description of Update Page

7/31/2015 Beta Release N/A

10/30/2018 Corrections and clarifications. Added AccessWeb Applications section. N/A


- 3 -

Table of ContentsBefore You Begin 5

About This Guide 6Requirements 7

SSLConfiguration for Prophet 21Web Applications 8

Primary Domain and Subdomains 8

SSL Recommendations/Requirements 8

SSL Certificates in IIS 8

Supported Browsers 10

Configure Server Roles 11WindowsServer 2008 R2 12

Configure Application Server Roles 12

Configure File ServicesRole 12

ConfigureWeb Server Role 13

WindowsServer 2012 15

WindowsServer 2016 18

Begin Add Roles and FeaturesWizard 18

Features 18

Role Services 19

Confirm and Install 21

Installing Web Applications 22Configuring Prophet 21Web Applications 29


- 4 -

Before You BeginBefore using any of the Prophet 21Web Applications, including the Prophet 21Web Applic-ation,Prophet 21Mobile Sales and Customer Profitability Analyzer (CPA), youmust be licensed for theapplication and then install it using the installation wizard. All of theWeb Applications use the sameinstallation wizard. Although the wizardmay show any or all of these applications as available for install,the wizard will only complete installation of those components for which you are licensed.

Note:The Prophet 21Web Application does not require a license, but it does require that youhave a subscriber domain set up in Epicor’s licensing center. If you do not know what you sub-scriber domain is, enter a case with Epicor support.


- 5 -

About This GuideThis guide describes the process of installing and configuring your Prophet 21Web Applications, and isdivided into the following sections:

l Configuring Server Roles – This section walks you through the steps to configure applicationserver roles, file services roles, and web server roles.

l Installing Prophet 21 Web Applications – This section walks you through theWeb Applic-ations InstallationWizard.

l Configuring Prophet 21 Web Applications – This section walks you through configuring yourWeb Applications.

About ThisGuide Web Applications Installation

- 6 -

RequirementsBefore you can install the Prophet 21Web Applications software, review the following prerequisites.

Important!The user installing theWeb Applicationsmust be part of theWindows domain.

l TheWeb Applications server must be withinWindows domain

l TheMicrosoft .NET Framework version 3.5 AND .NET Framework version 4.6 or later must beinstalled on the server

l A valid public SSL certificatemust be configured in IIS prior to performing theWeb Applicationsinstall. See the section above for more information about SSL certificates.

Note:Self-signed certificates are not supported.

l Information about hardware recommendations for the Prophet 21 Desktop andWeb Applicationscan be found on the Epicor CustomerWeb Site under Support, Documentation, HardwareRequirements.

l Prophet 21Middlewaremust be installed.

Tip: For information on installing the Prophet 21Middleware, please refer to the Prophet21Middleware Installation Guide.


- 7 -

SSL Configuration for Prophet21 Web ApplicationsThere are several approaches to configuring security in your Web Applications. There aremany dif-ferent variables involved in requesting an SSL certificate from aCertificate Authority (CA) such as Ver-isign or GoDaddy. Review this section for information on security your Web Applications.

Primary Domain and SubdomainsMore than likely, your company already has a domain (i.e. epicor.com) registered with a valid domainregistrar. This is your primary domain, which you can use for your corporate website and email.

A subdomain is amethod to further organize web site content under your primary domain. Subdomainsadd a new level onto the front of your domain where a URL can rout traffic to either another website ordirectory under a website.

For example, you could provide external access to the Prophet 21 API using a subdomain such as:

l https://p21api.epicor.com

This requires that you configure this subdomain to route to your Prophet 21Middleware API server viathe external port configuration on which the API in running.

SSL Recommendations/RequirementsEpicor recommends purchasing a valid SSL certificate from a trusted Certificate Authority rather thanusing a self-signed certificate.

Epicor recommends purchasing a wildcard SSL certificate so that you can configuremultiple websiteswith SSL. A wildcard SSL certificate protects your primary domain and an unlimited number of its sub-domains.

For example, a single wildcard certificate can secure https://www.mycompany.com, https://p21-mobile.mycompany.com, and https://p21api.mycompany.com. This will allow you to configure sub-domainswith a single certificate.

SSL Certificates in IISProphet 21Web Applications are hosted inMicrosoft Internet Explorer (IIS). Documentation on how togenerate an SSL certificate for IIS is available fromMicrosoft. In addition, Certificate Authorities, suchas Verisign, GoDaddy, Network Solutions, all provide documentation and assistance for installing yourSSL certificate. Epicor recommends following the instructions provided by your chosen CA.


- 8 -

Once you have a valid SSL certificate generated and installed into IIS, theWeb Applications installationwizardswill prompt you for which SSL certificate you wish to use. You can select the appropriate cer-tificate and the installation will bind that SSL certificate to the appropriate HTTPS port.


- 9 -

Supported BrowsersThe Prophet 21Web Application supports use across the following browsers:

l Google™ Chrome – desktop andmobile device support

l Apple Safari® - mobile device support

Prophet 21Mobile Sales and supports use acrossmultiple browsers, including:

l Microsoft Internet Explorer® 10 or later(note that compatibilitymodemay be required)

l Mozilla Firefox®

l Apple Safari®

l Google™ Chrome

You can run any of the above browsers on any operating system or mobile device.

Customer Profitability Analyzer (CPA) supports use acrossmultiple browsers, including:

l Microsoft Internet Explorer® 10 or later

l Mozilla Firefox®

l Google™ Chrome

CPA is designed for desktop use, so while it is possible to access frommobile devices, the screens arenot optimized for mobile viewing and navigation.


- 10 -

Configure Server RolesBefore installing or upgrading Prophet 21Web Applications, youmust configure server roles, includingthe Application Server, File Services, andWeb Server. Use the following steps to configure ServerRoles.

Note that these stepsmay differ based on your environment. If the server roles already exist, you canstill review the list of role features to verify that your roles are configured properly.

This chapter covers configuration of server roles for the following versions ofWindowsServer:

Windows Server 2008 R2 12Windows Server 2012 15Windows Server 2016 18

Configure Server Roles Web Applications Installation

- 11 -

Windows Server 2008 R2Complete the steps in this section only if you are usingWindowsServer 2008 R2.

Configure Application Server RolesComplete these steps to configure the Application Server Role.

1. On the server, openServer Manager, and then select theRoles node.2. In the Roles Summary section, verify that theApplication Server role lists.

a. If the role is listed, click Add Role Services and use the following steps to verify that therequired Application Server role services are installed.

b. If the role is not listed, clickAdd Roles, and then clickNext.3. On the Select Server Roleswindow, selectApplication Server.

a. If the Add RolesWizard opens, clickAdd Required Features to add any required, listedfeatures. For example, youmay need .Net framework andWindow Process Activation Ser-vices. Click Next.

4. On the Introduction to Application Server window, review the noted comments, and then clickNext.

5. On the Select Role Serviceswindow, .Net 3.5.1 is already selected. Select any of the additionoptions, including any of the following, and then clickNext.

6. TCP Port Sharing

l WindowsProcess Activation Service Support

l MessageQueuing Activation

l TCP Activation

l Named Pipes Activation

l Distributed Transactions

l Incoming Remote Transactions

l Outgoing Remote Transactions

l COM+ Network Access

7. ClickNext, and then click Install. The Application Server Role and features install.8. Once the installation completes, clickClose.

Configure File Services RoleComplete the following steps to configure the File Services role.


- 12 -

1. On the server, openServer Manager, and then select theRoles node.2. In the Roles Summary section, verify that Files Services is listed.

a. If the role is listed, click Add Role Services and use the following steps to verify that therequired File Services role services are installed.

b. If the role is not listed, clickAdd Roles, and then clickNext.3. On the Introduction to File Serviceswindow, review the notes, and then clickNext.4. On the Select Server Roleswindow, select File Services, and then clickNext.5. On the Select Roles Serviceswindow, enable the File Server check box, and then clickNext.6. ClickNext, then click Install. The roles, role services, and features install.7. Once the installation completes, clickClose.

Configure Web Server RoleComplete the following steps to configure theWeb Server role.

1. On the server, open Server Manager, and then select the Roles node.2. In the Roles Summary section, verify if theWeb 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 theAdd Role Services link on the right side. Then use the

step below regarding theWeb Server dialog to verify that the requiredWeb Serverrole services have been installed.

3. ClickAdd Roles, and then clickNext.4. On the Select Server Roleswindow, selectWeb Server (IIS), and then clickNext.5. On the Introduction toWeb Services (IIS) window, review the noted comments and clickNext.6. On the Select Role Serviceswindow, select following options:

l CommonHTTP Features:

l Static Content

l Default Document

l Directory Browsing

l HTTP Errors

l HTTP Redirection

l Application Development:

l ASP.NET

l .NET Extensibility

l ASP

l CGI

l ISAPI Extensions (if prompted to install dependencies, select Add Required Role Servicesand then continue)

l ISAPI Filters

l Server Side Includes


- 13 -

l Health and Diagnostics:

l HTTP Logging

l Logging Tools

l Request Monitor

l Tracing

l Custom Logging

l ODBC logging

l Security:

l Basic Authentication

l WindowsAuthentication

l Digest Authentication

l Client CertificateMapping Authentication

l IIS Client CertificateMapping Authentication

l URLAuthorization

l Request Filtering

l IP and Domain Restrictions

l Performance

l Static Content Compression

l Management Tools

l IIS Management Console

l IIS 6Management Compatibility

7. ClickNext, and then, click Install. The roles, role services or features install.8. Once the installation completes, clickClose.


- 14 -

Windows Server 2012Complete the steps to configure the Application Server role andWeb Server role usingWindowsServer 2012.

Note that if the roles already exist, you can still review the list of role features to verify that your roles areconfigured properly.

1. On the server, open Server Manager.2. In the left pane, selectApp Server.3. In the Roles and Features section verify thatApplication Server andWeb Server (IIS) Sup-

port are listed.a. If the Server roles are present in the sameRoles 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 theManagemenu, selectAdd Roles and

Features.4. On theAdd Roles and Featureswizard, in theBefore you Begin section, review the inform-

ation, and then clickNext.5. On theSelect Installation Type page, selectRole-Based or Feature-Based Installation,

and then clickNext.6. On theSelect destination server page, verify that your server is selected in the Server Pool list,

and then clickNext.7. On theSelect Server Roles page, select theApplication Server role, File and Storage Ser-

vices role, and theWeb Services (IIS) role.Note that the IIS Management Console is required for theWeb Server role installation

8. ClickAdd Features, and then clickNext.9. On theSelect Features page, verify that .Net Framework 4.5 is selected, and then clickNext.10. On theApplication Server page, clickNext.11. On theSelect Roles Serviceswindow, select the following options, and then clickNext.

l COM+ Network Access

l TCP Port Sharing

l WindowsProcess Activation Service Support

l MessageQueuing Activation

l TCP Activation

l Named Pipes Activation

l Distributed Transactions

l Incoming Remote Transactions

l Outgoing remote Transactions

12. On the File and Storage Service page, click Next.13. On theSelect Role Service page, select File and iSCSI Services, select the File Server ser-

vice to install, and then clickNext.14. On theWeb Server Role (IIS) page, clickNext.15. On theRole Service page, select theWeb Server and any of the following services to install.

Then clickNext.


- 15 -

l CommonHTTP Features

l Default Document

l Directory Browsing

l HTTP Errors

l HTTP Redirection

l Static Content

l Application Development

l .Net Extensibility 3.5

l .Net Extensibility 4.6

l ASP

l ASP .NET 3.5

l ASP .NET 4.6

l CGI

l ISAPI Extensions

l ISAPI Features

l Server Side Includes

l Health and Diagnostics

l HTTP Logging

l Custom Logging

l Logging Tools

l ODBC Logging

l Request Monitor

l Tracing

l Performance

l Static Content Compression

l Dynamic Content Compression

l Management Tools

l IIS Management Console

l IIS 6Management Compatability

l IIS Management Scripts and Tools


- 16 -

l Security

l Request Filitering

l Basic Authentication

l Client CertificationMapping Authentication

l Digest Authentication

l IIS Client CertificateMapping Authentication

l IP and Domain Restrictions

l URL Authorization

l Window Authentication

16. On theConfirmation page, click Install. The server roles and features install.17. Once the installation completes, close the Server Manager.


- 17 -

Windows Server 2016When runningWindowsServer 2016 use the instructions in this section to install the necessaryFeatures and Role Services.

Note that if the roles and features already exist, you can still review the items to verify that configurationis correct.

Begin Add Roles and Features WizardOn the server, open the Server Manager application fromwhere you can launch the Add Roles andFeaturesWizard.

1. FromServer Manager , select Local Server from the left panel.2. From theManagemenu, selectAdd Roles and Features. The Add Roles and FeaturesWizard

displays.3. On theBefore you Begin page, review the information, and then clickNext.4. On Installation Type, verify that the defaultRole-Based or Feature-Based Installation

option is selected, and then clickNext.5. On theServer Selection page, verify that your server is selected in theServer Pool list, and

then clickNext.6. On theServer Roles page, selectWeb Server (IIS). The result and your next actions depend

on the current server configuration.

l If theWeb Server (IIS) has not been installed yet, the wizard presents you with theAddfeatures that are required for Web Server (IIS) box. Click theAdd Features button.You complete the Features first and then configure the Server Roles. Refer to Featuressection.

l If the Features for Web Server (IIS) are already installed, you select the Role Services.Refer to Role Services section.

FeaturesAfter theWeb Server (IIS) role is selected, if not installed, you will select the Features to install. Expandthe appropriate node to find the Features to select.

1. If the wizard presents you with theAdd features that are required for Web Server (IIS) box,click theAdd Features button.

2. On the Features page, select Features as illustrated in the following table.Navigate to Features Select these Features

.NET Framework 3.5 Features > .NET Framework 3.5 (includes .NET 2.0 and3.0)


- 18 -

Navigate to Features Select these Features

.NET Framework 4.6Features >

.NET Framework 4.6

ASP.NET 4.6

.WCF Services > HTTP Activation

Message Queuing (MSMQ) Activation

Named Pipe Activation

TCP Activation

TCP Port Sharing3. After selecting Features, clickNext.

Role ServicesOn theServer Roles page, withWeb Server (IIS) selected, you can select the appropriate Role Ser-vices. WithinWeb Server (IIS), you select options fromWeb Server andManagement Tools. Selectingthe role services follows the Featureswhen theWeb Server (IIS) has not been installed.

1. On theServer Roles page, expand theWeb Server (IIS) node, and select the roles as illustratedin the following table.


- 19 -

FromWeb Server (IIS) role navigate to... ...and then select the Role Service

Web Server > CommonHTTP Features > Default Document

Directory Browsing

HTTP Errors

Static Content

HTTP Redirection

Health and Diagnostics > HTTP Logging

Custom Logging

Logging Tools

ODBC Logging

Request Monitor

Tracing

Performance > Static Content Compression

Dynamic Content Compression

Security > Request Filtering

Basic Authentication

Client Certificate Mapping Authenticate

Digest Authentication

IIS Client Certificate Mapping Authentic-ate

IP and Domain Restrictions

URL Authentication

Windows Authentication

Application Development > .NET Extensibility 3.5

.NET Extensibility 4.6

ASP

ASP.NET 3.5

ASP.NET 4.6

CGI

ISAPI Extensions

ISAPI Filters

Server Side Includes


- 20 -

FromWeb Server (IIS) role navigate to... ...and then select the Role Service

Management Tools>

IIS Management Console

IIS 6Management Compatibility > IIS 6 Metabase Compatibility

IIS Management Scripts and Tools2. After selecting Role Services, clickNext

Confirm and InstallAfter you have selected your Features and Role Services for Web Server (IIS), you can review theselections before you install them.

1. On the wizardConfirmation page, review the list of Features and Role Services.2. If the selections look accurate, click Install. The server roles and features install.3. Once the installation completes, close the Server Manager.


- 21 -

Installing WebApplications

Important! Youmust install the Prophet 21Middleware before installing the Prophet 21WebApplications. For information on installing the Prophet 21Middleware, please refer to theMid-dleware Installation Guide.

1. Download theEpicor.P21.WebApps.Setup.2018.X.xxxx.Install.exeWebApplicationsInstaller from the Downloads page of the CustomerWeb Site.

2. Navigate to the location that you saved the installer.

Note:RMB andmake sure Unblock does not show in bottom right

1. Right-click the file name and selectRun as administrator. The Prophet 21Web ApplicationsSetupWizard opens to guide you through the installation process.

InstallingWeb Applications Web Applications Installation

- 22 -

2. At theWelcome install dialog box, clickNext.


- 23 -

3. Select the instance name for your Web Applications, and then clickNext.

Tip: To enter a new instance name, selectNew and enter the new name.


- 24 -

4. Select the folder location in which you would like to install your Web Applications, or accept thedefault location, and then clickNext.

5. If this is a new folder, a window pops up asking if you would like to create the folder. ClickYes tocreate the folder and continue the installation.


- 25 -

6. Select the components that you want to install, and then click Next. For example, options thatmay be available to select are Prophet 21WebClient, and Prophet 21Mobile Sales.

Important! The dialog box lists all components available for installation. The list is not limitedto only those components for which you hold a license.


- 26 -

7. Verify the installation settings, and then click Install.All necessary files copy to your destination location.


- 27 -

Once the installation is complete, the Prophet 21Web Applications Setup wizard advances to the con-figuration of the selected component(s).


- 28 -

Configuring Prophet 21 WebApplicationsThe Prophet 21Web Applications configuration tool automatically opens once the installation com-pletes. This configures your Web Applications so that they can access your Prophet 21 database.

1. ClickNext to begin theWeb Applications configuration process.


- 29 -

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 theMy Organization Uses a Proxy Server

check box and enter your proxy server, user name, and password.4. ClickNext.

Important: The configuration tool verifies your licenses and domain. If you do not havethe proper licenses for the installation type, you will not be able to continue.

5. The web site name and application pool default based on the instance name. You can changethese names if necessary; however, Epicor recommends that you accept the default names.

6. If this is the first instance ofWeb Applications that you have installed, accept the default port num-ber. Each instance that you install requires a unique port number. If you are installingmultipleinstances, youmust change the default port number for each subsequent instance.

7. Click the ... button to select your SSL certificate.


- 30 -

8. Select the certificate to use for security, and then clickOK to return to the App Configuration win-dow.

9. ClickNext.

10. Enter the fully qualified server name and HTTPS port for theMiddleware instance you wish toconnect to. TheMiddleware instance determines the Prophet 21 database to which theWebApplication connects. The server namemust be the fully qualified server name that matches theSSL certificate.


- 31 -

Tip: If you do not know your server name or port number, navigate to Internet Information Ser-vices (IIS) Manager. Expand the server and sites. Select your Middleware site and find yourport number on the right-hand side of the screen.

11. Enter your ERP user name and password for theMiddleware instance.12. ClickNext.

13. All Web Applications that you selected during the installation steps InstallingWeb Applications onpage 22 list. You can have any combination of Prophet 21Client, Prophet 21Mobile Sales, andCustomer Profitability Analyzer. ClickNext to continue the configuration.

14. If you are licensed for Prophet 21 Mobile Sales:


- 32 -

l Enable theYes option to set up SMTP to send emails through your server. Fill inyour SMTP server information.

Note: The SMTP Server needs to permit relay of the Web Applicationsserver if you are not using authentication.

l If you opt not to setup SMTP at this time, you can configure it at a later time.

l ClickNext.

15. Configure your Prophet 21Mobile Sales Settings:


- 33 -

l Enter the amount of time, in seconds, to allow before timing out when sending andreceiving information fromProphet 21. The timeout defaults to 180 seconds.

l Enter the amount of time, in seconds, to allow before authenticating user log ins.The timeout defaults to 120 seconds.

l Enter the amount of time, in minutes, to allow before timing out a user session. Thetimeout defaults to 15minutes.

l ClickNext.

16. For the Prophet 21WebClient:

l Currently, there are no configurable settings for the Prophet 21WebClient. ClickNext.


- 34 -

17. Review a summary of the setup selections, and then clickRun Setup.As the setup runs, the wizard checks off each setup as it completes. If any step fails, the con-figuration 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 toopen your Web Applications in a browser. Save or bookmark each URL.


- 35 -

webapplicationsinstallation - epicor · revisionhistory date descriptionofupdate page 7/31/2015...

Documents