<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! IBM Quick Deployer limitations and known issues <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/updated.png" alt="updated.png" width="50" height="50" align="right"> %DKGRAY% %INCLUDE{"IBMQuickDeployerInsertAuthorBuildBasis"}% %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> ---++ Current limitations * The operating system of all VMs in deployment must be the same. QD does not support mixed OS deployments. * !UrbanCode Deploy agent must run as the root user on Linux and the Administrator user on Windows so all QD scripts will run in this context * LDAP support limited to Tivoli Directory Server * In general, the process cannot be restarted (should always create a snapshot of the VMs before running any !UrbanCode Deploy process) * Only one environment can be connected to a database server; otherwise, name conflicts and !UrbanCode Deploy process concurrency issues can occur * Will not support multiple instances of any application * The context root of the CLM or CE application's URL cannot be changed from the default * All CLM and CE application tags are expected to match the context route of their URL * For Windows deployments, if you select *local* as the installation media type, the local path cannot be a mapped network drive. * Python 2.7.5+ must be installed and included in the system path on the target VMs. Python 3.x is not supported. * If you use Oracle 12.1, you must use the 12.1.0.1 ojdbc7.jar. If you use the 12.1.0.2 ojdbc7.jar, you receive an error message when you run the repotools -createTables command. For additional information, see [[http://www-01.ibm.com/support/docview.wss?uid=swg21990430][repotools -createTables command fails with ORA-01000 on Oracle 12]]. ---++ Known issues * In CLM 6.0 scripted JTS Setup fails intermittently when attempting to register TRS providers with LQE. If this happens then JTS Setup will need to be completed from the web UI at ../jts/admin. * The *Install Applications* process fails when you try to install CLM by using an FTP media server. The workaround is to install CE instead. * You must set the default user and LDAP parameters before you run the *Install Applications* process. You can do this by entering values in the userCreds.properties and ldap.properties files before you run the [[IBMQuickDeployerInstallingIntoUCD][installer]]. Alternatively, you can run the Change Default User Parameters and Change Default LDAP Parameters processes. * DB2 user name restrictions are not enforced by the Change Default User Parameters process * If the Windows response time is slow, the Oracle installation might fail. The default total wait time is 60 minutes; after that, it exits with a failure. You can increase the number of tries or the interval wait time in function *post_windows_install* of the file Database/InstallOracle/install_oracle.py. * The Rational Requirements Management (RM) Converter application that renders the read-only view of RM graphical artifacts is installed but not configured. There was an issue discovered when deployed on RHEL 7+ so the war file will be present on the server but will not be configured in the !WebSphere Application Server. Read tech note [[https://jazz.net/library/article/1089][Requirements Management (RM) Converter application configuration and troubleshooting guide]] for detailed configuration instructions. * The sample ldap.properties file includes quotes in the *ldap primaryid* and *primaryid_Password* values. When you edit the file to specify your LDAP settings, remove those quotes. For example: * Before: * jazz_ldap_primaryid="_LDAP_ADMIN_USER_" * jazz_ldap_primaryid_Password="_LDAP_ADMIN_PASSWORD_" * After: * jazz_ldap_primaryid=_LDAP_ADMIN_USER_ * jazz_ldap_primaryid_Password=_LDAP_ADMIN_PASSWORD_ %INCLUDE{"IBMQuickDeployerInsertMiscellaneous"}% <sticky></div></sticky>
This topic: Deployment
>
WebHome
>
DeploymentInstallingUpgradingAndMigrating
>
IBMQuickDeployer
>
IBMQuickDeployerLimitationsKnownIssuesV20
History: r13 - 2017-12-11 - 19:20:42 - Main.ktessier
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.