Codeless Server IIS Installation

(1)

PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Tue, 12 Aug 2014 11:15:43 CEST

Codeless Server IIS

Installation

(2)

Articles

1. Revisions

₁ 1. Revisions 1

2. Prerequisites

₂ 2. Prerequisites 2

3. Transfer Codeless Files

₄

3. Transfer Codeless Files 4

4. Copy files to IIS locations

₅

4. Copy files to IIS locations 5

5. Configure IIS locations

₆

5. Configure IIS locations 6

6. Create Application in IIS

₉

6. Create Application in IIS 9

6.1 Codeless Application Pools 9

6.2 Convert IIS folders to applications 13

6.3 Repeat steps for Load Balancing 19

6.4 Recompile MSL 19

7. Test with stand-alone client

₂₁

7. Test with stand-alone client 21

8. Configure Click Once Client

₂₅

8. Configure Click Once Client 25

9. Create or Update Environment Webpage

₂₆

9. Create or Update Environment Webpage 26

References

Article Sources and Contributors 27

(3)

1

1. Revisions

Revisions:

Version Date Author Modification

1.00 04/06/2010 Wouter van de Ven

Initial document

1.01 22/06/2010 Radu Radulescu

Added more information to prerequisites, plug-in registering and other things that need to be tested.

Updated the default Codeless Installation path.

Registering a Codeless plug-in. Updated files location conventions. Configuration options for metadata load.Application pool shutdown.Use multiple sets option – to avoid generation of broken sets in the DB.Rename the environment in the catalog database.

1.04 09/11/2010 Alexandru Sarbusca

ISAPI and CGI Restrictions configuration

1.05 25/02/2011 Alexandru Sarbusca

Changed document to be compatible with Codeless 3.0.

3.1.2 06/06/2013 Alexandru Sarbusca

Added information about setting up the Server Monitor application

3.2.0.0 15/08/2013 Alexandru Sarbusca

(4)

2

2. Prerequisites

Prerequisites

Database

The following database must exist for your environment: <PacakgeName><EnvironmentType>

Domain user

A domain user must exist that is configured as the default application pool identity and that has read and write access to this database or a custom user can be used directly.

Internally this is the user: impulsit\CodelessService

Windows components

The following Windows Components must be installed on the server: - IIS – including IIS 6 Metabase and IIS 6 Configuration Compatibility

- ASP .Net - WCF

IIS configuration

Add the appropriate MIME Types, e.g. (.msp/.msu)

Add the appropriate Handler Mappings, e.g. (.svc) – see http://msdn.microsoft.com/en-us/library/ms752252(VS. 90).aspx

Windows Script Control must be installed on the server. It can be downloaded from this address: http://impiis/ CodelessProducts/Windows%20Script%20Control/

(5)

2. Prerequisites 3

For IIS 7.5, the AppWarmupModule must be installed – see http://www. iis.net/ downloads/microsoft/

application-initialization After the installation is completed, a reboot of the machine is needed.

This is needed for the Server Monitor application pool that has to automatically initialize the application, without a request being made to it. Application Initialization support:

- IIS 8 – included

- IIS 7.5 – must be installed as described above - IIS 7 – not supported

(6)

4

3. Transfer Codeless Files

Transfer Codeless Files

Installation default folders

A default location for all Codeless files that are transferred to a server must exist. This will be

D:\Codeless and referred from now on as %CIP% (Codeless Installation Path)

There should be no files directly in the %CIP% folder. Sub folders:

Location role Path

Codeless Client standalone Codeless Client\Version x.x

Codeless logs Logs\

Server Files ServerFiles\<PackageName><EnvironmentType>\ Releases (made with the Realease Maker) Server Files\<PackageName><EnvironmentType>\Releases Server Output (folder where output files a created, for example for interfaces) ServerOutput\

Server Input (folder where input files must be dropped) ServerInput\

Installation kits Install\

Temporary files (for example zip files that have been transferred) Temp\

Download Codeless

Download the correct version of the Codeless Server and both the standalone and ClickOnce Codeless Client. Internally the version can be found on the current location:

http://impiis/CodelessProducts/ Extract the files in the following folder:

%CIP%\Install

Copy the standalone Codeless client to:

(7)

5

4. Copy files to IIS locations

Copy files to IIS locations

When using Load Balancing it is useful to have a mechanism to sync files to all IIS machines so that changes to file do not have to be made on all machines.

