The workload monitor reads the workload statistics from the workloadcollector database. Various collectors must run at regular time
intervals so that this database always contains current data.

The background job SAP_COLLECTOR_FOR_PERFMONITOR starts the program RSCOLL00 and this program checks the TCOLL table for program which needs to be started.
Workload collector program starting from system release 7.00 the background job SAP_COLLECTOR_FOR_PERFMONITOR should always be scheduled
in client 000  and the #System Time Zone# which is maintained in the transaction STZAC in client 000 should be exactly the same as the OS time zone setting.

Please check followoing notes:
926290 - SWNCCOLL: SAP workload NW collector collects no data
12103  -  Contents of the TCOLL table
16083  -  Standard jobs, reorganization jobs

198411  -   Current data and information about time zones

481835  -   Analyzing the time zone settings

741734 - Incorrect times due to the time zone settings
910897 - ST03N: Configuration of the time profile

The job SAP_CCMS_MONI_BATCH_STARTUP_DP is an event triggered job and it is started automatically by the background dispatchert.

Configuring the Workload Monitor
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2d/b8be3befaefc75e10000000a114084/frameset.htm

Displaying and Changing the Scheduling of Performance Collectors
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/84/9e0e422dfcdc2ce10000000a1550b0/frameset.htm

SAP Netweaver online documentation new workload collector
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/27/930e422dfcdc2ce10000000a1550b0/frameset.htm

At every transaction step, ABAP work processes first write kernel statistics and application statistics data to a buffer. This data is then saved in an OS file in
the directory on the host of ABAP instance.

GRMG data collector method is started by the AutoAbap dispatcher program SAPMSSY8 and that it should be started by a GRMG background job in the transaction SM37.

In the transaction SM37 can be seen which GRMG background job is started every 5 minutes for this (note 1160083).

"If in the GRMG-Lite scenario a user and encrypted password is defined, please try to start the GRMG scenario in client 000, to see if the encrypted password can be found in client 000. If it cannot be found in client 000, you have to recreate the password again in client 000, as described in note 1323253."

908760 - NetWeaver - GRMG Portal Heartbeat

1134713 - STRING_LENGTH_TOO_LARGE in GRMG_APP ABAP-Service

974742  - ABAP Service GRMG_APP: MESSALERT in Response reset

1175659 - CCMS:Availabilty Monitoring for Loyalty System.

Please check how the GRMG data collector method is started in the <SID> system. If this is done by a background job, as described in note
1160083, than please check if the related background job is correctly scheduled in the transaction SM37 If the GRMG data collector method is not started by a background job, please open the complete GRMG monitoring structure in the transaction RZ20 and please select from the menu on top of the RZ20 screen "Views> Status data collector" and please inform us about what is exactly reported behind each GRMG monitoring node

GRMG Monitoring of SAP NetWeaver Components:
http://help.sap.com/saphelp_nw70/helpdata/EN/de/9bdb4064da712ae10000000a155106/frameset.htm

Configuring GRMG Monitoring
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/49/1758d6a2e314cde10000000a42189b/frameset.htm

Activating and Customizing Monitoring with the GRMG
http://help.sap.com/saphelp_nw73/helpdata/en/34/60cdd0d3fdeb4cb8cbc4eac681f961/content.htm

Monitoring the Availability of Web Pages with GRMG Lite
http://help.sap.com/saphelp_nw70/helpdata/en/6d/6fe040852f712ae10000000a155106/frameset.htm

Trouble-Shooting GRMG Scenario Execution
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/49/35125876aa5817e10000000a42189c/content.htm

The SAPOSCOL shared memory segment is created in the system number 99 area and on UNIX systems the related IPC object can be reported by using the SAP OS command ‘showipc 99’. Always check the dev_coll file to see if enough shared memory is allocated.

On Windows platforms SAPOSCOL is started as a windows service (note 436186). On UNIX platforms SAPOSCOL is started by the startsap script but it is not stopped by the stopsap script because it could be that there is more than one SAP system running on the same server.

If the SAPHOSTAGENT is installed on a server then SAPOSCOL is started by the program saphostexec (note 1064968).

When the SAPOSCOL process is stopped it will also try to remove the shared memory segment. Unfortunately this is not always possible,
to delete the shared memory segment manually you can use on UNIX systems the SAP OS command ‘cleanipc 99 remove’ (this will
remove all the ipc objects for the system number 99, also for the SAPCCMSR agent) and on Windows systems you can try to start SAPOSCOL in dialog mode by using the command syntax ‘saposcol –d’ and execute the command ‘leave’.

Step by step cleaninig the SHM:

- Stop the old SAPOSCOL process
- If there are SAPCCMSR or SAPCCM4X agents running on the same server it is also better to stop these processes too.
- Check if the shared memory segment is correctly removed (On Windows systems you can try to start SAPOSCOL in dialog mode and execute the

‘leave’ command. If this does not remove the shared memory segment on an OS restart will help. On UNIX systems you can use the OS command

‘cleanipc 99 remove’)
- Delete the coll.put file which is stored in the SAPOSCOL working directory
- Install the new SAPOSCOL executable in the correct executable directory
- Start SAPOSCOL (and the CCMS agents) again.
- After this always check the dev_coll file to see if the new collector process also did recreate the shared memory segment again.

Then a sure method to delete the existing shared memory segment is a restart of the Windows OS.

By default the SAPOSCOL collector process will try to collect new OS snapshots and store this date in the shared memory segment every 10 second.

For this the shared memory segment status needs to be set and if another process is connected to the SAPOSCOL shared memory segment

this is not possible and because of this the collector interval will be skipped.

How to analyse the missing performace data situation and how to check SAPOsCol issues

http://wiki.scn.sap.com/wiki/display/NWTech/How+to+analyse+the+missing+performace+data+situation+and+how+to+check+SAPOsCol+issues

Known:Warnings and error messages of dev_coll and possible problems with SAPOSCOL
http://scn.sap.com/community/netweaver-administrator/blog/2013/10/08/contain-of-devcoll-and-possible-problems-with-saposcol

SAPOSCOL Log Files
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c4/3a6c67505211d189550000e829fbbd/content.htm

HI

I was changing my SAP System SID and i thought it will be useful to share the used procedure which is extracted from System Rename guide and Available SAP NOTES .

I Hope my first blog will be on expected Level at least for beginners .

This Blog explains how to rename an SAP system using software provisioning manager 1.0.Which is the successor of the product- and release-specific delivery of provisioning tools, such as SAPinst and part of the Software Logistics Toolset . for more information check SAP NOTE 1680045

It is valid for SAP systems based on SAP NetWeaver releases described on the following  SAP NOTE 1619720  - System Rename for SAP Systems based on SAP NetWeaver

Available on SAP Service Marketplace at:

http://service.sap.com/sltoolset -> Software Logistics Toolset 1.0 -> Software Provisioning Manager.

by the way it is used also for

1-  Installation, copy, and transformation for products based on SAP  NetWeaver AS ABAP and AS Java

2- dual-stack split

3- System Rename

4- Frontend Installation and Distribution

You can rename the following SAP systems:

Systems installed by using the standard SAP tools.

Systems copied by using classical system copy (R3load/Jload or DB-specific procedure).

Systems created by using backup or restore with procedures offered by Microsoft Windows

Systems created by using SAP NetWeaver Landscape Virtualization management

Cloned systems (virtual to virtual, virtual to physical, or physical to virtual)

In the following case i am trying to change the SAP System SID , DB SID , and NR for the Source System

which is based on  SAP NetWeaver 7.0x and Oracle DB and windows Server 2008 OS

SAP System SID = S6C

DB SID = S6C

Nr= 00

to New SID the Target System

SAP System SID = T11

DB SID = T11

Nr= 11

Constraints:

Rename can be performed on primary application server instances – additional application server instances have to be reinstalled

according to your OS download Software Provisioning Manager1.0 Package  from SAP Service Marketplace at:

http://service.sap.com/sltoolset ->  1.0 -> Software Provisioning Manager

Log on to your SAP system

Extract the SAR file

Running the Software Provisioning Manager

On the Welcome screen, choose the following:System Rename ==> central System ==> SAP system Rename

Follow the instructions in the input screens AS shown in the following Step

Select SAP System Rename

And Click Next

Enter the Required  Parameter for source system (SID) and target System (NEW SID, Global Host and Installation Drive)  And Click Next

SAP Global Host is giving by default

If you Plane to use Virtual Host Name Make sure that the the virtual host name is bound to local network interface

For the Target Instance Number

Do not use the following numbers:

43 - used by MSCS "in case you are using MSCS"

89 - used by Windows Terminal Server

Click Next

Enter the Source SID and Target SID and Host Name For the Database and  New Password For Oracle Schema

Recommendation

Enter exactly the central instance number and SID that you have entered during the central instance installation.

If you choose different domain you have to follow the procedure of Changing Windows Domain in System Rename guide

Click next

the above step will be required in case you did not perform Maintaining Users and Groups Step

Enter the Password for the following OS user (<SID>ADM ,SAPService <SID>)

Click Next

if you like to change the ORACLE HOME deselect the checkbox of rename Oracle Software

Click next

Leave the field Empty

Click Next

Click Next

Click Next

Make sure your SAP System IS down

Click Next

Click OK

System rename finished successfully

-------------------------------------------------------

Follow-up Activities

Potentially, all follow-up activities for a system copy are also valid for the rename of your SAP system  For more information, see the system copy documentation

1-      check the New SID name on OS Level in the following Directories

          /usr/sap/SID

          /Oracle/SID

2 -       Logon to sap SAP system and as you have New Server Name Adapt your configuration accordingly

3-      Run an installation check: Administration System administration Administration Installation Check(transaction SM28).

4-      Perform server check (transaction SM51)

5-      Adapt the Transport Management System (transaction STMS) According to the New SID if it is required

6-      Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAH, SDBAP, SDBAR as it is Contain log and Monitoring data related to the Old SID

7-      Adapt all Background jobs needed in the SAP System

8-      Adapt the definition of the printers to meet the new system

9-      Adapt the RFC destination:  (transaction SM59).

10-     Adapt Your Operation Mode If it is configured

11-     Adapt Your Logical System According to your naming convention was used

12-     Adapt the instances and profiles

13-     Adapt CCMS settings (for example, alert thresholds, reorganization parameters of CCMS table MONI) if required.

14-     Replace all existing PSEs in the target systems with new ones, which contain the new system's information

15-     Add your System To the SLD

Restarting the SAP System

----------------------------------------------

Best Regards

As you might know, currently when you will perform an installation of a fresh SAP system based on SAP NetWeaver 7.0x and higher, there is an instance for ASCS. It was separeted from the ASCS for all the fresh installations.

But why SAP did that?

Because it is very crucial to ensure the availability of the Message Server and the Enqueue Replication Server. This way you will have one dedicated instance to perform the failover. Apart from High Availability, SAP recommends and/or wants to enable a setup where all systems have the same types of instances. For this reason and also to make High Availability enabling a bit easier, the splitt off functionality has been delivered.

