To install the Developer server, you must have administrator privileges to the computer on which you are installing it, or at least have necessary permissions to install software.
Before you install the Developer server, you will need the following information.
Setup Requirements for the Server
The server setup requires the IIS Admin and WorldWide Web Publishing services to be running. If they are not running, the setup program will attempt to start them; if they cannot be started, the installation will be aborted.
Authentication Methods
The Developer can authenticate users in one of two different security modes:
Microsoft Windows: All login authentication to the Developer is done through Microsoft Windows. The system checks the Microsoft Windows account under which the user has logged in to the local computer.
Standard: All login authentication to the Developer is done through accounts stored in the Developer database.
Note: Changing security authentication methods after installation will result in technical issues.
Profile Credentials
During server installation, you will be prompted to enter credentials for an administrator account for the Developer Library. If you are installing with the Standard authentication method, you must enter a user name and password and confirm the password. If you are installing with the Microsoft Windows authentication method, you can choose to use the Microsoft Windows account of the person installing the server or enter the information for a different Microsoft Windows login account.
Secure Web Site and SSL
If a secure web site is available, the installer defaults to that web site. While you can also install on a non-secure web site, using a secure web site and SSL is the recommended method of deployment for the web services, because SSL:
encrypts authentication data (username and password, session cookies) so it is not transported in clear text across networks
encrypts sensitive data
authenticates that the web server is being accessed by users who are who they say they are
protects data that should be accessed by certain users, and not accessed by others
Secure Web Site and Mixed Protocols
The default behavior for the Web Client Framework does not allow mixed protocols. For example, if the server on which you install the Developer uses http protocol behind a reverse proxy using http and the client comes from the outside through https, or, the Developer server and the reverse proxy are https and the client is http, the user will receive an AddressFilter mismatch error when attempting to log in. You can edit the configuration to allow mixed protocols.
To allow mixed protocols:
Locate the web.config file in the Repository.WCF folder in the folder where the Developer is installed on the server.
Open the web.config file in any text editor.
Search for the following tag:
<addressFilter filterMode="Exact"/> .
Edit the tag as follows:
<addressFilter filterMode="Any"/>
This tag appears twice in the file. Search for the second tag and repeat step 4.
Save and close the web.config file.
Change Protocols After Installation
You can install the Developer server on either a secure (SSL) or unsecure (non-SSL) server. If necessary, you can change the protocol after installation; for example, if you attach a certificate to web site, you can change the protocol for the Developer server.
To convert the Developer server from non-SSL to SSL:
Install and run the Developer server on a non-SSL web site.
Log in to the Developer and create a profile, using the HTTP bound web site URL for the Library Location.
Exit the Developer.
Apply the certificate and HTTPS bindings to web site on which the Developer server is installed.
Navigate to the installation location and open the Repository.WCF\web.config file in the editor of your choice.
Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding. There should only be one "name" attribute.
Locate the “security” key located within the key and change the "mode" attribute from “None” or "TransportCredentialOnly" to "Transport".
Locate the XML value for the node configuration/system.serviceModel/bindings/customBinding/binding/upkHttpsTransport. There should only be one node with this name.
Rename the node from upkHttpsTransport to httpsTransport.
Save the changes and close the web.config file.
Log in to the Developer using the Profile with the original non-SSL Library Location. If the HTTP binding has been removed from the site, you can open the Profile as Disconnected.
On the Tools menu, choose Profiles.
If you are in the profile that is on the affected web site, click Exit Profile, then select the profile to modify and click Edit.
In the Profile wizard, edit the Library Location URL to point to the new SSL location.
Log in to the Developer and verify it works.
To convert a Developer server from SSL to non-SSL:
Install and run the Developer server on a SSL web site.
Log in to the Developer and create a Profile, using the HTTPS bound web site URL for the Library Location.
Exit the Developer.
Navigate to the installation location and open the Repository.WCF\web.config file in the editor of your choice.
Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding. There should only be one "name" attribute,
Locate the “security” key located within the key and change the "mode" attribute from "Transport" to "None".
Locate the XML value for the node configuration/system.serviceModel/bindings/customBinding/binding/httpsTransport. There should only be one node with this name.
Rename the node from httpsTransport to upkHttpsTransport.
Save the changes and close the web.config file.
Remove the certificate and HTTPS bindings from the web site to be affected, if desired.
Ensure the HTTP binding is allowed on the web site.
Log in to the Developer using the Profile with the original SSL Library Location. If the HTTPS binding has been removed from the site, you can open the Profile as Disconnected.
On the Tools menu, choose Profiles.
If you are in the profile that is on the affected web site, click Exit Profile, then select the profile to modify, and click Edit.
In the Profile Wizard, edit the Library Location URL to point to the new non-SSL location.
Log in to the Developer and verify it works.
Folder Permissions
The installer will check the folders listed below for the following permissions, and apply the permissions where necessary.
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319 Windows Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
Standard Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
Windows Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
Standard Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
C:\WINDOWS\Temp (Special permissions) Windows Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
Standard Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
Install Directory (C:\Program Files...\Repository.WCF) or any local drive (D:\...\Repository.WCF) Windows Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
Standard Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
<Oracle folder>
Windows Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
Standard Authentication ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute, List Folder Contents, Read
IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
Database Access
If you choose to install the database at the same time as you install the application files on the server, you will be prompted for two sets of credentials for the database. The first set is for an account that the installer can use to create the database. You must use an existing account for this set of credentials, and the account must have permissions to create databases and logins.
Note: A Microsoft SQL database server must be configured with mixed mode authentication.
The second set of credentials is used for the Web Services access for the Developer to read from and write to the database. This can be a pre-existing login, for which you must supply the correct login name and password, or you can specify a new login name and password. The installer grants this account access to the database and adds it to the appropriate roles.
To install the server with an Oracle database, launch the Setup.exe file located in the root folder in the software installation files. If a Security Warning appears, click Run. You are then prompted to choose the language for the Installer, and the Install Wizard appears. During installation, you will proceed through these screens in the Install Wizard.
License Key: Depending on the product you are installing, this screen may appear. If it does, click Browse to navigate to the location of the license key file (usually license.xml).
Welcome: From this screen, you can access the Installation and Upgrade manuals in Adobe Acrobat format.
Setup Type: From the Configuration list, select Developer Server or Developer Server and Client.
Language Selection: Choose the language for the Developer server and library. This sets the default language for the templates and publishing styles in the library.
Software Requirements: Third-party applications are required for installation. If the applications are not present, this screen appears notifying you which applications are needed. You can choose not to continue and abort the installation. If you choose to continue, the applications are installed. If one of them is the .NET framework, the .NET Installer may prompt you to close the Installer. Ignore this warning and do not shut down the Installer.
Select Program Shortcuts: When you are installing the client along with the server, you can choose to install the full Developer or Record It! or both. The full client has all the functionality of the Developer. Record It! is a light version of the Developer, optimized for recording topics. At least one shortcut must be selected.
Select Program Folder: This screen appears if you selected Server and Client from the Configuration list on the Setup Type screen. You can indicate the desired program folder or accept the default.
Choose Destination Location: You can accept the default target location, or click Change to specify a different one.
Choose Web Site: The Available websites list contains the list of all web sites available to the user, allowing you to choose the most appropriate one. Preference is given to secure web sites. In the Application (virtual directory) name box, you can enter the name you want to use for the virtual directory, or accept the default. You also select the mode to use to authenticate the users, either Windows or Standard. Later, when you supply the credentials for the initial Profile, you must choose the same authentication mode.
Note: The web server and the database server must be in the same local network.
Web Site Options: This screen appears if there is no secure web site available or if you did not select a secure web site on the Choose Web Site screen. It allows you to ignore the recommendation and continue with the installation, or create a secure web site manually and retry the installation.
Database System: Choose Oracle Database.
Note: The web server and the database server must be in the same local network.
Oracle .NET Data Provider: A specific version of the Oracle .NET Data Provider must be installed for the Developer to work correctly. This screen appears if the correct version is not present. In the Path field, enter the physical location to which you want to install the software. In the Name field, enter the name of the Oracle Home.
SQL Script Options: If you have already run the scripts to create the database, click the Yes, the scripts have already been run for this version option. If you want the installer to create the database, click the No, the scripts have not been run, let the installer run them option.
Internet Information Services Option: During installation, the Internet Information Services will need to be stopped and restarted. You can choose to continue with the installation or cancel it and install at a later time.
Oracle Database Login: If the scripts have not been run, enter a valid system account name, password, and host string to connect to the Oracle Database server. This account must have permissions to create the schema and the tablespace. If the scripts have already been run to create the database, enter a user name, password and host string that has access to the user schema created to run the application. If the scripts have already been run, the Profile Credentials screen appears next.
Note: Host String represents the name you assign for TNS connectivity in the tnsnames.ora file. This typically identifies the machine, port number and SID of the Oracle database. If you need to connect to a remote Oracle database you will need to supply the host:port/service_name; for example, "myservername:1521/orcl". In some environments a tnsname.ora might not be present. If you are not sure, it is highly recommended that you supply the host/service_name or host:port/service_name (if remote).
Choose Schema: Specify a tablespace name, user name, and password and confirm the password. The user name is limited to 20 characters. The tablespace name is the name of the tablespace that will be created or used during the installation; the user name is the user name that will be created or associated with the schema.
Profile Credentials: If you chose to install the server with standard authentication, enter a user name and password for the default admin user, and confirm the password. If you chose to install with Microsoft Windows authentication, allow the system to use the current Microsoft Windows account or specify another valid Microsoft Windows user account and password.
Folder permission: The server or server and client installation needs certain permissions to complete the installation. If the installer detects any missing permission(s) it displays this screen, which lists the name of the folder, the user name, and the permission it needs before the installer can continue.
Click Yes, grant permission to the folders to automatically grant the permissions to the folders. If the permissions cannot be applied, this screen reappears. This option is highly recommended. Click No, ignore permission and attempt to continue installation to ignore the permission check and try to continue the installation. If the permissions are not set properly, the installation will fail. Use this option if you know that the permissions are already applied. Click Retry to recheck the folders without applying any permissions. The permissions must be applied manually.
Ready to Install: The Installation Wizard is ready to install the software. Click Back to review or modify any settings.
Setup Status: This screen appears while the files are being installed, the schema and virtual directory are being created, and IIS is being configured.
Installshield Wizard Complete: During the installation a file might be in use by the operating system on the computer; this will require a reboot to complete the installation. Also, make sure to run Windows update to get the latest patches from Microsoft.
To install the server with a Microsoft SQL database, launch the Setup.exe file located in the root folder in the software installation files. If a Security Warning appears, click Run. You are then prompted to choose the language for the Installer, and the Install Wizard appears. During installation, you will proceed through these screens in the Install Wizard.
License Key: Depending on the product you are installing, this screen may appear. If it does, click Browse to navigate to the location of the license key file (usually license.xml).
Welcome: From this screen, you can access the Installation and Upgrade manuals in Adobe Acrobat format.
Setup Type: From the Configuration list, select Server or Server and Client.
Language Selection: Choose the language for the Developer server and library. This sets the default language for the templates and publishing styles in the library.
Software Requirements: Third-party applications are required for installation. If the applications are not present, this screen appears notifying you which applications are needed. You can choose not to continue and abort the installation. If you choose to continue, the applications are installed. If one of them is the .NET framework, the .NET Installer may prompt you to close the Installer. Ignore this warning and do not shut down the Installer.
Select Program Shortcuts: When you are installing the client along with the server, you can choose to install the full Developer or Record It! or both. The full client has all the functionality of the Developer. Record It! is a light version of the Developer, optimized for recording topics. At least one shortcut must be selected.
Select Program Folder: This screen appears if you selected Server and Client from the Configuration list on the Setup Type screen. You can indicate the desired program folder or accept the default.
Choose Destination Location: You can accept the default target location, or click Change to specify a different one.
Choose Web Site: The Available websites list contains the list of all web sites available to the user, allowing you to choose the most appropriate one. Preference is given to secure web sites. In the Application (virtual directory) name box, you can enter the name you want to use for the virtual directory, or accept the default. You also select the mode to use to authenticate the users, either Windows or Standard. Later, when you supply the credentials for the initial Profile, you must choose the same authentication mode.
Web Site Options: This screen appears if there is no secure web site available or if you did not select a secure web site on the Choose Web Site screen. It allows you to ignore the recommendation and continue with the installation, or create a secure web site manually and retry the installation.
Database System: Choose Microsoft SQL Server.
Note: The web server and the database server must be in the same local network.
SQL Script Options: If you have already run the scripts to create the database, click the Yes, the scripts have already been run for this version option. If you want the installer to create the database, click the No, the scripts have not been run, let the installer run them option.
Internet Information Services Option: During installation, the Internet Information Services will need to be stopped and restarted. You can choose to continue with the installation or cancel it and install at a later time.
Microsoft SQL Server Login: From the Database server list, select the desired Microsoft SQL server. If the scripts have not been run, select Windows Authentication or SQL Server Authentication to connect to the database. If you select Microsoft SQL Server authentication, enter an existing login name and password that has database administrator access to the server.
Choose Database: Accept the default name for the database or enter a custom name. If you have already run the scripts, you must use the name of the database you created. Specify an existing database user ID and password and confirm the password, if necessary, or, if you have not run the scripts, you can also specify a new database user ID and password. The installer will create the login, if necessary, grant the login access to the database, and give it the appropriate permissions. If you ran the scripts to create the database, you must use the login you created.
Profile Credentials: If you chose to install the server with standard authentication, enter a user name and password for the default admin user, and confirm the password. If you chose to install with Microsoft Windows authentication, allow the system to use the current Microsoft Windows account or specify another valid Microsoft Windows user account and password.
Folder permission: The server or server and client installation needs certain permissions to complete the installation. If the installer detects any missing permission(s) it displays this screen, which lists the name of the folder, the user name, and the permission it needs before the installer can continue.
Click Yes, grant permission to the folders to automatically grant the permissions to the folders. If the permissions cannot be applied, this screen reappears. This option is highly recommended. Click No, ignore permission and attempt to continue installation to ignore the permission check and try to continue the installation. If the permissions are not set properly, the installation will fail. Use this option if you know that the permissions are already applied. Click Retry to recheck the folders without applying any permissions. The permissions must be applied manually.
Ready to Install: The Installation Wizard is ready to install the software. Click Back to review or modify any settings.
Setup Status: This screen appears while the files are being installed, the database and virtual directory are being created, and IIS is being configured.
Installshield Wizard Complete: During the installation a file might be in use by the operating system on the computer; this will require a reboot to complete the installation. Also, make sure to run Windows update to get the latest patches from Microsoft.
To allow mixed protocols: