Edit
Attach
P
rintable
r35 - 2017-07-28 - 21:38:17 - Main.ktessier
You are here:
TWiki
>
Deployment Web
>
DeploymentInstallingUpgradingAndMigrating
>
IBMQuickDeployerOld
>
IBMQuickDeployerLimitationsKnownIssuesOld
<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 * !UrbanCode Deploy agent must run as the root user and all scripts run as the root user * 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 ---++ 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. * If the SCP utility fails to copy files from the IHS server to any of the WAS servers then the QD script that runs SCP may fail without an error. * User must always run the Change Default User Parameters and Change Default LDAP Parameters process on each environment before running the Install Applications process. However, now the user can save their parameters for future use by following - [[IBMQuickDeployerUpdatingSystemPreReqParametersOld][Updating the Rational_QD_SystemPre-Requisite_60x* component]] * DB2 user name restrictions are not enforced by the Change Default User Parameters process * 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. * Under very specific conditions running a command as the db2inst1 user from within a UCD process can stop the DB2 database server when the UCD process step completes. We have seen this happen under the following conditions. For more details see section [[IBMQuickDeployerLimitationsKnownIssues#DB2_stopped_examples][DB2 stopped examples]]. * The OS where the DB2 database server runs is RHEL 7.x * The Rhapsody/DM prerequisites and their dependencies have been installed * The UCD agent on the DB2 database server machine is running as a service instead of from the command line ---++ DB2 stopped examples * Example 1 * The QD UCD application process Install Applications is used to install the full package including DB2 * The DBA needs to perform maintenance on the DB2 database server from the command line so the database is stopped and then started from the command line * Sometime later a process is run from UCD that does an su to the db2inst1 user and executes a command * The DB2 database server process will be stopped when the UCD step completes * Example 1 workaround * Either do not use UCD to manage the DB2 database server after the initial deployment or run the UCD agent on the DB2 database server machine from the command line and not as a service. * Example 2 * The QD UCD application process Install Applications is used with a customer supplied DB2 database server. * If the DB2 database server process was started from the command line then it will be stopped after the Create Database DB2 step of the Install Applications process and the process will fail later on the Configure App step. * Example 2 workaround * The UCD agent on the DB2 database server machine must be run from the command line and not as a service. %INCLUDE{"IBMQuickDeployerInsertMiscellaneous"}% <sticky></div></sticky>
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r36
<
r35
<
r34
<
r33
<
r32
|
More topic actions...
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
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
.