Home » 2007

Yearly Archives: 2007

SAP on Linux: Virtualization on commodity hardware now officially supported

This is great news for Open Source Community. Finally, SAP on Linux has support its implementation on virtualization environment. Although not all virtualization technique is supported by SAP.

I found this great news on SAP SDN Network community. Here some SAP Notes showing you about SAP support on virtualization environment :

1122387 – Supported virtualization technologies with SAP

1122388 – Linux: VMware ESX Server 3 configuration guideline
962334 – SAP on Linux on XEN virtual machine

1048303 – Red Hat Enterprise Linux 5: Installation and upgrade
958253 – SUSE LINUX Enterprise Server 10: Installation notes

895807 – SAP support in virtualized Linux environments

I hope you – Linux fans (including me) – enjoy this fantastic news.

SAPGUI for Java 7.10 : Greap leap from SAP

SAP had released the latest SAPGUI for Java. It has 7.10 version. As this 2007, SAPGUI for Java had been improved. Currently, SAPGUI for Java 7.10 had significant update including input history capability had been integrated.

For most SAP End User, this feature (Input History) was very helpful since it’s only available on SAPGUI for Windows. I had been try and test it on my several SAP end user and they said “its awesome”, “very helpful”, etc.

For me as SAP Basis, it’s time for SAP to accelerate this SAPGUI development and improvement because of its multiplatform. Almost all OS user could use it from Windows, Linux, Solaris, AIX, HP-UX, and Mac OS X.

Another SAPGUI for Java feature that had been amazed me is its capability to use frontend printing. Not “F” type as you thought, but “G” access method. If you’re SAP using Basis release 620, just check your SPAM level using SPAM tcode. If you had minimumly on level 52, then you could use this access method (“G”).

Also, i had just mentioned about my new SAPGUI for Java on Linux deployment. I used to deploy SAPGUI for Java on Linux manually. But starting now, I am using remotely and silently method. Its very simple and helpful for such “lazy Basis” like me :D.

Prepare your SAPGUI for Java installer on remote machine. Then, create a simple responfile like this sample on the same directory as your SAPGUI for Java installer :

# Example of a typical installation response file
# suppress user interaction
# install to the default path
# reinstall gui if already present

And you just type this command on your console :

#java -jar PlatinGUI-Linux-710.jar -i[name_of_your_responfile]

Its very simple, isn’t it ? Happy deploying !! Let me know if you have question.

DB14 : Daily SAP Basis job log to be monitored

SAP provides an excellent DBA tools (for Oracle DB) which is called BRTOOLS. BRTOOLS is a compilation tools range from BRBACKUP (tools to maintain backup database), BRARCHIVE (tools to maintain archive files backup), BRCONNECT (tools to maintain checking database, updating database statistics, etc), BRRESTORE (tools to maintain database restoration), and some specific and useful tool.

When SAP Basis running one or more tools from BRTOOLS, it will create a job log to provide SAP Basis some information about BRTOOLS activities whether it succeed, succeed with warning, or failed. We can access those log from SAP R/3 through SAPGUI.

SAP provides DB14 tcode for SAP Basis to access those database logs. Through this article, I’ll show you how to monitored your database logs.

First, type DB14 on your SAPGUI screen. You’ll have this screen :

To check your BRCONNECT logs, just click BRCONNECT button.

You’ll see some logs. The one which coloured grey is BRCONNECT job that had run well or successfully. The other one which coloured yellow is BRCONNECT job that had run but ended with warning. If your BRCONNECT job hadn’t run well then it will show you red coloured log. To see what’s really happened, justdouble click one of i logs.

For more detailed information, click Detail Log button.

For BRBACKUP job log, you can click BRBACKUP button.

For more information about BRBACKUP activities, double click on one of its log.

To get more detailed information, click on Detail Log button.

For BRARCHIVE log activities, click on BRARCHIVE button.

For detailed information, just double click on one of its lines and you’ll get this screen.

For detailed information, you have to click Detail Log button.

SAP through Going Live Check event will check this log to make sure that your SAP production system is ready to go live. They will mention and warn you if something wrong with your backup configuration. So, make sure that you’ll have this log check every day to make your system has high availability and minimize your SAP production downtime.

SAPOSCOL : how SAP R/3 instance communicate with OS

SAPOSCOL a tiny program developed by SAP as daemon so that SAP R/3 instance can comunicate with its OS host. By using this SAPOSCOL program, SAP R/3 can communicate and can get a lot of information about OS including CPU usage, memory level usage, swap, disk activity, network information, monitored process, system configuration, client – server connectivity, etc. Hmm….we can get it without directly communicate with OS. Just use SAPGUI from your workstation.

