I got a problem and just already found the solution this morning. I just want to share it

• Problem : Error occurred when accessing portal in dual-stack system -> The system is unable to interpret the SSO ticket received.

• Solution :Check expiration date of the ticket for Single Sign On between AS Java and ABAP. If it is expired, replace the ticket.

Procedure for replacing SAPLogonTicketKeypair for SSO :

1. Open Visual Admin.
2. Go to server_<ID number> – Services – Key Storage.
3. Check expiration date for ticket SAPLogonTicketKeypair.
4. If date is expired, rename or delete this ticket.
5. Click Create.
6. Fill the required field. Common Name should be unique. Entry name should be the same : SAPLogonTicketKeypair. Tick Store Certificate, Use RSA algorithm. Leave other field default. Then click Generate.
7. Export ticket SAPLogonTicketKeypair-cert as .crt format.
8. Login to ABAP in specific client which is accessed by Portal, ex : 800
9. Go to tcode STRUSTSSO2
10. Delete old certificate.
11. Import certificate .crt file mentioned above.
12. Click Add to Certificate List.
13. Click Add to ACL.
14. Save.
15. Finish.

Since April 2007 SAP Service Marketplace make a new rule for downloading Support Package files which has been released by that time. Want it or not, SAP ‘push’ the user to install SAP Solution Manager to use its tool to confirm the file that will be downloaded. It’s just a little function from the Solution Manager’s ability. From my viewpoints, Solution Manager is one gate to communicate between SAP support, SAP customers and SAP partners. Many other functionality that we can use here. Apparently, I’m still learning about all of its features. The quick overview of Solution Manager’s features are :

• Implementing and Upgrading SAP Solution : central access to all tools of your project,
• Solution Monitoring : central system administration with Service Level Reporting Real-time System Monitoring,
• Service and Support : access to programs and services to monitor and optimize the performance and availability of your system landscapes.
• Service Desk, Solution support with workflow to create and process problem messages.
• Change Management : manage change request.

So, here’s the installation step for Solution Manager 4.0 SR1 Installation. This is for Windows Server 2003 OS and Oracle Database. When you open this pdf file, the password will be required. If you need the password, you ca leave your email in this comment. Please feel free to give comments and questions.

>> Download SAP Solution Manager Installation Steps >>

Here is an IDES installation for mySAP ERP 2005 , another name for ECC 6.0. This system is installed in Windows Server 2003 SP2 and Oracle 10.2 database environment. I just want to share the installation step. You can download the installation step here . The installation document is in .pdf format. Don’t hesitate to give comments if you have succeeded the installation.

Posted by: asfan

The SAP Patch Manager (SPAM) is the customer side of the Online Correction Support (OCS). Transaction SPAM lets you efficiently and easily imports SAP-provided support packages into your system.

Depending on the system used or the configuration of your system, you must apply different types of support packages. You can get the support packages in the SAPNet R/3 FrontEnd, the SAPNet Web FrontEnd, or on Collection CDs.

SPAM runs at the SAP transaction level, so that knowledge of the operating system is not required for handling the tool.

SAP now uses the term support package instead of patch.
Note that you can only use this transaction with SAP GUI for Java and SAP GUI for Windows.

The SAP Patch Manager offers you the following functions:

You can find the import status in your system at any time using transaction SPAM. Transaction SPAM is integrated into the SAP upgrade procedure.

The SAP Patch Manager informs you of the status of the step currently being executed in the status bar. If you want to know which steps are executed for which scenario, run the program RSSPAM10.

The following list explains the steps executed by SPAM in the order in which they are performed.
PROLOGUE
In this step, the system checks if you are authorized to import support packages.
CHECK_REQUIREMENTS
In this step, various requirements are checked for importing a support package, for example, the transport control program tp logging on to your system.
DISASSEMBLE
In this step, files from the corresponding EPS parcels are disassembled, or unpacked, and stored in the directory.
ADDTOBUFFER
In this step, the queue is put into the transport buffer of your system.
TEST_IMPORT
In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the support package is imported.
IMPORT_OBJECT_LIST
In this step, the object lists for the support packages in the queue are imported into the system.
OBJECTS_LOCKED_?
In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the support package is imported.
SCHEDULE_RDDIMPDP
In this step, the transport daemon (program RDDIMPDP) is scheduled.
ADDON_CONFLICTS_?
In this step, the system checks if there are conflicts between objects in the queue and installed addons.
SPDD_SPAU_CHECK
In this step, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).
DDIC_IMPORT
In this step, all the ABAP Dictionary objects of the queue are imported.
AUTO_MOD_SPDD
In this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.
RUN_SPDD_?
In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.
IMPORT_PROPER
In this step, all the Repository objects and table entries are imported. Then actions such as distribution, conversion, activation and generation occur.
AUTO_MOD_SPAU
In this step, the system checks if modifications can be adjusted automatically.
RUN_SPAU_?
In this step, you are asked to adjust your modifications to the repository objects by calling transaction SPAU.
EPILOGUE
In this step, the import of the support package is ended. The system checks if the queue has been completely processed.

Silahkan lihat dokumen PDF dibawah ini :

SAP Security

Uploaded by : BWi

Silahkan lihat dokumen PDF dibawah ini :

http://jelajahsap.files.wordpress.com/2008/01/connecting-sap-fax-server.pdf

Uploaded by : BWi

Posted by: asfan

In SAP, memory usage is divided into several areas. such as:
1. SAP Buffer
2. SAP Roll Memory
3. SAP Extended Memory
4. SAP Heap Memory
5. SAP Paging Memory
How to allocate the parameter value of them? How do they work?
What will happen if the parameter is set incorrectly?
Review this Overview SAP Memory Management

