Best Practice: SAPGUI Version and Patch Upgrades

Hello -
Does anyone have some thoughts/information on best practices relating to SAPGUI version and patch upgrades.
Obviously, sometimes upgrades are forced upon us (e.g. 7.10 for Vista) and in other cases it may just be considered "nice to have".
Either way - it always signifies regression test and deployment effort. How do we balance the benefit and cost?
Thanks, Steve

Hi Steve,
you're right for the first part, yes, we (usually) patch twice a year.
Now for the rest
An uninstall will only happen on release changes (6.20->6.40->7.10), i. e. about every 4-5 years as SAP releases them.
Patches are applied to the installation server and the setup on the client will only update changed program parts. For example, upgrading 6.40->7.10 took about 10 minutes (incl. uninstall), applying patch 1 less than 5 minutes.
I recommend, you read the "SAP Frontend Installation Guide - 7.10" which you find at SMP alias sapgui. Navigate to Media Library - Literature. It explains setup of the installation server (sounds like a big thing, but ain't much more than creating a share), creating packages, applying updates etc.
Peter
Points always appreciated

Similar Messages

What is "SAP Best Practices Baseline Versions"?

Could you help explain what is the relationship between "SAP Best Practices Baseline Versions " and
other SAP products?
Thanks!

1)SAP Best Practices Baseline Versions will deliver preconfigured organizational settings for different scenarios with regard to the following areas: common organizational structures, logistic organizational structures, and intercompany organizational structures. these can be implemented on any of the component based on the platform availability, and cannot be directly used. For example with out installing an SAP sysetm you cannot implement baseline versions. So the relation would be Component or Product is primarily available to use the secondary component i.e Baseline versions on it.
The SAP Best Practices Baseline Package is available in different country versions (for example, for France, Nordics, Germany,
the United States, and the U.K.). The scope of these localized versions might differ depending on country-specific needs. Please check this link: http://www.sap.com/services/pdf/BWP_SAP_Best_Practices_for_Baseline_Package.pdf
2)The other products are
Customer Relationship Management (CRM)
Enterprise Resource Planning (ERP)
Product Lifecycle Management (PLM)
Supply Chain Management (SCM)
Supplier Relationship Management (SRM)
The SAP NetWeaver technology platform enables the composition, provisioning, and management of SAP and non-SAP applications across a heterogeneous software environment (release version from 640 to 700 and above) Prior to the introduction of SAP NetWeaver as an integrated technology platform, SAP has developed a number of integration technologies and offered them as individual products, among them for example SAP Enterprise Portal, or SAP Exchange Infrastructure.
SAP NetWeaver Platform
SAP NetWeaver Portal (formerly SAP Enterprise Portal)
SAP NetWeaver Business Intelligence
SAP NetWeaver Visual Composer
SAP Auto-ID Infrastructure
SAP Composite Application Framework
SAP Netweaver Development Infrastructure
Thank you,
Shyam

Best Practice for Planning and BI

What's the best practice for Planning and BI infrastructure - set up combined on one box or separate? What are the factors to consider?
Thanks in advance..

There is no way that question could be answered with the information that has been provided.
Cheers
John
http://john-goodwin.blogspot.com/

Best Practice regarding using and implementing the pref.txt file

Hi All,
I would like to start a post regarding what is Best Practice in using and implementing the pref.txt file. We have reached a stage where we are about to go live with Discoverer Viewer, and I am interested to know what others have encountered or done to with their pref.txt file and viewer look and feel..
Have any of you been able to add additional lines into the file, please share ;-)
Look forward to your replies.
Lance

Hi Lance
Wow, what a question and the simple answer is - it depends. It depends on whether you want to do the query predictor, whether you want to increase the timeouts for users and lists of values, whether you want to have the Plus available items and Selected items panes displayed by default, and so on.
Typically, most organizations go with the defaults with the exception that you might want to consider turning off the query predictor. That predictor is usually a pain in the neck and most companies turn it off, thus increasing query performance.
Do you have a copy of my Discoverer 10g Handbook? If so, take a look at pages 785 to 799 where I discuss in detail all of the preferences and their impact.
I hope this helps
Best wishes
Michael Armstrong-Smith
URL: http://learndiscoverer.com
Blog: http://learndiscoverer.blogspot.com

How can i get best practice for SD and MM

Please, can any body tell me how can i get best practices for SD and MM for functional approach?
Thanks
Utpal

Hello Utpal,
I am really surprised, in just 10 minutes you searched that site and found it not useful. Check out my previous reply "you will not find screen shot in this but you can add it in this"
You will not find readymade document, you need to add this as per your requirement.
btw, the following link gives you some more link for new SAP guys, this will be helpful. Check out HOW to BASIC transaction
New to Materials Management / Warehouse Management?
Hope this helps.
Regards
Arif Mansuri

Best practice for Plan and actual data

Hello, what is the best practice for Plan and actual data? should they both be in the same app or different?
Thanks.

Hi Zack,
It will be easier for you to maintain the data in a single application. Every application needs to have the category dimension, mandatorily. So, you can use this dimension to maintain the actual and plan data.
Hope this helps.

SAP Business One Best-Practice System Setup and Sizing

SAP Business One Best-Practice System Setup and Sizing
Get recommendations from SAP and hardware specialists on system setup and sizing
SAP Business One is a single, affordable, and easy-to-implement solution that integrates the entire business across financials, sales, customers, and operations. With SAP Business One, small businesses can streamline their operations, get instant and complete information, and accelerate profitable growth. SAP Business One is designed for companies with less than 100 employees, less than $75 million in annual revenue, and between 1 and 30 system users, referred to as the SAP Business One sweet spot. The sweet spot covers various industries and micro-verticals which have different requirements when it comes to the use of SAP Business One.
One of the initial steps during the installation and implementation of SAP Business One is the definition of the system landscape and architecture. Numerous factors affect the system landscape that needs to be created to efficiently run SAP Business One.
The <a href="http://wiki.sdn.sap.com/wiki/display/B1/BestPractiseSystemSetupand+Sizing">SAP Business One Best-Practice System Setup and Sizing Wiki</a> provides recommendations on how to size and configure the system landscape and architecture for SAP Business One based on best practices.

