Summary

The new Change Analysis (ABAP) is a tool to identify different kind of changes implemented in an SAP System – NetWeaver based, ABAP – during a given timeframe. The tool is released within transaction ST13 under Backoffice Tools for use by SAP or certified Service consultants and is only available in English.

Transaction ST13 and its toolset are delivered in Add-on ST-A/PI "Service Tools for Applications Plug-In" and the new Change Analysis (ABAP) tool will be available from ST-A/PI Release 01S*.

The objective of the document is to give information on how to use the Change Analysis (ABAP) tool. Official information can be reviewed in the Knowledge Based Article 2223746 - Backoffice Tools - Change Analysis (ABAP) in ST13.

Prerequisites & Limits

The new toolset Backoffice tools in ST13 which includes the Change Analysis (ABAP) tool will be available with the Add-on ST-A/PI Release 01S*. Please refer to SAP Note 69455 - Servicetools for Applications ST-A/PI (ST14, RTCCTOOL, ST12) for further information on how to install the Add-on.

In general a support user with minimal authorizations is needed to run the tool (refer to SAP Note 1405975 - Minimum Authorization Profile for Remote Service Delivery for necessary authorizations).

IMPORTANT INFORMATION FOR THE EXECUTION OF THE TOOL:

According the selected timeframe the performance of the tool can increase significantly. Please choose proper selection criteria to restrict the result set to a minimum – normally < 7 days should be sufficient. In maximum you can select a timeframe of 30 days only.

Introduction

With the Change Analysis (ABAP) tool it is possible to identify:

- Start time & date of Active Hosts

- OS/DB/SAP Parameter Changes

- Transport Requests

- Imported from other System

- Transport Requests

- Created in current System

- Change time & -date of Specific Program/Function Group/Class

In the following section a detailed description is provided on how to access and make use of the tool:

1. Logon to the SAP System with your support user and run transaction ST13.

2. Choose tool “BACKOFFICE_TOOLS” and press the execute button.

3. On the following screen mark “Change Analysis (ABAP)” and Execute (F8). Then the selection screen of the tool will open up.

4. On the selection screen you have five different kind of options to select which changes should be identified. Please mark the once you need.

a. Start time & date of Active Hosts

This option will be selected all the time as it identifies on which Hosts the System is currently running and when they have been started up (date & time).

b. OS/DB/SAP Parameter Changes

This option can be selected to identify Parameter Changes mainly on SAP level during a specific timeframe. For OS and DB also other vendor specific tools should be considered as the Change Analysis (ABAP) won’t be single source of truth.

Please note:

- The maximal selectable timeframe is 30 days. The performance can increase significantly if no proper timeframe is chosen.

- The Job SAP COLLECTOR FOR PERFMONITOR and/or Report RSORA110 has to run to collect the newest parameter changes. Only after a successful run the changes will be visible. Further details can be found in SAP Note 1733253 - CCMS: Monitoring of parameter changes in SAP system.

c. Transport Requests - Imported from other System

This option can be selected to identify which Transport Requests have been imported from another System (e.g. DEV/QA) during a specific timeframe. As an additional option the development package can be specified to restrict the result set.

Please note: The maximal selectable timeframe is 30 days. The performance can increase significantly if no proper timeframe is chosen.

d. Transport Requests - Created in current System

This option can be selected to identify which Transport Requests have been created in the concurrent System – changes that have been implemented directly in the System - during a specific timeframe.

Please note: The maximal selectable timeframe is 30 days. The performance can increase significantly if no proper timeframe is chosen.

e. Specific Program/Function Group/Class

This option can be selected to identify the change date, time and user of the specific Program/Function Group/Class.

Please note: This check only makes sense if you have already identified a specific Program/Function Group/Class to be the cause of an issue and just want to reconfirm when it was changes and who changed it.

5. After you finished your selection press the button “Execute” to get the results of the change analysis.

6. For each option you selected a single Tab will be visible on the result screen.

a. Start time & date of Active Hosts

The result of this check shows all currently active Hosts of the SAP System with the associated IP address and start date and start time.

b. OS/DB/SAP Parameter Changes

The result of this check shows which kind of parameter was changes (OS, DB or SAP), on which host it was changes, when it was changed, the parameter name and only the new parameter value.

c. Transport Requests - Imported from other System

The result of this check shows all Transport Requests transported from another system (e.g. Development/Quality) into the current system with Transport Request ID and information on the changed object (type & name), who changed it, change date and time, client and also the short description of the transport request.

d. Transport Requests - Created in current System

The result of this check shows all Transport Requests directly created in the current system with TR ID and information on the changed object (type & name), who changed it, change date and time, client and also the short description of the transport request.

e. Specific Program/Function Group/Class

The result of this check shows the information who changed the Program/Function Group/Class and when it was changed.

Additional Information

Please use this blog to provide feedback on the Backoffice Tools – Change Analysis (ABAP) in ST1, we are interested in your opinion and ideas.

Dear All,

I am herewith explaining the step by step way out for updating TREX server, which is very much required now in days in order to incorporate with dependent peripheral SAP SW Components . I am trying to architect the procedure based on one of my recent activity which includes following scenario :-

1. Old TREX Server : 7.10 SP40

2. Update Level : 7.10 SP55 (latest one)

3. OS: Windows 2008 (64 bit)

4. Number of connected SAP system RFCs : 3

Step 1: Check  the current version of TREX in connected SAP system though TREXADMIN T-Code.

Step 2: Download the latest patch level from SMP . Follow https://service.sap.com/swdc  >  Support Packages and Patches> Browse our Download Catalog> SAP NetWeaver and complementary products> SAP Netweaver > SAP NETWEAVER 7.0> Entry By Components > Search & Classification (TREX) > TREX 7.10 > Windows on X64 64 bit > TREX71_55-10004511.SAR

Step 3: Then extract it with SAPCAR with following command:-

sapcar -xvf <file name.SAR>

Step 4: Stop TREX service and also the Trex Admin console (if running somewhere).

Step 5: Execute SAPinst from the extracted directory :-

Step 6 :Choose "Update a TREX system" option :-

You can take restart of TREX server manually later on though MMC.

Step 7: Restart the TREX server through MMC and then you can check the latest version again in TREXADMIN.

NB: TREX Upgrade process from 7.1- PL 58 onwards, you can follow updated document - http://scn.sap.com/docs/DOC-69966

Regards,

Nilutpal.

When performing system administration, the more accurate technical information you find, the more likely you are to solve the issue quickly.

In this post document, you will get to know a compilation and an overview of important information (such as links to SCN documents, guides, SAP Notes) for dealing with kernel related tasks. The same content is provided to customers once they download one or more files that are part of the SAP “Kernel”.

We appreciate your feedback about the content to see if it is really working to speed up implementation and issue resolution, as well as other relevant comments or suggestions you may have.

Related spaces:

• SAP NetWeaver Technology Platform
• SAP NetWeaver Application Server

Information:

The concept of the security policies is to make the SAP system more secure, you can use this function to make your SAP system more protected, with collection of security policy attributes.

Introduction:

We all know the situations in daily work we need to maintenance the SAP system, and we want to restrict the users to login to the system, while system is in maintenance, and only the administrators, should be able to log on to the system.

SAP provides us this new feature with the amazing tool - Security policies.

Prerequisites:

This function is provided only with kernel releases 721, 740, 741 and subsequent versions as of SAP_BASIS 731.

Configuration:

First weneed to allow the administrators to login to the system while the system is in maintenance. For this we need to create new security policies

1. Use transaction SECPOL to create new security policies and assign the new attribute SERVER_LOGON_PRIVILEGE with the value 1.

               Picture 1.0

               Please check SAP Security policies / Group policies blog by Gowrinadh Challagundla

               This will give you more information regarding the Security policies, and how to create it.

     2. Change the value of SAP parameter login/server_logon_restriction to 1.

         This value will allow only those users whose assigned security policy contains the new attribute

           SERVER_LOGON_PRIVILEGE with the value 1 can log on to the system

                   Picture 1.1

                    Remember this value is dynamic value.

The following values are possible:

