vwhpv - micro focus · /hjdoqrwlfhv:duudqw\ 7kh rqo\ zduudqwlhv iru surgxfwv dqg vhuylfhv ri 0lfur...
TRANSCRIPT
-
odar1
-
odar 1 )
-
Troubleshooting Guide
odar 1
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 1
1. Codar Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Codar Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.1 On every navigation to a page that uses Adobe Flash Player, Chrome reloads the SWF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1.2 Communication error in Firefox when Use system proxy setttings is enabled . . . . . . . 41.1.3 Internet Explorer Enhanced Security Configuration interferes with the Codar Console 51.1.4 Attempting to add a valid approver fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1.5 Unable to log on to the Codar Console after installation when Single Sign-On is configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1.6 Various issues when logging into the Codar Console using multiple browsers . . . . . . . 71.1.7 A user cannot be searched in the Codar access control . . . . . . . . . . . . . . . . . . . . . . . . 71.1.8 Design not listed when access control added to any design in PLM . . . . . . . . . . . . . . . 81.1.9 Modified Group name not listed in Access Control Group Search . . . . . . . . . . . . . . . . 81.1.10 Packages are stuck in 'In Transition' state even though the OO flows are complete in OO
Central . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Codar Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.1 Non-English characters are not stored properly in Oracle . . . . . . . . . . . . . . . . . . . . . . . 101.3 Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.1 Cannot enable the load balancer host in the PostgreSQL database . . . . . . . . . . . . . . . 101.3.2 Codar installation hangs with no error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.3 Content upload not successful during Codar Installation . . . . . . . . . . . . . . . . . . . . . . . 111.3.4 Enable HTTPs traffic logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.5 Failed to execute Codar installer on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.6 Failure to install Codar on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.7 IDM deployment fails with ClassNotFoundException: com.hp.hpsso.HpSsoContextListener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.8 Installation fails because Codar cannot execute the bzip2 command . . . . . . . . . . . . . . 151.3.9 Installation fails with SQL errors in the install.log file . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.3.10 Multiple JDBC drivers exist for Oracle in the provided directory . . . . . . . . . . . . . . . . . 161.3.11 Multi-tier sequential designs failing with Operations Orchestration (OO) 10.20 . . . . . 171.3.12 Operations Orchestration (OO) upgrade fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.3.13 Performance issues while importing large archives . . . . . . . . . . . . . . . . . . . . . . . . . . 181.3.14 Tips for installing and configuring Codar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.3.15 Uninstallation did not finish successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.4 Miscellaneous issues and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.4.1 About the Codar support tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.4.2 Application deployment fails using some partial designs . . . . . . . . . . . . . . . . . . . . . . . 221.4.3 Clicking on action name for CMP Service action pops up a new login window . . . . . . . 221.4.4 Codar fails with a JDBC rollback error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.4.5 Error while publishing a topology design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.4.6 Error while updating sequential service design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.4.7 On a fresh install of Premium, the release pipeline view is blank for the Sequence Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.4.8 Response time is 20 to 30 seconds when fetching and displaying error message for non
valid CMP provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.4.9 REST API - Cannot create property names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.4.10 Triggering a build from TFS fails with error "Could not find the Design for the version" . . 1.4.11 User authorization fails if the base domain name of an organization is modified during a
user session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.4.12 When a custom action runs for a long duration (typically > 4 hours) , the package is found
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 2
in “transition” state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.4.13 While creating or updating package properties through the API, only the property values
are modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.4.14 Windows command-line commands do not get executed . . . . . . . . . . . . . . . . . . . . . . 28
1.5 Application-Level Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.5.1 An application design JSON cannot be exported and then imported into another Codar
application instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.5.2 Application packages get stuck in the transition state forever . . . . . . . . . . . . . . . . . . . . 291.5.3 Design versions of the container are in the locked state . . . . . . . . . . . . . . . . . . . . . . . . 291.5.4 User is unable to create application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.5.5 User is unable to delete application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.5.6 User is unable to delete custom roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.5.7 User is unable to delete default roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.5.8 User is unable to promote application package from one stage to another . . . . . . . . . 321.5.9 ‘Default lifecycle stage’ is not reflecting while creating a new application version. . . . . 321.5.10 ‘Run Security Scan’ gate action with ‘component property’ parameter fails. . . . . . . . . 33
1.6 Connection Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.6.1 Failed to open HTTP connection; failed to Get resource; exploration of OO flow run
execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.6.2 Page Not Found error when running the Pet Clinic out-of-the-box design . . . . . . . . . . 341.6.3 The Pet Clinic application deployment fails for the MySQL component . . . . . . . . . . . . 35
1.7 Integration Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351.7.1 ALM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.7.1.1 When there is a TestSetAction and Multiple Packages Promoted simultaneously, some packages stay in TRANSITIONING state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.7.2 Amazon Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361.7.2.1 An AWS instance cannot be reached using its public IP address . . . . . . . . . . . . . 371.7.2.2 Attaching the network interface to the server fails . . . . . . . . . . . . . . . . . . . . . . . . . 371.7.2.3 AWS provider validation fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381.7.2.4 Test run fails when more than one network interface is connected to a single AWS
server in the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381.7.2.5 The public IP address of the AWS server instance is not visible . . . . . . . . . . . . . . 391.7.2.6 Unable to provision the server because of difference between access point and zone
specified in the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391.7.3 Bamboo integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401.7.4 Chef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.7.4.1 Chef integration does not work when the Chef server tries to access provisioned VMs using SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.7.4.2 Failed to register new client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411.7.5 Docker Universal Control Plane - DOCKER UCP DATA CENTER . . . . . . . . . . . . . . . . 421.7.6 Helion OpenStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
1.7.6.1 Helion OpenStack - Cloud Service fails to create an instance . . . . . . . . . . . . . . . 421.7.7 Operations Orchestration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.7.7.1 Codar Operations Orchestration content not reflected in OO . . . . . . . . . . . . . . . . 441.7.7.2 Failure in trust store setup causes login lockouts . . . . . . . . . . . . . . . . . . . . . . . . . 441.7.7.3 javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException:
PKIX path building failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451.7.7.4 OO flow is not validating "docker run" arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.7.5 Timed out error when provisioning parallel servers for OOTB Sequenced Designs . . 461.7.7.6 Trust store setup failure leads to login lockouts . . . . . . . . . . . . . . . . . . . . . . . . . . . 481.7.7.7 ValidatorException javax.net.ssl.SSLHandshakeException . . . . . . . . . . . . . . . . . 49
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 3
1.7.7.8 Workflows in the Operations Orchestration public repository are invalid . . . . . . . . 491.7.8 SiteScope (Codar) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1.7.8.1 SiteScope monitor creation fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501.7.8.2 SiteScope monitor deployment fails with an error in OO reporting . . . . . . . . . . . . 51
1.7.9 VMware vCenter (Codar) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511.7.9.1 Cannot provision VMware vCenter server component . . . . . . . . . . . . . . . . . . . . . 521.7.9.2 Lifecycle Engine does not allow another lifecycle transition to begin if the vCenter Add
Server fails with timeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521.7.9.3 vCenter provision server fails when a specified cloned template is not present in the
given datacenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531.7.9.4 VMware vCenter customization template is missing . . . . . . . . . . . . . . . . . . . . . . . 53
1.8 Codar on the Linux platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541.8.1 Codar service fails to start or stop with an unrecognized service error on Ubuntu . . . . 541.8.2 Codar service startup fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551.8.3 Command not found error when the Codar service script is executed . . . . . . . . . . . . . 551.8.4 Embedded Operations Orchestration cannot be launched after rebooting the Linux server 561.8.5 Error when the content archive tool runs against an unsupported version of Codar . . . 561.8.6 psql error when connecting to the PostgreSQL database using the psql command . . . 57
1.9 Topology Design Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571.9.1 Amazon Server component fails to provision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581.9.2 Associating a floating IP address does not work using an internal network . . . . . . . . . 581.9.3 Cannot import Chef components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591.9.4 Codar 1.7 - Cannot execute a test run of a topology design in Codar . . . . . . . . . . . . . . 601.9.5 Deployment fails in the Check node step in Chef 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . 601.9.6 Failed to load SA Policies in Codar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611.9.7 Importing topology designs does not automatically add missing component relationship
definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621.9.8 Import of topology component of custom provider type does not work . . . . . . . . . . . . . 631.9.9 No IP addresses are listed when executing an Assign Floating IP public action using a new
Helion OpenStack setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631.9.10 OOTB Sequenced Design with Option Model does not work with Codar License . . . 651.9.11 Test run fails while using a topology design based on Server Automation software policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651.9.12 vCenter Server component fails to provision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
1.10 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661.10.1 Codar licensing UI issue with Chrome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671.10.2 License cannot be installed in cluster mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671.10.3 Relevant message not displayed when an expired emergency license is reinstalled . 68
1.11 Support Tool for Codar - Information and Instruction Page . . . . . . . . . . . . . . . . . . . . . . . . . 681.12 Codar Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1.12.1 "Overwrite Existing File" dialogue box appears during Codar upgrade. . . . . . . . . . . . . . . 1.12.2 Codar with MS-SQL- Application throws exception in Application’s list page . . . . . . . 691.12.3 HA upgrade fails with ‘Codar 1.80 Patch1’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701.12.4 Unique Constraint issue in Codar with Oracle database . . . . . . . . . . . . . . . . . . . . . . . 70
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 4
Codar Troubleshooting
This guide contains some issues that you may encounter when using Codar and workarounds totroubleshoot these issues.
Codar Console
On every navigation to a page that uses Adobe Flash Player, Chrome reloads the SWF file
Communication error in Firefox when Use system proxy setttings is enabled
Internet Explorer Enhanced Security Configuration interferes with the Codar Console
Attempting to add a valid approver fails
Unable to log on to the Codar Console after installation when Single Sign-On is configured
Various issues when logging into the Codar Console using multiple browsers
A user cannot be searched in the Codar access control
Design not listed when access control added to any design in PLM
Modified Group name not listed in Access Control Group Search
Packages are stuck in 'In Transition' state even though the OO flows are complete in OO Central
On every navigation to a page that uses Adobe Flash Player, Chrome reloads the SWF file
Problem: Chrome reloads SWF on each navigation to a page that uses Adobe Flash Player
Symptoms When accessing the Codar Console in Chrome,areas that use an SWF file (includingOrganizations and manyareas under Designs) reload on every usernavigation to the area.
Primary software component Codar Console
Failure message N/A
Probable cause Chrome reloads an SWF file from an HTTPSwebsite if the SSLcertificate configured for that site is not trusted bythe browser.
Solution
Configure a CA-signed certificate for use with Codar, as described in the .Codar Configuration Guide
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 5
Communication error in Firefox when Use system proxy setttings is enabled
Problem: Communication error in Firefox when Use system proxy settings is enabled
Symptoms A communication error message is displayed inFirefox immediately after youlogon to the Codar Console.
Primary software component Codar Console
Failure message Communication error
Probable cause In some network environments, Firefox is unable tocommunicatewith the Codar when the Use system proxy
setting is enabled.settings
Solution
Configure Firefox network settings to use a method other than Use system proxy settings. For example,configure Firefox to use either a manual or automatic proxy configuration.
In Firefox 33, the proxy settings are configured in > > > > .Tools Options Advanced Network Settings
Internet Explorer Enhanced Security Configuration interferes with the Codar Console
Problem: Internet Explorer Enhanced Security Configuration (ESC) interferes with the Codar Console
Symptoms When viewing the Codar Console in InternetExplorer on a system in which Enhanced SecurityConfiguration isenabled, the console may not display properly. InInternet Explorer versions 10 or 11, a blank screenmay be displayed when accessing the CodarConsole.
Primary software component Codar Console
Failure message N/A
Probable cause Internet Explorer Enhanced Security Configurationimpedes the proper display of the Codar Console.
Solution
To access the Codar Console on Internet Explorer on a system in which Enhanced Security Configurationis enabled, perform one of the following steps:
Add the URL of Codar as a trusted site. In Internet Explorer. Select > > Internet Options Security
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 6
1.
2.
> , and enter https://.Trusted sites Sites
Add Codar as a site in the local intranet zone. In Internet Explorer, select > Internet Options > > > , and enter https://.Security Local intranet Sites Advanced
Disable Internet Explorer Enhanced Security Configuration. In Server Manager on MicrosoftWindows, disable Enhanced Security Configuration.
Attempting to add a valid approver fails
Problem: If you try to add a valid approver after a failed attempt to add an invalid approver who does not have access to theorganization, the valid approver does not get added and an error message is displayed
SymptomsIf you try to add a valid approver after a failedattempt to add an invalid approver, thefollowing message is displayed: User does not have the permissionORGANIZATION_READ to perform theoperation.
After clicking , an attempt is made to addOKthe same valid user to the policy again withoutexiting the popup UI, and the add operation issuccessful.
Primary software component Codar Console
Failure message User does not have the permissionORGANIZATION_READ to perform the operation.
Solution
Click when the error message is displayed. Then add the same user to the policy again. The user isOKadded successfully at the second attempt.
Unable to log on to the Codar Console after installation when Single Sign-On is configured
Problem
A logon attempt to the Codar Console is unsuccessful after installation when Single Sign-On isconfigured.
Symptoms Unable to logon to the Codar Console
Primary software component Codar Console
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 7
Failure message No error message is displayed when attempting tolog in, but the login is unsuccessful. In the csa.logfile, the following error message is logged: setSSOToken cannot be performed, configuredcreationDomains does not contain receivedrequest domain
Probable cause The domain for Single Sign-On has not beenproperly specified.
Solution
If you install Codar on a system with a fully qualified domain name (FQDN) of the format a.b.com, and ifyou enable Single Sign-On during installation, you must specify a domain name of the format a.b.com onthe install screen in which the domain name is requested. If you specify b.com, you will be unable to logon to the Codar Console after installation. The Single Sign-On functionality requires a domain name ofa.b.com to be specified in this scenario.
If you have already installed Codar, you can edit the /jboss-as/standalone/deployments/csa.war/WEB-INF/hpssoConfiguration.xmlfile to set the domain property correctly, and then restart the Codar service.
Various issues when logging into the Codar Console using multiple browsers
Problem: Various issues may occur when you use multiple browser tabs to log on to the Codar Console with different usercredentials
Symptoms If you use multiple browser tabs to log on asdifferent Codar users, the last user to log ondetermines the access rights of all the currentlyopen browser tabs. This can result in errormessages beingdisplayed when a user attempts to perform anaction that the last logged on user does not haverights to perform.
Primary software component Codar Console
Failure Message --
Probable cause Improper handling of multiple tabs
Solution
Use only one browser tab at a time to log on to the Codar Console. If multiple tabs are used, ensure thatthe same user is logged in to each tab. To switch among users, first log out and then log back in as adifferent user.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 8
A user cannot be searched in the Codar access control
Problem: A user cannot be searched in the Codar access control if the role is configured with the user DN instead of the group DN
Symptoms Role-based search does not list a user if theOrganization Access Control role DN is configuredwith the user instead of the group's ActiveDirectory
Primary software component Codar topology design
Failure message --
Probable cause Provider organization access control roles DN for auser instead of group
Solution:
User access search is supported for groups that are configured in the provider access control but is notsupported for individual users. Therefore, add the user to the group in Active Directory.
Design not listed when access control added to any design in PLM
Problem: Design not listed when access control added to any design in PLM
Symptoms Design is not listed for a user of the group forwhich the access control is provided
Primary software component PLM
Failure message --
Probable cause Browser cache
Solution
1. Clear browser cache.2. Log out of Codar and re-log in.
Modified Group name not listed in Access Control Group Search
Problem: After modifying the group name in Organization Access Control page, the modified group name is not visible whensearching for the group in the Add Access Control page.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 9
Symptoms The modified group name is not visible in thesearch for groups in Access Control. Only the oldgroup name appears.
Primary software component Codar topology design.
Failure message --
Probable cause Only the display name of the group is updated, notthe actual name that is displayed in the groupsearch.
Solution:
When a group name in the Organization Access control page needs to be modified, delete the Old Groupname and create a new group with the same DN with the new name, instead of modifying the groupname.
Packages are stuck in 'In Transition' state even though the OO flows are complete in OO Central
Problem: Packages are stuck in 'In Transition' state even though the OO flows are complete in OO Central
Symptoms Some packages are stuck in 'In Progress' stateeven though the OO flows are complete in OOCentral.
Probable cause The default timeout value for script action and OOflow action is insufficient, hence such release gateactions are stuck in 'In Progress' state andpackages are stuck 'In Transition' state.
Solution
By default, the action timeout value is set to 7200 seconds (2 hours). If a particular action is going to takemore than 2 hours to complete, you need to change the timeout value of following properties in thecsa.properties file/.yaml file.
ReleaseGate.OOFlowAction.WaitTime=7200
ReleaseGate.ScriptAction.WaitTime=7200
This will ensure that the release gate action gets sufficient time to complete.
Codar Localization
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 10
Non-English characters are not stored properly in Oracle
Non-English characters are not stored properly in Oracle
Problem: Non-English characters are corrupted after being stored in Oracle
Symptoms Non-English characters do not display after beingstored in the Oracle database.
Primary software component Oracle database
Failure message --
Probable cause Oracle database localization parameters were notset before installing Codar.
Solution
To support localization, the Oracle database must be configured to support non-English characters. Thisconfiguration must be complete before Codar is installed. If the necessary parameters are not set to therequired values, and you have already installed and are using Codar, then to support non-Englishcharacters you must create another database configured for localization and then migrate the data to thisinstance. See the "Configure Oracle for localization" section of the Codar Installation and Configuration
.Guide
Installation and configuration
Cannot enable the load balancer host in the PostgreSQL database
Codar installation hangs with no error message
Content upload not successful during Codar Installation
Enable HTTPs traffic logging
Failed to execute Codar installer on Linux
Failure to install Codar on Linux
IDM deployment fails with ClassNotFoundException: com.hp.hpsso.HpSsoContextListener
Installation fails because Codar cannot execute the bzip2 command
Installation fails with SQL errors in the install.log file
Multiple JDBC drivers exist for Oracle in the provided directory
Multi-tier sequential designs failing with Operations Orchestration (OO) 10.20
Operations Orchestration (OO) upgrade fails
Performance issues while importing large archives
Tips for installing and configuring Codar
Uninstallation did not finish successfully
Cannot enable the load balancer host in the PostgreSQL database
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 11
1.
2.
Problem: Cannot enable the load balancer host in the PostgreSQL database on a cluster
Symptoms When setting up Codar in a scalable mode with aload balancer using a PostgreSQL database, youare not able to log on to Codar.
Primary software component Codar
Failure message Unable to log on to Codar
Probable cause The PostgreSQL database is not acceptingconnection requests from the load balancer.
Solution
Update the file with postgresql.conf listen_address ='*'
Add the load balancer IP address to the file as follows:pg_hba.conf#IPv4 local connections:host all all /32 md5
Codar installation hangs with no error message
Problem: Codar installation hangs with no error message displayed.
Symptoms Codar installation gets stuck with no error messageindication. The process appears to berunning. Installer log files are empty or do not exist.
Primary software component Installer
Failure message N/A
Probable cause The Codar installer fails in the pre-install phaseand does not log error messages in the installer logfiles. However, some messages are logged inthe pre-install log files in the directory.temp
Solution
Go to (in Windows) or (in Linux) and check theC:\Users\\AppData\Local\Temp\ /tmppre-install log file (named for example ). If this log filecsa-preinstall-2015-12-08-14-34.logcontains any error message, fix the problem and run the installation again.
Content upload not successful during Codar Installation
Problem: When Codar is installed with embedded Operations Orchestration (OO), component tool content packs are not being
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 12
automatically imported
Symptoms When Codar is installed with embedded OO,component tool content packs are not importedand a failure message is displayed.
Primary software component Codar
Failure message OO content upload was not successful. CannotUpload Contents, please follow configuration guideto upload contents manually.OO Content upload was not successful. Cannotcreate OO user, please follow configuration guideto upload contents manually.
Probable cause The first time the embedded OO service startsduring installation, it creates a database schemaand an internal user, and uploads the content. Ifthese operations do not occur before the contentuploading timeout value is reached due to, forexample, server or database performance issues,a failure ccurs.
Solution
Log on to OO and manually deploy the content packs, as necessary. For more information, see the"Configure Operations Orchestration" section in the .Codar Configuration Guide
Enable HTTPs traffic logging
Problem: HTTPs logging can be switched on to troubleshoot related issues
Symptoms Need more information about HTTPs traffic goingbetween Codar server and client endpoints.
Primary software component JBoss
Failure message N/A
Probable cause N/A
Solution
In case you need to have more information about HTTPs traffic when troubleshooting an issue, HTTPslogging can be switched on in the JBoss configuration file. The configuration file exists on path
%CODAR_HOME%\jboss-as\standalone\configuration\standalone.xml
In case of HA setup, the correct path is
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 13
%CODAR_HOME%\jboss-as\standalone\configuration\standalone-full-ha.xml
Look for the section below and uncomment the last line to enable the logging.
When the logging is enabled and the server is restarted, a new log file is created that contains informationabout the traffic.
%CODAR_HOME%\jboss-as\standalone\log\access_log.log
127.0.0.1 18/Nov/2015:17:18:41 +0100 HTTP/1.1 8444 GET /csa/api/ping - 401 - -127.0.0.1 18/Nov/2015:17:18:43 +0100 HTTP/1.1 8444 GET /csa/j_spring_security_logout - 302 - -127.0.0.1 18/Nov/2015:17:18:44 +0100 HTTP/1.1 8444 GET /csa/logout.jsp - 302v6t5EYIsaAmLrnXP4_jjgixC -127.0.0.1 18/Nov/2015:17:18:45 +0100 HTTP/1.1 8444 GET /csa/login - 200 v6t5EYIsaAmLrnXP4_jjgixC-127.0.0.1 18/Nov/2015:17:18:45 +0100 HTTP/1.1 8444 GET /csa/static/lib/react-intl/react-intl.min.js - 200v6t5EYIsaAmLrnXP4_jjgixC -127.0.0.1 18/Nov/2015:17:18:46 +0100 HTTP/1.1 8444 GET /csa/static/img/hpe_logo.png - 200v6t5EYIsaAmLrnXP4_jjgixC -127.0.0.1 18/Nov/2015:17:18:52 +0100 HTTP/1.1 8444 GET /consumption/rest/organization/accessPoint?orgName=CSA-Provider 404 - -127.0.0.1 18/Nov/2015:17:18:52 +0100 HTTP/1.1 8444 POST /idm-service/v2.0/tokens - 200zi7NNApDe0q3sWH3NGZBA75N -127.0.0.1 18/Nov/2015:17:18:52 +0100 HTTP/1.1 8444 POST /csa/j_spring_security_check - 302X79hB4pWVLxJilKAF11KP4G4 -127.0.0.1 18/Nov/2015:17:18:52 +0100 HTTP/1.1 8444 POST /csa/rest/audit/ - 200 - -127.0.0.1 18/Nov/2015:17:18:54 +0100 HTTP/1.1 8444 GET /csa/dashboard/index.jsp - 200X79hB4pWVLxJilKAF11KP4G4 -127.0.0.1 18/Nov/2015:17:18:54 +0100 HTTP/1.1 8444 GET /csa/html-lib/js/3rdparty/require/require.js -200 X79hB4pWVLxJilKAF11KP4G4 -
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 14
Failed to execute Codar installer on Linux
Problem: Failed to execute Codar installer on Linux
Symptoms Failed to execute Codar installer on Linux.
Primary software component Codar on Linux platform
Failure message No Java virtual machine could be found from yourPATH environmentvariable. You must install a VM prior to running thisprogram.
Probable cause $JRE_HOME/bin should be in the $PATH
Solution
Export PATH=/usr/java//bin:$PATH and continue installation.
Failure to install Codar on Linux
Problem: Failure to install Codar on Linux
Symptoms Codar installation fails on the Linux platform anddisplays an error message
Primary software component Codar
Failure message Check the
/MicroFocus_Codar_1_94_0_installation/Logs/helion_codar_install.log
file for the failure message:
HostInfo Error:
Status: ERRORAdditional Notes: ERROR -
java.net.UnknownHostException: or service notknown
Probable cause The FQDN is not resolvable.
Solution
Modify the file to include the IP address, host name, and FQDN./etc/hosts
For example, in the Linux system, edit the file and add following line: /etc/hosts < >< >host name FQDN
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 15
1.
2.
3.
4.
IDM deployment fails with ClassNotFoundException: com.hp.hpsso.HpSsoContextListener
Problem: IdM deployment fails with ClassNotFoundException: com.hp.hpsso.HpSsoContextListener
Symptoms The IDM file does not deploy successfully in.warWildFly (application server).
Primary software component The problem is located in the IDM file..war
Failure message Failed to start servicejboss.undertow.deployment.default-server.default-host./idm-service.UndertowDeploymentInfoService:
org.jboss.msc.service.StartException in servicejboss.undertow.deployment.default-server.default-host./idm-service.UndertowDeploymentInfoService:
java.lang.ClassNotFoundException:com.hp.hpsso.HpSsoContextListener from [Moduledeployment.idm-service. from Servicewar:mainModule Loader]
Probable cause The problem is cause by an incorrect value in thefollowing file:
jboss-as/standalone/deployments/idm-service.war/WEB-INF/web.xml
This file contains the following incorrect Java classname:
com.hp.hpsso.HpSsoContextListener
Solution
Stop Codar.
Locate the jboss-as/standalone/deployments/idm-service.war/WEB-INF/web.xml file.
Change com.hp.hpsso.HpSsoContextListener to com.hp.ccue.identity.hpssoImpl.HpSsoContextListener
Start Codar.
Installation fails because Codar cannot execute the bzip2 command
Problem: When installing Codar on Linux, the bzip2 command cannot be found during the OO installation
Symptoms Codar installation fails during the OO installation
Primary software component OO
http://warmainhttp://idm-service.war/WEB-INF/web.xmlhttp://idm-service.war/WEB-INF/web.xml
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 16
1.
2.
3.
Failure message tar (grandchild): bzip2: Cannot exec: No such fileor directory
Probable cause OO installation requires to be installed onbzip2the Linux system
Solution
Install on the Linux OS and run the Codar installer again.bzip2
Installation fails with SQL errors in the install.log file
Problem: Installation fails and SQL error messages are displayed in the install.log file
Symptoms Installation fails and SQL error messages aredisplayed in the fileinstall.log
Primary software component Codar
Failure message org.postgresql.util.PSQLException: ERROR:duplicate key value violates unique constraint"csa_category_type_pkey"org.postgresql.util.PSQLException:
ERROR: relation "csa_access_point" alreadyexists
Probable cause A fresh database schema was not used in theCodar installation.
Solution
Uninstall the failed Codar instance by following the steps provided in the .Codar Installation Guide
Create a new database instance.
Install Codar and specify details of the new database instance.
Multiple JDBC drivers exist for Oracle in the provided directory
Problem: Codar installation may not finish successfully if the provided directory with JDBC drivers for Oracle contains multipledrivers
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 17
1.
2.
3.
Symptoms Codar installation may not finish successfully incase that the provided directory with JDBC driversfor Oracle contains multiple drivers. For example,if multiple drivers have the same ojdbc(6|7)prefix, the installer randomly uses one of theprefixes and this prefix may not be the correct one.Ensure that the provided directory contains onlyrelevant JDBC drivers.
Primary software component Installer
Failure message [org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject](JCA PoolFiller) IJ000610: Unable to fill pool:javax.resource.ResourceException: Could notcreate connection (in server.log)
Caused by: java.lang.NoClassDefFoundError:oracle/dms/console/DMSConsole
Probable cause When installing Codar, you are prompted to enter apath to a directory that contains JDBC drivers forOracle. If the directory contains files that are.jaractually not JDBC drivers with the ojdbc(6|7)prefix, the installation may display errormessages.
Solution
Stop Codar.
Change the driver at this path\boss-as\modules\system\layers\base\com\oracle\ojdbc(6|7)\main\.jar
to \boss-as\modules\system\layers\base\com\oracle\ojdbc(6|7)\main\module.xml
to point to correct file name
Start Codar.
Multi-tier sequential designs failing with Operations Orchestration (OO) 10.20
Problem: Multi-tier sequential designs failing with OO 10.20
Symptoms Multi-tier sequential designs fails only withembedded OO 10.20
Primary software component Codar Console
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 18
1.
2.
3.
4.
5.
Failure message java.lang.RuntimeException: java.io.IOException:Server returned HTTP response code: 500 inCodar.
Solution
MS SQL schema used by the OO 10.20 should be configured by the following settings before theinstallation:
AllowSnapshotIsolation=True IsReadCommittedSnapshotOn=True
Operations Orchestration (OO) upgrade fails
Problem: Codar upgrade fails
Symptoms Codar upgrade fails with the following message:
OO upgrade failed. OO upgrade log contains:Unable to delete file.
Primary software component OO
Failure message Unable to delete file{OO_install_dir}/central/tomcat/work/Catalina/localhost/oo/org/apache/jsp/WEB_002dINF/jsp/login_jsp.class
Probable cause OO Central may have been started by a userdifferent from the Codar user and some files mayhave insufficient permissions for the Codar user.
Solution
When the upgrade fails, execute these steps:
Go to /upgrade/10.50/backup
Copy the OO Central folder back to (running a rollback in will not work)/upgrade/10.50/bin
Add execute permission to all the files in /central/bin
Remove or change permissions for all files that have incorrect permissions in .central/tomcat/work
Run Codar and resume upgrade or upgrade OO manually by running in ./apply-upgrade -f/upgrade/10.50/bin
Performance issues while importing large archives
Problem: Import of large archives (greater than 1.5 MB) is slow
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 19
1.
2.
3.
1.
2.
Symptoms The import operation goes on for a long time.
Primary software component Codar
Failure message "Out of memory" error in the fileserver.logduring the import operation
Probable cause The default heap size (1 GB) configured in Codaris not sufficient for the import operation.
Solution
Increase the heap size configured for Codar and perform the import. For additional details, refer to the"Import Large Archives" section of the Codar Installation Guide.
Tips for installing and configuring Codar
The following are some problems that you may encounter while installing Codar and workarounds for theproblems:
Symptom You have entered the database credentials but theinstaller cannotconnect to the database
SolutionConfirm that you have entered the correctcredentials.
Confirm that the user name used to connect tothe database has the appropriate databasepermissions to create tables.
Click Cancel on the installer. This creates aninstaller log file (
) on theCodar_Install_desktop. This file contains the stack trace withthe actual problem.
Symptom The LDAP user is unable to log on to the CodarConsole
SolutionVerify that the LDAP server is accessible.
Verify that the LDAP configuration in the CodarConsole is correct.
Symptom The Codar server does not start after install
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 20
1.
2.
1.
a.
b.
c.
2.
SolutionVerify that the ports used by Codar are free.The ports include 9999, 9990, 9443, 8009,8081, 8444, 8090, 4447, 4712, 4713, and1099.
If any of these ports are in use, modify the portthat is the cause of conflict in the
file.standalone.xml
Uninstallation did not finish successfully
Problem: Uninstallation did not finish successfully
Symptoms When the user runs uninstall of Codar, thefollowing message is displayed at the end ofuninstallation: "The uninstallation could not complete due to anerror."
Primary software component Installer
Failure message "The uninstallation could not complete due to anerror."
Probable cause Unexpected error when executing all uninstallrelated tasks.
Solution
Please follow these steps:
If CODAR_HOME foder was not removed, search for the uninstallation log file here:/_CSA_4_70_0_installation/Logs/uninstallLog.txt
If the uninstallLog.txt exists, please search for the root cause of an uninstallation failure in it.
Remove the impediment found the in the uninstallation log file.
Delete the whole Codar install directory.
Remove all corresponding Codar entries from /.com.zerog.registry.xml file.
Miscellaneous issues and information
About the Codar support tool
Application deployment fails using some partial designs
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 21
Clicking on action name for CMP Service action pops up a new login window
Codar fails with a JDBC rollback error
Error while publishing a topology design
Error while updating sequential service design
On a fresh install of Premium, the release pipeline view is blank for the Sequence Designs
Response time is 20 to 30 seconds when fetching and displaying error message for non valid CMPprovider
REST API - Cannot create property names
Triggering a build from TFS fails with error "Could not find the Design for the version"
User authorization fails if the base domain name of an organization is modified during a usersession
When a custom action runs for a long duration (typically > 4 hours) , the package is found in“transition” state.
While creating or updating package properties through the API, only the property values aremodified
Windows command-line commands do not get executed
About the Codar support tool
The Support Tool for Codar is a command line tool written in Java that collects important log andconfiguration files from different places in the Codar installation directory and packs them in a ZIP archive.The ZIP archive can then be attached to any service request or defect submission to provide themaximum amount of detailed information about your actual environment and the current state of theproduct. The support tool can be used anytime, and is especially useful when investigating andtroubleshooting technical issues.
The support tool is located in the folder inside the Codar installation folder. You can execute theToolssupport tool like any other tool in Codar. It does not require any arguments.
Running the support tool
To run the support tool, run the command.java -jar support-tool.jar
Use to see usage hints. There are two optional parameters: –-help
--home < >arg : Use this optional argument to use a specific folder instead of the home folder. Thehome folder is auto detected by default.
--output < >arg : Specify the output name of the ZIP archive file to override the default name .logs-and-configs_< >.zipyy-MM-dd
If the tool fails to auto-detect your Codar home folder, run the java -jar support-tool.jar command.--home /path/to/codar/home
To specify a name for the output archive file, run the java -jar support-tool.jar --output command.myarchive.zip
The tool gathers all logs and configuration files and packs them in an archive in the current directory. You
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 22
can then attach this archive to any service request to resolve issues more quickly.
Application deployment fails using some partial designs
Problem: During test run or pipeline deploy or package promote , there is an exception thrown which prevents applicationdeployment.
Symptoms With partial designs, test run or deployment fails.When the composite platform design is executed itworks fine.
Primary software component Partial Designs
Failure message Failed to run test for design.
Probable cause There are required parameters on the capabilitycomponent.
Solution
Parameters on capability component is not supported. If user is defining any parameter on a capabilitycomponent, it should be not be a required parameter.
Clicking on action name for CMP Service action pops up a new login window
Problem: In the release gate action instance page, clicking on any of the listed CMP Service actions, a separate login page appears,where you must login to view realized subscription.
Symptoms A login page appears on clicking on CMP Serviceaction name.
Primary software component Release Automation
Failure message N/A
Probable cause This happens when CSA and Codar instances arenot sharing the same IDM.
Solution
You need to login once and this will be valid till your current session lasts.
Codar fails with a JDBC rollback error
Problem: Codar fails to connect to the database and a JDBC rollback exception error message is displayed in the log file
Symptoms Codar fails to connect to the database and a JDBCrollback exception occurs in the log.
Primary software component Codar Provider Console
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 23
1.
2.
3.
4.
5.
1.
2.
3.
4.
5.
Failure message Codar functionality fails; a JDBC rollback errormessage is displayed.
Probable cause The database connection might be brokenbecause of network issues, or the databaseservice may be unresponsive.
Solution
Add configuration information as follows:
For a standalone Codar setup:
Stop the Codar service.
Navigate to .\jboss-as\standalone\configuration
Open the file and search for the tag that is used in the Codarstandalone.xml dataSourcedatabase configuration.
Add the following after the line that ends with : select1false
Start the Codar Service.
If your Codar instance uses the Oracle database, use the SQL query instead of select 1 from DUAL in step 4.select 1
For a Codar cluster setup:
Stop the Codar service.
Navigate to .\jboss-as\domain\configuration
Open the file and search for the tag which is used in the Codardomain.xml dataSourcedatabase configuration.
Add the following after the line that ends with : select
1
false
Start the Codar Service in cluster mode.
If your Codar instance uses the Oracle database, use the SQL query instead of select 1 from DUAL in step 4.select 1
Error while publishing a topology design
Problem: A topology design is created and saved without error, but an "unable to find the targetresource" error occurs when an attempt is made to publish it
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 24
Symptoms An "unable to find the target resource" error occurswhen an attempt is made to publish a giventopology design.
Primary software component OO
Failure message Example failure messages for situations as stated: -Design Consisting of AWS Network Component
Topology to Execution Plan conversion failed -Unable to find the target resource ofAmazonNetworkInterfaceTypeToAmazonServerTypefor instanceId
-Design Consisting of AWS Volume ComponentTopology to Execution Plan conversion failed -Unable to find the target resource ofAmazonVolumeTypeToAmazonServerType forinstanceId
Probable cause Some component types are defined with inputproperties that must be obtained via outputproperties of certain other component types. Ifsuch component types are used in a topologydesign without the proper companion componenttype that is the source of the required inputproperty, or if a proper relation is not definedbetween the components, the publish operation willfail.
Solution
Ensure that components that require input from certain other component types are properly paired in thetopology design, and that a relationship is defined between them.
Error while updating sequential service design
Problem: An error occurs while updating an upgraded sequential service design
Symptoms A generic error occurs while saving an upgradedsequential service design that has multipleproperties from a single option target bound to thesame service component.
Primary software component Service Design
Failure message Error updating service design
Probable cause Multiple properties from a single option are targetbound to the same service component.
Solution
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 25
Ensure that the service design does not have options such as multiple properties from any single optionbeing target bound to the same property on a service component.
On a fresh install of Premium, the release pipeline view is blank for the Sequence Designs
Problem: On a fresh install of Premium, the release pipeline view is blank for the Sequence Designs with Javascript errors seen inthe console
Symptoms The release pipeline view is blank for sequencedesigns in a fresh install.
Primary software component ARA Release Pipeline
Failure message There are Javascript errors on the console whenthe release pipeline view is loaded. Functionalityworks normally.
Probable cause
This happens because no sequence design is tagged asApplication.
Solution:
User can edit the sequence design and tag it as an Application design.
Response time is 20 to 30 seconds when fetching and displaying error message for non valid CMPprovider
Problem:
Symptoms The response time to display the message is 20 -30 secs.
Primary software component Providers
Failure message N/A
Probable cause With an invalid URL, there is a wait till the timeoutwhich is generally 30 seconds including thebrowsers like firefox for generating the response.
Solution
N/A
REST API - Cannot create property names
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 26
Problem: Cannot create property names using the REST API
Symptoms Codar REST API cannot create property names.
Primary software component Codar REST API
Failure message Object cannot be found.
Probable cause The property name uses special characters.
Solution
If property names, such as URLs, use special characters, the special characters must be encoded.
Triggering a build from TFS fails with error "Could not find the Design for the version"
Problem: Triggering a build from TFS fails with error "Could not find the Design for the version" even after an existing version ofthe Codar plugin is updated with the latest version.
Symptoms Unable to trigger a package deployment from TFS.
Primary software component TFS Codar plugin
Failure message The remote server returned an error: (400) BadRequest. The remote server returned an error: (405) MethodNot Allowed.
Probable cause The latest version of the Codar plugin is not beingused in TFS.
Solution
Please refer to the TFS Integration guide where this issue and solution has been documented.
User authorization fails if the base domain name of an organization is modified during a user session
Problem: User authorization fails if the base domain name of an organization is modified during a user session
Symptoms If the administrator modifies the base domainname in the LDAP settings of an organizationwhen a user is logged in, user authorization failsand navigation is disabled.
Primary software component Codar Console
Failure message Authorization exceptions
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 27
Probable cause The administrator changes the base domainname in the LDAP settings of an organizationwhen a user is logged in to the organization.
Solution
Once the user cache is cleared after the configured timeout that is set in the file, thecsa.propertiesuser can log on again and the user groups will be refreshed.
When a custom action runs for a long duration (typically > 4 hours) , the package is found in“transition” state.
Problem: When a custom action runs for a long time, and OO flow returns response code, the package is found in “SUCCESS” state.transition
Symptoms Custom action execution takes a long time.
Primary software component Release Gate Custom Action
Failure message N/A
Probable cause
Solution
Increase the value for " for the particular custom action in the table Thetimeout" csa_cd_rg_action. value is in seconds.
While creating or updating package properties through the API, only the property values are modified
Problem: While creating or updating package properties through the API, only the property values are modified. Othercomponent-specific properties are not modified.
Symptoms Update package properties through the API or CLIby specifying the package properties JSON. In theJSON body request, change the value of any inputproperty other than the package property.Thechanges are not reflected.
Primary software component Codar
Failure message None
Probable cause Only package property names and values aremodifiable.
Solution
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 28
Only modify the package properties value in the package properties JSON specified in the input.
Windows command-line commands do not get executed
Problem: Windows® command-line commands do not run
Symptoms Scripts or commands typed into the Windowscommand prompt fail.
Primary software component Windows command prompt
Failure message internal or external command, operable program orbatch file. For example, 'C:\Program' is not recognized as aninternal or external command, operable program orbatch file.
Probable cause If a variable is used in the command, the variablemight contain a space in the directory path name.
Solution
If a command uses a variable, enclose the command in quotation marks.For example,
"%CSA_HOME%\jre\bin\java" -jar process-defn_tool.jar -d db.properties -iHPOOInfoInput.xmlor"%ICONCLUDE_HOME%\jre1.6\bin\java" -jar CSA-3_10-ContentInstaller.jar-centralPassword mypassword
Application-Level Troubleshooting
An application design JSON cannot be exported and then imported into another Codar applicationinstance
Application packages get stuck in the transition state forever
Design versions of the container are in the locked state
User is unable to create application
User is unable to delete application
User is unable to delete custom roles
User is unable to delete default roles
User is unable to promote application package from one stage to another
‘Default lifecycle stage’ is not reflecting while creating a new application version.
‘Run Security Scan’ gate action with ‘component property’ parameter fails.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 29
1.
2.
1.
2.
3.
1.
2.
3.
An application design JSON cannot be exported and then imported into another Codar applicationinstance
Problem: An application design JSON cannot be exported and then imported into another Codar application instance
Symptoms When you export an application design as a JSONfile in a Codar instance and then try to import it intoanother instance, the import fails.
Primary software component Codar
Failure message Cannot import design.
Probable cause --
Solution
Export the design as a ZIP file from the UI and then import the zipped file into a different Codarapplication.
Application packages get stuck in the transition state forever
Problem: Application packages get stuck in the transition state forever the package cannot be deleted
SymptomsThe package is in the transition state foreverwhen promoted (when release gate actions areconfigured).
Packages that are in the transition state cannotbe deleted.
Primary software component Codar
Failure message None
Probable causeProvider is not configured.
Proper values are not mapped to the OO flowin Custom Action.
A content pack is accidentally deleted in OO.
Solution
Configure the resource provider correctly.
Map the component properties to the OO flow parameters properly in Custom Action.
Verify that the content pack is available in OO.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 30
Design versions of the container are in the locked state
Problem: If a container that is already associated with the release pipeline is dissociated from it, then the design versions of thecontainer can be in the locked state if the application design version contains packages
Symptoms The design cannot be modified and the design is inread only mode.
Primary software component Codar
Failure message None
Probable cause Packages already exist for the design.
Solution
Delete all existing packages in all the design versions of the application container before dissociating itfrom the release pipeline.
User is unable to create application
Problem: User is not able to create an application from an empty or invalid design.
Symptoms Unable to create Application
Primary software component Codar
Failure message -
Probable cause Issue can be related to empty or invalid .design
Solution
Verify if the design used to create the application is valid.Make sure the design used to create application is not empty; if so, add components to the design and trycreating application again.
User is unable to delete application
Problem: User is not able to delete an application.
Symptoms User is not able to delete application
Primary software component Codar
Failure message -
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 31
Probable cause The issue can be related to one of the followingreasons:
1) Multiple versions of application exist
2) An active package is in deployment stage
3) User does not have sufficient permission
4) Associated topology design is accidentallydeleted.
Solution
Check if an application has multiple versions; if so, delete each application version one by one.Verify if a package associated to an application is in deployment stage, if so, stop the the deployment andtry again.Check if the user has the required privilege to perform the delete operation. If not, provide the 'Delete'access privilege and try again.If an application is based on topology design,verify if that design is available in design module to ensure itis not accidentally deleted.
User is unable to delete custom roles
Problem: User is not able to delete custom roles in Codar
Symptoms User is not able to delete the custom roles
Primary software component Codar
Failure message -
Probable cause This issue can be related to user permission or theuser being part of an application's access control.
Solution
Verify if the user has sufficient privilege to delete custom roles, if not, grant the appropriate permissions.Check if the remove the access control and tryuser role is part of an application's access control; if so, again.
User is unable to delete default roles
Problem: User is not able to delete default roles.
Symptoms User is not able to delete roles which come bydefault in Codar.
Primary software component Codar
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 32
Failure message -
Probable cause Codar does not allow deletion of default roles.
Solution
N.A. as Codar does not allow of default roles.deletion
User is unable to promote application package from one stage to another
Problem: User is not able to promote application package from one stage to another.
Symptoms User is not able to promote application package toanother stage
Primary software component Codar
Failure message promote failed
Probable cause The issue is either related to release gate actionfailure/abortion or user does not have sufficientprivileges.
Solution
Check if the release gate action has failed; if so, fix the reason for failure and try again .Check if the user role has appropriate permission to promote a package in corresponding life cycle stage.If the user does not have the permission, grant the same to the corresponding user/role.
‘Default lifecycle stage’ is not reflecting while creating a new application version.
Problem: If an application is already created with a default lifecycle stage and if the default life cyclestage is appended with a new stage, since then, all newly creating application versions will not get thelatest default lifecycle stage.
Symptoms Newly added stage is not listing while creating anew version of an application.
Primary software component Codar.
Failure message NA.
Probable cause The design is creating at first and at this point, thedesign is referring a set of default life cycle stagesand newly introducing default stages are not bondto existing design.
Solution
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 33
There are two solutions to this behavior.
1) After introducing new default lifecycle stage, create new designs and then create new applicationversions by using that designs.
2) Manually modify new application version’s lifecycle configuration to get all the lifecycle stages.
‘Run Security Scan’ gate action with ‘component property’ parameter fails.
Problem: ‘Run Security Scan’ gate action has a provision to configure FPR file, Username and Source Code Directory via a featurenamed ‘component property parameter’. If these parameters are configured with ‘\’ (back slash), then the gate action fails.
Symptoms The ‘Run Security Scan’ gate action will be failedwhile a package is being promoted or deployed.
Primary software component Codar
Failure message [warning]: File homeSRChelloworld.java not found[error]: No valid input files were specified
Probable cause Codar program consider “/” (front slash) for'component property parameters'.
Solution
Use “/” (front slash) instead of “\” (backslash) for FPR file and Source Code Directory parameters.
Use username alone(Administrator) without having any domain name and slash(DomaiName\Administrator).
Connection Troubleshooting
Failed to open HTTP connection; failed to Get resource; exploration of OO flow run execution
Page Not Found error when running the Pet Clinic out-of-the-box design
The Pet Clinic application deployment fails for the MySQL component
Failed to open HTTP connection; failed to Get resource; exploration of OO flow run execution
Problem: Failed to open HTTP connection; failed to Get resource at ; exploration of OO flow run execution
Symptoms The Amazon Web Services design test run fails.
Primary software component Codar
Failure message Failed to open HTTP connection; failed to Getresource at < >; Exploration of OO flow runURLexecution
Probable cause Missing proxy host and port within OperationsOrchestration
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 34
1.
2.
3.
4.
5.
Solution
To fix this issue:
Set your proxy host and port in Operations Orchestration.
Navigate to the area in Operations Orchestration, and select the Content Management System tab.Properties
Select CSA_Proxy_Host, and then click the Edit button (pencil icon) to set the value of the proxyhost. Set the value to your browser’s current proxy host.
Similarly, set the value of CSA_Proxy_Port to your browser’s current proxy port.
Redeploy your design to allow the Operations Orchestration REST client to communicate beyondyour firewall.
Page Not Found error when running the Pet Clinic out-of-the-box design
Problem: Page Not Found error when running the Pet Clinic out-of-the-box design
Symptoms Deployment fails for the Pet Clinic out-of-the-boxdesign and a Page Not Found error message isdisplayed when the MySQL database componentis deployed.
Primary software component Pet Clinic, Tomcat, MySQL, Pet Clinic DBConfcomponents.
Failure message PAGE_NOT_FOUND
Probable cause The artifact URL or the configuration URLparameter path is not correct.
Solution
Ensure that the file exists in the URL path that is provided.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 35
The Pet Clinic application deployment fails for the MySQL component
Problem: End-to-end deployment fails for the Pet Clinic application when deploying the MySQL component
Symptoms An end-to-end deployment may fail whendeploying the MySQL database component whencopying the configuration file is being copied.
Primary software component MySQL component
Failure message Copy configuration OO flow will fail.
Probable cause This issue may occur if no input is provided to theVMware vCenter Server component thatcontains the database hostname/passwordproperties. The database host name and passwordmust be specified in the design even though theyare non-mandatory properties.
Solution
Specify the database host name and password before deploying the Pet Clinic application end-to-end.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 36
Integration Troubleshooting
ALM
Amazon Web Services
Bamboo integration
Chef
Docker Universal Control Plane - DOCKER UCP DATA CENTER
Helion OpenStack
Operations Orchestration
SiteScope (Codar)
VMware vCenter (Codar)
ALM
When there is a TestSetAction and Multiple Packages Promoted simultaneously, some packages stay inTRANSITIONING state
Problem: When there is a TestSetAction and Multiple Packages Promoted, some packages stay in TRANSITIONING state
Symptoms Issue occurs if 2nd package is promoted while the1st package’s RG is TRANSITIONING.
Primary software component Release Gate Action
Failure message
Probable cause ALM Server does not allow to execute a TestSetwhen the TestingHost is being used by anotherTestSet.
Solution
During Package promotion if the ALM test action is failing, then Test host may not be available. The testhost might be busy in exectuing tests for a different package or tests triggered manully from ALM. Somultiple requests to execute tests might fail becasue of concurrency issues
To avoid concurrency issues:1. Add more test hosts2. Ensure only 1 package is promoted at a time (which has Test Action)3. If the package keeps failing repeatedly because of Test action, then Promote after some time4. Check network connection between Codar and ALM machine
Amazon Web Services
An AWS instance cannot be reached using its public IP address
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 37
Attaching the network interface to the server fails
AWS provider validation fails
Test run fails when more than one network interface is connected to a single AWS server in thedesign
The public IP address of the AWS server instance is not visible
Unable to provision the server because of difference between access point and zone specified inthe design
An AWS instance cannot be reached using its public IP address
Problem: An Amazon Web Services (AWS) instance cannot be reached using its public IP address
Symptoms An AWS instance is provisioned with a public IPaddress, but cannot be accessed at that address.
Primary software component Amazon Web Services
Failure message None
Probable cause Either the AWS serversecurityGroupIdsproperty is not set, or the securityGroupIdsthat is set does not have a rule set up properly toallow network traffic to the server instance.
Solution
Ensure that the correct security group IDs are set in the AWS server in the design to enable access to theinstance. For more details, see the AWS user documentation.
Attaching the network interface to the server fails
Problem: Failure to attach the network interface to the server
Symptoms In a topology design that has server and networkinterfacesconnected to it, both the Server and NetworkInterface componentsget provisioned in AWS, but attaching the networkinterface to theserver fails.
Primary software component Amazon Web Services
Failure message You may not attach a network interface to aninstance if they are not in the same availabilityzone.
Error code: InvalidParameterCombination
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 38
Probable cause The subnet IDs of the server and network interfaceare in different zones.
Solution
Ensure that the subnet IDs of the server and network interface are in the same availability zone.
AWS provider validation fails
Problem: AWS provider validation fails
Symptoms When configuring a provider such as an AmazonWeb Services, you might encounter a validationfailed for resource provider error message.
Primary software component Codar
Failure message Provider Validation Failed
Probable cause This is a known issue with Codar and itscommunication behind some corporate firewallsthrough the service access pointpublic URL configured in the provider.
Solution
This is a known issue with Codar. As a workaround, validate that the URL can be accessed within yourbrowser.
For this issue and other general problems encountered while using the Codar UI (outside of OperationsOrchestration), see the Codar logs for debugging information:
/jboss-as/standalone/log/csa.log
/jboss-as/standalone/log/server.log
Test run fails when more than one network interface is connected to a single AWS server in the design
Problem: When more than one network interface or volume is connected to a single Amazon Web Services (AWS) server in adesign, the test run fails
Symptoms You can attach only one network interface orvolume to a server. If you attach a second networkinterface or volume to the server, a failure occurs
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 39
Primary software component Amazon Web Services
Failure message Instance < >ID_of_network_interface_or_volumealready has an interface attached at device index1.
Probable cause If the object causing the failure is of thetype network interface, then the deviceIndexproperty value is not set.
If the object causing the failure is of thetype volume, then the property valuedeviceNameis not set.
Solution
In designs where more than one network interface or volume is connected to a single AWS server,different values must be specified for the property for network interfaces or the deviceIndex
property for the volume.deviceName
The public IP address of the AWS server instance is not visible
Problem: Public IP addresses for Amazon Web Services (AWS) server instances are not visible
Symptoms In an AWS server, the public IP address propertyvalue that was earlier present has nowdisappeared.
Primary software component Amazon Web Services
Failure message None
Probable cause The server might have been stopped andrestarted.
Solution
This is expected behavior in AWS when the server is stopped and then restarted. See the AWS userdocumentation for more information.
Unable to provision the server because of difference between access point and zone specified in the design
Problem: You are unable to provision a server due to a difference between your access point and the zone specified in the design.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 40
Symptoms You are sometimes able to provision a given AWSserver and sometimes the provisioning operationfails.
Primary software component Amazon Web Services
Failure message "An internal error has occurred. Error code:InternalError" message on the OperationsOrchestration (OO) flow.
Probable cause The AWS provider selected for deploying thedesign might have a mismatch between its zoneand the design. For example, the provider might beconfigured for the "west" zone while the design hasan availability zone set to "east."
Solution
If multiple AWS providers are configured in Codar, then make sure the correct provider instance is chosenfor deploying a package.
Bamboo integration
Problem: Bamboo integration fails with an error stating 'file not found'
Symptoms Bamboo integration fails with an error stating 'filenot found'
Primary software component Atlassian Bamboo
Failure message File not found
Probable cause User authentication
Solution
End-users need to re-evaluate user credentials given across this Bamboo integration.
Chef
Chef integration does not work when the Chef server tries to access provisioned VMs using SSH
Problem: Chef integration does not work when the Chef server tries to access provisioned VMs that are not trusted by the Chefserver using Secure Shell (SSH)
This is applicable only for topology content.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 41
Symptoms Chef-based design provisioning fails withconnection refused error.
Primary software component Chef-based design provisioning
Failure message The following error message is displayed duringthe Chef and Operations Orchestrationdeployment, in the Check Node step:
Connection refused:connect
Probable cause During the Chef-based design realization, the Chefserver connects to the provisioned VMs using SSHto execute Chef operations. If the provisioned VMsare not trusted by the Chef server, this operationfails.
Solution
Add the following lines in the SSH configuration file of the Chef server for the user defined in the Chefprovider configuration property ( ):chefClient
Host *StrictHostKeyChecking noUserKnownHostsFile /dev/null
For example:
ChefClient:developer
SSH Config file location would be /home/developer/.ssh/config
Failed to register new client
Problem: BootStrapNode fails when trying to register the Chef client.
Symptoms BootStrapNode fails when trying to register theChef client.
Primary software component Chef
Failure message Failed to register new client, 4 tries remaining WARN: Response: HTTP 503 - 503 "ServiceUnavailable" WARN: Failed to register new client,3 tries remaining.
Probable cause The issue is caused by the proxy settings duringthe time of deployment. After the deployment of theChef client, the new client tries to register with theChef server. During the first run or during theregistration you will observe the above message.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 42
1.
2.
3.
4.
5.
6.
7.
8.
Solution
Bypass the Chef server host name and IP address in the template. That is, add the following entries in the file in Ubuntu or in Red Hat Enterprise Linux 6.x.bashrc .bash_profile
For example,
export no_proxy=127.0.0.1,localhost,,
The above setting will by-pass the proxy for above hostname and ipaddress. Chef-Run.jpg
Docker Universal Control Plane - DOCKER UCP DATA CENTER
Problem: Docker UCP component won't get deployed due to missing "Undeploy" flow
Symptoms After importing the images as components fromDocker trusted registry, when the Docker UCPcomponents are added to the design and deployedthe design will not get deployed.
Primary software component Provider Type : DOCKER UCP DATA CENTER
Solution
Follow these steps in the given order:
Log on to ITOM Marketplace using your Passporthttps://marketplace.microfocus.com/logincredentials.
Download the content pack https://marketplace.microfocus.com/itom/content/capsule-docker-ucp and it will download a file named " " .Docker UCP V1.0.0.zip
Delete the existing content with the name "Docker Universal Control Pane Content" or "UCP".
Extract the downloaded zip file "Docker UCP V1.0.0.zip" to a folder.
Extract the zip file docker-ucp-data-center.zip which will be inside the previously extracted folderfrom above step 4.
Deploy the content pack docker-ucp-data-center-1.0.0-SNAPSHOT.jar in to OperationsOrchestration.
Import the component (this component should have "Deploy and Undeploy" flows).
Add this component to the design and deploy it. Refer the Docker Universal Control Pane contentguide for more information.
Helion OpenStack
Helion OpenStack - Cloud Service fails to create an instance
https://rndwiki.houston.softwaregrp.net/confluence/download/attachments/1006375621/Chef-Run.jpg?version=1&modificationDate=1435573493000&api=v2https://marketplace.microfocus.com/loginhttps://marketplace.microfocus.com/itom/content/capsule-docker-ucp
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 43
1.
2.
3.
1.
2.
3.
Problem: Helion OpenStack - Cloud Services fail to create an instance when executing a test run usingOpenStack_HPCS_Compute_v3.20.00
Symptoms The Helion OpenStack - Cloud OperationsOrchestration flow (OpenStack Create Instance)fails to execute a test run usingOpenstack_HPCS_Compute_v3.20.00.
Primary software component Helion OpenStack - Cloud Services
Failure message The Operations Orchestration flow (OpenstackCreate Instance) fails to execute and displays thefollowing error message in the flow:
No match found for XPath query;returnResult=Nomatch found for XPathquery;returnCode=0;sessionId=iconclude-4316373317873968843"
Probable causeThe Helion OpenStack - Cloud Servicesprovider is configured with an invalid accesspoint URL.
The Helion OpenStack - Cloud Servicesprovider properties are case-sensitive.
The value of is incorrect.tenantId
Solution
The provider access point URL for Helion OpenStack - Cloud Services must start with https.
The properties defined for the Helion OpenStack - Cloud Services provider are case-sensitive.Define property names as , , and instead of defining them intenantId proxyPort proxyServercapital letters.
Verify that the value of the is correctly entered in the property.tenantId tenantId
Operations Orchestration
Codar Operations Orchestration content not reflected in OO
Failure in trust store setup causes login lockouts
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX pathbuilding failed
OO flow is not validating "docker run" arguments
Timed out error when provisioning parallel servers for OOTB Sequenced Designs
Trust store setup failure leads to login lockouts
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 44
1.
2.
3.
4.
ValidatorException javax.net.ssl.SSLHandshakeException
Workflows in the Operations Orchestration public repository are invalid
Codar Operations Orchestration content not reflected in OO
Problem: Codar Operations Orchestration content is not reflected on OO.
Symptoms After installing the CSA OO content installer(CSA-3_20-ContentInstaller.jar), the CSA flows arenot reflected in OO Studio.
Primary software component Operations Orchestration
Solution
Follow these steps in the given order:
Clean up the OO repository.
Reinstall OO-SA content.
Reinstall OO Content Pack.
Reinstall the CSA-OO content, CSA-3_20-ContentInstaller.jar.
Failure in trust store setup causes login lockouts
Problem: Trust store setup failure causes login lockouts
Symptoms After installing and setting up Codar andconfiguring the Codar trust store to enable accessto Operations Orchestration, it is not possible to login to Codar or Operations Orchestration.
Primary software component Codar, Operations Orchestration, Java keytool,certificate files, McAfee trust authenticationservices
Failure message Browser errors. No login page is displayed in eitherCodar or Operations Orchestration. Indication thatweb services are inaccessible or do not exist.
Probable cause Misstep or typographical error occurred whenrunning the keytool export/import process, followedby manipulation and/or replacement of themonitored certificate files. The may have triggeredthe McAfee trustauthentication security software to intercept andprevent access to either the Codar or OperationsOrchestration web services.
-
© 2011-2018 Copyright EntIT Software LLC, a Micro Focus company 45
1.
2.
3.
Solution
Do not modify the trust store certificates file in its source directory. Modify a copy of this file and verify thatall steps, passwords, and entry changes are correct before replacing it.
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed
Problem: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed
Symptoms javax.net.ssl.SSLHandshakeException:sun.security.validator.ValidatorException: PKIXpath building failed.
Primary software component Codar and Operations Orchestration
Failure message Caught exception:javax.net.ssl.SSLHandshakeException:sun.security.validator.ValidatorException: PKIXpath building failed:sun.security.provider.certpath.SunCertPathBuilderException:unable to find valid certification path to requestedtarget.
Probable cause The Operations Orchestration certificate is notimported into the Codar installed JRE securitycacerts path.
Solution
Ensure that the value of the $PATH environment variable has set as per the JRE$JRE_HOME\binselected during the Codar installation (for example, either openjre or Oracle JRE.)
Verify that the OO10.x certificate is imported correctly to the Codar installed JRE cacerts path,using the following commands:If Oracle JRE is selected during the Codar installation, then import the OO 10.x certificate usingthe keytool.exe -importcert -alias tomcat -file"C:\Temp\oo10-certificate.cer" –keystore
command."C:\ProgramFiles\Java\jre7\lib\security\cacerts"If openjre is selected during the Codar installation, then the OO10.x certificate has to be imported to
using the C:\ProgramFiles\MicroFocus\Codar\openjre\lib\security keytool.exe-importcert -alias tomcat -file "C:\Temp\oo10-certificate.cer" -keystore"C:\ProgramFiles\microfocus\Codar\openjre\lib\security\cacerts" password:
command.changeit
After importing the certificate, restart the Codar service.
For more in