Since release 700, the SAP_COLLECTOR_FOR_PERFMONITOR job requires the timezone settings on your system to be correct.  If there are timezone setting problems on your system, then you may be missing data in ST03 or the ST03 stats may be always a couple of days behind.  Transaction STAD is also effected by missing data if the timezone or DST setting is a problem.

Your timezone and (if applicable) Daylight Savings Time must be set correctly on both OS level and on SAP.

The SAP_COLLECTOR_FOR_PERFMONITOR job should be running in client 000 so to check your timezone you should go to transaction STZAC in client 000.  Make sure that the "System Time Zone" setting here is correct.

Another useful report is TZCUSTHELP, which also needs to be run in client 000.  When you run TZCUSTHELP you can enter your own current date, time and timezone.  Then you are presented with a report which should say "System time zone seems to be correct".

Daylight Savings Time settings are maintained in transaction STZBC and the rules defined here vary from country to country.  For example, the USA adjusted the DST change for the country by a couple of weeks in 2007 for all future years.  This change needed to be made in SAP as described in note 919538:

• 919538 - Daylight saving time start/end in USA and Canada as of 2007

Without the correct DST rule setting, SAP systems in the USA for those releases would be missing ST03 data for the couple of weeks that the DST change in the country was in effect.  Changes such as these happen in other countries, and can therefore effect the time and timezone settings of the SAP system there, which can in turn effect the ST03 data.  Make sure your DST rules are always setup correctly for your countries timezone  For example:

• 2126354 - No daylight saving time in Chile from year 2015 onwards
• 2055935 - Russia: End of permanent daylight saving time and start of permanent
• 1839444 - Daylight saving time in Morocco in 2013 and following years
• 1458775 - Daylight saving time in Israel (2012 - 2015)

Also see the KBA note 1841468 which provides further detail on this:

• 1841468 - Missing ST03 Data after DST Timezone Change

After you fix any timezone settings in your system, allow the collector to run for some time (up to 24 hours).

More information and troubleshooting guides (including this one) on the BC-CCM-MON area are available in the CCMS Wiki space at:

Computing Center Management System (CCMS) - Technology Troubleshooting Guide - SCN Wiki

The kernel writes workload statistics with each transaction step into buffers.  This buffered data is then saved to stat files in AL11 directory DIR_DATA  /usr/sap/<SID>/DVEBMGSxx/data  (parameter stat/file).  The files are named stat.DATxxx.  When you run transaction STAD, it is reading from these files.

astat files (as opposed to stat files) are application statistics.  Application stats are only created if it is setup in the application itself to create the stats.  Many systems do not create these.  System stats (stat files) on the other hand are always created at each step by the kernel.

You can deactivate the statistics by setting parameter stat/level = 0 (default is 1).  You can do the same for application stats with stat/as_level = 0

stat/max_files determines how many stat files are kept and therefore how long the STAD data is retained.  The maximum is 99 hours.  See the following link:

http://scn.sap.com/community/netweaver-administrator/blog/2015/01/23/stad-retention-period

Related notes:

• 1927118 - STAT Files Grow Too Large
• 6833 - Deleting statistics file, size of statistics file
• 16513 - File system is full - what do I do?

More information and troubleshooting guides (including this one) on the BC-CCM-MON area are available in the CCMS Wiki space at:

Computing Center Management System (CCMS) - Technology Troubleshooting Guide - SCN Wiki

Hello guys,

Problems related to the lack of data in ST03 due time zone incorrect settings are highly recurrent. I mean HIGHLY. The root cause for those wrong settings are, in the majority of the times, related to two scenarios:


---> Wrong time zone settings at SAP level (transactions STZBC, STZAC, etc...)

---> Mismatch between the timezone used by the OS level and SAP system.

There is a procedure that I often use to "navigate" through the possibilities and find out whether a time zone issue exists and, in case it does, where it's located. It is fairly simple and has helped for in several occasions while working with related scenarios.

The flow of the troubleshooting / decision making follow these steps, starting with the symptoms see at ST03:

ST03 does not report data / does not report current data (last two days) / ST03 seems odd...

In order to confirm or rule out a time zone issue as the root cause for the above topic, the first thig to do is go to STAD transaction and run it with the default settings. Just get into it and execute:

In case STAD does not report any data whatsoever, then we most likely have a winner. In case workload data is returned, then the issue should be approached thorugh different ways. We follow assuming that nothing returned to the query.

The very next thing to do is to check OS level time zone settings and cross it with R/3 level (client 000). The procedure vary depending on the operating system but on unix platforms, the command "date" will bring the desired information. For windows, "systeminfo":

UNIX:	WINDOWS:

Then you cross that information with R/3 level (client 000), transaction STZAC. The same timezone name must be seen there. The SAP system used for this analysis is hosted at a linux server (above) so the OFFSETs are matching.

That was the easiest check to do. Now comes the tricky part, which we approach in case the outputs present correct settings but even so ST03 and STAD are presenting issues.

First we need to understand the the system has its own timezone but users have it as well. User timezone can be the same as the system's (for cases in which both are located at the same region) or different (like seen above) where server is located at one place and users in another. We are using that feature in our advantage in this analysis.