• 0 - No restriction All users can log on to the application server
• 1 - Logon to the application server only permitted with special authorization. (SERVER_LOGON_PRIVILEGE with the value 1 can log on to the system.)
• 2 - No logon to the application server permitted
• 3 - External logon to the application server now only permitted with special authorization. (SERVER_LOGON_PRIVILEGE with the value 1 can log on to the system.)
• 4 - No external logon to the application server permitted

     3. Add the security policies to the users – Go to SU01 and assign the Security policies

         to the administrator's users.

               Picture 1.2

So after we finish the configuration, we can start the tests.

               Picture 2.0

               Users without security policies cannot login to the system. (Restricted logon). Users with security

               policies will succeed.

SAP Sources:

1891583 - Restricting logon to the application server

http://scn.sap.com/community/security/blog/2013/01/04/sap-security-policies-group-policies

Caution:

Logonto the system with the SAP* user is always possible.

Thanks

Naor Shalom

Dear All,

Below are the step by step procedure for SAP IGS helper upgrade.

**************************Start**************************

Step 1:
Check current IGS version in your system

Step 2:

Download the relevant SAP IGS helper patch from SAP support portal

Step 3:

Stop SAP APP and DB.

Step 4:

Take backup of old IGS files from usr\SAP\SID\DVEMBGS00\IGS folder

Step 5:

Uncar the downloaded IGS files in a temp directory.

Use attrib /s -r command after unpacking.

Step 6:

Delete old IGS files from usr\SAP\SID\DVEMBGS00\IGS

Step 7:

Copy new IGS files from temp folder to above location

Step 8:

Start DB and SAP application.

Step 9:

Check current SAP IGS version after upgrade.

*******************Completed**********************

You can do this procedure in parallel with Kernel update.

Regards,

Prasad

patch name          SAPHOSTAGENT

patch level         10

patch   date           patchtext

    1   2015/05/04     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/05/04     Fix issue with workdir switch on z/OS, note 1113545

        2015/05/04     HostAgent SapPortReserve: improve log messages, note 401162

        2015/05/04     Porting sapdbctrl on HANA for 721_REL, note 2131602

        2015/05/04     SAP Host Agent 7.21, note 2130510

        2015/05/04     SAP on Linux with Hyper-V: Enhanced Monitoring, note 2147139

        2015/05/04     SAPOsCol terminates during EarlyWatch run, note 2141935

        2015/05/04     SIQ plugin initial check-in, note 2153941

        2015/05/04     SYB: saphostctrl/sapdbctrl - stop running isql before ASE da, note 2133098

        2015/05/04     Could not load platform library on linuxppc64, note 1550099

        2015/05/04     Create environment block fix for windows, note 1113545

        2015/05/04     Sapdbctrl causes lots of messages Login failed for user '<, note 2152992

        2015/05/04     Sapdbctrl: not member of sysadmin, note 1877727

        2015/05/04     Saphostagent HANA: Attach - create homedir with rev 93, note 2146861

        2015/05/04     Saphostagent HANA: Snapshot Handling for HANA SP7, note 2141369

        2015/05/04     Saphostagent HANA: support on Linux Power, note 2153138

        2015/05/04     Saphostagent HANA:getproperties wrong output instance list, note 2147554

        2015/05/04     Saposcol Linux: add patchlevel to OpSysDetails, note 1102124

    2   2015/05/10     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/05/10     SYB: Grey availability metrics in technical monitoring, note 2103798

    3   2015/05/18     CCMS: Sapstartsrv process hangs after stop action, note 2165518

        2015/05/18     Sapdbctrl/HANA: correction no database for service stop, note 2166891

        2015/05/18     Sapdbctrl: HANA password output with trace level 3, note 2167907

        2015/06/12     Fix sapdbctrl function loading traces, note 1113545

        2015/06/12     Monitoring with CIM Provider on Oracle Solaris, note 2140498

        2015/06/12     SAP Host Agent support for SAP IQ, note 2153941

    4   2015/07/21     Saposcol dumps on SIGSEGV in libc, note 2142737

        2015/07/21     SYB: saphostctrl/sapdbctrl - Improvements for ASE Upgrade, note 2167456

        2015/07/21     Sapdbctrl/HANA: startdb bigger timeout, note 2181530

        2015/07/21     Sapdbctrl/HANA: stopdb: Error on offline database, note 2185110

        2015/07/21     Sapdbctrl: not member of sysadmin, note 1877727

        2015/07/21     Hostexecstart compatibility fix, note 1113545

        2015/07/21     Fix resource leak, note 1113545

        2015/07/21     SAPCAR manifest extraction, note 1113545

        2015/07/21     Hostexecstart compatibility fix update, note 1113545

        2015/07/21     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

    5   2015/07/27     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/07/27     Additional Host Agent Operations for ACC/SAP LVM, note 1759181

        2015/07/27     Where-used check Trade Lane, note 1750181

        2015/07/31     Fixes and Features in CommonCryptoLib 8.4.38, note 2181733

        2015/07/31     Fixes in CommonCryptoLib 8.4.39, note 2192597

        2015/07/31     HANA & ABAP: New option to enable/disable FIPS 140-2, note 2180024

        2015/07/31     SAP Host Agent Patches specific to Windows, note 2125101

        2015/07/31     SAP Landscape Virtualization Management 2.1 SP05, note 2092694

        2015/07/31     The discovery process creates duplicate entries, note 2198765

        2015/07/31     Pfoscol counters for Suse VM on Azure, note 2191498

        2015/07/31     Saposcol Linux: vSphere 6.0 extended metrics, note 1102124

    6   2015/09/01     Saphostctrl missing create mountpoint option, note 1113545

        2015/09/01     Add Oracle 12c Support, note 1113545

        2015/09/01     Audit Logging Open File Fix, note 1113545

        2015/09/01     Fix Linux OS.PagesPagedIn/Out Metrics, note 1113545

        2015/09/01     Improve install/upgrade handling from hostagent directory, note 1113545

        2015/09/01     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2015/09/01     Problems with SAP Host Agent, note 1113545

        2015/09/02     SAPHOSTAGENT/HANA: Correction Stop DB no database found, note 2193060

    7   2015/10/07     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/10/07     DB6: Avoid log records regarding missing implementations f, note 2209841

        2015/10/07     Fix skip of log lines displayed, note 1550099

        2015/10/07     Improve Oracle archive destination handling for DB Copy, note 1113545

        2015/10/07     Potential denial of service in saposcol, note 2220064

        2015/10/07     Problems with SAP Host Agent, note 1113545

        2015/10/07     Restore OS default Signal behaviour, note 1113545

        2015/10/07     SAP Host Agent 7.2.1, note 2217610

        2015/10/07     SAPHOSTAGENT/ADA: missing getproperties output manag.-host, note 2223593

        2015/10/07     SAPHOSTAGENT/HANA: Corr Err msg: Instance already exist, note 2215504

        2015/10/07     SAPHOSTAGENT/HDB: missing getproperties output manag.-host, note 2223591

        2015/10/07     SAPHOSTAGENT/MaxDB: Correction listDatabase empty list, note 2216207

        2015/10/07     SYB: saphostctrl/sapdbctrl - use of odbc driver, note 2201973

        2015/10/07     Issue checking active IP Address, note 1550099

        2015/10/07     Issues modify exports and fstab, note 1550099

        2015/10/16     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2015/10/16     SAPHOSTAGENT/HANA: setproperty handling hdbuserstore logon, note 2225880

        2015/10/23     Saphostctrl -function AttachDatabase fails with access den, note 2233703

    8   2015/11/16     CCMS: Cannot maintain properties of MTEs from J2EE context, note 2242207

        2015/11/16     SAPHOSTAGENT/HDB: correction getproperties core dump, note 2236036

        2015/11/25     CIM-Based Monitoring for SAP Systems on HP-UX, note 2090656

        2015/11/25     Fixes in CommonCryptoLib 8.4.46, note 2243018

        2015/11/25     Update internal SIQ configuration settings if correct user, note 2241927

        2015/12/01     Patch Collection Nov 2015, note 1113545

        2015/12/01     Problems with SAP Host Agent, note 1113545

    9   2015/12/04     IBM i: Operating system performance data in CIM format, note 2078088

        2016/01/17     Linux saposcol patch collection Nov 2015, note 2240028

        2016/01/17     Outside Discovery Temporary Fix  for Database Status, note 1113545

        2016/01/17     SAP Host Agent Patches specific to Windows, note 2125101

        2016/01/17     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2016/01/17     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2016/01/17     SAPHOSTAGENT/HANA/LINXPPC64: wrong path hdbnsutil, note 2238705

        2016/01/17     SAPHOSTAGENT/HANA: Correction getDatabaseStatus, note 2235510

        2016/01/17     SAPHOSTAGENT/HANA: support multi Database with HANA SP 11, note 2243020

        2016/01/17     Hostagent crash preparing large exports if they are hooked, note 1113545

        2016/01/17     DB2-z/OS:CCMS:HAG: CIM-Provider Enablement for z/OS, note 2047924

        2016/01/17     SYB: saphostctrl/sapdbctrl - Improvements for SAP ASE upgrad, note 2167456

        2016/01/17     SYB: saphostctrl/sapdbctrl - correction for stop of heartbea, note 2232933

        2016/01/17     Continuous improvement of 7.21 saposcol, note 2136972

        2016/01/17     Saposcol data not updated, saposcol hanging, note 1984681

        2016/01/17     Saposcol parent process dumps at startup, note 2264155

        2016/01/17     Unwanted 10s collection interval in saposcol, note 2264242

        2016/01/17     Saphostagent/hana: Correction SAP_RETRIAVAL_PATH not set, note 2265273

   10   2016/01/22     Enable ListDatabaseSystems/GetDatabaseSystemStatus, note 1113545

        2016/01/22     Sapstartsrv: Fix ReadLogFile endcookie response, note 877795

        2016/01/24     SYB: saphostctrl discovery on Windows, note 2267843

   11   2016/02/04     Dump on AIX for PrintNetwork, note 1550099

        2016/02/07     Sapacosprep access local share via unc path, note 1550099

        2016/02/09     Linux: Avoiding TCP/IP port conflicts and start problems, note 401162

        2016/02/09     SYB: saphostctrl Solaris with Fault Manger, note 2275093

        2016/02/15     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2016/02/15     Additional Host Agent Operations for ACC/SAP LVM, note 1759181

        2016/02/15     Fix Oracle Online Copy Regression, note 1113545

        2016/02/15     Issues with sapacosprep, note 1084753

        2016/02/15     New operation for LVM to get hana infos, note 1550099

        2016/03/01     Additional environment win2012 fix, note 1113545

        2016/03/01     Problems with SAP Host Agent, note 1113545

        2016/03/01     Windows Metric Provider fixes, note 1113545

