of course it depends what is in the transport but its always a good solution to do transports at times with low activity like lunch or evenings

 

for program-changes, there might occur a DUMP (/NST22) Type LOAD_PROGRAM_LOST, this is nothing critical as the next time when the user calls the program it will be the new version.

 

For Classes (typical CRM) there might be DUMPS with LOAD_PROGRAM_CLASS_MISMATCH (Users have to re-login into CRM Session again)

for CRM it might be necessary to reset Shared Memory (Webui caching) using /NSHMM see  KB http://service.sap.com/sap/support/notes/1870987

 

most critical are changes in data dictionary structures (tables and structures):

 

if after a transport into the production system a lot of transaction generate a short dump with 'LOAD_TYPE_VERSION_MISMATCH', one of the transported tables/structures/append was used during generation of the new structure which causes a mismatch in dictionary and not matching with the current load of the abap reports.

if this is for example VBAP or BSEG, you might have thousands of dumps in a short time an nobody can work

 

the table is active in data dictionary and also the new field is corretly transported, its just a load-version that does not match. solution is described in sap note 1567187 - LOAD_TYPE_VERSION_MISMATCH

 

in the dump you see the table name which causes the problem

first you should just activate this table in se11 again

 

if this does not help, use program TOUCHTAB, after that all programs using this structure will be generated next time someone calls the report (this takes just a sec, or select 'direct generation' for immediate generation - this will take some time

if you have multiple appservers they need to be restarted (you can try with transaction code $sync first)

 

 

another common issue with transports into production is, that if a db-index has to be re-generated, the update process is stopped during the generation,

this might be too long for large tables

Many a times you raise an incident with SAP Support about a performance issue on Java server, only to realize that you missed saving the necessary logs. The problem you face now is : You have already restarted the system or the problem seems to disappear  but you still need the root cause lest the problem should appear again

This article provides you some guidelines on which logs need to be collected before you trigger that all important "restart" of Java server.

 

 

1) Slow Java start-up : That moment when you wait forever for the state to change from starting application/framework to running

- Thread Dumps(Most Important) : When the start-up or the system even when it is up hangs, trigger thread dumps. To do so, use these notes depending on the Netweaver release

 

1955835 - AS Java server node hangs at starting phase - What To Do for 7.0X

1953845 - AS Java server node hangs at starting phase - What To Do for 7.10+

 

 

You need to capture at-least 3-4 dumps at an interval of 1 minute. This is done to get a complete picture of the hang situation. For example, if a thread consistently shown as blocked/hanged in all the thread dumps then the problem lies there. You can also do thread dump analysis on your own using the tool in SAP note#1020246 - Thread Dump Viewer for SAP Java Engine

 

Apart from the above method, you can use SAPJVM profiler tool as well. The SAP JVM Profiler helps to analyze the resource consumption of a Java application running on a SAP Java VM.

To collect profiling information for a slow start-up , use the SAP Knowledge Base Article(KBA) 1995883 - Analyzing slow AS-JAVA startup using the SAPJVM profiler. Send the output *.prf file to SAP Support.

 

 

2) High CPU consumption : You have situations where some Java processes start consuming High CPU. It is very important to collect the right logs while the issue is happening. Thread dumps come handy here as well but for systems running on SAPJVM, it is recommended to use SAPJVM profiler to collect the required data. For this, use the SAP KBA#1783031 - Analyzing AS Java performance with SAP JVM Profiler

 

 

3) Outofmemory issues. Many a times you'll see Java server restarts/becomes unresponsive with "outofmemory"(dev_serverX log in work directory says "JControlCloseProgram: good bye... (exitcode = 666)" or "java.lang.OutOfMemoryError "). The most important log file is the heap dump generated during the crash. This dump will usually be found  /usr/sap/<SID>/<instance>/j2ee/cluster/serverX. It will normally have the format *.hprof. The size of this file will be equal to the heap memory consumption at the time of the crash. Send this file to SAP support before deleting it permanently. This file is automatically generated if the profile parameter is set.  Note 1004225 - How to create a full HPROF heap dump of J2EE engine ; will help you in setting these parameters.

 

 

4) Slow response from the server/ enterprise portal: Here again thread dumps and SAPJVM profiler output are needed. Capture the logs when the issue is occurring in the same way as for slow startup.

 

 

6) It is always recommended to attach these logs while raising an incident 1) Logs mentioned in 1867207 - Collecting traces to troubleshoot Netweaver AS Java runtime/startup issues 2) SAPMMC snapshot : Refer to KBA 1847251 How to create an MMC snapshot about an SAP system. If the issue is not reproducible at will, mention the last time-stamp when the issue occurred(of course, attach the logs from the same time period). In addiction, do inform about any changes that were done on the system.

Background:

Like we all know, there is an option to push the data from an ABAP only satellite system to a Java only based SLD. However, the same old technique doesn't help when you have your SLD on a netweaver platform equivalent or above 7.3.

 

We have recently completed 7.4 AEX (Advanced Adapter Engine Extended) on Linux platform with Oracle DB. Post AEX installation, we have decided to push the data of our existing ERP system to the SLD of the newly installed AEX. As we all know, in a Java only SLD system, we have to edit the profile at the SLD level to adapt and use the gateway of an existing ABAP system of your choice (may be highly available) to receive data from the ABAP only systems (eg. ERP). The same approach did not help as Java itself has its own gateway service/process from NW 7.3 and above as shown below.

 

<host name>:<sid>adm 51> ps -ef|grep gw

<sid>adm 10542 10522  0 Nov05 ?        00:00:10 gw.sap<SID>_SCS01 pf=/usr/sap/<SID>/SYS/profile/<SID>_SCS01_<host name> -no_abap

 

Solution:

As we have the Java only SLD on NW 7.4, you can use its own gateway service provided you set the parameter "gw/acl_mode = 0" in the SCS instance profile of SLD. But, this parameter can also be set to 1 ensuring that you have properly maintained the reg_info and sec_info files in your Java only SLD system.

 

Once you are done with maintaining this parameter, you have to restart the SLD system (SAP) and proceed with the below steps.

 

Steps to be followed in your Java only SLD system:

Launch SLD (http://<host name of SLD>:5<instance number>00/sld).

Click on administration

Click on Settings


 

In the Section drop-down, select ALL. Ensure you have the entries maintained for Gateway Host and the Gateway Service as shown below.


 

Save the settings. Restart the SLD.

 

Steps to be followed in your ABAP only satellite systems:

Go to RZ70, adapt the gateway parameters as shown below.

 

 

Activate these settings and click on “Start the data collection”.

This should push the information of the satellite ABAP only system to the Java only SLD.

When I am in Projects I see often that People do not understand how certificates work,

However this is easy to answer...

 

A Protocol like https, ldaps or what ever need certificates to work secure as the encryption is

based on the them. You can have selfsigned certificates (normal case when you have just installed a Netweaver System)

or CA signed certificates. Using self signed certificates in a Project can make a lot of effort, use a CA when ever possible.

 

But why there are certificate errors?

Once the communication starts the Caller check the following things in the Certificate he received:

1. Do I know the Issuer of the certificate?

2. Is the certificate in a valid time window.

3. Is the CN exactly that what was called

 

How to check whats wrong with the Certificate?

 

1. Do I know the Issuer of the certificate?

 

 

 

Check the certificate:

CA Certificate_1.png

 

If  you don't trust this CA or self signed certificate it looks like this:

CA Certificate_3.png

Read and execute

To Trust the certificate import it:

CA Certificate_2.png

CA Certificate_1.png

CA Certificate_1.png

CA Certificate_1.png

CA Certificate_2.png

Now you trust the Certificates from this Issuer.

If you still receive Errors check the next Question:

 

2. Is the certificate in a valid time window.

After some time Certificates are on their EOL. ^

You can check easily by looking into the Valid from - to Property

CA Certificate_3.png

 

The most common problem come from different CNs what bring us to the last question:

 

3. Is the CN exactly that what was called

Each Certificate have a CN Which you can see in the Issued to Property:

CA Certificate_3.png

Assuming this certificate is issued to CN=hostname.domain.local, ensure that you exactly call this within your application,

otherwise it will fail.

Often in Projects is that someone calls https://hostname:port/application instead of https://hostname.domain.local:port/application

and then is blaming about certificate errors


Hi,

 

To segregate the developments in the phases of project deployments/ BU implementations, you can create a local project and assign the transports.


different Phases like

  • Development phase
  • Break fix phase etc.

 

     Go to t code SPROJECT_ADMIN


1.png
  Click on create
 
  2.png

Give the project name

3.png

Fill the required details

6.png

 

Once you fill the details go to transport requests tab

5.png

Click on Activate CTS functionality as below, to enable the

transport functionality.

 

Then the CTS functionality will activated.
        

Thanks

Seshu

Hi,

 

I tried local client copy after installation while scheduling the client copy the below error came and solved as below.

 

Local client copy
error:  FINBTR@<SID>CLNT<client> destination not exist error

 

 

When I tried to
perform a client copy I got the above error in new system (after installation).

 

 

Create entry in SCC4 for new client

 

And logged in the target client

 

T Code: SCC4

 

Source 001

 

Target is 100

 

1.png

  •      Clicked on schedule as background job and next screen as
    below

 

2.png

 

 

After this click on schedule job.

 

  • Then it gave an error with a pop up of FINBTR@<SID>CLNT<client>
    destination not exist

 

 

Solution:  Create the above destination by clicking on WIZARD option in the pop up (once the
error came)

 

 

  • It will open new screen and continue with RFC creation and
    give a password and proceed next.
  • Then the RFC will be created successfully and the actions as
    below.

 

3.png


  

Click on tick mark and check sm59 ….FINBTR* RFC will be
created.

 

 

Now you can proceed with client copy without any error.

4.png

and continue

5.png

 

successfully completed.

 

 

 

Thanks

Seshu


Hi Experts,

 

I will explain the procedure for changing released TR into unrelased TR. i.e; modifiable state. There is no option given explicitly for chaning the released TR into unreleased TR in STMS or SE01 Transactions. we have to follow the below steps.

 

1. Go to SE38

2. execute the report RDDIT076

 

To_Blog_1.JPG

 

3. now, we will get the below screen which asks for TR/Tasks . give the released TR number and execute (F8)

 

To_blog_2.JPG

4. Once executed, you will get the below window,

To_blog_3.jpg

 

5. first we need to change the task to unreleased. double click on the task number. now, click on the pencil button to enter edit mode.then click on input help on the filed "Status"

 

To_Blog_4.jpg

6. change the status from "R" to "D" and save

To_blog_5.jpg

7. now repeat the steps 5 and 6 for Transport request. finally the status column should be in "D" as shown in below. To_blog_6.jpg

 

8. now goto SE01 or SE09, type the TR number and check. it will be in modifiable state.

 

Cheers,

Pradeep

[symptom]

  • When you access NetWeaver java for example NWA, portal,
  • You see script error relevant to messagebundle_xx_XX.properties. e.g. messagebundle_ja_JP.properties
  • Or in httpwatch trace, you see the 404 request like:404 messagebundle_ja_JP.properties.PNG

 

[reason and prequist]

This 404 JS error is not real error and can be ignored.

The user has been assigned the locale as "ja_JP" and the resourcebundle for Japanese is with "_jp" and not with "ja_JP".

So first it tries to look for the locale specific file if not found it loads the language based file which will works.

 

[Solution]

None

The SAP Net Weaver Application Server is a web application server defined for SAP solutions. The Web AS is the base on which most of SAP products operate. The SAP application server consists of five layers including presentation layer, business layer, integration layer, connectivity layer, and persistence layer. However, the SAP Net Weaver Application Server supports HTTPS for encrypted communication. In this article, we will reveal about installation of SSL certificate into SAP Web Application server 6.10+.


Before going through the installation of SSL certificate, we have to aware about SSL Server PSE (Personal Security Environment). It contains the application server’s security information that is being used while SSL communication. It is a certificate list used by the server for the authentication purpose. The application server makes use of this list to decide which CAs the server believes. Now let us go through the procedure of SSL installation into SAP server.


Generate CSR:


To install SSL certificate, you must create a certificate request (CSR) that uses an SSL server PSE. Check individual SSL server PSE in Trust Manager by elaborating SSL server PSE node and click on the server, it appears the server’s name and for which you have to generate the CSR.


Procedure


  • Browse Trust Manager and expand the SSL server PSE node.
  • Select the application server, in the PSE maintenance section it shows the application server’s certificate.
  • Select “Create Certificate Request” from the PSE maintenance section, and a dialogue box will be there showing the certificate request.
  • Select the content shown in the certificate request and copy or save the content to a local file (<file name>.P10).

 

Installation of SSL certificate on SAP Net Weaver Application Server 6.10+:


  • Download the Intermediate Certificate and save as it as "intermediate.crt" on your server.
  • Open the Trust Manager and click to elaborate the SSL server PSE node.
  • To assign an individual Certificate to each application, you should follow the below steps.
    • Click on the desired application server, you will see SSL server PSE in the PSE maintenance section.
    • Import Cert. Response. You will find a dialog box for the certificate request response.
    • In the dialogue box, paste the content of Certificate Request Response or select the local file from the system.
    • Now, you can see in the PSE maintenance section a signed public key certificate that is imported into the SSL server PSE.
    • To view information about the imported certificate, click on it. The details of the certificate will be shown in the certificate maintenance section.
    • Finally, save the complete data.

 

Importing the CA's Root Certificates if Not Located in the Certificate Database


  • Go to Certificate section and select “Import Certificate”, it will show a certificate dialogue.
  • Choose the Database tab.
  • Choose the certificate from the certificate database and select Enter.
    You can see the certificate in the certificate section.
  • Now, select “Add to Certificate List”.
    The certificate will be added to the certificate list, which you can see in the PSE maintenance section.
  • Save the data.

 

Importing the CA's root certificate from the File System:

  • Go to Certificate section and select “Import Certificate”, it will show a certificate dialogue.
  • From the file system, enter the suitable file name and choose the file format. In case, if you are not sure about the certificate’s file format, then open the certificate in a Notepad. If the content of the certificate is readable then it is a Base 64 format.
  • You can see the certificate in the certificate maintenance section.
  • Now select “Add to Certificate List”. The certificate will be added to the certificate list, which you can see in the PSE maintenance section.
  • Save your data.

 

Importing the CA's root certificate from Different PSE:

  • Click on SSL Server PSE node to choose the application server. Check PSE maintenance section where PSE and the certificate list will be shown.
  • You can see the certificate in the certificate maintenance section. Click on the certificate.
  • In the SSL server PSE node, choose a single application server with a double click.
  • Now select “Add to Certificate List”. The certificate will be added to the certificate list, which you can see in the PSE maintenance section.
  • Save your data.
Samuli Kaski

HTTPURLLOC demystified

Posted by Samuli Kaski Jun 4, 2014

Recently I had to configure table HTTPURLLOC in order to support a scenario where users were either accessing the system externally through a hardware reverse proxy connected to SAP Web Dispatcher or the SAP system directly. In this blog I want to share my experience with SCN members.

 

The first take away from this blog is that HTTPURLLOC can't be used for switching from one protocol to another nor rewriting URLs, that happens elsewhere (e.g. Web Dispatcher modification rules, portal configuration, ICF node settings, etc). HTTPURLLOC has values with valid protocol, host and port combinations that can be used to generate URLs, otherwise the generic URL generation of the system is used. That is why HTTPURLLOC is called an exception table, not a URL generation table.

 

So now how does it work? Basically the system looks at the request object and tries to determine the requested host, this is usually the virtual host name, DNS alias, etc. which was requested by the client, e.g. the browser. This is the second take away. The host as requested by the client should be preserved throughout the request, even if there are other proxies, load balancers, etc. in the loop. If the client browser requests abc.company.com, this host should be visible in the request object of the SAP system. The only way to guarantee it is that all appliances/programs are instructed to preserve the host that was requested by the client. Apache has the PreserveProxyHost directive for it, Web Dispatcher does it automatically, others might require further configuration.

 

The third take away is that as with the host requested by the client, the protocol used by the client must be preserved as well. This is especially important if HTTPS is terminated before the request hits the SAP system. Again, configuration directives might be required to insure this. Apache has the RequestHeader directive which can be used to set variable clientprotocol to either HTTPS or HTTP depending on the scenario. Web Dispatcher does it automatically assuming wdisp/add_client_protocol_header is set to true, others might require further configuration.

 

The fourth take away is to understand how entries in HTTPURLLOC are matched against the request. The most important variable is the protocol, second most important variable is the host, third most important variable is the application and last one is the domain. If the client requested abc.company.com with protocol HTTPS and assuming that the host and protocol are preserved meaning the SAP system sees the original values, the HTTPURLLOC table is queried first for all entries that have the protocol HTTPS. Next the requested application is checked, then the domain and finally the host. There are several rules which will affect the end result meaning whether the entry in HTTPURLLOC will be used or not, the best way is to figure it out yourself by debugging method IF_HTTP_SERVER~GET_LOCATION_EXCEPTION of ABAP class CL_HTTP_SERVER.

 

The fifth take away is to understand that HTTPURLLOC is client specific and especially if you are using System Logon, you will have to configure HTTPURLLOC for client 000 as well as the clients you use.

 

The sixth and last take away is to understand that in case the requested host is unknown (it is possible in some scenarios), HTTPURLLOC will be queried based on the protocol and the first match will be used (in ascending order, based on SORT_KEY).

 

Update 11/22/14: in case you want to generate URLs in an offline scenario (background job, classic GUI transaction, basically anything where there is no IF_HTTP_SERVER object), you should create a default entry in HTTPURLLOC and set the SORT_KEY value to the smallest value of all entries. For example, if you want to generate all NWBC URLs with specific protocol, port and host values, create an entry with the lowest SORT_KEY value and set the application to /NWBC/. That way, regardless in which context the NWBC URL is generated, the URL to NWBC will be generated using the values you specified with the lowest SORT_KEY. The key here is to set a value for APPLICATION.

 

I hope this blog will save others time and headaches trying to figure out the mysteries of HTTPURLLOC. See also the official documentation on URL Generation in an AS-ABAP - Web Dispatcher Configuration.

Introduction

 

 

The upgrade of our BI 7.01 (ABAP+JAVA Dualstack) was requested by our BW-team. They wanted
to use the new features of NW 7.3. The better integration of the BO tools was
also a benefit of an upgrade. The upgrade was divided into two parts:

 

 

Part 1: The Dual Stack Split.

 

This procedure separates the JAVA stack from the ABAP stack.  Before the dual stack split the JAVA and ABAP runs under one SID. After the split you have two SIDs (the old SID for ABAP and one new SID for JAVA).

 

Part 2: The Upgrade

 

This was an usual upgrade.

 

 

The Problem

 

Before the split we had this topology:

blog1.png

After the split and the upgrade the HA features didn't work anymore In a dualstack system the sap gateway service is addressed by sapgw$$. $$ is substituted by the actual system number.

 

The following picture shows the topology after the split:

blog2.png

The problem is the Gateway service.  sapgw00 is configured in several destinations, in the UME and the JCO.

It was quite plain to me. The gateway service is HA critical!

 

A little shame on SAP

 

This is what you find about "high availability" in the documentation of the Dual stack split:

blog3.png

In the installation documentation of a java stack you find the HA configuration of a "normal" java stack! But what is the difference between a "normal" java stack and a split java stack? It is the UME! In a split java stack the UME is in ABAP!  I'm very glad to know that nobody heard my comments when doing the HA cluster test on our production system!!!

blog4.png

In this picture you see the topology of a HA java stack (found in the installation guide).  But what is to do,  when using the java stack in a BI system with HA? I know somewhere in the paper jungle of SAP you can find something. But sap gives no hint in the standard documentation

 

The solution


The following configuration needs to be changed:

 

1. separate the gateway service
2. logon groups in ABAP
3. the UME Backend Connection
4. JCo RFC-Provider
5. SLD

 

Separate the gateway service. OSS note 1010990 " Configuring a Standalone Gateway in an HA ASCS instance" explains how to configure the gateway service.

 

Step 1:
*Changes to the exe-directory
sidadm> cdexe               

*gives you the path <exe_path> of exe-directory
sidadm> pwd                    

*edit the sapcpe config file
sidadm> vi <exe_path>/scs.lst      

*add this line to the file      
gwrd                       


Step 2:
*Changes to the profile-directory
sidadm> cdpro                  

*gives you the path <pro_path> of profile-dir.
sidadm> pwd                    

*edit ASCS instance profile
sidadm> vi <pro_path>/<SID>_ASCS<Sys.Nr.>_<hostname>

*add this line to the profile
gw/netstat_once = 0         

Step 3:
*edit the start profile of ASCS

sidadm> vi <pro_path>/START_ASCS<Sys.Nr.>_<hostname>

*Search the first Start_Program_<xx>-entry in the profil, then enter
_GW=gwrd$(FT_EXE)


*earch the Start_Program_<xx>-entry with the highest value of <xx>, then enter:

Start_Program_<xx+1> = local $(DIR_EXECUTABLE)/$(_GW) pf=$(DIR_PROFILE)/<SID>_ASCS<Sys.Nr.>_<hostname> -no_abap

 

Step 4:
*check in /etc/services the entries:
sapgw<Sys.Nr.>
sapgw<Sys.Nr.>s

 

restart system

The new gateway service is sapgw<Sys.Nr.> because of the system number of ASCS.

 

logon groups in ABAP

 

Logon to the ABAP system and enter transaction SMLT. Configure for each Instance a logon group (in the picture it is PUBLIC)

blog5.png

 

UME Backend Connection

 

Comment

You can determine the hostname of

- message server (1)

- gateway server (2)

(1) The name of the Instance Profile of ASCS is <SID>_ASCS<Nr.>_<hostname>

(2) Same hostname as hostname of ASCS

 

http://<hostname>:50<Sys.Nr. of java>0/nwa

  ->Configuration

  ->Infrastructure

  ->Destinations

blog6.png

blog7.png

blog8.pngblog9.png

 

JCo RFC-Provider

 

http://<hostname>:50<Sys.Nr. of java>0/nwa

  ->Configuration

  ->Infrastructure

  ->Destinations

blog10.png

blog11.png

blog12.pngblog13.png

blog14.png

 

http://<hostname>:50<Sys.Nr. of java>0/nwa

  ->Configuration

  ->Infrastructure

  ->Jco RFC Provider

blog15.png

blog16.png

blog17.pngblog18.png

 

Login to the ABAP BI system. Go to Transaction SE16 -table-> RSPOR_T_PORTAL

blog19.png

In field RFCDEST you can find the JCo RFC-Destination in ABAP. Go to transaction SM59 and find the RFC destination.

blog20.png

Enter the gateway configuration

 

SLD


http://<hostname>:50<Sys.Nr. of java>0/sld
  ->Administration
  ->Settings

blog21.png

blog22.png

Logon to ABAP BI system and go to transaction SM59. Enter the gateway configuration (like in RFC destination of JCo) in the following  RFC destinations:


blog23.png

 

EPILOG

 

Be aware: You get no hint in the documentation of the dual stack split or the installation about the correct HA settings.

 

 

 

Best regards

Willi Eimler

I noticed that recently many of you have problems implementing this note, while in transaction SNOTE  the following error message is displayed when downloading SAP note 1900200 - "Directory traversal in BC-SRV-ARL":


SAP Note 0001900200 incomplete

     Message no. SCWN106

Diagnosis

     SAP Note 0001900200 is incomplete.

System Response

     This SAP Note cannot be imported.

 

Follow the (general procedure from) SAP KBA 1939285 - "SCWN106 - SAP Note incomplete in transaction SNOTE or SPAU" in order to implement the note.

I would like to share with you that I'm currently engaged in one of my personal projects creating the Generic Object Services (GOS) Troubleshooting Guide.

Please check it and update me with your feedback in a direct message on SCN. More information about GOS can be found in the online help documentation.

The GOS FAQ (created in 2009 and updated frequently) can also provide helpful information regarding the most common questions in GOS, but I decided to create this troubleshooting guide to provide step-by-step guides for errors and questions on the behavior in different scenarios.

When you using GOS toolbox menu in some transactions the Attachment list service is active, but when you opened it there are no attachments in it. Previously this was the designed behavior when the application published GOS with more than one business object. Recently an enhancement was released in SAP note 1966453 in order to give the control to the customers to decide:

 

  • have a consistent behavior of the active / inactive status of the Attachment list, so when no attachment exists make the service always inactive or as usual active when there is least one attachment in it, but in this case some delays may occur when the GOS toolbox menu is opened

OR

  • have the standard behavior, so when the application publishes GOS with more then one business object the Attachment list stays always active and in this case no performance problems can happen

 

You can find more information about this in the GOS Troubleshooting guide under the section The Attachment list is active, but no attachment displayed in it and in SAP note 1966453.

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

Posted by Ishteyaque Ahmad in SAP NetWeaver Administrator on May 22, 2012 11:41:22 AM

 

 

There are various materials present about features of SAP NetWeaver 7.3 but not all of them are directly useful for Basis people like us. So I thought to collect some of differences/features which I noticed.

I know some folks will say that not all features are introduced in 7.3 some of them were introduced in 7.1 and 7.2, but I am a greedy man and I wanted to increase number of features in this blog so I included them as well. Beside it will be helpful to those who haven't got chance to work with 7.1 or 7.2 and directly started working with 7.3.

So lets begin...

 

1. SAP NetWeaver 7.3 Goes Green

 

With NW7.3 you can save more energy from architectural perspective, you can get details of it here, I find it interesting.

http://scn.sap.com/community/sustainability/green-it/blog/2011/06/06/sap-netweaver-73-goes-green

 

2. SAP NetWeaver 7.3 – Lean Avatar

  • In the process integration, a Java-only, lightweight advanced adapter engine is now available for NetWeaver 7.3, eliminating the need to run SAP NetWeaver Process Integration (SAP NetWeaver PI) as a dual stack.
  • From SAP NetWeaver 7.30, customers can reduce their hardware needs as a result of common deployment options for all Java usage types, including enterprise portals, SAP NetWeaver BW, and SAP NetWeaver Composition Environment (SAP NetWeaver CE), with one unified Java application server.
  • NetWeaver Portal 7.3 uses half as much memory on average to execute navigations.
  • NetWeaver Portal 7.3 server node starts up much faster than 7.01, with improvement of 33% in average.

 

3. Instances Naming convention

As of SAP NetWeaver 7.1, the concept and naming of SAP system instances has changed. The terms “central instance” and “dialog instance” are no longer used. Instead, the SAP system consists of the following instances:

  • Application server instances

Application server instances can be installed as “primary application server instance” (PAS) or “additional application server instances” (AAS).

  • Central services instance
  • Database instance

 

4. The Central Services Instance ABAP - ASCS

The central services instance for ABAP (ASCS instance) is now installed with every SAP ABAP system distribution option: Standard System      Distributed System      High-Availability SystemThe enqueue replication server instance (ERS instance) can now be installed  together with the central services instance for every installation :

  • Standard System (optional)
  • Distributed System (optional)
  • High-Availability System (mandatory)

ERS.pngAt the time of SCS installation if we can select the above option it will install ERS instance as well.Though I am such a naive person who is failed to understand the purpose of having ERS instance on same host where we are having Enqueue server.

5. The Central Services Instance ABAP - ASCS

With new Installation Master for ABAP+Java, SAPInst does not provide option for separate ASCS and SCS Instance.  Though it can be separated manually after installation on different host.ASCS.png

6. Split Off ASCS Instance

SAPInst now has an option to "Split Off ASCS Instance"With the option Split Off ASCS Instance from Existing Primary Application Server Instance, you can split off an central services instance for ABAP (ASCS instance) from the primary application server instance of an existing ABAP system or ABAP+Java (dual-stack) system.ASCSsplit.png

7. Solution Manager Key

As of SAP NetWeaver 7.3, Solution-Manager-Key at the time of Installation is not asked/required by SAPInst.Even in previous installation people found out the way to generate the Solution Manager Key out of SolMan System.http://kohanov.com/tmp/sap_keys.vbs

8. Start Profile Merged

As of SAP NetWeaver 7.3, Start Profile has been removed as separate file.In earlier versions of NetWeaver there were 1 Default profile per SAP system, 1 Start profile per Instance and 1 Instance profile per instance.Now the Start profile contents are merged with Instance profile. With help of new Instance profile SAP processes are started and at the same time instance specific parameters are read.This removed total number of profile files. 1 Default profile per SAP System, 1 instance profile per instance. Now Profile Directory will look neater !!

9. JSPM (Java Support Package Manager) Initial credential requirement changed

  • While starting JSPM – SDM password is not being prompted, Instead you need to provide Java Admin User ID and password.

jspm.jpg

  • While deploying and upgrading components it needs restart of just Java and sometime complete SAP restart, for which Admin User ID at OS level and its password is asked.

jspm2.jpg

  • SDM is replaced with JSPM and directory SDM is altogether removed.

jspm3.jpg

  • Un-deployment of SCA’s/EAR files are not possible using JSPM. You have to use NWDI for this purpose.
  • No support for PAR files. All portal applications are now EAR (Enterprise Archive) based, PAR migration tool for converting PAR files to EAR files

10. JCMON changed menu

 

jcmon.jpg

After NetWeaver 7.01 JCMON menu 20: Local Administration Menu is non functional.

jcmon2.png

Select opton Solid Rock ....  name is funny I mean Rocks are solid anyway

and you will able to see which state of different components/nodes. Unlike previous version I didn't find refresh option here, so go back and come to this menu again for recent view.

 

11. Visual Admin Vs NWA

 

As of SAP NetWeaver 7.1, Visual Admin has been replaced with NWA

VA&NWA.png

 

12. Support Pack Stack

 

NW7.0SPLevel.png

Earlier in NetWeaver 7.0, For a Support Pack Stack the  release level of BW component was generally  2 release ahead of the ABAP and Basis component.

Now all components are  released on same level.

NW7.3SPLevel.png

Please continue with second part of this blog.

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

Actions

Filter Blog

By author:
By date:
By tag: