Friday 22 June 2012

Changing IP address in SAP systems

Internally, SAP systems use host names to communicate. As a result, you should experience no problems when you change an IP address.


Theoretically, you only need to make changes at operating system level:

- /etc/hosts

- /etc/services

- DNS entries

- Routing tables

However, you should err on the side of caution and check the following in the SAP system:

- Transaction SM59, table RFCDES, also see Note 88346 for additional information

- Transaction SM55, if you are using IP addresses here, you must adjust them

- Transaction SM51, check for consistent host names

- Transaction SMLG, check whether the entries for the server groups have been created with IP addresses

Also ensure that changes are not only made in the affected system but in all SAP systems, clients, and external programs that communicate with the affected system in any way.

Outside the SAP system:

- saprouter, adjust the saprouttab to the changes

* If the saprouter receives a new address:

You should inform SAP on  this change (for sapserv3).

Open a message on the 'xx-ser-net-chg' component and inform us of the address change.

- Adjust the IP addresses so that the service connection continues to function

- If you use an APO system, see Note 154997

Depending on your system landscape and configuration, additional relevant points may be added.

Thursday 21 June 2012

JSPM – Java Support Pack Manager

Check whether the used JDK version and the Java VM settings of the Java runtime system comply with  the requirements in the SAP Note 723909. Update the JDK and adjust the settings if necessary. You can update all software components of SAP products that are deployed on the system by applying a support package stack. Support package stacks are defined by SAP collections of support packages for software components that work best together. In addition, you can apply a support package stack, which contains newer versions of SAP software components that have been modified in the NWDI
Before you can apply a support package stack of a given level, you have to update JSPM to the same level by applying it as a single support package The update of JSPM does not require a restart of the J2EE Engine and does not affect the system operation. If the stack is produced for this system by the Maintenance Optimizer, this option will: upgrade with the included components all components that are already deployed on the system to a higher release or to the same release but a higher support/patch level install new components if there are any in the support package stack.

Prerequisites

The settings of your system are according to note 723909.

The SAP NetWeaver Application Server Java (AS Java) and the database have been backed upDirectories and files have not been deleted, renamed, or created in the following directories and their subdirectories: /usr/sap//SYS/exe and /usr/sap//SYS/profile. Otherwise, JSPM cannot detect the kernel and the system profiles, and cannot be started. If a backup of the kernel and the system profiles has been required, it has been created in a different directory.

If your database is MaxDB, the overwrite mode for the log area has been set

The support package stack you want to apply and the corresponding stack definition XML file have been downloaded to the global EPS inbox directory /usr/sap/trans/EPS/in. For more information about SAP products, see SAP Service Marketplace at service.sap.com/sp-stacks.

If the support package stack you want to apply includes the Enterprise Portal, the SDM timeout for the automatic start/stop of the J2EE Engine has been increased to 2 hours.

The adm user has Read permissions for the global EPS inbox directory /usr/sap/trans/EPS/in.

The database and the SDM repository have been synchronized.

There is enough disk space..

Maintenance Optimizer and Support package definition file creation

More information at help.sap.com ® SAP Solutions ® SAP Solution Manager ® select a language ® Change Management ® Maintenance Optimizer

Download the support package stack with all the usage types that need to be updated and the Support Package Stack definition file.

Note: The Support package definition file can be created as follows:

After adding the support package stack in the download basket, you can choose the option to “save in a file”. Right click on the option tab and save as XML file. You can also save it as a CSV file. You can also find more details in SAP Note 884537

Copy the downloaded Support Package files and the definition file (XML file) to the JSPM inbox. [:\\usr\sap\trans\EPS\in]

Note: There must be one and half times as much disk space available as the SP files to be deployed in the JSPM inbox for temporary file transfer by SDM.

To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available disk space during the update process, you can change the file transfer directory of SDM in a system by using the following commands:

cd StopServer.bat

sdm.bat jstartup "mode=standalone" sdm.bat filetransferdir "dir=" sdm.bat jstartup "mode=integrated" StartServer.bat

Check whether the used JDK version and the Java VM settings of the Java runtime system comply with the requirements in the SAP Note 723909. Update the JDK and adjust the settings if necessary.