Internally this has been setup. All changes under the wwwroot folders on impiis1 are sync with the wwwroot folder of impiis2. This is done every 5 minutes, so it may take max 5 minutes for changes on one server to be seen on both. The current installation steps can be executed on impiis1, impiis2 will be updated automatically.

Server

Create folder under IIS location:

c:\inetpub\wwwroot\<PackageName><EnvrironmentType>CodelessServices

Copy files from under the server version you want to install (for example Codeless.Server.Web - v3.2.0.0) to the IIS location.

Check for plug-ins required by the package/installation and copy them too. Check for other files or settings that may be needed by the plug-ins.

Client

Create folder under IIS location:

c:\inetpub\wwwroot\<PackageName><EnvrironmentType>CodelessClient

Copy files from folder under the client version you want to install (for example CodelessClientClickOnce - v3.2.0.0) to the IIS location.

Log

The Log4Net Dashboard application is integrated as a subfolder of the Codeless Server, so you should find it at the following location:

c:\inetpub\wwwroot\<PackageName><EnvrironmentType>CodelessServices\Log

Server Monitor

The Codeless Server Monitor application is integrated as a subfolder of the Codeless Server and it is located at the following location:

(8)

6

5. Configure IIS locations

Configure IIS locations

Server

Edit web.config file that should be located at:

c:\inetpub\wwwroot\<MyPackage><Envrironment>CodelessServices\web.config Update the following values:

<connectionstring value="Data Source=<MyDBServer>;

initial Catalog==<PackageName><EnvrironmentType>; Application Name=<PackageName><EnvrironmentType>; Integrated Security=SSPI;"/> </appender> </log4net> <appSettings>

</appSettings>

If you specify TrustedConnection = “1” you don’t have to supply a User ID and Password. Instead, the account under which the application pool runs will be used for accessing the database. In both cases, either the application pool user or the user specified in the configuration file must be set as Database Owner for the target database. You can set this using SQL Management Studio, in the Security section for your server:

(9)

Log

c:\inetpub\wwwroot\<MyPackage><Envrironment>CodelessServices\Log\web.config Update the following values:

<connectionstring value="Data Source=<MyDBServer>; initial Catalog=<PackageName><EnvrironmentType>; Application Name=L4NDash; Integrated Security=SSPI;"/> </providersettings> </datasource> </l4ndash>

As with the Server configuration, you can either use Integrated Security or specify a User ID and Password for connecting to the database and reading the logs.

(10)

Server Monitor

c:\inetpub\wwwroot\<MyPackage><Envrironment>CodelessServices\ServerMonitor\Web.config Update the following values:

<add key="CodelessServerUrl" value="http://<MyIISServer>/<MyPackage><Envrironment>CodelessServices/"/> </appSettings>

(11)

9

6. Create Application in IIS

The IIS folder must now be registered in IIS. Before this can be done, a new application pool must be created.

6.1 Codeless Application Pools

Codeless Application Pools

Create main Application Pool

Application pools must be created on all IIS server is load balancing is being used. In IIS, go to Application pools and select Add Application Pool option. Enter the following name:

<PackageName><EnvironmentType>

Configure main Application Pool

The following settings must be changed for the application pool: - Managed Pipeline Mode - Classic

- User for the application pool (if a user has not been configured as the default application pool identity) - Idle Time-out = 0 – so that the application pool is not shutdown because of inactivity

- Load User Profile = True – access to server printers’ configurations is available only if this is set to true

- Recycling Regular time intervals = 0 – prevent automatic recycling of the application pool (especially important if all metadata is loaded)

(12)

Configure Server Monitor Application Pool

The following settings must be changed for the application pool: - Managed Pipeline Mode = Integrated

- Start Mode = AlwaysRunning (IIS 8.0)

- User for the application pool (if a user has not been configured as the default application pool identity) - Idle Time-out = 0 – so that the application pool is not shut down because of inactivity

- Recycling Regular Time interval (minutes) = 5 – restarts the Server Monitor application every 5 minutes so that certain commands are performed regularly

(13)

Note: In IIS 7.5, the Start Mode setting is not present in the application pool’s general configuration panel, but instead it can be found in the server’s configuration editor; follow the next steps in order to get to and edit it:

- Select the IIS server and go to Management > Configuration Editor - Section: system.applicationHost/applicationPools

- Open the Collection

(14)

(15)

6.2 Convert IIS folders to applications

Convert IIS folders to applications

Codeless Services

Under 'Default Web Site' select the server folder:

'<PackageName><EnvironementType>CodelessServices'

Right click to open context menu and select "Convert to Application".

(16)

(17)

Log

