How to Upgrade/migrate from 9.01 to latest 9.1 ?

Reply

mmukesh Posted: Tue, May 5 2009 8:40 AM

rated by 0 users

Hi,

How to upgrade/migrate from 9.01 to 9.1 with losing the data and work like items/categories/lifecylce/workflows/data entries etc.?

Cheers

MK

Reply

RonCK replied on Wed, May 6 2009 11:11 AM

rated by 0 users

I'm very interested in knowing this as well.  Has anyone done the upgrade themselves?  We would like to upgrade but don't want to loose any of our current customizations.

best regards,

RonCK

Reply

Kevin Friske replied on Tue, Jun 9 2009 1:26 PM

rated by 0 users

Hi ,

I have just completed our upgrade from 9.01 to 9.1.  It is not a difficult task if your willing to put some time into it.  Here are the steps that I used:

• Create Package Definitions of the items you have created or modified from the original install. This will take work but it will make life a lot easier when newer versions come out.
• Export the Packages you have created using the Solutions upgrade tool.
• Install the Aras 9.1 onto a test server.
• Import the Packages you just exported into Aras 9.1.  (You may have to modify the XML file if errors occur, and I used the 902 version of the upgrade tool.)
• Review the items just imported by comparing them to the production version of Aras.
  • I did have to re-associate some of the Relationship Types and I had to add the Life Cycle Map (since that is a major change in 9.1).
  • The Forms may also need a little adjustment since new tools have been added (groupbox for one).
  • Also if you have Methods that are used in the Forms to place information be aware that the <span> tag has been replaced by the <div> tag.
• The next step is to import the data from the Production database to the Test Database.  This is a very critical step in that not all tables need to be synced.  I used a database compare tool that allowed me the ability to see the changes made from 9.01 to 9.1 so that I could better understand the data structure and flow.  I then used the same tool to start syncing the data.  I did not move all the data over at one time because I wanted to verify the information in 9.1.
• Once the data was moved over I then started to verify the functionality of our Mods to make sure that they were working the way we set them up originally.  I did have to tweak some of the items but most seemed to be fine from the initial import.
• Once satisfied that the functionality and data is good move the database (under a different name) to the production SQL Server and install the new Aras 9.1 onto your Production IIS Server (I used a different directory then the original so that i could still get back to the 9.01 version if needed).  Remeber to associate the Vault location to your Production Vault.

Patience is a virtue when doing this, and yes Murphy's law reared its ugly head a few times.  I did have to start over 3 times with a new database before I got the information over correctly. Good luck

Reply

RonCK replied on Tue, Jun 9 2009 2:52 PM

rated by 0 users

Thanks for the great reply friske1!  That answers several questions that we were fighting with, but it brings up a few more.  How did you get the Solutions Upgrade Tool?  Were you a subscriber?  Is there a way we could get it?

thanks again,

RonCK

Reply

Kevin Friske replied on Tue, Jun 9 2009 3:38 PM

rated by 0 users

Go to Aras website, click on Projects in the upper menu bar. Then click on Solutions in TOC on the left side and in the main window you will see a list of solutions - go towards the bottom and you will see it there (Solutions Upgrade Tool).

Kevin

Reply

SamsAn replied on Tue, Jun 9 2009 4:12 PM

rated by 0 users

Before importing 9.0 AML into 9.1 database you should manually setup ItemType.history_template property instead of save_history=1 flag (just an addition to the pointed metadata changes (Life Cycle Map, Forms)). There are a lot of places with changed metadata in 9.1, but i bielive they can be ignored during the proposed way of migration.

In general, it is not accurate to use AML exported from 9.0X to import into 9.1. You should upgrade 9.0X database to 9.1 version using Innovator 9.1, then export your solution from the upgrade db, then import the exported AML into another db.

SamsAn.
Original Mind Any Level Innovator Solutions Free-Lancer, http://sites.google.com/site/caraacc

Reply

Phil replied on Mon, Apr 19 2010 4:14 PM

rated by 0 users

I'm running into issues with simply trying to upgrade from 9.1 to 9.2. I was hoping it would have been as simple as running the 9.2 installed and then selecting "use existing database" during the install.  Not so much.  The funny thing is, even with doing it that way, I am able to get Aras up and running. It just turns out that I am not able to access ANY items. I can see them in the TOC, but no items show up in the grid frame.

