Production — Enterprise Deployment Checklist
Provided below is a summary of the steps involved in planning and performing a Production – Enterprise deployment. Use this as a checklist when planning and performing an installation.
For guidance on upgrading existing deployments, refer to the section at the end.
Planning a Production – Enterprise Deployment
1. Decide which optional components will be installed. Some optional components are selected for installation by default. You will need to de-select any optional components that you do not wish to install:
a. Modeler Model Editor
This component, and its sub-components, are required to use the Modeler client application. These components are required for Client Only installations and selected by default. These components are optional for Server Only installations and are de-selected by default.
b. Floating License Server
This component is required for server-based floating licenses, which is the recommended licensing approach for this deployment. This component is selected by default during the Server Only installation. The Floating License Server can be installed on any computer but it is recommended that it is installed on the Modeler Server as part of the Server Only installation. For more information on licensing, refer to Introduction to licensing Modeler.
c. DOORS Synchronizer
This component is required if you wish to use the Integration for IBM Rational DOORS. If IBM Rational DOORS is installed on your machine, this component will be selected by default. For more information on this integration, refer to Overview of Integration for IBM Rational DOORS.
d. Integrity Lifecycle Manager Integration Admin
If you wish to use the Integration for PTC Integrity Lifecycle Manager, this component is needed to perform configuration of the Integrity Lifecycle Manager server. It must be installed on at least one computer, either the Modeler Server or a Modeler Client. For more information on this integration, refer to Overview of Integration for PTC Integrity Lifecycle Manager.
e. Model Manager
For more information on this component, refer to Model Manager overview.
f. Web Interface
For more information on this component, refer to Overview of Web Interface.
 |
