XI / PI in high availability setups

Did you install XI / PI in a high availability setup?
There is quite a bit of post processing needed to fully exploit these setups.
Look at the below SAP notes :
Note 1052984 - Process Integration 7.1 - High Availability
Note 951910 - NW2004s High Availability Usage Type PI

SAP GUI 7.10 SP 13 - Support for Office 2007 Formats (*.docx and *.xlsx) and for Internet Explorer 8

SAP released SP13 for SAP GUI beginning of May. This service pack brings along two important new features:

1.Support of IE 8 in SAP GUI, see SAP note 66971
2.Support for Office 2007 files (*.docx and *.xlsx), note 1286768

“With new changes done in SAP Office Integration, both old .DOC & .XLS as well as new *.DOCX & *.XLSX files of MS Office will be supported.
Previously from SAP Office Integration it was only possible to work with compound document formats. As new Microsoft Office 2007 (*.docx, *.xlsx) files are non-compound document, it was not possible for SAP Office Integration to support the same. Now *.DOCX and *.XLSX format are also supported.”

SAP changed this in SP 13 for SAP GUI and DOCX as well as XLSX files are now supported. See also SAP note 1286768.

TMS setup in high availability systems

When you setup the transport system in a landscape,SAP automatically generates
RFC destinations to the different servers.But they only point to one host by default and cannot be changed in SM59.
SAP Note 943334 can help you with this. It uses report 'TMS_MGR_LOADBALANCING' to change the definitions in STMS to access the systesm via their message servers and then update SM59.
Now transport can happen as long as 1 instance per system is up.