I ran dbcompare and saw that there are really no database differences (schema/object) wise between the 2 versions. I then ran a SQL profiler session to see exactly what statements were ran during searches for items. It looks as if though there may be something with the Preference table or something pertaining to the Users that could be creating this mess.

Any help would be greatly appreciated.

Reply

Kevin Friske replied on Mon, Apr 19 2010 6:47 PM

rated by 0 users

Phil,

This version was a little easier to upgrade.  There are some changes to the software such as the search package changed and a notification package was added.  I am sure there is more but I have not noticed the change (Other then IE8 support).

The following is the process I took to upgrade our system.  Please be advised that we are still in the testing phase of the upgrade system but I believe it to be stable. You will also need the Import and Export tools in the Projects area.

1. I installed Aras 9.2 onto a test server.
   1. Let it create the default Database
      1. Name it whatever you desire just so that it distinguishable from the other Innovator databases on SQL
      2. Have the install create a new website (I called mine InnovatorTest)
   2. I then created a copy of the live 9.1 database.  I named it InnovatorSolutions_9.2
   3. Modify the InnovatorServerConfig.xml file to include the copied database as a selection
2. Use the export tool and export the entire list 9.2 pakages.
   1. In the tool connect to the Test site
   2. Login to the database that was created in the install
   3. Select a package and export
      1. I did them independently as to allow installation of a single package at a time
      2. Also allowed for me to remove the unneeded packaged xml files
3. Now that all the packages are exported it is time to import into the Copied Database (ie: InnovatorSolutions_9.2)
   1. The first thing you will need to do is to go into core folder Core\com\aras\innovator\core\  that was exported in step 2
      1. There is a change to ItemType Method that has to be executed first
         1. Create a folder in the ../innovator/core folder called original
         2. Move all the folders into the original folder
         3. in the ../innovator/core re-create the folder ItemType and copy the xml file method.xml (That was moved into the folder original) into it
      2. Run the import tool  logging into the test server (ie: http://localhost/InnovatorTest)
         1. Login as root
         2. Choose the copied database and login
         3. In the Manifest file choose the Core Folder
            1. This should give you the aras.innovator.core package
         4. I used the type=merge  and mode=fast
         5. Select aras.innovator.core and run the import
         6. Once completed you will have to move the folders that were copied into the Original folder back and re-run the import.
         7. I then ran the packages in this order
            1. Search package
            2. Notification Package
            3. Admin Package
            4. i18n Package
            5. Dashboard Package
            6. History Package
            7. PLM package
               1. This package included PLM, Project and QP
               2. I removed the SQL package  so that it would not over right the stored procedure mods
               3. I ran PLM first, then Project and then QP
            8. Sharepoint Package
            9. I skipped the Preference Package.  It overwrote some of the grid mods.  I may have to add some of the package later based on functionality.
      3. That was pretty much it.  You have to watch your imports to see were it dies and investigate.  I did have to remove additional xml files due to our mods.  But these files were usually identical to the 9.1 version.
      4. After the CORE, SEARCH and NOTIFICATION packages were completed I would log into the test server (connectiong to the copied database) after each import to verify how well the imports were doing.
      5. Once you feel you have a stable test system then you can backup the live database and make the changes stated previously along with any variations to it. 
      6. Install Aras 9.2 into the live Production Server
         1. In the install do not create a database just use the existing live database that was just modified
      7. That's it!

Hope this helps, I ran through it quickly so forgive me of any typos. If you have any questions just let me know.

Kevin

Reply

Phil replied on Wed, Apr 21 2010 1:08 PM

rated by 0 users

Friske, thanks so much for your help! Its pretty impressive that you figured this all out on your own!

Quick question though: When you were importing the 9.2 packages into the 9.1 database which options did you use? I tried merge and fast...but that didnt seem to work. Thanks again for your help.

Here is the behavior I am seeing: I can't get to any Items. Even if I go to Administration->ItemTypes and run an empty search...it comes back with nothing. I am not sure what could be causing this.

Reply

Kevin Friske replied on Wed, Apr 21 2010 1:48 PM

rated by 0 users

Phil,

In some situations I changed the the type to Ignore.  I know when I imported the Nofications package I switched the mode  to Thorough and the  type to Merge. 

 I also forgot to mention that I had to login into the Test system, using the copied database, and remove the calendars for 2011. 2012 and 2035 and then let the Project package re-install them. You could also do this in the live system before you copy the database.

It is truly trial and error.  There may be some of the xml package files that you will have to remove from the import package that is causing you problems.  I would always examine the xml file and check it against the 9.1 package (follow export procedures from previous post for 9.1).  If it is needed I would just remove it so the package would load and then place it back in and re-run the import.  The import tool will stop at the problem and show you an error.  Before accepting the error  you should be able to see what folder and xml file that is causing the problem in the status area. 

Again if there is anything else I can do just let me know.

Kevin

Reply

Kevin Friske replied on Wed, Apr 21 2010 1:51 PM

rated by 0 users

One thing I forgot to mention.  I used the 9.02 Import/Export tool.

Kevin

Reply

Kevin Friske replied on Wed, Apr 21 2010 1:55 PM

rated by 0 users

Phil,

To the search problem.  That is due to the upgrade that was done on the search module (my opinion).  That is why I imported the Search package after the Core package.  I too had that problem and importing the Search package solved that.

Kevin

Reply

Phil replied on Wed, Apr 21 2010 2:50 PM

rated by 0 users

I can't say that this is the easiest upgrade to a service pack/next release of anything that I have ever done. So...after following the import order you had listed previously it is sorta working, but not really.

I was able to do all of my imports with modes MERGE and THOROUGH...if something bombed out that didnt look too useful (all in the report and qp packages) I just removed the offending xml file. Besides that , all the other imports went smoothly.

Now, unfortunately I can only login to my test 9.2 system using the root user (which is the account I used for the imports). Any other account I login with, I get a blank screen that just sits there. Even when I do login with the root user, when I go to access Items I get somewhat cryptic error messages. This seems to point to something going kerfloowie with the user account/permissions ......but I don't know how that could have got hosed?

Reply

Kevin Friske replied on Wed, Apr 21 2010 3:26 PM

rated by 0 users

Phil,

I guess easy is relative term :).  I am sorry that you are experiencing problems.  The only other thing I did in my ealier attempts to upgrade was run the following script on the copied database.  It is part of the CoreandSolutions92.sql file in the DB folder.  But I removed and copied the live database several times as I was documenting the procedure for the upgrade and I did not run this on the current upgrade but you could give it a shot.  Your problem may be related to SQL authentication problems. Make sure innovator is set up as a user and that it has rights to the copied database and is applied to the schema innovator of the copied database.  I copied my database to the same server that the live database lived so users were not an issue.  If you could post the error I might be able to help even further.

 -- Generated on 4/1/2010 2:39:53 PM
