SAP Solution Manager Series: Preparation

“Success depends upon previous preparation, and without such preparation there is sure to be failure.” - Confucius

To get a good picture on what I currently have, here's an inventory of hardware and software:

HARDWARE:
IBM x346 2-way dual core processor with 4 GB RAM and 100+ GB disk

SOFTWARE:
Oracle 10.2.0.2.0
SAP Solution Manager 4.0 SR2
Redhat Linux Enterprise Edition Release 4

First off is the installation guide. Download the Inst. Guide SAP Solution Manager 4.0 SR2 Linux - Oracle PDF file from http://service.sap.com/instguides > SAP Components > SAP Solution Manager > Release 4.0

For the system variant to be used, I am going to use the Central System (all instance in one host).


For the Basic SAP System Parameters, here's the values I choosed:

SAP System ID: SSM
Database ID: SSM
Instance Number: 00
Name of Instance Host: sap23
SLD Destination: sap23
Code Page: Unicode

Other parameters not mentioned above are set to default values.

To check if the hardware and software requirements meets the requirements, make sure that all items mentioned under Requirements for Linux (page 43) as well as Requirements for Central System (page 45) are satisfied. You can also run the Installation Prerequisite Checker that is part of the sapinst. I also used the script mentioned in Oracle Metalink Note 309401.1. The script will perform a series of checks from CPU, OS version, swap space, installed RPMs and a lot more.

For the file system, make sure that the following file system is set properly:



Recommended sizes are indicated in page 57. For the oracle file system, check page 60.

For the Java Development Kit, I used the one from IBM as mentioned in SAP Note 861215. If you use a different platform, check SAP Note 709140.

I normally put the installation cds to the disk so that I don't mount/unmount the cd drive during the installation. Here's the items that I normally copy to their corresponding folders in the disk:

Oracle 10g RDBMS CD - /extra/solman/ora_rdbms
Oracle 10g Client - /extra/solman/ora_client
Oracle 10g Patch - /extra/solman/ora_patch
Solution Manager 4.0 SR2 Export CDs - /extra/solman/export
Solution Manager 4.0 SR2 Installation Master Linux - /extra/solman/master
Solution Manager 4.0 SR2 Java Component - /extra/solman/JAVA
NW 2004s SR2 UC-Kernel 7.00 Linux on x86_64 64bit - /extra/solman/kernel

Next Picture: SAP Solution Manager Series

My next post will be a series of how-tos. I'll try to cover as much as I can for the following topics:

1. Installation Preparations.
2. Solution Manager installation.
3. Client Copies.
4. Connecting Satelite Systems to the Solution Manager.
5. Setting up RFC connections.
6. Configuring the Service Desk.

SU53 for the web?

i recently encountered a problem with missing authorization for web users who are shopping online using the mySAP SRM. for unknown reason, the su53 doesn't display the missing authorization objects. as a workaround, i enabled the authorization trace using ST01.


just tick the authorization trace, activate the trace (trace on) and let the user run the problematic transaction. wait until the error appears before deactivating the trace (trace off).

to view the results, just click on the analysis button to view the missing authorizations.

cleanup script for brbackup to disk

Here's the script I used to cleanup the backup directory I used for brbackup to disk which I discussed from the previous post:

#Find directories under sapbackup backup dir and delete files older than 46 hours. Logs are stored in the log folder
find /backup/XXX/sapbackup/bdu* -type d -mmin +2760 -maxdepth 1 xargs -i ksh -c " echo `/bin/date +%y%m%d%k%M` {} >>/backup/log/sapbackup.log; rm -Rf {}"

#Find files under saparch backup dir and delete files older that 3 days. Logs are stored in the log folder
find /backup/XXX/saparch/*arch* -type f -mmin +4320 -maxdepth 1 xargs -i ksh -c " echo `/bin/date +%y%m%d%k%M` {} >>/backup/log/saparch.log; rm -Rf {}"

Make sure to test it thoroughly.

Disclaimer: use at your own risk!

brbackup to disk

no tape drive locally attached to the server? no backup agent for sap? try placing the backup to a local drive (or even NFS if you have the guts to face the wrath of your network admin)

first, setup the directory where you want the backup to store the database files. make sure that the owner and rights are set correctly. if you don't know how, try to google chown and chmod.

then edit the init<SID>.sap. the following parameters needs to be modified:
backup_dev_type = disk
backup_root_dir = <brbackup backup directory>
archive_stage_dir = <brarchive backup directory>

if you don't have much disk space in the backup directory, try enabling the compression by modifying:
compress = yes

and make sure that compression command is set
compress_cmd = "gzip -c $ > $"

run brbackup or braarchive to test your backup. in the header you will see something like this:


make sure to clean up your directory. i got some scripts which i'll post next time.