Preparing Your System for the Update
To make the most of working through any update issues on your test system, you must ensure that your test system and your production system are synchronized. If your production system contains code that is not on your test system, then updating your test system may not be as helpful as expected.
Before you update your solution, take your system offline by stopping any web server, servlet engine, and Windchill servers that could interact with the Windchill product files. This includes closing any application that may have a Windchill file open (for example, a text editor, a Windchill shell, or a Windchill log file).
Next, delete the content of the Windchill\Embedded Servlet Engine\instances\ folders.
When your system is offline, but before installing the maintenance release, you must perform all necessary backups. Backing up your files is an important step in the process. If you do not have backup files, you may not be able to restore files if an error occurs.
At a minimum, you should back up the following:
• Windchill database—Use the database backup procedures available for the Oracle or SQL Server environment. This backup must follow your site’s data recovery processes.
• Windchill solution installation directory—By default, this is C:\ptc\Windchill_11.x or /opt/ptc/Windchill_11.x. Back it up by creating a duplicate copy of it and keep it somewhere that follows your site’s data recovery processes.
• Windchill solution LDAP directory content (LDIF file)—Execute the LDAP export procedure described in “Exporting Entries to an LDIF File”. Store the LDIF file somewhere that follows your site’s data recovery processes.
• PTC Solution Installer Global Registry directory—Create a duplicate copy of the PTC Solution Installer Global Registry directory called "installer" located in the <Windchill> directory. Keep this PTC Solution Installer Global Registry directory somewhere that follows your site’s data recovery processes.
|
|
Data in JMX database statistics tables is purged on a regular basis in Windchill. This data is used to populate server charts available from the > > page and various information provided by links from the > > > page in Windchill. If data exists in these tables during an update or upgrade, it is not migrated to the target system.
For more information about Server Status, see the Server Status.topic in the Windchill Help Center. |
Adding the Default Administrator to the Cognos system administrator role
Following steps are required to be performed before starting the update process. The update must be from a source system where Windchill Directory Server was supported, to a system where Windchill Directory Server is not a bundled component. On the source system, it is required that the system administrator is added to the Cognos system administrators role.
1. Login to source Cognos system, using administrator credentials. It is recommended to use Internet explorer.
2. Browse to the Administration Console.
3. Click Security tab.
4. Navigate to Cognos section for Users, Groups, and Roles.
5. Click > .
6. Add Administrator credentials (Administarator user mentioned in db.properties) as wt.cognos.admin.uid. This will add the Administrator user to the Cognos system Administrator’s role.
7. Continue with the update process.
You are required to stop the existing Cognos service and close the associated configurations, files and folders before the update process begins. This is mandatory for updating from:
• Source system with Windchill Directory Server support to target system without Windchill Directory Server support.
• Source and target systems without Windchill Directory Server support.