Web Interface is required if you wish to use the REST Service or the OSLC Provider.
|
g. Documentation
This component is selected by default during the Client Only installation.
2. Plan the system architecture:
a. Decide how distributed users (those not physically close to the Modeler Server) will access and use model data. Refer to the Help topic called Overview of working across sites as well as the other topics in chapter called Working across sites. Decide if Microsoft Remote Desktop Service or Citrix XenApp (previously called MetaFrame) will be utilized.
b. Review Client/Server architecture information and identify the computers that will host the Modeler Server (or servers) and Modeler Clients (or Microsoft Remote Desktop Service or Citrix XenApp clients). Refer to the Client/Server section of Installation configurations. If you are using Microsoft Remote Desktop Service or Citrix XenApp, refer to Direct access of a remote model through Microsoft Remote Desktop Services or Citrix MetaFrame.
c. Review Client/Server architecture installation process. Refer to Installing Modeler for a project team.
d. Review security considerations explained in Managing Modeler and Web Interface Security. If required, plan the security configurations for your site.
e. If you are installing the Web Interface, determine the user authentication strategy and if LDAP will be used. Refer to Setting up user authentication for a Web Interface website.
3. Plan licensing:
a. The Production – Enterprise deployment uses server-based floating licenses. Identify which license type(s) you will be using. Refer to Modeler license types: subscription, evaluation, permanent, incremental and upgrade.
b. Identify which features will be needed as well as the number of licenses for each feature. The license file will be requested from PTC Support after installation. For more information on licensing, refer to Local and server-based licensing.
c. If you have chosen to install the Web Interface, plan the licenses required for Web Interface Server and Clients. Refer to Client licensing of a Web Interface website.
d. If you have chosen to install Model Manager, refer to the Licensing Model Manager section in Installing Model Manager.
4. Plan the environment:
a. Confirm that the computers which will host the Modeler Server and Modeler Clients meet the environment requirements. Refer to Environment requirements for each installation type.
b. Confirm that the computers which will host the Modeler Server and Modeler Clients meet the hardware requirements. Refer to Hardware requirements.
5. Plan installation of maintenance releases:
◦ Access PTC Support and check if there are any Maintenance or patch releases available for the relevant version of Modeler (e.g. M010). If so, download the installation files for the latest maintenance release.
Performing a Production – Enterprise Deployment
1. Prepare for Server Only and Client Only installations:
a. Ensure all environment requirements are met for Server and Client computers. Refer to Preparing for a server only installation and to Preparing for a client only installation.
2. Perform Server Only installation:
a. On the computer that will host the Modeler Server, complete the steps provided in Performing a server only installation. Select the optional components you require, such as Model Manager or Web Interface.
b. If you are using Microsoft Remote Desktop Service or Citrix XenApp, install the Microsoft Remote Desktop Service or Citrix XenApp Server software. Refer to the steps provided in Direct access of a remote model through Microsoft Remote Desktop Services or Citrix MetaFrame.
3. Perform post-installation tasks for the Modeler Server:
a. Install the latest Maintenance Release, if one has been released. Download the latest Maintenance Release from PTC Support and run the executable file.
b. Use the License Manager Request Wizard to request a license file for the correct version of Modeler, with the correct number of licenses for each component. Once the license has been received from PTC Support, configure Modeler to use the new license. Refer to Working with a server-based floating license.
i. If you have installed the Web Interface, refer to Licensing a Web Interface website and selecting the databases it can access.
ii. If you have installed Model Manager, refer to the Licensing Model Manager section in Installing Model Manager.
c. Set up the Windows firewall. Refer to Post-server only installation tasks.
d. Set up databases. Refer to Post-server only installation tasks.
e. Optionally set up a server to add users and groups through an organizational unit. Refer to Post-server only installation tasks.
f. Optionally set up databases to utilize quad-core processors. Refer to Post-server only installation tasks.
g. Setup a backup procedure. Refer to Setting up a backup procedure.
h. If you have installed Web Interface:
i. Grant the PTC-IM-WSU user account access to every database that you want to be accessed on Web Interface.
|
|
The PTC-IM-WSU user has the modelerappuser server role by default. This user should have Read access to all Modeler databases and all public models should be visible to this user. Also, access to private models should be restricted to access provided by respective model owners. Only a Modeler system administrator can modify the permissions of this PTC-IM-WSU user through Model Explorer.
|
ii. Bookmark databases as PTC-IM-WSU user. Refer to the section called To select which Databases can be accessed from the Web Interface website in Licensing a Web Interface website and selecting the databases it can access.
iii. Complete testing. Refer to Testing and launching a Web Interface website. If the Web Interface is not working, refer to Troubleshooting a Web Interface website.
iv. If the Web Interface is not working, refer to Troubleshooting a Web Interface website.
v. Optionally configure Web Interface user authentication. Refer to Setting up user authentication for a Web Interface website.
vi. Optionally configure Web Interface user account management. Refer to Setting up how Web Interface website accounts work.
vii. Optionally configure HTTPS. Refer to Configuring the Web Interface website to use HTTPS.
4. Perform Client Only installations:
a. On all computers that will host the Modeler Client, complete the steps provided in Performing a client only installation. Select the optional components you require.
b. Specify the SQL Server that will be used.
c. Optionally specify the Floating License Server that will be used by the Modeler Client. Refer to Post-client only installation tasks.
d. If you are using Microsoft Remote Desktop Service or Citrix XenApp:
i. Install the Modeler Client on the Modeler Server using the Client Only installation.
ii. Install the Microsoft Remote Desktop Service or Citrix XenApp Client on all client computers. Refer to the steps provided in Direct access of a remote model through Microsoft Remote Desktop Services or Citrix MetaFrame.
5. Perform post-installation tasks for the Modeler Clients:
a. Install the latest Maintenance Release, if one has been released. Download the latest Maintenance Release from PTC Support and follow the instructions in the included Release Notes.
b. Bookmark databases. Refer to Post-client only installation tasks.
Upgrading a Production – Enterprise Deployment
If you already have Modeler installed using the Product – Enterprise deployment, follow the instructions below to upgrade the Modeler Server then each of the Modeler Clients to the latest version of Modeler.
1. Perform upgrade installation:
a. Refer to Performing an Upgrade. Complete any preparation and installation steps that apply to your upgrade situation.
b. On the Modeler Server, complete the steps provided in Performing a Server Only installation. Select the optional components you require.
c. If prompted to install Microsoft .Net Framework 4.8, click the Install button to confirm.
d. When prompted to uninstall the previous version of Modeler, click Yes to confirm.
e. On all Modeler Clients, complete the steps provided in Performing a Client Only installation. Select the optional components you require.
2. Perform post-upgrade tasks:
a. Refer to Performing an Upgrade. Complete any post-installation steps that apply to your upgrade situation. At a minimum, this will involve upgrading models and profiles in models.
b. Use the License Manager Request Wizard to request a license file for the correct version of Modeler, with the correct number of licenses for each component. Once the license has been received from PTC Support, use the Replace function in License Manager and select the received license file to install the new license. Refer to Working with a server-based floating license.
c. Install the latest Maintenance Release, if one has been released. Download the latest Maintenance Release from PTC Support and follow the instructions in the included Release Notes.