</Setting> </Setting> At this point, the Dimensions CM user can login using SBM SSO only if the user name exists in SBM. Step 3 is only necessary if you do not want to require your CM , RM or other SSO user to be in SBM.
jboss instances running the orchestration engines we get a FATAL error each time jboss is started. This only occurs when there is no mashup manager installed on this jboss instance.
A JBoss instance that runs the orchestration engine throws errors each time Jboss is started. : ERROR 2010-05-21 12:30:51,932 STDERR -- LoggerWrapper.loadLogger: Loaded Common Logger class: com.serena.eventlog.internal.logger.LoggerImpl : INFO 2010-05-21 12:30:51,963 mashupmgr.EventLog.Server -- Initializing event log...
The "renew" utility is an alternative to the "purge" utility. The purge utility allows you to remove completed instance data from the orchestration database. Renew addresses situations where this is not sufficient.
When setting up SSO for both CM and SBM, you can use either the CM or SBM identity store for users, if you use CM , then the Mashup Manager "logon as" functionality will not work.
Click the View Examples link in the Connection Properties area, and then select the JBOSS jBPM example to add it to the URL list. Change the server name and port to those for the machine on which the Orchestration Engine is installed . Click OK.