But if you have installed your SAP System a long time ago and your ASCS is into the PAS, you can split them into 2 instances. For systems based on SAP NetWeaver 7.1 or higher, it is possible to use the latest version of SWPM (For further reference, please check SAP note #1680045).

I used as example the option to split off a SAP NetWeaver 7.3 EHP 1 with Oracle. But the option is available for every system and database combination present in the SWPM for NW 7.1 and higher.

But if you have a system based on SAP NetWeaver 7.0x, this option is not available in the 70SWPM, The only way to do that would be running a system copy of the system. Then during the target system installation, you would be able to install the new system with sepated ASCS from PAS .

For further information regarding this subject, you can check the Installation Guide for SAP NetWeaver 7.1 and higher. Check the section 2.5 Central Services Instance for ABAP Separate from Existing Primary Application Server Instance of an Upgraded System for furtther information regarding the subject pointed in this post.

Also check the section 7.6 Splitting Off a Central Services Instance for ABAP from an Existing Primary Application Server Instance to know how to run the split.

Dear All,

BO 4.0 configuration with SLD using Auto Configuration Tool.

I have used this tool , for all the below activity.

1. Adding BO system to SLD

2. Configure Wily Introscope on BO System.

SAP Note followed :

BO configuration as per SAP Note 1653689 SolMan 7.1 Managed Sys Setup BOE 4.0.

In this note you will find the attachment for

1. AC (AutoConfigure)

2. BOE4_scripts.zip

3. CMS_lst.zip

4. SAP_BOE4_procmon.zip

Prerequisite To Start Auto Configure:

1. You need to install the java 6 jre on the window server.

2. Download the SAPCAR file from Service Market Place

3. As per the SAP Note 1508421 - SAP SLD Data Supplier for Apache Tomcat

    Download the TomcatSLDDataSupplierWEB.zip which will contain the .war file.

2. You need to install the SAPHOST Agent and SAP Diagnostic Agent.

Starting the Auto Configure Tool :

1. Download the AC_part1.rar

2. Extract the AC_PART1.rar

On Extracting the folder , you will get the below files. Now double-click on AutoConfigure_2012_11_12.

In the downloads folder , place all the downloaded file mentioned in SAP Note 1653689 SolMan 7.1 Managed Sys Setup BOE 4.0

Step 1: Below window will appear for AutoConfigure , where you need to select the option which you want to run.

Step 2 : At first , i have selected four options and then click on Execute Selected button.

             It will ask to enter the Tomcat Service.

Step 3 : Enter the SLD Server host

Step 4 : Enter the SLD Port number

Step 5 : Enter SLD User (which has the read and write permission).

Step 6 : Enter the password

Step 7 : SSL is not configured , so we are not using HTTPS over here

Step 8 : Click on Yes , to trigger data to SLD

Step 9 : Enter the BOE system information such as

              1. BOE System : <hostname>:<port> (port :6400 for example)

              2. username and password

Step 10 : Enter the hostname , port of Enterprise Manager and change the value of IntroscopeAgentEnableInstrument from false to true.

Step 11 : Enter the SMD Agent hostname and port(5$$18)

Step 12 : Restart the BOE system

Step 13 : Installation of Wily agent on BOE , Select Install a new Agent

Step 14 : Provide the location where you want to install the Wily Agent.

                By Default , we place the wily in /usr/sap folder but we need to provide folder /usr/sap/ccms for

                Auto Configure tool.

Step 15: It will display the path where you want to Install Wily.

Step 16 : Enter the Introscope EM Host

   Step 17 :  Enter the Introscope EM port

   Step 18 : Now it will add the Wily parameter in tomcat java options and to make it effective it will ask to restart the

                   Tomcat Server. It will make the required changes in Introscope_Agent_ac.profile

Step 19 : Now Configure it will configure the jmx which will be required by the solman system to connect to Tomcat.

               It will ask to for JMX user (smdAgentRole by default)

Step 20 : Enter the password

Step 21 : Enter the port number which is 9004 by default.

Step 22 : Click on OK , and this parameter will be used in manage system setup for Tomcat in solution manager.

   Step 23 : Restart the Tomcat

  BO configuration with SLD using Autoconfigure tool Part -II

http://scn.sap.com/community/netweaver-administrator/blog/2013/11/29/bo-configuration-with-sld-using-autoconfigure-tool-part-ii

Step 24 : Now it will create the parameter JVM GC Log and to make it effective you need to restart Tomcat

   Step 25 : Tomcat logging parameter will get added for Tomcat

   Step 26 : Restart Tomcat

   Step 28 : Here we will deploy the TomcatSLDDataSupplierWEB.war file on Tomcat. In this Step we face a

                   issue has we were not able to logon to Tomcat server.

Step 29 : goto the directory ./Tomact6/conf and open the tomcat-users.xml

Step 30 : Remove the symbol <!--  and --> after <tomcat-users> and before </<tomcat-users>

   Step 31 : Create a new entry

                   <role rolename="manager">

                   <user uername="tomcat" password="tomcat" roles="tomact,manager">

Step 31 : Now again execute the phase and click on Update it button

Step 31 : Click on Keep it as we have created the connect.key in the first step.

Step 32 : Enter the Extended SID for the BOE system. In solman it will show <SID>_WAS

  Step 33 : Click on Yes .In this step it will make a entry in sldDataSupplier.properties files and the file is located in ...\Tomcat6\webapps\sap.com~TomcatSLDDataSupplierWEB folder.

   Step 34 : We can use the url

   Step 35 : Enter the Solution manager stack level

After following the above steps from PART I and PART II , BOE system will be added to the SLD and will get reflected in Manage system configuration.

Thank you so much in advance for reading the blog and also correct me if i have mentioned something wrong!!!

With Regards

Ashutosh Chaturvedi

Before I start with the steps let me tell you about the environment where I have done the SWD patching.

This is installed on a standalone Windows (Win08 R2 64-bit) system.

Current Version 701 Patch number 31

Idea for patching web dispatcher  is very simple as follows:

• Download the latest patch from SMP

• Stop all the web dispatcher instances  and backup the executable from the directory  <Drive_Letter>:\usr\sap\<SID>\SYS\exe\nuc\NTAMD64

• Extract the SAR file into any temp directory

• Copy the files from sapwebdisp_< PL >-<...>.SAR into the directory <Drive_Letter>:\usr\sap\<SID>\SYS\exe\nuc\NTAMD64) and start the web dispathcer instances.

• Check your sap web dispatcher version :

Congratulations!! Your sap web dispatcher is patched from 701 to the latest 720.

Some pitfalls that might come up :

