Eway - Installation Guide
Date: Desember 2012
Build: 5.2
Version: 1.0
1
1
1.
2.
2
Platform requirements ....................................................................... 3
Software .......................................................................................... 3
Server ............................................................................................................................ 3
Client .............................................................................................................................. 3
Hardware ......................................................................................... 3
Minimum configuration...................................................................................................... 3
Recommended configuration .............................................................................................. 3
Extended configuration ..................................................................................................... 3
Scalable configuration ....................................................................................................... 3
eWay Setup ........................................................................................ 4
1.
Copy eway files from the distribution folder .......................................... 4
2.
The eWay database ........................................................................... 4
3.
4.
5.
6.
7.
8.
9.
Troubleshooting ............................................................................................................... 5
Configure the eWay IIS site on a Windows 2000 / Windows 2003 server .. 6
Create a new web-site ...................................................................................................... 6
Add New Application Pool .................................................................................................. 6
Properties of the web-site.................................................................................................. 6
eway and ewaysvc as applications in IIS ............................................................................. 6
WebDav .......................................................................................................................... 7
Dav ................................................................................................................................ 7
WebDAV settings.............................................................................................................. 7
Settings for image store .................................................................................................... 7
Spelling check .................................................................................................................. 7
Install eWay ISAPI Filter ................................................................................................... 8
Configure the eWay IIS site on a Windows 2008 server........................ 10
Installation .................................................................................................................... 10
Create a new web-site .................................................................................................... 10
Other properties of the web-site ....................................................................................... 12
Settings for Application Pool ............................................................................................ 14
Dav .............................................................................................................................. 18
Install the WebDAV Security Modules ................................................................................ 18
Office 2007/2010 MIME types ........................................................... 24
Windows 2003 (IIS6) ...................................................................................................... 24
Windows 2008 (IIS7) ...................................................................................................... 26
Hosts ............................................................................................. 26
File access ...................................................................................... 26
Index the document store ................................................................ 26
Index the document store on a Windows 2000 / Windows 2003 server ................................. 26
Index the document store on a Windows 2008 server ......................................................... 26
Do changes in the Web.config ........................................................... 29
eWay Scheduler Setup ..................................................................... 30
1.
Installation ..................................................................................... 30
2.
Configuration .................................................................................. 30
3.
Add an instance .............................................................................. 30
4.
Adding several instances .................................................................. 32
5.
Start the eWay Scheduler service ...................................................... 32
6.
Uninstalling the eWay Scheduler service ............................................ 32
4 TreadCorp functionality .................................................................... 32
1.
Configure custom 404-handling ........................................................ 32
3
2.
5
Windows 2003 (IIS6) ...................................................................................................... 33
Windows 2008 (IIS7) ...................................................................................................... 34
Configure eWay to use friendly URL ................................................... 37
Trouble shooting .............................................................................. 39
1.
403 - Forbidden: Access is denied ..................................................... 39
2.
404 – Page not found ...................................................................... 39
3.
ARITHABORT error message ............................................................. 40
4.
ISAPI filter Troubleshooting .............................................................. 40
6.
eWay WebDavSecurity ..................................................................... 44
2
1
PLATFORM REQUIREMENTS
1. Software
Server



Windows 2000, 2003 or 2008
MS .Net Framework version 4
Sql Server 2000 SP3, Sql Server 2005 or SqlServer 2008
Client





Compatible with all browsers.
eWay Administration tools can only be run with MS Internet Explorer.
In order to make use of eWay's Office ComAddin, one needs Office 2000 or
upwards.
eWay’s Office ComAddin runs only with the 32-bits version of Office 2010.
In order to make use of eWay's Shell Extension, one needs Windows XP or
upwards.
2. Hardware
Minimum configuration





IIS and Sql Server on the same physical server
CPU (for up to 30 users): minimum 1GHz P3 or equivalent
Memory: 512 MB Ram
Network: 100 Mb
Disk: 7200 RPM ATA or SCSI
Recommended configuration





IIS and Sql Server on the same physical server
CPU: 2 GHz P4/Xeon/AMD Opteron
Memory: 1 GB Ram
Network: 1 Gb LAN
Disk: 10000 RPM SCSI or S-ATA disks. RAID 1, 3 or 5 for redundancy.
Extended configuration



Separate physical servers for IIS and Sql Server.
The disk system should have the highest priority on the Sql Server machine.
Otherwise same as the recommended configuration.
Scalable configuration



Several servers for IIS against one common database server.
One should then setup load balancing between those IIS servers.
Otherwise same as the recommended configuration.
3
2
EWAY
SETUP
1. Copy eway files from the distribution folder
eWay files, i.e. Release.zip, can be downloaded from ftp://demo.eway.no
1. Extract the files locally.
2. Create a folder, e.g. eway5. Copy the extracted eway- and ewaysvc-folders under
the eWay5-folder.
3. Copy the extracted davstore-folder under the eWay5-folder.
Figure 1. An example folder structure for eWay files.
2. The eWay database
Start Sql Service Enterprise Manager(SQL Server Management Studion)
1. Create
a.
b.
c.
New database
Database name, e.g. “eWay51”
Use full-text indexing.
Collation: You may use the server default if this is the collation order you
wish. For Norwegian sites it should be set to Danish_Norwegian_CI_AS.
d. Recovery model: Consider setting the recovery model to “Simple”. 1
e. Set compatibility level to Sql Server 2000 (80).
f. Option / Arithmetic Abort Enabled: set to TRUE
2. Create and schedule a full text catalog named eway_ftc (right-click on Storage/Full
Text Catalogs under your database, and choose New Full-Text Catalog). You may
create a catalog under “Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\FTDATA” and choose this as the location for your full text
catalog:
1
Read more about different recovery models in Sql Server: http://www.sql-serverperformance.com/articles/dba/Database_Recovery_Models_in_SQL_Server_p1.aspx
4
Figure 2.
Full-text catalogue.
3. Run the “ewaymaster_design.sql” script in order to create tables, indexes and so
on.
4. Run the “ewaymaster_data.sql” script in order to insert rows to the tables.
5. Create full text indexes on the text columns of the tables km_messages,
km_message_fields. Remember:
a. To enable "Used In" tab in message editor, full text search must be
enabled and the field "Value" in table "Km_message_fields" must be
indexed.
b. To display list images in the "Used In" tab in message editor, the field
"list_image_url" in table "Km_messages" must be included in the full text
index.
6. Create a job for accumulating tracking information.
a. Choose New / New Job…. While right-clicking on the “Sql Server Agent /
Jobs”
b. Name: e.g. “Update tracking eWay51Database”
c. Create a step with:
i. Any name, e.g. Step 1
ii. Type: T-Sql
iii. Choose your database, i.e. eWay51.
iv. Command: Copy / Paste from “update_tracking.txt”
d. Schedule to run a few times a day.
7. Create a database user (or use an existing one), e.g. “eWay” with dbo-privileges to
the eWay51.
Troubleshooting

If you get an error message from the database saying “INSERT failed because the
following SET options have incorrect settings: ‘ARITHABORT’.
Verfiy that SET options are correct for use with indexed views and/or indexes on
computed columns and/or query notifications and/or xml data type methods.”, in
SqlServer Enterprise Manager (Server Management Studio) set:
" eWay51Database/properties / options / Arithmetic Abort Enabled" to "True".

An out of memory exception might occur when running the ewaymaster_data.sql
script.
A workaround is to insert "GO" statements between the INSERT statements where
5
there are many INSERT statements. For example if there are 10000 INSERTstatements for km_tracking, place GO statements for every 2000 INSERTstatement.

