This is step 6 of performing a major upgrade from Enterprise Server 7 to Enterprise Server 9. (See a list of all steps)
Our recommendation is to directly upgrade to either version 9.4.10 or to version 9.8.2. Please be aware of the following upgrade paths:
- Upgrading to version 9.4.10 can be done from versions 7.0 – 7.5.
- Upgrading to version 9.8.2 is not directly possible from version 7; this requires one of the following upgrade paths:
- An upgrade from version 7.6 to version 9.6 and then to 9.8.2
- An upgrade from version 7 to version 8 and then to 9.8.2
Note: In most production environments, the new Enterprise server is initially installed next to the existing server so that the new setup can be tested before it is made live. For this explanation therefore, the current Enterprise Server will initially be left intact and a new Enterprise Server will be installed separately.
Step 1. Download the Enterprise Server application from the software download page.
Note: The name of the file is EnterpriseServer_9.x.x_Buildyy.zip, where "x" stands for the Server version number and "y" for the build number. For example: EnterpriseServer_9.0.0_Build100.
Step 2. Unzip the file.
This will create a folder named Enterprise containing files such as index.php, index.html, index.htm.
Step 3. Copy the complete Enterprise folder to the server machine’s Web root folder (such as webroot).
The location is dependent on the system and HTTP Server used (Apache/IIS), but should normally be in the following location:
- Mac OS: /Library/Web Server/Documents
- Windows: c:\inetpub\wwwroot
- Linux: /var/www/html
Step 4. (Optional, only when Content Station Web or the Multi-Channel Text Editor in Content Station is used) Add the files for Content Station Web:
Step 4a. Download the Content Station Web file from the software download page.
Note: The name of the file is ContentStationWeb_9.x.x_Buildyy.zip, where "x" stands for the Content Station Web version number and "y" for the build number. For example: ContentStationWeb_9.0.0_Build100.
Step 4b. Unzip the file. The file is unzipped as a folder with the name contentstation.
Step 4c. Copy the contentstation folder to the root folder of Enterprise Server (see location in Step 3).
Step 5. Verify the following options in the configserver.php file:
Caution: You must not just copy your old configserver.php file over the new one, as important modifications have been made which are necessary to run Enterprise 9.
The type of database used:
- “mysql” MySQL (default option)
- “mssql” MSSQL Server
- “oracle” Oracle
Note: Make sure that the values are in lower case.
The location of your database server. By default this is the same machine as the application server.
- Mac OS: ‘127.0.0.1’
- Windows/Linux: ‘localhost’
Type the machine name, not the IP address.
Use the following:
Step 6. Verify the following options in the config.php file:
Caution: You must not just copy your old config.php file over the new one, as important modifications have been made which are necessary to run Enterprise 9.
Note: If a standard installation is performed using all standard paths with Application Server, database and FileStore all on a single machine, there may be no need to change this configuration file.
The Web server path of the Enterprise folder.
Default value: ‘/Enterprise’
The name of your Enterprise database.
Default value: ‘Enterprise’
The database user to be used by the application server. This is the single database user that is used by the application server to access the database. This database user account needs SELECT, INSERT, UPDATE, and DELETE privileges, plus ALTER TABLE privileges for the creation and deletion of custom properties.
The application server itself authorizes all requests for the user logged on via the Enterprise user tables which are completely separate from the database users. Default is ‘root’. For MSSQL Server you could use ‘sa’ as default.
The password for the database user. The default setting is an empty string.
The path to the FileStore folder (the root folder where Enterprise stores all its files). This can also be a mount point on a different machine.
- Mac OS: ‘/FileStore’
- Windows: ‘c:\FileStore’
Important: This folder MUST be present in order for Enterprise to work. It is also important to make sure that the Web user has Read and Write access rights to this folder.
The folder in which Enterprise stores temporary, export, and production files.
Important: This directory MUST be a child directory of the ATTACHMENTDIRECTORY.
The folder in which Enterprise Server stores temporary system files.
The folder into which all exported files are downloaded.
Step 7. In Enterprise Server, click Advanced > Health Check.
The Health Check page appears.
Step 8. Click Clear All to clear all tests.
Step 9. Select the Database Connection test.
Step 10. Click Test.
If the database is not up-to-date, you are redirected to the Database - Installation / Upgrade page. Enterprise will automatically detect the current status of the installation and will list the necessary SQL scripts to run.
Step 11. (Optional, only when directed to the Database - Installation / Upgrade page). Review the settings on the page and click Start.
The SQL scripts are executed; Enterprise tables are altered and new tables are created. Because you are upgrading, data will be migrated as well. Each SQL command is echoed to your browser; in case any errors occur, these will be shown in red. After running the scripts, be sure to check for these red errors as they will almost always point out a significant problem, most likely to do with the configuration of either Enterprise or the database.
Step 12. In the Config_solr.php file, make sure that the ‘SOLR_SERVER_URL’ setting points to your Solr environment.
Note: The remaining settings in this file are needed to fill the Solr environment with Enterprise data and to query these data. This should work out-of-the-box.
Step 7. Activating the Enterprise license
- 27 September 2016: Added the recommendation to upgrade to either version 9.4.10 or to version 9.8, and provided the possible upgrade paths.
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
Please sign in to leave a comment.