Enabling Remote File Server Support if Not Enabled with the PSI
If Enable Remote File Server Support was not selected in PSI during the master installation, you can enable it using the information provided in the following sections.
Manually Creating the Installer Bundle Zip File (CCsInstallerBndle.zip)
You must manually create a bundle ZIP file that contains the installers used for replica installation, using the following steps:
1. Locate the script needed to create installer ZIP and MD5 files in the following location:
<Windchill>/bin/CCSTools/createZip.xml
The script must be run from <Windchill>/bin/CCSTools for each CD image in this format:
ant -f createZip.xml -Dpsi_loadpoint.dir=<val> -Dsource_image.dir=<val>
where <val> is the psi_loadpoint directory containing PSI’s separately managed rule files.
For example:
D:\ptc\PJL\Windchill\bin\CCSTools\>ant -f createZip.xml -Dpsi_loadpoint.dir=D:\ptc\PJL\PSI -Dsource_image.dir=E:\CD_JavaSDK
The result should be <installer_name>.zip and <installer_name>.zip.MD5 files in <Windchill>/CCSTools/install for each CD.
2. Using the script, create a ZIP and MD5 checksum of the following sub-installers. These sub-installer zips and MD5 files must reside in the ZIP respository located in the following location:
(<Windchill>/CCSTools/install
◦ JDK
◦ LDAP Server
◦ Web Server
◦ Servlet Engine
◦ Info*Engine Server
◦ Windchill Services
◦ PTC Solution Installer
|
|
Apache and Tomcat must share a common directory when they are unzipped, for example CD_CAPPS/Apache and CD_CAPPS/Tomcat. To ensure that this structure is preserved Apache and Tomcat must be individually copied into a separate CD_CAPPS folder and this folder must be referenced when calling createZip.xml..
|
3. Gather the installer zips created above into the master bundle zip file, named CCsInstallerBndle.zip. To create this zip run the following command:
ant -f createZip.xml bundleInstallerZips
The result should be CCsInstallerBndle.zip file in <Windchill>/CCSTools/install.
Manually Generating the CCSDsu.zip File (If Necessary)
If Enable Remote File Server Support was not selected during the initial solution installation, this ZIP file does not exist after applying the maintenance updates, so you must generate it manually.
An ANT script that handles this task resides in the following location: <Windchill>/bin/CCSTools/create_ccsdsu.xml. This script creates the CcsDsu.zip file based on a BOM (bill of materials). It maintains a cumulative BOM, <Windchill>/CCSTools/CcsDsuBom.include, with which any future BOMs are merged.
To generate the ZIP file, run the following command from a Windchill shell:
where <params> are:
• -Dccsdsubom_include (optional)—Any alternative BOM file with contents relative to <Windchill>.
This points to a BOM of contents to append to the CcsDsu.zip.
• -Dccsdsu_exclude_list (optional)—A regular expression-based list containing any files to exclude from the DSU. It defaults to <Windchill>/installer/wnc/ccsdsu_regex_exclude_list.txt).
The script runs and generates the CcsDsu.zip and a corresponding MD5 checksum file in the <Windchill>/CCSTools/update directory.
This CcsDsu.zip is downloaded to the remote File Server. Ensure that the ZIP file is placed in the same location as the master site: <Windchill>/CCSTools/update.
The CcsDsu.zip is applied when Windchill is restarted on the File Server.
|
|
When applying an update (a patch or maintenance release) to a master site that has a cluster setup, the patch is applied to each the node in the cluster individually. However, for the CCS (File Server) automatic update to function properly, the files in the <Windchill>/CCSTools/update directory in the master node (background method server) of the cluster must be copied to the <Windchill>/CCSTools/update directory of each node in the cluster. This is essential to ensure that the CCSDsu.zip and its CCSDsu.zip.MD5 files on all nodes are exactly the same.
|
Installing a New File Server Using CcsInstallerBundle.zip and CcsDsu.zip
|
|
CcsInstallerBundle.zip did not exist in versions earlier than Windchill 10.2.
|
To install a new file server using CcsInstallerBundle.zip and CcsDsu.zip use the following procedure:
1. Download the CcsInstallerBundle.zip.
2. Once CcsInstallerBundle.zip is downloaded, unzip it into a common location and run the unzipped PTCSolnInstaller image.
3. To unzip in Windows, you can use WinZip (or a similar application) or the built-in Windows .zip functionality.
For UNIX, unzip <file name> can be used. You may need to install the unzip functionality.
4. When the PSI is started, select the Solution scenario, choose File Server as an installation option, and point the staging area to the location containing all of the unzipped images.
Once you have installed File Server using PSI you need to apply CcsDsu.zip file.
Updating the File Server
Maintenance updates for a remote File Server are required when maintenance releases or patches are applied to the master site. The updates are delivered by a file named CcsDsu.zip that contains all the necessary updates for a maintenance release. If Enable Remote File Server Support was selected when the solution was installed, this ZIP file is generated on the master site when the maintenance updates are applied. To update the file server you must:
• Update Existing Standalone Products on the File Server Using CCsInstallerBundle.zip
• Update Non-Standalone Products on the File Server using CcsDsu.zip
Updating Existing Standalone Products on the File Server Using CCsInstallerBundle.zip
To update existing standalone products on the file server using CCsInstallerBundle.zip use the following procedure:
1. Shut down the method servers, server manager, and web server on the file server.
2. After applying the update on the master and restarting it, check the content of File Server Management inside the Windchill page from > > to see if the standalone products have been updated (verify their date).
3. If the standalone products have been updated, download the CCsInstallerBndle.zip master zip from the master server and extract it into the staging area..
4. Run PSI located on the staging area and select Update Existing Installation.
5. Select the instance of the file server to be updated.
6. Provide the location of the staging area for PSI to install the standalone products update.
7. Click Next until you reach the end of the last panel for running the installation.
Updating Non-Standalone Products on the File Server Using CcsDsu.zip
To update non-standalone products on the file server using CcsDsu.zip use the following procedure:
| If you have completed the master site update and the autoManageCCS property in the wt.properties file is set to true, then broadcast the file server configuration to automatically download the CcsDsu.zip file to the following location on the file server: <Windchill>/CCSTools/update. If the autoManageCCS property is set to false, you must manually download the CcsDsu.zip file from <Windchill>/CCSTools/update using the File Server Management utility, available from > > . |
Updating Non-Standalone Products on the File Server Using CcsDsu.zip Automatically
If your system is set up to update existing File Server installations automatically when the master site is updated with a maintenance release or patch, the following process begins once the Site Manager on the master site has prepared the information and files, performed an update on the site, and restarted that site:
1. The master site notifies the File Server of the need to update.
2. The site is set to Read-only status.
3. The master site sets the status modifier on the File Server to Update in Progress status.
4. Each File Server recognizes the need to update itself.
5. The master site pushes the update to the File Server.
6. The status modifier changes to Restart Required status.
7. The system sends notifications to appropriate managers asking them to perform the restart.
8. If updated versions of standalone products and PSI are available, you must update the existing standalone products on the file server with PSI before restarting Windchill on the file server to apply the update.
9. The restart is performed.
10. The File Server updates itself during the restart.
11. The master site does the following:
◦ Verifies the File Server release level
◦ Removes the Restart Required status modifier from the File Server
◦ Removes the Read-only status from the site
Updating Non Standalone Products on an Existing File Server Installation Manually
If your system is not set up to update existing File Server installations automatically when the master site is updated with a maintenance release or patch, you must manually update each File Server site:
1. Shut down all Windchill-related server applications, including the method servers, web server, servlet engine, and server manager, and exit all Windchill shells.
2. If updated versions of standalone products and PSI are available, you must update the existing standalone products on the file server with PSI before executing the install_ccsdsu.xml file.
3. Open a system console and navigate to the <Windchill>/bin/CCSTools directory.
4. Ensure that the Windchill Directory Server is running.
5. Using ANT, execute the script file install_ccsdsu.xml as follows:
ant -f install_ccsdsu.xml
| If ant -f install_ccsdsu.xml fails on the first attempt, run it again to successfully complete the update process. |
6. Once the execution completes, start Windchill.
> > to see if the standalone products have been updated (verify their date).