patch name          SAPHOSTAGENT

patch level         12

patch   date           patchtext

    1   2015/05/04     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/05/04     Fix issue with workdir switch on z/OS, note 1113545

        2015/05/04     HostAgent SapPortReserve: improve log messages, note 401162

        2015/05/04     Porting sapdbctrl on HANA for 721_REL, note 2131602

        2015/05/04     SAP Host Agent 7.21, note 2130510

        2015/05/04     SAP on Linux with Hyper-V: Enhanced Monitoring, note 2147139

        2015/05/04     SAPOsCol terminates during EarlyWatch run, note 2141935

        2015/05/04     SIQ plugin initial check-in, note 2153941

        2015/05/04     SYB: saphostctrl/sapdbctrl - stop running isql before ASE da, note 2133098

        2015/05/04     Could not load platform library on linuxppc64, note 1550099

        2015/05/04     Create environment block fix for windows, note 1113545

        2015/05/04     Sapdbctrl causes lots of messages Login failed for user '<, note 2152992

        2015/05/04     Sapdbctrl: not member of sysadmin, note 1877727

        2015/05/04     Saphostagent HANA: Attach - create homedir with rev 93, note 2146861

        2015/05/04     Saphostagent HANA: Snapshot Handling for HANA SP7, note 2141369

        2015/05/04     Saphostagent HANA: support on Linux Power, note 2153138

        2015/05/04     Saphostagent HANA:getproperties wrong output instance list, note 2147554

        2015/05/04     Saposcol Linux: add patchlevel to OpSysDetails, note 1102124

    2   2015/05/10     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/05/10     SYB: Grey availability metrics in technical monitoring, note 2103798

    3   2015/05/18     CCMS: Sapstartsrv process hangs after stop action, note 2165518

        2015/05/18     Sapdbctrl/HANA: correction no database for service stop, note 2166891

        2015/05/18     Sapdbctrl: HANA password output with trace level 3, note 2167907

        2015/06/12     Fix sapdbctrl function loading traces, note 1113545

        2015/06/12     Monitoring with CIM Provider on Oracle Solaris, note 2140498

        2015/06/12     SAP Host Agent support for SAP IQ, note 2153941

    4   2015/07/21     Saposcol dumps on SIGSEGV in libc, note 2142737

        2015/07/21     SYB: saphostctrl/sapdbctrl - Improvements for ASE Upgrade, note 2167456

        2015/07/21     Sapdbctrl/HANA: startdb bigger timeout, note 2181530

        2015/07/21     Sapdbctrl/HANA: stopdb: Error on offline database, note 2185110

        2015/07/21     Sapdbctrl: not member of sysadmin, note 1877727

        2015/07/21     Hostexecstart compatibility fix, note 1113545

        2015/07/21     Fix resource leak, note 1113545

        2015/07/21     SAPCAR manifest extraction, note 1113545

        2015/07/21     Hostexecstart compatibility fix update, note 1113545

        2015/07/21     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

    5   2015/07/27     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/07/27     Additional Host Agent Operations for ACC/SAP LVM, note 1759181

        2015/07/27     Where-used check Trade Lane, note 1750181

        2015/07/31     Fixes and Features in CommonCryptoLib 8.4.38, note 2181733

        2015/07/31     Fixes in CommonCryptoLib 8.4.39, note 2192597

        2015/07/31     HANA & ABAP: New option to enable/disable FIPS 140-2, note 2180024

        2015/07/31     SAP Host Agent Patches specific to Windows, note 2125101

        2015/07/31     SAP Landscape Virtualization Management 2.1 SP05, note 2092694

        2015/07/31     The discovery process creates duplicate entries, note 2198765

        2015/07/31     Pfoscol counters for Suse VM on Azure, note 2191498

        2015/07/31     Saposcol Linux: vSphere 6.0 extended metrics, note 1102124

    6   2015/09/01     Saphostctrl missing create mountpoint option, note 1113545

        2015/09/01     Add Oracle 12c Support, note 1113545

        2015/09/01     Audit Logging Open File Fix, note 1113545

        2015/09/01     Fix Linux OS.PagesPagedIn/Out Metrics, note 1113545

        2015/09/01     Improve install/upgrade handling from hostagent directory, note 1113545

        2015/09/01     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2015/09/01     Problems with SAP Host Agent, note 1113545

        2015/09/02     SAPHOSTAGENT/HANA: Correction Stop DB no database found, note 2193060

    7   2015/10/07     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/10/07     DB6: Avoid log records regarding missing implementations f, note 2209841

        2015/10/07     Fix skip of log lines displayed, note 1550099

        2015/10/07     Improve Oracle archive destination handling for DB Copy, note 1113545

        2015/10/07     Potential denial of service in saposcol, note 2220064

        2015/10/07     Problems with SAP Host Agent, note 1113545

        2015/10/07     Restore OS default Signal behaviour, note 1113545

        2015/10/07     SAP Host Agent 7.2.1, note 2217610

        2015/10/07     SAPHOSTAGENT/ADA: missing getproperties output manag.-host, note 2223593

        2015/10/07     SAPHOSTAGENT/HANA: Corr Err msg: Instance already exist, note 2215504

        2015/10/07     SAPHOSTAGENT/HDB: missing getproperties output manag.-host, note 2223591

        2015/10/07     SAPHOSTAGENT/MaxDB: Correction listDatabase empty list, note 2216207

        2015/10/07     SYB: saphostctrl/sapdbctrl - use of odbc driver, note 2201973

        2015/10/07     Issue checking active IP Address, note 1550099

        2015/10/07     Issues modify exports and fstab, note 1550099

        2015/10/16     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2015/10/16     SAPHOSTAGENT/HANA: setproperty handling hdbuserstore logon, note 2225880

        2015/10/23     Saphostctrl -function AttachDatabase fails with access den, note 2233703

    8   2015/11/16     CCMS: Cannot maintain properties of MTEs from J2EE context, note 2242207

        2015/11/16     SAPHOSTAGENT/HDB: correction getproperties core dump, note 2236036

        2015/11/25     CIM-Based Monitoring for SAP Systems on HP-UX, note 2090656

        2015/11/25     Fixes in CommonCryptoLib 8.4.46, note 2243018

        2015/11/25     Update internal SIQ configuration settings if correct user, note 2241927

        2015/12/01     Patch Collection Nov 2015, note 1113545

        2015/12/01     Problems with SAP Host Agent, note 1113545

    9   2015/12/04     IBM i: Operating system performance data in CIM format, note 2078088

        2016/01/17     Linux saposcol patch collection Nov 2015, note 2240028

        2016/01/17     Outside Discovery Temporary Fix  for Database Status, note 1113545

        2016/01/17     SAP Host Agent Patches specific to Windows, note 2125101

        2016/01/17     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2016/01/17     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2016/01/17     SAPHOSTAGENT/HANA/LINXPPC64: wrong path hdbnsutil, note 2238705

        2016/01/17     SAPHOSTAGENT/HANA: Correction getDatabaseStatus, note 2235510

        2016/01/17     SAPHOSTAGENT/HANA: support multi Database with HANA SP 11, note 2243020

        2016/01/17     Hostagent crash preparing large exports if they are hooked, note 1113545

        2016/01/17     DB2-z/OS:CCMS:HAG: CIM-Provider Enablement for z/OS, note 2047924

        2016/01/17     SYB: saphostctrl/sapdbctrl - Improvements for SAP ASE upgrad, note 2167456

        2016/01/17     SYB: saphostctrl/sapdbctrl - correction for stop of heartbea, note 2232933

        2016/01/17     Continuous improvement of 7.21 saposcol, note 2136972

        2016/01/17     Saposcol data not updated, saposcol hanging, note 1984681

        2016/01/17     Saposcol parent process dumps at startup, note 2264155

        2016/01/17     Unwanted 10s collection interval in saposcol, note 2264242

        2016/01/17     Saphostagent/hana: Correction SAP_RETRIAVAL_PATH not set, note 2265273

   10   2016/01/22     Enable ListDatabaseSystems/GetDatabaseSystemStatus, note 1113545

        2016/01/22     Sapstartsrv: Fix ReadLogFile endcookie response, note 877795

        2016/01/24     SYB: saphostctrl discovery on Windows, note 2267843

   11   2016/02/04     Dump on AIX for PrintNetwork, note 1550099

        2016/02/07     Sapacosprep access local share via unc path, note 1550099

        2016/02/09     Linux: Avoiding TCP/IP port conflicts and start problems, note 401162

        2016/02/09     SYB: saphostctrl Solaris with Fault Manger, note 2275093

        2016/02/15     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2016/02/15     Additional Host Agent Operations for ACC/SAP LVM, note 1759181

        2016/02/15     Fix Oracle Online Copy Regression, note 1113545

        2016/02/15     Issues with sapacosprep, note 1084753

        2016/02/15     New operation for LVM to get hana infos, note 1550099

        2016/03/01     Additional environment win2012 fix, note 1113545

        2016/03/01     Problems with SAP Host Agent, note 1113545

        2016/03/01     Windows Metric Provider fixes, note 1113545

   12   2016/03/04     IBM i: Program does not start with error: tcsetattr: Inval, note 2288677

        2016/03/04     Saphostagent/maxdb: wrong error Prepare Database Copy, note 2269733

        2016/03/11     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2016/03/11     Patch Collection 03.2016, note 1113545

        2016/03/11     SAP Host Agent Patches specific to Windows, note 2125101

        2016/03/11     SYB: saphostctrl/sapdbctrl - Support database metrics, note 2288152

        2016/03/11     Saposcol data not updated, saposcol hanging, note 1984681

        2016/03/11     Sapstartsrv: Fix http logfiles support, note 877795

        2016/03/15     Problems with SAP Host Agent, note 1113545

        2016/03/15     SAPHOSTagent/Hana: Detach im Scaleout-System funktioniert be, note 2283687