--    into server=NULL dbname=SolutionsInnCore92Build5562TagRELS9_2
--    from SolutionsInnCore92Build5562TagRELS9_2.xml
IF EXISTS (SELECT * from sys.database_principals WHERE name='aras_innovator') DROP USER aras_innovator
GO
CREATE USER aras_innovator WITHOUT LOGIN WITH DEFAULT_SCHEMA=[innovator]
GO
GRANT ALTER ON SCHEMA::[innovator] TO [aras_innovator]
GO
GRANT DELETE ON SCHEMA::[innovator] TO [aras_innovator]
GO
GRANT EXECUTE ON SCHEMA::[innovator] TO [aras_innovator]
GO
GRANT INSERT ON SCHEMA::[innovator] TO [aras_innovator]
GO
GRANT REFERENCES ON SCHEMA::[innovator] TO [aras_innovator]
GO
GRANT SELECT ON SCHEMA::[innovator] TO [aras_innovator]
GO
GRANT UPDATE ON SCHEMA::[innovator] TO [aras_innovator]
GO
GRANT CREATE FUNCTION TO [aras_innovator]
GO
GRANT CREATE PROCEDURE TO [aras_innovator]
GO
GRANT CREATE TABLE TO [aras_innovator]
GO
GRANT CREATE TYPE TO [aras_innovator]
GO
GRANT CREATE VIEW TO [aras_innovator]
GO

Do you have a tremendous amount of modifications applied to your Aras? 

Kevin Friske
Mitek Corporation

Reply

Phil replied on Wed, Apr 21 2010 3:52 PM

rated by 0 users

I haven't tried your sql script yet, but I may give it a shot here shortly. I checked the sql user/schema settings for innovator and they seem to be ok. 

It is really strange. Whenever I login with a user account that isn't "root" , It comes up with an IE error : "The webpage you are viewing is trying to close the window. Do you want to close this window?". To which I tell it NO, and then the Aras screen just sits there and nothing comes up. 

However, when I log in as root, I do not get that error and everything (with the exception of opening individual Items), navigates and displays as expected.  The search even works.  I really don't think that its a coincidence that root was the user I used for the imports.