System copy
System changeability and client settings
Support Packages from SAPNet - Web Frontend or Collection CDs are available in a compressed format. Note that you must unpack the support packages before processing. Download the support packages from the SAPNet - Web Frontend or mount the appropriate CD. Log in with the following user: Operating system users UNIX adm AS/400 OFR Windows NT adm Go to the following subdirectory in your system: Operating system UNIX and AS/400 usr/sap/trans/tmp Windows NT :\usr\sap\TRANS\TMP Unzip the archive containing the support packages with the following command: Operating system command UNIX CAR -xvf ///_CAR AS/400 CAR '-xvf /QOPT///_CAR' Windows NT CAR -xvf :\\ CHIVE>.CAR Put the unpacked support packages in the EPS inbox of your transport directory: Operating system EPS-Inbox of the transport directory UNIX /usr/sap/trans/EPS/in AS/400 /usr/sap/trans/EPS/in Windows NT :\usr\sap\trans\EPS\in Now bring the support packages into your system with Support Package Upload. You will see a list of uploaded support packages that are now known with all their attributes in the SAP system and can be handled in the right way by the SAP Patch Manager. Select Back to return to the SPAM entry screen.
An SAP HANA system lives on applications. When you develop these applications, you should think about securing them early. Using HTTPS instead of HTTP is one of the basics. In addition, you ensure secure authentication and implement a Secure Software Development Lifecycle to ensure backup in your own developments. In your applications, you better start to check them for risks early on and run this backup process regularly. You can analyse and restrict access to source code later. Create a risk register and address security vulnerabilities in a risk-based manner. The later you discover a risk, the more expensive the fix will be. Further information on SAP Security in addition to the article can be found here. Do you have any further questions or suggestions concerning this topic? Would you like us to go further on the subject? I look forward to your feedback!
Client management
As an SAP Basis administrator, you are faced with the challenge of balancing acute daily business and recurring routine tasks. As the complexity of the systems and the interdependencies tend to increase, the challenges are great and the requirements are growing. Daily and at the same time business-critical routine tasks are SAP job control and regular data backups. Automating these tasks can free up time for the day-to-day business of maintenance, servicing, support and troubleshooting. Clear monitoring and alerting in the event of an error help to maintain operational reliability and meet corporate compliance requirements.
If you are running a multi-system landscape with a common transport directory, it is convenient to enable this option only in the first system you are inserting support packages into, and to disable it in the following systems. Since the data files no longer need to be regenerated there, this saves time when playing in. Delete data files after inserting You can specify whether the data files should be deleted after inserting the support packages. This saves disk space and is enabled in the default setting. If you are running a multi-system landscape with a common transport directory, it is convenient to disable this option, since then the data files in the other systems no longer need to be re-created (see above Regenerate data files). Execute ABAP/Dynpro generation This option determines whether the programmes and screens shipped with the support packages should be generated during the commit. Note that generation can take a long time. Without automatic generation, the programmes and dynpros are not generated until the first call. Note that this parameter can only be affected by you if the generation is allowed by SAP during the insertion of this support package. The SPAM update does not affect the generation. SPAM Settings Option SAPM Basic Setting Transmission Monitor From Scenario Standard Rebuild Data File A data file after the example. Delete Do a Generation From Use the transaction SPAM to insert Support Packages [page 8] into your system, regardless of whether the support packages come from the SAPNet - R/3 Frontend, the SAPNet - Web Frontend, or Collection CDs. Prerequisites User: It must have the appropriate permissions [page 7] for the SAP Patch Manager. He must be registered with the client 000. He must have called the transaction SPAM. Select Tools ABAP Workbench Tool Maintenance Patches or enter the transaction code SPAM.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Whether release upgrades or importing important support packages - we are your experts.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
For more information, see the log file in the /usr/sap/trans/log (UNIX) directory.