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.
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.
This problem can occur when SBM is set up to use two-way SSL authentication. When you add a manual deployment task and try to deploy, the execution link points to the wrong port and the page hangs.
The fix for this problem will be to disable SSL configuration if using temporary profiles. Example of the start of the message is as follows: See the end of this message for details on invoking
"Do you want to view only the webpage content that was delivered securely? This webpage contains content that will not be delivered using a secure HTTPS connection , which could compromise the security of the entire webpage."
2) Tomcat SSL is configured at the port level. A SSL connector port is defined in the Tomcat server.xml file and specifies the SSLEnabled=”true” attribute.
Check the SSO connection configuration, by default, located in C:\Program Files\Serena\SBM\Common\jboss405\server\default\deploy\idp.war\WEB-INF\conf\Configuration.xml. Find the section that starts with this line:
