| |
Results |
|
How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
|
If the user exists in the client requesting authentication, the user will be logged in, otherwise a login failure will occur. For example, if I go to the Dimensions CM website, I will be redirected to the SBM SSO Engine where my login can be authenticated via LDAP. Finally, I will be returned to the calling product (application) with an authenticated token where my username will be mapped to the product's internal user database; if the username does not exist, login will not be granted.
|
|
|
|
What are the exact privileges needed for the SSM orchestration user?
|
The user that you specify in the orchestrations must be an SBM user (not a local Windows account) which has the Product Access type of API/Script. This user must also have item level permissions for View All Items, Update All Items, and Transition All Items. The user needs these item permissions for these projects:
|
|
|
|
Failed to upgrade Orchestration Engine Database. The specified user is invalid....when the password being used has an &
|
The strange part is everything else in the entire product works with this password just not the upgrade in configurator. As a workaround do the upgrade of the OE database with a username password combo with no ampersand &.
|
|
|
|
Custom MashupTool: Event mapping isn't updated after Product Instance is changed
|
• Create a new orch mashup. Add a new orch workflow. Add a new mashup tool, new object and event type for it.
|
|
|
|
For SBM versions 11.0 to 11.6.1, the default sample SBM Certificates for STS, Federation Server and SSO Gatekeeper expire on 15th June 2020.
|
For complete steps on how to update the SSO Certificates, including steps for updating the SSO certificates for integrations with Dimensions RM, Dimensions CM , Deployment Automation, and Version Manager, see KB S142197 which has links to fixing these other products .
|
|
|
|
Cannot deploy Orchestration - [ERROR] META-INF/bpel-definition.xml could not read wsdl document
|
The workaround for this scenario is to use a newer version of *.jar file which ships already with the product . 1. Stop JBoss service 2. Locate older wsdl4j.jar
|
|
|
|
Cannot deploy Orchestration - [ERROR] META-INF/bpel-definition.xml could not read wsdl document
|
The workaround for this scenario is to use a newer version of *.jar file which ships already with the product . 1. Stop JBoss service
|
|
|
Orchestration Scaling and Design in SBM
|
• Synchronization – There are two ways to achieve data synchronization: ▪ In one scenario, synchronization takes place after the fact in a batch process. It involves processing a large number of records in multiple systems to ensure that they remain synchronized after changes to one or more of the data sets. Some examples of data synchronization are: ▪ Synchronizing a customer or product master database with data stored in distributed systems.
|
|
|
|
Contents
|
Product Integration Type Comment VM 8.4.5 or later, 8.5 SourceBridge 2009 R3 Dimensions CM 12.2.2.x, 14.1.0.x Direct IDM Point to Point Dimensions CM 12.2.2.x, 14.1.0.x CM /SB Synchronizer Sync Dimensions RM 12.2, 12.1.1 RM/SBM Sync Dimensions RM 12.2, 12.1.1 Orchestration License Manager 2.2.0 Required for ...
|
|
|
|
Performance Improvements in SBM
|
Product development standards adhere ... Older Product Version Test Focus ... ... Comparison Test for Orchestrations [page 18 ... ... service interactions using orchestrations ... for Basic, Global , and Advanced ... • Project Scalability Improvements ‐ ... 5,000 projects in individual applications ... ... For example, users can browse lists ... system filters out projects that have no ... ... large number of projects . ... large number of users . ... Owner Improvements ‐ Users will experience increased ... a Multi- User or Multi- ... ... based on a user's locale has been ... ... On as Another User ‐ A Find ... On as Another User option on the ...
|
|
|
