| |
Results |
|
About integrating PPM/Mariner and SBM
|
In this integration, SBM becomes the central point of activity. All of the data manipulation and updates are done through orchestrations . This gives you the advantage of keeping all of your code together in one place, making it easier to organize and maintain.
|
|
|
|
Mariner web services fault can't be caught in Business Mashups
|
If you try to catch a fault from any methods of the Mariner Web Services in a Business Mashups orchestration , this will fail.
|
|
|
|
After upgrading PPM, the integration with SBM no longer works
|
Login to the SMB Application Administrator ui and on the left click on the " Orchestration Engine" | "Event Manager Log" screen. This screen is helpful because it will show any events that have been received by SBM. In the example above you should be able to scroll to the end of the log and see an event called "IdeaUpdate" in the type column.
|
|
|
|
Mariner integration with SBM fails due to authentication error
|
Mariner integration with SBM fails due to authentication error
|
|
|
|
When I go to the SBM login screen there are no images, the background is white and the page looks way out of alignment.
|
When I go to the SBM login screen there are no images, the background is white and the page looks way out of alignment.
|
|
|
|
Would like to be able to update existing Mashup Tool Event Mapping
|
The Mariner release number is being passed to SBM as the "Product Version". Therefore, with each release of Mariner, the version number changes and the Mashup Tool Event Map must be recreated. "Product Version" is not really a good name for this field.
|
|
|
|
Would like to be able to update existing Mashup Tool Event Mapping
|
The Mariner release number is being passed to SBM as the "Product Version". Therefore, with each release of Mariner, the version number changes and the Maskup Tool Event Map must be recreated. "Product Version" is not really a good name for this field.
|
|
|
|
"Object reference not set to an instance of an object" when navigating in Mariner
|
After successfully logging in to Mariner, error messages like the following appear when trying to browse the Mariner interface. These errors occur when Mariner and Serena Business Mashups are installed on the same IIS web server. Mariner 2008 and SBM on the same IIS web server
|
|
|
|
On Update notifications shouldn't get sent for changes not in Attribute History
|
In other words if the fact that an attribute changed wasn't deemed important enough to show in the attribute history tab then an on update notification shouldn't fire either. Another side effect of this issue is that when the nightly post job runs it causes all the investments in the system to get an update which in turns causes notifications to be sent for on update and each one firing to the sbm server. During this time the scheduler service is using around 4gb of ram and throwing out of memory errors.
|
|
|
|
Mariner 2008 R3.04 Patch Release
|
DEF167105 ‘onbeforesave’ javascript event is not firing DEF167238 Mariner integration with SBM fails due to authentication error DEF167633 Rich text fields should keep line breaks on custom reports
|
|
|
