Pre-migration activities
Aegis V7 Fusion system deployments utilize a singular Microsoft SQL Server database to store all product and process revision information. FactoryLogix is based on the same philosophy, but uses a modern database schema.
Before you can migrate or import any V7 Fusion system product and process revision data to FactoryLogix, you must create and configure a new FactoryLogix database. If you prefer, the FactoryLogix database may be installed on the same database server that currently services the V7 Fusion system, although this is not a requirement. Unlike a V7 Fusion system, FactoryLogix also requires a FactoryLogix Application Server to be deployed within your environment.
Connect FactoryLogix to a V7 database
When connecting FactoryLogix to a V7 database, first you need to determine if the Database Source Name (DSN) connection to the V7 database will use SQL or Windows authentication. Although you can change this option at any time, it is important to determine which authentication method you will use to avoid any disruption of system usage:
Windows authentication requires creating Active Directory accounts which may be subject to any applicable Group Policy Objects (GPOs), including password strength and expirations. If a password expires, system downtime may occur.
SQL authentication requires only a single account that the system will use to access the FactoryLogix database.
The FactoryLogix Application Server will be configured at the time of installation to maintain a connection to your existing V7 database. When you create a new assembly or process in the FactoryLogix NPI client application, you will be given the option to base it on any process revision contained in your V7 assembly tree.
...
...
Note
...
The V7 database connection only needs to be set up on the FactoryLogix Application Server—any connecting clients will not need the V7 DSN configured.
Set up an ODBC connection to the V7 database
From the FactoryLogix Application Server, access the system's ODBC Data Source Administrator by selecting Start > Administrative Tools > Data Sources (ODBC).
On the System DSN tab, select Add to add a system data source.
...
Select SQL Server Native Client 11.0 or SQL Server Native Client RDA 11.0 to select the driver, then select Finish.
In the Create a New Data Source to SQL Server dialog, enter a Name for the connection (FUSION, for example), and (optionally) a Description in the fields provided.
...
Under Which SQL Server do you want to connect to? enter the SQL Server name or IP address or select from drop-down, then select Next.
Do one of the following to select an authentication method:
If using Windows authentication, select the With Integrated Windows authentication button.
If using SQL authentication, select the With SQL Server authentication using a login ID and password entered by the user button.
Enter the SQL user Login ID.
Enter the SQL user Password.
...
Select Next.
Enable the Change default database to: check box, then select the Fusion database from drop-down.
...
Accept the other default settings, then select Next.
Accept the defaults on next page, then select Finish.
...
Select the Test Data Source button. The system should respond with the message Test completed successfully.
Select OK and exit ODBC Administrator.