Upgrading from SBM 2008 R2.X

Remember the following points when upgrading your existing event definition WSDL files from SBM R2.X to the current version.

Replace the SBM 2008 R2.x Event Manager .wsdl and .xsd files with new ones from the Advanced Orchestration Package.
Change the type of <your product value> EventBaseType's EventId to SourceEventIdType.
You might need to update your clients to set ALFSecurityType in order to fulfill the authentication requirements if you choose to use Single Sign-On (SSO).

Starting in SBM 2008 R3, there is an authentication mechanism for external events.
Note: The following information only applies to systems where external events were used with orchestration workflows in which SSO was not used:
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. Security tokens are now 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, visit the Knowledgebase and search for no_authentication.

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, visit the Knowledgebase and search for no_authentication.

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 as you upgrade. 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.

Upgrading from SBM 2008 R2.X

Related Topics