Codeless Server IIS Installation

Transcription

1 Codeless Server IIS Installation PDF generated using the open source mwlib toolkit. See for more information. PDF generated at: Tue, 12 Aug :15:43 CEST

2 Contents Articles 1. Revisions 1 1. Revisions 1 2. Prerequisites 2 2. Prerequisites 2 3. Transfer Codeless Files 4 3. Transfer Codeless Files 4 4. Copy files to IIS locations 5 4. Copy files to IIS locations 5 5. Configure IIS locations 6 5. Configure IIS locations 6 6. Create Application in IIS 9 6. Create Application in IIS Codeless Application Pools Convert IIS folders to applications Repeat steps for Load Balancing Recompile MSL Test with stand-alone client Test with stand-alone client Configure Click Once Client Configure Click Once Client Create or Update Environment Webpage Create or Update Environment Webpage 26 References Article Sources and Contributors 27 Image Sources, Licenses and Contributors 28

3 1 1. Revisions 1. Revisions Revisions: Version Date Author Modification /06/2010 Wouter van de Ven /06/2010 Radu Radulescu /06/2010 Radu Radulescu /07/2010 Radu Radulescu /11/2010 Alexandru Sarbusca /02/2011 Alexandru Sarbusca /06/2013 Alexandru Sarbusca /08/2013 Alexandru Sarbusca Initial document 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. ISAPI and CGI Restrictions configuration Changed document to be compatible with Codeless 3.0. Added information about setting up the Server Monitor application Updated version to

4 2 2. Prerequisites 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 / 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: / impiis/ CodelessProducts/ Windows%20Script%20Control/ Check the ISAPI and CGI Restrictions in IIS Manager to be set on Allowed :

5 2. Prerequisites 3 For IIS 7.5, the AppWarmupModule must be installed see / 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 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 logs Server Files Releases (made with the Realease Maker) Server Output (folder where output files a created, for example for interfaces) Server Input (folder where input files must be dropped) Installation kits Temporary files (for example zip files that have been transferred) Codeless Client\Version x.x Logs\ ServerFiles\<PackageName><EnvironmentType>\ Server Files\<PackageName><EnvironmentType>\Releases ServerOutput\ ServerInput\ Install\ 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: / impiis/ CodelessProducts/ Extract the files in the following folder: %CIP%\Install Copy the standalone Codeless client to: %CIP%\Codeless Client

7 5 4. Copy files to IIS locations 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 - v ) 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 - v ) 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: c:\inetpub\wwwroot\<packagename><envrironmenttype>codelessservices\servermonitor

8 6 5. Configure IIS locations 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: <log4net> <appender> <connectionstring value="data Source=<MyDBServer>; initial Catalog==<PackageName><EnvrironmentType>; Application Name=<PackageName><EnvrironmentType>; Integrated Security=SSPI;"/> </appender> </log4net> <appsettings> <add key="servername" value="<mydbserver>" /> <add key="databasename" value="<packagename><envrironmenttype>" /> <add key="trustedconnection" value="0" /> <add key="userid" value="dotnet" /> <add key="password" value="d0tn3t" /> <add key="loadallmetadata" value="0"/> </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 5. Configure IIS locations 7 Log c:\inetpub\wwwroot\<mypackage><envrironment>codelessservices\log\web.config Update the following values: <l4ndash> <datasource> <providersettings> <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 5. Configure IIS locations 8 Server Monitor c:\inetpub\wwwroot\<mypackage><envrironment>codelessservices\servermonitor\web.config Update the following values: <appsettings> <add key="codelessserverurl" value=" </appsettings> Also, configure the logger same as in the server s Web.config.

11 9 6. Create Application in IIS 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) - Enable 32-Bit applications = True

12 6.1 Codeless Application Pools 10 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 - Enable 32-Bit applications = True

13 6.1 Codeless Application Pools 11 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 - Select the desired application pool and scroll down to the startmode property and set it to AlwaysRunning

14 6.1 Codeless Application Pools 12 - Click Apply

15 6.2 Convert IIS folders to applications 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". Then in the Add Application dialog press Select and chose the newly created application pool. Then press OK.

16 6.2 Convert IIS folders to applications 14

17 6.2 Convert IIS folders to applications 15 Log Repeat the steps for the Log subfolder: '<PackageName><EnvironemenType>CodelessServices\Log'

