a. It’s not possible to create a stack xml file to update just one or two or some specific components, mopz doesn’t work this way, you need upgrade the complete stack together. b. It’s not possible to create a mopz just to update patches,we can only just INTEGRATE patches in mopz, but not generate a stack xml file for patches alone. For example if customer wants to update the patches of Netweaver 7.30 SP05,he needs upgrade to SP06 or a higher SP level together with the patch levels.
There are three ways to deal with Daylight Saving Time:
A Two hour downtime method: Completely avoid running SAP system during this double hour.
B One hour downtime method: See Note 102088
C Zero downtime method: Use the default “stretched time”.
For customers who choose the way A, a switch is provided to shut off the stretched time. For details please see Note 102088.
As the "stretched time" is set as the default, all customers should decide for themselves whether they can accept the disadvantages of the "stretched time". If they can, the system can continue to run.
If not, the customer needs to choose way either A or B.
Be aware of that, "stretched time" is first introduced since release 46C. For older releases there is no such a choice.
How to code with “stretched time” by your own, so that it could run during the “double hours”, please see the “Information for the ABAP Developer”.
We know of at least one example of an application which cannot work with the "stretched time":
Component "IS-H," SAP Patient Management (see customer message 0000298268 120 050 410 2005).
"Letting the “double hours” run first, and then dealing with any possible errors" is a rather risky approach.
Type 1) errors are not very likely to occur, but type 2) errors are almost certain to occur. You need to
analyze your situation exactly in order to choose the right method for you.
No valid Maintenance Certificate found on AS Java with SID. For more information, refer to SAP Note 1236587 .
You get this message when your Hardware is changed or the existing certificate is expired or you have uninstalled SAP and installed SAP on the same hardware
To request a new maintenance certificate for an existing system
1. Go to service.sap.com/licensekeys
2. Request Keys from a List
3. Select the required SID from the list
4. Click Edit System
5. Click Change System and change the Version of product if you changing from Dual stack to Java
8. Enter email
You'll receive the license to your email
Apply License via NWA if it's a Java System, SLICENSE if its an ABAP system.
XPI Inspector is basically a tool developed by SAP which is a web application for collecting information about XI-related configurations and traces.
The tool also performs certain number of configuration checks, such as SSL client/server verification.
Which checks are executed depends on the selected example or the type and properties of the selected XI communication channels.
This XPI Inspector tools collects the below information based on the trace selection
1. Collect debug traces from Messaging System
2. Collect debug trace from XI Module Processor
3. Collect HTTP Traces
4. Collect Open SQL Traces
5. Collect JCo Traces
6. Collect information about the system state.
Download the file named "xpi_inspector_ear.ear" from the sap marketplace.
Deploy the tool on the XI Adapter Engine which you would like to inspect. Note that if you download the file from the web version that the extension of the file could be changed from EAR to ZIP. In this case you have to rename it again right after download from ZIP to EAR.