| |
Results |
|
SBM Version Diff
|
Differences Between Versions The SBM System Administrator is starting ( build {0}). - The SBM Broker Server is exiting.
|
|
|
Configuration Files, Web Interface Templates, JavaScript Files, and String Changes That Have Changed in 2009 R4
|
<string xml:space="preserve" version="904000514" resname="IDS_LOG_ADMIN_EXITING">The SBM System Administrator is exiting.</string> <string xml:space="preserve" version="904000514" resname="IDS_LOG_ADMIN_STARTING">The SBM System Administrator is starting ( build ).</string>
|
|
|
|
SBM: Gridlist listing report is missing links to First Item / Previous Item / Next Item / Last Item
|
there is a list of items. When you open one of these items, the top of the form should have links for First Item / Previous Item / Next Item / Last Item. These links are missing.
|
|
|
|
InitExtension error when AE db needs to be upgraded still says to use SBM System Administrator
|
Wanted Database Version: 1100000041 Database Software Version: 10.01.05.03 ( Build 135 ) This Software Version: 11.00.00.00 ( Build 451 )
|
|
|
|
After upgrade from SBM 11.0.1.1 to SBM 11.1, work center search does not return any new items and gives "The search index is currently building". (missing SSF_IDXTABLEINFO table)
|
Execute the appropriate SQL statement for your flavour of database (see below for MS/SQL and Oracle versions) Start Tomcat and check the logs when it has started - the errors should have gone MS/SQL version
|
|
|
SBM System Administrator Guide
|
This overrides the default form specified for the workflow assigned to the project. Quick Form indicates that the built -in form will be used; other forms are custom forms created in SBM Composer. From the Default Transition Form drop- down list, select a form for all transitions in the project.
|
|
|
|
SBM System Administrator Guide
|
This feature can enable SBM to locate LDAP user objects on separate servers in the event that some users can not be found in the primary server's LDAP directory. If your LDAP directory entries are split across two or more LDAP servers, the primary LDAP server can be configured to respond to queries in multiple ways: • If the primary server enables "chaining", it will automatically search any secondary servers and build a list of responses as though all the entries were on the primary server.
|
|
|
|
SBM System Administrator Guide
|
This feature can enable SBM to locate LDAP user objects on separate servers in the event that some users can not be found in the primary server's LDAP directory. If your LDAP directory entries are split across two or more LDAP servers, the primary LDAP server can be configured to respond to queries in multiple ways: ▪ If the primary server enables "chaining", it will automatically search any secondary servers and build a list of responses as though all the entries were on the primary server.
|
|
|
|
SBM System Administrator Guide
|
• Consider common traits of users as you construct search filters. For example, (telephoneNumber=555*) returns accounts in which users have phone numbers beginning with 555.
|
|
|
|
SBM: How to Troubleshoot a SBM to ZMF integration (Turning on ZMF trace logging)
|
Any issues in this initial stage will be logged in the SBM server.log (by default, located at C:\Program Files\Serena\SBM\Common\tomcat\server\default\logs)
|
|
|