Repeat the 6.2.1 steps for the Log subfolder:

(18)

Server Monitor

Repeat the 6.2.1 steps for the ServerMonitor subfolder:

'<PackageName><EnvironemenType>CodelessServices\ServerMonitor' with the following additions:

- Use the ServerMonitor application pool and tick the Enable Preload checkbox

(19)

Note: In IIS 7.5, the Preload Enabled setting is not present in the application’s advanced settings panel, but instead it can be found in the server’s configuration editor; follow the next steps in order to get to and edit it:

- Select the IIS server and go to Management > Configuration Editor - Section: system.applicationHost/sites

- Open the Collection

(20)

- Select the Server Monitor application and go to its’ Properties - Set preloadEnabled to True

(21)

6.3 Repeat steps for Load Balancing 19

6.3 Repeat steps for Load Balancing

Step Create Application in IIS and Convert IIS folders to applications must be repeated for each IIS machine that is part of a load balancing cluster.

6.4 Recompile MSL

After each Server installation, the MSL must be recompiled. This step is very important for assuring the MSLs will be executed properly.

Open IIS and recycle the application pool for the Server. Then open the Server Files location, find the MSL (or

MSL_sql) folder and delete it.

(22)

6.4 Recompile MSL 20

This operation might take a while, depending on the size of the environment. You can monitor the MSL folder and see when the number of files generated stops increasing.

(23)

21

7. Test with stand-alone client

Test with stand-alone client

Test Connection and Configuration

Use the stand alone client to test connection the server. Locate the correct version of the client (impiis1: %CIP%\Codeless Client). Make sure there is no existing configuration. This is done by deleting Configuration.xml if client folder (if it exists).

Then start the client and the following screen appears.

Press Add to create a new configuration. Enter the following: <PackageName><EnviromentType>

Check the setting Use Codeless via Webservices and enter the Codeless Server Webservices location: http://<iisServer>/<PackageName><EnvironmentType>CodelessServices/ASPortalWebWCF.svc

(24)

7. Test with stand-alone client 22 Make sure that the “Use Multiple Sets” option is checked.

Important: When using load balancing do not enter the iisServer name of a single server, but use the name of the load balancing cluster. Internally this is 'impiis'.

Press Save and then Open and test if the client works normally.

If the package name does not contain the environment type, you must edit it in the Catalog databas -> table T001InstallatieCodes -> column InstallatieCode. It must be set to

<PackageName><EnvironmentType>:

If it is correct, it will be shown in the logon screen of the Codeless Client:

(25)

7. Test with stand-alone client 23 In the client folder a file Configuration.xml has been created. This file can be renamed to Configuration.xml.deploy and can be used during the creation of the click once location in the following chapter.

Register Plug-ins

All plug-ins that are used by a specific model must be placed in the bin folder of the Codeless Server. Register the plug-ins that have been transferred (if any) in function 3266:

(26)

(27)

25

8. Configure Click Once Client

(28)

26

9. Create or Update Environment Webpage

There should be an environment webpage for your package, if this is the first environment for a package a webpage must be created.

If this is an added environment for a package, the environment webpage should be updated. The page should be located at.

c:\inetpub\wwwroot\<PackageName>

(29)

Article Sources and Contributors 27

Article Sources and Contributors

1. Revisions Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2576 Contributors: AnaTurcan

2. Prerequisites Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2579 Contributors: AnaTurcan

3. Transfer Codeless Files Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2580 Contributors: AnaTurcan

4. Copy files to IIS locations Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2582 Contributors: AnaTurcan

5. Configure IIS locations Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2584 Contributors: AnaTurcan

6. Create Application in IIS Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2588 Contributors: AnaTurcan

6.1 Codeless Application Pools Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2591 Contributors: AnaTurcan

6.2 Convert IIS folders to applications Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2593 Contributors: AnaTurcan

6.3 Repeat steps for Load Balancing Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2594 Contributors: AnaTurcan

6.4 Recompile MSL Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2596 Contributors: AnaTurcan

7. Test with stand-alone client Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2602 Contributors: AnaTurcan

8. Configure Click Once Client Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?oldid=2603 Contributors: AnaTurcan

(30)

Image Sources, Licenses and Contributors 28

Image Sources, Licenses and Contributors

File:Iis install 1.png Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?title=File:Iis_install_1.png License: unknown Contributors: AnaTurcan

File:Iis install_13.png Source: http://hosting1.codeless.com/CodelessDevelopmentWiki/index.php?title=File:Iis_install_13.png License: unknown Contributors: AnaTurcan

Codeless Server IIS Installation