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.

AIX Virtual Memory Management: Tuning Recommendations

I recently had to deal with a system which had a lot of RAM available but was still paging a lot. It was running AIX 5.3. Eventually we found note 973227 which gave us the correct parameters for tuning SAP virtual memory. Also look at note 1157425 which gives some details on configuring the correct amount of AIO processes for AIX.

Security Troubleshooting Guide For NetWeaver J2EE 640/700

I found a very nice security troubleshooting guide attached to note 1296330.
Below is the index of the document :

Chapter 1 - Authentication

Read this chapter if you have general problems logging in to a resource on the SAP J2EE Engine (NetWeaver Administrator, User Management, System Information) or to standalone SAP applications which connect to the SAP J2EE Engine (Visual Administrator). No single sign-on must be active on the system.

Chapter 2 - Authorization

Read this chapter if you see error messages saying that the user is not authorized to access the requested resource.

Chapter 3 - Session Management

Read this chapter if you think that the security sessions of the user expire when they should not or if a user is incorrectly logged in to the SAP J2EE Engine as another user.

Chapter 4 - Single Sign-On

Read this chapter if you have a single sign-on scenario and it fails.

Chapter 5 - SPNego

Read this chapter if you have setup the SAP J2EE Engine to use Kerberos authentication via SAP's SPNego mechanism.

Chapter 6 - SSL

Read this chapter if you have enabled communication over the SSL protocol and it fails.

Chapter 7 - Key Storage

Read this chapter if you see error messages saying that there are problems with Key Storage views or if you have problems importing/exporting certificates.

Change Livecache user password

I recently had an issue changing the Livecache user in a SCM 5.0 system.
Changing the password in the ABAP stack transaction LC10 was easy.
But you also have the change the password in the Livecache database.

So do that you need the following commands.

(XXX is the database name)
1.Start the Livecache DB command line : dbmcli -d XXX -u control,[password]
2. Login as Superdba : sql_connect superdba,[password]
3.Change Livecache user password : sql_execute alter password sapr3 [new password]
4. Make the new password known : user_sap sapr3,[new password]

If you don't know the SuperDBA password you can execute the following command after step 1 above : user_put superdba password=[new password]

Solution Manager EHP1 : upgrade steps

I recently upgraded 2 Solution Manager 4.0 systems to EHP1 and here is the steps I followed:

1.Update Java stack to SPS17 (including IGS) via JSPM.This step is a prereq. Time = 5-7 hours.
2.Update Java stack to EHP1 (including IGS) via JSPM. Time = 3-4 hours
3. Update SPAM/SAINT patch level to 33.
4. Update Kernel to 7.01 patch level 23.
5.Install EHP1 via SAINT on ABAP stack.Time = 9-15 hours

Notes :

• You need BI_CONT 7.03 installed in the ABAP stack before you can upgrade to EHP1.
• Make sure the Java Heap parameters is set correctly before running JSPM
• You have ample free disk space in the disk drive that SDM in running in, as it creates files temporariliy when compiling in JSPM.
• Make sure all the plugins in the system is upgraded to it's latest level before installing EHP1.
  

Below a screenshot of what SAINT looks like before your start EHP1 install :

Upgrading Solution Manager 7.0 to 7.0 EHP1 (Stack 18)

Solution Manager 7.0 EHP1 (Stack 18) is now available for download. Please make sure that you read note1169247 before starting the upgrade. Also check out this detailed presentation on what EHP1 contains.