Next Steps
Next Steps
Now Evolve Web Platform is installed, the tasks on the server are complete. The processes for creating, configuring and deploying an Evolve Site are performed by Evolve Administrator using Evolve Designer which is installed on the web server.
You do this using the Server Configuration utility.
All instructions for creating, configuring and publishing Sites are in the Evolve Designer Help, which is accessible from Evolve Designer itself. See Appendix E – Accessing the Evolve Designer Helpfor details.
|
|
In order to run Evolve Designer you must log in with a Casewise user that has System Manager rights. In addition, certain functions performed by Evolve Designer require that the application is Run as administrator on your machine. Additional operations requiring System Manager level rights include: •IIS configuration •IIS feature installation •Meta Model upgrades |
Information Checklist
Information Checklist
Please ensure you capture all the details needed for the Evolve Designer user to continue with the server configuration. See Appendix B – Post Install Information Checklist for details.
Appendix A Pre Install Components
Installation of the Web Server (IIS) Role is required prior to Evolve installation.
To install the IIS Role:
1.Navigate to the Add Roles Wizard and select the Server Roles option.
2.A list of Roles with corresponding checkboxes will display:
3.Check the Web Server (IIS) box.
4.Press the Next button.
▪The Web Server (IIS) role will expand to list the different features to be installed:
5.Check the related checkboxes to install the following features:
|
Application Development Features: •.NET Extensibility 4.7 (or above) •.NET Extensibility 3.5 •ASP.NET 4.7 (or above) •ASP.NET 3.5 •ISAPI Extensions •ISAPI Filter •WebSocket Protocol (for the Diagram Editor)
Security •Basic Authentication •Windows Authentication •Request Filtering |
Performance Features •Dynamic Content Compression Static Content Compression
Common HHTP Features: •Static Content •Default Document •Directory Browsing •HTTP Errors •HTTP Redirection
Health and Diagnostics •HTTP Logging |
Appendix B Post Install Information
In order to create an Evolve Site, the following information gained from the installation needs to be available to the Evolve Administrator:
|
Type |
Description |
Required for |
Deployment Type |
|
IIS USer |
The Username and Password of a User of the web server machine that the Evolve application can run as.
This User must have Administrative rights on the web server machine.
Note: When Active Directory Authentication is used, this IIS User must be part of the domain. |
ISS Configuration when Creating a Site (post installation), or during manual setup of IIS. |
Dynamic Static |
|
CW System Manager User Account |
When running Dynamic Sites you must enter the details of a Casewise System Manager User. |
This account is used by Evolve to access the repository. |
Dynamic |
|
Active Directory USer |
The Username and Password for a domain user which can read the Active Directory. |
Only required if Active Directory Authentication is to be used. |
Dynamic |
|
Active Directory connection path |
The path to connect to the Active Directory. |
Only required if Active Directory Authentication is to be used. |
Dynamic |
|
Active Directory Social User grouP |
The name of the Active Directory group used for Social Users. |
Only required if Active Directory Authentication is to be used. |
Dynamic |
|
Active Directory Contributor User |
The name of the Active Directory group used for Contributing Users. |
Only required if Active Directory Authentication is to be used. |
Dynamic |
|
active directory Diagram user |
The name of the Active Directory group used for Diagram Editor users. |
Only required if Active Directory Authentication is to be used. |
Dynamic |
|
active directory Static user |
The name of the Active Directory group used for Static Site users. |
Only required if Active Directory Authentication is to be used, and Static Authentication is enabled. |
Static |