Upgrade Process

This section walks you through applying the Aras Innovator 30 Patch to Aras Innovator Releases 14 or newer. Aras recommends you do a test run of this upgrade on a non-production instance, before attempting this upgrade on your production system.

Upgrading the production instance of Aras Innovator should be done with planning of a short timetable, and an ability to back out the upgrade if something in the process unexpectedly fails.

The following sections are a rough outline of the steps used when upgrading the Aras Innovator production instance.

1. Notify users that the system will be down at a scheduled time, and that they should log out of the system prior to the start of the process.
Note
It is best to give at least 24 hours of notice, as well as a reminder 15 minutes prior to the upgrade.
2. Back up the code tree:

The ‘Code Tree’ refers to files and folders installed to the disk when Aras Innovator was first installed. The default path for the Code Tree installation would be something similar to: C:\Program Files (x86)\Aras\Innovator With the following contents:



You can confirm the installation folder with the following steps:

1. From the Start Menu, select Start --> Control Panel.
2. From the Control Panel, select Programs and Features.
3. Right-click on the ‘Name’ column header and select More…

Select the Comments header if it is not checked Click OK.

4. Search for the Aras Innovator entry in the Programs and Features window.
5. View the value set in the Comments column for the Aras Innovator entry:



Once you have determined where the code tree is installed, you would want to back up the folder and all of its contents.

3. Disconnect all users from the database.

The easiest way to prevent client sessions from committing any further changes to the database is to change the database connection string in the InnovatorServerConfig.xml from <DB-Connection… to <xDB-Connection and restart the w3svc service (IIS). This expires all session and prevents all new connections to the Aras Innovator database through the existing instance.

4. Backup the database.

Place this file in a safe location, as it is necessary when you restore from it, if the upgrade fails.

5. Enable database connections.

After your database backup has completed, you can enable the database connection string in the InnovatorServerConfig.xml by simply changing it from <xDB-Connection… to <DB-Connection and restarting the w3svc service (IIS).

The Upgrade Process is handled by the Aras Update tool. But it has to be run locally on each server where an Aras Innovator component is installed.

1. Copy and unzip the Aras Innovator 30 Patch.zip file on the server.
2. Launch Aras Update tool.
3. Click on the Local button.



4. Add reference to the unzipped Aras Innovator 30 Patch folder.
1. Click on + Add package reference.
2. Select the top-level folder containing the patch and click OK.

Aras Upgrade Package should be added as shown.



5. Click on the Install button.
6. Select appropriate installation components from the listed modules and click the Next button.



Note
The code tree upgrades will only work correctly if the components are installed locally. Database can be upgraded from any machine that can make a successful http connection to Aras Innovator application.
7. Select the Detailed Logging option and then click Next.



8. If updating a code tree components, specify the path to the top-level Innovator folder as shown in example below and click Install.



The installation process should run and complete successfully.

9. If updating the database, specify the following information:
1. Server URL: URL address for Aras Innovator.
2. Database: Name of the database that should be updated.
3. Username: Must be root.
4. Password: Password for root user.



The import process should run and complete successfully.

Note
Remember to disable the root user after the import is complete.

10. Repeat steps above for all modules as needed until all components of Aras Innovator are upgraded successfully.

If your previous version of Aras Innovator had Aras Visual Collaboration enabled, you must update it to include the Aras2DPdfViewer package. This package is required in order to continue using Aras Visual Collaboration. Use the following procedure to upgrade Visual Collaboration:

1. Confirm that a current version of the Aras.PDFViewer Feature license is activated in the database:
1. Log into Aras Innovator as an administrator.
2. Go to Administration\FeatureLicenses in the TOC and do a search for “Aras.PDFViewer” license.
3. If the license is not found, subscribers can request a license from licenses@aras.com.
2. Get a copy of ArasPDFViewer package found in the Utilities folder of the Aras Innovator CD Image.
3. Copy the \Innovator folder to the root of your install directory, overwriting the existing \Innovator folder and all its contents.
Note
It is recommended that an administrator perform this procedure on the server.
1. Click Yes when prompted to merge the ‘Innovator’ folder.
2. Select the Do this for all current items check box and click Yes when prompted to merge the ‘Client’ folder.
3. Select the Do this for the next … conflicts check box and click Copy and Replace when prompted There is already a file with the same name in this location. Click the file you want to keep.

Use the following steps to check if your code tree and database have applied the upgrade to Aras Innovator 30.

1. Log in to Aras Innovator as an administrator.
2. From the Main Menu select Help --> About.
3. Confirm that the dialog shows the following:
• Aras Innovator Release 30 Build 14.0.21.39684



4. Click OK.
5. From the TOC, select Administration --> Variables.
6. Confirm that following variables are listed:

If any part of this test fails, revert to your backups and contact Aras Support at Support@aras.com.

Aras recommends you test any critical functionality before going live with any upgrade

• Test critical functionality
• Test the vault
• Add a new file, view that file, and finally delete that file.
• View existing file from prior to the upgrade.

If all tests are satisfactory, notify users the system is running again.