Pro/INTRALINK:

Upgrading from 2.0 to 3.0

Stan Balish


Even with all the excitement about PTC's newest release of its Pro/ENGINEER
database management software, Pro/INTRALINK 3.0, there are still people who
will cringe at the thought of upgrading their current Pro/INTRALINK
installation. These fears are mainly due to the potential problems that can
occur when upgrading the dataserver. The PTC Technical Support knowledge base
on the PTC website offers a very good suggested technique on how to upgrade
Pro/INTRALINK 2.0 to 3.0. If you follow PTC's technique and you do not get
any errors, than you are good to go. If not, the following technique will
make the transition to the Pro/INTRALINK 3.0 release a bit smoother while
eliminating as much risk as possible. Remember before you start that you
should always do the upgrade on a test server first before you upgrade your
production server. Also, it is critical to make a backup of your meta-data
and your file vaults.

The upgrade to Pro/INTRALINK 3.0 breaks down into 5 steps:

1) Export a dump file from 2.0 dataserver

2) Back up files from 2.0 vaults

3) Install ilink 3.0 fs and 3.0 ds on the new or existing machine

4) Import the 2.0 dump file to the 3.0 dataserver
Run ilink_patches. Modify the oracle tables via DSMU or srvmgrl

5) Move/copy files from your 2.0 vaults to your 3.0 vaults.

Now we will look at each one of the five steps to make sure that you understand
what needs to happen during each step. (Note: This procedure applies
to Windows NT/2000 OS only.)

Step 1
Create a dump file of your Pro/INTRALINK meta-data. You can either
use your DSMU (Data Server Management Utility) or open a MS-DOS window
and go into the /intralink/export directory and execute the
ILINK_EXPORT.bat file. Next, copy all your files from the 2.0 file vault
to a media device, a CD-ROM or a separate folder on the machine.

Step 2
Now that you have all your data backed up you can go ahead and shut down
the 2.0 dataserver and then the fileserver. Next, install the 3.0 fileserver.
If you are using the same machine that your 2.0 installation is on then just
upgrade the fileserver. If you are using a new machine then a fresh install
of the fileserver will do fine. Once you have the 3.0 fileserver installed
you can go ahead and install the 3.0 dataserver. For the technique described
in this article, a fresh installation of the 3.0 dataserver is recommended.
If you are not going to use a new machine for your 3.0 installation, be sure
to uninstall the 2.0 dataserver while using the PTC-suggested technique.

There are a few steps involving registry cleanup that need to be completed
before you install the new 3.0 dataserver.

Step 3
Now that the 3.0 fileserver and the dataserver are loaded and running,
import the dump file that you created in Step 1. To do this, open an MS-DOS
window, return to the /intralink/export directory, and execute the
ILINK_IMPORT.bat file. The meta-data from the dump file will now be loaded.

Step 4
To prepare the meta-data to be used in the new 3.0 installation it is
necessary to set a few variable values and then run a number of patches.
To do this, open an MS-DOS window, go to the
/intralink/dbs/ilink_patches/tools directory, and type the following commands
one at a time to set variable values. Be sure to type the commands letter for
letter exactly as they are shown below:

set PROI_SYS_PWD=dschangeme
set ORA_SYS_PWD=manager
set FS_SYS_PWD=fschangeme

In the same folder, type the following commands one at a time in order to run
the patches. Be sure to type the patch commands exactly as they are shown below:

ilink_patches.bat oracle ilnk
ilink_patches.bat SCHEMA English INTRALINK
ilink_patches.bat VALIDATION English INTRALINK

Now that the variable values are set and the patches have been run, you are
ready to modify the oracle tables. This procedure will configure the meta-data
to recognize the new fileserver and dataserver hostnames (if different) as well
as the new vault paths where your files will be stored. In an MS-DOS window
(location is not important but /intralink is fine), type the following commands
exactly as shown below. Text that is in parentheses is for information purposes.
svrmgrl
connect internal/internal;

This section will update the dataserver:
select * from pdm.pdm_pool (this will list vaults from old DS)
update pdm.pdm_poolset poolpath='(new vault path)';
update pdm.pdm_poolhostset poolhost='(new hostname)';
commit

This section will update the fileserver:
select * from pdm.pdm_fileserver (this will list hostname from old FS)
update pdm.pdm_fileserverset fsvhost='(new hostname)';
commit
exit

Step 5
The last step is to move or copy all of your files from the old 2.0 vault into
the new 3.0 vault. Be sure not to modify any properties of the vault files
during this process. Otherwise, this could result in the files becoming
unreadable by Pro/INTRALINK.
Your new installation of Pro/INTRALINK 3.0 is now ready to be used. Although
this procedure may seem somewhat on the complicated side, it is a great way
to get up and running when other techniques will not work.

More For Customer Service Calls

Pro/INTRALINK Log in to the Pro/INTRALINK data server as the user who installed the data server
(usually user "oracle" on UNIX platforms or "administrator" on NT platforms).

Create a data directory, (usually the directory is named using the associated call number),
in which to store data for this issue.

Ensure that all users are currently logged out of Pro/INTRALINK, but keep the data server running.

Create a dump file of the data server by running the script ilink_export as follows:

/intralink/export/ilink_export

When prompted for the name of the dump file, include the path to the data directory created in Step 2
so that the dump file will be created in the data directory.

Create a tar or zip file of each vault location and place those files in the data directory created in Step 2.