Usually, SAPOSCOL program had to be started before your SAP R/3 instance so that it can supply your R/3 instance with OS information. To start SAPOSCOL program, your just entered your OS console/terminal and use ora[SID] (if you’re using Oracle) or SAPservice[SID] if you’re using MS SQL.

Just type : #saposcol

If SAPOSCOL process had been running, it will show you the information and status.

To stop SAPOSCOL, just type : #saposcol -k

To check SAPOSCOL information, just type : #saposcol -s

SAPOSCOL program is very important to SAP R/3 instance. It can delivered information to SAP tcode such as RZ20, ST03, ST06, etc.

If your SAPOSCOL program did’nt run then you’ll need to run it manually. Usually, Basis forget about its permission (if you’re working in UNIX environment) and claimed  “Hey, my SAPOSCOL didn’t run ? help…”

Your first step is check its permission on OS level (no need to restart your SAP R/3 instance nor your database server).

Hope this tutorial can help you.

Searching for The Best Linux distros for SAP Workstation

In my previous “personal” projects, my client always keep asking me what’s linux distro that I use and recommended for SAP workstation. Before I answer that question, I always gave them some of SAPGUI requirements. Based on that requirements, even you can decide which linux distro is the best linux OS for SAPGUI.

Here some guidelines before choosing linux distros :

  • Must be able to run SUN java environment because SAPGUI for Java was the only SAPGUI client available for Linux right now. There is no native SAPGUI for Linux. Not like Windows OS.
  • Must have office suite applications such as OpenOffice.org, KOffice, etc.
  • (Optional) Having remote desktop applications so that your SAP helpdesk or IT/EDP crew can help you figure out what happened if something bad is happening on you linux environment.
  • (Optional) Having MP3 player, Movie Player, Chat application, etc…just kidding.

Based on this requirements, you can decide the best linux distro for your own.  Another consideration before choosing your company official linux distro to use are :

  • How long do your IT/EDP crew to prepare a single desktop PC until its ready to be used ? If your choosen linux distro had already shipped with SUN java, OpenOffice an all applications you need then you’ll ready to boot your client just in a few minutes. This is the reason why I am using Vector Linux 5.0 SOHO and Vector Linux 5.8 SOHO edition. I recommend them as SAPGUI-ready distro 😀
  • Linux support and documentation. Soon or later, you’ll need help when installing or operating linux distro as SAPGUI workstation. Some of linux distro are well supported by big company such as Redhat, Novell, Xandros, Linspire, etc. Maybe one day you’ll need their support. For me, I prefer community based linux because I do not use complicated setting or configuration on my linux client. But, your bozz will decide this, right ?? Usually, well established company are still need legal support from another company support. You can get this support from your native or local company. (FYI, my private company, Ardhian Linux Shop are providing SAP support and also Linux PC and server support for Indonesia. Hope for my all over the world clients :D. Who knows ?? )
  • Regular linux distro release. Computer programs always have bugs. So, you always need to update or –radically– upgrade your linux distro. Ubuntu is one of the best linux that give their promise to be regular release every 6 months. You can rely on that.

I use Ubuntu and Vector Linux for my office. Of course, you can also use another linux distro such as PC Linux OS, Linux Mint, Freespire, etc.

Happy migrating your “pirated” Windows version to Linux !

Checking SAP R/3 Database via BRTOOLS

BRTOOLS is a database tool developed by SAP to help SAP Basis manage his Oracle based SAP R/3 database. In the last tutorial, I had shown you how to check your database through DB13 tcode. DB13 is database independent tcode to manage your database whether you’re using MS SQL, Oracle, DB2, or SAPDB.

Here, I am going to demonstrate how to use BRTOOLS to check your Oracle 9i database. You need to logon to your SAP R/3 server using ORA[SID] user.

Type BRTOOLS on your console and then you’ll have this screen. For your information, I’am using UNIX OS. It might be different when you’re using Windows OS.

Choose number 6 option by typing 6 and then press ENTER.

To check your database choose number 1 option and then press ENTER.

In this screen, you might need to input some information about your database such as your SAP Database profile, your database user and password, database owner, and something you might not want to be checked. For this moment, I am using default properties and press ENTER.

This screen show you BRTOOLS confirmation. Just type C and then press ENTER to proceed to the next step.

Press ENTER to proceed.

Now, you’ll see that database check process is running. Wait until it finished.

Type S to stop and exit from BRTOOLS menu. Now you had learn how to check your SAP R/3 database by using DB13 tcode and BRTOOLS command. In the next tutorial, I’ll show you another tips and trick that might be useful and helpful. Stay there and always connected.

Critics and suggestion are welcomed. Please feel free to contact me on devratt@yahoo.com.