While extracting the SAR files into the current executable directory E:\usr\sap\W20\SYS\exe\nuc\NTAMD64, you may error  saying some file or folder is open  and will not allow you to copy, reason is not all services are properly shut down when we stopped the isntances with MMC  See below:

The workaround is to extract the file to some temp directory and drop the extracted files to the destination folder ,E:\usr\sap\W20\SYS\exe\nuc\NTAMD64

I still got the windows pop up that some files are in use by another program , I have to rename the files like "dghelp.dll.old" and then proceed with copying after doing the same for other files which were still being used. I finally  managed to copy the whole executable files to the destination folder.

Recommended SAP Notes : 908097

This is my first blog, hope some may find it useful

When the jcontrol fails before it reaches ‘starting processes’ check first the bootstrap logs.

Bootstrap logs are located in \usr\sap\<SID>\<instance>\work

In these logs you find log-information on the beginning of the startup process of the J2EE engine.

Most important ones are:

dev_bootstrap

dev_dispatcher

dev_server

When the jcontrol fails shortly after start with ‘some processes running’ check first the dispatcher logs.

Dispatcher logs are located in \usr\sap\<SID>\<instance>\ j2ee\cluster\dispatcher\log

Specially check the latest defaulTrace.<x>.trc

When the jcontrol fails some after start with ‘some processes running’ check first the server logs.

Server logs are located in \usr\sap\<SID>\<instance>\ j2ee\cluster\server0\log

Specially check the latest defaulTrace.<x>.trc

Hello Everyone,

Monitoring a standalone DB server using CCMS agents is a very common activity and there are some points that we should pay attention to in order to have data available exactly where we want it.

In most of the cases the idea is to have the OS monitoring information available in transactions like ST06 and OS07, therefore instead of using RZ21 to create a new remote monitoring entry and point to this host you should use a standalone CCMS agent which can be downloaded from the SAP Marketplace.

In case the registration of this host is made using RZ21, the OS monitoring data for this host system will only be available in transaction RZ20.

More details about the registration using RZ21 please check the below link.

Registering SAP NetWeaver Components and Hosts in CEN - Infrastructure of the SAP NetWeaver Management Agents - SAP Libr…

Since there is no ABAP instance running on the standalone DB server, the SAPCCMSR agent should be used in the registration.

If the information is required in the old ST06 transaction and the database is installed in a different host, than the SAPLOCALHOST parameter should be maintained correctly in the agent profile, the value for this parameter should be exactly the same as the SAPDBHOST parameter value in the instance profile. If it is done correctly the saposcol destination of the database host will automatically flagged as DB Server in the transaction AL15 and the data will be visible in the ST06 transaction.

For more details about using the standalone CCMS agents, installing, registering and setting up the SAPLOCALHOST parameter please check the below links.

Controlling CCMS Agents (SAP Library - CCMS Agents)

Installing/Registering the CCMS Agents for Experts (SAP Library - CCMS Agents)

Profile Parameters for Central Monitoring - Infrastructure of the SAP NetWeaver Management Agents - SAP Library

You can also refer to the SAP Note 1491115 for this.

1491115 - OS monitors ST06n, OS07n do not display data in CEN system

Hope you like it,

Daniel Grings

Hello Everyone,

I decided to create this short guide on how to analyze the EXPORT_TOO_MUCH_DATA dumps in SAP_COLLECTOR_FOR_PERFMONITOR.

We need the following in order to precisely analyze this kind of dump.

1) Full dump details (You can also find this in ST22).

2) Access to SE16 to check the entries in the SWNCMONI table.

In the dump details you can always see two important sections for this analysis.

The first one is easily found under "AGGTYPE" in the dump details as you can see below.

AGGTYPE

4

WQ <<<

This is the profile name which SAP_COLLECTOR_FOR_PERFMONITOR was doing the TOTAL calculation.

There is a strong indication that this profile is the responsible for the dumps.

The second one is found under "I_MONIKEY-PERIODSTRT" as you can see below.

N0 I_MONIKEY-PERIODSTRT

L0 16

V0 20131001 <<<

This is showing us what is the period on which the SAP_COLLECTOR_FOR_PERFMONITOR generated the dump while creating the TOTAL.

For the next steps please refer to the SAP Note 1110822.

1110822 - Workload collector: Reducing the size of aggregates

The SWNC_COLLECTOR_COMPRESSION report should be used in order to compress the data associated to the profiles with more than 15 thousand entries

in the table SWNCMONI.

Data you have collected should be entered as per the below screenshot in SE16, after this you can use the button "Number of Entries" to check how many

entries exist each of the profiles. The profile names are WD, WF, WJ, WM, WO, WP, WQ, VA, VB, VC, VD, VE, VO,VV.

After compressing all the needed profiles run the report SWNC_COLLECTOR_RECOMPRESS one time manually as per the SAP Note 1110822.

In case the dumps are happening to the current month calculation, the effects of the compressions will only appear in the next month and the dump

will disappear in two weeks.

You check once again the number of entries in SWNCMONI table to make sure there is an expected number of entries for each profile (less than 15 thousand entries for each one).

Hope you like it,

Cheers,

Daniel

Dear all,

We need to deploy the MQ libraries on java engine so that messages can be processed from PI/PO sytems to MQ server.

I have taken the reference from the below SAP Notes

1. 747601 - J2EE JMSAdapter: MQSeries libraries

2. 1770304 - PI: How to prepare the com.sap.aii.adapter.lib.sda for deployment

From the SAP Note 747601 , you will get the required libraries information which you need to deploy as per the version of MQ server.

You will need to build aii_af_jmsproviderlib.sda and com.sap.aii.adapter.lib.sda depending on the version of XI adapter.

For XI Adapter 3.0/7.0 , you need to have aii_af_jmsproviderlib.sda file.

For XI Adapter 7.1 above , you need to have com.sap.aii.adapter.lib.sda file.

From where to get the above files :

For version 3.0/7.0 , You will get the aii_af_jmsproviderlib.sda

/usr/sap/<SID>/DVEBMGS<SYSNO>/SDM/root/origin/sap.com/com.sap.aii.af.jmsproviderlib/SAP AG/3.0.0220040608173429.0000/aii_af_jmsproviderlib.sda

For version 7.1 , you will get the com.sap.aii.adapter.lib.sda in SAPXI3RDPARTY08_0-10009499.SCA file.

Preparing com.sap.aii.adapter.lib.sda for deployment :

In our case , the MQ server version is 7.0 , so we have used the below libraries.

1. CL3Export.jar

2. CL3Nonexport.jar

3. com.ibm.mq.headers.jar

4. com.ibm.mq.jar

5. com.ibm.mq.jmqi.jar

6. com.ibm.mq.pcf.jar

7. com.ibm.mqjms.jar

8. connector.jar

9. dhbcore.jar

10. fscontext.jar

11. providerutil.jar

12. rmm.jar

Step 1 :

Rename the SAPXI3RDPARTY08_0-10009499.SCA file to SAPXI#RDPARTY08_0-10009499.ZIP and extract it. You will get the below directories

1. BUILDARCHIVES

2. DEPLOYARCHIVES

3. META-INF

Step 2 :

Enter into the DEPLOYARCHIVES directory where you can locate the the required .sda files. com.sap.aii.adapter.lib.sda.

Step 3 :

Rename the com.sap.aii.adapter.lib.sda to com.sap.aii.adapter.lib.zip file and extract it

Step 4 :

Extract the zip file com.sap.aii.adapter.lib.zip

Step 5 :

Now goto the directory com.sap.aii.adapter.lib and lib folder you need to put all the jar files as mentioned in the sapnote

Step 6 :

Goto the directory SAPXI3RDPARTY08_0-10009499\DEPLOYARCHIVES\com.sap.aii.adapter.lib\server and open the provider.xml file

Step 7 :

Now edit the provider.xml file as below, we need to add lines <jar-name>lib/CL3Export.jar</jar-name> between the tags <jar></jar>.

Save the provider.xml file.

Step 8 :

Now , zip  the file com.sap.aii.adapter.lib to com.sap.aii.adapter.lib.zip

Step 9 :

Now rename the com.sap.aii.adapter.lib.zip file com.sap.aii.adapter.lib.sda

Step 10 :

Now deploy the file with the help of SDM , JSPM and telnet.

I will update the blog from time to time.

Thanks for reading it.

With Regards

Ashutosh Chaturvedi

Short time ago I was faced with the issue to transfer my SAP Client Passport certifcates from a Windows 7 installation to Windows 8.1.

After processing the Signle Sign-On Wizard in the SAP Support Portal (in IE11) I received always errors about my active X settings in Internet Explorer.

So after a long time of trying to change my activeX settings i tried to use the IE Developer Tools and found a way to install my passport certificates into Windows 8.1 with Internet Explorer 11.

1. To open the IE Developer Tools press F12
2. On left side change to the options "Emulation"
3. Change the "Documents modus" to 5
4. Change the "Browser Agent" to "Internet Explorer 7"

(Sorry for the german screenshot)

After reconnecting to http://service.sap.com including the changed browser settings the import Wizard of Windows 8.1 works fine.

Don't forget to reset your emulation Settings!

Christian

As usual, this blog is not for geniuses or Basis gurus! Most of the time I like to write for people like me who learns by doing and some time looking at others works.

In this blog, my focus will be on two things:

1. How to work with the NetWeaver Developer Studio 7.31 (NWDS) for deploying and un-deploying any SAP or third party java component.
2. How to play with SCA, SDA & jar files where to look for the required class.

...of-course with help of lots of screenshots, fun starts now!

I think I am not re-telling what is present at the link below

SAP NetWeaver Developer Studio 7.1 Overview

SAP has this habbit to take out people from their comfort zone, some time for good and some time for ....... anyway.

It will not be fair to compare SDM and NWDS. Later is much versatile tool, I have seen PI guys working with NWDS instead of their old ways from SXMB_IFR then ESR or IB.

This is just an example, that NWDS is not just for us(Basis). Lets see how we can use this tool:

NWDS can be downloaded from service market place, unzip it and its ready to work. Double click on executable, it will first ask for a directory location, you  can provide the location or let it select the default one, its upto you.

<<If you want to view screenshot clearly then you need to click on each of the screenshot so that they can open in actual size, otherwise some of them are not clearly readable.>>

Here is the first screen. Click on Windows the preferences.

You will get screen like below select SAP AS Java, if you have older version, find something similar to that.

On right side you can find Add button. Click on it, you will get another pop-up window seeking