For such high volume licenses, you may contact the SAP Local Product Experts.
You may get their contact info from this site
[https://websmp209.sap-ag.de/~sapidb/011000358700001455542004#India]

DNS best practices for hub and spoke AD Architecture?

I have an Active Directory Forest with a forest root such as joe.co and the root domain of the same name, and root DNS servers (Domain Controllers) dns1.joe.co and dns2.joe.co
I have child domains with names in the form region1.joe.com, region2.joe.co and so on, with dns servers dns1.region1.joe.co and so on.
Each region has distribute offices that may have a DC in them, servers named in the form dns1branch1.region1.joe.co
Over all my DNS tests out okay, but I want to get the general guidelines for setting up new DCs correct.
Configuration:
Root DC/DNS server dns1.joe.co adapter settings points DNS to itself, then two other root domain DNS/DCs dns2.joe.co and dns3.joe.co.
The other root domain DNS/DCs adapter settings point to root server dns1.joe.co and then to itself dns2.joe.co, and then 127.0.0.1
The regional domains have a root dns server dns1.region1.joe.co with adapter that that points to root server dns1.joe.co then to itself.
The additional region domain DNS/DCs adapter settings point to dns1.region1.joe.co then to itself then to dn1.joe.co
What would you do to correct this topology (and settings) or improve it?
Thanks in advance
just david

Hi,
According to your description, my understanding is that you need suggestion about your DNS topology.
In theory, there is no obvious problem. Except for the namespace and server plaining for DNS, zone is also needed to consideration. If you place DNS server on each domain and subdomain, confirm that if the traffic browsed by DNS will affect the network performance.
Besides, fault tolerance and security are also necessary.
We usually recommend that:
DC with DNS should point to another DNS server as primary and itself as secondary or tertiary. It should not point to self as primary due to various DNS islanding and performance issues that can occur. And when referencing a DNS server on itself, a DNS client
should always use a loopback address and not a real IP address. detailed information you may reference:
What is Microsoft's best practice for where and how many DNS servers exist? What about for configuring DNS client settings on DC’s and members?
http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail-sack-saturday-edition.aspx#dnsbest
How To Split and Migrate Child Domain DNS Records To a Dedicated DNS Zone
http://blogs.technet.com/b/askpfeplat/archive/2013/12/02/how-to-split-and-migrate-child-domain-dns-records-to-a-dedicated-dns-zone.aspx
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Enterprise Portals versions and patches release dates

Could some one let me know, where can I find the release dates of the enterprise portal versions and patches, as I am interesetd to know about them.
I am new to EP and I dont have access to SAP service market place.
Thank you

Hi Raj Reddy,
You should have SAP market place id to get the EP versions and patch release dates. These are all available in the form pdf documents. In some documents we have to convert the weeks to corresponding years and months to guessestimate the dates.
Product overview
Version     Description     Release Type     Delivery Date     Status     Date     Mainstream / Extended Maintenance until     Printable Version
SAP WORKPLACE 2.11
SAP WORKPLACE 2.11      GA Release      General Availability      Available      Since 30.11.2000      30.09.2005 / -      Print...
Product overview
Version     Description     Release Type     Delivery Date     Status     Date     Mainstream / Extended Maintenance until     Printable Version
SAP ENTERPRISE PORTAL 5.0
SAP Enterprise Portal 5.0      GA Release      General Availability      Available      Since 28.12.2001      30.09.2005 / -      Print...
SAP EP 6.0 ON WEB AS 6.20
SAP Enterprise Portal 6.0 on SAP Web AS 6.20      Standard      Release to Customer      Available      Since 17.03.2003      31.12.2006 / -      Print...
Product overview
Version     Description     Release Type     Delivery Date     Status     Date     Mainstream / Extended Maintenance until     Printable Version
SAP NETWEAVER 04
SAP NETWEAVER 04      Standard      Release to Customer      Available      Since 31.03.2004      31.03.2010 / 31.03.2013      Print...
SAP NETWEAVER 2004S
SAP NETWEAVER 2004 S      Standard      Release to Customer      Planned      from 31.10.2005      31.03.2011 / 31.03.2014      Print...
The dates are available from EP5.0 General availability. to Netweaver 04 2005-06-03.
Hope this helps.
Regards,
Rajesh Khanna Venkatesan.

DB Version and Patch level

Hi Friends
Where can i see DB2 Version and patch level on ECC 6.0?
For Windows Database : DB2 or DB6??
Patch level?
Thanks
srinivas

Hi Srinivas,
DB6 is a SAP abbreviation for "DB2 for Linux, Unix and Windows" .
The DB2 version and FP level of your database server can be found in SAP transaction ST04 or DBACOCKPIT.
In SM50 you can view the work process traces to display the server and client level
C Running with UTF-8 Unicode
C Running with CLI driver
C
C Wed Oct 21 17:03:27 2009
C DB2 client driver version '09.05.0001'
C Connected to DB2 server type 'DB2/LINUXX8664'
C Connected to DB2 version '09.05.0002'
If you need more detailed information you have to use "db2level" in a DB2 CLP window on the DB server.
Regards
Frank

Is there a difference between LR4 full version and the upgrade.

I purchased the upgrade for LR4. I now have LR3. I want to download and install now and them put in the serial number to license it when it arrives. Is there a difference between installing the full version and the upgrade version. I don't want to screw up my catalog or anything else for that matter.

There is no difference and you're actually better off downloading and installing rather than installing a shipped version. The download will likely be newer.

Best practice for version control B2B, ESB and BPEL

Hello,
we are setting up a new system using B2B, ESB and BPEL. The development team is more experienced working with PL/SQL, Oracle Workflow and we are worried that Jdeveloper generates changes to the source files during development and that we might have problems with the version control.
Is there any best practice for setting up version control for these systems? Do we need to take anything in particular into consideration when setting up the projects?
We are using Serena Dimensions 9.1 for version control with the add-on in Jdeveloper.
Thanks in advance!

I believe JDeveloper has a plugin for Dimensions.
I havent used it but to get it, go to tools (It may be help I don't have JDeveloper on this machine to confirm) check for updates.
If you select the thrid party check box - next, you will see an entry for dimentions.
Configure the connection and develop as you would any other project.
cheers
James

Best Practices to do software Patching and Software Deployment for bigger environment like 300 K computers

Hi Friends,
i am looking for low level suggestions and a ppt/document etc too , The client base is 300 k users and spread globally ( major in three different regions), the requirement is
1) methodology to do software patching, can we patch all in one go or do we have to divide as per region etc
2) How many clients can be targeted for software patching in one go ( ex : can we target 20K clients in one go ?), i know there are other factors too will play key role here like band width etc , but i am looking answers out of real time experience
3) What Methodology to follow when it comes to critical/emergency updates ?
Regards
Tanoj
OSLM ENGINEER - SCCM 2007 & 2012

