print this page
Latest Post

SAP KERNEL Version How to check for Java System?

Login to <sidadm>
Type this command : disp+work -v|more

You will see the kernel Patch level













Restriction with stack xml - SAP MOPZ


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.






SAP DAY LIGHT SETTINGS

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.



Post By Zhi Lue

No valid Maintenance Certificate found on AS Java with SID

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
6. Save
7. Continue
8. Enter email
9. Submit


You'll receive the license to your email
Apply License via NWA if it's a Java System, SLICENSE if its an ABAP system.

SAPLICENSE HARDWARE KEY - Command to find

> saplicense  -get

Output Looks like this 
saplicense: HARDWARE KEY = Z1365131582



This command works for both ABAP & Java Stack system


sapcontrol version- How to check ?

Command to find sapcontrol version in SAP
> sapcontrol -nr 01 -function GetVersionInfo

You can see the version highlighted in yellow.

Output Logs

27.10.2014
GetVersionInfo
OK
Filename, VersionInfo, Time
/usr/sap/<sid>/SCS01/exe/sapstartsrv, 741, patch 11, changelist 1457969, RKS compatibility level 0, optU (Nov 23 2013, 14:27:00), rs6000_64, 2013 11 27 14:35:33
/usr/sap/QP3/SCS01/exe/gwrd, 741, patch 11, changelist 1457969, RKS compatibility level 0, optU (Nov 23 2013, 14:27:00), rs6000_64, 2013 11 23 05:28:57
/usr/sap/<sid>/SCS01/exe/msg_server, 741, patch 11, changelist 1457969, RKS compatibility level 0, optU (Nov 23 2013, 14:27:00), rs6000_64, 2013 11 27 14:35:35
/usr/sap/<sid>/SCS01/exe/enserver, 741, patch 11, changelist 1457969, RKS compatibility level 0, optU (Nov 23 2013, 14:27:00), rs6000_64, 2013 11 23 05:28:31
/usr/sap/<sid>/SCS01/exe/sapwebdisp, 741, patch 11, changelist 1457969, RKS compatibility level 0, optU (Nov 23 2013, 14:27:00), rs6000_64, 2013 11 23 05:29:02

How to check if SAP HOST AGENT is running ?

Command to verify saphostagent is running or not

root# /usr/sap/hostctrl/exe/saphostexec -status


Successful logs

[root@hostname:/root]# /usr/sap/hostctrl/exe/saphostexec -status
saphostexec running (pid = 9699506)
sapstartsrv running (pid = 13238512)
14:54:55 27.10.2014     LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
saposcol running (pid = 18874488)



Additional Info:
Command to START SAPHOSTAGENT
root# /usr/sap/hostctrl/exe/saphostexec -restart

Successful logs
[root@hostname:/root]# /usr/sap/hostctrl/exe/saphostexec -restart
-> Start /usr/sap/hostctrl/exe/saphostexec pf=/usr/sap/hostctrl/exe/host_profile <-

start hostcontrol using profile /usr/sap/hostctrl/exe/host_profile



Command to STOP SAPHOSTAGENT
root# /usr/sap/hostctrl/exe/saphostexec -restart




SAP JVM - How to the check the version ?


  1. Login to OS
  2. Swith to Profile directory /usr/sap/<SID>/SYS/profile
  3. Open Instance profile
  4. Search for the parameter SAPJVM_VERSION = 6.1.059





tags: sap, version, check, JVM, jre, stack, os level, profile,

What is XPI INSPECTOR in SAP PO 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.


Additional Info:
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.



How to deploy XPI Inspector tool? Multiple ways

Option1:
Deploy View Plug-in from SAP NWDS.

Option 2: [ Recommended for Basis]
Telnet command: deploy <xpi_inspector_ear.ear file path> version_rule=all

Option 3
SAP SUM tool

Additional Info:
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.



tags: XPI, sap, PO, PI, telnet, command, unix, deployment, download, file, xpi_inspector_ear.ear


XPI INSPECTOR - How to check the version of this tool?

Answer:
You can check the version of the XPI tool already deployed on your system by using "About" dialog in the UI.





tags: sap, pi,CPA Cache,Authentication & SSL,RWB, Mapping Runtime,Performance Problem,Authorization & Session Management,JEE Service,JEE Application,Default Trace











UNINSTALL SAP - Should I stop SAP application & Database ?

Answer:
When you are uninstalling SAP on the source system you don't have to stopsap or db as the sapinst that you use to uninstall will take care of those steps.
























Error: Remote access to the NetWeaver Administrator is forbidden. See SAP Note 1451753 for details.

After you successfully install SAP NW 7.4 Java, first time when you try to launch the NWA page you get a 403 error

Remote access to the NetWeaver Administrator is forbidden. See SAP Note 1451753 for details.

You should apply SAP Note 1451753 to resolve this error. Find the steps below


FIX:

·         Logon to Unix with <sid>adm user

·         Switch to directory /sapmnt/<SID>/global/security/data.


·         Open the file  icm_filter_rules.text using vi editor.

·         Comment all the lines using #

·         Save the file and exit from vi editor.

·         Restart  SAP system.

·         Log on to NWA using http://<hostname>:50000/nwa URL.


Additional Info:

icm_filter_rules.txt file after commented out.

NW 7.4 INSTALLATION MANSTER SCREENSHOT OF SUPPORT RELEASE 1

NW 7.4 INSTALLATION MANSTER SCREENSHOT OF SUPPORT RELEASE 1

 
Copyright © 2011. SAP BASIS ANSWERS | SAP BASIS ADMIN BLOG - All Rights Reserved
T C P M
Proudly powered by Blogger