Quick Deployments
Report
Randy602049Follow
Mar. 30, 2023•0 likes•87 views
0 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Check these out next
Quick Deployments
Mar. 30, 2023•0 likes•87 views
0 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Download to read offline
Report
Presentations & Public Speaking
In this presentation, you will learn how to build a Quick Deploy XML for Deployment Center (DC). And to validate your XML using an XSD to reduce the number of iterations. Ensuring you have no errors, find syntax errors, or even identify a severe error, usually with a recommendation on how to fix it! - A Quick Deploy XML can be used to create and install a new environment in DC. - Validate the XML using an XSD before running it. - Reduce the number of iterations while building the XML. A complete method.
Randy602049Follow
Recommended
Jump-start your application migration to AWS with CloudEndure - STG305 - New ...Amazon Web Services
How to build a cloud adapterMaarten Smeets
How to build a Oracle cloud adapter SOA, Integration & API'sGetting value from IoT, Integration and Data Analytics
Connect 2013 show101 making ibm traveler high available_part2_extending and s...a8us
Innovate 2014: Get an A+ on Testing Your Enterprise Applications with Rationa...Teodoro Cipresso
IBM Datapower Gateways - Devops with UrbanCode DeployJared Putman
Quick Deployments
- WELCOME Join the transformation Las Vegas, May 9-12, 2022
- Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- REALIZE LIVE 2022 Quick Deployments Join the transformation Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- Agenda In this session, you will learn how to build a Quick Deploy XML for Deployment Center. And to validate your XML using an XSD to reduce the number of iterations. Ensuring you have no errors, find syntax errors, or even identify a severe error, usually with a recommendation on how to fix it! • A Quick Deploy XML can be used to create and install a new environment in DC. • Validate the XML using an XSD before running it. • Reduce the number of iterations while building the XML. A complete method. Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- Presenters Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Randy Ellsworth
- Why Quick Deploy? Show of Hands... Who has used Deployment Center? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- Why Deployment Center? Why Quick Deploy? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Deployment Center is a centralized web application for deploying software to Teamcenter environments, both servers and clients. It simplifies the process of installing and updating software and automates deployment. You can manage a variety of Teamcenter environments more efficiently. Download software packages to a central location, set up your installation or update in Deployment Center, and generate deployment scripts. Run the scripts on target machines that access and install the software. Benefits • Deploy, manage, and maintain multiple versions of software in multiple Teamcenter environments from a single web application with authenticated user access. • Reduce the costs of managing Teamcenter environments by reducing the number of steps and time involved in software deployment. • Provide a centralized location to create and view Teamcenter environments and view deployment information. • Ensure consistency and accuracy by reviewing and adjusting deployment configuration before rollout to Teamcenter environments. • When setting up your environment, take advantage of entering parameters for one component and having those values shared with related components. For example, when you enter a machine name or port number for a component, that information is shared with other components that require the same information.
- Environments: All-in-One, Single Server, or Distributed? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Deployment Reference Architecture https://support.sw.siemens.com/en- US/product/282219420/download/ PL20211204580108043
- Teamcenter Deployment Reference Architecture Sample QD Files Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Quick Deploy configurations are provided for both wntx64 and lnx64
- Download a OpenJDK Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Download Azul Zulu Builds of JRE (optionally, JDK) https://www.azul.com/downloads/?version=java-11-lts&os=windows&architecture=x86-64-bit&package=jre 1 2 3 4
- Install OpenJDK Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Install Azul Zulu 11 and set JAVA_HOME In the Custom Setup dialog, Click Set JAVA_HOME variable and select Entire feature will be installed on local hard drive then click Next and Install. 1 2 3 4 C:Program FilesZulu
- Installing Deployment Center Show of Hands... Who has installed Deployment Center? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- Stage the Software Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Download and extract DeploymentCenter_4.2.1 to C:Temp https://support.sw.siemens.com/en- US/product/282219420/download/ PL20220314275597017 1 2 3 4
- Launch a Command Prompt Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Run as administrator Run an “Administrator: Command Prompt” and view the utility Help
- Open the Installer Config File Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Open in your favorite editor Open C:TempDeploymentCenter_4.2.1deployment_centerinstall_config.properties
- the password must not contain any of the following characters: ! @ $ % = & ' " ^ : ; . _ < > ( ) { } Generate Encrypted Passwords Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Best Practice: Use encrypted passwords cd /d C:TempDeploymentCenter_4.2.1deployment_center dc_encrypt.bat -password=dcadmin Cleartext password 14pXjKcFG8CIrbjdy1teV5JWJY/aVc7tj6BgDCQ3 abiAJjZ4GWdFbV3MI0e+jSPhN2R+W6RPS/dd3 YxENZFX/A== cd /d C:TempDeploymentCenter_4.2.1deployment_center dc_encrypt.bat -password=dcadmin -file=dc.pwf Save for later SHA256
- Zulu-11 JDK versus Zulu-11 JRE Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 JDK Fix - C:TempDeploymentCenter_4.2.1deployment_centerdc_encrypt.bat if not exist "%JAVA_HOME%jre" Add quotes C:Program FilesZulu JRE JDK
- Edit Install Config Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Edit install_config.properties and Save As acme_install_config.properties enableSoftwareAnalytics=No serverDir=C:SiemensDCwebserver serverPort=8180 serviceName=Teamcenter_DC_Service repoDir=C:SiemensDCrepository repoPort=8190 repoServiceName=Teamcenter_DC_RepoService repoPublisherPort=8181 repoSubscriberPort=61616 user=dcadmin password=14pXjKcFG8CIrbjdy1teV5JWJY... useEncryptedPassword=true useHttpsCommunication=false
- Install Deployment Center Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Run the installer using the config file cd /d C:TempDeploymentCenter_4.2.1deployment_center deployment_center.bat -install -inputFile=.acme_install_config.properties
- Validate the Installation Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 http://localhost:8180/deploymentcenter/
- Tour the Installation Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Post repository tasks repositorysystemdeployer C:SiemensDC Teamcenter_DC_ReportService Manages scanning of software Teamcenter_DC_ReportService_Publisher Watches for new software to scan Teamcenter_DC_Service Runs DC web app
- Populate the Repo Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Add software to the repository repository repositorysoftware webserverrepotoollogs
- Generate Software Configuration Report Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Generate a Software Configuration Report for the software in the repository 1 2 3 4
- Backup the Installation Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Backup and Recovery webserverdb repository Software must be recovered to the same location
- Install Quick Deploy Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Extract to DC_ROOT webserveradditional_tools C:SiemensDC
- Building the Quick Deploy XML Show of Hands... Has anyone customized a Quick Deploy XML? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- Export Full versus Export Lean Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Export the XML from the DC UI or using the QD utility dc_quick_deploy.bat -dcurl=http://acme:8180/deploymentcenter/ -mode=export -environment=TC4ACME -exportType=Full (or Lean) -exportFile=.acme_quick_deploy.xml -dcusername=dcadmin -dcpasswordFile=.dc.pwf Full Export or Lean Export Rename the export file after export from the DC UI to avoid overwriting. Warning! Passwords are not exported.
- Validate the Install Path Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 DC 4.2 now includes an Install Path column
- Export the Environment Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Export a QD XML from the DC UI 1 2 3 4 Rename the file after export from the DC UI to avoid overwriting. Passwords are not exported.
- Remember the Encrypted Passwords! Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Best practice: Use encrypted passwords in your QD XML dc_quick_deploy.bat -encrypt=ospassword Cleartext Passwords are always encrypted in the DC database. Encrypted : true Encrypted : false DC now supports HTTPS!
- Review the XML File Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Exported Quick Deploy XML
- Software Configuration Reports Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Configuration Report for Active Workspace 6.0.1 • Teamcenter_ActiveWorkspace_6.0.1.html • Teamcenter_ActiveWorkspace_6.0.html • Teamcenter_Foundation_13.3.html • Teamcenter_Foundation_13.html • Teamcenter_Foundation_14.0.html • Teamcenter_MicroServiceFramework_6.0.1.html
- Review the Software Configuration Report Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Media Information, List of Applications, List of Components, ConnectedTo Teamcenter_ActiveWorkspace_6.0.html
- Building the Configuration Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 quickDeployConfig, archType, quickDeploySoftware, and quickDeployClients
- Install BMIDE Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Business Modeler IDE Standalone
- BMIDE Component in QD XML Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Component for BMIDE
- Mass Deploy TCCS Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Mass Deploy for TCCS-Only LB LB FO
- Mass Deploy TCCS in QD XML Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Mass Deploy for TCCS-Only with Fail-Over and Load Balancing LB LB FO
- Install the Rich Application Client Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Install a 4tRAC or 2tRAC, combined 2t4tRAC is not supported in DC. Same Machine Name Same Machine Name 1 2 3
- Mass Deploy 4tRAC Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Mass Deploy for 4tRAC
- Mass Deploy 4tRAC in QD XML Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Mass Deploy for 4tRAC
- Mass Deploy BMIDE Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Mass Deploy for BMIDE
- Mass Deploy BMIDE in QD XML Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Mass Deploy for BMIDE
- Validating an XML Show of Hands... Has anyone validated an XML using an XSD? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- How do I find the XSD? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Drag and Drop C:SiemensDCwebserverwebserverjetty_9.4.43webappsdeploymentcenter.war WEB-INFlibdc_quick_deployjarcom.dc.common.jar comsiemensdeploymentcentermodelquickdeployschemadc-quickdeploy.xsd C:SiemensDCdc_quick_deploy
- A quick look at dc-quickdeploy.xsd Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Use this XSD to validate that your XML is well-formed and will not cause issues in DC. High level process... • Open Plugins Admin and Install XML Tools in Notepad++. • Open the XML document that you want to validate. • Click on the Plugins > XML Tools > Validate Now option. • Browse and select an XSD file to validate the XML.
- Install the XML Tools Plugin Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Launch Notepad++, click Plugins and Plugins Admin..., click XML Tools and Install 1 2 3 4 5
- Validate the XML Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Open the XML document that you want to validate. Click Plugins, XML Tools and Validate Now 1 2 3
- Select the XSD Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Select dc-quickdeploy.xsd and click OK. 1 2
- Error Detection Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 You will either get “No errors detected.” Or a syntax error (missing closing bracket).
- Severe Error with Recommendation! Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Or a more severe error with a suggestion on how to fix it!
- Create an Environment Show of Hands... Has anyone used a Quick Deploy XML to create an environment? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- Iterate Template Version in DC Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Iterate the software version before adding package to the DC repo Iterate! Build version is optional template-internal-name_OS_template-version_build-version_YYYY_MM_DD_HH-MM-SS
- Validate DC Command Line Switches Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Review QD help dc_quick_deploy
- Create an Environment in DC and Build Scripts Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Run QD using the XML dc_quick_deploy.bat -dcurl=http://acme.com:8180/deploymentcenter/ -environment=TC4ACME -inputFile=.acme_quick_deploy.xml -dcusername=dcadmin -dcpasswordFile=.dc.pwf repositorydeploy_scripts skipScriptGeneration
- Deploy the New Environment Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 Copy and unzip the deploy package locally before running deploy.bat -dcurl=http://acme:8180/deploymentcenter/ -dcusername=dcadmin -dcpasswordFile=Z:dc_quick_deploydc.pwf -softwareLocation=Z:repositorysoftware -diagnosticChecks deploy.bat -dcurl=http://acme:8180/deploymentcenter/ -dcusername=dcadmin -dcpasswordFile=Z:dc_quick_deploydc.pwf -softwareLocation=Z:repositorysoftware Fix issues E:Tempdeploy_ACMECORP1
- Troubleshoot the Deployment Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 See logsdeployer_timestamp.log, section Diagnostic Checks Detail logs Check directories... • TC_ROOTlogs • TEMP
- What’s Next... Show of Hands... Has anyone automated their deployment process? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
- What are my next steps? Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022 CI/CD Orchestration Mass Client Deploys Software Configuration Report Patch Upgrade send_configuration_to_dc Install Andrew Blainey (andrew.blainey@siemens.com)
- THE TIME IS NOW Join the transformation Accelerate your journey by leveraging the Quick Deploy XML Restricted | © Siemens 2022 | 2022-05-09 | Randy Ellsworth | Quick Deployments | Northrop Grumman | Realize LIVE 2022
Editor's Notes
- Note: TEM is deprecated (Tc13.2 May 2021) and will be removed in Teamcenter 15 (obsolete).
- Let’s get some preliminary steps out the way... What kind of architectures can Deployment Center build... An “All-in-One” environment includes the database software on the same server. A “Single Server” environment has the database software on a separate server but all the Teamcenter components on the same server. A “Distributed” environment separates the Teamcenter components across multiple servers for performance, scalability and can include even redundancy. Ref: Teamcenter_Deployment_Reference_Architecture_DC4.2_v1.pdf
- There are several Quick Deploy configurations provided with the Teamcenter Deployment Reference Architecture. The term “Multitier” is the same as “Distributed”.
- See SFB-TEAMCENTER-8016820 (an update to SFB-TEAMCENTER-8015506). Download and install Zulu 11 JRE... Select Java Version: Java 11(LTS) Select Operating System: Windows Select Architecture: x86 64-bit Click .msi button Change Java Package: JDK Click .msi button (for later installations)
- Install Azul Zulu 11 by right-clicking the MSI and selecting “Install”. You can validate that the install is correct by opening C:\Program Files\Zulu\ in Windows Explorer and that the JAVA_HOME System variable is set correctly. Tip: Remove the appended “\“ and also set JRE_HOME and JRE64_HOME to the same value. These variables will be available after the next reboot.
- Download the software from Support: https://support.sw.siemens.com/en-US/product/282219420/download/PL20220314275597017 Extract and stage the software in C:\Temp
- Find “cmd”, Rclick and select “Run as Administrator” - required since you will be modifying the system by installing services. Note: A JDK and setting JAVA_HOME is required to run DC. In the command prompt... cd /d C:\Temp\DeploymentCenter_4.2.1\deployment_center deployment_center.bat -h This will let you know that everything is ready, and you can begin the installation. Notice all the switches that are available for “-install”?
- An easier way to install DC is using the install_config.properties file. It contains most of the switches available on the command line. Rather than typing all the switches and values, which you can do, modify this file to make the process repeatable. Open install_config.properties in your favorite editor (Visual Studio Code or Notepad++ are recommended). Note: For those who had their hand up, open upgrade_config.properties.
- In the install media, C:\Temp\DeploymentCenter_4.2.1\deployment_center... Use a password file when running utilities. dc_encrypt -password=dcadmin -file=dc.pwf Save dc.pwf wherever you need it, for instance, C:\Siemens\DC\dc_quick_deploy\dc.pwf. Use encrypted passwords in your QD XML’s to prevent others from discovering them. e.g., ps -ef on Linux. dc_encrypt -password=dcadmin Use in these utilities: deployment_center.bat -maintenance can also update an existing password later. send_configuration_to_dc deploy dc_quick_deploy can also generate encrypted passwords.
- If you are installing the Active Workspace Client Builder, JAVA_HOME must be set to the Java JDK location. Normally, you install the JRE for use with Deployment Center. However, if you install a JDK then line 17 fails and skips to line 21 which appends “jre” to JAVA_HOME which does not exist with the JDK. Add quotes around %JAVA_HOME%\jre to resolve this error.
- Edit install_config.properties... enableSoftwareAnalytics=No (If you are a government contract otherwise “Yes”). Enable later using http://dc_server:port/deploymentcenter/rest/softwareanalytics/updatesoftwareanalytics?enabled=true serverDir=C:\\Siemens\\DC\\webserver (I remove spaces in the installation PATH and install under the vendor's name). serverPort=8180 (8080 is the default port for many web servers). serviceName=Teamcenter_DC_Service (Add “Teamcenter_” so this service sorts with the rest of your Teamcenter services). repoDir=C:\\Siemens\\DC\\repository (Keep the same “root” installation folder if possible). repoPort=8190 (8090 is the default port for Microservices). repoServiceName=Teamcenter_DC_RepoService (Add “Teamcenter_”). repoPublisherPort=8181 (8081 does not have a conflict that I’m aware of but staying with the same port range). repoSubscriberPort=61616 (no change). user=dcadmin (no change). password=dcadmin (no change). useEncryptedPassword=false (no change). useHttpsCommunication=false (no change). Save the file. You do not need to rename the file, but it is recommended that you follow the best practice by not modifying OOTB files (unless you must - explained later).
- Use the properties file created earlier to install DC. Back in the administrator command prompt... deployment_center.bat -install -inputFile=.\acme_install_config.properties The installation will pause for a while on [Step 8 of 12]. Be patient. Review the “\logs\deployment_center_debug_<datetime>.log” if you encounter errors (or are just curious). Note: The DC utilities have moved.
- Launch your Browser (Chrome recommended)... Enter the address: http://localhost:8180/deploymentcenter/ Enter the Username Enter the Password Click Sign In
- Remember the osUserName* and osUserPassword* settings in the install_config.properties file? I don’t normally change them in the file because I want to change the third “Publisher” service too. Not required. Common modifications to a standard “Deploy” can be made in \system\deployer\deploy.bat. This deploy.bat is basically the template for the ones generated in deploy_scripts.
- Populate the \repository\software\ directory with all the software that will be used in your environment or your Quick Deploy will fail. Tip: Stop the Teamcenter_DC_RepoService and Teamcenter_DC_RepoService_Publisher services before pasting software into the repository. Remember to unzip the software. Review the \webserver\repotool\logs\* for scanning issues if the software does not appear in the Software Repository.
- These reports used to be delivered with the DC software but do not exist in DC 4.2.1. After populating the software repository and starting the services, log into DC and click “Software Repositories”. Notice that the “Configuration Report” column shows “Not Generated” on every row. Select a Row and the “Generate Software Configuration Report” icon will be shown. Click the icon to generate the report. You will need to refresh, then a “Download Report” hyperlink is shown. The actual reports reside in the \webserver\report\ directory. Repeat for all the software in the repo.
- Stop the services. Backup the db files and software directory content. Start the services.
- Extract \webserver\additional_tools\dc_quick_deploy.zip to a known location for later. e.g. DC_ROOT\dc_quick_deploy\ Note: The send_configuration_to_dc.zip can be uploaded to servers in any preexisting environments that contain TEM that you want DC to manage.
- A Full Export includes all possible component properties (Checked). A Lean Export will only include required or changed default properties (Unchecked). A “lean” XML is about half the size.
- Cool new feature, the Install Path column. Now supports installing components: Teamcenter Security Service Session Agent Teamcenter Management Console
- Select the Environment Click Export Environment Check Export all component properties Click Export
- Use encrypted passwords in your QD XML. The dc_quick_deploy utility can also encrypt passwords, not just dc_encrypt.bat. When the value is encrypted, ensure that encrypted=“true”. When the value is in cleartext then encrypted=“false”. Passwords are always encrypted when imported into the DC. HTTPS works with: send_configuration_to_dc deploy dc_quick_deploy
- Leverage the Software Configuration Report to build your own QD XML. The “Type” (Environment Type) can be set but has no hidden functionality. The “Site Name” cannot be set (future addition). The “configName” in the XML does not have any effect (used for Mectronics) which is why the “-environment” switch is still required on the command line.
- Review the Software Configuration Report to build your own QD XML.
- Practice creating environments in the DC UI and “Export Full” until you understand all the properties needed. Then you can start manually creating/changing your QD XML’s. The “Client” tag accepts “Component” tag id’s.
- The advantage of installing the standalone BMIDE is that you get the template selection for free.
- Unlike RAC, the standalone BMIDE requires TCCS. Create a mass deploy for the developers configuring the data model. Note: You can also create a combined 4tRAC/4tBMIDE by using the same name, 4tRACBMIDE, to combine the features into a single mass deploy.
- Several MCAD support embedded AWC but require TCCS be installed. Enable Client Communication System. Shared. FSC, Override Connection, Set Priority to the same value for “Load Balancing” Set to higher value for “Fail Over”.
- Several MCAD support embedded AWC but require TCCS be installed. Enable Client Communication System. Shared. FSC, Override Connection, Set Priority to the same value for “Load Balancing” Set to higher value for “Fail over”.
- Combining the 4tRAC and 2tRAC by using the same Machine Name results in an error. You cannot install the combined 2t4tRAC using DC 4.2.1. Use TEM to install the combined 2t4tRAC then “send_configuration_to_dc”. I did not try this so you are on your own here - might not be supported. Warning! Click “Remove” and not “Delete”.
- Some functionality has not been ported to AWC yet and will require the RAC. Create a mass deploy for these situations.
- Some functionality has not been ported to AWC yet and will require the RAC. Create a mass deploy for these situations.
- Support your developers!
- Unlike RAC, the standalone BMIDE requires TCCS. Create a mass deploy for the developers configuring the data model. Note: You can also create a combined 4tRAC/4tBMIDE by using the same name, 4tRACBMIDE, to combine the features into a single mass deploy.
- A big THANK YOU to Bob Donovan! There is no need to edit or redeploy the JAR file. So far, these files have been added to the dc_quick_deploy directory. In DC 4.2.1, find it here: C:\Siemens\DC\webserver\webserver\jetty_9.4.43\webapps\deploymentcenter.war \WEB-INF\lib\dc_quick_deploy\jar\com.dc.common.jar \com\siemens\deploymentcenter\model\quickdeploy\schema\dc-quickdeploy.xsd
- This XSD will be used to validate your XML. There are some powerful tools available for purchase that can validate that your XML is well formed, like Altova’s XMLSpy XML Validator. XMLSpy is not just for validating XML but also used for JSON and WSDL too. Although I use the free Visual Studio Code editor, most folks use Notepad++ so I’ll use it in this example.
- In the Plugins Admin window, you will see a list of available plugins that you can enable or disable whenever you want. Also, it shows the plugins that you have installed and for which updates are available. Select the XML Tools plugin and click Install. Notepad++ will have to exit and restart to install the plugin. Click the Yes button.
- I would not have found this without help from Bob Donovan!
- No error detected. Please fix xml syntax first.
- Sever erro with recommendation.
- Tip: In BMIDE, Generate Software Package dialog, ensure to iterate the Software Version (optionally, the Build Version) before adding the custom template to the software repo in DC. DC will not deploy the template unless the version is higher than previous deployments.
- Command Prompt… cd /d C:\Siemens\DC\dc_quick_deploy\ dc_quick_deploy.bat -help Note: "-h" fails, must use "-help".
- Use skipScriptGeneration until you are ready. Use generateScripts to force the generation of deploy scripts. Use override to make minor changes to an existing quick deploy configuration.
- Troubleshooting: Find the path to log files are listed in deployer_timestamp.log (Diagnostic Checks Detail). Also check TC_ROOT\logs and TEMP directories for additional clues. Bonus: debug send_configuration_to_dc using... tem_config_scanner_error_timestamp.log, scanning operation failures. tem_config_rest_service_timestamp.log, communication between this util and Deployment Center.
- Learning pipeline: Deployment Center Quick Deploy Deploy Automation Deploy Automation pipeline: Quick Deploy (using a config file to generate deploy scripts) Deployment Center Dev Ops Tool (coordinates activities) https://docs.sw.siemens.com/documentation/external/PL20201019171727925/en-US/dc_videos/deployment_center/4.1/dc_videos/common/en_US/graphics/graphicLibrary/videos/dev_videos/sample_files/DC_3.1_sample_files.zip \DeployAutomationExamples\Jenkins\ BuildAndDeployCustomSoftware InstallNewAndUpdate InstallNewTeamcenterEnv ScanAndUpdateEnv