Another workaround is to increase allowed memory usage for the SQL server.
The ewaymaster_design.sql script cannot create full text catalogs. If the fulltext
catalog eway_ftc isn't created then the script will display an error message when
run. Create the fulltext catalog "eway_ftc" before running the script will solve this
problem.
If one wants to give another name to the fulltext catalog one should change the
name in the sql script. Search and replace "eway_ftc" in the script.
3. Configure the eWay IIS site on a Windows 2000 / Windows 2003 server
Start Internet Information Services from the Computer Management Console.
Create a new web-site
1. Choose New / Web Site… from the right-click menu while standing on the “Web
Sites”.
2. Web Site Description: Type a description of the Web site, e.g. “eWaySite”
3. IP Address and Port Settings: Type a host header for the Web site, e.g. Intranet
4. Web Site Home Directory:
a. Enter the path to the eWay5-folder
b. Check “Allow anonymous access to this Web site” if the site is not a single
sign-on site.
5. Web Site Access Permissions: Check “Read” and “Execute”
Add New Application Pool
1. Choose New / Application Pool… from the right-click menu while standing on the
“Application Pools”.
2. Give an ID to the application pool , e.g. “eWay5 pool”
3. Use dafualt settings for new application pool. It seems like using "Network Service"
as identity may prevent having problems in some server environments.
Properties of the web-site
Right-click on the web-site and choose “Properties”.
1. Documents-pane: Add “eway/default.aspx” and “default.aspx” to the “Documents”
of the new site. Move them up in the list.
2. Home Directory:
a. Create an application
b. Execute permissions: Scripts only
c. Application pool: “eWay5 pool”
3. ASP.NET: Set 2.0 as Asp .NET version
4. HTTP Headers:
Set .msg and .oft as MIME Types.
eway and ewaysvc as applications in IIS
Right-click on the eway-folder and choose “Properties”.
5. Create application with the Create-button.
6. Choose “eWay5 pool” as the application pool.
Right-click on the ewaysvc-folder and choose “Properties”.
7. Create application with the Create-button.
8. Choose “eWay5 pool” as the application pool.
6
WebDav
Note: On an Windows 2003 server, WebDAV must be Allowed under the IIS/Web Service
Extensions. Note that this is disabled as default:
Figure 3. WebDAV must be allowed. Otherwise eWay documents will always be ReadOnly.
Dav
Create a virtual folder for the documents. Right-click on the “eWaySite” and choose New /
Virtual Directory…
1. Alias: dav
2. Path: Enter the path to the davstore-folder
3. Choose “Read” and “Write”
WebDAV settings
1. If the davstore folder is under the site root (e.g. a eway5 catalogue that contains the
eWay folder), it should say no read-, write-or execute as web-sharing configuration on IIS
on that folder.
2. The virtual dav folder should be set with read- and write (no execute).
3. At the file system, "everyone" should have full control to the davstore folder.
4. Both "Anonymous Access" and "Integrated Windows Authentication" should be set on
the virtual dav folder. In the case of single sign-on, "Anonymous Access" should be
disabled.
Settings for image store
Similarly the following access should be set for the image store:
1. Read / write as web-sharing configuration on IIS on that folder.
2. At the file system "everyone" should have full control to the imgstore folder.
Spelling check
eWay supports advanced dictionaries for spelling check. We describe specifically
configuration of Open Source dictionary that contains 1.4 million words only for
7
Norwegian! Follow the instructions in the \Install\Telerik Norsk ordliste\OpenSource liste\
Bruke Open Source ordliste i eWays stavekontroll.docx document.
We describe also configuration of MS Office Word dictionary as spelling check tool for
eWay. Remember that this requires that MS Office Word is installed on the server. In this
case, follow the instructions in the \Install\Telerik Norsk ordliste\Word\ Bruke Microsoft
Word ordliste i eWays stavekontroll.docx document.
Which dictionary should be used, should be specified as a system parameter with eWay’s
Additional Confguration tool.
Install eWay ISAPI Filter
1. Installing components
To install the components that the ISAPI filter uses you should run
\Build\Release\Server\Utilities\ISAPI Filter\Setup\SetupISAPIFilter.msi.