Hello,

I just want to share a script to start the saprouter in a easy way on unix. Just put the content bellow in a sh file, and pay attentio on the variables.

Then, just execute "sh start_saprouter.sh" for example, or put some schedule on it.

I hope it is useful.

Regards,

Richard W. L. Brehmer
http://www.rbrehmer.com

In this 2-part document, the steps of a new test server installation via system copy of development system are described. In the first part you find HANA DB installation steps. In the second part you find the SAP System installation steps and some main postprocessing steps. In our scenario, SAP System and HANA DB run on different servers. SAP System is based on NW 7.40.

Main SAP Note : http://service.sap.com/sap/support/notes/1844468

I've downloaded the main guide for the installation with S-User and password via that link: https://websmp104.sap-ag.de/~sapidb/011000358700000877172012E

Then please go through: SAP HANA Database->Unix.

For the filesystems, prerequisites and preparations for the system, you should look at the guide.

Here are main steps and screenshots of database installation on the new server:

• Login with root user to server where HANA DB will run and change directory to the path where HANA Software is located. Then execute ./hdblcmgui in order to start HANA installation interface.

• Local hostname is the hostname of the server where HANA will be located. Provide SID for your HANA DB.

• Check your inputs once again.

For the SAP System installation please see : SAP HANA System copy - part 2/2 (SAP System Installation)

In this 2-part document, the steps of a new test server installation via system copy of development system are described. In the first part you find HANA DB installation steps. In the second part you find the SAP System installation steps and some main postprocessing steps. In our scenario, SAP System and HANA DB run on different servers. SAP System is based on NW 7.40. For the first part (HANA DB Installation) plese see : SAP HANA System copy - part 1/2 (HANA DB Installation)

Main SAP Note : http://service.sap.com/sap/support/notes/1844468

I've downloaded the main guide for the installation with S-User and password via that link: https://websmp104.sap-ag.de/~sapidb/011000358700000877172012E

Then please go through: SAP HANA Database->Unix.

For the filesystems, prerequisites and preparations for the system, you should look at the guide. The latest version of SWPM is strongly recommended.

Here are main steps and screenshots of primary instance installation on the new server:

• Create a backup of the source system via SAP HANA DB Studio.

• Copy the backup files to the target server. The name of the backup will be used as SWPM input.

• SID is the system ID of application server (SAP System). It differs from DB SID. 7.40 Kernel DVD number is 51049350.

• Hostname of the server where HANA DB is installed. Also DB SID and HANA system number (from part 1/2) should be given. All DB-related passwords MUST be same with the source system DB.

• The name of the source system's backup. And the location where the backup files have been moved in the first step above.

• Latest kernel DVD has been downloaded and pointed to SWPM, in order to save time and effort. So we don't need to patch default SWPM kernel.

• Check your inputs once again and execute the installation.

• ERROR DURING INSTALLATION and SOLUTION

Root cause was unsuccessful connection attempt to the database. The reason was that ".KEY" and ".DAT" files had not been created properly. R3trans -d testing was also unsuccessful.

sapinst_dev.log

WARNING 2016-04-04 17:34:57.434 (root/sapinst) id=modlib.jslib.childAppReturn

Execution of the command "/usr/sap/SID/SYS/exe/uc/linuxx86_64/saplikey pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSSN_HOST -install_first_temp N1211111111 XXXXXX" finished with return code 2. Output:

saplikey: failed to connect to the database.

ERROR 2016-04-04 17:34:57.436 (root/sapinst) id=nw.processError errno=CJS-30023

Process call '/usr/sap/SID/SYS/exe/uc/linuxx86_64/saplikey pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSSN_HOST -install_first_temp N1111111 XXXXXX' exits with error code 2. For details see log file(s) saplikey.log, dev_slic.

ERROR 2016-04-04 17:34:57.583 (root/sapinst) id=controller.stepExecuted errno=FCO-00011

The step createTempLicense with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|NW_Temp_License_ABAP|ind|ind|ind|ind|lic|0|createTempLicense was executed with

status ERROR ( Last error reported by the step: Process call '/usr/sap/SID/SYS/exe/uc/linuxx86_64/saplikey pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSSN_HOST -install_first_temp N111111111 XXXXXX' exits with error code 2. For details

see log file(s) saplikey.log, dev_slic.).

SOLUTION

The hdbuserstorelist command should give the following outputs on the servers where SAP Instance and HANA DB are installed:

<DB_HOST>:HDB:<DB_SID>adm /usr/sap/<DB_SID>/HDB<HANA_SN>> hdbuserstore set SYSTEM <DB_HOST>:3<HANA_SN>15 SYSTEM <PASSWORD>

