I have begun trying to migrate eCM content for an test upgrade I just made, but having a very difficult time following the manual.
Here is my entire configuration.
10.6 is still in production on a web server and SQL server.
I have a seperate server that hosts the entire iMIS 15.1 application and web server pointing to the common SQL server below.
SQL server hosts both databases - the current development database in 10.6 which is a mirror of production 10.6 and the newly upgraded to 15.1.3632. Content folders reside in both dB's.
Copy of Production 10.6 dB: iMIS15_DEV
Upgraded db: iMIS15_1
I'm trying to follow the directions but it's very confusing to follow them, because it's assuming that you've already put the dB into production and eCM is already working in iMIS 15.1 which doesn't seem like a reasonable assumption. Here is how I followed the steps in the instructions:
1. I applied this script to the iMIS15_1 dB
UPDATE SystemConfig
SET ParameterValue = 'CM5:provider=SQLOLEDB;
Data Source = ISRISQL;
User ID = sa;
Password = Correct Password;
Initial Catalog = iMIS15_DEV;'
WHERE ParameterName = 'SecondaryConnection'
AND ParameterValue LIKE 'CM5%'
The script resulted in one changed record.
2. I went into the iMIS15.1 application/web server and modfiied the CM5MigrationTool.exe.config file to the following information
<connectionStrings>
<!-- datasource for the destination database.-->
<add name="DataSource.iMIS.Connection" connectionString="server=ISRISQL;database=ISRIIMIS_15_1;uid=sa;pwd=isriimis;" />
</connectionStrings>
and
<add key="SourceRootLocation" value="O:\Program Files\ASI\iMIS15\indexServiceProtected\Public" />
I ran the CM5MigrationTool.exe file from the same server which hosts the new iMIS 15.1 configuration.
Here is the error that I'm receiving:
O:\Program Files\ASI\iMIS15\Net\bin>cm5migrationtool.exe
Starting migration...
Loading import log...
Loaded 8 import log entries in 00:00:00.0015685.
Loading public view page map...
Error during migration: System.Data.OleDb.OleDbException: Invalid object name 'dbo.COmponent.Script_ref'
at System.DAta.OleDb.OleDbDataReader.processResults(OleDbHReslut hr)
at System.Data.OleDb.OleDbDataReader.nextResult()
at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBeahvior beahvior, String method)
at System.dAta.Ole etc... etc... etc... (Hope that's enough typing)
This doesn't look
This doesn't look right:\
<add key="SourceRootLocation" value="O:\Program Files\ASI\iMIS15\indexServiceProtected\Public" />
The value of that key should be the path to your eCM source folder, which unless things are configured very differently than I expect, should not be in your indexServiceProtected folder (that folder is new in 15.1 and stores search metadata and uploaded files for WCM).
Also, note that this tool cannot be used if you were running eCM in two-database mode; you must have your eCM/eSeries database as the same database as your iMIS database. (I don't believe the upgrade will even succeed in two-database mode, so that's probably not the case here.)
If you are using a single-database install and just want to migrate your eCM content into WCM, then both connection strings should be the same (i.e. the source and destination DBs would be the same). They only need to be different if you actively want to migrate eCM content into a different database.
Eric Means
System Architect, ASI