tag:blogger.com,1999:blog-76965565145928979092011-11-28T00:58:50.856+01:00JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.comBlogger91100tag:blogger.com,1999:blog-7696556514592897909.post-46253885882003615512010-03-05T12:21:00.003+01:002010-03-05T12:51:57.657+01:00

Due to errors, because you want to roll-back to any SPAM version, or just because SAP Support has requested you to do so; you can implement the following workaround to re-import a current (or older!) SPAM/SAINT update to your system.Procedure: 1- Call transaction SEPS --> Goto --> Inbox, and order by column Subject. Search for all the SAPKD* packages (for example SAPKD70026). 2-

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com2tag:blogger.com,1999:blog-7696556514592897909.post-48184189937417538772010-03-04T09:54:00.004+01:002010-03-04T10:09:00.929+01:00

Here is an updated document of the Best Practices (including hardware design) of SQL Server 2008 implementation for SAP.Most of the design foundations are applicable by logic to any other Database platform, excluding of course, specific SQLServer configuration.I highly recommend its reading:http://download.microsoft.com/download/d/9/4/d948f981-926e-40fa-a026-5bfcf076d9b9/SAP_SQL2008_Best%

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com2tag:blogger.com,1999:blog-7696556514592897909.post-66153700676235186802010-03-04T09:32:00.002+01:002010-03-04T09:47:00.108+01:00

A few months ago, SAP did not support ORACLE under a VMWare enviroment.Now the support has increased a bit, but still with the following limitations:- Only version 10.2.0.4 or higher (no 9.x, no 10.2.0.2)- Only single instance (no RAC support)- If you plan to virtualize your SAP/Oracle system under Microsoft platform, the minimun version supported is Windows Server 2008.- When opening an OSS

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com1tag:blogger.com,1999:blog-7696556514592897909.post-30118357584684361472009-10-07T16:12:00.002+02:002009-10-07T17:30:30.289+02:00

Hyper-V technology from Microsoft is now officially supported by SAP even for production usage.The following combinations of OS/DB are supported for SAP under Hyper-V:- Windows / DB2 for LUW- Windows / SQL ServerRegarding Oracle virtualization usage for production, at the moment is not supported -- not even under VMWare or XEN (see note 1173954).One of the big goals of correctly designing a

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com1tag:blogger.com,1999:blog-7696556514592897909.post-3572002992964481562009-09-15T14:23:00.003+02:002009-09-15T14:51:38.255+02:00

If your SAP system runs on a UNIX host, and you are not granted remote X access, there is a workaround to run JSPM Server on the UNIX host and JSPM GUI on your Windows.For NetWeaver 7.10 and up:1. Open a shell on the server with adm, go to JSPM directory and run:go -remotegui2. Open a web browser on client host with JRE installed. Browse to this address: http://:519 - host is the server´s host

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com1tag:blogger.com,1999:blog-7696556514592897909.post-15359119142137359162009-08-27T10:23:00.002+02:002009-08-27T10:43:03.271+02:00

I came across different situations on where I had to analyze some specific PI performance issues.Besides all the technical aspects you have to consider when implementing a PI solution (correct hardware sizing, network traffic design, and so on), you have to carefully plan a Data Archiving solution so your Database does not grow up quickly and PI tables become unmanageable.First thing to watch is

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com1tag:blogger.com,1999:blog-7696556514592897909.post-32489315999716024822009-07-31T20:01:00.004+02:002009-08-01T00:45:42.342+02:00

I will try not to enter into every detailed aspect of a Duet 1.5 technical implementation. However, if you are new to a Duet 1.5 landscape, you must always prepare very carefully all the pre-requisites outlined in the SAP Duet Guides (Admin and Master). The following components enter in action on a Duet 1.5 system: SAP Duet 1.5 Server (based on Netweaver 7.0 Java - SP18 or higher).SAP Duet 1.5

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com1tag:blogger.com,1999:blog-7696556514592897909.post-90153054183912728182009-07-30T18:30:00.007+02:002009-07-31T03:25:55.272+02:00

If you dont want to pay any additional third-party SSO solution for your SAP enviroment, you can already use some out of the box utilities since WebAS 6.20 and up, including the lastest releases.Before implementing SSO on SAP / Windows, there are a few things you should know:You requiere on your landscape, a Microsoft LDAP Server (Active Directory).Your SAP system NT accounts (sidadm and

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com4tag:blogger.com,1999:blog-7696556514592897909.post-38006911577333941482009-07-29T12:23:00.009+02:002009-07-31T03:24:20.200+02:00

With the SAP release strategy of EhP4, there is a new mandatory tool to perform the installation/upgrade of ECC 600 ro release 604, and Netweaver components 700 to 701 (EhP1). SAPehpi (Enhacement Package Installer), acts as the SAPup tool we all know that performs upgrades from different releases. The traditional method of installation/upgrade before EhP4 was the stantard tool SAINT. I have

JPhttp://www.blogger.com/profile/03217117795974543447noreply@blogger.com0