18 6.2 Convert IIS folders to applications 16 Server Monitor Repeat the steps for the ServerMonitor subfolder: '<PackageName><EnvironemenType>CodelessServices\ServerMonitor' with the following additions: - Use the ServerMonitor application pool and tick the Enable Preload checkbox - Go to application s Advanced Settings and make sure that Preload Enabled is set to True (IIS 8.0)

19 6.2 Convert IIS folders to applications 17 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 - Select the Default Web Site, go to properties and open the Collection

20 6.2 Convert IIS folders to applications 18 - Select the Server Monitor application and go to its Properties - Set preloadenabled to True - Click Apply

21 6.3 Repeat steps for Load Balancing 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. Go to the Server Admin page -> Class Information section and press the Compile All MSL button.

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 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:

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: Check if the System Menu is working correctly.

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: Register all plug-in methods in function 3267:

26 7. Test with stand-alone client 24

27 25 8. Configure Click Once Client 8. Configure Click Once Client Follow instruction from the following document: Codeless.ClickOnceDeployment.Moving.docx

28 26 9. Create or Update Environment Webpage 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> Edit the file index.html using a text editor (do not use a WYSIWYG editor like Word or Frontpage).

29 Article Sources and Contributors 27 Article Sources and Contributors 1. Revisions Source: Contributors: AnaTurcan 2. Prerequisites Source: Contributors: AnaTurcan 3. Transfer Codeless Files Source: Contributors: AnaTurcan 4. Copy files to IIS locations Source: Contributors: AnaTurcan 5. Configure IIS locations Source: Contributors: AnaTurcan 6. Create Application in IIS Source: Contributors: AnaTurcan 6.1 Codeless Application Pools Source: Contributors: AnaTurcan 6.2 Convert IIS folders to applications Source: Contributors: AnaTurcan 6.3 Repeat steps for Load Balancing Source: Contributors: AnaTurcan 6.4 Recompile MSL Source: Contributors: AnaTurcan 7. Test with stand-alone client Source: Contributors: AnaTurcan 8. Configure Click Once Client Source: Contributors: AnaTurcan 9. Create or Update Environment Webpage Source: Contributors: AnaTurcan

30 Image Sources, Licenses and Contributors 28 Image Sources, Licenses and Contributors File:Iis install 1.png Source: License: unknown Contributors: AnaTurcan File:Iis install 2.png Source: License: unknown Contributors: AnaTurcan File:Iis install 3.png Source: License: unknown Contributors: AnaTurcan File:Iis install 4.png Source: License: unknown Contributors: AnaTurcan File:Iis install 5.png Source: License: unknown Contributors: AnaTurcan File:Iis install 6.png Source: License: unknown Contributors: AnaTurcan File:Iis install 7.png Source: License: unknown Contributors: AnaTurcan File:Iis install 8.png Source: License: unknown Contributors: AnaTurcan File:Iis install 9.png Source: License: unknown Contributors: AnaTurcan File:Iis install 10.png Source: License: unknown Contributors: AnaTurcan File:Iis install 11.png Source: License: unknown Contributors: AnaTurcan File:Iis install 12.png Source: License: unknown Contributors: AnaTurcan File:Iis install_13.png Source: License: unknown Contributors: AnaTurcan File:Iis install_14.png Source: License: unknown Contributors: AnaTurcan File:Iis install_15.png Source: License: unknown Contributors: AnaTurcan File:Iis install_16.png Source: License: unknown Contributors: AnaTurcan File:Iis install_17.png Source: License: unknown Contributors: AnaTurcan File:Iis install_18.png Source: License: unknown Contributors: AnaTurcan File:Iis install_19.png Source: License: unknown Contributors: AnaTurcan File:Iis install_20.png Source: License: unknown Contributors: AnaTurcan File:Iis install_21.png Source: License: unknown Contributors: AnaTurcan File:Iis install 22.png Source: License: unknown Contributors: AnaTurcan File:Iis install 24.png Source: License: unknown Contributors: AnaTurcan File:Iis install 25.png Source: License: unknown Contributors: AnaTurcan File:Iis install 26.png Source: License: unknown Contributors: AnaTurcan File:Iis install 27.png Source: License: unknown Contributors: AnaTurcan File:Iis install 28.png Source: License: unknown Contributors: AnaTurcan File:Iis install 29.png Source: License: unknown Contributors: AnaTurcan File:Iis install 30.png Source: License: unknown Contributors: AnaTurcan