Install the Target System
This section provides the order in which you must install your target system. For specifics on installing the target system, see the Windchill Installation and Configuration Guide.
 |
The design and implementation of the desired target Windchill architecture is driven by customer requirements. Design your target Windchill system based on your individual business objectives. The design impacts the following steps that install the target system for upgrade.
|
1. PTC requires that you use the same operating system (OS) platform, if it is supported. Set up your hardware using your existing OS or upgrade your OS.
2. The source database version may also need to be updated. Verify by checking the Windchill Software Matrix for the target:
◦ If the target release supports the source database, then no data migration is required.
◦ For most upgrades, the exported source data need to be migrated to a database version compatible with the target Windchill. Refer to the procedures specific to your database version.
◦ After the Windchill upgrade, additional database updates or migrations can be performed if it was not possible to directly migrate the data to the desired database version.
If you are migrating from Oracle to SQL Server, see the Windchill Database Migration Guide for supported paths.
3. Install any other third party applications such as JSDK, Solr (Windchill Indexing) or TIBCO (Windchill ESI).
4. Install all of the necessary Windchill solutions and optional products on the target system that are installed on the source system. The Windchill solution installation must include a supported web server. This must also include Windchill Information Modeler if you are deploying modeled customizations. If your source system uses multibyte characters, select the multibyte character option when configuring the Windchill database. Install the latest critical patch set, if applicable.
During the target installation of Windchill, be aware of the following considerations:
|
|
• The target system must be fresh installation. It must not be updated from previous maintenance release.
• The source system as a single-byte configuration and the target installation as a multi-byte configuration is also supported.
|
a. Working directory server—Be aware of the following considerations when installing and configuring :
▪ Directory server to be installed can be a active directory or other V3 compliant LDAP. Configuration information for the default LDAP must include the LDAP distinguished name and the field mapping information for LDAP attributes. A single LDAP adapter can be configured during target installation.
▪ The PSI field Base Distinguished Name for LDAP Users appears. User can configure single LDAP Adapter in the PSI panel.
There is a single PSI fields that specify the target Base Distinguished Name for the LDAP users.
▪ For eg.Base Distinguished Name for LDAP Users—ou=people,cn=Ldap,cn=Windchill_12.0.2.0,o=ptc could be provided.
▪ For eg. LDAP User Distinguished Name—cn=Manager could be provided.
If you are not sure about your source system’s Base DN, refer to the value of the ie.ldap.propertyBaseDN property in the <Windchill>/site.xconf file on your source Windchill installation.
b. Target database installation options—You can create a new database or use an existing database. You must create a new database installation user or use an existing database installation user. If you chose to create a new database installation user, you must create the database installation user for the target installation before running the PTC Solution Installer (PSI).
c. Organization Internet Domain Name—When specifying the administrative settings, the value of the Organization Internet Domain Name in PSI during the target Windchill installation must be the same as the Organization Internet Domain Name of the source system. To find this value, refer to the value of the property wt.inf.container.SiteOrganization.internetDomain in the <Windchill>/site.xconf file on your source Windchill installation.
d. Base Data Language—The value of the Base Data Language field in PSI during the target Windchill installation must be the same as the value of the Base Data Language of the source system.
e. Multibyte support—the configuration for multibyte support on the target Windchill installation must be the same as the configuration for multibyte support of the source system.
| | The source system as a single-byte configuration and the target installation as a multi-byte configuration is also supported. |
5. When installing target system for upgrade, you must select the Import license from a file option to manually initiate the license activation process.
The details of importing a license manually using License Management utility is described in the section “Retrieving License Using Windchill License Management Utility” in Windchill Licensing.
6. If you are doing multiple upgrade passes, check for and install the latest maintenance releases, if applicable, before each upgrade pass. For more information, see Overview of the Upgrade Procedure for Windchill Products.
7. If your target solution implements a cluster configuration, install and configure hardware cluster nodes.
| | You would need to convert the cluster to a monolithic configuration at a later step. For more information, see the section Converting to a Single Server System. |
For more information on cluster configurations, see Advanced Deployment Considerations.
8. If the system you are upgrading uses Windchill File Server, you must install the Windchill File Server software on the remote file servers before the upgrade. When installing the target system with the PTC Solution Installer, select the option Enable Remote File Server Support. After the upgrade is complete, the Windchill server will re-broadcast out to the remote Windchill file servers and replication and vaulting will work as it did prior to the upgrade. For a test upgrade, cloning of a remote file server is recommended, but not required, unless your test upgrade has the main content on file server sites and you would like to upgrade vault content during the upgrade. Follow the steps below to install and configure file servers before the upgrade. This set up is required if you want to update file server configuration during upgrade by selecting Update File Server Configuration for the file server drop down in the gather upgrade properties phase in the Upgrade Manager.
a. Install file servers. See Set Up File Servers for more information.
| | You can choose to install the target file server on the same host where the production (source) file server is installed for a production upgrade. However, for a test upgrade, install the target file server on a different host than the production file server host as content is modified during the upgrade and you do not want to modify production content during a test upgrade. |
b. Get the public key and the secret key from the source server found at <Windchill>\CCSTools\key.
c. Copy the public key and the secret key found in the previous step to the target main site at <Windchill>\CCSTools\key.
d. Copy the public key to all the file server sites in the location specified by the following property in the wt.properties file on the file server:
wt.intersvrcom.masterSite.1=mainurl,<location_of_main.pubkey>
The key needs to be copied to the location indicated by <location_of_master.pubkey>
e. Start the target Windchill server.
f. Import the secret key by executing the following command from Windchill shell:
windchill wt.fv.tools.PreUpgradeUtility -u=
<username> -p=<password> -t=<16 character token> -i
<username> -p=<password> -t=<16 character token> -i
where <username> and <password> are the site administrator’s login credentials. Use the same 16 character token that you used for exporting the secret key from the source server. For more details, refer to Exporting the Secret Key.
g. Copy vault content as described in Copy Vaults Content to New Hardware.
h. Verify that the method server is running on the file servers before you begin the upgrade on the main site.
9. Run the Windchill version to confirm that all the required components are reported as installed.
10. Verify the installation was successful by checking the method server log for any errors or warnings.