Created By : Neval
Ozturk
Last updated : 8/11/2005
ü Go through OSS notes 492222, 492221 492208.
ü Make sure Java version 1.3.1 is installed
ü Make sure Perl version is installed and at
least 5.005_03.
ü Create/make sure you have
the following filesystems- (OSS note 492221):
o
/oracle/stage
3GB
o
/tmp 1.5GB
o
/oracle/SID/920_64
4GB
o
At least 4
sapdata filesystems
o
/oracle/client
100MB freespace
o
origlog and
mirrlog has at least 120MB each
o
Filesystems
are set > 20 and FILE = -1
ü lsdev –C –t aio should return Asynchronous
I/O as “Available”
ü Make sure AIX patch IY63076
is installed for AIX 5.3
ü Download Opatch and latest
Oracle patches according to OSS note 629588. (These are already downloaded to
/sapcd on sapaps)
ü Use LIBPATH instead of
LIB_PATH for AIX
ü Make sure
/etc/security/user has 640 (-rw-r-----) and owned by root
ü Make sure no entries in
/etc/services for 36XX, 32XX, 33XX, 48XX.
ü Make sure C++ > 5.0.2.0
o
llslpp
–l xlC.rte
ü /usr/sap/trans should be owned by root with 775
ü Make sure JAVA_HOME is defined in root’s
profile
ü Move /usr/java131/jre/lib/ext/*.jar files
unitl the end of installation to some other extension (Installation guide page
26)
ü OSS Note 146528, 128935. Check the
parameters, Check RAM, SWAP space
ü Make sure perfagent is installed on the
Solution Manager system (Installation guide)
ü BD54: Create a logical system(OR Define
Logical systems through V_TBDLS at SM30.)
ü Set up STMS as a single system
ü Apply the latest support packs (At least
Basis patch 51)
ü Apply the latest ST-PI and ST-A/PI:
Ø Check OSS note 539977, 597673, 69455, 666043.
Ø For systems <=31I check OSS notes 69455, 187939. These
will bring:
1. RTCCTOOL: SAPKVSDE03
2. ST14: SAPKVSDA30
Ø Implement 712757, and 207223.
ü Create a new client, 100, from Client 001
with User Master data. Use SOLMAN user.
ü SMSY_SETUP choose LIS. Click on Schedule
data transfer from LIS/LCR à Schedule the job to run daily at 22:00. LANDSCAPE FETCH job will be created.
ü Make sure OSS1 is configured and SAPOSS RFC
connection is there.
ü Check OSS notes 752570 and 666043.
ü Install CCMSPING:
Ø According
to OSS note 209834 and 381156 download CCMAGENT.SAR and uncar the SAR file.
Ø Make
sure that /etc/services and /etc/hosts has all the entries for the
systems/hosts to be monitored.
Ø Register the CCMSPING and run it:
1. ccmsping –R
2. ccmsping –DCCMS
Ø
Availability
Monitoring configuration: RZ21, build or check the sapmsg.ini file on your
desktop. It is usually located at c:\winnt\. Make sure all the boxes you want
to monitor are listed as SID= hostname. Upload this file at RZ21 Technical
Inrastructureà
Configure Availability Monitoring.
ü In SMSY at Solution Manager System, Create
RFC destinations. Remote logon should work for SOLMAN (should be a dialog user
on both sides, Solution Manager and Satellite systems, otherwise Analysis
methods do not work at RZ20 in Solution Manager system) To avoid to many RFC destinations
and user definitions, I prefer one single user and one single RFC destination
for analysis, data collection etc. At satellite systems, I used
SOLUTION_MANAGER RFC destination. At Solution Manager, I used Logical System
names as RFC destination naming convention. I used the same SOLMAN user all
across. Depending on the Solution Manager system usage, such as who will be
connecting and if there should be any limitation on accessing satellite
systems, you may prefer to follow SAP’s standard method create multiple users
with suggested roles and multiple RFC destinations. I prefer to protect
Solution Manager System accessibility – Only SAP Basis Admins!
ü Create hosts, databases, and systems. !!!
Attention attention!!!
Ø Hosts: Do not forget to define IP. D
Ø Databases: Do not forget to define the
release and Manufacturer of the database. Otherwise, monitoring trees do not
get activated at “solution_manager” transaction.
Ø Systems: Create a system by assigning the
type of SAP solution then enter the logical system name and “Read System Data
Remote” It should be able to populate the data if you defined the RFC
destinations right at both sides. If not troubleshoot the user ID/ password or
RFC definitions on both sides.
ü