For the above STZAC situation, the would be the expected output for SYSTEM > STATUS menu:

The "System time" field will present the time zone from the system itself and the "Time Zone" issue will report the timezone *ONLY IN CASE* the user have a different than the system. If both have the same timezone set, the field Time Zonewill not appear at all.

Now here starts the "trick"... Whenever facing time zone issues on your system, you'll notice that the extra "Time zone" field will be there, and we'll use it in our advantage in this analysis.

As soon as you know what is the default time zone being used by the system (transaction STZAC, client 000) you go to:enu

     > Menu system > User profile > Own data. Then, you change to tab "Defaults";

Inside of the Defaults tab, we'll look for the section "Personal Time Zone", where the current user time zone settings can be changed. First thing to check is whether the same is being used. In case its not set at all (assuming the system time zone) or set to another value, please set it to the same value:

After that, you have to save the changes, log out and in again. As soon as you log in again, you need to check menu "System > Status" one more time. Most likely you'll see something like this:

Above we can see that even using the very same time zone as the system, the output still shows one hour difference. Now what we have to do its change the user time zone settings again and, instead of CET (which should be equivalent for UTC+0100) use the OFFSET directly in the field. We already know that the OFFSET is not properly equivalent to UTC+0100 as it should, because if it were, the extra field "Time zone" would not appear at "System > status" menu.

Finally you just have to try another UTC OFFSET, lets SAY "UTC+0200" in the field, log out and log in again until the "Time zone" filed ceases to appear at "System > status" menu. Then you can finally access STZBC transaction and check why the time zone set for the system (in this case CET) is not behaving correctly as UTC+0100 but as UTC+0200 insted.

This procedure might appear complicated for first timers but, in time, you'll get the hang of it. I can assure

Cheers,

Ian Segóbio.

When we are doing our job as BASIS guys we need some tools like below in my exprience.

I will not give the names of the tools but I think must of us are using similar and well known tools.

You will remember when you are reading the lines through.

• At the beginning I want to give a computer characteristics that a BASIS guy must at least have to work  with.

The computer of a BASIS guy must be FULL HD. Since you do alot of RDP, connect to alot of systems at the same time.

It must have at least 8 GB RAM

It must have SSD HDD.

It must not be very havy especially for consultants who are travelling alot.

You must not have a simple mouse, instead you must have multipurpose one. And wireless one.

You must have a good bag to carry this computer off course.

• Every BASIS guy must have a tool for taking notes

This tool must have ability to save words, pictures, even files together.

I must reach the whole notes with one click. Mean when I open the program I must see all notes in my program.

This tool must have ability to search through all notes even through pictures using character recognition (OCR). So that I can reach the required info even in pictures.

This tool must have quick and powerful search ability.

This tool must save automatically when I am writing, taking notes. I must not push save button all the time and must not be suspicious whether I saved orr not.

This editor must be used through cloud.

• Every BASIS guy must havea text editor for displaying logs on SAP servers

This text editor must keep more than one file open

This editor must search through all open files

This editor must open file when it is being used

This editor could open big files

This editor must be installed easiliy

This editor could be portable also

• Every BASIS guy must have a tool for keeping passwords.

This tool must have master password so that I can keep all passwords in secure place.

This tool must paste user-password with key combinations or with mouse clicks into requested fields.

This tool must be configurable so that I could paste user and password according to the program, site etc.

This tool must be used throug cloud also.

This tool must be portable.

• Every BASIS guy must have a screen capture tool

This tool must have an ability to draw lines, rectangles, circles, write notes on screenshots while you are taking screenshot.

You must be able to do this screen capturing with on of the mouse buttons

You must copy the capture to clipboard so that you could paste it wherever you want

• Every BASIS gu must have an RDP Manage program.

This tool must keep many system infos

This tool must keep passwords securely

This tool must have grouping capability of systems

This tool must be portable

• BASIS Guy must pin below programs to taskbar on an SAP Server for SIDADM user for quick access in my opinion. We always need them.
  • SAP Microsoft Management Console
  • Services.msc
  • DB Management Studios
  • Command Prompts (cmd)
  • Internet Browser
  • Explorer
  • SAP GUI (Of course not on all system. On solution manager maybe)
  • For MS Windows below folders must be created in favourites
    • x:\Usr\sap\trans
    • x:\Usr\sap\SID
    • x:\Usr\sap\SID\DVEBMGS##\word
    • x:\Usr\sap\SID\SYS
    • x:\usr\sap\ESM\DVEBMGS##\j2ee

I think these are the tools that are needed at least when we are doing our job efficiently, carefully, quickly and effectively.

Can you advise us any other tools?

Looking forward to hearing your helpers?

Regards,

Yuksel AKCINAR

Now that the ASUG Annual conference is over, it is time to focus on SAP TechEd 2015 - Las Vegas (October 19-23)!!!   Maybe you submitted an abstract for the annual conference and did not get selected due to space limitations, or maybe you attended the conference and now have a better idea of what would be interesting to share, or maybe you didn't attend the annual conference and want to lock in the opportunity to attend SAP TechEd .

Which ever it is, time is running short.

ASUG SAP TechEd Proposal Submission

• Submit your session proposal at SAP TechED 2015 Las Vegas
• Deadline to submit proposals is Sunday, May 24th

Other Resources and Information:

ASUG Members, the SAP TechEd 2015 call for speakers is coming soon!!! 

Tammy Powlas

          Plan Now for Call for ASUG Speakers for SAP TechEd Las Vegas

          Don't Delay - Submit your ASUG SAP TechEd Abstract Today

Gretchen Lindquist ASUG members, start planning to present at SAP TechEd 2015!

Viva Las Vegas!!!!!!!!!!!!

lasvegasdice.net

Hi All,

Welcome back to this new blog, I would like to share a new learning of mine in this blog , where the user were see some funny characters while extracting reports to HTML format. Being a Basis resource this issue first sounded like an issue with some standard code to me and yes, it was indeed solved with an SAP note, like most of the other issues

Going into further details, we recently had an SP upgrade performed in our landscape and post upgrade there was this strange issue where user see some HTML code in the final exported output if report from transaction GR55(Execute Report Group). I could not really find much help with this while looking for this error on internet ( need to brush up my Google search skills ) and decided to post this blog

Below are component levels on which I have faced this issue :

SAP_BASIS    701    0016

SAP_APPL    604    0016

Funny character like : < /TT> ; &n bsp;  < /TD> and ';' (semicolon) at unwanted places do appear in this format. (Example screenshot below)

If you are facing this issue refer to below SAP notes and it could be helpful :

1000364 - Report Writer HTML export file not correct

979680 - RW: Exported HTML file incorrect

So lessons learned : add this step to your SP upgrade checklist to make sure that issue could be resolved immediately after the upgrade.

If you do have any such learning please do comment  and share the knowledge

Old Standalone SAPOSCOL:

The old saposcol is a simple standalone program.  All it does is create a shared memory segment, collect Operating System statistics and store them in shared memory (shared memory segment 99 area).  The OS stats can then be read in transaction ST06.  It is installed once on the physical host, and it has nothing to do with the kernel or any other program.

Up until SAP_BASIS 710 (and until you upgrade to the 720 kernel as described in note 1636252), the old standalone saposcol executable is in the kernel directory.  However it has nothing to do with the kernel release of the system which means you can always use the highest release of saposcol (downward compatibility).  For a 46C system, you can use the 720 saposcol for example.

