Clarity: The 'NIKU DEPLOY' command executed against the Clarity application (non clone) will change the properties.xml file so that it uses the default ports and URL.

book

Article ID: 52776

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL CA Identity Manager CA Identity Governance CA Identity Portal Clarity PPM SaaS - Application Clarity PPM On Premise

Issue/Introduction

Description:

Users getting page cannot be displayed error.

Steps to Reproduce:

Prerequisites: The application URL is something other than localhost, and port is something other than port 80 or the same two values are different in the copy of the properties.xml that is located in the $CLARITY_HOME\config folder and the copy located in the $CLARITY_HOME\.setup\templates\config folder.

  1. niku stop app
  2. niku remove app
  3. niku add app
  4. niku deploy app
  5. niku start app

You will notice in the properties.xml file that the URL is now changed to http://localhost and the port is changed to 80 or the values that were originally in the copy located in the $CLARITY_HOME\.setup\templates\config folder.

Solution:

The 'destroy' option is performing as designed. The destroy should be used when you don't want to use an app or bg service any more at all. It will remove the service completely from the properties.xml.

If the 'destroy' option has to be used and you want to keep the properties intact here is what you need to do the following before using the destroy option:

Copy your current properties.xml file from your \clarity_home\config folder to the \clarity_home\.setup\templates\config folder; the current information will be stored there. Then when the series of commands that includes the 'destroy' option is run, the 'deploy' option will copy the correct information into the properties.xml.

Keywords: CLARITYKB, configuration, installation.

Environment

Release: NCSVCS05900-8.1-Clarity-Service Connect-for MS-SQL
Component: