|
Results |
|
Dim CM: Error "There was a problem contacting the authentication server" when connecting to Pulse
The cause of the problem was that the port number used on the Dimensions server had changed from the default (671) and therefore the $DM_ROOT/ pulse _data/conf/ startup.properties file (or C:\ProgramData\Micro Focus\Dimensions CM\ Pulse \conf\ startup.properties on Windows) had to be updated to reflect the correct port, for example:
|
|
|
DimCM: Pulse Agent: When viewing the Pulse Agents, the Embedded Agent and/or Agents are showing as Unlicensed
When Pulse is being used in an SSO configuration Pulse needs to be told which Dimensions CM server to use for licensing via the license.dcm.server property in the $ Pulse \conf\ startup.properties file. This should be the CM host/port and if using http, the http scheme, i.e. For examples:
|
|
|
DIM14: How to configure Bridge and Pulse to use a non-standard SDP port
For CM Bridge: On Windows modify the file c:\ProgramData\Serena\Bridge\conf\ startup.properties On UNIX/Linux modify the file: $DM_ROOT/ bridge_data/conf/startup.properties
|
|
|
Dim14: Pulse: Can we change the database password for the Pulse user?
3. In turn, you will then need to update the startup.properties file in the <$Pulse>\conf directory as follows:
|
|
|
DimCM: Pulse: How to change the link or links for Help, Quick Tour, Community, Product News & Events
2. Open the startup.properties file in a text editor.
|
|
|
DMCM: Pulse connection failure following manual upgrade to 14.x
When setting the value of database.jdbcurl in Pulse's startup.properties file, ensure that the hostname specified is the hostname of the Oracle database server, NOT the Dimensions Application server.
|
|
|
Dim14: Pulse: 404 page not found error accessing Pulse following a Dimensions Server Components only install
To fix the issue: 1. Locate the startup.properties file which is in the <$Pulse>\conf directory and modify the following lines similar to the following:
|
|
|
Dim CM 14.x: Session activation failed for user dmsys, connecting to cm_typical@DIM10 with PULSE-WEB from nodename (6)
In addition the Pulse interface was working correctly. There were no configuration files in the %DM_ROOT%dfs folder containing DIM10 and the Pulse startup.properties file under ProgramData\Serena\Pulse\conf contained the correct database connection string of DIM14 for the JDBC url.
|
|
|
PulseUno: Http failure response for http://server:8080/pulse/services/rest/hostedrepos: 500 internal server error.
To change “lcoalhost” to “localhost” update $ PULSE _DATA/conf/ startup.properties and modify the value for “gitserver.url”. A second file that needs to be changed is $GIT_DATA/conf/pulse.properties. Here the value for "pulse.url"
|
|
|
CM: Upgrade to 14.3.1 - Pulse no longer starts up correctly - org.springframework.beans.factory.BeanCreationException
It looks like the upgrade had modified startup.properties to use an Oracle SID of dim10, which is not a valid SID on the current system. Logged as a bug:
|
|
|