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 Where are the SBM JDBC connections stored in 11.x?
SBM contains both a Windows component (IIS) and a Java component. IIS uses the ODBC Administrator for its database connection. SBM 11.x and Tomcat stores its database connection information in the following file.
CMS-XML Data Direct driver for exclusive use with SBM
ERROR [HY000] [ SBM ][ ODBC Oracle driver]The DataDirect product you are attempting to access has been provided to you by Serena Software, Inc. for the exclusive use with SBM . You are not licensed to use this product with any application other than SBM. If you would like to purchase this product, please ....
CMS-XML Error "InitExtension Failed" when logging into the SBM User Workspace
Step 1: Test the ODBC connection
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database
If your MS SQL Server is setup with the Force Encryption value set to yes then you will have to make the following changes for SBM to communicate with it. If your SQL server is setup this way then the Application Engine components will work fine because they connect via ODBC but the JBOSS components will fail to connect via JDBC and need the following changes made to the JDBC connection string in order to connect to the SQL Server database.
CMS-XML Why don't I have access to the features in the new Application Administrator that I used to access via ODBC?
After upgrade to SBM 10.1 or later from a version prior to SBM 10.1 I cannot do the functions I used to be able to do in the ODBC System Administrator e.g. field overrides. In SBM 10.1 the legacy Web Admin has now been replaced by the Application Administrator and many of the System Administrator functions moved here also.
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database in SBM 11.x
If your MS SQL Server is setup with the Force Encryption value set to yes then you will have to make the following changes for SBM to communicate with it. If your SQL server is setup this way then the Application Engine components will work fine because they connect via ODBC but the Tomcat components will fail to connect via JDBC and need the following changes made to the JDBC connection string in order to connect to the SQL Server database.
CMS-XML Upgrading SBM from Windows 32-bit to 64-bit
install, which installs every component on a single 64-bit server. You can still perform Remote Administration tasks or connect directly to the database via ODBC using 32-bit clients.
CMS-XML Oracle Advanced Security and SBM (data encryption)
3. Open the OBDC Adminstrator 4. Edit your ODBC data source and go the the Advanced Security tab. Set your encryption level and data integrity level to '3 - Required' and set the required types. You have now set encryption and integrity for the Application Engine (user interface).
CMS-XML Database Clients and Drivers for SBM
SQL Server 2008 – Use the SQL Server Native Client 10.0 driver. The SQL Server ODBC driver is not compatible with SQL Server 2008.
CMS-XML SQLNET.ALLOWED_LOGON_VERSION prevents SBM from connecting to the Oracle Database
From the Start Menu, search for REGEDIT Go to HKEY_LOCAL_MACHINE\SOFTWARE\ ODBC \ ODBC .INI\Mashup2009 where Mashup2009
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs