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. To upgrade a multi-user installation, you must first upgrade the server and the database. The content authors must then install the new version of the client, log in to connect to the library, and create a new profile.


Before you upgrade the database and the server, you should:

To upgrade 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 proceed through these screens in the Install Wizard.

  1. 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).
     
  2. Welcome: From this screen, you can access the Installation and Upgrade guides in Adobe Acrobat format.
     
  3. Setup Type: From the Configuration list, select Developer Server or Developer Server and Client.
     
  4. 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.
       
  5. 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.
     
  6. Microsoft .NET Framework Update: Choose to install Microsoft .NET Framework 4.5. Note that a reboot might be required. This screen only appears if the .NET Framework 4.5 needs to be installed.
       
  7. 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.
      
  8. Choose Destination Location: You can accept the default target location, or click Change to specify a different one.
      
  9. 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, enter the virtual directory name used in the previous release. 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.
     
  10. Virtual Directory Options: On the previous screen, you specified an existing virtual directory. On this screen, confirm that choice by selecting the Replace existing virtual directory option.
     
  11. URL Settings: The URL of the web site is determined by the installer and used to populate the initial Developer library. However, what the installer determines and what the actual URL should be may not be the same, so you can modify it as necessary. All DNS and proxy settings should be considered before changing the value. If no changes are needed, or if you are unsure of the settings, the URL should be left as it is currently set.
     
     
  12. Database System: Choose Oracle Database.
      
  13. Oracle ODBC Components: The installer requires a 32-bit ODBC driver to be installed to connect to the Oracle Database. If there is no ODBC driver, the installer installs one. This screen does not appear if an ODBC driver already exists. In the Path field, enter the physical location to which you want to install the Oracle ODBC components.
      
  14. SQL Script Options: If you have already run the scripts to update the database, click the Yes, the scripts have already been run for this version option. If you want the installer to update the database, click the No, the scripts have not been run, let the installer run them option.
       
  15. 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 update the schema and the tablespace. If the scripts have already been run to update 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).
     
  16. Choose Schema: Specify the tablespace name you want to upgrade, 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 is created or used during the installation; the user name is the user name that is created or associated with the schema. This user is for the Developer application to read and write information to the database. If you want to specify a different Oracle application user, deselect the Create Application User Based on These Credentials option. The Application User screen appears next.

    In previous versions, the application user name and password was always based on the schema owner account created. Checking or unchecking the checkbox in this case does not attempt to create anything new; rather the installer verifies the default account was created previously.  If it was not, the Application User screen appears and you are prompted for the application user credentials.
     
  17. Schema Options: If this screen appears, choose Use existing schema if you have already run the upgrade scripts, or Update schema if you have not run the scripts.
     
  18. Profile Credentials: Enter the login for an account in the administrator group in Developer. This account must already exist in the Library.
      
  19. Folder permission: The server or server and client installation needs certain permissions to complete 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.
      
  20. Ready to Install: The Installation Wizard is ready to install the software. Click Back to review or modify any settings.
      
  21. Setup Status: This screen appears while the files are being installed, the schema and virtual directory are being created, and IIS is being configured.
      
  22. 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 upgrade the server with a Microsoft SQL Server 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 proceed through these screens in the Install Wizard.

  1. 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).
     
  2. Welcome: From this screen, you can access the Installation and Upgrade guides in Adobe Acrobat format.
     
  3. Setup Type: From the Configuration list, select Developer Server or Developer Server and Client.
     
  4. 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.
       
  5. 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.
     
  6. Microsoft .NET Framework Update: Choose to install Microsoft .NET Framework 4.5. Note that a reboot might be required. This screen only appears if the .NET Framework 4.5 needs to be installed.
         
  7. 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.
       
  8. Choose Destination Location: You can accept the default target location, or click Change to specify a different one.
       
  9. 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, enter the virtual directory name used in the previous release. 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.
     
  10. Virtual Directory Options: On the previous screen, you specified an existing virtual directory. On this screen, confirm that choice by selecting the Replace existing virtual directory option.
     
  11. URL Settings: The URL of the web site is determined by the installer and used to populate the initial Developer library. However, what the installer determines and what the actual URL should be may not be the same, so you can modify it as necessary. All DNS and proxy settings should be considered before changing the value. If no changes are needed, or if you are unsure of the settings, the URL should be left as it is currently set.
     
     
  12. Database System: Choose Microsoft SQL Server.
     
  13. 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.
       
  14. Microsoft SQL Server Login: This screen appears if the scripts have not yet been run to upgrade the database. From the Database server list, select the desired Microsoft SQL Server and 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.
     
  15. Select Microsoft SQL Server: This screen appears if the scripts have been run to upgrade the database. Choose the server on which the existing database is installed.
      
  16. Choose Database: Select the existing database and enter the credentials.
      
  17. Database Options: If this screen appears, choose Use existing database if you have already run the upgrade scripts, or Update database if you have not run the scripts.
     
  18. Profile Credentials: Enter the login for an account in the administrator group in Developer. This account must already exist in the Library.
      
  19. Folder permission: The server or server and client installation needs certain permissions to complete 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.
      
  20. Ready to Install: The Installation Wizard is ready to install the software. Click Back to review or modify any settings.
      
  21. Setup Status: This screen appears while the files are being installed, the database and virtual directory are being created, and IIS is being configured.
      
  22. 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.

Table of Contents  Back

Upgrade_the_Server