Deployment Manual YasperWE - Server part

abashedwhimsicalΛογισμικό & κατασκευή λογ/κού

2 Νοε 2013 (πριν από 3 χρόνια και 11 μήνες)

78 εμφανίσεις

11/02/2013

Deployment Manual

YasperWE
-

Server part



11/02/2013


about


this document


Author

Ivo Raedts

Version

1
.3
.
2

Subject

YasperWE server
installation

Title

Deployment Manual

Last
u
p
date

Feb 21
, 2006

Last u
pdate by

Reinier Post


Contents of this document
:

Contents of this document:

................................
................................
................................
.

2

YasperWE server installation
prerequisites

................................
................................
........

3

YasperWE server installation items

................................
................................
....................

3

Installing and configuring IIS

................................
................................
.............................

4

Installing IIS
................................
................................
................................
....................

4

Allowing public access to your webpages in IIS

................................
............................

7

Configuring the use of ASP.NET

................................
................................
...................

9

Installing the YasperWE web service

................................
................................
...............

11

Installing the YasperWE database

................................
................................
....................

14

Testing the installation

................................
................................
................................
......

14



11/02/2013


YasperWE server

installation prerequisites



The following software must be present and functional before the YasperWE server
software can be installed:



As the database backend: MySQL 4.1
(MySQL 5.0 does *not* work)

(a free
download from mysql.com)



For convenient database configuration:
MySQL Administrator 1.0

(a free
download from mysql.com)



To support the YasperWE
server
software
:

o

IIS 5.0
, 5.1

or 6.0

(a Windows component; it is on the Wi
ndows
distribution CD)

o

.
NET Framework 1.1 runtime
, with SP1 (free downloads from
Microsoft.com)

o

MySQL ODBC 3.51 Driver

(a free download from mysql.com)

o

MS
WSE 2.0 SP3

(a free download from Microsoft.com)


Other

versions may work, but have not been tested,
except MySQL 5.0
, which is
known not to work. Note that
he MySQL server can b
e installed on a different host.


YasperWE server installation items


The following components
must

be installed:


1.

the
YasperWE web service
software

2.

the initial
YasperWE database

content


11/02/2013

Installing
and configuring IIS


Installing IIS


Internet Information Services (IIS) is a webserver.

It is a component of the Microsoft Windows operating system and available on the
Windows installation CD.


To install IIS, select Start
-
>Settings
-
>Control Panel
-
>Add or Remove Programs,
then Add/Remove Windows Components:





11/02/2013

Be sure to check Internet Information Services (IIS). Under Details, the Internet
Information Services Snap
-
In must be selected.

Have your Windows installation CD handy.


O
nce IIS is installed, administration can be performed with the “snap
-
in” mentioned.
One way to open is through

Start
-
>Settings
-
>Control Panel
-
>Administrative Tools
-
>Internet Information
Services.





You probably want to serve webpages without user authe
ntication. Right
-
click on
Web Sites

and select
Properties
, then


11/02/2013



11/02/2013


under Directory Security, click Edit …
, then enable Anonymous access and Integrated
Windows authentication.


Allowing public access to your webpages in IIS


The listed user has been cre
ated by the IIS installation; this user must have read
permissions on your website’s files.

There will be a default website (in the example above, it has been renamed to
Reinier’s testing webserver
); right
-
click on it and select
Properties
, then click on
H
ome Directory
:


11/02/2013





11/02/2013

On the directory listed in
Local Path:
, the user mentioned before must be given read
and execute access:


find it, right
-
click on it, and under Security, enable read and execute access for that
user.




Test the results by feeding
http://localhost/

to a web browser and seeing that it
returns a page.



Configuring the use of ASP.NET


The .NET Framework 1.1 installation installs ASP.NET support on your computer.
To
configure IIS to use it,
go to the d
irectory in which you have installed the .NET
Framework, which is by default



C:
\
WINDOWS
\
Microsoft.NET
\
Framework
\
v1.1.4322
\


and execute the command



aspnet_regiis.exe

i


11/02/2013

For details, see Microsoft KB article
555132

at



http://support.microsoft.com/default.aspx?scid=kb;en
-
us;555132


11/02/2013

Installing the YasperWE web service




Optional Step

If you want to have control about the location where the files are stored on the
disk, y
ou can create a virtual directory called “YasperWE”.

Start

Administrative Tools

Internet Information Services

Browse to “Default Website” (or the current active one).

Right
-
Click

New

Virtual Directory

Next

enter “YasperWE”

Next

Browse to your desired
locat
ion

Next

Next

Finished.

This is what it looks like in the IIS configuration tool when the virtual directory
has been created; also is the properties screen (rightclick on
YasperWE
, select
Properties)




1.

Install the files

Open “ServerSideSetup.msi”

Next

Ne
xt

Next

Close.


With the optional step of creating a virtual directory, after the first Next the screen
looks roughly as follows:

11/02/2013




2.

Configure the web service


This amounts to editing an XML file.
Browse to the directory where YasperWE is
stored.

(If yo
u install into a virtual directory, this directory is a property of the
virtual directory, as shown in the previous screenshot.)


Open
W
eb.config

with an editor, e.g., Notepad or WordPad.

Scroll down and you
will see:


<
appSettings
>

<
add

key
="MySQLConnect
ionString"

value
="DRIVER={MySQL ODBC 3.51
Driver};

Server=
localhost
;

Database=
ywe
;

UID=YasperWE;

PASSWORD=yas;

OPTION=3"/>

<
add

key
="BaseURL"

value
="D:
\
Projects
\
InfopathYasper
\
ServerFiles
\
"/>

</
appSettings
>


2
parameters can be modified:




MySQLConnectionSt
ring
-

The string to the MySQL database.

o

Server
-

defines the server name from the database server.

If

the MySQL
server is on a different

computer,

replace

localhost

with its Internet
(DNS) name or IP address
.

o

Port


defines the TCP/IP port number (this c
an be omitted, in which case
the default number
3306

is used)

11/02/2013

o

Database


defines the name of the database instance.

Set this to
yasperwedb
!

o

UID


defines the name of the database user that is used by this web
service.

o

PASSWORD


defines the password of th
e database user.


The Database,
UID and Password
settings
must not be changed!




BaseURL


The directory where the files belonging to the Project Types
and t
he
Project Instances will be stored on the server.

If YasperWE is installed in a
virtual directory
it is convenient, but not necessary, to define this directory to be
a subdirectory of the virtual directory.

Don’t forget to create this directory on
disk.

11/02/2013

Installing the YasperWE database


Open MySQL Administrator.


Select
Restore

from the left
-
menu.

Se
t the file to
restore to
PlainYasperWE.sql
, which

can b
e found on the YasperWE
website.

Click
Start Restore
.


The (empty)
database tables are now present as a database (“catalog”) with the
name of
yasperwedb
.


Now make
sure the user specified in the
w
eb.co
nfig

MySQL query string (see above)
can access this database:


Select
User Administration
from the left menu.

Click on
New User
.

Enter
the correct username (default:
YasperWE
) at

MySQL User
.

Enter
the correct password (default:
yas
) at
Password

and at
Conf
irm Password
.

Click on
A
pply C
hanges
.


Select
YasperWE

from
User Accounts
.

Click on the tab page
Schema Privileges
.

Select
yasperwedb

from
Schemata
.

Click on the
<
<

button in order to assign all privileges.

Click on
Apply Changes
.




Testing the installat
ion


There is no specific software for testing the installation.

The recommended procedure is to simply verify with the client
-
side

tool

Admin
Project
Control

tool that a project can be uploaded successfully.

If that doesn’t work,
the web services should
at least respond; this can be tested by feeding the URLs that
appear in the
AdminProjectControl.config

file into a regular web browser.


Bear in mind that these URLs can be configured in the client configuration files,

AdminProjectControl.exe.config
and
Cl
ientTaskControl.exe.config
, in your
clien
t installation directory

(on a default installation,

C:
\
Program Files
\
ASPT
\
YasperWEClients
).


Once everything configured here is set up correctly, the YasperWE server application
will log what it is doing into the
l
og

table of the
yasperwe

database. You can use a
tool like the MySQL Query Browser to view this log, for instance, with the query



SELECT * FROM log ORDER BY logid DESC