If you don't know whether those are already installed or not, you can go to the Control
Panel and choose "Add or Remove Programs". If you see the "eWay ISAPI Filter" there,
it means that they are already installed.
If you are upgrading the ISAPI filter components, you should first remove the "eWay
ISAPI Filter" from the Control Panel and then run the SetupISAPIFilter.msi program to
install the newer version.
2. Configuration of ISAPI filter per eWay site
Run C:\Program Files\eWay\eWay ISAPI Filter\eWayISAPIUtil.exe.
Enter the connection string to your database (you can copy that from your web.config file).
Note that the connection string shall not contain " "!! Enter name of the web server and
"Add":
Figure 4. Running eWayISAPIUtil.exe
Note that you might have several server names for the same server (i.e. a server that is
accessed by http://ewaysite.eway.no can also be accessed as http://ewaysite if you are in
the same domain). If this is the case, you have to repeat this step for each server name:
8
Figure 5. In case there are several server names for the same server…
3. Add the ISAPI filter to your site
Find you eWay site on the IIS. Choose "Properties", "ISAPI filters" and then "Add…".
Give any name to the filter, e.g. eWay ISAPI, and then browse to find the eWayAuth4.dll:
Figure 6. Adding the ISAPI filter to your site
Choose "OK" or "Apply" and close the dialog. When you open the dialog again, you should
have the following picture if the installation is succeeded:
Figure 7. The eWay ISAPI Filter is added
9
4. Configure the eWay IIS site on a Windows 2008 server
Installation
You should install IIS 7 on the Windows 2008 server if this is not already installed. IIS is a
“Role” in Windows 2008:
Figure 8. Install IIS
Create a new web-site
Start Internet Information Services Manager from the Server Manager.
1. Choose ”Add Web Site…”… from the right-click menu while standing on the “Sites”
folder.
10
2. Type a Site name e.g. “eWaySite”
3. An application pool with the same name, i.e. “eWaySite”, will be created
automatically.
4. Physical path: Enter the path to the eWay5-folder
11
5. IP Address and Port Settings: Type a host header for the Web site, e.g. Intranet
6. Restart the site if you see a red X on the site node:
Figure 9. Restart the eWay web-site
Other properties of the web-site
7. Start “Default Document”.
8. Add “eway/default.aspx”. Move “default.aspx” and “eway/default.aspx” up in the
list:
12
Figure 10. Default document
1.
Answer yes to allow the change to take place.
2. Choose the eWay-directory, right-click and choose “Convert to Application”:
Figure 11. Convert to application
3.
4.
5.
6.
Change the Application Pool to the site application pool, i.e. “eWaySite”
Choose the ewaysvc-directory, right-click and choose “Convert to Application”
Change the Application Pool to the site application pool, i.e. “eWaySite”
Choose the main site, and the choose “MIME Types” and add .msg and .oft as
MIME Types. Use “application/” in front of the MIME Type:
13
Figure 12. Add MIME type Outlook .msg files
Settings for Application Pool
7. Check that .Net version 2.0 is set for the application pool:
Figure 13. .Net 2.0 for the application pool
8. In Windows Explorer: Give the “Application Pool Identity”, e.g. Network Service,
Read & Execute priviliges to the eWay5-folder
In Windows2008 R2, the Application Pool Identity is a Managed Service Account.
This means that it exists on the local computer, and that its name is the same as
the application pool name, and that it belongs to the “iis apppool”, see below:
Find the name of the application pool (here eway51WinAut)
14
Rightclick the eway-folder and choose properties,security.
Choose edit.
The choose add. Make sure location is the local computer.
15
Make sure Object Types include “Built-in security principals”
Search for “iis apppool\” followed by the name of the application pool (and check
the number of p’s)
16
Click “Check Names” and you can see whether the name was accepted.
You can now set the permissions
17
Dav
Create a virtual folder for the documents. Right-click on the “eWaySite” and choose Add
Virtual Directory…
1. Alias: dav
2. Path: Enter the path to the davstore-folder
Install the WebDAV Security Modules
This is a description of how to preserve eWay security while using the WebDAV protocol
when eWay is installed on a Windows 2008 Server.
Previously this was accomplished using the ISAPI-filter. The version of IIS that comes with
Windows 2008 use a different architecture, that allows for the use of managed code in the
development of modules that plug into the event pipeline. We have therefore made a
replacement of the old ISAPI-filter in order to handle WebDAV security on Windows 2008
server.
1. Components
The WebDAV Security System consists of two modules that plug into the IIS architecture.
These two modules are:
 WebDavAuthentication module
 WebDavSecurity module
