1) Install Intralink 3.3 (2002471 - ilink-033_2002471) fileserver on pdmlink server
(lfpplm.clearpath.lan).

2) Upgrade Intralink fileserver to later datecode (M022 - ilink-033_M022_WIN).

==================
Agron
==================
A simple backup method to restore the blank PDMLink 8.0  (Pro/INTRALINK 8.0)
after having populated it with data from a first migration attempt
(export/import of an oracle dumpfile). 
  
When performing a data migration, you will repeat the migration procedure
a number of times to rehearse the process.  Each migration attempt results
in data being migrated into the target system.  In order to perform
subsequent migrations, this migrated data will need to be removed from the
target system, otherwise duplicate object conflicts would occur for every
object in the system.
 
The simplest way to reset the system to a pre-migration state, is to import
an Oracle Dumpfile "snapshot".  Creating the snapshot should be done
immediately before a migration attempt begins, at the point where the
Windchill 8.0 system, including the Data Migrator, has been completely
installed, configured, and validated.
 
This "snapshot" of the Oracle database will act as the waypoint that can be
returned to easily, by importing the dumpfile into Oracle.  The following
procedures should be followed for creation of the shapshot before migration
(Steps 1-3), dropping the PDMLink schema user, recreating the user and
Importing the dumpfile to reset the system (Step 4), and recompiling
packages that might have been invalidated (Step 5). 
  
1. After a successful  Pro/INTRALINK 8.0 and Pro/INTRALINK Data Migrator
installation login to Pro/INTRALINK 8.0 as local admin (wcadmin/wcadmin),
configure and validate the external vaults, create the IBA organizer 
(TestOrganizer) and the libraries and products. 
  
2. Run "ildataloader Mapping" and select option 1 (test connection).
If this test is successful exit out of the dataloader and follow the step
below to create a pdmlink dumpfile. 
  
3. Create a pdmlink dumpfile: 
  
DOS>exp system/manager@wind file=D:\ptc\pdmlink\empty_ilink8_M10_dump.dmp owner=guest log=exp.log 
  
where: "wind" is the Pro/INTRALINK 8.0 service name
and "guest" is the owner of Pro/INTRALINK 8.0 schema. [wcuser]
 
These names can be different depending on what you chose during the
installation procedure. 
  
4. After the dumpfile is created, proceed with the migration steps and run all
the migration loaders including the filetransfer. When the time comes that you
want to run the migration a second time around, all you need to do is drop the
PDMLink schema user, run the script <pdmlink loadpoint>\db\sql\create_user.sql 
and  import the dumpfile you created in the previous step as illustrated in
the example below: 
  
DOS> sqlplus system/manager@wind
SQL> drop user guest cascade;
SQL>@<pdmlink loadpoint>\db\sql\create_user.sql
Enter username: guest
Enter temporary tablespace: TEMP
Enter users tablespace: USERS
SQL>exit 
  
DOS>imp system/manager@wind file=D:\ptc\pdmlink\empty_ilink8_M10_dump.dmp full=y ignore=y log=import_log.lst 
  
5. Follow instructions of TPI 128926 to identify and re-compile any packages
that might have been invalidated. 

=================

Migration Roadmap 

Migration involves definition, rehearsal, and smooth execution of a solid 
process especially when moving between unknown or dissimilar systems and 
must be executed with minimum impact on users using legacy systems. 

To ensure smooth migration it is important to structure the process as 
follows: 

. Plan 
. Conflict Identification (Metadata Only Migration) 
. Conflict Resolution and Data Cleansing 
. Rehearsal Migration 
. Production Migration 

====================================================================

Plan 

Planning is similar to the planning activity that occurs in other project types. 
The following tasks are an important part of the planning process: 

. Create a project plan for migration 
. Determine the data mappings between the source and target systems and 
document them in a migration specification document. 
. Create a validation plan. A validation plan is a concise documentation of 
test cases and tests, test objects, and expected results. The plan is applied 
during the validation steps that are included in the Rehearsal Migration 
and the Production Migration phases. 

====================================================================

Conflict Identification (Metadata Only Migration) 

The Conflict Identification phase involves an initial migration of metadata 
(data contained in Oracle, but not the file vault data) from the source 
Pro/INTRALINK system to the target system, for the purpose of identifying 
conflicts. The Pro/INTRALINK Data Migrator 8.0 requires that conflicts be 
resolved as they are encountered, so it may be necessary to apply temporary 
artificial conflict resolutions during the Conflict Identification phase, in 
order to complete the metadata-only migration. An artificial resolution might 
consist of generically adding DUPLICATE_ to the names of any objects that 
have duplicate object conflicts. These objects will have real conflict 
resolutions applied during a later phase. 
To perform metadata migration: 

. Run the migration tool on the metadata only (do not run the File Transfer 
data loader in this phase), using data mappings from the migration 
specification document. 
. Conflict logs generated during this process enable you to identify 
conflicts. 

====================================================================

Conflict Resolution and Data Cleansing 

A data migration conflict occurs whenever the process of correctly migrating 
data from the source system to the target system is unclear. In many cases, 
conflicts can be resolved by deciding how best to migrate the data and which 
data must be altered to support that decision. The following steps are an 
important part of this activity: 

. Review conflict logs to determine conflict resolutions and document them 
in the migration specification document. 
. Update the validation plan and project plan, if necessary, based on the 
results of the Metadata Migration and Conflict Resolution. 
. Apply required conflict resolutions and data cleansing to the data in the 
source Pro/INTRALINK system. 

====================================================================

Rehearsal Migration 

The process validation activity is a full rehearsal of the migration process. 
This activity always starts off with some readiness activities, such as the 
setup, installation, configuration of hardware and software, and continues 
with a series of process steps and validations. The following are an important 
part of this activity: 

. Execute a full migration using Data Mappings and Conflict Resolutions 
from the migration specification document. 
. Validate the migration process using the validation plan. 
. Review the rehearsal validation results. Update the migration 
specification, validation plan, and project plan, as necessary, based on 
these results. 
. Perform additional conflict resolution and data cleansing, if necessary, 
prior to Production Migration. 

====================================================================

Production Migration 

This activity is the live performance of the rehearsed migration process. The 
production migration is usually done on the production data or production 
systems. After you begin executing the process steps and the validation steps, 
the goal is to do them for the last time, and to go live with the software. The 
following are the important steps of this activity: 

. Execute Production Migration using Data Mappings and Conflict 
Resolutions from the migration specification documents. 
. Validate the migration process using the validation plan. 
. Review the Production Migration validation results. 
. Make a decision to Go Live with the software. 

====================================================================

Path=
D:\oracle\ora92\jre\1.4.2\bin\client;
D:\oracle\ora92\jre\1.4.2\bin;
D:\OraHome_1\jre\1.4.2\bin\client;
D:\OraHome_1\jre\1.4.2\bin;
D:\OraHome_2\bin;
C:\Program Files\Oracle\jre\1.3.1\bin;
C:\Program Files\Oracle\jre\1.1.8\bin;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\System32\Wbem;
D:\oracle\ora92;
D:\oracle\ora92\bin;
d:\wc_fs\fileserver3.3\bin

====================================================================

1. Copy all files in <mig_home>/ilscript/ to <ProI_home>\tools\bin 
 
2. 
PROI_SYS_PWD = dschangeme 
ORA_SYS_PWD = manager 
 
3. <ProI_home>\tools\bin\tclsh healing_before_migration.tcl 
 
4. To put Pro/INTRALINK in restricted mode, run the following script
from a command window:
 
<ProI_home>\tools\bin\tclsh pdm_sql_wrapper.tcl restrict_proi_usage.sql
 
[View these scripts & see if both should be run at same time].
 
5. Lock Pro/INTRALINK Schema and Unlock the Migration Schema 
 
<ProI_home>\tools\bin\tclsh disable_il_for_migration.tcl <migration schema password>
 
<migration schema password> is the ilmigpassword  property value in the
<MIG_HOME>\codebase\com\ptc\migration\migration.properties file
(the default value is migchangeme).
 
6. 
 

 
