Database Servers

In the Database Servers tab, you configure the distribution and connection information for the SBM databases. You typically configure the Database Servers tab in wizard mode after you install SBM.

Initially, the Database Servers tab contains a single server (Server 1). By default, all of the SBM databases are listed on this server. You can define additional servers by dragging and dropping SBM databases into the space below Server 1. Alternatively, right-click any database and select the option Move to new server.

To use the SBM sample database, select the Use sample database check box and configure the database server settings for the server that will host the sample database. For more information, see About the Sample Database. If you installed Microsoft SQL Server Express locally to host the sample database, this check box is selected by default. For more information, see SQL Server Express Sample Database.

Entering Database Server Information

To connect to your database server, provide the following information:

Field Name	Description
Application Engine ODBC data source	Displays the current ODBC data source that is used to connect to the Application Engine database. Click Change to create a new data source, rename the default data source, or select an existing data source. For more information, see About Data Sources.
Type	Select the type of DBMS you are using (SQL Server or Oracle). The database type that you select determines which of the following fields appear.
Use SSL	Applies to SQL Server only. Select this check box to encrypt connections from SBM components on this server to SQL Server. For details, see Configuring SQL Server Data Encryption Options.
Windows Authentication	Select this check box to use Windows Authentication instead of SQL Authentication. For more information, see About Windows Authentication.
Host	Enter the host name of your database server.
Instance Name	Enter the SQL Server instance name. Provide a name if more than one instance exists in SQL Server.
Service Name	Enter the Oracle Service Name. This identifies the service name that hosts your Oracle schema. Important: If you performing an upgrade from a previous version of SBM and previously designated a SID for Oracle, then that SID is automatically used in the service name field. Ensure that the correct service name is specified here.
Port	Enter the database server port number. The default SQL Server port is 1433. The default Oracle port is 1521.

Entering Database Connection Information

After you enter your database server information, enter connection information for each SBM database. A warning message appears for each required field that is not completed.

Note the following important information:

The SBM Mail Services component uses the SBM Application Engine database to store settings and configuration. Therefore, you must ensure that the server or servers that run the SBM Mail Services have access to the correct SBM Application Engine database connection information.
You must enter database connection information for the Application Engine database (even though the database connection information is in the DSN that is selected in the Application Engine ODBC data source field). This ensures that SBM framework elements and components that do not use ODBC can still connect to the database.

To connect your databases, provide the following information:

Field Name	Description
Database	Enter the name of the database space you created in SQL Server. Note: You can specify the same name if one or more components will share the same database. If you plan to have separate databases for each component, consider naming the database after the component. For example, "SBM Application Engine Database."
User name	Enter the name of a privileged DBMS user account. Also known as the "schema" in Oracle. Note: For SQL Server databases, enter a SQL Server user account, not a Windows user account.
Password	Enter the user's password.
Confirm password	Enter the password again to confirm.
Connection	After you have entered the connection information, you can test the connection to the database. If the test fails, review the information and make sure the database is online. You can also test the connection from an outside source like Microsoft's ODBC Data Source Administrator or Oracle's SQLPlus.

Configuring SQL Server Data Encryption Options

For SQL Server databases, you can select Use SSL to encrypt the connection and data that is transmitted between the SBM components on this server and SQL Server. You enable this setting on a server-by-server basis—you must manually enable it on each server where SSL encryption from SBM to SQL Server is needed. When the Use SSL check box is cleared, SSL encryption is not requested or used.

CAUTION:

Enforcing data encryption between SBM and SQL server can negatively impact performance because an SSL handshake is made for each connection to the database.

Before you begin, you must configure SSL for SQL Server and install a certificate that meets certain requirements. You must also decide if SQL Server will force encryption or not. Refer to "Encrypting Connections to SQL Server" here for details on configuring SQL Server.

To encrypt connections, select Use SSL in SBM, and then select one of the following options:

authenticate – Selected by default. SSL encryption is required and the server's certificate must be signed by a trusted certificate authority (CA). Data encryption must be enabled on the server in order to complete the SSL handshake and the client (SBM machine) must trust the root authority of the certificate that is used by the server. This means you must also import trusted root and intermediate certificates into the Windows trust store on all servers in your installation and into the appropriate Java key stores on each SBM Tomcat server to use this option.
request – SSL encryption is requested; however, if the server does not support SSL, a plain connection is used. If data encryption is enabled on the server, an SSL handshake is performed; however, the server's certificate is not validated.
require – SSL encryption is required; however, if the server does not support SSL, an exception is thrown. If data encryption is enabled on the server, an SSL handshake is performed; however, the server's certificate is not validated.

Note that for both the request and require options, the server's certificate is not validated and a self-signed certificate is used instead. This is not as secure as using the authenticate option, which performs certificate validation on each connection and requires the server to have a certificate issued by a trusted authority.

Retrying Orchestration Engine Upgrades and Clearing Warnings

The information in this section only applies to upgrades from versions prior to 11.0.

The Orchestration Engine database upgrade is performed by the renew utility that is installed with SBM Orchestration Engine. (For detailed information about the renew utility, refer to the SBM Orchestration Guide.) The renew utility is responsible for restoring existing data from the JBPM tables into the new BPEL tables that are used by the Apache ODE BPEL engine. Existing data in the event manager tables is preserved to ensure that orchestrations continue to run as they did prior to the upgrade.

When the renew utility is launched, all process apps that contain orchestrations are redeployed. If any failures are encountered, a message appears and presents the following options:

View Warnings
This opens the fail_out.xml file located here:
```
installDirectory\Serena\SBM\Misc\renew\fail_out.xml
```
This file contains a list of process apps that failed to upgrade successfully and target environments that are invalid.
View Log
This opens the upgrade.log file located here:
```
installDirectory\Serena\SBM\Common\tomcat\server\default\logs
```
This file contains details about the upgrade, including detailed error messages for any failures that were encountered.

Use the list in fail_out.xml in combination with the detail from the upgrade.log to investigate any failures. Depending on the failures, you have the following options:

You can address the failures, and then click Upgrade Database again. In the prompt that appears, click Retry Upgrade. This launches the renew utility again and attempts to deploy your process apps now that the failures should be fixed.
If the failures are expected and you do not want to change anything, click Upgrade Database again in SBM Configurator, and then click Clear Warnings in the prompt that appears. This prevents the warnings from appearing again and completes the database upgrade.

For example, if the schema version in a process app needs to be upgraded, NOT_SUPPORTED_VERSION appears as the cause in the fail_out.xml file. This means the process app schema version needs to be upgraded by redeploying from SBM Composer. You can either redeploy from SBM Composer and run the database upgrade again, or if you do not want to redeploy at this time, but you want to finish the database upgrade now, click Upgrade Database again, and then click Clear Warnings.

The database upgrade will report failures if the target server information in your environments is missing or cannot be verified. For example, if you are testing the production database upgrade by moving the database to a different environment, the upgrade process will report failures related to your environment definition in Application Repository. You can either update the endpoint and target server information and click Retry Upgrade or click Clear Warnings to proceed without making the changes to finish the upgrade.

Note: You can optionally pass the fail_out.xml file as an argument with the following -redeploy options:

-redeployInFile fail_out.xml

This option redeploys the process apps that are listed in fail_out.xml.

-failOutputFile fail_out.xml

This option recreates the fail_out.xml if it is deleted or missing.

For more examples on these options, refer to the renew command "-redeploy" in the SBM Orchestration Guide.

Database Servers

Entering Database Server Information

Entering Database Connection Information

Configuring SQL Server Data Encryption Options

Retrying Orchestration Engine Upgrades and Clearing Warnings

Related Topics