There is no single best practice to patching, if there were then SCCM would ship preconfigured :). As an example, Microsoft internally patches 300,000 workstations with 98% success in about a week according to their own podcast:
Microsoft Podcast
That said, I do follow a few rules when building a patching plan for a client. Maybe you'll find it helpful:
Always use a "soak tier". I forget where I first heard the term, but the idea is to have a good cross section of users get patches one or more weeks before your general deployment. This will help identify potential issues with a patch
before it hits general release. Make sure said group is NOT just the IT department ... we make the worst guinea pigs (we aren't known for closing out end of the month billing or posting legal documents).
When it comes to workstations, avoid needlessly phased deployment. 99% of the time, using local time zones is enough of a phased deployment. Unlike servers with very particular boot and patching orders, workstations can simply be patched. You
have enough collections in your environment ... so any new collection for patching should be justified.
Keep your ADR count down. It's tempting to build a new ADR for everything (workstations, general servers, exchange servers, etc.). Problem is that best practice also has you building a new SUG every time each ADR runs ... so you end up getting
flooded with update groups and that much more maintenance. When possible simply use maintenance windows to break up patching schedules instead of using mostly duplicate ADRs that simply have separate start dates.
Use Orchastrator. To me Orchastrator is to Software Updates what MDT is to Operating System Deployments: effectively mandatory. Even if you don't have complicated cluster updates you need to automate with SCO integrated to SCCM (there
are great examples on the web if you do), you can at the very least create run-books to manage that monthly maintenance you otherwise have to handle manually in SCCM (which is a lot IMO). I have monthly run-books that delete expired updates from SUGs,
consoldate SUGs older than 6 months unto a single annual group, and even create new update packages (and update all ADRs to use them) every 6 months to keep a single repository from getting too large.
I'm sure others out there can give you more advice ... but that's my two cents.

What are best practice for packaging and deploying j2EE apps to iAS?

We've been running a set of J2EE applications on a pair of iAS SP1b for about a year and it has been quite stable.
Recently however we have had a number of LDAP issues, particularly when registering and unregistering applications (registering ear files sometimes fails 1st time but may work 2nd time). Also We've noticed very occasionally that old versions of classes sometimes find their way onto our machines.
What is considered to be best practice in terms of packaging and deployment, specifically:
1) Packaging - using the deployTool that comes with iAS6 SP1b to package is a big manual task, especially when you have 200+ jsp files. Are people out there using this or are they scripting it with a build tool such as Ant?
2) Deploying an existing application to multiple iAS's. Are you guys unregistering old application then reregistering new application? Are you shutting down iAS whilst doing the deployment?
3) Deploying ear files can take 5 to 10 mins, is this normal?
4) In a clustered scenario where HTTPSession is shared what are the consequences of doing deployments to data stored in session?
thanks in asvance for your replies
Owen

You may want to consider upgrading your application server environment to a newer service pack. There are numerous enhancements involving the deployment tool and run time layout of your application that make clear where you're application is loading its files from.
If you've at a long running application server environment, with lots of deployments under your belt, you might start to notice slow downs in deployment and kjs start time. Generally this is due to garbage collecting in your iAS registry.
You can do several things to resolve this. The most complete solution is to reinstall the application server. This will guarantee a clean ldap registry. Of course you've got to restablish your configurations and redeploy your applications. When done, backup your application server install space with the application server and directory server off. You can use this backup to return to a known configuation at some future time.
For the second method: BE CAREFUL - BACKUP FIRST
There is a more exhaustive solution that involves examining your deployed components to determine the active GUIDS. You then search the NameTrans section of the registry searching for Applogic Servlet *, and Bean * entries that represent your previously deployed components but are represented in the set of deployed GUIDs. Record these older GUIDs, remove them from ClassImp and ClassDef. Finally remove the older entries from NameTrans.
Best practices for deployment depend on your particular environmental needs. Many people utilize ANT as a build tool. In later versions of the application server, complete ANT scripts are included that address compiling, assembly and deployment. Ant 1.4 includes iAS specific targets and general J2EE targets. There are iAS specific targets that can be utilized with the 1.3 version. Specialized build targets are not required however to deploy to iAS.
Newer versions of the deployment tool allow you to specify that JSPs are not to be registered automatically. This can be significant if deployment times lag. Registered JSP's however benefit more fully from the services that iAS offers.
2) In general it is better to undeploy then redeploy. However, if you know that you're not changing GUIDs, recreating an existing application with new GUIDs, or removing registered components, you may avoid the undeploy phase.
If you shut down the KJS processes during deployment you can eliminate some addition workload on the LDAP server which really gets pounded during deployment. This is because the KJS processes detect changes and do registry loads to repopulate their caches. This can happen many times during a deployment and does not provide any benefit.
3) Deploying can be a lengthy process. There have been improvements in that performance from service pack to service pack but unfortunately you wont see dramatic drops in deployment times.
One thing you can do to reduce deployment times is to understand the type of deployment. If you have not manipulated your deployment descriptors in any way, then there is no need to deploy. Simply drop your newer bits in to the run time space of the application server. In later service packs this means exploding the package (ear,war, or jar) in to the appropriate subdirectory of the APPS directory.
4) If you've changed the classes of objects that have been placed in HTTPSession, you may find that you can no longer utilize those objects. For that reason, it is suggested that objects placed in session be kept as simple as possible in order to minimize this effect. In general however, is not a good idea to change a web application during the life span of a session.

Best practices for an oracle application upgrade

Hello,
We have an enterprise application deployed on Oracle Weblogic and connecting to an Oracle database (11g).
The archive is versioned and we are using Weblogic's feature to upgrade to new versions and retire old versions.
In a case of emergency when we need to rollback an upgrade, the job is really easy on Weblogic but not the same on Oracle DB.
For most of our releases, the release package is an ear plus some database scripts.
Releases are deployed with minimum downtime, so while we are releasing our clients are still writing to the DB.
In case of a rollback is needed, we need to make sure the changes we made to the DB structure (Views, SP, Tables...) are reverted but data inserted by clients stayed intact.
Correct me if I am wrong, but Flashback and RMAN TSPITR are not the good options here.
What other people usually do in similar cases? What are best practices and deployment plans for our case?
Guides and direction are welcomed.
Thanks!

Hi Magnus
I guess you have to install again to ensure no problems. BP installation also involves ensuring correct SP levels (cannot be higher) for all software components.
Best regards
Ramki

Best Practice: SAPGUI Version and Patch Upgrades

Similar Messages

Maybe you are looking for