SAP NW Newbie

SAP has provided Web Diagtool that lets you set trace levels on a few locations and collect the information as zip file. It is much convinient to use diagtool compared to log configurator when the problem can be reproduced on demand. Once you have deployed the sda file attached to SAP Note 1045019, you can call the diagtool using http://<host>:<port>/diagtool Usage: 1. Open http://<host>:<port>/diagtool 2. Select "All" for "Component" 3. Using the "Search Pattern", add the location on which you would like to collect the trace 4. Press Start. 5. Reproduce the problem 6. Press Stop, when the error occurs. 7. The trace is presented as html. You can also downalod the trace as a zip file. - You may have to increase "Maximum number of collected records" property if you wish to run the tool for a long duration. - Before starting the diagtool, make sure you are ready to reproduce the problem. The following...

Copy the iaik_jce.jar or iaik_jce_export.jar from the SCS Instance \\<HOST>\SAPMNT\<SID>\SYS\global\security\lib\tools\iaik_jce.jar to your CI \usr\sap\<SID>\JC<Inst. Nr.>\j2ee\admin\lib

This means that the Adapter service/application hosting the CC is stopped. Check the corresponding Service to verify if it is running. In case of 3rd party adapters like Seeburger, check the applications on Deploy service. If the problem repeats with every restart, chances are that the service or application is set not to start automatically. The following example shows how a Seeburger application is set not to start:

Attempt to start the J2EE engine fails with an exit code -11113 (check dev_* trace file). The exit code -11113 means that a mandatory service has failed to start. You need to check the std_* trace file to determine which service has failed. Sample Error 1: Core service p4 failed. J2EE Engine cannot be started. Solution: Check bindHost property using Config Tool. Navigate to configtool -> Instance -> dispatcher -> services -> p4 -> bindHost Make sure that a correct value is maintained there. Remove any additional IP(backup IP) maintained. Sample Error 2: Core service file failed. J2EE Engine cannot be started. Caused by: org.omg.CORBA.INITIALIZE: cannot instantiate com.sap.engine.system.PortableRemoteObject vmcid: 0x0 minor code: 0 completed: No Solution: In this example, one of the Java parameters is set incorrectly. The parameter should have been com.sap.engine.system.PortableRemoteObjectProxy instead of com.sap.engine.system.PortableRemoteObject. Naviga...

update-apt-xapian-index is truncated and shown as update-apt-xapi in top tool. This process is responsible for maintaining an index of packages to speed up search on Synaptic and is scheduled as a cron job (/etc/cron.weekly). This is the cron job, triggering the process: #!/bin/sh CMD=/usr/sbin/update-apt-xapian-index IONICE=/usr/bin/ionice # Rebuild the index if [ -x $CMD ] then if [ -x $IONICE ] then nice $IONICE -c3 $CMD --quiet else nice $CMD --quiet fi fi Edit the lines to show the following: #!/bin/sh CMD=/usr/sbin/update-apt-xapian-index IONICE=/usr/bin/ionice # Rebuild the index if [ -x $CMD ] then if [ -x $IONICE ] then nice -n 19 $IONICE -c 3 $CMD --update --quiet else nice -n 19 $CMD --update --quiet fi fi The modification will help reduce CPU usage . -n 19 option gives least favorable scheduling priority. --update option causes the process to update the index instead of rebuilding it every time.

The SAP architecture uses Message Server for handling cluster communication instead of each node contacting with every other node.  Had each node been designed to talk to every other node, it would need an open connection per node (point-to-point network was used in 6.20 architecture). For such a setup, the required number of connections would be n*(n-1)/2. The number of connections (network overhead) would increase as a quadratic function of the number of nodes. By using Message Server as the central service (star network) for cluster communication, the number of connections would be n, making it a linear  function of the number of nodes.

There is an incompatibility between the way passwords are stored in older R/3 systems and the newer ones. When using a newer SAP system (> 640) to connect with older R/3 systems (<= 640), make sure that the password used for RFC authentication is not longer than 8 characters and is in uppercase letters. The older systems the password is converted to uppercase and truncated to 8 characters.