The WebDavSecurity module is the part that takes care of the eWay security. The
WebDavAuthentication module is a replacement for the standard “Anonymous
18
authentication”, as this latter in Windows 2008 does not allow anything but read-only use of
the WebDAV catalog.
2. Installation and activation of WebDAV
In order for WebDAV to work, it needs to be installed. There are separate ways of doing this
for Windows 2008 and Windows 2008 R2.
 In Windows 2008 this is an extra download, which needs to be downloaded from the
Microsoft download site (Microsoft WebDAV 7.5 for IIS 7.0).
 In Windows 2008 R2 this is chosen during installation of the role.
When this is done, you will find the WebDAV icon in the IIS Manager.
Figure 14. WebDav icon in the IIS Manager.
After installing WebDAV, you have to activate it for the web-site in question. This needs to
be done on each web-site that will use WebDAV in order for it to work. If this is not done,
you will not get any error messages, but the documents in the folder will function only by
normal http-download. You activate it by double-clicking, and then choosing “Enable
WebDAV”.
If there is no Authering Rule, it should be added with “Add Authoring Rule”. You basically
need a rule that give everybody full access to everything:
19
Figure 15. Add Authoring Rule
Figure 16. Enabling WebDav.
3. Installation of WebDavSecurity and WebDavAuthentication modules
Necessary preparations
The following commands should be run to prepare the site for eWay WebDAV
Authentication:
20
%windir%\system32\inetsrv\appcmd.exe unlock config /section:windowsAuthentication
%windir%\system32\inetsrv\appcmd.exe unlock config /section:anonymousAuthentication
%windir%\system32\inetsrv\appcmd.exe set config /section:system.webServer/modules runManagedModulesForWebDavRequests:true
Adding WebDavSecurity
To add WebDavSecurity, open the Modules part.
Figure 17. To add WebDavSecurity, open the Modules part.
Then add a managed module by writing the module name, i.e.
Name: eWay WebDavSecurity
Type: eWay.WebDavSecurity.WebDavSecurity
21
Figure 18.
Add a managed module.
Answer “yes” if you get the following warning:
Adding Authentication
If you are not using Single Sign On, you need to install the eWay authentication. Open the
Authentication part.
22
Figure 19.
Open the Authentication part..
Make sure that everything is set to disabled.
Figure 20.
Make sure that everything is set to disabled.
23
Then go back to modules, and add the WebDavAuthentication-module by writing the
module name, i.e:
Name: eWay WebDavAuthentication
Type: eWay.WebDavAuthentication.WebDavAuthentication
Figure 21.
Add the WebDavAuthentication-module.
Answer “yes” if you get the following warning:
5. Office 2007/2010 MIME types
Windows 2003 (IIS6)
IIS6 does not support Office2007 automatically. You may therefore need to add different
Office 2007 formats as MIME types on the IIS. You can do that manually or by editing the
metabase.xml file on the server.
Following MIME types should be added:
a) Adding MIME types manually
1. Open Computer Management. (Right-click My Computer... Manage...)
2. Right-click Internet Information Services (IIS) Management... Properties...
3. Click MIMETypes...
24
4. Click New... and add the following extensions one by one:
Extension
MIMEType
.docm
application/vnd.ms-word.document.macroEnabled.12
.docx
application/vnd.openxmlformats-officedocument.wordprocessingml.document
.dotm
application/vnd.ms-word.template.macroEnabled.12
.dotx
application/vnd.openxmlformats-officedocument.wordprocessingml.template
.potm
application/vnd.ms-powerpoint.template.macroEnabled.12
.potx
application/vnd.openxmlformats-officedocument.presentationml.template
.ppam
application/vnd.ms-powerpoint.addin.macroEnabled.12
.ppsm
application/vnd.ms-powerpoint.slideshow.macroEnabled.12
.ppsx
application/vnd.openxmlformats-officedocument.presentationml.slideshow
.pptm
application/vnd.ms-powerpoint.presentation.macroEnabled.12
.pptx
application/vnd.openxmlformats-officedocument.presentationml.presentation
.xlam
application/vnd.ms-excel.addin.macroEnabled.12
.xlsb
application/vnd.ms-excel.sheet.binary.macroEnabled.12
.xlsm
application/vnd.ms-excel.sheet.macroEnabled.12
.xlsx
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
.xltm
application/vnd.ms-excel.template.macroEnabled.12
.xltx
application/vnd.openxmlformats-officedocument.spreadsheetml.template
5. Restart IIS.
b) Adding MIME types to the metabase.xml
1. Stop the “IIS Admin Service” and “World Wide Publishing Service”.
2. Take backup of your metabase XML file
(C:\WINDOWS\system32\inetsrv\MetaBase.xml)
3. Open the metabase XML file in a text editor.
4. Search for "iismimemap" and append the following to the appropriate node:
.docm,application/vnd.ms-word.document.macroEnabled.12
.docx,application/vnd.openxmlformatsofficedocument.wordprocessingml.document
.dotm,application/vnd.ms-word.template.macroEnabled.12
.dotx,application/vnd.openxmlformats-officedocument.wordprocessingml.template
.potm,application/vnd.ms-powerpoint.template.macroEnabled.12
.potx,application/vnd.openxmlformats-officedocument.presentationml.template
.ppam,application/vnd.ms-powerpoint.addin.macroEnabled.12
.ppsm,application/vnd.ms-powerpoint.slideshow.macroEnabled.12
.ppsx,application/vnd.openxmlformats-officedocument.presentationml.slideshow
.pptm,application/vnd.ms-powerpoint.presentation.macroEnabled.12
.pptx,application/vnd.openxmlformats-officedocument.presentationml.presentation
.xlam,application/vnd.ms-excel.addin.macroEnabled.12
.xlsb,application/vnd.ms-excel.sheet.binary.macroEnabled.12
.xlsm,application/vnd.ms-excel.sheet.macroEnabled.12
.xlsx,application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
.xltm,application/vnd.ms-excel.template.macroEnabled.12
.xltx,application/vnd.openxmlformats-officedocument.spreadsheetml.template
5. Save the changes to the Metabase.xml.
6. Start the “IIS Admin Service” and “World Wide Publishing Service” – and also
services “FTP Publishing” and “HTTP SSL” if these were stopped earlier.
7. Restart IIS.
25
Windows 2008 (IIS7)
IIS7 support office 2007/2010 MIME Types.
6. Hosts
Use the IP address of the server and add the new site to the hosts file of the server. Hosts
file is under the \WINDOWS\system32\drivers\etc folder.
7. File access
Start Windows Explorer.
1. Davstore privileges:
a. Go to the davstore-folder.
b. Right-click and choose “Properties”.
c. Give “Everyone” Modify-privileges.
2. Imgstore privileges:
a. Go to the eway\imgstore-folder.
b. Right-click and choose “Properties”.
c. Give “Everyone” Modify-privileges. (Remember that the same folder in IIS
is still read only).
3. Style sheet editing:
a. Give the Application Pool user / identity Modify-privileges to the
eway\Custom\Design-folder.
8. Index the document store
Index the document store on a Windows 2000 / Windows 2003 server
Indexing service
Start Services from the Computer Management Console.
1. Choose Properties from the right-click menu while standing on the “Indexing
Service”.
2. Start up type: If you want the Indexing Service to start automatically, choose
Automatic.
Create an index catalog
Start Indexing Service from the Computer Management Console.
1. Choose New / Catalog from the right-click menu while standing on the “Indexing
Service”.
a. Name: e.g. “ewaycat”
b. Location: e.g. C:\Inetpub\IXCatalogs\eway
2. Choose New / Directory from the right-click menu while standing on the “ewaycat /
Directories”.
a. Path: Path to the davstore-folder.
b. Alias: dav
Index the document store on a Windows 2008 server
Indexing service
By default, the Indexing Service is not installed on a Windows Server 2008-based
computer. To install the Indexing Service on a Windows Server 2008-based computer, you
must first use Server Manager to add the File Services role to the server. Then, you must
add the Indexing Service role service that is available under the Windows Server 2003 File
Services role2.
2
See here for more on this subject: http://support.microsoft.com/kb/954822/en-gb
26
Figure 22.
Selecting the “Indexing service” role.
Create an index catalog
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Administrative Tools, and then double-click Computer
Management.
3. In the console tree, double-click Services and Applications, and then doubleclick Indexing Service.
4. Right-click Indexing Service, point to New, and then click Catalog:
Figure 23.
Creating a new indexing catalog.
5. In the Name box, type a name for your new catalog, e.g. ewaycat.
27
6. Click Browse, click the folder in which you want your new catalog located, and
then click OK twice:
Figure 24.
Creating a new indexing catalog.
7. When you receive the "Catalog will remain off-line until Indexing Service is
restarted" message, click OK.
The new catalog is created and is listed under Indexing Service in the console tree. l3
8. Double click on the Indexing Service folder.
9. Choose the catalog you created
10. Right-click on the Directories-folder, and choose New Directory
11.
Figure 25.
Creating a new directory for the indexing catalog.
12. Enter the path to the davstore-folder with Alias, “dav”:
3
For more information about how to create and configure a catalog for indexing, click the
following article number to view the article in the Microsoft Knowledge Base: 308202
(http://support.microsoft.com/kb/308202/ ) How to create and configure a catalog for indexing
28
Figure 26.
Creating a new directory for the indexing catalog.
13. Restart the Indexing Service.
9. Do changes in the Web.config
(1. web.config under both eway and ewaysvc, the rest only for web.config under eway)
1. Modify the connection string with your own server name, database name, user
name and password as e.g.:
<add key="connectionstring" value="server=ewaytest;database=eWay51;user
id=eway;password=eway"/>
2. Modify the path to the default design folder if necessary:
<add key="designfolder" value="eway5"/>
3. Modify the page title:
<add key="pagetitle" value="Welcome to Track AS"/>
4. Modify the path to eWay’s Web Service as e.g.:
<add key="ewayapp.eWaySvcRef.eWaySvc"
value="http://ewaySite/ewaysvc/ewaysvc.asmx"/>
5. Modify the name of the index catalog if necessary:
<add key="ixcatalog" value="ewaycat"/>
29
3
EWAY
SCHEDULER SETUP
1. Installation
\Build\Release\Server\Utilities\eWayScheduler\Install Service.bat installs the eWay
Scheduler Service (i.e. ewaySchedSvc.exe) as an NT Service.
Run "Install Service.bat" by double clicking on the "Install Service.bat" file in a Windows
Explorer window. You will then get the following screen. Be sure that it says "successfully"
- as marked with a white arrow in the figure below.
Figure 27. Running the Installation.bat program
You should then press any key to close the command window.
2. Configuration
Run the \Build\Release\Server\Utilities\eWayScheduler\ eWayShedCfg.Exe to configure the
eWay Scheduler Service.
3. Add an instance
30
Figure 28. No scheduler instances are configured (yet).
Click on "Add…" to add a new instance.
Figure 29. Values for a Scheduler instance .
Click on "Test" to see that the information is valid.
Figure 30. "Test" succeeds.
Click OK and return to the configuration dialog.
31
Figure 31. An instance is added.
4. Adding several instances
If you are running Replication, you have to repeat the steps described in 3 for all the
servers that are involved in Replication.
Endre Polling interval med å klikke File/Set Polling Interval i bildet på Steg 4, eller la det
være som default, 300 seconds.
Figure 32. Polling interval.
5. Start the eWay Scheduler service
Remember to restart the "eWayScheduler Service" in the Services Snap-in.
6. Uninstalling the eWay Scheduler service
\Build\Release\Server\Utilities\eWayScheduler\UninstallService.bat uninstalls the eWay
Scheduler Service (i.e. ewaySchedSvc.exe).
4
TREADCORP FUNCTIONALITY
In order to get the TreadCorp portal to function, it is necessary to perform the following
steps.
1. Configure custom 404-handling
The TreadCorp Portal uses friendly URL functionality. This requires that the IIS server is
set up to use custom 404 handling.
32
Windows 2003 (IIS6)
In IIS Manager, right-click the site and chose “Properties”
Choose “Custom Errors”
Choose the HTTP error 404 and “Edit”
Change “Message type” to URL and type in /eway/library/FriendlyUrlHandler.ashx
33
Click “OK”
Click “OK” again.
Windows 2008 (IIS7)
1.1.1.
Open “Error Pages”
34
1.1.2.
Double Click the 404 page
1.1.3. Type in the name of the custom handler
The custom handler being used is found at /eway/library/FriendlyUrlHandler.ashx. Type
this into the URL-box of the “Execute a URL on this site” option and click OK.
35
36
2. Configure eWay to use friendly URL
Log on to eWay, and choose the administration portal:
37
Click on Portal Configuration and choose the TreadCorp portal.
Type in the Host header for your site (as a comma separated list if there are several host
headers).
38
(If you are testing this out directly on the Windows 2008 server: In order to make friendly
URL work on the server, you need to choose “Edit Feature Settings”,
and choose the “Custom error pages” choice)
If you want to configure TreadCorp further, or if you are experiencing problems with the
TreadCorp-portal of the eWay Master, please refer to the document
“Konfigurasjonsveiledning på elementer som inngår i TreadCorp-portalen.doc”, especially
the chapter called “Brukervennlige lenker (korte URL’er)”.
5
TROUBLE SHOOTING
1. 403 - Forbidden: Access is denied
http://ewaysitename/eway works fine, but you receive this error when you just use
http://ewaysitename. Then check the application pools you’ve set for the web-site and for
the eWay application under the web-site. These two should be the same; the
http://ewaysitename call does not work if the application pools on the root and on the
eway-folder are different.
2. 404 – Page not found
1. One solution for solving this problem may be reinstalling the asp.Net 2.0 with
parameters –i and –enable, like for example:
C:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –i –enable
2. Another solution may be setting .Net to be “Allowed” at IIS:
39
3. ARITHABORT error message
If you receive ARITHABORT error message from the Sql Server, try running this in the
Query Analyzer:
Alter database <database name> set ARITHABORT on
4. ISAPI filter Troubleshooting
1. If you make any reconfiguration to the ISAPI filter, you should remember to restart the
IIS in order to empty the IIS cache!
2. If the ISAPI filter does not work as expected, you should check whether the ISAPI
components are up-to-date.
3. If the green arrow does not appear, try to start your eWay from the browser. The
ISAPI filter does not get activated unless a connection is established to the site.
40
Figure 33. ISAPI Filter components
4. If the ISAPI filter does not work as expected, you should also check whether the ISAPI
components point to the correct folder (the registry settings regarding the Codebase).
In order to do that, you should first find the ewayfilter.dll in the Registry Editor:
Figure 34. Finding the ewayfilter.dll with the Registry Editor
Figure 35. Checking the CodeBase for the filter
41
If the CodeBase does not point to the correct folder, you should:
1. Unregister the eway filter with regasm.exe
2. Register it with the correct path for the components, i.e. codebase
Figure 36. Registering the eWay filter with the correct path for CodeBase
5. Problem : ISAPI filter has a ”red arrow” after it is configured in IIS for an eWay 5.1
site
Check for these related error-messages in the event-viewer.
Errors in the Application error records:
42
Errors in the System error records:
Then see if a version of Microsoft Visual 2008 C++ redistributable is installed.
This can be done in Add/Remove programs.
If Microsoft Visual 2008 C++ redistributable is not required for other programs then
uninstall this version and then uninstall and reinstall the ISAPI filter.
43
6. eWay WebDavSecurity
If you receive an error saying:
Could not load type 'eWay.WebDavSecurity.
If you upgrade an old site, remember that you need to make a new bin-catalog at the root,
that contains the files connected to the new WebDavSecurity-module. All three bincatalogs (site/bin, site/eway/bin, site/ewaysvc/bin) must contain the files connected with
the WebDavSecurity-module
44