In the last few months I got numerous questions if ESR is needed for Duet Enterprise.

ESR is not needed when a solution only consists of Reporting, Workflow and Starter Services.
This is when you install Duet Enterprise out-of-the-box.

But when custom development is needed like instance of ESR is needed. An example is exposing HR information,workflows and other HR related information. This is not standard (yet) in Duet Enterprise. So you will need to do some ABAP work and some other work.

A tip here, if you are going to use an ESR, use the one from a PI 7.1 system as it comes with it’s own SLD (needed for creating own namespace)

We got this error last when trying to get SSO working between NetWeaver and ECC.

To solve this check transaction SSFA on client 000 and your current client and delete the “Standard application” entries (maybe take a screenshot to re-enter them just in case).

Then try again. Usually setting these values in the profile should be enough – you do not have to maintain the
standard application in SSFA as well.

SAP Marketplace Duet Enterprise downloads have different version numbers. Due the different version, the connection will not work correctly. SAP downloads are all based on Feature Pack 2 but the SharePoint part is still Feature Pack 1
The solution to the problem is to uninstall the feature pack on SharePoint 2010 and install feature Pack 2 from the MSDN site from Microsoft.

This will get the connection between SharePoint and SAP working correctly

SAP released a Self-Paced Duet Enterprise site with video what are all about Duet Enterprise. It begins at a beginner and this will go up to more advanced.

http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=272531775

We were setting up an Microsoft and SAP combined environment for a Duet Enterprise installation.
After we finished the Domain installantion and the installation of SharePoint we started installing SQL Server for SAP ECC.
This install is slipstreamed, aka completely automatic. But the latest VBS script what is shipped from SAP for the installation of SQL Server contains some small errors.
The install location paths contain spaces, which are deadly for these types of installation.

Error:

MSI (s) (98:5C) [11:55:26:478]: PROPERTY CHANGE: Adding PATCH property. Its value is ‘H:\SAP\MS SQL SERVER 2008 R2 RDBMS SP02\x86-x64-IA64\EnterpriseEdition\PCU\x64\setup\sql_common_core_msi\sql_common_core.msp’.
…
[11:55:26:493]: MainEngineThread is returning 1639
Info 1639.Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
;”H:\SAP\MS
Solution:

‘H:\SAP\MSSQLSERVER2008R2RDBMSSP02\x86-x64-IA64\EnterpriseEdition\PCU\x64\setup\sql_common_core_msi\sql_common_core.msp’

Endly, after a few months waiting the long awaited feature pack is here. There are some mayor improvements as the new SAP NetWeaver Gateway 2.0 but also other cool features to get you’re Microsoft – SAP platform up2speed.

read more on http://blogs.technet.com/b/tothesharepoint/archive/2011/12/07/feature-pack-1-for-duet-enterprise-is-available.aspx

good information about Azure Security:

• SQL Azure Security Overview –  http://social.technet.microsoft.com/wiki/contents/articles/overview-of-security-in-sql-azure.aspx

• Securing SQL Azure –  http://technet.microsoft.com/nl-nl/magazine/hh351833(en-us).aspx

• Security Guidelines for SQL Azure – http://social.technet.microsoft.com/wiki/contents/articles/security-guidelines-for-sql-azure.aspx

• How Do I: Configure SQL Azure Security? – http://technet.microsoft.com/nl-nl/cloud/ff772115.aspx

BizTalk360 is released! See the new features and possibilities on the BizTalk 260 site.

http://www.biztalk360.com/Default.aspx

Since a while I am reading more about LEAN and how to use it for Software Architecture. While reading and searching I found this post about the topic.

Hopefully I will find the time to do more searching and researching how to use LEAN for software architecture

Found a nice blogpost about Software Architects.

Link to the blog