Posted by: asfan

Daily task:
1. DB13 – Database planning calendar
  a. check the DB check job
  b. check the whole online database backup
  c. check the redolog backup
  c. check the statistics optimizer job
2. DB02 – Database Performance
  –> check database size, free space, space critical, missing index, etc
3. DB12 – Backup Logs
  –> check database backup and redolog backup
4. DB16 and DB24 – Log of database operation
  –> check/monitor all database related job or activity
5. SM50 – Process overview
  –> check the runtime of program
6. ST06 – Operating system monitor
  –> check the CPU, disk, memory and filesystem utilization
7. ST22 – ABAP runtime errors
  –> check the generated errors and dumps
8. ST03N – Workload overviwe
  –> check/monitor the application performance and load
9. SM04 – User List
  –> check the connected user, idle user
10.ST02 – Tune summary
  –> check the application buffer usage, also roll memory,extended memory,heap memory

Weekly task:
1. SP11 & SP12 – TemSe administration
  –> check the outdated TemSe object
2. DB13 – Database planning calendar
  –> do the next extent of database
  –> do the database verification to check the physical structure
3. ST06 – Operating system monitor
  –> check the free space available

Monthly task:
1. SU01 – User maintenance
  –> change the admin password
2. ST06 – Operating system monitor
  –> check the free space available
3. DB02 – Database Performance
  –> see database statistics to estimate the database growth
4. DB13 – Database planning calendar
  –> do the clean-up log job
5. STMS – Transport management system
  –> clean-up the old transport request buffer

Posted by: asfan

This is the overal directory structure in SAP system.
Unix based: use /
Windows based: use <drive>:\

Shared directory:
/sapmnt/<SID>/profile  è  SAP instance profile
/sapmnt/<SID>/global  è SAP central system log
/sapmnt/<SID>/exe  è SAP executable application directory

Main directory:
/usr/sap  è  physical parent directory
/usr/sap/trans  è  transport directory
/usr/sap/<SID>  è  SAP system parent directory
/usr/sap/<SID>/SYS  è  contain common & global SAP system files (i.e. profile, global, and exe directory)
/usr/sap/<SID>/<instance_name>  è  contain SAP instance specific directories (i.e. data, log, and work)
/sapmnt  è  directory structure for sharing common files to all system belonging into the same group
/sapmnt/<SID>  è  link or share folder of directory /usr/sap/<SID>/SYS
/oracle  è  directory of the whole database system
/oracle/stage  è  directory that used for database installation and upgrades
/oracle/<SID>  è  directory of the whole database application and data files

Final directory:
/sapmnt/<SID>/exe  è  contain all SAP runtime program
/sapmnt/<SID>/exe/opt  è  contain optimized program
/sapmnt/<SID>/exe/dbg  è  program can run under symbolic debuggers
/sapmnt/<SID>/exe/run  è  actual runtime program (SAP kernel)
/sapmnt/<SID>/global  è  contain global & common data shared by all instance (i.e. central system logs & batch job logs)
/sapmnt/<SID>/profile  è  contain instance profile (startup, default, instance-spesific)

Temporary directory (normally refreshed when SAP instance is restarted):
/usr/sap/<SID>/<instance_name>/data  è  contain virtual storage data (i.e. user context & roll area)
/usr/sap/<SID>/<instance_name>/log  è  log entries generated by instance
/usr/sap/<SID>/<instance_name>/work  è  holds all error message & trace information for the instance process

Transport directory:
/usr/sap/trans  è  main transport directory
/usr/sap/trans/bin  è  contain TPPARAM file (global transport parameter)
/usr/sap/trans/data  è  contain transport data file
/usr/sap/trans/log  è  transport logs, trace and statistic file
/usr/sap/trans/buffer  è  special buffer with the SID of every system in the transport group (including control information)
/usr/sap/trans/cofiles  è  control file directory
/usr/sap/trans/sapnames  è  contain information of SAP User that performs export and keep tracks of each transport status
/usr/sap/trans/tmp  è  temporary directory
/usr/sap/trans/actlog  è  action log files (managed by SAP system)
/usr/sap/trans/olddata  è  archived transport files
/usr/sap/trans/backup  è  directory of logical backup with R3trans program
/usr/sap/trans/serial  è  contain serialization of tp

Posted by: asfan 

1. Login as root

2. Make new backup directory
cd /
mkdir SIDkernel_10102007

3. Create latest kernel backup
cp -pr /sapmnt/SID/exe/* /SIDkernel_10102007

4. Compare the original kernel and the backup
du -sk /sapmnt/SID/exe/ à 840413  /sapmnt/SID/exe
du -sk /SIDkernel_10102007 à 841992  /SIDkernel_10102007

5. Make new shadow kernel directory
cd /
mkdir newkernel_175

6. Copy the new downloaded kernel files into /newkernel_175

7. Unpack the new downloaded kernel in folder /newkernel_175
SAPCAR -xvf SAPEXE_175-20000221.SAR
SAPCAR -xvf SAPEXEDB_175-20000223.SAR

8. Login as sidadm

9. Stop the SAP System
stopsap

10. Stop saposcol
saposcol -k

11. Login as root

12. Go to the current kernel directory
cd /sapmnt/SID/exe

13. Copy all extracted support packages into this folder
cp -pr /newkernel_175/* /sapmnt/SID/exe

14. Copy back the original file saproot.sh into this folder.
cp -p /SIDkernel_10102007/saproot.sh /sapmnt/SID/exe

15. Go to the current kernel directory
cd /sapmnt/SID/exe
Then run:
./saproot.sh SID

16. Login as sidadm

17. Start the saposcol service
saposcol

18. Start the SAP system
startsap