Here we go, SAP Basis Academy material for old version, most of them are still valid though. This is based on SAP Netweaver 7.0 which I think still pervasively used in a lot of companies. The current SAP Netweaver technology certification is based on the newer version like SAP NW 7.31. Anyway, you still can learn a lot from here. Enjoy! 🙂
As in the title, this is the procedure to configure SMTP Inbound and Outbound in SAP.
- Setting Profile Parameter below:
- icm/plugin_<*> = PROT=SMTP,PLG=<prog>, ex : icm/plugin_2 = PROT=SMTP,PLG=./smtpplugin.so
- icm/server_port_<*> = PROT=SMTP,PORT=<port>, ex : icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180
- is/SMTP/virt_host_<*> = :<host>:<port>,<port>,…;, ex : is/SMTP/virt_host_0 = *:25000;
- Create a user with type system (Tx code: SU01 ) and assign S_A.SCON to it. for example : MAILSYS
- Setting SMTP Server in tx code SICF
- In Host Data : Enter the sequence number of a parameter is/SMTP/virt_host_ from the profile
- In Service Data : Enter client, user created in step 2 and also its password
- In Handler List : Enter CL_SMTP_EXT_SAPCONNECT as item 1
Activate SAPConnect service
- SAPConnect Administration (Tx code SCOT)
- Set default domain in Setting -> Default Domain, so you can use this as your sender domain. For exampe if you set this to test.com, and You use BASIS user to send an outbound email, then the sender will be BASIS@TEST.COM
- Choose View -> Node view
- Double Click on SMTP Node
- Select Node In Use
- Set Mail Host and Mail Port (usually port number 25) where emails are being sent to
- Click Set on the supported address type – Internet. Specify internet addresses that are to be reached.
- Click Confirm
- Set the background job to send out queue outbound :
> Choose View -> Jobs or create if this doesn’t exist, choose Job -> Create.
> Enter a job name and confirm.
> Select the variant SAP&CONNECTALL. Choose Schedule Job.
> Choose Schedule Periodically. Enter periodic time to run this background job.
> Choose Create.
- For Inbound Processing automatically you can set in Settings -> Inbound Processing or Settings -> Inbound Distribution
If you run a Portal application based on SAP Web AS, you may find an error on your running process. Mostly the errors are logged into a log files of Java server process. A Portal application usually identified by prefix http://<hostname>:<port>/irj/… Here’s the important log files location :
X: server process number, start from 0,1,2 .. X
xx:default trace number which will be overwritten between 0-19 by default. the most updated can be displayed with the latest timestamp in OS.
The thing is not all people can read what is inside the log files since this is generated roughly from Java process, but those texts are very helpful to predict the portal application. The logs also display some Java class which is used by application. for example :
Yes, of course you need to practice how to solve the issue. There will be a hundreds or even a thousands of variation of the error. Well , prepare your time to learn then 🙂
If I’m not mistaken, display for DB02 is changed from SAP Netweaver 7.0 SP12 into a kind of DB Cockpit which also can be accessed from tx code ST04, DB13, DB14, and some DB transactions. After a Support Package upgrade or refresh sometimes it’s not displayed properly or blank as displayed below :
In my case, to make this transaction displayed correctly, I implement SAP Notes 868063 – Database space statistics monitor for Oracle. Here’s the steps :
- Run report RSORACUP.
- Fill input parameter :
CON_NAME : DEFAULT (for local system), or one of database connection as in F4 help
Due to incorrect logon or forgot the password user itsadmin in SAP ITS 6.20 is locked. Incorrect password can be occured after upgrading ITS or just after installation. Here’s the procedure how to reset the password:
- Make a backup of ItsRegistryADM.xml in configuration folder, so you can revert it back if needed.
- Search “itsadmin” in ItsRegistryADM.xml file.
- Password value would be like “<value name=”password” type=”text”>des26(7930d45240f)</value>” .
- Remove the value “des26(7930d45240f)” so that the format would be like this :
<value name=”password” type=”text”></value>
- Save the file and Restart ADM instance.
- When you first login again, leave the password empty.
- Change the password in Administration->ChangePassword, there will be a prompted window to fill and confirm the new password.
- Save and you can logon with new password.
From SAP Glossary , SAP Web Dispatcher is an SAP solution for load distribution for HTTP(S) requests. If an SAP system consists of multiple instances, the SAP Web Dispatcher receives the requests from the browser and forwards them to the application server that currently has most capacity. This simplifies administration since there is only one entry point (IP address, HTTP(S) port, and so on) to the SAP system.
Command for installing webdispatcher :
sapwebdisp pf=<profile file>
Sapwebdisp can also be started using bootstrap options, which then created sapwebdisp.pfl and icmauth.txt if these don’t exist :
For Windows NT you can install the service with this command :
ntscmgr install sapwebdisp -b <program_path>\sapwebdisp.exe -p “service pf=<profile file> <options>”
To kill sapwebdisp service you can use this command, in Windows :
sapntkill -INT <PID>
In Unix you can use this command to kill the running process:
kill -2 <PID>
You can monitor SAP Web Dispatcher from icmon command line program or Web Interface http://<server with domain>:<SAP Web Dispatcher port>/<admin prefix>. SAP Webdispatcher process is specified in parameter icm/server_port_0 and admin prefix is specified in icm/HTTP/admin_0. Both parameters are specified in profile file.
sapwebdisp -v -> check SAP Web Dispatcher version
sapwebdisp -checkconfig pf=<profile> -> check configuration which connect to certain message server.
icm/server_port_<x> : port to receive HTTP request
rdisp/mshost : message server host to be accessed
ms/http_port : message server port to be accessed
This ebook provide a basic concept for SAP R/3. This is a very basic thing if you want to learn about SAP Basis.
The first chapter is talking about the history of SAP R/3 evolve into SAP Netweaver technology, and of the new architecture or technology foundations that are found in the new set of products or components of the SAP NetWeaver integration platform.
The Second Chapter explains the SAP kernel and how it evolved and prepared for the Web: from the traditional SAP Basis and the client/server architecture to the Internet Business Framework and then up to the current SAP Web Application Servers. Continue reading
Here we come, a new page for all about SAP Basis. Since I’m driving my self into SAP especially Basis Area. I want to share, open to discuss and also learn for different view points. I’ll try to write from beginner and middle level for SAP Basis works, since I’m also still learning and learning again. Thanks for your visiting to my website.