Saposcol on Windows is started by a service (SAP note # 436186 - Installing saposcol as a service).

Saposcol on Unix is started in the Unix startup script.

For more information on standalone saposcol refer to the 701 online documentation at:

"Operating System Collector SAPOSCOL":

Operating System Collector SAPOSCOL - Operating System Monitor - SAP Library

SAPOSCOL in SAPHOSTAGENT:

From SAP_BASIS 710 onwards, and also when you install saphostagent with the 720 kernel (note 1636252), saposcol is contained in the saphostagent package.  Saphostagent is also completely downward compatible, so again you can install saphostagent 720 on a 46C system for example.

• SAP note # 1031096 - Installing Package SAPHOSTAGENT

With saphostagent installed, saphostagent will start saposcol automatically.

On Windows with saphostagent the service is called SAPHostExec (SAP note # 1439391 - SAPOSCOL Service deleted after SAPHostAgent Installation).

On Unix, when you install SAPHOSTAGENT as described in SAP note # 1636252 (Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11):

"you must delete the call of the program SAPOSCOL from all the start profiles"

This way you will only be starting the correct SAPHOSTAGENT saposcol from the HOSTAGENT directory, and not trying to start a second standalone saposcol from the kernel directory, which can sometimes cause problems.

The dev_saphostexec trace file in /usr/sap/hostctrl/work provides details on your SAPHOSTAGENT patch version and on the saphostexec process starting up.

The saposcol trace file dev_coll is still located in the old /usr/sap/tmp directory.  When saposcol is being correctly started by SAPHOSTAGENT the dev_coll should have an opening line similar to:

LOG: Profile           : /usr/sap/hostctrl/exe/host_profile

on Unix, or:

LOG: "C:\Program Files\SAP\hostctrl\exe\saposcol.exe" -q -w60 pf="C:\Program Files\SAP\hostctrl\exe\host

on Windows.

When installing SAPHOSTAGENT on a remote host to monitor OS stats (for example to monitor a standalone DB server) refer to SAP KBA Note # 2164753:

• 2164753 - CCMS Monitoring of non-SAP Server (eg. Standalone DB)

For more information on saphostagent saposcol refer to the online documentation at:

"Operating System Monitor"  ->  "Downloading and Installing Package SAPHOSTAGENT":

http://snipurl.com/29xj1ef

More information and troubleshooting guides (including this one) on the BC-CCM-MON area are available in the CCMS Wiki space at:

Computing Center Management System (CCMS) - Technology Troubleshooting Guide - SCN Wiki

Everybody knows the western The Good, the Bad and the Uglyin my opinion. And its soundtrack off course.

When I was thinking of writing a blog about how to be a good BASIS guy, I saw the blog "Are You a Rock Star Blogger?" (I liked the blog and played tthe game. I advice you, too.) After that I changed the header of this blog. I like the soundrack by the way.

I also think that many people will have something to say about BASIS guys. when I commented on one of the blog, a colleague wrote about BASIS crimes as "Insufficient supplies of coffee…""

Lets come to the topic. What is good, bad and ugly for a BASIS consultant?

The good BASIS consultant;

• Shows emphaty and put him/herself  in place of the customer (not only customer also other consultants)
• Is helpfull to colleagues
• Is tidy: Does not leave many old documents on the desktop or filesystems of the SAP server
• Takes notes, documents what is done
• Learns from mistakes
• Makes plan or runbook even for small work
• Is secure
• Is hard working
• Is honest
• Is a team member
• Knows about OS, DB, Network, Storage
• Follows the technology and new features
• Uses additional languages
• Reads guides and follows guides
• Troubleshoots well
• Has good communication skills
• Has a certification
• Keeps eye on systems always
• Has sixth sense to use sometimes
• Has some IT Backgroud or some development background
• Has good understanding on functional topics or client business process
• Is experienced being involved in many projects
• Involved in big projects
• Asks people before stoppping the system
• Is user friendly
• Does not say bad words to colleagues and shouts at people
• Strong hearted
• Has Patience
• Has determination and vigorous nerves
• Gets official trainings
• Dooes not afraid of making hands dirty
• Challanges
• Ask seniors in doubt
• Never gives up
• Knows the power of knowledge
• Knows how and where to find the information
• Takes responsibality
• Knows how to manage resources
• Loves his job
• Does not forget duties
• Is on time for meetings

The bad BASIS consultant;

• Does not follow the guides
• Does not complete the work
• Does not take notes
• Does not help people
• Does not inform others
• Does not clean upp after installations
• Does not respect others
• Is selfish
• Does not want to be a team member
• Does not have lesson from mistakes
• Starts work without checking backup
• Betrays the ream
• Is not on time

And the ugly one;

• Stops system without informing users
• Says bad words to other people
• Gossips about people
• Hides what he learns
• Makes the same mistake again and again
• Ruins the team
• Always late

These are the things fallen from my keybboard to the blog in short time.

As I said, most of you have many things to say I bleieve.

Why don't you comment on this?

Thank you for reading and sharing.

Regards,

Yuksel AKCINAR

Starting with SAP_BASIS 710 the old ST06 is not displayed anymore.  However in the new ST06 you can select from the menu:  Environment -> Old ST06.

The SAP note 1483047 lists out the SAP releases and exactly which versions of ST06 / OS07 / OS07N are available with each release:

• 1483047 - "Old" version of operating system monitor not available

Old ST06:

The old ST06 transaction shows Operating Statistics information for each SAP instance.  As it is instance dependant it will open the ST06 stats for the instance you are currently on.  The old ST06 takes its information from SAPOSCOL shared memory.  You can use transaction OS07 to view the OS stats of another instance or monitored host when setup in AL15.  See SAP note 371023:

• 371023 - OS07/ST06: Monitoring operating system data

Old ST06 only reports old style OS data for the physical CPU of the server, ie. it does not report separate virtualized environments for 2 or more instances on one server for example.  It takes 10 second snapshots of the OS data.  You can adjust the default 10 second collection interval as described in SAP note 1284656:

• 1284656 - Saposcol collection interval

The "Detail Analysis Menu" button allows you to display information by OS statistics category or data over the last 24 hours or 30 days averages:

For more information on the old ST06 Operating System Monitor see the online documentation at:

Operating System Monitor - SAP Library

New ST06:

The new ST06 (or OS07N) displays the OS stats for all instances and other monitored systems and hosts.  It is therefore instance independent.  OS07N takes its information from SAPOSCOL, plus RZ20, plus the RZ23N CPH (central performance history) information.  It is therefore a much more complicated setup than the old ST06.  The new ST06 / OS07N is also described in the SAP note 1084019:

• 1084019 - OS07N: New operating system monitor

The top-left corner if the display lets you choose your instance, servers from other monitored systems, or the Hosts section for monitored non-SAP servers (such as standalone DB for example, see KBA note 2164753).

OS07N handles virtualization.  With OS07N and virtualization, the structure of the OS data and how it is collected has changed.  Now on the left column you have:

• Snapshot information which is the current OS info at the moment.  Taken from SAPOSCOL shared memory, every 10 seconds.
• Previous Hours information which is taken from RZ20 CCMS shared memory segment.  So if the Operating System nodes in RZ20 are not working for any reason, then you will be missing data here in Previous Hours also.
• History information which is taken from the CPH (central performance history).  Again, if the CPH is not setup, then you will be missing the History data in OS07N.

For missing data in Previous Hours or History, check the KBA note 1915341 and the SAP notes listed within it:

• 1915341 - No History Data in OS07N / ST06

For further details on virtualization and setup, depending on your Operating System, check the SAP note 994025:

• 994025 - Virtualized OS environments in the operating system monitor

For more information on the new ST06 / OS07N Operating System Monitor see the online documentation at:

Operating System Monitor - SAP Library

More information and troubleshooting guides (including this one) on the BC-CCM-MON area are available in the CCMS Wiki space at:

Computing Center Management System (CCMS) - Technology Troubleshooting Guide - SCN Wiki

How many times have you open SOLMAN_SETUP -> Managed system configuration just to find your Diagnostics Agent does not show up in the list?..

There is a number of reasons why diagnostics agents do not get registered properly or fail to start during install and then registration is missing or incomplete, in any case there is a few options to get them back on track (including re-install), but assuming the installation was successful the quickest way to recover the Diagnostics Agent and get it talking to both SLD and SOLMAN is to re-register them.

I've found the best way to do this is to follow this steps,

First, the first... Stop the diagnostics agent

Go to the script directory /usr/sap/<DA_SID>/<DA_instance>/script

Register with the SLD using command,

./smdsetup.sh sldconf hostname:"<sld_host.fqdn>" port:"<sld_port>" user:"<username>" pwd:"<password>"

Immediatly after, register with solman using command,

./smdsetup.sh managingconf hostname:"sapms://<solman_host.fqdn>" port:"<port>" user:"<username>" pwd:"<password>"

Finally, restart your Diagnostics Agent

Sometimes, if the initial registration ended badly the diagnostics agent servername can also be missing which leave you with an error similar to "Server name assignment'' on the agent failed  mainly caused by the name of host missing from the agent. This can be corrected by using the following command,

./smdsetup.sh changeservername servername:"<diagnostic_agent_host>"

These few commands should be a good resource to deal with rebel diagnostics agents during Managed System Configuration.

Love to hear your comments

SAP System copy - Affected tables

Reason :

• The production SAP systems data is copied to other system(s) in one of the following use cases
  • Testing SAP upgrades
  • Refreshing test environments for better data quality which can avoid many incidents in Production.
  • Replication for disaster recovery
  • Other requirements from Customers/Projects,etc.,
• The post processing steps takes the major portion of the system copy process
• It becomes handy to export and import the system tables to minimize/avoid certain post processing steps , for example, to recreate the RFCs etc.,
• It is difficult to find the relevant tables to be exported ( before system copy)  & Imported ( after system copy)

How to find the relevant tables ?

• Go to SE38 --> SCTC_LIST_TABLES -->  select the component --> Execute ( F8)

You can select different components here and find out the relevant tables ( to be exported )

You can note down these list of table which can exported and imported to avoid post processing.

This feature is part of SAP LVM. Either you could use the full features of LVM ( Also refer transaction STC01 and different task lists available) or you could utilize this procedure to find the list of tables affected due to system copy.

SAP System copy - Minimize Post processing

Export :

You could use either DB independent method or DB dependent method( using DB tools) . Here we explain using DB independent method (R3trans) which is commonly used.

• Create the export.ctl file in the SAP application sever under a directory and fill with the list of  table entries found in the above exercise

• run the following command " R3trans -w export.log -u 1 export.ctl "
• It will create trans.dat ( data ) file and log file. Check the log for RC and table entries exported.

Import :

• After the System copy is completed, you can now (re)import the exported tables .
• You can truncate the tables ( which you were exported ) in the target system ( for example, QA system ) before the import . This may not be needed in latest R3trans versions. You can check the tables entries after import and check the against logs of the table export
• Create the import.ctl file with entries, for example,

• Run the command "R3trans -w import.log import.ctl "
• Check the log for the imported table entries and return code.

An integral part of any AS Java system is HTTP Provider that provides a low level communication and transportation service for AS Java over HTTP. One of the important features of it is, capability of accessing file system via HTTP – that is actually the key for the topic that is discussed in this blog.

In order to be able to get read access to some directory of the file system of AS Java system, it is necessary to configure the respective alias. To do this, follow steps described below:

To enable directory browsing:

Open Visual Administrator, go to ServerID -> Services -> Http Provider. On the tab Runtime -> Virtual Hosts -> General (which is shown by default) there's a check box 'Directory List'. Check it and click on the button 'Save properties'. Do this for every server node in the cluster.

   1. Select the Directory list check box in General Tab, 

From Aliases tab, need to create a Alias and provide the path of the folder which have images 

Click on save properties.
 

Use this below URL to view the images which has saved in alias folder.
 

http://<HOSTNAME>:<PORT>/alias
 

Click on any listed image to access/display in web

Thank you.. 

Hey out there!  Our internal SSL certs expire every 2 years, so I recently  had to go through the steps to quickly renew them in our web dispatcher(s).

I'd like to share that information here to serve as quick reference for others!

Our OS:

AIX 6.1

Our Web Disp Version:

Commands:

As WXXADM, in the $SECUDIR directory:

./sapgenpse gen_pse -p SAPSSLS.pse -onlyreq -r WXX.req

./sapgenpse gen_pse -p SAPSSLC.pse -onlyreq -r WXXsslc.req

This exports the request

FTP the files to your PC. Now goto CRL, sign new P7B for each(save the files as WXXcertnew2015.p7b and WXXsslc-certnew2015.p7b) .  FTP back to to $SECUDIR

./sapgenpse import_own_cert -p SAPSSLS.pse -c WXXcertnew2015.p7b

./sapgenpse import_own_cert -p SAPSSLC.pse -c WXXsslc-certnew2015.p7b

This imports the signed certs

./sapgenpse seclogin -p SAPSSLS.pse -O wxxadm

./sapgenpse seclogin -p SAPSSLC.pse -O wxxadm

This generates new cred_v2 files for the user (if prompted for a PIN,enter it)

STOP and START the WEB DISPATHER

You must restart the web dispatcher before it’ll read the new certs

Now hit your back-end ECC/CRM/BW (whatever) system using the HTTPs port on your webdispatcher.

check cert to see if signed for another 2 years!

Hope that helps!

NICK

Hi All,

We See, We Follow, We Learn - That is what many people at SCN are about.

Today, I would like to thanks everyone and especially the ones who inspired me the most on SCN.

• Juan Reyes
• Sunny Pahuja
• Rishi Abrol
• Hemant Kumar
• Ashutosh Chaturvedi
• Jansi Rani Murugesan
• Reagan Benjamin

       and many more....

Thank you guys..  you have given me a lot !!

Thanks a lot..!!

And YOU.. do you have anyone who inspired you on SCN ?

If yes, then it's time to thanks them all.

Regards,

This blog refers " How to config and send email from SAP with third party tool XAMPP "

1. XAMPP installation & configuration part.

2.  SCOT settings from SAP end.

1. XAMPP installation & configuration part:

XAMPP is an easy to install Apache distribution containing MySQL, PHP, and Perl.

XAMPP stands for Cross-Platform (X), Apache (A), MySQL (M), PHP (P) and Perl (P). It is a simple, lightweight Apache distribution that makes it extremely easy for developers to create a local web server for testing purposes. Everything you need to set up a web server – server application (Apache), database (MySQL), and scripting language (PHP) – is included in a simple extractable file. XAMPP is also cross-platform, which means it works equally well on Linux, Mac and Windows. Since most actual web server deployments use the same components as XAMPP, it makes transitioning from a local test server to a live server is extremely easy as well. Web development using XAMPP is especially beginner friendly, as this popular PHP and MySQL for beginners course will teach you.

Installation of XAMPP:

We can download the free version of  XAMPP from web.

- Disable your anti-virus as it can cause some XAMPP components to behave erratically.

- Disable User Account Control (UAC). UAC limits write permissions to XAMPP’s default installation directory (c:/Program Files/xampp), forcing you to install in a separate directory

- Start the installation process by double-clicking on the XAMPP installer. Click ‘Next’ after the splash screen.

- Here, you can select the components you want to install. Choose the default selection and click ‘Next’.

- Choose the folder you want to install XAMPP in. This folder will hold all your web application files, so make sure to select a drive that has plenty of space.

- The next screen is a promo for BitNami, an app store for server software. Deselect the ‘Learn more about BitNami for XAMPP’ checkbox, unless you actually enjoy receiving promo mails!

-Setup is now ready to install XAMPP. Click Next and wait for the installer to unpack and install selected components. This may take a few minutes. You may be asked to approve Firewall access to certain components (such as Apache) during the installation process.

- Installation is now complete! Select the ‘Do you want to start the Control Panel now?’ checkbox to open the XAMPP control panel.

Understanding XAMPP Control Panel

The XAMPP control panel gives you complete control over all installed XAMPP components. You can use the CP to start/stop different modules, launch the Unix shell, open Windows explorer and see all operations running in the background.

Here is a quick overview of the Control Panel. For now, you only need to know how to start and stop an Apache server.

CONFIGURE MERCURY MAIL TRANSPORT SYSTEM -XAMPP

1. Start Mercury (using the XAMPP Control Panel) and then open the admin panel.

2. First of all we disable the HTTP server of Mercury so that it doesn't conflict with the apache:

1. “Configuration” -> “Protocol modules” .
2. Disable the check “MercuryB HTTP web server” .
3. I also disabled “Mercury IMAP4rev1 server” because I won’t need that one .
4. Leave the window opened, we’ll need it immediately .

3. To be able to send external mail we have to disable “MercuryE SMTP end-to-end delivery client” in the same dialog and enable “MercuryC SMTP relaying client”. Click “OK” and restart Mercury!

4. Now let’s configure Mercury in general:

1. “Configuration” -> “Mercury core module”, tab “General”

we want to send from localhost, therefore we check if “localhost” is the value of “internet name for this system” and adjust that if not

1. All other settings stay the same as they are already configured, but we’ll have a look to the checkboxes beneath:
2. Disable all but “Send copies of all errors to postmaster”

3. Check under the tab “Local domains” if the entry “localhost (local host or server) localhost (internet name)” is there, if not, add it

4. Click “OK” and leave the dialog.

5. Next we focus on the MercuryS SMTP Server for outgoing emails:

1. “Configuration” -> “MercuryS SMTP Server”
2. choose the tab “General” and add a wonderful name for your SMTP server under “Announce myself as”, simply fill in any name, I’ve chosen “CS SMTP”.
3. under “Listen on TCP/IP port” fill in “25″, that’s the SMTP port
4. add “127.0.0.1″ to “IP interface to use”, that’s the local IP of your pc. With the IP of the pc within the network (192.168.0.X) it doesn’t work (at least for me)

 
6. Now we limit the access to the server so that only our local machine can access it:

1. Under “Connection Control” click on “Add restriction” and add the IP range from “127.0.0.1″ till “127.0.0.1″ (it’s that simple, isn’t it?)…
2. Select “Allow connections”…
3. Leave all checkboxes deselected

with a click on “OK” we quit the dialog and we’re looking forward to the next one

7. Now we have the important one “MercuryC SMTP Client”

1. “Configuration” -> “MercuryC SMTP Client”
2. To send mail to external addresses we need to have an external SMTP server. If you’re renting webspace somewhere and have mail included then you normally have access to a SMTP server. My webspace is hosted at HostEurope and I’ll use the SMTP of my domain. Without such an external server the whole thing won’t work because domain names won’t be resolved among other things. I’ve chosen this path because I didn’t feel like configuring around the whole day.
3. Enter the address of your SMTP under “Smart host name”, for example “mail.meinedomain.com”
4. Depending on the way you access the server fill the values under “Connection port/type”:  we finally fill in the “Login username” and the “Password” that normally is supplied by your webhost and we’ve nearly finished…

   1. For a “normal” SMTP that would probably be port 25 and “Normal (no SSL encryption)”

   2. I access my SMTP via SSL, that would be port 465 and “SSL encryption using direct connection”
   3. if you have other parameters simply try around a little.

After completing the XAMPP configuration test Mail :

Go to File Menu --> Click on Send mail message option:

Give the recipient email Address and subject then click on Send button:

XAMPP Configuration done!!!

2.  SCOT settings from SAP end.

- Create a User (SCOTUSER):-SU01

- Give the User Name and Email Address.

- In Logon Data: User Type : Service

- Assign the below parameters:

- Assign the Profile: S_A.SCON - SAP Connect All Auth.RFC User/SAP Phone.Centr.Arch

- Click on Save.

- Add the highlight parameter in Instance profile :

Profile Parameter (Instance) :

- Run the TX. SCOT for settings :

Give the below details as in below screen shot:

Click on settings tab: Assign the SFDN

Create a new Job :

Sending a mail :(SO01)

Click on New message:

Click on send button on Top menu bar

Now go to Tx SOST:

Status is changed to send:

Mail is sent to the recipient, confirmation from mail inbox.

Thank you..

SAP JCo RFC Destination:

SAP JCo connector is using for Java Application to communicate with SAP ABAP system via Remote Function Call (RFC). JCo RFC support bi-directional for communication like Java to ABAP system and ABAP system to Java system.

To Access the JCo RFC, We need to login with Visual Administrator.

1. Maintaining a JCo connection in the portal

Visual Administrator:

Goto the Path: Drive\usr\sap\<SID>\JC<nr>\j2ee\admin\go.bat

Click on --> Connect

Provide the Password and click on --> Connect

Now you have successfully connected the Visual Administator.

Next, Go to <SID> --> Server 0(node)-->Services -->JCo RFC Provider

Provide the details like below:

Click on -->Set

We have completed the JCo RFC destination.

Now, we need to login in ABAP system and test the RFC.

Login to system.

Go to Tx. SM59. Select the TCP/IP connections

Click on -->Create

Provide the detail:

Click on Connection Test.

RFC connection is working!!!.

Hope this will help to resolve the issue.

Thanks,

Raj Kishor.

Hi All,

This document will help you to install SAP Host Agent.

SAP HOST AGENT Installation

1. Download the Host Agent file from SMP and Extract in a folder.

     Select the SAP HOST AGENT-> SAP HOST AGENT 7.21 -> Windows on x64bit

    Select the file and click on Add to Download Basket.

2. Extract the file by the below command.

3. Go to the Directory and run the saphostexec.exe command with SID user.

    F:\SAP Host Agent>saphostexec.exe -install -user SAPSMD\SMDADM

4. SAP Host Installation started.

5. Provide the SAP<SID> ADM password and Press -> Enter.

SAP Host Agent installation is completed.

Thanks,

Raj

Since release 700, the SAP_COLLECTOR_FOR_PERFMONITOR job requires the timezone settings on your system to be correct.  If there are timezone setting problems on your system, then you may be missing data in ST03 or the ST03 stats may be always a couple of days behind.  Transaction STAD is also effected by missing data if the timezone or DST setting is a problem.

Your timezone and (if applicable) Daylight Savings Time must be set correctly on both OS level and on SAP.

The SAP_COLLECTOR_FOR_PERFMONITOR job should be running in client 000 so to check your timezone you should go to transaction STZAC in client 000.  Make sure that the "System Time Zone" setting here is correct.

Another useful report is TZCUSTHELP, which also needs to be run in client 000.  When you run TZCUSTHELP you can enter your own current date, time and timezone.  Then you are presented with a report which should say "System time zone seems to be correct".

Daylight Savings Time settings are maintained in transaction STZBC and the rules defined here vary from country to country.  For example, the USA adjusted the DST change for the country by a couple of weeks in 2007 for all future years.  This change needed to be made in SAP as described in note 919538:

• 919538 - Daylight saving time start/end in USA and Canada as of 2007

Without the correct DST rule setting, SAP systems in the USA for those releases would be missing ST03 data for the couple of weeks that the DST change in the country was in effect.  Changes such as these happen in other countries, and can therefore effect the time and timezone settings of the SAP system there, which can in turn effect the ST03 data.  Make sure your DST rules are always setup correctly for your countries timezone  For example:

• 2126354 - No daylight saving time in Chile from year 2015 onwards
• 2055935 - Russia: End of permanent daylight saving time and start of permanent
• 1839444 - Daylight saving time in Morocco in 2013 and following years
• 1458775 - Daylight saving time in Israel (2012 - 2015)

Also see the KBA note 1841468 which provides further detail on this:

• 1841468 - Missing ST03 Data after DST Timezone Change

After you fix any timezone settings in your system, allow the collector to run for some time (up to 24 hours).

More information and troubleshooting guides (including this one) on the BC-CCM-MON area are available in the CCMS Wiki space at:

Computing Center Management System (CCMS) - Technology Troubleshooting Guide - SCN Wiki

Eventually I come across issues in WEBGUI, Web Dynpro ABAP or Security that involves different languages.

I usually test such scenarios in internal systems, but not all languages were installed.

Installing a new language in a ABAP SAP system seems to be quite easy. Maybe not that much.

Looking for documentation, there are SAP notes, SAP Help pages. A comprehensive blog can be found here.

Using SMLT

In my test system I decided to install a few extra languages.

But then I realized that only installing a language might not suffice. I also would have to import support packages, supplement clients.

Given the Support Package Stack level, the number of languages and the number of clients in each system, I started to think this task would be a nightmare.

As a beginner in SMLT matters, I installed the languages (8 new languages + DE/EN):

Then I started to import support packages.

Then used SMLT to supplement all the clients, beginning with client 000.

In the end, I wonder whether I have done all the work. Was everything ok?

Using ZLANTOOL

In this particular moment I found an excellent tool, called "Language Supportability Tool". It is delivered via SAP KBA 2145047. It consists of a transport request that can be imported in the system (as long as the environment is ok, i.e. according to the KBA).

With this tool it is possible to find whether there are missing steps while maintaining a language in SMLT.

And more! You can find the delivered texts, so you know where a missing translation might be.

Verifying installed languages.

First I tested on that I was sure that was ok: French.

The results were:

Green light! Let me test another one: Russian. The results were:

I discovered that I missed the supplementation of one client.

I decided to test one more language: Portuguese, with the following results:

I missed a lot of work in Portuguese language: import support packages and supplement all the clients in the system.

After importing missing support packages and supplementing missing clients, all the languages are consistent and ok for use in my system.

If you also need to verify the language(s) configuration in your system, give a chance to the Language Supportability Tool.

What is Software Update Manager (SUM) tool ?

A support pack contains lots of errors correction and new features. SUM tool is used to upgrading system to higher level, installing enhancement packages, updating single components and appluing SPS.

How to download SUM tool?

Current Available version:Software update manager 1.0 sp13

What are prerequisites of using SUM tool?

1) Most importantly Read the Sum guide available on Service market place described as per SAP System. It contains SUM guides for ABAP systems, JAVA       systems and ABAP+JAVA systems.

https://websmp104.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000783082011E

2)Make sure SAP system and database are started.

3)To Start SUM GUI, Java 6 or higher has to be installed.

4)Sum tool has feature to upgrade ABAP and JAVA stack at the same time.

5)Create the back up of the system.

Where do I find more details about SUM tool?

There is an excellent blog written by Boris Rubarth. Kindly follow the below link

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2012/11/07/software-update-manager-sum-introducing-the-tool-for-software-maintenance

How do I use SUM tool?

I found an awesome blog for that wriiten by Jyotish Gogai. Follow the demo steps in the blog :http://scn.sap.com/docs/DOC-25113

SUM tool Common Errors ?

1) JAVA application Blocked : application blocked by JAVA security

    Resolution: follow the sap note 2192751

2) Error in the Phase:READ-BASE-JVM-PROFILES for Dual Stack system:

    Resolution: Follow the sap note 2191002

3) Error in the phase validation_results : A target for these components were calculated earlier in the CREATE-QUEUE step.

   Resolution: Follow the sap note 2190432

4) Error in phase TOOLVERSXML_UPG: Mismatch between the last tool version run and the current one

   Resolution: Follow the sap note 2183731

5) Error in the phase INITPUT_PRE : Upgrade phase "INITPUT_PRE" aborted with severe errors

   Resolution: Follow the sap note 2183619

6) Error in the phase :   start-as-java for dual stack topology

   Resolution: Follow the sap note 2183160

7) Error in the phase deploy_sdm: SDM server has been set to standalone mode

   Resolution: Follow the sap note 2179754

8) Error in the phase : post-undeploy-components : Undeployment finished with error

   Resolution: Follow the sap note 2177329

Regards,

Neelkanth