<DB_HOST>:HDB:khqadm /usr/sap/<DB_SID>/HDB<HANA_SN>> hdbuserstore list

DATA FILE       : /home/khqadm/.hdb/<DB_SID>/SSFS_HDB.DAT

KEY FILE        : /home/khqadm/.hdb/<DB_SID>/SSFS_HDB.KEY

KEY DEFAULT

  ENV : <DB_HOST>:3<HANA_SN>15

  USER: SAPSR3

KEY SYSTEM

  ENV : <DB_HOST>:3<HANA_SN>15

  USER: SYSTEM

<PAS_HOST>:SAPSIDadm> hdbuserstore set SYSTEM <PAS_HOST>:3<HANA_SN>15 SYSTEM <PASSWORD>

<PAS_HOST>:SAPSIDadm> hdbuserstore list

DATA FILE       : /home/DBSIDadm/.hdb/PAS_HOST/SSFS_HDB.DAT

KEY FILE        : /home/DBSIDadm/.hdb/PAS_HOST/SSFS_HDB.KEY

KEY DEFAULT

  ENV : <DB_HOST>:3<HANA_SN>15

  USER: SAPSR3

KEY SYSTEM

  ENV : <DB_HOST>:3<HANA_SN>15

  USER: SYSTEM

• After successful installation, install SAP HANA License via SAP HANA DB Studio. Right click DB there and select properties->licenses. License key is requested from service.sap.com.

• Post system copy steps can be checked from the guide.

patch name          SAPHOSTAGENT

patch level         13

patch   date           patchtext

    1   2015/05/04     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/05/04     Fix issue with workdir switch on z/OS, note 1113545

        2015/05/04     HostAgent SapPortReserve: improve log messages, note 401162

        2015/05/04     Porting sapdbctrl on HANA for 721_REL, note 2131602

        2015/05/04     SAP Host Agent 7.21, note 2130510

        2015/05/04     SAP on Linux with Hyper-V: Enhanced Monitoring, note 2147139

        2015/05/04     SAPOsCol terminates during EarlyWatch run, note 2141935

        2015/05/04     SIQ plugin initial check-in, note 2153941

        2015/05/04     SYB: saphostctrl/sapdbctrl - stop running isql before ASE da, note 2133098

        2015/05/04     Could not load platform library on linuxppc64, note 1550099

        2015/05/04     Create environment block fix for windows, note 1113545

        2015/05/04     Sapdbctrl causes lots of messages Login failed for user '<, note 2152992

        2015/05/04     Sapdbctrl: not member of sysadmin, note 1877727

        2015/05/04     Saphostagent HANA: Attach - create homedir with rev 93, note 2146861

        2015/05/04     Saphostagent HANA: Snapshot Handling for HANA SP7, note 2141369

        2015/05/04     Saphostagent HANA: support on Linux Power, note 2153138

        2015/05/04     Saphostagent HANA:getproperties wrong output instance list, note 2147554

        2015/05/04     Saposcol Linux: add patchlevel to OpSysDetails, note 1102124

    2   2015/05/10     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/05/10     SYB: Grey availability metrics in technical monitoring, note 2103798

    3   2015/05/18     CCMS: Sapstartsrv process hangs after stop action, note 2165518

        2015/05/18     Sapdbctrl/HANA: correction no database for service stop, note 2166891

        2015/05/18     Sapdbctrl: HANA password output with trace level 3, note 2167907

        2015/06/12     Fix sapdbctrl function loading traces, note 1113545

        2015/06/12     Monitoring with CIM Provider on Oracle Solaris, note 2140498

        2015/06/12     SAP Host Agent support for SAP IQ, note 2153941

    4   2015/07/21     Saposcol dumps on SIGSEGV in libc, note 2142737

        2015/07/21     SYB: saphostctrl/sapdbctrl - Improvements for ASE Upgrade, note 2167456

        2015/07/21     Sapdbctrl/HANA: startdb bigger timeout, note 2181530

        2015/07/21     Sapdbctrl/HANA: stopdb: Error on offline database, note 2185110

        2015/07/21     Sapdbctrl: not member of sysadmin, note 1877727

        2015/07/21     Hostexecstart compatibility fix, note 1113545

        2015/07/21     Fix resource leak, note 1113545

        2015/07/21     SAPCAR manifest extraction, note 1113545

        2015/07/21     Hostexecstart compatibility fix update, note 1113545

        2015/07/21     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

    5   2015/07/27     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/07/27     Additional Host Agent Operations for ACC/SAP LVM, note 1759181

        2015/07/27     Where-used check Trade Lane, note 1750181

        2015/07/31     Fixes and Features in CommonCryptoLib 8.4.38, note 2181733

        2015/07/31     Fixes in CommonCryptoLib 8.4.39, note 2192597

        2015/07/31     HANA & ABAP: New option to enable/disable FIPS 140-2, note 2180024

        2015/07/31     SAP Host Agent Patches specific to Windows, note 2125101

        2015/07/31     SAP Landscape Virtualization Management 2.1 SP05, note 2092694

        2015/07/31     The discovery process creates duplicate entries, note 2198765

        2015/07/31     Pfoscol counters for Suse VM on Azure, note 2191498

        2015/07/31     Saposcol Linux: vSphere 6.0 extended metrics, note 1102124

    6   2015/09/01     Saphostctrl missing create mountpoint option, note 1113545

        2015/09/01     Add Oracle 12c Support, note 1113545

        2015/09/01     Audit Logging Open File Fix, note 1113545

        2015/09/01     Fix Linux OS.PagesPagedIn/Out Metrics, note 1113545

        2015/09/01     Improve install/upgrade handling from hostagent directory, note 1113545

        2015/09/01     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2015/09/01     Problems with SAP Host Agent, note 1113545

        2015/09/02     SAPHOSTAGENT/HANA: Correction Stop DB no database found, note 2193060

    7   2015/10/07     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2015/10/07     DB6: Avoid log records regarding missing implementations f, note 2209841

        2015/10/07     Fix skip of log lines displayed, note 1550099

        2015/10/07     Improve Oracle archive destination handling for DB Copy, note 1113545

        2015/10/07     Potential denial of service in saposcol, note 2220064

        2015/10/07     Problems with SAP Host Agent, note 1113545

        2015/10/07     Restore OS default Signal behaviour, note 1113545

        2015/10/07     SAP Host Agent 7.2.1, note 2217610

        2015/10/07     SAPHOSTAGENT/ADA: missing getproperties output manag.-host, note 2223593

        2015/10/07     SAPHOSTAGENT/HANA: Corr Err msg: Instance already exist, note 2215504

        2015/10/07     SAPHOSTAGENT/HDB: missing getproperties output manag.-host, note 2223591

        2015/10/07     SAPHOSTAGENT/MaxDB: Correction listDatabase empty list, note 2216207

        2015/10/07     SYB: saphostctrl/sapdbctrl - use of odbc driver, note 2201973

        2015/10/07     Issue checking active IP Address, note 1550099

        2015/10/07     Issues modify exports and fstab, note 1550099

        2015/10/16     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2015/10/16     SAPHOSTAGENT/HANA: setproperty handling hdbuserstore logon, note 2225880

        2015/10/23     Saphostctrl -function AttachDatabase fails with access den, note 2233703

    8   2015/11/16     CCMS: Cannot maintain properties of MTEs from J2EE context, note 2242207

        2015/11/16     SAPHOSTAGENT/HDB: correction getproperties core dump, note 2236036

        2015/11/25     CIM-Based Monitoring for SAP Systems on HP-UX, note 2090656

        2015/11/25     Fixes in CommonCryptoLib 8.4.46, note 2243018

        2015/11/25     Update internal SIQ configuration settings if correct user, note 2241927

        2015/12/01     Patch Collection Nov 2015, note 1113545

        2015/12/01     Problems with SAP Host Agent, note 1113545

    9   2015/12/04     IBM i: Operating system performance data in CIM format, note 2078088

        2016/01/17     Linux saposcol patch collection Nov 2015, note 2240028

        2016/01/17     Outside Discovery Temporary Fix  for Database Status, note 1113545

        2016/01/17     SAP Host Agent Patches specific to Windows, note 2125101

        2016/01/17     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2016/01/17     SAP LVM 2.1 SP01 required sapacosprep storage library functi, note 2088477

        2016/01/17     SAPHOSTAGENT/HANA/LINXPPC64: wrong path hdbnsutil, note 2238705

        2016/01/17     SAPHOSTAGENT/HANA: Correction getDatabaseStatus, note 2235510

        2016/01/17     SAPHOSTAGENT/HANA: support multi Database with HANA SP 11, note 2243020

        2016/01/17     Hostagent crash preparing large exports if they are hooked, note 1113545

        2016/01/17     DB2-z/OS:CCMS:HAG: CIM-Provider Enablement for z/OS, note 2047924

        2016/01/17     SYB: saphostctrl/sapdbctrl - Improvements for SAP ASE upgrad, note 2167456

        2016/01/17     SYB: saphostctrl/sapdbctrl - correction for stop of heartbea, note 2232933

        2016/01/17     Continuous improvement of 7.21 saposcol, note 2136972

        2016/01/17     Saposcol data not updated, saposcol hanging, note 1984681

        2016/01/17     Saposcol parent process dumps at startup, note 2264155

        2016/01/17     Unwanted 10s collection interval in saposcol, note 2264242

        2016/01/17     Saphostagent/hana: Correction SAP_RETRIAVAL_PATH not set, note 2265273

   10   2016/01/22     Enable ListDatabaseSystems/GetDatabaseSystemStatus, note 1113545

        2016/01/22     Sapstartsrv: Fix ReadLogFile endcookie response, note 877795

        2016/01/24     SYB: saphostctrl discovery on Windows, note 2267843

   11   2016/02/04     Dump on AIX for PrintNetwork, note 1550099

        2016/02/07     Sapacosprep access local share via unc path, note 1550099

        2016/02/09     Linux: Avoiding TCP/IP port conflicts and start problems, note 401162

        2016/02/09     SYB: saphostctrl Solaris with Fault Manger, note 2275093

        2016/02/15     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2016/02/15     Additional Host Agent Operations for ACC/SAP LVM, note 1759181

        2016/02/15     Fix Oracle Online Copy Regression, note 1113545

        2016/02/15     Issues with sapacosprep, note 1084753

        2016/02/15     New operation for LVM to get hana infos, note 1550099

        2016/03/01     Additional environment win2012 fix, note 1113545

        2016/03/01     Problems with SAP Host Agent, note 1113545

        2016/03/01     Windows Metric Provider fixes, note 1113545

   12   2016/03/04     IBM i: Program does not start with error: tcsetattr: Inval, note 2288677

        2016/03/04     Saphostagent/maxdb: wrong error Prepare Database Copy, note 2269733

        2016/03/11     Additional Host Agent Operations for ACC/SAP LVM, note 1550099

        2016/03/11     Patch Collection 03.2016, note 1113545

        2016/03/11     SAP Host Agent Patches specific to Windows, note 2125101

        2016/03/11     SYB: saphostctrl/sapdbctrl - Support database metrics, note 2288152

        2016/03/11     Saposcol data not updated, saposcol hanging, note 1984681

        2016/03/11     Sapstartsrv: Fix http logfiles support, note 877795

        2016/03/15     Problems with SAP Host Agent, note 1113545

        2016/03/15     SAPHOSTagent/Hana: Detach im Scaleout-System funktioniert be, note 2283687

   13   2016/03/25     Fix collection 03 2016, note 1113545

        2016/03/25     IBM i: Der SAPHOSTAGENT und alle von ihm gestarteten Program, note 2289344

        2016/03/25     MSS: saphostctrl/sapdbctrl - Support database metrics, note 2290902

        2016/03/25     Problems with SAP Host Agent, note 1113545

        2016/03/25     Enhancements, note 1084753

        2016/04/05     Sync of -install / -restart, note 1113545

        2016/04/05     Rpm fixes for install/uninstall, note 1113545

