Contents

1. From the Windows Start menu, open the Control Panel and select User Accounts.
2. Turn off UAC:
   • On Windows 2008, open the User Accounts window, click Turn User Account Control on or off and clear the Use User Account Control (UAC) to help protect your computer check box.
   • On Windows 2008 R2, click Change User Account Control settings, and move the slider to the Never notify position.
3. Click OK.
4. Reboot the server and perform the install.

After the installation is finished, you can enable UAC; however, you must disable it again if you attempt to uninstall SBM.

msiexec -?

You can use the SBM System Administrator that is installed by the suite installer on a 64-bit Windows 2008 R2 server to upgrade the database. As part of the upgrade, review and upgrade any scripts and APIs that were originally created on a 32-bit operating system to ensure that they also run on a 64-bit system. For example, if you have any scripts that load .dll files, those dll files must be upgraded to run on a 64-bit machine.

The hardware requirements for SBM running on a Windows 2008 R2 64-bit operating system are as follows. The memory requirements are greater than those for a 32-bit operating system.

• Recommended Requirements – 2 GHz or higher multi-processors; 16 GB memory; 10 GB operational disk space.
• Minimum Requirements – 800 MHz or higher single processor; 8 GB memory; 2.5 GB operational disk space.

If you previously designated a SID for Oracle, then that SID is automatically used in the Service name field in SBM Configurator. Verify with your DBA that the correct service name is now used in the Database Servers tab of SBM Configurator.

For example, you can back up your current Common Log database on your production server and restore it to a new space on your development database server. Once the data has been restored in the development database, purge the existing Common Log database space on the production database server and create a new database space for your test server (this results in two blank databases--one for test and one for production). Run SBM Configurator on the test and development SBM servers and update the Database Servers tab with the database connection information for the two new unique Common Log databases.

This ensures that you have unique databases for the Common Log in each environment and it also moves your existing Common Log data from the previous production space into the new development space.

• The internal state and transition names are derived from the internal name of their defining workflows. These internal values are set when you open a process app in SBM Composer for the first time after upgrading to SBM 10.1 or later versions.
• You can change the new default internal names for states and transitions at any time before the process app is published for the first time in SBM 10.1 or later versions. Once the process app is published, the internal names cannot be changed.
• The internal names for existing projects are automatically created upon upgrade to SBM 10.1 or later versions. When you create new projects in the Application Administrator in versions after 10.1, SBM automatically creates the internal project name for you.
  Note: During promotion, if the internal project name clashes with an existing internal project name, the internal name in the target database is affected in one of two ways:

  • For new projects that are added during promotion, when a conflict occurs, the project name in the target database will be a blank or empty string.
  • For existing projects that are updated during promotion, when a conflict occurs, the project name in the target database remains unchanged. If the internal name in the incoming XML does not conflict with the internal name in the target database, then the promoted project's internal name is used.

For customers currently using MAPI, perform the following steps to configure the Notification Server to connect using MS Exchange:

1. Run the SBM Configurator on each server where the Notification Server is installed.
2. In the Mail Services tab, select the Notification Server tab.
3. In the E-Mail Server Type drop-down list, select Exchange.
4. Enter your current Exchange server version, connection URL, and system user credentials.

You might use the Exchange option if your company does not allow connection through SMTP. The Exchange protocol is also available for use with the Mail Client in the event your company does not allow connection through POP3 or IMAP. If no such restrictions exists, consider choosing SMTP for the Notification Server and POP3 for the Mail Client because they enable faster connection speeds than MS Exchange.

• If you are upgrading from a release earlier than SBM 2009 R4, you will see no change; no icon will appear on the application tab.
• If you are upgrading from SBM 2009 R4 or later, and changed the default red icon to something else, you will see no change; your icon will still appear on the application tab.
• If you are upgrading from SBM 2009 R4 or later, and kept the default red icon, you will no longer see the icon; the application tab will be blank. If you want to restore the red icon, you can select it from the list that opens when you select "New image..." from the drop-down list in the application editor in SBM Composer. Redeploy your process app after making this change.

• If SSO was enabled in a prior release, after the upgrade to 10.1.1.3, deployed apps will use Security Tokens automatically without having to be redeployed.
• If SSO was disabled in a prior release, after the upgrade to 10.1.1.3, deployed apps will not use Security Token authentication unless they are redeployed (even if SSO is enabled after the upgrade).

• With the use of security tokens for all communication with SBM components regardless of authentication method, it is now necessary to provide credentials in the User element of external events that are processed by the Event Manager. Credentials must be supplied in order to receive a security token.
• Previous SBM releases allowed anonymous events if SSO was disabled. As of SBM 10.1, security tokens are used in all underlying communication. As part of the upgrade process, in order to still accept external events without credentials, the Event Manager is automatically configured to continue to accept external events without authentication credentials. If SSO was enabled prior to upgrade, then it is assumed that external events always included credentials and will continue to do so in your environment.
  Important: If you are currently using external events without SSO, it is strongly recommended that you adjust the source of those external events to now include credentials. Once you adjust the external source to include a credential, you can then manually override the Event Manager settings by setting the no_authentication parameter to “false” in the alf.properties file. For configuration instructions, see solution S138463.
• After upgrading, the no_authentication setting is independent of the SSO setting. If you are performing a new installation, you can override the default behavior for the Event Manager and enable it to accept external events without credentials. For configuration instructions, see solution S138463.
• For SBM Application Engine Web services, the SBM Application Engine auth still overrides the security token auth. In some cases, this is useful in day-to-day operations and may be useful if you are upgrading from versions prior to 10.1. For example, orchestration workflows that contain coded auth for the SBM Application Engine service calls will continue to work if the external event is changed to send a credential; the coded auth will override the security token and continue work as it did prior to upgrade.