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 After upgrade to SBM 10.1 and above, I am getting an "Authentication Error" when connecting to the Application Repository
You must ensure that all of the SBM components are installed on one or more servers prior to upgrading. This includes SSO and SBM Common Services. You can choose to enable or disable SSO once it is installed; however you still must install the SSO component for SBM to function properly.
CMS-XML About the Application Repository component and database (How to manually remove the Application Repository component)
Connection attempt failed. Could not connect to the Repository . Please check that the Repository Machine Name and Port are connect.
CMS-XML Login attempt to SBM 10.1 Application Repository fails with no error message
You must use a POST request to get answer from gsoap ! see WebWare gsoap ISAPI module documentation. If the URL cannot be reached because it is incorrect or needs a fully-qualified domain name, the server name can be changed in the Host field on the Component Servers tab in SBM Configurator in most cases.
CMS-XML Why does SSM installer need to be run on Application Engine, Application Repository and Common Services if on different servers?
SSM installer lays down different parts of SSM depending on what is installed on the server. It is therefore important that the SSM installer is run on each of the servers if they are not installed on the same one.
CMS-XML Disable Audit Monitoring in Application Repository
By default, the audit monitoring feature logs Application Repository events such as when items were added to or purged from the repository, as well as deployment and promotion activities. This log is displayed as part of the Purge Audit History tab. Audit monitoring can cause high CPU usage when SQL statements are run against the repository or during audit history purges.
CMS-XML Developer Tools shows (blocked:csp) when loading screens so some parts are not displayed correctly. CSP - Content Security Policy configured in IIS Response Headers
e.g. In the Application Repository - The left and right arrows and a refresh buttons appear as tiny squares. Customer was using IIS to proxy Tomcat and had to add the following to their existing Content-Security-Policy setting on the virtual directory in IIS
CMS-XML Application Repository receives Method Not Allowed (405) error when proxied through IIS
For Use Case 1, make sure that IIS does not have the WebDAV component installed. This component blocks the PUT and DELETE methods. This feature can be removed in the IIS Roles setup area under the Common HTTP Features section called "WebDAV Publishing".
PDF Deployment Automation Artifactory Tutorial (DA 6.1.4)
Table of Contents Introduction 3 Step 1: Install Artifactory 3 Step 2: Create an Artifactory repository and configure 4 Step 3: Configure the artifactory repository 5 Step 4: Install Curl 6 Step 5: Create and add a file to the repository 7 Step 6: Download and Install the plugin 8 Step 8: Create a component to test the plugin 9 Step 9: Create an application 11 Step 10: Run the Artifactory component process 12 SDA 6.14 Artifactory Tutorial Page 2
CMS-XML Symptoms of Common Services being mis-configured. Generally see odd behavior in Work Center. Branding changes two systems at once, missing applications from menus etc.
Let's say you have two environments setup in SBM ( Prod and Test ). When you open Configurator on each box and look at the Components Server screen the only component that should technically be shared between envronments is Application Repository . In this situation you might have all the components setup and running on the Prod box but on the Test box you might have Common Services pulled out onto another box.
CMS-XML Serena SSO/CAC Setup through port 443 Only
When a firewall is placed between the SBM server and the SBM user, it is not always possible to open JBOSS ports 8085, 8243 and 8343 to allow communication through the firewall. The JBOSS components (SSO, Application Repository , Orchestration Engine, etc.) can be installed on a separate server without IIS such that JBOSS Tomcat web server is configured to use port 443. This configuration is straight forward and easily managed.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Comparing files (demonstration)
This Dimensions CM demonstration shows you how to compare two item revisions in the repository, and compare an item revision in the repository with a file in a work area
Dimensions CM: Updating a work area from a stream (demonstration)
This Dimensions CM demonstration shows you how to update a work area from a stream, restrict the update to specific folders in the stream, and exclude files from the update.
Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision
Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs