Seamless connectivity to monitor SAP servers via mobile device is really revolutionary. I always used to dream about monitoring my system farm by seating at Miami beach.

Today I came across SAP AG's android application 'SAP System Monitoring' on Google Play. I was happy like a child who got his x'mas gift from Santa. In description it says “With the SAP System Monitoring mobile app for Android, you can monitor availability, performance, and exceptions of important systems in the landscape anywhere and anytime. This app connects to the SAP Solution Manager application management solution and allows administrators to check alerts and monitor metrics right from their Android device.” I was in seventh heaven, and immediately downloaded the application.

After download, I understood that it requires SUP (Sybase Unwired Platform) to connect to solution manager..... and I landed back from my dream as I don't have SUP in my landscape. Now I have to postpone my Miami trip till SUP gets implemented in my landscape  ;-)

One thing I didn't understand is why this application need permission to read Phone Identity and records??

 

Regards,

 

Vishal Ranadive

Last year in March one of my client came up with hardware migration plan on which his SAP ECC 5.0 system was installed. He wanted to move from SPARC architecture to intel x86 architecture with same operating system SOLARIS.

I had experience of copying system from PA-RISC to IA64 on HPUX, but there was binary compatibility (Thanks to HP). In SOLARIS there is nothing like binary compatibility between these two versions (SPARC SOLARIS & intelx86 SOLARIS) and also Juan Reyes suggested that Solaris SPARC platform is big endian while Solaris x86 platform is little endian, based on that I had to perform a heterogeneous system copy. My worry was if I had to go for heterogeneous copy then TADM70 certification is mandatory.

In all these discussion Ruchit Khushu came up with good statement and I should call it perfect solution. He said “The copy would be classified as homogenous since no OS/DB change is involved. However with in homogenous system copy export/import method has to be used. Backup/Restore won't work. Often export/import is mistaken for heterogenous copy which is not correct. Export/Import can be used for both homoegenous as well heterogenous copy. Back/Restore is purely Homogenous.  Change in endianess will cause the code page to change and that can only be taken care of using export/import. Nevertheless it can be termed homogenous system.

SAP is very very clear on this: If hardware architecture changes but OS remains the same it is homegenous system copy. In other words if OS is callled the same on both source and target (SOLARIS) in this case, it is homegenous system copy. Of course this automatically doesn't imply the possibility of backup/restore to copy database (SAP specifically gives example is of SOLARIS on SPARC and Intel). Further SAP adds that it treats this copy as homogenous and no OS/DB migration check is needed.”

This solved my problem. Thanks to SDN and all active contributors.

Regards,

Vishal Ranadive

In past few years SAP with DB2 implementations has grownup not just because of it's performance, low storage requirement or low TCO but bundling DB2 with SAP License.

Increase in same platform implementations tends to increase same skill sets and hence reduces total cost of implementation with timeliness. This phenomena has increased number of SAP ECC implementations in SMB market.

With my broad experience in SMB market I have observed many companies implement x86 hardware architecture and always get delay in decision of operating system. Ofcourse their first preference is Widows due to it appears easy to administrate using GUI, where infact troubleshooting on windows is really tricky and difficult (No Offense!). I personally prefers SLES due to it's SAP optimized operating system and  integrated support with SAP, but no doubt RHEL is also good and stable operating system with SAP environment.

If SAP manages to include any of this Linux OS in bundle with SAP & DB2 license then, it will be more cost effective solution for SMB market.

Vishal Ranadive

SAP on XEN

Posted by Vishal Ranadive Dec 28, 2012

Introduction

Now a days Enterprises are looking to increase server utilization with minimizing server farm and reduced total cost of ownership (TCO).The Xen is an open source hypervisor technology which enables to create multiple server environments on single hardware. Running SAP on Linux under Xen, offers with flexibility and may help you to reduce TCO.

 

SAP and Xen

Looking at future's need SAP started supporting Linux under Xen virtual machine back in December 2007.

Currently two Linux distributions RedHat and SuSE are certified for Xen Virtualization , But on IA64 processor architecture only RedHat is certified.

Right Now we can use only Xen para-virtualization , full-virtualization is currently not supported by SAP.

 

Deploying SAP on Xen VM

SAP strongly advice us to put Xen virtual machine on raw device or partition to get desired I/O performance also advices to use external storage for Virtual Machines.

While deploying Guest operating system on Host OS , SAP recommends to use same distributions; But practically we may need to use some other distribution or OS, here SAP supports the installation if guest system is already certified by SAP with out supporting the third party applications like Database.

As per the SAP Lab test result overhead of the host OS i.e. Xen virtualization layer is less than 15 %.

Actions