1. your java hostname,
2. Java system instance number like you give in your URL(http://<hostname or IP>:5NN00) here NN is instance number.
3. Add to Domain: I select from drop down value "Default"

When you click on OK you may be able to view one entry like below for your Java system ID. If you are not able to see any entry, don't worry click OK because sometime I get the entry and sometime I don't see any entry, but in both cases it works as expected.

Now again click on Window -> Show View -> Other

You will get below screen, Select "Deploy View" and click on OK.

Now click on External Deployable Archives, you will see options with radio button on right side.

Selecting the option "Update deployed archives with any version"

By this option you can over-write the java component of present version with any version you want.

(For example with SAP or someone else suggestion you upgraded certain components but it didn't worked as expected so you want to revert it back. Additionally I have used this options to deploy com.sap.aii.af.axisprovider component several times)

Right click on "External Deployable Archives" and click on Add

you can browse to the SCA or SDA files where you have stored them on to your system from where you have started NWDS. You can select more than one component at a time.

After selecting and clicking on Open button we can see those entries below "External Deployable Archives"

Again you can right click on "External Deployable Archives". Now you can see the deploy option, click on the Deploy.

It will prompt for your Java system admin and password, unless you have not selected the option "Store username and password in secure storage"

(Based on the type of your system it could be j2ee_admin or administrator or any other user with similar authorization.)

Personally I prefer to give password manually everytime, so I uncheck the tick like below screenshot. Its your choice.

If everything is fine the deployment will start and you can click on right-bottom to view details of deployment.

including "progress view" from my another deployment just to show.

The time taken varies based on the number of components and their type. When it is finished you can see the details.

1. File:C:\Users\ahmadi\Desktop\AS1\AJAXRUNTIME07P_7-10008281.SCA

                Name:AJAX-RUNTIME

                Vendor:sap.com

                Location:SAP AG

                Version:1000.7.30.7.7.20130709001200

                Deploy status:Success

                Version:LOWER

1. File:C:\Users\ahmadi\Desktop\AS1\ENGINEAPI07P_21-10007921.SCA

                Name:ENGINEAPI

                Vendor:sap.com

                Location:SAP AG

                Version:1000.7.30.7.21.20130620213900

                Deploy status:Success

                Version:SAME

1. File:C:\Users\ahmadi\Desktop\AS1\FRAMEWORK07P_5-10007877.SCA

                Name:FRAMEWORK

                Vendor:sap.com

                Location:SAP AG

                Version:1000.7.30.7.5.20120702074800

                Deploy status:Success

                Version:SAME

1. File:C:\Users\ahmadi\Desktop\AS1\WDRUNTIME07P_18-10007825.SCA

                Name:WD-RUNTIME

                Vendor:sap.com

                Location:SAP AG

                Version:1000.7.30.7.18.20130715190900

                Deploy status:Success

                Version:LOWER

1. File:C:\Users\ahmadi\Desktop\AS1\SERVERCORE07P_66-10007988.SCA

                Name:SERVERCORE

                Vendor:sap.com

                Location:SAP AG

                Version:1000.7.30.7.66.20130705014900

                Deploy status:Success

                Version:SAME

Result

Status:Success

Now lets give a quick glance at how to un-deploy any component, though I have not done it my self yet! because there was no requirement, and I need to keep my job going too

Lets get the undeploy View.

Click on Window -> Show View -> Other

You will get below screen, Select "Undeploy View" and click on OK.

As we have seen in earlier discussion we need to put the hostname, instance and domain.

We get a view like below. Check those two groups of radio button. You need to be very sure what you are doing. If I need to undeploy any component and I am not sure if that component has dependency, I will select "If depending stop"

We can click on refresh.

It will prompt for Java Admin User ID and password

based on the type of your system it could be j2ee_admin or administrator or any other user with similar authorization. Now you will be able to see all the installed components in left hand side of Undeploy View.

Select the component or sub-component and right click on that. Select "Add to Undeploy List" by doing that you'll see the component name will get added to right hand side panel along with its detail.

You can add more than one components in the "Undeploy List Panel".

Now you can see the button  ("Undeploy all items in the list") as pointed in below screenshot.

When all set, click on the button to undeploy the component.

In this last section, lets discuss the structure of SCA, SDA and jar file.

Recently I was working with com.sap.aii.af.axisproviderlib.sda file, because there was requirement to deploy some missing components in PI related to Axisprovider. Below is the screenshot.

In your PI System you can get this screen by this URL

http://<PI Hostname>:5<NN>00/XIAxisAdapter/MessageServlet

This will also give you suggestion from where to download missing jar file. Sometime you will not be able to get compatiable jar files, you don't have to find the jar file with exact same name. What is more important is getting the class file in exactly same location as it is being searched by the System.

Lets verify if the jar file is correct file or not. First you will get a zip file, you need to unzip it to get jar file. If you are downloading from net you can directly get jar file. When you find the jar file, you can make a copy of jar file and rename it to .zip file. Now use your installed zip program like winzip or any other program to see where is the desired .class file is located.

In case if you are getting .class file with exactly same name but it is placed in different path then deploying that jar file is not going to help you.

Now even if path and class name matches it does not ensures that after deploying it will resolve issue, compatibility with rest of the dependent component can only be found out after deploying them.

So it is Very Strongly suggested that you should have a backup of .sda file which you deployed earlier, so that in case after deploying the services will not come-up you can re-deploy the old file and get back the services. For any of these action you don't have to restart java.

Next question is how to pack this jar file in existing sda/sca/ear file?

Secret is; all sda, sca, ear, jar files are actually a type of zip file, you can always rename them to zip and use your local zip program on your PC. Locate the directory inside the unzipped directories where you see other jar files, place your new jar file there... and look for provider.xml file in other directory

for example in our case the jar name is commons-net-1.4.1.jar so we will add one extra line in between of others.

<jar-name>lib/commons-net-1.4.1.jar</jar-name>

In the end, zip everything back and rename it from .zip to .sda, now you are ready to deploy with NWDS.

I am not going in much details because there are already material out there on net and sdn about it. For example read this note to get some idea about it

1028961 - How to prepare axisproviderlib.sda for Adapter Framework

you can also read blog Deploying JDBC drivers in PI 7.1x Systems

After deployment you can actually go and check at OS level. Like in our case this file is external file, so you can goto

/usr/sap/<SID>/DVEBMGS<NN>/j2ee/cluster/bin/ext  (ext means external)

our sda file name is com.sap.aii.af.axisproviderlib.sda

so we will find a directory named com.sap.aii.af.axisproviderlib

inside it as we put all our jars inside lib directory before zipping it back, we can find one lib directory and there we will see all the jars successfully deployed there. If you will redeploy the same .sda file after removing particular jars, then that particular jar will get deleted from OS level as well.

Now in some of your "quests" if you are looking for any class file, you know now that they will be inside some jar files, simple go to the most probable location and give this command, like I am searching for HttpClient.class I will go to /usr/sap/<SID>/DVEBMGS<NN>/j2ee/cluster/bin/ext and execute below command

find . -name "*.jar" -exec grep -Hsli HttpClient.class {} \;

.....By this I am signing off, your comments and suggestions are most appreciated

My other Blogs, if you have time...

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-I

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-II

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

Escaping tough moments of SPAM or SAINT

SAP Software Provisioning Manager : with screenshots

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

Script for deleting files within a directory structure with different retention days

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

How to Rename the Oracle Listener & Change Listener port for SAP

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Start/Stop SAP along with your Unix Server Start/Stop

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

List of Newly added/converted Dynamic parameter in NetWeaver 7.3

Sunset for ops$ mechanism: No more supported by Oracle & Not Used by SAP

Essential Basis for SAP (ABAP, BW, Functional) Consultants Part-I

Essential Basis for SAP (ABAP, BW, Functional) Consultants Part-II

Essential Basis for SAP (ABAP, BW, Functional) Consultants Part-III

The CCMS Alert Monitoring Infrastructure consists of three parts:

• Data Collection
• Data Storage
• Data Reporting/Administration

SAP provides an expert tool, the CCMS Alert Monitoring transaction RZ20 as a display transaction to report the monitoring structures
and monitoring data which are stored in the monitoring segments. Alternatively,you can use the Solution Manager to display the monitoring data in a
business-oriented context. If the system identifies a problem an alert will be created.

  In general if you complete an alert manual it means that the user thinks that the problem is solved and because of this the alert can be
completed. If the problem is really solved than with the next run of the data supplier no new alert (YELLOW or RED) will be created but if
the actual problem is not solved a new alert will be created. Now it depends on how you did setup your 3-rd Party monitoring system because
if this system does read all the ACTIVE alerts every 5 minutes than it means that after 5 minutes also the actual status of the alerts also
will be reported in the 3-rd Party monitoring system and in this way you can only use SAP CCMS to manage the alerts.

A GREEN alert means that the data supplier reports that the problem is solved (not the user).

-Working with All-Clears (Green Alerts)

http://help.sap.com/saphelp_nw04/helpdata/en/b2/dfee407552742ae10000000a155106/content.htm

Recommended notes:

414029 -  RZ20: Automatic reorganization of alerts

1055793 - Gray alerts with "(..::)" in SolMan Solution Monitoring

543414 -  RZ20: Alerts stay in status ACTION_REQUIRED

1703934 - Green alerts after monitoring pause

746193 -  RZ20: Generating all-clears ("green alerts")
382769 -  RZ20: Error messages do not generate any Alerts
1462715 - Old alerts are not visible after switching to summer time

GREEN alerts can note used for the node "Shortdumps" because a GREEN  alert is only created after the status of the node is YELLOW or

RED and after this a new message is sent with the rating GREEN and this will create the GREEN alert. For the "Shortdumps" node this will never

happen because only message with YELLOW or RED rating will be sent to this node.

For example you can use it for the OS_Collector State monitoring node becuase when SAPOSCOL id dowm a RED message will be sent and a RED
alert will be created and as soon as SAPOSOL runs again a GREEN message will be send (SAPOSCOL is running) and a GREEN alert will be created.

[...]

RZ20

Operating System
       probud2_BCS_02
           Filesystems
           CPU
           Memory
           Paging
           Swap_Space
           OS_Collector
>>>>       State    The OS collector (saposcol) is running, Green...
[...]

Often, after the project is completed, there's a need to display the system and configuration in Production server for data analysis.

To achieve this, we can adopt existing SAP_ALL profile and adjust it so that user access the system in display mode only.

Many SCN posts tell you to export the role to notepad, and then change the "ACTVT" field value to "03".

Well, this is not entirely true. You may got decent working role, but since you are not dealing with only one activity code, you can't ensure that your role will work flawlessly across departments in your company.

Common display activity codes are 03, 04, 08, 09.

Some modules uses 27, 28, 29, 53, 54, A5, etc.

You can check table TACT to list all display-related activity.

Having said that, you won't know either whether an ACTVT field can have value 03, 04, both, or all values except to browse the field one by one and maintain it manually.

This is a very time consuming process, but in the end you can finally have a reusable role that work across your projects.

Good news is, I have gone through this and you can download the role below.

It has been validated using table AGR_1251 and contain only display values across tons of object.

System: ECC 6.0 EhP7

two pans of pizza were harmed during making process

Download this File

Dear All,

I would like to share below checklist which helped me to remind of doing things before starting SUM tool while working with multiple systems in a upgrade project. After reading ECC EHP6 master guide, SUM guide, Upgrade guide and recommended SAP notes from service marketplace which is obvious separate guides and notes which I have downloaded on my disk for reference. But I needed something handy for each phase which I can print and stick it to my desk so I have created a master document in which I have created multiple sheets like below :

Master Document :

- High Level Technical Plan - Sharing / Updating this sheet weekly and sending across client steering committee for Project update

- Detail Technical Plan - A pure tech plan sheet mixed of above mentioned guides & SAP Notes

- Planning & Preparation - Checklist before starting SUM tool

- Solman Specific - Technical steps from adding system to LMDB/SMSY till STACK file generation

- Execution & Postwork - Execution phases are actual SUM phases like Initialization, Extraction, Configuration etc., and Postwork steps

- SAPNotes for reference & Monitoring log files path - Details from SAP notes like keyword from note: 1790828, Increase DB process in case of error in Preprocessing phase refer note : 34432.

Below is the example of Planning & Preparation sheet I will try correct and post remaining sheets from above document soon.

Source : SAP ECC 6.0 EHP2 with Oracle 11g on RHEL 6

Target : SAP ECC 6.0 EHP6 with Oracle 11g on RHEL6

Thanks & Regards,

Salim

1. Check whether ADS is installed on PI Java Stack

    2. If it is installed, Configure the communication between PI and ECC

• Download support package ADSSAP07_0-10009589.SCA (SP07for ADOBE DOCUMENT SERVICES 7.31) from SAP support portal.
• Upload SCA file to AS Java server (any temp location).
• Logon to AS Java server console via SSH with <sapsid>adm user.
• Execute telnet localhost <telnet port> and login with administrator of AS Java user (Administrator or similar).
• Execute lsc (refer to SAP Note 1715441)
• Deploy SP07 for ADOBE DOCUMENT SERVICES 7.31
  (refer to http://wiki.scn.sap.com/wiki/display/TechTSG/(JSTSG)(Telnet)DeployController+Commands?original_fqdn=wiki.sdn.sap.com)
  with command:
  
  deploy /tmp/ADSSAP07_0-10009589.SCA on_deploy_error=stop
  Note: during deployment of ADSSAP component AS Java server instance is restarted.

1. Log on to the ABAP system, call transaction SM59,and select 'ADS' from 'HTTP connection to ext. server'.
2. Specify the server name and http port number of the additional stand-alone AS Java.
3. You also need to update the corresponding user and password information on the 'Logon/Security' tab.

4. Make sure that create the user ADS_AGENT with the
corresponding role SAP_BC_FP_ICF and SAP_BC_FPADS_ICF exist in AS ABAP. If this
user does not exist, create it according to the steps in ADS Configuration
Guide.

6. Choosedefault_host→  sap  → bc →  fp in the tree.

7.Choose Service/Virt.Host  →  Activate

8. If AS ABAP and AS Java (with ADS) are installed in different systems, and you want to bundle your forms to
     improve performance, you also have to activate the fpads ICFservice.

1. Log on to the NetWeaver Administrator of your additional standalone AS Java.
2. Select Server -> Service -> destination -> HTTP.
3. Create an entry 'FP_ICF_DATA_<SID>',   where <SID> is the ABAP backend System ID.
4. Enter the ABAP HTTP port (http://<servername>:<port>) in the 'URL' field.
5. Enter the user 'ADS_AGENT' in the User name field, and the corresponding password of ABAP backend system.
6. Save your entries.

 

Note: When
you do ping test for the destination the result can be “Error 404: Not found”.
This is normal.

 

As Java configuration for WebDynpro Application:

 

1.    Log on to the NetWeaver Administrator of your additional standalone AS Java.

 

2.    Select SOA Management -> Technical Configuration -> Destination Template

 

3.    Management

 

4.    Select'Create Destination' and Enter following entry:

 

5.    Destination Type: WSIL

 

6.    Destination Name: ConfigPort_Document

 

7.    URL:http://<standalone AS Java server name>:<http port>/inspection.wsil

 

8.    SecurityTab

 

9.    Select Authentication 'HTTP Authentication' and 'User ID/Password (Basic)'

 

10.  Select 'Details' and enter the user ADSUser and the corresponding password.

 

11.  Select 'Save

 

Testing ADS Configuration:

 

·       Checking ADS Configuration in an ABAP Environment

 

1.  Log on to the AS ABAP system.

 

2.  Start the transaction SA38.

 

3.  Enter the program name FP_TEST_00.

 

4.  Choose Program Execute (F8)
.

 

5.  Make sure, that the following default values are entered in the respective fields:

 

o  Form:FP_TEST_00

 

o  ADS Connection:
ADS or the RFC Destination name specified in your system (if it does not
correspond to the default entry)

 

6.  Choose Program Execute (F8)
.

 

7.  Enter the Output Device.

 

8.  Choose Print Preview.

 

9.  If the system displays a form containing several lines on two pages, the ADS configuration is correct. Otherwise, perform the
tests described below.

 

 

·       Checking the ABAP Connection to ADS

1. Log on to your SAP system.
2. Start the transaction SA38.
3. Enter the name of the test report FP_PDF_TEST_00.
4. Enter the name of the connection. Enter the default name ADS, or, if you have specified another name, the one you are using in your system.
5. Choose Execute (F8).
6. If the configuration is correct, the system displays the version number of the Adobe Document Services.

1. Log on to your SAP NetWeaver AS ABAP system.
2. Call transaction SA38.
3. Enter the name of the test report
   FP_CHECK_DESTINATION_SERVICE.
4. Execute the test without choosing the option With
   Destination Service.
5. The system renders a test form in the background
   without using the destination service and displays the size of the created PDF.
6. Execute the test again. Now select the option With
   Destination Service.
7. If the settings of the destination service are
   correct, the system displays the same message as before (see step 5).

We were using SUM 1.0 SP10 Patch 3 for upgrading the JAVA system/DUAL System. We got an error in Execution phase in step Import cr-sda models.

The ERROR which was recorded in IMPORT-CR-SDA-MODELS_01

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[G:\SUM_xxx\SUM\sdt\log\SUM\IMPORT-CR-SDA-MODELS_02.LOG]/-->

<!--PATTERN[IMPORT-CR-SDA-MODELS_02.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Apr 23, 2014 11:47:28 AM [Info  ]: About to process archive G:/SUM_xxx/SJL_Download/LMMODELNW04_0-20009684.SCA. The CR-SDA content will be extracted first.

Apr 23, 2014 11:47:28 AM [Info  ]: About to import archive G:\SUM_xxx\SUM\sdt\tmp\sap.com~product~lm-model-nw.sda.

Apr 23, 2014 11:48:17 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.j2ee.tools.feimport.FunctionalElementsImporterException: Cannot import file G:\SUM_xxx\SUM\sdt\tmp\sap.com~product~lm-model-nw.sda. See next messages for details.

com.sap.sdt.sldeploymentlib.SLDeploymentException: CIM_ERR_FAILED: CIM model version insufficient, version in <local>, namespace active is 1.6.17, but should be greater or equal to 1.6.37

com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: CIM model version insufficient, version in <local>, namespace active is 1.6.17, but should be greater or equal to 1.6.37

SOLUTION TRIED :

We have upgrade the CR Content and CIM Model to latest patch , but error was not resolved.

Searched in SCN :

We have looked for the error in SCN community and found that its a bug in SUM 1.0 SP 10 patch 3.

1. Re: CIM_ERR_FAILED: CIM model version insufficient

2. SUM Netweaver 7.4 Java SP update error

.

SOLUTION :

Reset the upgrade and start the upgrade with SUM 1.0 SP8 patch (X) or SUM 1.0 SP9 patch (X).

Hope this will help you all

With Regards

Ashutosh Chaturvedi