SAP NW Newbie

http://publib16.boulder.ibm.com/cgi-bin/ds_form?lang=en_US&viewset=AIX

To determine if XI messages are the cause for start-up problems try the following: 1. Start the offline config tool from shell: /usr/sap/[SID]/[Instance]/j2ee/configtool/offlinecfgeditor.sh 2. Browse to "cluster_data/server/[NodeID]/cfg/services" and switch to 'edit' mode. 3. Open Propertysheet "com.sap.aii.af.ra.ms-runtime" and set startup-mode = manual. 4. Save and restart the cluster node. If J2EE engine comes up, change the problematic message's status to FAIL at database level and undo the above changes. SAP Note 994433

To prevent a virus attack that uses AutoPlay feature, turn off the feature on XP 1. Go to Start --> Run, and type Gpedit.msc (If this gives you "Access is Denied" error, g to Start --> Run , type system32. Right click on Gpedit.msc and Open With mmc.exe (you can access it from System32)) 2. Browse through Computer Configuration, Administrative Templates and click on System, Turn off Aotoplay and Properties 3. Click Enabled , select All drives in the Turn off Autoplay box to disable Autorun on all drives. 4. Click OK and restart the computer

This has happened to us when one of the developer's deleted other's XI objects by mistake. This trick was helpful in saving a lot of rework/restore time. If you delete any XI object by mistake, you can recover them by creating a dummy object with the same name and activating the original one from history. This method may not work on a few objects. If you choose to export the object from another system (ex: from QA to Dev) in the landscape, make a note of Namespaces in SWCV. During import, the SWCV also gets updated and it might cause the newly added Namespaces (Dev system's SWCV may have more Namespaces in its list) and their objects to disappear (not deleted)

If you find Archive/Delete jobs not clearing off messages (causing the Persistence Layer fill level to continuously increase); if the old messages were processed by the IDoc Adapter, check if SXMS_REFRESH_ADAPTER_STATUS job is running properly. Check its variant and see if it selects the messages properly. This job checks the status of messages that were sent to the IDoc adapter. Since the IDoc adapter does not send response messages, it is not automatically known whether a message was processed or not.