Setting up SMS/Email Alerts in SUM Tool in MS WINDOW

Steps below is Showing you how to configure SMS and Email ALERT in SUM tool.

Once it is configured, SUM will send a email/SMS to the configured email ID and SMS when the SUM tool is waiting for user input.

Pre-requisites:

• Find out the SMTP server name within your organization and port (you can find it from TCODE SCOT in a SAP ABAP system)
• Find out Email to SMS for your phone number - It will be look like yourcellphonenumber@yourserviceprovider.com (Ex. 0000000000@serviceprovider.com)

Steps:

1. Create VB script (Alert.vbs) and place it in a location that can be accessed by SUM

Set objMail = CreateObject("CDO.Message")

Set objConf = CreateObject("CDO.Configuration")

Set objFlds = objConf.Fields

objFlds.Item("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2 'cdoSendUsingPort

objFlds.Item("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "Your SMTP Server" 'your smtp server domain or IP address goes here

objFlds.Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 'default port for email

'uncomment next three lines if you need to use SMTP Authorization

'objFlds.Item("http://schemas.microsoft.com/cdo/configuration/sendusername") = "your-username"

'objFlds.Item("http://schemas.microsoft.com/cdo/configuration/sendpassword") = "your-password"

'objFlds.Item("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate") = 1 'cdoBasic

objFlds.Update

objMail.Configuration = objConf

objMail.From = "email From "

objMail.To = "exampleemail@servername.com, examplephone@servername.com"

objMail.Subject = "SUM is Waiting for User Input"

objMail.TextBody = "Please Check SUM"

objMail.Send

Set objFlds = Nothing

Set objConf = Nothing

Set objMail = Nothing

Note: Save this file with file extension .VBS

2. Create the BAT (SendAlert.bat) file and place it in a location that can be accessed by SUM

X:\usr\sap\SID\SUM\SUMalertscript\Alert.vbs

3. Test the script

- verify the script can run without errors

- ensure you receive the email/SMS when you execute the script

4. Configuration in SUM tool (screen shot attached)

4.1. Launch SUM tool

4.2. select SUM tool ==> Select Alert ==> Alert Info

4.3. For "Program" select the script that you created SendAlert.bat

4.4. Leave "Alert File" default value or You can create file as you want with text in it

4.5. Set "Alert Delay" (default 500s)

4.6. Test the alert mechanism works by clicking the "Test" button

     - clicking the test button will call the script you prepared in step 1

     - so this should trigger an email alert

4.7. Ensure the "Set Active" check-box is checked

4.8. Press OK

Ref: Setting up Email Alerts in SUM Tool

More information on new SUM tool 1.0 SP16

Since new SUM tool (SP 16) allow multiple logins in to interact with tool for : Update of SAP Systems Using Software Update Manager (ABAP+Java Systems) and Update of SAP Systems Using Software Update Manager (ABAP Systems).

If you go to guide :

Update of SAP Systems Using Software Update

Software Update Manager 1.0 SP16

Technology: Java

Platform: Windows

Database: MS SQL Server

Page number : 98

Section : 7.4.6 Using the Alert Function

PS: Alerting is available as :Update of SAP Systems Using Software Update Manager (Java Systems)

First Check below setting in Solution manager

1. Apply theCentral notein Solution Manager. Most of the time some of the notes embedded in central note leads to various dump in standard T-Codes, so please make sue whether all are applicable to your scenario or not. Otherwise after implementing all, you can uninstall the inconsistent ones from SNOTE itself.

2. Cross check whetherOSS1 connectionis working or not and also check theSAP ROUTER connectionis open for it or not.

3. Install latest ST-PI & ST-A/PI software component patches in satellite as well as in Solution Manager Systems. (It's required for EWA configuration).

SLD Configuration in Solution Manager 7.1 STEPS:-

1. Execute RZ70 in ECC (as we have taken ECC as satellite system) and provide credential of Solution manager (Hostname and gateway) and trigger "Start Data Collection and Job Scheduling". It will send the data to Solution Manager SLD.

Click on Yes

If you don't get any error in in RZ70 and it shows that it got successfully sent

But if unluckily you get error like 'RFC OPEN ERROR' then follow below additional steps:

      A. Delete the SLD_UC & SLD_NUC RFCs from Solution Manager System.

      B. Surf http://<solman host name>: <port>/sld and click on ADMINISTRATION > PROFILE . Select the SECTION as ALL and give the details of ECC server host name & gateway details in two respective fields.

C. Now save the changes and restart the SLD.

D. Now again go to ECC server and run RZ70 by giving details of ECC server itself instead of Solution manager. It will trigger the SLD details to Solution manager

2. Now you can see the technical system details in Solman SLD. Now check whether "SAP_LMDB_LDB_0000000001" job (program name: AI_LMDB_R_SYNC_RUNNER) is continuously running successfully or not, because it plays vital role to drag data from SLD to LMDB.

3. Now go to SMSY_SETUP T-Code and click on "Schedule Data Transfer from TMS/SLD" or PRESS F8 and monitor the Landscape_Fetch job. After successfully completion of this job, you can see the ECC system SID in SMSY.

Similarly check in LMDB in solman

If the system is not detected in LMDB then execute the Batch Job “Landscape_Fetch” this will sync data between SLD and LMDB

Purpose

The purpose of this document is to list the error codes that can be returned during a trusted RFC connection, including the meaning of each return code.

Cause

A trusted RFC was configured between two ABAP systems.

However, something is not correct at this setup, causing an error while such trusted connection is being used.

Such error is usually observed at a "CALL_FUNCTION_SINGLE_LOGIN_REJ" dump (transaction ST22).

Solution

Fix the incorrect settings related to the trusted setup.

Knowing the meaning of the return codes can help identifying what needs to be fixed.

• The possible return codes for the "trusted system" (T-RC) are:

• The possible return codes for the "logon procedure" (L-RC) are:

See also

• SAP note 128447: Trusted/trusting systems
• SAP Help - Maintaining Trust Relationships between SAP Systems
• Official SAP Support Video on Youtube

  Related spaces:

• SAP NetWeaver Application Server
• SAP NetWeaver Technology Platform

Recently I was involved in a SAP SCM 7.0 upgrade using Software Update Manager (SUM) 1.0 SP16 (PL6). This SUM version lacks the functionality of alerting whenever the upgrade stops waiting for input. Instead of standing for hours staring to the tool, I developed a Windows script (Microsoft (R) Windows Script Host) that monitors the existence of the SUM\abap\tmp\upalert.log file.

The script is available at https://github.com/andrecastronunes/SAP-checkSUM

Usage:

C:\cscript checkSUM.vbs -file|-f <path\upalert.log> [-smtp <SMTP server>  -to|-t <semicolon separated e-mail addresses> -from <e-mail address>] [-verbose|-v]

C:\cscript checkSUM.vbs [-help|-?]

The file parameter is the upalert.log that is created whenever SUM stops waiting for input. For example, X:\usr\sap\SUM\abap\tmp\upalert.log

A log called X:\usr\sap\SUM\abap\tmp\upalert.log.TXT is created with all the stops and starts.

Example:

SUM stopped;18-05-2016 10:45:10

SUM running;18-05-2016 10:45:46

SUM stopped;18-05-2016 10:47:27

SUM running;18-05-2016 10:54:39

SUM stopped;18-05-2016 14:51:49

This script should run at certain intervals in background.

To avoid a command prompt window from showing up, the attached script runHidden.vbs can be used.

1. Go to client and system that you want to login (e.g. R01 CLIENT 300)

2. Tcode SM01 - to unlock the tcodes SCC4 AND SE06

     In SM01, Search SCC4, select SCC4 and client lock/unlock button.

Note: Locking/Unlocking the tcodes depends on project landscape requirement. As I worked in both environment currently I require to lock the t codes. sometimes it's not necessary depends on project requirements

3. After unlocking SCC4 , go in SCC4 --> "change option" tab ---> Edit (2 setting we have to change.)

3.1 Intial option:

          3.1.1. No changes allowed.

          3.1.2. No changes to repository and cross client customizing allowed.

3.2 change option:

          3.2.1 : changes without automatic recording nand no TR allowed.

          3.2.2. : changes to repository and cross client customizing allowed.

4. Save.

5. Go to Tcode SE06

     select system change option.

     5.1. global setting change to Modifiable. (By default it's Non-modifiable)

     5.2  In Edit tab, select,

          "Namespace Modifiable"

          "Software component Modifiable."

6. Save.

7. Again lock SCC4 and SE06 tcodes in SM01 as given in step2

Note: we cannot keep client open more time.

8. For client closing reverse the steps.

Configuring SAP Web Dispatcher to Support SSL - With Trust Manager

Information:

The SAP Web dispatcher lies between the Internet and your SAP system. It is the entry point for HTTP(s) requests into your system, which consists of one or more SAP NetWeaver application servers. As a “software webswitch”, the SAP Web dispatcher can reject or accept connections. When it accepts a connection, it balances the load to ensure an even distribution across the servers. The SAP Web Dispatcher therefore contributes to security and also balances the load inyour SAP system. (SAP)

Our missions this year is to focus on the security side of SAP system, we make many activities to make the SAP system more protected, more secure.

Introduction:

One of our web service applicationused SAP Web Dispatcher and we want that incoming connection will use HTTPS. For this we must configure SAP Web Dispatcher as an SSL (Secure Sockets Layer) server.

Pics by SAP

Pics by SAP

More information regarding the Web Dispatcher:

https://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/8FE37933114E6FE10000000A421937/frameset.htm

There are 2 ways to configure SSL for Web Dispatcher.

• Using the trust manager.
• Using the configuration tool sapgenpse.

This guide will help you to configure SSL for Web Dispatcher using trust manager.

Prerequisites:

You are familiar with the architecture and functions of SAP Web Dispatcher. In particular, you are familiar with the possible connections and how SSL is used with them. See the figure above. (SAP)

The SAP Web Dispatcher is installed and configured to use SSL.

Profile parameter:icm/server_port_ <xx> = PROT=ROUTER, PORT= <port>,TIMEOUT= <timeout_in_seconds>

Configuration:

Configure Environment variable

Picture 1.0 - environment variable SECUDIR

• Variable value = d:\usr\sap\SID\W00\sec

The reason we set the environment variable SECUDIR is because we will use thesapgenpseforCredentials and for export the certificate.

Creating the SAP Web Dispatcher's PSEs Using the Trust Manager

Picture 1.1 - trust manager

Go to transaction code STRUST right click on the File and choose create. (You have to be in edit Mode).

Picture 1.2 - Create (RSA)

• Change the name – Full FQDN of WD
• Change the Algorithm to RSA with SHA-1 (I used the old algorithm)

In cryptography, SHA-1 (Secure Hash Algorithm 1) is a cryptographic hash function. SHA-1 produces a 160-bit (20-byte) hash value known as a message digest. A SHA-1 hash value is typically rendered as a hexadecimal number, 40 digits long. (Wikipedia)

https://en.wikipedia.org/wiki/SHA-1

Picture 1.3 – Save the PSE

Save the PSE to local file.

Sending the Certificate Requests to a CA.

Click on File and choose the PSE we download before

Picture 2.0 - PSE you saved in the previous procedure

Click on Create certificate request, save the certificate reques to local file and send it to the CA for request response.

Picture 2.1 - certificate request

Picture 2.2 – Export certificate request

Picture 2.3 - Pics by SAP

After you get back the certificate response from the CA, Choose file and import the certificate response.p7b

Picture 2.4 – Import certificate response

Picture 2.5 – certificate response

Picture 4.3 – Add to certificate list

Click on Add to certificate list Save and replace

Picture 4.4 – the certificate is in the list

Now you can see the certificate is signed and valid.

Creating Credentials for the SAP Web Dispatcher

The SAP Web Dispatcher must have active credentials at runtime to be able to access itsPSEs.

Put the SIDPSE.pseinthe secdirectory

Picture 5.0 – PSE in the SEC directory

Run the following command:

sapgenpse seclogin -p SAPSSLS.pse -x abcpin -O ABCadm

Picture 5.1 - The following command line opens the SAP Web Dispatcher's SSL server PSE and creates credentials for the user SIDadm

Profile parameter

Add the following parameter to the WD profile

Picture 5.2 – Profile parameter

Restart the WD!

Test the SSL connection

Picture 6.0 – Certificate is issued

Export P12 certificate for F5 - Option

Picture 6.1 – Export the certificate

SAP Sources:

https://help.sap.com/saphelp_nw74/helpdata/en/49/3db10a19341067e10000000a42189c/content.htm

https://help.sap.com/saphelp_nw74/helpdata/en/49/4590d23a293b5be10000000a42189b/content.htm

https://help.sap.com/saphelp_nw74/helpdata/en/49/4561a6f4383659e10000000a42189b/content.htm

https://help.sap.com/saphelp_nw74/helpdata/en/49/458f193a293b5be10000000a42189b/content.htm

https://help.sap.com/saphelp_nw74/helpdata/en/49/458f193a293b5be10000000a42189b/content.htm

I hope this document will help you Feel free to ask questions

Thanks Naor.

Hello all,

I want to provide you the required steps (with the help of my colleagues from team) in order to create a connection between a SAP system running on Linux (SuSe in my case) and external SQL server. For the SAP system level configuration (DBCO transaction entry needed), you can check the note 178949 - MSSQL: Database MultiConnect . Main note for this activity: 1644499 - Database connectivity from Linux to SQL Server

My Linux version:

root-> cat /etc/SuSE-release

SUSE Linux Enterprise Server 11 (x86_64)

VERSION = 11

PATCHLEVEL = 4

1- Check you SAP Kernel, if dbmssslib.so file is in place. Make sure that mentioned packages in the note already installed:

root-> cd /sapmnt/SID/exe/uc/linuxx86_64/

root-> ls -ltr dbmssslib.so

-rwxr-xr-x 1 sidadm sapsys 1820217 Oct 30  2015 dbmssslib.so

root-> rpm -q glibc

glibc-2.11.3-17.90.4

....

2- Download ODBC Driver from this address:

• http://www.microsoft.com/en-us/download/confirmation.aspx?id=34687

3- Download unixODBC component from this address:

• ftp://ftp.unixodbc.org/pub/unixODBC/unixODBC-2.3.0.tar.gz

4- Create a temporary directory and copy those 2 downloaded files there. Then extract and build in following order:

root-> mkdir /tmp/MSSQL_ODBC

root-> gunzip msodbcsql-11.0.2260.0.tar.gz

Copy unixODBC under the new folder:

root-> cp unixODBC-2.3.0.tar.gz ./msodbcsql-11.0.2260.0/

Build it:

root-> cd ./msodbcsql-11.0.2260.0

root-> ./build_dm.sh --download-url=file://unixODBC-2.3.0.tar.gz

5- Install unixODBC:

root-> cd /tmp/unixODBC.10010.13772.354/unixODBC-2.3.0

root-> make install

Making install in extras

make[1]: Entering directory `/tmp/unixODBC.10010.13772.354/unixODBC-2.3.0/extras'

make[2]: Entering directory `/tmp/unixODBC.10010.13772.354/unixODBC-2.3.0/extras'

make[2]: Nothing to be done for `install-exec-am'.

root-> ./install.sh verify

root-> ./install.sh install --force

Check if ODBC properly installed:

root-> odbcinst -q -d -n "ODBC Driver 11 for SQL Server"

[ODBC Driver 11 for SQL Server]

Description=Microsoft ODBC Driver 11 for SQL Server

Driver=/opt/microsoft/msodbcsql/lib64/libmsodbcsql-11.0.so.2260.0

Threading=1

UsageCount=1

You can execute ADBC_TEST_CONNECTION report for testing the connection:

Other useful links and even a video from SAP:

http://scn.sap.com/community/hana-in-memory/blog/2016/04/15/microsoft-odbc-driver-for-sql-server-on-linux--by-the-sap-hana-academy

https://www.youtube.com/watch?v=npgNjSNXG2Q

http://scn.sap.com/docs/DOC-68640

http://scn.sap.com/docs/DOC-56997

http://scn.sap.com/community/sqlserver/blog/2013/01/19/how-to-access-an-external-microsoft-sql-server-database

http://help.sap.com/saphelp_hana_options_sds_conf/helpdata/en/e7/83b19c6f0f10149a438f15eda0ba9f/content.htm

Hi,

We have come across a situation where there are lot of validations because we are upgrading to HR Renewal 2.0 and there are a lot of changes that have to be moved from our validations systems to our real environments.

Validation systems RS4, RS2

Live systems: Dev, Qas1, Qas2, Production.

There are 2 validations performed..

During our first validations, change requests from RS4, RS2 were created, after HR Renewal Upgrades

Later RS4, RS2 had to be refreshed, HR Renewal Upgrades have to be performed and again there were another set of change requests from RS4, RS2 from the second validations.

Now, After our live environment upgrade to HR Renewal, the change requests have to be imported from the 2 validations.

So it is very important that in our second validations we had to set the Transport Request to the Number we decide, so that there will not be a duplicate entry from our first validation.

Last Transport Request Name from the first Validations: EX : RS4K900110, RS2K900131

Second Validations: First Transport Request: RS4K900111, RS2K900132: How can this be achieved?? is the purpose of this document.

it is simple, no access keys or no developer keys required.

1. SE16N

2. E070L table

3.Table content

4. Execute

5. Select the LASTNUM, TRKORR

6. Display

7. Switch on the debugging /h in the menu bar and enter

8. Edit the code "Show to Edit" as shown

9. Enter and Continue

10.Enter the transport Number that you want your transports to start with, in this case i am choosing SIDK900<110>

11. Now Save.

Now test if the changed worked by created a test transport..

12. And it will start with TRKORR+1

This was quite helpful in our project, Hope it will be useful to whoever is going through this document.

Regards,

Sebastian

Setting up SMS/Email Alerts in SUM Tool in MS WINDOW

Steps below is Showing you how to configure SMS and Email ALERT in SUM tool.

Once it is configured, SUM will send a email/SMS to the configured email ID and SMS when the SUM tool is waiting for user input.

Pre-requisites:

• Find out the SMTP server name within your organization and port (you can find it from TCODE SCOT in a SAP ABAP system)
• Find out Email to SMS for your phone number - It will be look like yourcellphonenumber@yourserviceprovider.com (Ex. 0000000000@serviceprovider.com)

Steps:

1. Create VB script (Alert.vbs) and place it in a location that can be accessed by SUM

Set objMail = CreateObject("CDO.Message")

Set objConf = CreateObject("CDO.Configuration")

Set objFlds = objConf.Fields

objFlds.Item("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2 'cdoSendUsingPort

objFlds.Item("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "Your SMTP Server" 'your smtp server domain or IP address goes here

objFlds.Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 'default port for email

'uncomment next three lines if you need to use SMTP Authorization

'objFlds.Item("http://schemas.microsoft.com/cdo/configuration/sendusername") = "your-username"

'objFlds.Item("http://schemas.microsoft.com/cdo/configuration/sendpassword") = "your-password"

'objFlds.Item("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate") = 1 'cdoBasic

objFlds.Update

objMail.Configuration = objConf

objMail.From = "email From "

objMail.To = "exampleemail@servername.com, examplephone@servername.com"

objMail.Subject = "SUM is Waiting for User Input"

objMail.TextBody = "Please Check SUM"

objMail.Send

Set objFlds = Nothing

Set objConf = Nothing

Set objMail = Nothing

Note: Save this file with file extension .VBS

2. Create the BAT (SendAlert.bat) file and place it in a location that can be accessed by SUM

X:\usr\sap\SID\SUM\SUMalertscript\Alert.vbs

3. Test the script

- verify the script can run without errors

- ensure you receive the email/SMS when you execute the script

4. Configuration in SUM tool (screen shot attached)

4.1. Launch SUM tool

4.2. select SUM tool ==> Select Alert ==> Alert Info

4.3. For "Program" select the script that you created SendAlert.bat

4.4. Leave "Alert File" default value or You can create file as you want with text in it

4.5. Set "Alert Delay" (default 500s)

4.6. Test the alert mechanism works by clicking the "Test" button

     - clicking the test button will call the script you prepared in step 1

     - so this should trigger an email alert

4.7. Ensure the "Set Active" check-box is checked

4.8. Press OK

Ref: Setting up Email Alerts in SUM Tool

More information on new SUM tool 1.0 SP16

Since new SUM tool (SP 16) allow multiple logins in to interact with tool for : Update of SAP Systems Using Software Update Manager (ABAP+Java Systems) and Update of SAP Systems Using Software Update Manager (ABAP Systems).

If you go to guide :

Update of SAP Systems Using Software Update

Software Update Manager 1.0 SP16

Technology: Java

Platform: Windows

Database: MS SQL Server

Page number : 98

Section : 7.4.6 Using the Alert Function

PS: Alerting is available as :Update of SAP Systems Using Software Update Manager (Java Systems)