Chat now with support
Chat with Support

erwin Evolve 2020.1.1 - User Guide

erwin_Evolve_User_Guide
erwin_Evolve_User_Guide
Getting Started Creating Sites and Pages Data Layout Options Filtering Data Property Groups Data Visualizations Displaying Diagrams Using Web Modeler Automatic Diagrams (Diagram Designer) Navigating your Site Workflow Explained Social Interaction Features Questionnaires Reference Configuration and Administration Customizing Your Site Troubleshooting Upgrading

File Structure

File Structure

Overview of the folder structure of Evolve Web Platform

If you have configured your site to replicate content from one server to another, for example when using a load balancer, you may need to adjust your 'Copy' scripts for 2020.0.2 onwards. See the details below to determine what folders have moved.

Unlike many Windows applications, including 'Evolve Suite', 'Evolve Web Platform' is typically installed to the root of your C: drive.
While most of the files that are installed are not intended for user serviceability, there are a few folders that contain content, useful for administrators. Most significantly, folders containing customized content, search indexes, and generated content. All of which may be replicated to other servers, when load balancing.

Up to and including Evolve Web Platform 2020.0.1 the folders followed this pattern:

Folder

Description

c:\erwin\evolve            [or]
c:\casewise\evolve

Main installation folder

\CWSServices

Global Search services

\CWSServices\Data

Global Search encrypted audit records, for indexing (and sharing to other servers in a load balanced group)

\Data\Common

Shared web client content for all sites (javascript)

\Data\Sites\[sitename]

Specific content for the given dynamic site sitename
This would include any temporarily generated content, such as gallery content, images, user pictures, diagrams, hotspot maps etc.

\Data\Statics\[sitename]

Specific content for the given static site sitename
This would include all generated static site content.
The static content could also be used by a dynamic site, with static pages.

\Diagrammer

The new Web Modeler application service

\ElasticSearch

The elastic search runtimes to operate Global Search

\Elasticsearch\elasticsearch-6.4.0\data\nodes

The elastic search database files. If upgrading within the same Major release version, these files can be kept, to remove the need for a full search re-index. In large installations this can save many hours of re-indexing.

\JRE

The Java runtime to support ElasticSearch and other Java components

\node_modules

The node modules required to support Web Modeler

\Site\bin\sites

The site configuration files that describe site settings

\Site\bin\webDesigner\custom

The location for customization files for Evolve Web Platform

\Site\logs

The Web Designer, Diagram Designer, and Live log files for the platform

\WebRestAPI

The REST API that replaces Portal Web Services, and supports interaction over a http interface

What has changed from 2020.0.2 onwards, is the location of the static generated content, and any data related content for the dynamic site. The new structure is as follows:

Folder

Description

\Data\Sites\[sitename]

Site structure and design for the given dynamic site sitename
This NO LONGER includes any site content / data.

\Data\Statics\[sitename]

Site structure and design for the given static site sitename
This NO LONGER includes any site content / data.
The generated JSON files are NOT put here.

\Data\Data\[sitename]\live\

Content data for the site sitename
This includes images, gallery content, user pictures, temporary diagram images, hotspot maps etc.

\Data\Data\[sitename]\static\

Content data for the site sitename
This includes all generated static site content.
The static content could also be used by a dynamic site, with static pages.

 Related Topics

Global Search

Customization Explained

Required MIME Types

Required MIME Types

Your web server machine must be configured to understand some specific file formats used by Evolve.

The instructions below alter the settings for the Evolve application only. You can make these settings at a higher level, such as the Default Web Site, that will then ensure they are available to all applications below.

To specify the new MIME Types:

          1. On the web server machine, run Internet Information Services (IIS) Manager

          2. In IIS Manager’s left-hand pane, select the node for the Evolve application

          Ensure you have the central pane set to Features View, then double-click MIME Types in the IIS section

          The MIME Types settings are displayed

          3. Check the list of extensions that are already configured and see if any of the following are missing:

.eot

.json

.ttf

.woff

          4. For each extension that is not already configured, do the following:

i. Right-click in the central pane and select Add�

ii. Enter the following details, depending on which you need to add

File name extension

MIME Type

.eot

application/octet-stream

.json

application/json

.ttf

application/octet-stream

.woff

application/font-woff

iii. Click OK

          5. Close IIS Manager.

 

Configuration and Administration

Configuration and Administration

Server Configuration

Server Configuration

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating