Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML 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:
CMS-XML 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:
CMS-XML 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
CMS-XML 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:
CMS-XML 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.
CMS-XML 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.
CMS-XML 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"
CMS-XML 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:
PDF Dimensions CM Pulse Running an Expert Chain on a different server
Step 2: Configure Pulse on CM2  On the second server edit the file % PULSE _ROOT%/conf/ startup.properties NOTE: % PULSE _ROOT% maps to the location of the Pulse home directory Windows: C:\ProgramData\Serena\ Pulse Linux: $DM_ROOT/ pulse _data  The database.jdbcurl line references the primary server (CM1)  The authentication.dcm.server line references the secondary server (CM2)
CMS-XML Dim CM: "There was a problem contacting the authentication server." when attempting to connect to PulseUno
To solve this problem you need to edit $DM_ROOT/ pulse _data/conf/ startup.properties (UNIX), or C:\ProgramData\Micro Focus\Dimensions CM\ Pulse \conf\ startup.properties (Windows), and update the following line to include the new listener port number: Change authentication.dcm.server=SERVER
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs